2020-02-13 Meeting Notes

Date and Time

Thursday 02/13/20, 3pm Eastern

Zoom URL

https://lyrasis.zoom.us/j/897871318

Participants

• Kevin Schlottmann

• James Griffin (Unlicensed) (Note taker)

• Daniel Michelson

• Bria Lynn Parker (Unlicensed) - regrets

• Dallas Pillen

• Jared Campbell

• Christine Di Bella

Goals

• Work Plan

Discussion topics

Notes

(Ice Breaker Responses)

Update from Laney

• Laney is going to be leaving the ArchivesSpace community for another opportunity, and hence, they were not available to attend this meeting.

• When their (former) role is filled, the Sub-Team shall look to try and invite the new person to discuss this topic

Dev/Pri Updates

• (Updates from Daniel)

• Did Dev/Pri need to be included in discussions for tickets designated as bugfixes from the Metadata Standards Sub-Team?

• This was determined not to be necessary

• Christine, Kevin, or James will request permission to update the individual tickets in order to label these as bug fixes

• Awaiting prioritization to ready for implementation is the normal workflow

• We have the authority to circumvent this and just register these as bugfixes and see these advanced

• James will be responsible for advancing tickets as JIRA bugfixes

Metadata Tickets

Proposed answer for ANW-969:

The metadata standards subgroup examined this ticket. The developers correctly implemented the new language specification as written. However, we consulted with Cory Nimer, the primary author of the new language spec, and he suggested that in this particular case (EAD2002 Language of Description export), the spec is incorrect.  Req-4 for Language of Description should have been written similarly to Req-5 for Language of Materials, where the EAD2002 export behavior of language of description mimics that of language of materials, basically: if a free-text note exists export that, otherwise export the translation of the encoded language as a text strings with the codes in attributes, with some boilerplate.The subgroup proposes the following guideline:

The system shall export Language of Description, Script of Description, and Language of Description Note field content in EAD2002 records, when available.

If a Language of Description Note is available, export only that:
<langusage>[Language of Description Note, if any]</langusage>

If no Language of Description Note is available, export the Language field translation values for the Language and Script subrecord, separated by commas, enclosed in a <language> element with associated @langcode and @scriptcode attribute values, and terminated by a period.

<langusage>Description is written in:
<language langcode="[Language of Description (code value)]">[Language of Description (translation value)]</language> <script scriptcode="[(Script of Description (code value))]">
​[Script of Description (translation value)].</script>
​</langusage>

<langusage>Description is written in:
<language langcode="eng">English</language> <script scriptcode="Latn">
(Latin)</script>.
​</langusage>

(James):

ANW-805

• Looked at the ticket, and in terms of inheritance, all found Nancy’s comment was correct

  • If the “publish” attribute is false, the @audience should be “internal”

ANW-969

• We do was <langusage> tags in support of the EAD2002 specification

• It was not likely the intention to exclude the tag in this case (hence, this is a bug)

• What was the previous behavior? It likely used to generate the <langusage> tag (or a free-text note, within ArchivesSpace) prior to the 2.7 release

  • The language was always free-text in previous releases

• We will look to post a comment clarifying this on the issue

Priority Fields

EAD Tag usage study:
http://slis.simmons.edu/blogs/kmwisser/files/2015/06/americanArchivist2013.pdf

MARC Tag Usage:

https://www.oclc.org/content/dam/research/publications/library/2010/2010-06.pdf

Based on these two references and common, I think we can come up with a reasonable set of commonly-used MARC and EAD2002 tags for which we can verify import and export in this TAC term.

MARC

001, 008, 040, 1XX, 245, 300, 351, 500, 506, 520, 524, 545, 555, 541, 546, 583, 561, 6XX, 7XX

From:

Table 2.1: MARC tags occurring in 20% or more of WorldCat records; Table 2.7: Mixed materials: Tags used more heavily than in WorldCat as a whole; some common sense

EAD2002

eadheader and all children; all tags above 10% in tables 10, 11, and 12 (archdesc/did); all tags above 50% in tables 17 and 19 (archdesc/dsc).

(James):

• Kevin and Greg worked to identify priority fields for evaluation in the work to improve the documentation being maintained by the ArchivesSpace community

• Two subsets of MARC and EAD tags

  • Using these for reference, we should ensure that these tags are included in some example records (used for testing ArchivesSpace imports)

  • Does this look like a reasonable set of tags for the Sub-Team to focus on for the next three months?

    • (No objection from attendees)

• We should all try and take one of these cases and try to follow the process outlined in Import/export mapping review process

• Question of EAD

  • EAD data model is much more aligned with the ArchivesSpace data model

  • In MARC, there is quite a bit of information which is not core to the ArchivesSpace data model

    • This should be more trivial, particularly if we select core tags

Somebody from EGAD giving a presentation on RiC (Daniel)

• Sub-Team could organize a standalone presentation and invite members from the committee

• Daniel Pitti is working with a colleague to find someone to present this to the Sub-Team

• We need to discuss this with Jessica Crouch and organize this as a community