2022-03-31 Metadata meeting notes
Microsoft Teams meeting
Click here to join the meeting
Participants
@Elizabeth Roke - Absent
@Valerie Addonizio
@Kevin Schlottmann
@Jared Campbell - Emergency regrets!
@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: Migration Tools and Data Mapping - ArchivesSpace
The MARC importer: Spreadsheet | Code
EAD 2002 importer: Spreadsheet | Code
Current Work Plan
2021-2022 Metadata Sub-team Work Plan
Previous Agendas
2021-08-19 Metadata meeting notes
2021-09-16 Metadata meeting notes
2021-10-20 Metadata meeting notes
2021-11-11 Metadata meeting notes
2021-12-09 Metadata meeting notes
2022-01-27 and 2022-02-03 Metadata meeting notes
2022-03-09 Metadata meeting notes
Discussion Topics
Time | Item | Notes |
---|---|---|
5 mins | Intro | Five minutes on the timer to read the agenda |
| AS Online Forum Recap and Feedback | The chat log from the forum is below; recording is here. I gave it a read and re-watched the video can report the following: On compliance versus interchangeability
On Elizabeth’s MARC topic
Minutes from Discussion:
On Kevin’s MARC topic
Minutes from Discussion:
|
| MARC importer documentation and progress | Next steps?
|
| Tiers of Support | Next steps?
|
| Guest! Kate Bowers will be joining us at 12:30 | Kevin suggested we add Kate Bowers to this meeting to discuss the following:
|
| EAD Mapping reorganization | Opening the floor to @Regine Heberlein to show us her continuing work and invite comments.
|
| Draft a ticket for this? (bumped from online forum discussion) | @Kevin Schlottmann Issue 2: Mapping of 852 call number import (MARC 21 Format for Bibliographic Data: 852: Location (Network Development and MARC Standards Office, Library of Congress) ) Note that repository information is not considered, as it is, appropriately, set at the AS Repository Level (organization, address). |
| New/Ongoing ticket review | Revisiting: https://archivesspace.atlassian.net/browse/ANW-943 and: In a prior meeting we reviewed https://archivesspace.atlassian.net/browse/ANW-547 and we had the following comments. Another review of this ticket is a low priority (at this time) given the items above. This was particularly difficult. There is a lot in here, would be better broken up into multiple user stories. Reading this as the ability to emulate the repeatable unitid with a type attribute in EAD. Better argument at the archival object level because there are some ways to work around this in Resources with the use of plugins. Different use case of managing agents because there are different authority records, but ArchivesSpace should be the database of record. Hesitance about prioritizing giving intellectual records multiple identifiers. No solid conclusion today, will continue to revisit. |
| Kevin’s drafted ticket | Kevin sent us a draft of a ticket requesting that the AS importer code confirm the elements that were handled by an ingest process, allowing users an assessment of what was not handled. Here is his draft, below:
As a user, I would like all importers to generate a report of every element from a source record that is handled. I would like this functionality for all imported record types (MARC, EAD, EAC-CPF, csv). For example, if I'm importing a MARCXML record with a 245 field, subfield a, I would like an indication that the field was handled by the importer. If possible, noting *where* it was imported would be desirable as well. For example, 245$a -> Title. This idea came up in the Metadata Standards subgroup as we were reflecting on all the data that the importers silently skip. Metadata Standards plans to propose that the importers handle fewer elements (so it is easier to document and maintain), meaning the importance of this functionality will increase. We would also like whatever report is generated to encourage the user to check the report against the source record, to identify any skipped fields. If this is something that could be addressed, Metadata Standards would be happy to provide more specific examples and input. |
| Review Work Plan Items | |
5 min | Next steps/homework |
|
Action Items
@Kevin Schlottmann Three MARC tickets in this agenda, and happily a path forward on the MARC 300 field
@Valerie Addonizio Follow up with Kate
@Valerie Addonizio Think about descriptive versus interoperability in the Tiers.
Long term Action Items (by or at end of term)