Page Comparison

Recordings are posted Here                                           Slack channel for Q&A, discussion between meetings

Requirements details Here                                             Additional discussion topics in Subgroup parking lot

Attendees: Ann-Marie Breaux (Deactivated)   leeda.adkins@duke.edu Jennifer Eustis Timothy Watters Autumn Faulkner Robert Scheier Christie Thomas Jenn Colt Lloyd Chittenden Raegan Wiechert 

Lotus

• Lotus Folijet planning: dashboard where you can see the current scope and status of Data Import work for Lotus
• Current Data Import feature development dashboard and bugfix support

Agenda topics: Morning Glory refinement

• Other things we need to consider as priorities
  • Field protections (Jenn/Cornell)
  • Matching issues (Jenn/Cornell)
    • Expanding MARC-MARC - make sure we have Bugfest
    • When you add a submatch, the results are not cut down
    • Build a match for the smallest record (item) and then be able to update its associated holdings and its associated instance and its associated MARC Bib
  • Matching and associated actions are challenging
  • Problems with multiple 856s in the same MARC Bib
  • Issues with MARC Modifications
    • Hasn't been practical to use because not being able to use MARC-MARC match and not being able to nest (5C/Cornell)
  • Creating/Updating multiple holdings and items from 1 MARC Bib (Christie: Chicago/Seattle PL/5C)
  • Maybe a survey: top priorities for live and about-to-be-live libraries for functionality that is missing (A-M)
  • Separate section of the survey: what are your library's top 3 workflows that are not supported adequately by DI today (Kiwi) (A-M)
  • DI affecting Circ performance: how much is that addressed in Lotus? (A-M to PTF and Folijet)
  • Delete all holdings based on an input file (Christie/Chicago)
  • Jenn E/Raegan: First Single record import (Jenn) or Regular import (Raegan) of the day always bombs in their local environment
    • Completes with errors
    • Run the same file and job profile again and it works fine
  • Still getting the resume message Jennifer E (Kiwi)
  • Check MARC-Instance matching and updating the MARC. Isn't it already working?
• Update the overview in tips & tricks to identify which release something is done or planned (A-M)
• Permissions: if we make permissions more granular in Morning Glory, what distinctions would be needed? 
  • Data Import Permissions Refinement
  • UXPROD-1384
  • Current UI Permissions: 
    • Data Import: All permissions
      • Upload files
      • Assign job profiles
      • Run imports
      • View logs
    • Settings (Data import): Can view, create, edit, remove
      • All 4 profile types
      • File extensions
      • Field protections
  • Possible new permissions
    • Data Import: All permissions
      • Does this need to be broken down any? If so, how?
      • Raegan: small library; all are fine
      • Christie: mainly agree, maybe be able to have view only for logs
      • If view only (cannot upload, cannot assign job profile, cannot run job); but can get to the landing page, view all/search and filter, and use hotlinks in the log details
    • Settings (DI): All permissions
      • How to break this down?
        • View only option? Not urgent; if library doesn't want users to view, just give them DI permissions, but not DI Settings
        • Separate permission for Field protections? All permissions or no permissions for Field protections
        • What else?
  • Inventory Single Record Import has separate permissions - leave those alone?

    • Inventory: Import single bibliographic records

    • Settings (Inventory): Configure single-record import
  • Probably will leave existing Data Import permissions (all) as-is and add more restrictive permissions
    • Will prevent problems from deleted permissions
    • Carve out file extensions and field protections
    • User admin would need to review users with current DI permissions to decide if they should be reduced to a more restricted permission
    • Subgroup is fine with that
• Data Import Support for the new Inventory Admin Note (all 3 record types)
  • UXPROD-2892
  • Is there a use case for matching on the Admin Note? If yes, we'll add stories for that.
  • No use case identified, especially since it's a free-text field
  • If no, we'll only add stories for field mapping profiles and importing the data
  • The Admin note field will not be mapped in the MARC Bib-to-Inventory Instance or MARC Holdings-to-Inventory Holdings default mappings
  • When a user edits an Instance or Holdings with Source = FOLIO, the Admin note field will be editable (not controlled by the underlying SRS record)

...

From Jenn Colt to Everyone 01:06 PM

...