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) Christie Thomas Heather MacFarlane (Deactivated) Jennifer Eustis Lynne Fors Monica Arnold Taylor Smith Timothy Watters Lloyd Chittenden
Morning Glory
- Morning Glory Folijet and Spitfire planning: dashboard where you can see the current scope and status of Data Import work for Morning Glory
...
- Lotus Potential Hotfixes:
- Key factors: regressions or not, risk level, data integrity, any workarounds
- Quota Exceeded error
Jira Legacy server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIDATIMP-1205 - Will be included in Lotus HF2
- Awaiting deployment to Lotus BF, so that it can be tested
- Holdings source problem, when Holdings created by opening an order is updated by Data Import
Jira Legacy server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODORDERS-717 - Will be included in Lotus HF2
- Is not locking down fields, but changes the Source from FOLIO to MARC
- Fix is ready and is awaiting deployment to Lotus Bugfest for testing
- Will add a note in the Lotus release notes about related scripts for fixing existing Inventory Holdings with Source = MARC, but no underlying MARC Holdings in SRS
- 035 Matching regression
Jira Legacy server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODSOURCE-521 - May be included in Lotus HF3
- Related to
Jira Legacy server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODSOURCE-509 - Also have to be competing 035s to happen, so if clean all of them out, it's OK
- Also can pre-construct the new 035, and that helps
- Affects MARC-to-Instance, which we were not trying to change
- Almost done with the development work, then need to test heavily and release in Lotus HF3
- Dev team's recommendation is to only release the regression fix, not all the work from both Jiras - is that OK?
- Hopefully extensive testing in Lotus BF by SMEs
- Protected fields being removed from the record on import
Jira Legacy server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODDICORE-272 - The 2 scenarios actually look like 2 different issues
- Scenario 1: (field number): already fixed in MG, but low-ish risk to backport to Lotus
- Scenario 2: ($5 value on any field):
- Per Christie, it was definitely working in Kiwi - doublecheck
- Still looking at whether it ever worked in Kiwi or not
- It is working in Morning Glory
- It is risky to backport to Lotus
- Is it OK to add a "known issue" release note for Kiwi and Lotus, as long as it's fixed in MG? Need to revisit this once more testing and discussion with devs
- The 2 scenarios actually look like 2 different issues
Change default mapping for relator term (Nolana)
Jira Legacy server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODDATAIMP-700 - Similar to how the 336 mapping was changed - OK?
- Yes - still TBD if the Instance field will change to multi-select; if not, only the first relator term is visible in the Instance, but all are still in the SRS MARC underneath
...