Date and Time
Thursday 01/09/20, 3pm Eastern
Zoom URL
https://lyrasis.zoom.us/j/897871318
Participants
James Griffin (Unlicensed) (Note taker)
Goals
Discussion topics
Time | Item | Presenter | Notes |
---|---|---|---|
5 min | Ice Breaker Question: Favorite kind of weather / season | ||
15 min | Standing item: review metadata tickets | Specific tickets =flagged for us by Christine Di Bella https://archivesspace.atlassian.net/browse/ANW-974 https://archivesspace.atlassian.net/browse/ANW-969 See below for Kevin’s discussion prompts / draft replies | |
10 min | Ideas from TAC discussion | *There is a desire to see us engage with RiC. Suggestions included a blog post about RiC for the AS community; and inviting EGAD to present to TAC. *We should make explicit what AS versions the import/export mappings are keyed too. Speed of AS updates vs review might be an issue. Thoughts? | |
5 min | Deliverables from previous meeting | James will provide updates on the GitHub repositories Kevin will show the draft instructions for import/export review: Import/export mapping review process Kevin created ticket for 245f/g issue: https://archivesspace.atlassian.net/browse/ANW-1002 Christine created a dedicated test server for Metadata Standards team, available at http://metadata.lyrtech.org/staff/. (admin/admin) For testing against the current version using/creating data that is reliably and predictably there. | |
10 min | DACS tooltips review - updates on scope and process | Update on the spreadsheet | |
10 min | MARCXML /EAD import review | Updates on the Google Sheet: https://docs.google.com/spreadsheets/d/1jU6MYF7UI7a-UKdd5XhYCV6W1UyrMMCzYDFlgb8iNW8/edit#gid=1527709562 | |
5 min | Anything else? |
Action items
Notes
Introductions
Metadata Tickets
Proposed reply for https://archivesspace.atlassian.net/browse/ANW-974
“As Rachel notes correctly, the 044 is incorrect, since country of publication is determined at the repository level and in AS there can only be one. Per MARC rules therefore the country code should (and is, by AS) encoded only in the 008, p15-17. Light testing indicates that the country codes are being exported correctly, including the US code ‘xxu’ as discussed in ANW-673.
The metadata subgroup of TAC agrees with the reporter and recommends that the 044 field be removed from the MARC exporter.”
Other comments:
The 008 AS->Marc needs to be updated (I made a note in our Google sheet)
In the sandbox (2.7.0), I created a test repo with the country as Germany. The MARC export code to the 008 and 044 is de. The code is correct. The placement in the 008 is correct.
MARC 008 definition: https://www.loc.gov/marc/bibliographic/bd008.html
MARC 044 definition: https://www.loc.gov/marc/bibliographic/bd044.html
MARC country code list: http://www.itsmarc.com/crs/mergedProjects/councod/councod/contents.htm
Looking at the spec, current AS->EAD2002 behavior matches the implementation request (encoded language of description is NOT exported to EAD2002; only the free-text language of description is exported). I also note that langusage is optional in EAD2002, and not required by DACS(!).
All agreed to this proposed solution, this will be posted to the JIRA Issue on 01/10/19
Question: What is the process for these types of Issues for Dev. Pri.?
For something like this when the Issue is submitted, and then it is delivered to this Sub-Team, there is enough information now to know that this MARC field should be suppressed
Dev. Pri. shouldn’t need any additional information, and this would be routed as “ready for implementation”
Prioritization should be minor for this issue, we want to ensure that the Co-Chair for Dev. Pri. is okay with this
Maybe it does make sense for this to be placed into the queue for Dev. Pri. - the ticket itself does not need priority if that is the case
Proposed Reply for https://archivesspace.atlassian.net/browse/ANW-969
We should discuss, but if this were open for a do-over, I would propose that the EAD2002 export behavior of language of description mimic that of language of materials (in short, 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 prepended. E.g.:
<langusage> Finding aid written in: <language langcode="[Language (code value)]" scriptcode="[Script (code value)]">[Language (translation value)]</language></language>
However, the spec appears to have been drafted pretty carefully, so perhaps we should reach out to Corey Nimer and see if this was intentional.
Spec (see PDF linked in ticket): https://archivesspace.atlassian.net/browse/ANW-697
EAD: https://www.loc.gov/ead/tglib/elements/langusage.html
DACS: https://www2.archivists.org/standards/DACS/part_I/chapter_4/5_languages_and_scripts_of_the_material
Ideas from TAC