jpmckinney
commented
5 months ago from @duncandewhurst
https://github.com/OpenDataServices/oc4ids-mapping-template
(Old approach: https://colab.research.google.com/drive/1gkFQMyZjzUC-q8HVOX7P_OvzE8q8TskM)
Notable changes:
- A new, pure Python, command-line tool for generating the template, replacing the old Python/Google Apps Script approach, which involved many manual steps.
- Updated user and developer documentation. This is all in the GitHub repo, but we could consider moving the user documentation to either the OC4IDS documentation site or the resources section of the OCP website, and the developer documentation to the handbook, if appropriate.
- Aligned language with OCP's use of 'data source' and 'data element' in mapping documentation.
- Improved documentation within the template, including a note on each column header containing a description of the column's semantics.
- Re-implemented 'mapped to' column in the (Source) Data elements sheet, which was previously disabled, with more performant and cross-compatible formulae
- An optional 'CoST IDS Elements' sheet to allow users to select which (core and sustainability) CoST IDS Elements they want to map. The mapping sheets then show the selected elements alongside each OC4IDS field to which they are related.
- Fully compatible with Google Sheets and Excel desktop and online versions.
- Various other formatting and usability improvements.
I've done this in a way that could be reused for the OCDS and OCDS for PPPs mapping templates with fairly minimal adaptation. Doing so would address most of the open issues on https://github.com/open-contracting/field-level-mapping-template/issues.
yolile
Originally reported in #5537 by @duncandewhurst: