Versions Compared

Key

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

Submitted

Approved

Status

Status
titleDRAFT

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

...

Drawio
mVer2
zoom1
simple0
inComment0
custContentId10027036
pageId9371656
lbox1
diagramDisplayNameVolaris-Reading-Room-ERD.drawio
contentVer5
revision5
baseUrlhttps://folio-org.atlassian.net/wiki
diagramNameVolaris-Reading-Room-ERD.drawio
pCenter0
width938
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?

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