January 7 at 3pm est
https://rutgers.zoom.us/my/dbiunno?pwd=c3RiOEgzSlNGekgzVmNHNHBtaEhYZz09
Participants:
Goals:
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
ASpace test site: https://test.archivesspace.org/
Agenda
5 - 10 minutes | Welcome everyone! Happy New Year! Any updates from the group ? |
|
30 - 40 min | Jira Tickets | Jira Tickets: Below is the list of outstanding Jira tickets. |
| ANW-2113 - Getting issue details... STATUS | Newly added ticket (Kate) Ready for testing! |
| ANW-1055 - Getting issue details... STATUS | PUI, EAD and MARC export (Diane) Within the <profiledesc> portion of the <eadheader> an optional subelement <langsage> can be used to provide information about the languages, sublanguages, and dialects represented in the finding aid. The language(s) in which the finding aid is written can be further specified using the <language> subelement within <langusage>. For bilingual or multilingual finding aids, either identify each language in a separate <language> element, or mention only the predominant language. The LANGCODE attribute can be used to provide the three-letter ISO 639-2b code for the language. The SCRIPTCODE attribute may be used to specify the ISO 15924 code for the script in which the language is written. |
| ANW-1384 - Getting issue details... STATUS | PUI, EAD and MARC export (Kevin) This appears to be resolved? Agent terms with qualifiers appear in the PUI in my test environment (v3.5.1), and the qualifiers appear in exports – as part of the <*name> EAD element, and in subfield G (miscellaneous information) in the MARC 1xx/6xx fields. They don’t appear in PDF exports but it doesn’t look like any controlaccess terms appear in PDF exports… |
| ANW-547 - Getting issue details... STATUS | EAD export Jacqueline (below is the response to the forum) Jacqueline, I am not particularly interested in this requested feature so I will not add to ANW-656. I am responding to your request to understand how the OAI-PMH is used. I am finalizing plans to use certain records of it in my school's ILS. Specifically, I intend to import all DC records matching our criteria for serendipitous discovery in PrimoVE. Here is the test that I will present to my committee tomorrow.
https://cvlc-uni.primo.exlibrisgroup.com/permalink/01NRTHIOW_NRTHIOW/1vb6lb8/alma991010305553202841
-Matt Hi Jacqueline,
I can see why someone might want to repeat an identifier (ANW-547), but I am slightly concerned about the technical implications. If you had multiple identifiers, would you need to designate one as "primary," like we can now do with Agents? If this was not possible (or possible and not done), would it just privilege the first one listed? This would impact the file names of exports and, more significantly, sorting for both staff and public users, so needs to be considered.
We do include OCLC numbers in our finding aids (when available), which could be considered secondary identifiers. However, putting them into a General Note has worked well for us, since it gives us the added benefit of including a permalink to our catalog. While we do occasionally search for OCLC numbers, we do not ever need to sort on them, so this may not be an analogous situation. I try not to solve problems with General Notes, but this one has worked out fine. Best, Jaime
Jaime L. Margalotti (she/her/hers) Associate Librarian / Archival Metadata Librarian Special Collections and Museums University of Delaware Library, Museums & Press 181 South College Ave. Newark, DE 19717 302-831-2229 |
| ANW-1602 - Getting issue details... STATUS | MARC export |
| ANW-943 - Getting issue details... STATUS | MARC export |
| ANW-1709 - Getting issue details... STATUS | EAD 3, 2002
|
| ANW-656 - Getting issue details... STATUS | Dublin core export (Frank posted with Jacqueline the the ASpace forum) The Dublin Core export for Archival Objects (ANW-656) might be helpful, depending on how an institution creates metadata for digital collections. In general, our digitization team maps EAD-XML to the fields in our digital repository. The repository technically uses custom fields, but they are heavily based on Dublin Core. I don't know if staring with Dublin Core would make their work easier or if it would be about the same.
Best, Jaime
|
| ANW-2072 - Getting issue details... STATUS | MARC Import
|
| ANW-1409 - Getting issue details... STATUS | MARC Import
|
| ANW-1886 - Getting issue details... STATUS | LCNAF Plug-in import (Jacqueline) |
2-3 minutes | Action Items |