2021-01-11 Metadata meeting notes

5 min

Welcome

25 min

Jira ticket

https://archivesspace.atlassian.net/secure/RapidBoard.jspa?rapidView=15&modal=detail&selectedIssue=ANW-320

• Kevin: not likely that a lot of repositories will be using this in the same functional way that it would be used in the MARC environment. Most likely to be a question of how information is displayed. We can/should minimize the of complexity of the solution. We could suggest prepending a Parent Institution Name before Repository Name if a Parent Institution Name exists. This would resolve the <agencyname> issue.

• Elizabeth: <agencycode> – if a prefix is not there, it might not validate. <agencycode> requires a country prefix.

• Kevin: The exporter adds a country prefix based on configured country in your ArchivesSpace instance.

25 min

Mapping homework

See Minutes from December: https://archivesspace.atlassian.net/wiki/spaces/AC/pages/1938817025

• Progress?

• Issues?

  • Elizabeth: Found the process fairly intuitive. A few places where the code was a bit confusing and could only make guesses about what the code is doing.

  • Kevin: There are errors in the code where it looks like it’s following some conditional logic, but there might be some error in, for example, a regular expression.

  • Valerie: Reading the code only tells you what it does, not what it doesn’t do.

  • Elizabeth: We can address issue of code matching spreadsheet. More difficult to address issue of, is code doing what it should be doing.

  • Kevin: The code/spreadsheet documents a lot of fields that will probably never be used. If we focus on the 20-25 most commonly used notes for more complex efforts. For example, getting the 300 field as correct as possible.

  • Elizabeth: Should we commit to maintaining the documentation and testing for those most commonly used fields?

  • Valerie: The code also does a lot of cleanup on punctuation, too. Is there a need to document that?

  • General discussion about MARC records, punctuation, etc. and whether or not that sort of logic should or even could maintain the correct punctuation-based functionality going forward.

  • Discussion about sustainability of this particular sub-team reviewing the code going forward. Suggestions to better comment the code and contribute to unit tests to make it more maintainable going forward.

  • How do we get notified that something in the code has changed?

    • Christine: Pull requests are reviewed by an ArchivesSpace developer and given tags. Trying to put a metadata tag on code changes related to metadata.

    • That should be sufficient for this group.

• Proposals:

  • Can we go through the MARC → ASpace and ASpace → MARC spreadsheets and nominate fields for inclusion in the subset of fields that we will commit to maintaining going forward.

    • We will start with MARC → ArchivesSpace spreadsheet. Next time we meet we will go through that column to confirm that everyone gives the thumbs up. Following up on that, we will move the information to the ASpace → sheet.

  • We will continue to go through the field mappings before next meeting

5 min

Next steps

• Elizabeth will add column to nominate fields