...
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. | ||||||||
|
| Newly added ticket (Kate) | ||||||||
|
| 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. | ||||||||
|
| 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… | ||||||||
|
| EAD export (Jacqueline) | ||||||||
|
| MARC export | ||||||||
|
| MARC export | ||||||||
|
| EAD 3, 2002
| ||||||||
|
| Dublin core export (Frank ) | ||||||||
|
| MARC Import
| ||||||||
|
| MARC Import
| ||||||||
|
| LCNAF Plug-in import (Jacqueline) | ||||||||
2-3 minutes | Action Items |