Microsoft Teams meeting
Click here to join the meeting
Participants
Minutes
Quick links
Google drive space: https://drive.google.com/drive/u/1/folders/1RQftm8w4XkNISQHVbtjr6sNY4_iyyXMV
Test records: https://github.com/ASpace-Metadata-Standards
Published import/export AS standard: https://archivesspace.org/using-archivesspace/migration-tools-and-data-mapping
EAD 2002 importer. Spreadsheet: https://docs.google.com/spreadsheets/d/1jU6MYF7UI7a-UKdd5XhYCV6W1UyrMMCzYDFlgb8iNW8/edit#gid=1669916495 Code: https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/ead_converter.rb
There is no EAD3 importer at this time.
Previous Agendas
2021-08-19 Metadata meeting notes
2021-09-16 Metadata meeting notes
Discussion Topics
Time | Item | Notes |
---|---|---|
5 min | New member! | 🥳 🥳 Please welcome our new colleague Regine Heberlein, Library IT Data Analyst at Princeton! 🥳 🥳 (it’s Regine recently worked on an EAD2002 migration and has recent notes and experience with the importer; she also has a huge supply of test data. |
10 min | Review and confirm work plan | Remaining issues from 2021-06-08 minutes have been added to this term's workplan. This makes the workplan more detailed than usual, but brings this info together into one place. Regarding a more pro-active role in the development cycle, please list ideas for that. I know there are some ongoing, but I don’t have them written down. |
25 min | Update on progress | Action items from last agenda: https://archivesspace.atlassian.net/wiki/spaces/AC/pages/2901704756/2021-09-16+Metadata+meeting+notes#Action-Items |
10 min | New/Ongoing ticket review | Check for new tickets. If there are no new tickets, we will move on. https://archivesspace.atlassian.net/browse/ANW-943?filter=13658 https://archivesspace.atlassian.net/browse/ANW-1416 Thanks to Kevin for taking a look at 1416: |
5 min | Order of events and individual momentum |
|
5 min | Next steps/homework |
Action Items
- 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