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
The MARC importer: Spreadsheet | Code
EAD 2002 importer: Spreadsheet | Code
Regine’s version of the EAD 2002 import mapping: https://docs.google.com/spreadsheets/d/1uBWibkBRy3o39sZf8cQfNDiCZ7v36Hds/edit#gid=2022215819&fvid=202912311
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
2022-03-31 Metadata meeting notes
Discussion Topics
Time | Item | Notes |
---|---|---|
2 mins | Intro | Some text lifted directly from emails, below: |
10 minutes | Ticket updates |
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 (Draft is in Agenda, linked here): · Minutes: We reviewed why we reversed this ticket; I had to leave the meeting before a final conclusion on whether to remove the detailed reporting of what fields were mapped Direct follow ups:
|
15 minutes | MARC importer documentation and progress | Elizabeth Roke Next and final steps? Minutes from Discussion:
Direct questions to address in the next meeting:
|
10 minutes | Tiers of Support | Valerie Addonizio Next and final steps? |
10 minutes | ANW-547 | - ANW-547Getting issue details... STATUS You commented on having a need, which helps us frame our response. I am in favor of supporting this functionality, so I want to get started on the practical needs for the developers. That will consist of:
I’d like you to focus exclusively on resources/components and not on Agents. The original writer of the ticket was talking about resources/components and then it was a commenter that opened the discussion to Agents. I’d like to separate out the Agents question and focus back on just the resource and component level. |
10 minutes | Updated EAD Mapping | I have asked Jared Campbell to work with some sample EAD mappings between now and the end of term. Key here is to to prepare for the work of next term. Some thoughts: What to focus on next might not be so much what to actually do in the spreadsheet as designing the next phase of work for a team with various comfort levels. |
New/Ongoing ticket review | Revisiting: | |
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:
| |
Review Work Plan Items | ||
5 min | Next steps/homework |
Action Items
Long term Action Items (by or at end of term)
- Elizabeth Roke
Contact Mark about the EAD4 questions andinvite him to a future meeting - Elizabeth Roke and Valerie Addonizio Alert Christine to the updated version of the MARC importer mapping + inquire about how they might want the new tickets delivered (and good suggestion from Kevin to include the DACS mapping element in the ticket creation). Also inquire about keeping an older version of the mapping for posterity.
- Elizabeth Roke and Valerie Addonizio Contact Christine about publishing the Draft of Tiers of Support
- and our stance on being included upstream in decisions that effect external standards
- Valerie Addonizio Put RiC review in the notes in our retrospective. Essentially we know we absolutely must render a verdict on this, but we decline to do so on a draft. We have doubts about the stated aspirations (transmission standard, descriptive standard, one ring to rule them all). We want to be included in the decision of how ASpace reacts, and not just the recipients of said decision.
- Valerie Addonizio Put our statement about being included upstream in the notes in our retrospective