Page Comparison

Recordings are posted Here

Slack channel for Q&A, discussion between meetings

Attendees: Ann-Marie Breaux (Deactivated)

To do's in red

Agenda topics:

1. Current development: Sprint 116:
   1. Finalizing Juniper releases, Iris Hotfix 2 releases, Onboarding 5 new staff (new scrum master, 2 BE devs, 1 FE dev, 1 tester)
   2. Quick review of the outstanding bugs
2. Field protection fixes: review examples. Is this correct and complete? 
   1. Probably will not be done by Iris Hotfix 2, needed in an Iris Hotfix 3?
   2. After this, follow-on work to override field protections (once they are working properly) and update individual SRS fields
3. Bug when creating Instances instead of matching/updating them: MODDATAIMP-427
   1. Review the bug and confirm preferred action
   2. Not planned as an Iris hotfix since it's an edge case. Needed as a Juniper bugfix? Or can it wait until Kiwi release?

NOTE: Additional discussion topics in Subgroup parking lot

To do's

•  Confirm Rancher environment for Data Import/quickMARC testing (Khalilah and Ann-Marie) - IN PROCESS
•  Data Import FAQ updates (Ann-Marie) - IN PROCESS

...

1. Added rows for quickMARC edit/create actions and Instances created by POLs
2. Update instance - only updates fields that are not part of the MARC record, e.g. instance status

...

1. Update instance status (Action profile = update instance) (also implicit update of the SRS MARC)
2. Delete acq data from 9xx field (Action profile = Update SRS MARC/modify) (also implicit update to instance, to remove a vendor number, or other extraneous info. Note that the 9xx data can live on the SRS MARC but not affect the instance if the 9xx data is not surfacing in the instance. If the default MARC-Instance map does not have any mappings for that 9xx data, then no updates will surface on the Instance after the SRS MARC update)
3. Update the holdings with call number (Action profile = Update holdings)
4. Update the item with barcode (Action profile = Update item)

...

1. Batch update to an item, but not retaining the MARC record, which is just being imported to carry in the change
2. If matching only on holdings ID or item ID, will make the updates on those records and not update the ACTUAL SRS MARC;
3. A-M make a video of brief and how it affects holdings/item without Instance/SRS MARC update, versus - if I use a brief MARC to update suppress or status on a group of MARC records, will that overlay the SRS MARC

...

•  Make videos confirming the following scenarios
  •  For import profiles that match on Holdings or Item IDs (and doesn't need to affect the Instance), make a video showing what happens to SRS MARC (Ann-Marie)
  •  For a brief MARC updating the suppress status on a group of instances. What happens with the SRS MARC (A-M)
•  Talk with Kimie and see if ideas for updating the UI for implicit

...

1. 1. Lehigh MARC program creates SRS MARC for the new orders as well as Instances. In FOLIO, currently POLs only create Instances, not SRS MARCs
      1. Per Michelle Suranofsky this is the project: https://github.com/folio-labs/order-import-poc
      2. Chicago has made it more configurable and added the ability to create invoices.  Their branch: https://github.com/folio-labs/order-import-poc/tree/uchicago-invoice-import
   2. Upcoming meeting: Go through Acquisitions workflow - matchpoints, import profiles
   3. Kiwi will probably not have Data Import for MARC Order/Invoice info. Would it be helpful to prioritize matching by POL to identify relevant Instance, Holdings, Item

...

1. Fix column sorting - will help with large results sets
2. Mockups
3. Export – only errors? All?

...

1. Default profiles and EDIFACT Syntax
2. Some fixes split to a separate Jira – OK to make it lower priority?
3. Vendors
   1. Already spoken with GOBI, Harrassowitz, EBSCO
   2. Have contact info for WT Cox, Hein; will reach out to them
   3. Any others?

...

• (A-M)