Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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:
        Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyMODDICORE-303
        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
      • 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

...