Last week we started discussing the collected needs and identifying what is already covered and making edits.
First we went through to ask any further questions or clarifications about Title/Key items.
place in line (que number)
What does it mean?
If you have a que in requests, how many patron requests are before you.
edge- patron quePosition
Where does it display?
Results display
Account display
Indicate items that can't be renewed
Other messages we might to include
Uwe Reh Should we add patron is locked, maximum number of renewals is reached?
These two are patron specific reasons why a patron cannot check out, whereas the other point deals with item status
Brooks Travis One potential issue is that FOLIO can’t know if an item is renewable until it tries to renew it… since the loan policy is (potentially) updated during that process…It could “estimate” it based on the current loan policy value of the loan…Or retrieve the currently applicable loan policy in the backend, prior to the response…
Human-readable pickup locations
Currently FOLIO stores the pickup locations in one language/text field. Discussion on if there was a separate display
Course reserves
Moved to other page
Proxy support
How can this be supported by the patron interface api?
Is the idea for the user to be able to check their account? "I am proxy for x, x is proxy for me."
Also, could the user perform functions for their proxy when logged in as themselves? i.e. if they login as themselves, then they see a book they want to check out for someone they are a proxy for, they can do so without having to log out.
How would this work?
Brooks Travis Currently when EDGE-API asks for patron information it's provided just an external system id with parameters that can be passed. While we could use the HRID, it would be better if using the UUID (less high-level).
This functionality would take both API and Discovery UI work to make happen, leave for further discussion.
Title v. Item Level Request
Brooks Travis This should be supported as of Morning Glory