Review ISO and DCAT-US3.0 initial mapping
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 200
- Avg merge
- 4h 56m
- Merged PRs (30d)
- 5
Description
## Purpose
We want to merge compliant metadata into DCAT-US3.0, but we're not sure how to do that.
Given above unknowns, reviewing Lynda Wayne's initial [ISO->DCAT-US3.0 schema mapping](https://docs.google.com/spreadsheets/d/1lagepdNntrDXlBE4Km5P1LhAMThTS1oD/edit?gid=1387459942#gid=1387459942) is needed to provide factual knowledge on future steps.
1 day of effort has been allocated and once compete, findings will be demonstrated and specific future actions will be decided.
### Acceptance Criteria
[ACs should be clearly demo-able/verifiable whenever possible. Try specifying them using [BDD](https://en.wikipedia.org/wiki/Behavior-driven_development#Behavioral_specifications).]
- [ ] WHEN 1 day expires\
THEN spreadsheet is discussed with the geoplatform team \
AND architecture/design decisions are discussed with the team \
AND stories covering future action are created if needed
### Background
DCAT-US3.0 and ISO mapping is much more detailed. ISO was always considered way more exact and detailed than 1.1, and 3.0 is much more detailed than 1.1 as well. This may result in a "basic and iterative" approach, whereby we define core examples/fields and then define improvements as future iterations.
### Sketch
- Review spreadsheet, making notes/comments.
- Consider integration with MDTranslator vs custom process
- Consider NARA definitions and possible integration
Contributor guide
Assessment
This issue has not been assessed yet.