wrandtkeflvc
commented
6 years ago Librarian could change transformation in https://github.com/FLVC/FLVC_Islandora_XSLTs , and then request developers to place text file into Islandora.
Decided at Nov. 15, 2018 FLVC Islandora Developers meeting to make it to where
MARC 245 fields and MODS mapping. The MODS on save will map a
<titleInfo><title>(no attribute) to MARC 245. It will not map a<titleInfo type="uniform"><title><titleInfo type="alternative"><title><titleInfo type="translated"><title><titleInfo type="abbreviated"><title>to 245, as those are all appropriately 246 fields.Meanwhile, the MODS forms allow to enter a
<titleInfo><title>with attribute and omit a<titleInfo><title>with no attribute. This can lead to a display issue in Mango. When all<titleInfo><title>elements have an attribute, then there's no 245 field. No 245 field makes the record not display in Mango.I am recommending a change to the MODS to MARCXML mapping to where it will first look for
<titleInfo><title>to store to MARC 245, then if there is no<titleInfo><title>look for<titleInfo type="uniform"><title>, then if there is nothing yet look for<titleInfo type="translated"><title>, then if there is nothing yet look for<titleInfo type="alternative"><title>, then if there is nothing yet look for<titleInfo type="abbreviated"><title>. FLVC already deviates from the LOC's MODS to MARC mapping, so the MARC coming out of Islandora won't be a perfect representation of the MODS in instances where there isn't a<titleInfo><title>with no attributes, but the MARC already isn't a perfect representation of the MODS.Could also change this in the Mango configuration such that if there's no 245 field, then take the first 246 field and use that as a 245 field. That fixes the display issue, while leaving the MARC records perfect matches to MODS.
The librarian fix for this would be to split the Title element to two separate boxes on the form (longer form) and make no attribute title it's own required box. This would add a whole page down to the form and make it much longer for a person to scroll down on. That's not good for usability. I feel very strongly that the forms should be kept concise.
Regarding the MODS forms not requiring a
<titleInfo><title>field with no attributes. I have checked the SSDN Metadata Guidelines, and this issue will affect ability to participate in the DPLA federated search project - SSDN will require a<titleInfo><title>field. This is a reason to make<titleInfo><title>mandatory in the forms, but I really don't want visually longer forms.