Description
This interface provides access to view the repository data. It also provides an interface to close workitems and merge ukrdcids which will be expanded to support all error correction work. Finally it provides a way of searching for errors for facilities, NHS number and files this will alos be expanded to provide more comprehensive error information/views.The Purpose of the UKRDC Web User Interface is to be able to interact with the UKRDC database's depending which instance of the Web UI you are accessing (live, staging or dev). You can interact with Work Items, view file loading errors and view patient data.
Please read UKRDC-Web-User-Interface for more information about interacting with the User Interface.
Code design and Description
There are two separate codebases - frontend and backend.
Backend - The application is split into two parts:
- The Server side code:
- Repository: User-API
- Python django app, using django rest framework. There is only one special thing about it is that we add ukrdc_session and jtrace_session to request object. Both of them commit/rollback after request is finished. UKRDC3 and JTRACE settings are defined in the settings module and appropriate environment file (staging.py for staging, development.py for dev, etc.)
...
- The Client side code:
- Repository: User-Client
- Angular app. Having several modules - viewer, errorbrowser... Workitems module is in the main app, but should be split into separate module.
Code base
https://bitbucket.renalregistry.nhs.uk/projects/TNG/repos/user-client/browse
https://bitbucket.renalregistry.nhs.uk/projects/TNG/repos/user-api/browse TODO: Expand on how the both code bases work.