/
2025-2-26 Data Import Subgroup meeting

2025-2-26 Data Import Subgroup meeting

Owned by Ryan Taylor
Last updated: Feb 26, 2025 by Christie Thomas

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: Ryan Taylor, Jennifer Eustis, Robert Pleshar, Whitney Christopher, Tess Amram, Lynne Fors, Raegan Wiechert, Yael Yod, Christie Thomas, Mary Aycock, Sara Colglazier

Notetaker: 

Links:

Agenda: 

TopicWhoMeeting NotesRelated JiraDecisions and Actions

Announcements:


WolfCon 2025 will be in Kansas City September 23-25, 2025 with a pre conference on September 22. The request for papers is not out yet, but will be posted soon. 



Review current status of UXPROD-4944: Set for deletion - Phase 2 enhancementsRyan Taylor
  • Uploading MARC Bibs with Leader 05=d results in 'set for deletion' flag + 'suppress from discovery' + 'staff suppress'.
  • Set for deletion flag displays on Instance view + updated warning.
  • Set for deletion checkbox control now available on Edit Instance view.

Discussion notes:

Q: Will the check box field be placed on the holdings and items as well? A: The scope of this was just for instances. Holdings and items is the next phase. There is an open question about how connected holdings and items be impacted by the change to the instance? This property on the holdings and items would facilitate those actions. 

Q: What happens to the piece in receiving when there is a connection to a POL? What would happen in orders if the inventory records go away? A: This spreadsheet on what should happen when there are dependencies should help determine this:

Q: What about the placement of the set instance for deletion? It is currently first  in the list of checkboxes and displaces suppress from discovery then staff may accidentally choose set for deletion by muscle memory. A: Recommendation to take back to developers: at the end of the list, after Previously Held.

Q: What about permissions? Will set for deletion permission that controls the action from the instance action menu also control the ability to edit the Set for Deletion checkbox? A: Ryan Taylor will need to check with developers on the permissions. 


https://folio-org.atlassian.net/issues/UXPROD-4944
Review Log Enhancement ideasAllInitial Log enhancement ideas:
  • Update Data Import log view to default display of more than 100 records (This could be controlled in settings e.g. 100, 200, 300, 500, 1,000)
  • 'No action' needs to be reported in the log summaries (e.g. Completed, Completed with Errors, Completed with No Actions)
  • Offer ability to Download a csv of the logs (e.g. Action dropdown option for 'Export logs'). This should be available for both, File-specific logs and Overall Job logs.
  • With the logs it would also be nice if the 001 of the incoming records could be displayed. Today, if there are multiple 'no actions', you have to use the title or click into each record to clarify value.

Further questions:
  • What additional fields would be helpful to include in Data Import logs?
  • What kind of reporting would be helpful in relation to Data Import?

Discussion notes: 

Feedback from Christie Thomas that log performance when there are more than 1000 records is not great currently. Some feedback that individuals would not prioritize changing the default or adding an option to display more than 100 records at a time in the log. 

Additional feedback that perhaps we should prioritize reporting and the downloading of the log, downloading of errors, and downloading of record sets for external analysis or processing.

Additional fields - include the time for the entire job and not just the split job. This could be addressed by a single log for the entire job that allows for drilling down into the logs for the parts. If this UI could provide a summary across all parts, a link to error records from across all jobs, show total run time, etc. 

No action / No content errors - improved reporting in this area would help identify issues that need attention. No action could mean that there is an error and no action was taken or that the import profile indicates that no action should be taken. In this instance there was not an error. There is no way to differentiate between No action that is an error and no action that is not an error. 

Users should provide examples of the No content error in data import logs. Examples will be discussed in the next meeting.









Documentation Discussion: Identify gaps/needs

Ryan/All

Spreadsheet for tracking documentation needs:



Review Topics Tracker


All

Data Import Implementers Topic Tracker


















Notes from previous meetings...





Upcoming meetings/agenda topics: --


Chat: 


Related content