2023-03-22 Data Import Subgroup meeting

Owned by Ann-Marie Breaux (Deactivated)
Last updated: Mar 29, 2023
4 min read

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 Raegan Wiechert leeda.adkins@duke.edu Lynne Fors Monica Arnold Christie Thomas Kim Lisa Smith 

Current development (Orchid)

Agenda: 

  • Announcements
    • FOLIO Production Library Import Statistics - thank you for adding some in the past week; keep adding!
    • New Folijet (Data import) Bug Dashboard, for anyone who wants to track
      • Check Jira - see if Christie/Jennifer E has different permissions from others - cannot assign issues to A-M
      • If cannot assign issues, try at-mentioning people in Interested parties or in a comment
      • A-M: When changing bugs into spikes or features, try to retain something that indicates it's a bug; maybe retain the original bug as a testing Jira once the story/task/feature work is done
    • Data Import tips and tricks (wiki) documentation likely getting an overhaul
      • Have a separate Slack channel for DI-documentation?
      • Jenn will create a new channel for DI-documentation and advertise it in the regular DI channel and maybe MM SIG channel
      • Maybe create field mapping profile pages for each type of record, and have a table that lists the fields, what type they are, validated or not, and any special notes (is a field required? is there info in an info icon on the field mapping profile that should be noted in the documentation?)
      • Plan to discuss more at lab on 30 March; Jenn will invite Erin
  • Bugfest and Orders UAT
    • Folijet has 410 manual test cases on TestRail. All were tested during Bugfest
    • We have 3 failed that have been deferred to Poppy
    • Some will need re-testing when we finish the Orchid Bugfix releases next week
    • Remaining Orchid Bugfixes are listed here
    • Any outstanding questions? 
      • Vendor mapping: test based on the Jira: MODDICORE-303 - Getting issue details... STATUS and its associated TestRail
      • Acq Unit? No bug, because it was a user error. Importer must be a part of the acq unit(s) being assigned by the field mapping profile, or else the order will not be created
      • A-M: Check whether there is a TestRail for Acq Unit, and create one if not
      • A-M: Check if there is an error message if a user does not belong to an acq unit and tries to create an order for that acq unit
        • Error message is not very informative; added a story in Poppy to make it better: UIDATIMP-1425 - Getting issue details... STATUS
      • A-M: Add 2 little stories for an info icon for acq unit on order and invoice field mapping profile (importer has to be a member of any acq unit being assigned in the field mapping profile)
  • Log subgroup work
    • Quickly reviewed the background slides
    • Homework: please look at them more before next week; add comments/questions
    • We will discuss more next week; goal is to finalize the requirements, so that we can finish the Jira stories in the next 2 weeks

Upcoming meetings/agenda topics:

  • 29 March 2023
    • Final review of ISRI multiple profile UAT, Orders UAT, Bugfest, Orchid release
    • Poppy scope
  • Misc
    • Discuss/review mockups for MARC updates refinements
    • 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
    • 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?
    • Revisit use cases for Updating individual MARC fields - what are the most common use cases?


Chat

Jennifer Eustis  to  Everyone 1:15 PM
Same thing for me. I ping Ann-Marie in the comments

Christie Thomas (she/her)  to  Everyone 1:17 PM
All good tips. Thanks!

Jennifer Eustis  to  Everyone 1:29 PM
Thanks Jenn

Kimberly Wiljanen  to  Everyone 1:32 PM
what time is the lab meeting?

Jenn Colt  to  Everyone 1:33 PM
Thursday at 3

Jennifer Eustis  to  Everyone 1:34 PM
https://cornell.zoom.us/j/232783383

You  to  Everyone 1:40 PM
Vendor mapping Jira: https://folio-org.atlassian.net/browse/MODDICORE-303

Lynne Fors  to  Everyone 1:42 PM
Is there a Nolana HF coming?
If anyone knows

Jenn Colt  to  Everyone 1:49 PM
I have not seen one get approved in the bug triage channel

Lynne Fors  to  Everyone 1:50 PM
I was wondering as I saw a Jira issue with it as a release

Lynne Fors 1:50 PM
https://folio-org.atlassian.net/browse/CIRC-1737

Jenn Colt 1:51 PM
For us EBSCO patched that without a hot fix being released so they should be able to do that
I think people are wondering about this though if someone in RA sig can address it

Lynne Fors 1:53 PM
Thanks