2017-02-27 Meeting notes

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).

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

• What documentation exists for using refactored tool; is it accurate?

• Archivists Toolkit migrator

• Documenting advanced features? Does this exist somewhere?

• How-to guides for customizing importers / exporters with plugins