Patron Portal Support (for Patron Features in Discovery) (UXPROD-992)

[UXPROD-351] Patron Portal Support (for Patron Features in Discovery) Created: 05/Mar/18  Updated: 16/Sep/20  Resolved: 21/Nov/18

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q2 2018
Parent: Patron Portal Support (for Patron Features in Discovery)

Type: New Feature Priority: P3
Reporter: VBar Assignee: Khalilah Gambrell
Resolution: Done Votes: 0
Labels: edgeapi, external_sys_int, patronportal
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to FOLIO-354 Integrate VuFind + FOLIO In Progress
relates to UXPROD-1061 Title-Level Requests (Basic) Closed
relates to UXPROD-1809 Title-Level Requests (Basic) - bug fi... Closed
relates to UXPROD-1810 Item-Level Requests - discovery servi... Closed
relates to UXPROD-365 Edge API for Patron Portal Closed
relates to UXPROD-366 Develop mod-patronportal Okapi Module Closed
relates to UXPROD-367 Configuration for Patron Portal Closed
Epic Link: Patron Portal Support (for Patron Features in Discovery)
Front End Estimate: Small < 3 days
Front End Estimator: VBar
Back End Estimate: XXL < 30 days
Back End Estimator: VBar
Rank: Chalmers (Impl Aut 2019): R1
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: GBV (MVP Sum 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: MO State (MVP June 2020): R1
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R1

 Description   

The Patron Portal encompasses the set of functionalities through which Patrons interact with the Folio system. Patrons do not directly log-in to the Folio User Interface and as such there is no UX associated with the Patron Portal The Patron Portal consists of a set of APIs that allow the users to perform actions such as: placing a hold on an item; paying overdue fines; etc.. The Patron does not interact with the APIs directly but rather through user interfaces that integrated to those APIs: e.g. an OPAC or Discovery system.

The Patron portal would also be used to implement some of the functionality required by GDPR: such as correcting a user record.

Estimates from stories:
UXPROD-367 Closed Configuration for Patron Portal FE: Small < 3 days BE: Medium < 5 days
UXPROD-366 Closed Develop mod-patronportal Okapi Module FE: None BE: XL < 15 days
UXPROD-365 Closed Edge API for Patron Portal FE: None BE: Medium < 5 days

Features completed for this feature:

  • Patron authentication via SSO
  • Ability to view loans
  • View fines & fees
  • View holds
  • View past history of loans returned & paid fees
  • Renew loans on items

The ability to issue holds by title are being handled by an additional feature: UXPROD-1061 Closed



 Comments   
Comment by Cate Boerema (Inactive) [ 26/Apr/18 ]

VBar, I need to tag this with a project. Is it Analytics? GDPR? Something else?

Comment by VBar [ 26/Apr/18 ]

None of the above. It is essentially the Patron domain for Folio - which doesn't have a UX component, but only an API. You might want to go with "Patron" or even "OPAC Integration"

Comment by Cate Boerema (Inactive) [ 09/Jul/18 ]

Changing all the external system integration features into epics. While this will extend the epic list by 7 items, these really are all mini-projects that can be assigned to teams and have POs and priorities. In that regard, they make sense as epics. I will deprecate the old External Systems Integrations epic.

Comment by Cate Boerema (Inactive) [ 09/Jul/18 ]

Actually, I should keep these as features and clone to create epics. I will change this back to a new feature and link it up to a new, cloned epic: UXPROD-992 Closed

Comment by Hkaplanian [ 21/Nov/18 ]

I'm closing as we have completed:

  • Patron authentication via SSO
  • Ability to view loans
  • View fines & fees
  • View holds
  • View past history of loans returned & paid fees
  • Renew loans on items

The ability to issue holds by title are being handled by an additional feature: UXPROD-1061 Closed

Generated at Fri Feb 09 00:07:31 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.