Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
Call Info:
1-888-354-0094
Access code is 731627
Date
@2pm
Attendees
Goals
- Review EAD3 export mapping work; discuss subteam priorities and potential projects with Laney and Christine
Discussion items
Time | Item | Who | Notes |
---|
| Roll call |
|
|
5 min | Welcome Laney/Christine | Noah Huffman | Brief overview of subteam charge / ongoing work |
20 min | Review EAD3 spec | Noah Huffman | ASpace to EAD3 export map: https://docs.google.com/spreadsheets/d/1i6m0WB43EpdCtzYyOImL5VRk-k2m1snRVeVsQ7F9gAY/edit?usp=sharing Guiding principles for EAD3 support: https://docs.google.com/document/d/1flWS83CRDvdc2cG8pWYA7bqRTckj9yJc3ucMBgLz8qE/edit?usp=sharing Outstanding issues / questions: - Parsing agent / subject terms on export (use sort_name in single <part> element or separate terms into defined parts?)
- How to accommodate date_expression when using <daterange> in EAD3? EAD3 requires two date expressions for begin and end date
- Parallel extents. When structured and unstructured (container_summary) exist as part of an extent record, no way to group these in EAD3
- Mapping to controlled type lists in EAD3 (@physdescstructuredtype, @daotype)
- @langcode for finding aid language (not controlled in ASpace, EAD3 requires a language code).
|
20 min | Discuss sub-team priorities | Christine Di Bella Noah Huffman Laney McGlohon (Unlicensed) | Discuss potential subteam projects and ongoing priorities with Christine and Laney - Short term working groups?
Some ideas: - Review of existing import/export maps
Digital Objects EAD MARCXML importer
XML schema for importing accession records Archon migration tool Archivists Toolkit migrator How-to guides for customizing importers / exporters with plugins
|
5 min | Wrap up |
|
|
Action items