Introduce DCB Admin For Libraries

Description

Background

DCB Admin is currently available for consortium users only. However, several libraries have already requested access to DCB Admin to manage their library’s DCB experience, and many library users could benefit from this ability.

DCB Admin currently does not suit the needs of library users, as it has been designed around the consortium use case and all views are from the consortium user perspective. This means there is a great deal of data that a library staff user would have to be prevented from seeing, and an equally large surface through which sensitive data could inadvertently be accessed by said user (i.e. other libraries' requests). Furthermore, the information and actions that are most relevant for a library user are not prioritised within DCB Admin at present, and there is no way to do this without compromising the consortium user experience.

As such, a completely different experience is required, and in order to best meet the requirements of both groups we have decided to split DCB Admin into two separate applications. One will be the existing application, which can now be thought of as “DCB Admin for Consortia”. The second will be a new application, which will be named “DCB Admin for Libraries” and be solely focused upon library management within DCB.

The context of this ticket is the work required to deliver a first release and deployment ‘v1’ of DCB Admin for Libraries.

Requirements

We must establish two separate applications / zones for both libraries and consortia. This will ensure each application only has what it needs, and no more.
Library users must not have access to information from other libraries, and must only have the most relevant information.

Please see the DCB Admin For Libraries document for more information on requirements, goals, UX, and other considerations.

Individual Pieces of work

Split DCB Admin into separate applications for Libraries and Consortia.
- The “Consortia” app may stay on Next.js, but the ‘Libraries’ app must use a framework compatible with micro frontends - so not Next.js
Introduce staff requesting for libraries, where library staff can make proxy requests on behalf of their patrons only - as opposed to the current consortium-level implementation.
Re-design the individual library page as a “home page” for library users.
Automatically direct users to their individual library page upon login - this requires information about a user’s library (its UUID and name) to be held in their Keycloak account in a way that DCB Admin can access.
Implement the data change log for individual libraries, so library users only see changes for their library.
Implement “DCB Service Status” for a library.
Create a test deployment and any associated infrastructure for DCB Admin for Libraries deployments.
- i.e. Vercel project, GitLab project/pipelines, custom domains
Lock down filtering throughout the application to ensure library users can’t use it to see data from other libraries.

Future considerations