...
- Regine Heberlein Will brainstorm how to transform or add to the EAD import spreadsheet to better reflect handling at different levels. For example, to document how a unittitle is handed in the top-matter versus as a component. Some ideas floated: adding every single element, attribute, and level; XPath. Spreadsheet | Code
- Elizabeth Roke Will list the DACS elements missing from the MARC importer and provide to the group. Elizabeth, please also confirm which version (most recent?) of DACS you’re using.
- Elizabeth Roke Will add two columns to the EAD2002 importer spreadsheet to match the new columns on the MARC importer
- Elizabeth Roke Please see outstanding action items from https://archivesspace.atlassian.net/wiki/spaces/AC/pages/2901704756/2021-09-16+Metadata+meeting+notes#Action-Items
- James Griffin (Unlicensed) Will begin a code review of the EAD2002 importer: Spreadsheet | Code
- Jared Campbell Will begin a code review of the EAD2002 importer: Spreadsheet | Code
- Kevin Schlottmann Will comment on https://archivesspace.atlassian.net/browse/ANW-1382
- Kevin Schlottmann Will comment on https://archivesspace.atlassian.net/browse/ANW-1416
- Kevin Schlottmann Will draft a ticket requesting that the AS importer code spit out any element that is not handled (though I did not note whether you meant for MARC, EAD, or both)
- Valerie Addonizio Add minutes and action items and find unfinished business; revisit workplan; draft new agenda; check for new tickets
Minutes
Elizabeth review of the MARC importer versus DACS revealed that AS does not support every DACS element in the DACS crosswalk, and we will be following up
We discussed and agreed that we are using DACS to judge support of the MARC importer because:
ArchivesSpace is not a bibliographic software
We are aligning with the dominant standard in our field
We will make recommendations that support for MARC fields be depreciated, but not until a certain year so that the community has plenty notice that this is going away
For EAD2002, we are still feeling our way in how much to document, but agreed in general that we should first focus on what is already present in the code. We will begin by getting organized and oriented.
We are splitting attention and members between old business and new business but will discuss everything as a group