2023-03-08 Data Import Subgroup meeting
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 Monica Arnold Lynne Fors Kayla Valdivieso Christie Thomas Jenn Colt Raegan Wiechert Taylor Smith Kim
Current development (Orchid)
Agenda:
- Bugfest
- Some folks are just starting to test
- Some log messages are still odd (and will not be fixed until Poppy)
- A-M ask Kitfox to run the cleanup script from - MODSOURCE-585Getting issue details... STATUS on Orchid Bugfest a couple times, to see if we clean out any orphan SRS records (which may be messing with matches) (Pending - see - BF-465Getting issue details... STATUS )
- Orders UAT
- Took care of some questions and issues raised in the Slack channel, e.g. https://folio-project.slack.com/archives/CA39M62BZ/p1678129160676939
- Backend bug related to PO prefixes and suffixes permissions
- Additional feedback?
- So far, mostly OK, though some hurdles at the beginning
- A-M will add to known issues on the UAT form: If create an open order with Create inventory = None, but with Inventory actions in the job profile, Inventory records will be created, but the POL links and receiving pieces will not be.
- Some UI changes underway, based on recent discussions; will be included in Orchid release
- Very confusing to look at the changes one by one
- Hopefully will be more clear to the users after they are all in place
- UI and handling logic changes will be made in the next couple of weeks and will roll out to the UAT site within a day or two after the Snapshot change, and to Orchid Bugfest within a week or so after the Snapshot change
- A-M will consolidate the feedback next week and discuss with subgroup; so far, no showstoppers
- Review/confirm mockup for revised log for multiple holdings/items
- See slide deck - just the log JSON for today
- Holdings and Item JSON screens look fine; not confusing
- Is there a non-edge use case for trying to create/update multiple holdings with the same perm loc from the same MARC Bib?
- See slide deck - just the log JSON for today
- Bugfest
Upcoming meetings/agenda topics:
- 15 March
- Helpful? FOLIO Production Library Import Statistics
- Review the final requirements for multi holdings/items
- Review work from log subgroup and proposed updates in Poppy
- Review of ISRI multiple profile UAT, Orders UAT, Bugfest
- 22 March
- Discuss Poppy scope
- Discuss/review mockups for MARC updates refinements
- Misc
- POL/VRN matching
- For invoices, we only consider open POs
- For Instance, Holdings, Items, we currently (Orchid and before) only consider open POs. Should we change the Inventory matching logic to allow matching on closed POs as well?
- Deleting outdated versions of SRS records
- Can we define a cutoff date? 90 days ago? 1 year ago?
- Different for records that are used during import and then not consulted again? (e.g. EDIFACT invoices, MARC bibs that only create/update orders, holdings, items)
- Effects on the import log
- Can we define a cutoff date? 90 days ago? 1 year ago?
- OCLC number cleanup
- Confirm 035 structure, aim for it to be consistent across all FOLIO tenants
- Downloading log info
- Lots of interest, especially for errors
- Including identifiers for everything
- What would UI look like?
- What would output look like?
- Variation between PTF and production library performance results - why?
- POL/VRN matching
Log
Christie Thomas (she/her) to Everyone 1:55 PM
It would be great if these transaction only records could not be saved and definitely not saved as actual.
From a log perspective I don’t think that we need to know anything about the record that is created as a part of the back end processing. In the log I only care about the sis record that is connected to the instance.
I have to leave for another meeting. Thank you for the update.
Taylor Smith to Everyone 2:02 PM
thanks!