Page Comparison

Information and updates from ARLEF

• Presentations from last ARLEF Meeting on Data Import

• • 2023 ARLEF issues on Data Import
  • 2023 ARLEF Call |Slide Deck

• FROM ARLEF notes that might be of interest

  • Still a pain point. Q to us: How much was solved, from our perspective? what’s still an issue? What are midterm work-arounds

  • Input so far: 
    • EBSCOdeck from Khalilah and Ryan
      
    • Index Data proposal, with UChicago inputInventory Importer Idea
    • Cornell’s top two tickets
      • https://

• • • • issues.

• • • • folio.

• • • • org/

• • • • browse/UXPROD-2742 - Matching
      • https://issues.folio.org/browse/MODDATAIMP-710 - Mods to MARC data as load records
  • Shawn’s report from MSU
  • Stanford report (doc to link)Stanford Data Import Issues

Information and updates from the working group

• Documenting issues in a transparent way
  • Volunteers from the working group created the Data Import Topic Tracker where people can log issues. The aim is to track when issues have been discussed in the working group, if there is a related Jira, and what actions are being taken to solve the issue. This wiki page is based on the one for Acquisitions. There is a request to review this page at least once a month in a working group meeting.
• Documenting functionality
  • Volunteers from the working group are working to create an audit functionality spreadsheet related to the deduping of the 856 field by the system,

General Updates on Functionality

• Performance/Reliability/Stability
  • Work continues on improving this for Data Import. Olamide Kolawole presented this at the last WOLFCon and is working to improve the process.
  • Slicing comes with queue management and parallel processing
• Improvements with Poppy
  • Log improvements
  • Ability to create/update multiple holdings and items
  • Fixing bugs (see EBSCO presentation)

Asks for PC

• Requirements: Need SMEs to provide real-life examples/scenarios/data to ensure we capture all requirements and meet users' expectations. 
• Documentation: Data import subgroup has mentioned that the lack of documentation has been a significant challenge. We need someone who can define a plan for how to address this challenge and then have someone(s) address it.
• PO/QA support: We would love to have PO/QA support to triage and verify user stories/bugs
• Development resources: Folijet team is also responsible for Inventory app. There are features/bugs we would love to delegate to another team/developer so that the team can focus on more data import features.