...
- Lotus Bugfest:
- Testing began this week; any issues?
- Ann-Marie still writing additional tests that will be available this week and next week
- Set up your own logon
MARC field protections apply to MARC modifications when they should not
Ann-Marie: build a few draft tests in Lotus BugFest and have SMEs add the details
- Create a script for libraries to refresh Instances against an updated MARC-Instance map
- First iteration this week; get it to do the right thing, then work on speed
- Script would be deployed on demand
- Would act on all instances with Source = MARC
- Release version would not matter
- Any other questions or requirements?
- MARC Field protection:can
- Can we assume that LDR, 002-009 fields would never need field protection
- If any do need field protection (maybe 006 or 007), can we always assume * for data? (Ind1, Ind2, Subfield n/a)
- Record matches are not decreased when additional match conditions are added to a job profile
- See example in bug; Devs need additional examples of multi-tiered matches
- Make first match as specific as possible (retrieve no more than 90 results), then secondary match to narrow that further
- Kiwi release notes: add as known issue
- Lotus release notes: add that this is partially addressed in Lotus fix, will aim to change/remove restriction in Morning Glory
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?
- Lotus Bugfest:
...