Page Comparison

• two hot fixes have been put through:
  • status of a record (can see the date/time and in-progress, as well as noting the existence of an error
    • (Laura W notes an issue with 'in-progress' and source record storage in Cornell's test database; changes are not being made in SRS)
      • Christie suggests that if there is ONLY one holdings and item, the instance updates quickly, but the more the holdings or items, the slower the delay)
      • Stephanie says this makes sense but that more work will need to be done to speed up this change)
      • references item posted in slack channel
  • Notes that records with errors in fixed fields can be loaded, but if changes are made, the bad fixed fields will not allow the record from being saved (in order to restrict bad fixed fields from disrupting data in SRS)
  • talked about issues of language codes
    • feedback from MSU on the delete icon ( required new release will highlight delete row in next release Q3)
    • saved button being grayed out (because no changes have been made - then some data change triggers the change to blue in order to save)

• Raegan at MSU and the migration (update):
  • consortium required certain considerations with records, all of them, and only their records
  • coming from III sierra
  • Overlay not working (using data import)
  • Ann-Marie asking about match points...
  • not syncing with SRS at the point of the data import
    • Discussion:
      • Have your previous decision on mapping proved to be good, or would need rethinking if possible
      • Keeping system numbers (previous system identifier)
      • but not carrying over as the default new HRID (happy to have kept those)
      • Anything you miss in FOLIO?
        • keyboard shortcuts
        • Immediate editing
        • getting used to more clicks
      • Anything in MM realm that needs better documentation, or is really lacking
        • much of it is lacking (but is following up in slack) wants to make more use of the Wiki
      • mark Arnold (wished one could add items for everything for the sake of notes, but did keep some circ counts)
        • feels the nature of item counts is more fuzzy
        • not a clear count of items per location or globally
        • items without barcode generally does not circ, but might want to revisit (acknowledges the notes could be super useful)
        • might hand enter some of these notes back into
      • Question from Felix about mapping full MARC to inventory 
        • did restrict some of this data for the instance for the sake of 'screen space'
        • Ann-Marie notes about following the trail of 'next' but that causes some confusion (Raegan suggests a next or previous button might be nice)
        • Charlotte can start some stories and processes to get that into the possible development plan
        • Mapping question of legal vs non-legal marc tags, what to do with these tags if they are NOT legal and not caught in pre migration cleanup?
        • ETL (mapped data of MARC to instance)
        • Much of this data is determined by each institution
        • Some data was emptied that was not mapped or used (and caused an issue) but this data was not needed by MSU
        • Charlotte suggests new UX principles as familiarity grows with data interactions (Laura W will add this to a new agenda in the future)
        • Christie's comment about disparity between stored MARC data (what is present) and that is seen in the Instance record (mapped and displayed)
          • really wants less information displayed if not needed by an institution's workflows
          • But the current instance in inventory displays the full mapping
        • More conversation on this later (or sooner rather than later)
    • FINAL WORD: get started early on documentation!

Please rank UXPROD-2663 - Inventory. Tenant settings for item list in the top of the instance record

Slide deck, where we can gather input on the libraries preferred display of the item list in the top of the instance record: https://docs.google.com/presentation/d/1UeEi-UqVaH7cdZYQv0NOzYyCYIOJ2dvFI7vzlaJyZoc/edit#slide=id.p

In the slide deck there is a slide per tenant. The idea is by using drag and drop of X's and numbers, then the library in an easy way can design it's preferred view. 

Notes:

• UChicago and public libraries want to add copy no.
• Libraries might be able to arrange order of and could suppress some columns (to use that space for other information)
• configurable at the tenant level (as noted in the google slides linked above)

Please also rank features Ann-Marie links to in the Implementers & Data Import Slack Channels

Add ideas here

https://docs.google.com/document/d/1u1tvfVxn6i3fTImrWWCYHlh7RT5cf3_G7YgDuxKob4M/edit