Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

 @2pm

Attendees

Goals

  • Review EAD3 export mapping work; discuss subteam priorities and potential projects with Laney and Christine

...

TimeItemWhoNotes

Roll call


5 minWelcome Laney/ChristineNoah HuffmanBrief overview of subteam charge / ongoing work
20 minReview EAD3 export mapNoah 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?)
    • Feedback: Should spec both ways (using sort_name and separating into parts); ASpace is not obligated (yet) to import what it exports
  • How to accommodate date_expression when using <daterange> in EAD3? EAD3 requires two date expressions for begin and end date
    • Feedback: Might require simple data model change. How to accommodate without data model change?
  • 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).)

JIRA: Implement EAD3 (AR-923)


20 minDiscuss 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:

Discussion notes:

Christine on short term working groups:

  • Forming Digital Objects group in March; currently 5 volunteers; goal is to examine DO export maps and revise, gather feedback, and submit for development
  • Next group will focus on MARCXML export (Brian H. and Noah interested in joining this group)
  • Migration sub-team members encouraged to participate in working groups

Other potential projects for migration subteam

  • Review of existing import/export maps (participate in short-term working groups)
    • Digital Objects (March 2017)

    • EAD

    • MARCXML importer(Summer 2017?)

  • XML schema for importing accession records (is this still a need?)

  • 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?

5 minWrap up

Noah will gather more feedback on EAD3 export mapping: have discussion with Terry C. and others about areas where current AS data model is incompatible with EAD3; make modifications to export mapping; notify Jason L. and Laney when the export map is ready for prioritization for development.

Sub-team members will monitor the work of short-term import/export map working groups and participate as appropriate. Noah and Brian H. volunteered for MARCXML group; Michael V. volunteered for EAD group if formed.

Action items

  •  Noah Huffman – investigate JIRA feature request for XML schema for importing accession records (is this still a need?)
  •  Noah Huffman, Former user (Deleted), Cory Nimer – Review / refine EAD3 export mapping; include spec for exporting name parts as well as single string (sort_name); have targeted discussion of areas where current data model is not compatible (esp. date ranges)
  •  Noah Huffman – notify Laney and/or Jason Loeffler when EAD3 spec is complete and ready for prioritization for development