2021-04-13 Metadata meeting notes

5 min

Welcome

20 min

Discuss new mapping documents

https://github.com/archivesspace/archivesspace/tree/master/backend/app/converters/lib

• Impact of these shifting?

• Looks like the base maps split to support importing just authority imports/exports for agents, but functionality should be the same. This should be a rare occurrence.

• This group needs to be able to rely on a single place to look for mapping information.

• A Google alert on the on the library for the mapping docs? Or an email from Christine any time the import/export map tag is used? Christine will plan to email this group and look for a way to set up an alert.

• Are there ways to update via the code rather than manually? This seems like a second manual process.

  • We are still wondering about whether unit tests are possible that would flag when mappings change. Maintenance has always been an issue. Developers do have automated tasks set up for pull requests. It may be possible to send out alerts when certain files are touched in a pull request.

  • Testing the importers/i.e. things happen that don’t match the map is out of scope for this group. But this group can make the judgement calls about how the importer should make decisions. Testing the importers might be a good project for the testing group.

25 min

Mapping doc review

Marc to AS seems done: https://docs.google.com/spreadsheets/d/1jU6MYF7UI7a-UKdd5XhYCV6W1UyrMMCzYDFlgb8iNW8/edit#gid=1527709562

• How to handle problems/questions (in yellow highlight)?

  • These need to be filed individually. Extent needs to be hashed out in this group to make a call as to what needs to be the default.

  • Christine will go back and let us know where we have identified problems where there have been code changes. Elizabeth will then take that info and let people know where tickets need to be submitted.

  • We also need to discuss which fields are being ignored by the importer at our next meeting.

• Do we need to revisit lines dealing with authorities? (per Feb. meeting minutes: https://archivesspace.atlassian.net/wiki/spaces/AC/pages/2155446331 ) Elizabeth can submit this ticket.

• Can we go ahead and publish this? Format? In tech docs?

  • Excel allows implementers to merge cells and that has been helpful. Color coding is helpful.

  • View only Google docs?

  • Might be difficult for markdown to be able to read this doc.

  • Interest in leaving the notes as to when the column was last reviewed.

  • Decision to publish the MARC to AS mapping doc in Google Sheets or Excel.

• Group decided to focus on importers this year and let the next year’s committee handle exporting, which seems to be more complicated to understand in the code.

10 min

Next steps

• Christine will email Elizabeth about the highlighted sections in the mapping doc where there have been code changes. Elizabeth will determine which highlighted sections need tickets and send to group. Group members will submit individual tickets for sections they reviewed by next meeting.

• For next meeting:

  • Discuss import issues that need some kind of default decision (such as extent)

  • Discuss MARC fields ignored by the MARC importer

• Homework: Begin same review process for the EAD importer. Spreadsheet: Code: https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/ead_converter.rb