Contradiction between notice-types.json and codelists #1185
Replies: 2 comments
-
The specific codelists contain the allowed values of BT-01 Procedure Legal Basis for each notice subtype. The notice-types.json only includes the preset value of BT-01. This is the value that is preselected when a user is creating a notice using eNotices2. But the user can change this selection. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thank you very much for the answer! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
We have notives the following:
notice-types.json defines only 1, specific legal basis for each notices. E.g.:
{ "documentType" : "CN", "legalBasis" : "32014L0024", "formType" : "competition", "type" : "cn-standard", "description" : "Contract notice – general directive, standard regime", "subTypeId" : "16", "_label" : "notice|name|16", "viewTemplateIds" : [ "16", "summary" ] }
On the contrary, field BT-01 Procedure Legal Basis uses a specific codelist for each notices which contain more than 1 codes. (Schematron rules also validate based on the codelists.)
Could you please answer which one is applicable? What is the reason for the difference?
Beta Was this translation helpful? Give feedback.
All reactions