Versions Compared

Version Old Version 2 New Version Current
Changes made by

Jennifer Eustis

Christie Thomas

Saved on

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: Robert Pleshar Autumn Faulkner Jennifer Eustis Lynne Fors Ryan Taylor Sara Colglazier Whitney Christopher Kim Wiljanen Christie Thomas Vivian Gould Lisa English

Notetaker:  Christie Thomas

Links:

...

TopicWhoMeeting NotesRelated JiraDecisions and Actions

Announcements:





Request for Data Import Job Profile examplesRyan

To support the Performance Testing team, we are asking users to share real-life examples of Data Import Job Profiles that could be used during testing. 

If you have a job profile to share, please reach out to Ryan Taylor. Job profile details can be shared via screenshots or by leveraging the job profile export function via API described here: https://folio-org.atlassian.net/wiki/x/NYCnIQ

  • The export should work in Quesnelia (Ryan will test after the call.) It is only the import that will not work until Ramsons. 


Documentation Discussion: Identify gaps/needs

Ryan/All

Spreadsheet for tracking documentation needs:

Lref gdrive file
urlhttps://docs.google.com/spreadsheets/d/1ejmYJ2Tc9TYkZ4HiXjQTpVFaIZB72ckthP68zTjI0Pw/edit?usp=sharing

  • Reminder to fill in the Documentation needs spreadsheet.


Trouble Editing in QuickMarc after Overlay

Raegan

From Slack: "I just tried again and I am not able to edit in qm after overlay (currently on Quesnelia sp-5). I have not heard anything on my Ebsco ticket (and I don't know if the person who is in charge of submitting our tickets actually submitted it or not). However, there have been a couple of Jiras filed. MODCPCT-85 describes the same problem, but it was closed as a duplicate of MODDATAIMP-1058. It has been closed and is set to be a part of the Ramsons release. So I have just kept a list of the problem records, waiting until we upgrade to Ramsons and have been avoiding using overlay (which has been annoying)."

With Ramson's release unknown, is it possible to backport this to Quesnelai?

  • Chicago is also seeing something similar on occasion.
  • There is a script to clean up multiple actual srs records. Underlying problem will be resolved in Ramsons.
  • Ticket for the unerlying issue:
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyMODDATAIMP-1058


Review Topics Tracker


All

Data Import Implementers Topic Tracker

The following issues

below

Sunflower Flower Release are labeled for Sunflower. Knowing that there isn't a lot of time, what are priorities for Sunflower

?

  • https://folio-org.atlassian.net/browse/MODSOURMAN-1094

  • https://folio-org.atlassian.net/browse/MODSOURMAN-857

  • https://folio-org.atlassian.net/browse/MODSOURCE-691

  • https://folio-org.atlassian.net/browse/MODSOURCE-665

  • https://folio-org.atlassian.net/browse/MODSOURCE-594

  • https://folio-org.atlassian.net/browse/MODDICORE-386

  • https://folio-org.atlassian.net/browse/MODDICORE-386

  • https://folio-org.atlassian.net/browse/MODDICORE-353

    • https://folio-org.atlassian.net/browse/MODDICORE-352

    ?

    What is the most important thing for SME's in regards to Data Import for this year?

    • Ryan will spend some time reviewing tickets and any others to review non-feature work. And possibly move things back into Trillium. 
    • For 2025 focus on Documentation. 
    • Start testing in the Eureka environment for Ramsons. (Will be a Ramsons Eureka environment and a snapshot Eureka environment. Links will be shared.)
    • Ideas:
      • Enhancements to log messages. 
      • Enhancements to set for deletion. 
    • There is a set for deletion that will be worked on in Sunflower. 
      • Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyUXPROD-4944
    • Comment: Set for deletion should not be the first check box in the edit instance record since there is a lot of muscle memory for clicking suppress from discovery in that space. 
    • Q: Selecting set for deletion will place a d in the LDR 05 position. And deleted will be set to true. Can it be unchecked? Yes. LDR 05 will be set to c and deleted will be set to false. 
    • Q: What changes are made to staff suppress and suppress from discovery when a record when set for deletion is unchecked? Should suppress from discovery or staff suppress be unchecked? 
      • Two votes for leaving suppress from discovery checked and unchecking staff suppress. 
      • Two votes for both being unchecked.



















    Notes from previous meetings...





    ...