Versions Compared

Key

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

Recordings are posted Here (2022+) and Here (pre-2022)                   Slack channel for Q&A, discussion between meetings

...

Attendees: Ann-Marie Breaux (Deactivated) Jennifer Eustis Monica Arnold 

Morning Glory

...

  • MM SIG presentation on last week Data Import and Morning Glory/Nolana
  • Deleting import logs via API:
    • Available as of Morning Glory
    • There was a Slack question recently about being able to delete Import logs via API as of Morning Glory. We have added some documentation in the Data Import tips and tricks. Please see this page: 4-Data Import Logs, in the last section: Deleting Import Logs via API.
  • MARC Modifications and Field protections
    • MG bug:
      Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyMODDICORE-248
    • Modify scenarios – describe real use cases – homework
    • Any scenario where a job would have a Modify action without a Create or Update?
      • Example: https://bugfest-mg.int.aws.folio.org/settings/data-import/job-profiles/view/5564537e-9bda-426f-a755-de5ae16d7ebd?sort=name
        • What would be the expected outcome for a job set up like this?
      • Would it be valid to say that field protections and overriding field protections only invoke when there is one of these Update actions in a job profile?
        • Update MARC Bib (protect and override)
        • Update Instance (protect only, if override need an Update MARC Bib action)
        • Update MARC Authority (protect only, in previous discussion, decided that overrides are not needed for MARC Authority, only Bibs)
        • Not for update Holdings, Item actions (no MARC record underneath)
        • Not for update MARC Holdings action (field protections not currently allowed in FOLIO, per previous discussion)
  • Lotus HF3 Hot fixes for Data Import:
    • View list here
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyMODSOURCE-509
      : working except one small issue; when an incoming MARC Bib has an HRID in 001, an 035 will be created; documenting as known issue in Lotus; attempting to correct in Morning Glory
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyMODDICORE-272
      : working but would be good to have additional testing
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyMODSOURMAN-841
      : working but would be good to have additional testing
  • Morning Glory Bug fixes for Data Import: 
    • View complete list here
    • View unclosed bugs here
      • Some issues have different solutions for Lotus HF versus MG Bugfix versus Nolana, e.g.
        Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyMODSOURCE-509
        versus
        Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyMODSOURCE-528
        , or
        Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyMODSOURMAN-841
        versus
        Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyMODSOURMAN-843
        ; fixed Lotus first, now MG in progress
      • Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyMODDICORE-275
        : tested on Snapshot, and seems to be working properly; would be good to have someone else test it on Snapshot and confirm, before we release it to MG BF
      • Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyMODSOURMAN-840
        : finishing the fix; files where some records have 999 ff's and some don't were giving us the most trouble
      • Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyMODINV-709
        :
        • Separate profiles for 1) match by POL and update Inventory records and 2) match by VRN and update Inventory records work properly
        • Aiming to fix in Nolana; use separate profiles as a workaround for MG

...