2022-11-01 Discovery Integration Subgroup Meeting notes

Owned by Uwe Reh
Last updated: Nov 01, 2022 by Nicole Trujillo
3 min read

Date

EDT 11:00am to 12:00


Attendees 

  •  

Goals

Discussion items

Time

Item

Who

Notes

11:00Start of the meeting


Discussion of the collected needs and its coverage by edge_patron

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
  • Batch Renewal, request, cancel
    • Marie Widigson The one we get the most complaints about is batch renewals (in EDS), if there is any priority this should be at the top.
    • Brooks Travis It is a known issue and is in JIRA
  • Check Out/Renewal via Terminals
    • Out of Scope

Returning to points discussed last week

  • Hold shelf expiration date
    • Managed automatically by the system whenever the item is added to the holdshelf, as set by the service point. It should be available in the response from the Patron API.
    • We looked at this last time and saw only the request patron date, not the hold date.
  • Pick up location, change pickup location
    • Demian Katz Is there a reason to single these two out?
      • Brooks Travis You can create and cancel requests. Maybe we should include the ability to modify request so that we could include all of those functions?
  • Granular error messages
    • Brooks Travis Current apis get why the system fails; most systems will want to translate this for the users
      • kristin.olofsson Currently it's hard to translate through discovery as their are so many different error codes. 
      • Need a translation table (circulation example) in the Discovery system.
        • Discussion of if this should live in discovery system vs FOLIO
      • In favor of codes rather than strings since strings change.
  • Patron info, change patron info
    • This needs to be a separate api, since this is confidential information
    • It could still be a part of the patron api module, but have a dedicated endpoint/method to preserve confidentiality




11:55How to proceed

Uwe Reh How should we proceed? Finish this discussion and next week start on availability api? Or should we talk about what to do with the patron api information (looking for existing JIRA, existing functionality, ways of making sure these issues are addressed)?

Group decided to finish this discussion and then start on the other apis to get a sense of scope and then double back to the technical detail. Brooks Travis will help with finding JIRA and current functionality in the system and reporting back to the group (Thank you! Others are welcomed to help!)

12:00End of the meeting