Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Recordings are posted Here (2022+) and Here (pre-2022)                   Slack channel for Q&A, discussion between meetings

Requirements details Here                                                                    Additional discussion topics in Subgroup parking lot


Attendees: Ann-Marie Breaux (Deactivated) Jennifer Eustis Heather MacFarlane (Deactivated) Timothy Watters Kim Wiljanen Jeanette Kalchik Lisa Smith Taylor Smith Jenn Colt Christie Thomas Jamie Jesanis (Unlicensed) 

Current development (Orchid)

Agenda:

    • Migrating profiles from Lotus to MG
      • Per Jenn Colt significant effort to update matches and updates to take advantage of the field protections
      • If you want to override field protections, but also update instance with admin data, you have to change to a MARC-MARC match and add a MARC update action into the existing profile, which allows for overriding the field protections
      • And if adding a statistical code, also have to match to the Instance and then update instance
    • Creating/Updating Multiple Holdings/Items on a Single Instance
      • Jira Legacy
        serverSystem JiraJIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyUXPROD-3729
      • See beginnings of documentation/strategy here, including questions from developers
      • For matches: item submatch (e.g. On order) can also be really helpful
      • Do we agree on the base functionality that is needed? 

Log info for multi - have row for instance, then row for each holdings/item created/updated/discarded - for multiples, show HRIDs or locations to make it clear which one(s) were acted on; would be helpful for the single imports as well as multi

Future: Export/download the reports, with identifiers for all records that were acted on and what happened

Image Added

Upcoming meetings/agenda topics:

  • Creating orders from imported MARC Bibs - E2E review and testing
  • Limitations of DI in terms of being able to do what is needed
    • Update the instance and the SRS - and having to do separate matches for them
    • Needing to use a submatch for the instance, e.g. match on the 035 and then submatch for the instance status
    • Would there be a way to invoke field protections when updating Instances instead of doing separate matches for SRS and Instance
    • Flexibility in field mapping profiles, e.g. go back to defaults when you selected a dropdown value
    • A-M add to the list of general future topics

Comments

(copy from meeting recording)