Purpose:

This user story facilitates the verification of patron access to the reading room, ensuring that staff users can efficiently manage and track patron privileges and access permissions.

Story:

• As a Security Officer or Reader Registration librarian,

• I want to verify whether a user is allowed to access the reading room,

• So that I can track patron access according to patron privileges.

Acceptance criteria:

1. Upon launching the ‘Reading Room Access’ app, users are directed to the initial 'Scan Patron Card' page.

2. For displaying profile pictures in the ‘Reading Room Access’ app, include the atomic permission ‘users.profile-picture.item.get’ in sub-permissions of permission “Reading room access: In app - track access”

3. The 'Scan Patron Card' page provides users with the ability to scan a patron card, enter a patron barcode manually, or perform a patron lookup as per the UI prototype.

4. When a staff user enters patron, parton details and access status are displayed on the ‘Scan patron card’ page.

5. Staff users can allow or deny access to the patron.

6. The system records actions for reading room usage, including patron details, staff information (indicating who granted or denied patron access), room name, date, and timestamp.

Scenarios:

• Scenario 1: Redirect to Scan Patron Card page

  • Given: Staff user has ‘Reading room access: In app - track access’ permission,  

  • When: User opens the 'Reading Room Access' app,

  • Then: The user is redirected to the 'Scan Patron Card' page.

• Scenario 2: Validate Functionality of Scan Patron Card page

  • Given: Staff user has ‘Reading room access: In app - track access’ permission  and has opened the 'Reading Room Access' app,

  • When: User interacts with the 'Scan Patron Card' page,

  • Then: User has the ability to enter a patron barcode or perform a patron lookup.

• Scenario 3: Verify Details of Patron with Allowed Access

  • Given: Staff User with ‘Reading room access: In app - track access’ permission  navigated to  Reading Room Access > Scan patron card

    • And Patron has access to the selected reading room (associated through service point)

  • When: Staff user enters Patron barcode

  • Then: Allow access, Deny access, and Cancel actions are available for the Staff user

    • And system displays Patron details following the UI Prototype:

      • User's name,

      • User's barcode,

      • Expiration date,

      • Reading room access status (e.g. “Allow access”)

      • Reading room access note if present.

Open

• Scenario 4: Verify Details of Patron with Denied Access

  • Given: Staff User with ‘Reading room access: In app - track access’ permission  navigated to  Reading Room Access > Scan patron card

    • And Patron does not have access to the selected reading room (associated through service point)

  • When: Staff user enters Patron barcode

  • Then: Staff can’t allow access to the patron (the button is disabled), only Deny access and Cancel actions are available

    • And system displayed Patron details following the UI Prototype:

      • User's name,

      • User's barcode,

      • Expiration date,

      • Reading room access status (e.g. “Deny access”)

      • Reading room access note if present.

Open

• Scenario 5: Allow /Deny Access to the Patron

  • Given:  Patron details and access status are displayed on the ‘Scan patron card’ page

  • When: Staff user grants (or denies patron access)

  • Then: System clears patron details on the screen (initial 'Scan patron card' page should be displayed)

    • And system stores the following details in the log:

      • current datetime

      • patron ID,

      • reading room ID,

      • user ID,

      • action (allowed/denied)

Open

• Scenario 6: Cancel

• Given:  Patron details and access status are displayed on the ‘Scan patron card’ page

• When: Staff user clicks on Cancel

• Then: System does not store any details in the log

Addition note:

• UI Prototype

• Reading room access app icon

Note: Manual QA effort is 2 SP.