Page Comparison

Charlotte Whittand others

New UX proposal - using two new subsections dividing actions for Inventory and quickMARC

1. Default mapping profile - default MARC Bib mappings:
   • Instance relationship – child instance
   • Instance relationship – parent instance
2. Administrative data and SRS (possibly UXPROD-3254 or combination of UXPROD-2679, UXPROD-2225, UXPROD-977)
   • The administrative data includes (as presented in the Administrative data accordion):
     • Suppress from discovery
     • Staff suppress
     • Previously held
     • HRID
     • Source
     • Cataloged date
     • Instance status term
     • Mode of issuance
     • Anything else?
   • What format should the data be exported: cvs, json, MARC?
   • If not MARC, then do we need to use SRS instead of inventory records?
3. Custom mapping profile – populating the transformation form dynamically (UXPROD-3253)
4. UXPROD-1396 Generating MFHD on the fly
   • It will require adding option for saving Holdings UUIDs on the Inventory Holdings tab – similarly to Saving Instance UUIDs on the Inventory Instance tab
   • 
   • Do we need to preserve Saving Instance UUIDs on all tabs?
   • Current default mappings as defined in: https://docs.google.com/spreadsheets/d/1ac95azO1R41_PGkeLhc6uybAKcfpe6XLyd9-F4jqoTo/edit#gid=1117349574 includes:
     • holdings HRID: mapped to 001
     • associated instance HRID: mapped to 004
     • associated instance UUID: mapped to 014 1 $a
     • associated instance OCLC control number mapped to 035 $a
     • permanent location mapped: to 852 $b
     • holding statement and notes: mapped to866 $a $z
     • holding statement for supplements and notes: mapped to 867 $a $z
     • holding statement for indexes and notes: mapped to 868 $a $z
     • holdings UUID: mapped to 999 ff $i
   • Should the default mappings for MFHD be revisited?
   • Do we need a default mapping profile for holdings ( like we have the default mapping profile for instances)?
5. UXPROD-142 Exporting MFHD from SRS

• • This will be possible once the SRS work is complete

NOTE:

Distinction between Custom mapping profiles and Default mapping to help group assess the spreadsheets accurately. The two processes are very distinct from each other:

• mapping-preferences - spreadsheet that defines custom mapping profiles in data export. - These come into play when the user defines custom profiles in Settings/Data Export. A custom mapping. The fields seen when the user clicks on "Transform" is driven by the Custom mapping spreadsheet.
  
  
• recommended mapping - spreadsheet covers the properties that are part of the default mapping profile. Common use case for default mapping profile: Select records in Inventory > Actions - export Instances (MARC). The MARC record appears in the Data Export app directly from that action. The resulting default record has a 999 field with UUIDs from Source Storage, another from Inventory Storage