Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Page Properties

Submitted

Approved

Status

Status
colourBlue
titleDRAFTdone

Impact

Status
colourBlue
titlemedium

Arch Ticket

Jira Legacy
serverSystem JIRAJira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyARCH-177

Prod ticket

Jira Legacy
serverSystem JIRAJira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-4070

...

As described in prod ticket:

Jira Legacy
serverSystem JIRAJira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-4070

...

  • Security:

    • The solution should allow permission-based access to reading rooms for patrons

    • The solution should allow read-only access to patron records for security officers

  • ModifiabilityExtensibility:

    • The solution should allow extending the room access feature’s capability with additional funcfunctionality

  • Maintainability:

    • The solution should be independent and loosely coupled as the FOLIO core modules do not include the feature.

...

Solution

Description

Pros

Cons

Decision

1

Reuse existing service points mechanism to serve as a reading room

  • Does not require a new module introduction

  • Adding unrelated responsibility to the existing entity of service point

Declined

2

Introduce a separate entity of for the reading room

  • Requires new module introduction

Target Solution

...

FOLIO should provide the capability to allow access to individual reading rooms for a patron. Patron records can be represented in user records with Patron or Staff user type

Drawio
mVer2
zoom1
simple0
inComment0
custContentId9338955
pageId9371656
lbox1
diagramDisplayNameVolaris-Reading-Room-Access-Context.drawio
contentVer3
revision3
baseUrlhttps://folio-org.atlassian.net/wiki
diagramNameUntitled Diagram-1707198206060.drawio
pCenter0
width1051
links
tbstyle
height471

...

Drawio
mVer2
zoom1
simple0
inComment0
custContentId10027036
pageId9371656
lbox1
diagramDisplayNameVolaris-Reading-Room-ERD.drawio
contentVer56
revision56
baseUrlhttps://folio-org.atlassian.net/wiki
diagramNameVolaris-Reading-Room-ERD.drawio
pCenter0
width9381042
links
tbstyle
height457

Permissions

The solution requires the creation/extension of the following roles:

  • Security Officer. Allowed actions:

    • View patron permissions for reading room access

    • View/Create/Update “allowed” and “denied” events for access log

  • Librarian.

    • View/Create/Update/Delete patron permissions for reading room access

    • View/Create/Update “allowed” and “denied” events for access log

    • View/Create/Update/Delete relation between Reading Room and Service Points

For LoC the creation/modification of roles should be implemented through Roles & Capabilities

For tenants with OKAPI, the related permissionSets should be created in FOLIO.

Eureka Support

The new modules included in the solution should support the “application” approach for LoC

Questions

  1. Should the Security Officer log access on a patron entering and exiting events or only on entering the room?

    1. >> Just entering. Also, LoC will not be collecting gate counts.

  2. Can we use user-type for distinguishing Security Officer and Librarian roles?

    1. No, use permissions or Eureka roles for the purpose.