-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Value fields: remove "total" #1207
Labels
Milestone
Comments
JachymHercher
changed the title
Value fields: "procurement", "total" and "upper"
Value fields: remove "total"
Feb 7, 2021
I think "estimated" is important, otherwise data publishers may think the field only supports a fixed value. |
@JachymHercher I support the changes to award.value and contract.value. For tender.value, did you mean to delete "total" instead of "estimated"? |
Yes, corrected, sorry. |
(To avoid unnecessary conflicts, I will create the PR for this issue once #1208 is merged (it moves around some value fields).) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Value fields in OCDS often use the term "total". I am not sure what it means and I think it might be misleading, e.g. because a "total" value field might be tax-less (see #817) or represent just a single award, contract a lot from a contracting process that contains more of them.
I would suggest replacing:
tender.value
award.value
andcontract.value
.The text was updated successfully, but these errors were encountered: