2023-03-01 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 Lloyd Chittenden leeda.adkins@duke.edu Taylor Smith Lisa Smith Raegan Wiechert Monica Arnold Kim Jenn Colt Autumn Faulkner Jeanette Kalchik
Current development (Orchid)
Agenda:
- Announcements
- Signup for Bugfest and test cases happening this week
- Actual testing starts next week
- New MARC-to-Instance wiki page
- Default MARC Bibliographic-to-Inventory Instance Mappings
- Still in progress, but cleaner and simpler than the underlying Excel file
- Will clean up the Mappings landing page after this is finished
- Will also find and organize the MARC Holdings and MARC Authority mapping pages
- Order import UAT
- https://forms.gle/yxACZ8TAQL48tKCP6
- Creating a few test profiles that folks can use, or you can create your own
- Check on status of repeated 050 call number bug - Jennifer
- Signup for Bugfest and test cases happening this week
- Review/confirm mockup for revised log for multiple holdings/items
- See slide deck - just the log for today
- JSON for multiple items - separate green blocks for each item's JSON, but all on the same tab; if an error, that red block should appear just above the green block for the affected record
- A-M/Kimie mock up JSON screens for the holdings and items in the sample log and add UI stories
- JSON for multiple items - separate green blocks for each item's JSON, but all on the same tab; if an error, that red block should appear just above the green block for the affected record
- Confirm identifying data for holdings (HRID or perm loc?) and item (HRID ok?)
- Holdings - Perm Loc
- Some interest in Permanent Location and HRID, but OK to start with just PermLoc
- If both, maybe would need an ellipsis, and when hover over it, would see the rest of the data; that is more extensive dev work
- Item - HRID
- Implications for existing logs (from pre-Poppy imports)
- Item: HRIDs will be fine; already stored with the log data
- Holdings: PermLoc is not currently stored, so pre-Poppy logs will not show that data; will need to add some tests to ensure that we don't break pre-Poppy logs
- Holdings - Perm Loc
- Is there a non-edge use case for trying to create/update multiple holdings with the same perm loc from the same MARC Bib?
- Still TBD; discuss next week
- See slide deck - just the log for today
- Announcements
Upcoming meetings/agenda topics:
- 8 March
- Continue Order UAT
- Review of ISRI multiple profile UAT
- 15 March
- Review the final requirements for multi holdings/items
- Review work from log subgroup and proposed updates in Poppy
- 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?
- POL/VRN matching
Chat
Lisa Smith, Mich State to Everyone 1:11 PM
Thank you for adding it!
Lisa Smith, Mich State to Everyone 1:25 PM
I'm really looking forward to this! Will try to test Friday. I'm out for spring break next week.
Kimberly Wiljanen to Everyone 1:33 PM
I think so --
Lisa Smith, Mich State to Everyone 1:33 PM
I like the set up
Taylor Smith to Everyone 1:40 PM
a screen would help
Lisa Smith, Mich State to Everyone 1:42 PM
I think that's ok; it's kind of like the invoice voucher export
Jenn Colt to Everyone 1:42 PM
I have to run!
Kimberly Wiljanen to Everyone 1:42 PM
I think it makes a lot of sense and it could be difficult to change the Jason tabular structure
Lisa Smith, Mich State to Everyone 1:45 PM
column=total error count
Christie Thomas (she/her) to Everyone 1:48 PM
But, the permanent location is not always unique
Kimberly Wiljanen to Everyone 1:49 PM
Yes
Taylor Smith to Everyone 1:49 PM
sound good to me
Lloyd Chittenden to Everyone 1:50 PM
I would prefer location.
jeanette kalchik to Everyone 1:50 PM
The location would be nice.
Christie Thomas (she/her) to Everyone 1:50 PM
I prefer hrid, but location would work most of the time and we could just look up each individual record if we need to when it matters.
Kimberly Wiljanen to Everyone 1:51 PM
HRIDs might be more reliable
Taylor Smith to Everyone 1:52 PM
I agree with Christie. I would slightly prefer HRID, but either would be fine most of the time.
Lisa Smith, Mich State to Everyone 1:54 PM
Would be nice to have both hrid & location
Jennifer Eustis (she/her) to Everyone 1:55 PM
+1 Christie
Lisa Smith, Mich State to Everyone 1:55 PM
+1 Christie
Kimberly Wiljanen to Everyone 1:55 PM
It's a question of what can be done, granularity always helps if it can be established.
location is usually what most of us are looking for initially
Taylor Smith to Everyone 1:58 PM
an ID download would be great for the future
Jennifer Eustis (she/her) to Everyone 1:59 PM
and marc srs
Kimberly Wiljanen to Everyone 1:59 PM
+1
jeanette kalchik to Everyone 1:59 PM
+1 for reporting.