-
Notifications
You must be signed in to change notification settings - Fork 40
Tailored code list procedure-type-16 and schematron rules #1374
Hi,
I try to understrand how to link the tailored code list "procedure-type-16" with fields specification provided by fields.json.
When I look to field BT-105-Procedure, I see that I have to display "procurement-procedure-type" code list in our forms.
"codeList" : {
"value" : {
"id" : "procurement-procedure-type",
"type" : "flat"
},
"severity" : "ERROR"
},
So we load values from codeList procurement-procedure-type.gc
Trying to validate using schematron, an error is triggered by rule BR-BT-00105-0135 in validation-stage-3b-16 when selection is in ( 'comp-tend', 'exp-int-rail', 'neg-wo-call' )
It's ok regarding how the rule is triggered :
<assert id="BR-BT-00105-0135" role="ERROR" test="normalize-space(.) = ('comp-dial', 'innovation', 'neg-w-call', 'open', 'oth-mult', 'oth-single', 'restricted')">rule|text|BR-BT-00105-0135</assert>
My question is : How do we know that for a specific notice Type we have to load a tailored codeList ?
My understanding is that we should load "procedure-type-16" tailored code list (procurement-procedure-type_procedure-type-16.gc file) instead of "procurement-procedure-type" code list (procurement-procedure-type.gc file) for a noticeType 16.
But I don't find a logical link between those code lists in SDK files.
It seems that something has been added to link legal-basis code list with relative tailored code list (legal-basis-1, etc...) regarding notice type value but we don't have such kind of link for others tailored code list....
Did I miss something ?
All reactions
Hi,
You've properly understood the relation between the tailored list and the accepted values.
Information is also summarized in the documentation: https://docs.ted.europa.eu/eforms/latest/schema/all-in-one.html#procedureTypeSection
This is currently reflected in the rules a same way it is done with the legal basis codelist.
EN2 is currently not able to deal with the tailored lists and no way has currently been defined for defining this in field.json
KR
Replies: 1 comment 2 replies
Hi,
You've properly understood the relation between the tailored list and the accepted values.
Information is also summarized in the documentation: https://docs.ted.europa.eu/eforms/latest/schema/all-in-one.html#procedureTypeSection
This is currently reflected in the rules a same way it is done with the legal basis codelist.
EN2 is currently not able to deal with the tailored lists and no way has currently been defined for defining this in field.json
KR
All reactions
Ok, it was "easy" to match a "tailored list" for procedureTypeSection. But how do we know which tailored list to use for the country fields ?
There's tailored list for country in SDK, it means we should use them in some case or for specific country code, no ?
Where can I find which tailored list to which country code field ?
All reactions
Hi,
The country codelist has multiple tailored lists, defined and used for a specific purpose
They aren't actually associated to a given field but used for further checks (need for NUTS level 3 codes, need for postcode, lawfulness in regard to submitting notices).
KR