Closed jpmckinney closed 1 week ago
Business terms removed:
selection-criterion
codelist)usage
codelist)New Business terms added
fsr
codelist)foreign-subsidy-measure-conclusion
codelist)exclusion-grounds-source
codelist)selection-criterion
codelist)selection-criteria-source
codelist)Codelist values now listed rather than just naming the codelist:
type 'id' now type 'id-ref' with list of 'idSchemes'
No longer mandatory
Conditional mandatory
Now mandatory
Codelist name change
Change in xpathAbsolute
New 'businessEntityID' added to all business terms
New 'referencedBusinessEntityIds' field
I'll review the changes for relevance and add the new guidance etc later this week
I updated the instructions with a step to update drop
(to ignore any irrelevant new properties like businessEntityId and referencedBusinessEntityIds), and I re-did the commit, to make the diff smaller. Please git pull
. If you get merge conflicts, you can either (1) abandon the pull, git reset
to a known good commit, then pull or (2) delete your local repository and start over (this assumes you have no local branches).
I also did this step:
Fields removed from
source/fields.json
remain inoutput/mapping/eforms/guidance.yaml
with only eForms guidance, eForms example, OCDS example and sdk fields. Remove such fields manually.
The diff is a manageable size now: https://github.com/open-contracting/european-union-support/commit/045a51bfad8c508f706ed11e848d28fbc3dad69a
edit - moved this comment to new issue https://github.com/open-contracting/european-union-support/issues/219
Codelist name changes - no updates needed
Business terms removed - BT-747 and BT-749 are both referenced in mappings that affect the same SelectionCriteria
objects. These references will need to be removed and likely replaced with references to BT-806, BT-809, BT-821 (still to create mappings for these new fields)
type 'id' now type 'id-ref' with list of 'idSchemes' - no changes needed, just placing constraints on the id code pattern for the publisher when they're creating their eForm but OCDS doesn't enforce similar constraints on the id
fields being mapped to
mandatory changes - no changes needed to OCDS mapping
xpath changes
I'll apply the listed changes as part of a PR to update the mappings once they've been agreed
moved this comment to new issue https://github.com/open-contracting/european-union-support/issues/220
sorry I didn't think they were all going to be so big and I should have started new issues for them. I've done so for the final new field https://github.com/open-contracting/european-union-support/issues/218 and moved the others into their own issues
https://github.com/OP-TED/eForms-SDK/releases/tag/1.12.0
1.11 was #204
I haven't had a chance to review, but my typical process is to start a branch, run the "Upgrade SDK version" steps, and document changes here, like in #204 and earlier.