...
- Thunderjet:
- Create API endpoint that would allow lookup by POL for related Instances, Holdings, Items
- Already have a query for using VRNs to find POLs
- No additional indexes needed, since there are already searches and indexes for POLs and VRNs, which probably will be fast enough
- Folijet:
- Create match queries and matching logic for POLs and VRNs
- Will need cross-index query if POL/VRN matches need to be limited to specific statuses (e.g. Open (and maybe closed), but not Pending)
- Add stories for happy path and exception Karate tests
- Prokopovych:
- No dev work required
- Other
- Have PTF help with performance check once dev work is completed
- Analyze MARC-MARC matching for 0xx and 9xx fields (based on the MARC query work previously done)
- May not be needed if can use MARC-Instance matching to create/update SRS MARC Bib
...
- Folijet:
- Update UI matching screen to include options for POL and VRNs for each Inventory record type
- Add stories for happy path and exception E-to-E tests
Developer Questions:
Question | Status | Conclusion | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| What changes are needed to the UI matching screen? |
| ||||||||||
| Any different considerations if the match-from and/or match-to field is repeatable? |
| ||||||||||
| Where do we pull the POL and VRN from, and how are they linked to the appropriate instances, holdings, items |
| ||||||||||
| If we only wanted to match on POLs or VRNs for orders that are Open (and maybe Closed), but NOT Pending, would that be an issues? (we already use similar logic for EDIFACT invoice matching between Invoice line and POL/VRN) |
| POs with Ongoing status (in receipt or payment) are included with Open Order status is at the PO level, but POL/VRN are at the POL level. May need to hit a composite endpoint to get the number and the status. Per Siarhei H, can use cross-index query to also find the status of a POL | |||||||||
| E-to-E automated tests; how many, and happy path only, or negative too? |
|
|
...