2021-10-20 Metadata meeting notes
ย
Microsoft Teams meeting
Click here to join the meeting
Participants
@Elizabeth Roke
@Valerie Addonizio
@Kevin Schlottmann
@Jared Campbell
@James Griffin (Unlicensed)
@Regine Heberlein
Minutes
@Valerie Addonizio
Quick links
Google drive space: https://drive.google.com/drive/u/1/folders/1RQftm8w4XkNISQHVbtjr6sNY4_iyyXMV
Test records: ArchivesSpace Metadata Standards Sub-Team
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: archivesspace/backend/app/converters/ead_converter.rb at master ยท archivesspace/archivesspace
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: 2021-09-16 Metadata meeting notes | Action Items The ticket writer is correct, this is technically true: https://www.loc.gov/marc/authority/ad024.html In AS 3.0, record identifier is a required field (correctly), but only 024$a maps there (AS code). If we were to recommend a change, the logic would be: If no 024$a, then use 024$0 as identifier; if no 024$0 either, then use 024$1. If 024 exists but none of ${a,1,2} are present, reject the import However, this is an edgy edge case; Iโd suggest we state the above but not this is not a development priority. However, it is probably an easy fix for someone looking to dip a toe into pushing code. (kws) |
10 min | New/Ongoing ticket review | Check for new tickets. If there are no new tickets, we will move on. ANW-943: Ability to export an Accession record as MARC recordAwaiting More Information ANW-1416: Translation to MARCXML country codeClosed-Complete Thanks to Kevin for taking a look at 1416: The MARC spec for the 008ย position 15-17 points to this MARCย country code list.ย However, when serializing to MARC, AS finds this data by looking up the country listing for the repository, and then findingย the iso 3166 country code from a local controlled value list (country_iso_3166).ย ย ISO3166 is not remotely equivalentย to the MARC list.ย ย So the ticket writer is correctย that the wrong value for the Netherlands is getting into their MARC export.ย (This is avoided in the US because of a special exception that places the xxu country in all US-American records.) One could tell the ticket writer to edit (i.e. break) the local iso 3166 controlled valueย list to map to the correct MARC Country code for the Netherlands.ย This however would make the EAD export invalid, since EAD points to iso 3166.ย ย One could also suggest to the ticket writer to do some local post-export processing for theis MARC records (which we do here at Columbia for similar issues).ย However, this presupposes a fair bit of technical knowledge and access to the various implicated systems. And it is brittle.ย ย The *right* answer is to add the MARC country code list to the controlled value lists that ship with AS, and have AS look to that list when serializing MARC.ย ย |
5 min | Order of events and individual momentum |
|
5 min | Next steps/homework | ย |
Action Items
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 expect to start with the NOT IMPORTED and MIXED CONTENT sections.
We are splitting attention and members between old business and new business but will discuss everything as a group