Recordings are posted Here Slack channel for Q&A, discussion between meetings
Requirements details Here Additional discussion topics in Subgroup parking lot
Attendees: Ann-Marie Breaux (Deactivated) leeda.adkins@duke.edu Monica Arnold Nick Cappadona Jennifer Eustis
Lotus
- Lotus Folijet planning: dashboard where you can see the current scope and status of Data Import work for Lotus
- Current Data Import feature development dashboard and bugfix support
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
Agenda topics: Lotus Bugs
- Lotus Bugfest:
- Sign up for tests this week
- Ann-Marie still retiring tests that have been replaced by Automated end-to-end tests
- Ann-Marie still writing additional tests that will be available for signup this week and next week
- Create jobs without match profiles that include records with 999 ff fields cause errors in the srs-instance relationship
- What is preferred action?
- Wipe out the 999 ff and replace with a new one with new Instance and SRS UUIDs? And maybe move the 999 ff to some other field?
- Move the existing 001 down to an 035 and assign a new HRID?
- Fail the import since there is no match action (and advice the user to remove the 999 ff field, then try importing again)
- Something else?
- What is preferred action?
HRID Settings: is there ever a use case to change these after initial migration?
- Yes: define the specific use case, test it in Lotus BF, update the bug
- No: close the bug as won’t do; retire the manual TestRail
Completed job appears at top of log, then disappears, then reappears
- Is this still happening in Kiwi production environments?
- Yes: document and assign the bug to Morning Glory
- No: close the bug
- Is this still happening in Kiwi production environments?
MARC field protections apply to MARC modifications when they should not
Agree on preferred action - only applies to MARC records that have existing SRS (since field protections have no effect on newly created MARC records)
- If modifications to the incoming MARC record (add or change or remove some fields)
- Take those modifications into account, and then apply the field protections (MARC updates)
- Take the field protections into account (MARC updates), and then apply the modifications
- Vary the logic depending on whether the MARC update or MARC field protection is first in the job profile sequence
- Review use cases in the comments - build a few draft tests in Lotus BugFest and have SMEs add the details?
Extend MatchValueLoader implementations to allow filtering according to Qualifiers and MatchCriteria:
Identifier matching should allow for qualifiers, compare part, and match criteria
Are there any specific match use cases that you want to use that you cannot (NOT MARC-MARC right now; that's next)
Any qualifier/begins/contains matches that are not working but that are needed?
- MARC-MARC matching
- Lotus: Allows for any field in a MARC record except
- Are these needed in Morning Glory?
- Matching for 100-899 fields? (I think they work, but not heavily tested yet)
- Repeatable fields (e.g. 024, 035)
- Incoming record: Only first version of the field is considered (doublechecking with the dev on whether it's the first field that has the requested indicator(s) and/or subfield, or just the first field, regardless of indicators/subfield)
- If it takes Ind 1, Ind 2, Subfield into account (in addition to the data)
- Does FOLIO need to check all incoming 024s against all 024s in the existing SRS records? Or just the first?
- Wildcards for Ind 1, Ind 2, Subfield (repeatable or non-repeatable fields)
- Needed?
- Create a script for libraries to refresh Instances against an updated MARC-Instance map
- What kind of result do we expect after script? (current->expected)
- What should we do about different releases installed for different libraries?
- Do we need to upgrade script that Ian Walls wrote or we will need to write another one to update many records at a time?
- What is the scope of the script? All the instances (even updated ones) or just not updated ones?
- Lotus Bugfest: