The existing logic uses the InstanceId when instead it should use the ItemId.
Switch to the ItemId to ensure each item works.
This addresses the backend portion of the referenced issue.
Changes to the front-end are suggested such that each item can be uniquely identified (Such as "Barcode" or "Effective Call Number").
There are some additional performance considerations as well.
The current design fetches from the patron edge and then performs okapi requests to loans.
If we have to access Loans directly rather than through the edge module, then why not do so?
Query can be done using something as simple as:
resolves TAMULib/MyLibraryService#194
The existing logic uses the InstanceId when instead it should use the ItemId. Switch to the ItemId to ensure each item works.
This addresses the backend portion of the referenced issue. Changes to the front-end are suggested such that each item can be uniquely identified (Such as "Barcode" or "Effective Call Number").
There are some additional performance considerations as well. The current design fetches from the patron edge and then performs okapi requests to loans. If we have to access Loans directly rather than through the edge module, then why not do so? Query can be done using something as simple as:
(Taken from the edge patron code.)