Page Properties | ||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
As described in prod ticket:
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
...
Drawio | ||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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
Should the Security Officer log access on a patron entering and exiting events or only on entering the room?
Can we use
user-type
for distinguishing Security Officer and Librarian roles?