PO update on new app functionality for Lotus and overview of planned work for Morning Glory | @Khalilah Gambrell | Lotus Release 4/19/22 quickMARC - MARC holdings Create via inventory Mapped fields read only Addressed defects
Data Export - MARC holdings quickMARC - Authorities Search w/ ES View Edit via quickMARC Browse
Data Import - Authorities Create Update Match on any MARC field
quickMARC - improved error messaging, Backend support for Optimistic locking MARC authority app New component - advanced search Some filters, facets implemented Sort by relevance - change with column headings or actions dropdown 1xx are bold "Authorized". "Exclude see from" checkbox to only see 1xx Edit = quickMARC view Browse by various options
Inventory - Holdings Actions -> Add MARC holdings -> screen with Instance HRID in 004 populated and can select permanent location from look-up If underlying source is MARC, instance holdings becomes read only for anything mapped to MARC tag Export via save holdings UUIDs → Data export
Morning Glory MARC Authority app search refinements, defects, delete and export records, define control tech approach, performance improvements
Data import quickMARC edit flow to use DI update (some users seeing 500 errors when editing and this should prevent), optimistic locking, ldr and 008 validation, view MARC bib permission, show field protection indicator
Inventory
Questions quickMARC using DI flow - would like to start testing asap Deletion of Auth Rec - what happens if someone tries to bring in record again? Khalilah questions to group (Aiming for Morning Glory or earlier)
LDR/06 (type of record) cannot be edited in quickMARC. Received requests to make it editable - does this group agree? Sara: Yes need to be able to change. Assumption was to change in 008 and LDR would update. Jacquie in chat: Lacking those data in 06 and 07 means the MARC format is invalid altogether. So being able to edit would be good/nice. Often see incorrect or missing data here. But need to have 07 editable also. Right now ldr/06 and 07 controls 008. Should we continue dependency? Sara: should edit ldr and remove 06/07 bytes from 008 display. Should be in correct byte order Khalilah: Requirement change - Make 06/07 editable in ldr, remove Type and BLvl from 008, put in order based on type, maybe add byte position to LDR labels Ryan: Also critical for looseleaf cataloging updates (often done in local system)
If you put an incorrect char in ldr 06/07 what should happen to the 008? Right now a blank 008 is shown and record can't be saved or updated. Rec just hangs If we allow ldr 06/07 to be edited then new 008 would be properly set, solving above issue
System generated bytes, e.g. 20-23 - will be fixed automatically when hitting save instead of an error (like data import does). OK?
Anne Marie out today and will present next week on Data Import |