BT-769-Lot (Multiple Tenders)
Closed this issue · 4 comments
This field is effectively a boolean. However, it is mapped to a (new) string field SubmissionTerms.multipleTendersPolicy
. Is there a reason not to map it to a boolean field in OCDS?
Also, in keeping with OCDS's terminology, I think the field should be called multipleBids
rather than multipleTenders
.
I don't think it's a boolean. I uses the permission codelist, which has 3 values: https://op.europa.eu/en/web/eu-vocabularies/concept-scheme/-/resource?uri=http://publications.europa.eu/resource/authority/permission
We tend to use the Policy
suffix for fields that use a permission codelist.
Agree to substitute Bids
for Tenders
.
For this field specifically, only the 'allowed' and 'not-allowed' values from the permission codelist are permitted (that's what I meant by effectively a boolean):
The Multiple Tenders business term allows to specify for a given Lot whether a tenderer may submit more than one tender ("allowed") or not ("not-allowed"). This information is marked using the "cbc:MultipleTendersCode" for which only the two previous values of the permission codelist are accepted.
Ah, good catch! (but also what a confusing way to design their schema)
So, yes, the boolean can be named multipleBidsAllowed
.
PR for updates: open-contracting-extensions/ocds_submissionTerms_extension#4