BE | Extend the requests object to allow for Reading room circulation requests

Description

Overview:

This ticket was generated out of discussions on the 09-22-2024 working group for Reading Room Circulation.

https://folio-org.atlassian.net/wiki/spaces/RA/pages/309821573/2024-08-22+Agenda+and+meeting+notes

As a Staff member i require that the request object collect and retain if the request is a Reading room circulation requests or not. this value will be displayed to users via the UI, filtered on and alter the check-in check-out actions for the item.

In scope:

  • Add a flag to the request object to indicate if it is a Reading room circulation request or not

  • Backfill all current request data to set a default value of the new field to FALSE / “no”

    • No previously generated request should be considered a Reading room circulation request

  • Expose the flag to all relevant API endpoints

  • The field should default to FALSE / No if no value is supplied during request creation.

Permissions:

No extra permissions are needed to edit this field. The already established permissions for View, Edit, Create and Update the requests object should be applied.

Out of scope:

  • Changes to the UI

  • Changes to the Check-in / Check-out action

Questions / Concerns

Todo:

SPIKE:

  • investigate what API endpoints need to be updated
    Backed:

  • Ticket - Add the new field to the request object schema

  • Ticket - update business logic to ensure the field is set to a value of FALSE / no if no value is supplied during creation

  • Ticket - Add a new field to all API endpoints for the request object including and edge APIs.
    Frontend:

Environment

None

Potential Workaround

None

Checklist

hide

Activity

Show:

Details

Assignee

Reporter

Priority

Development Team

Klemming

Release

Trillium (R2 2025)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created March 18, 2025 at 1:12 PM
Updated 8 hours ago
TestRail: Cases
TestRail: Runs