PROTOCOL
A protocol is a template. It defines a test. Change the protocol, and every test defined by it changes with it.
TEST
A test is a single instance of a template.
WHAT IS CHANGING?
Protocols have always existed in the software. Hans has been defining them in code. We just haven't named them or separated them.
The Shift: Instead of hard-coding a protocol, an Admin defines it in a Protocol Editor. The protocol is saved as a JSON file. When a test runs, software now reads that JSON. Same concept - now a protocol is visible, editable, out of the code, and has a much faster turn-around time.
For labs who prefer not to manage Protocols themselves, we can define them in-house and ship them. The protocol files are small. To do this, we must provide an easy way for Admin to load the protocol into the database. Once loaded, it's accessible to both User and Admin
THREE PERSPECTIVES
Given this, we will have three perspectives in the software: USER, POWER ADMIN and CASUAL ADMIN. You can explore what is visible to each type of user. Menu items that do nothing are marked with an asterisk. Use RETURN - HOME to return here.
The POWER ADMIN (glass theme) can:
- define protocols via protocol editors
- run tests
- add, delete modify lab equipment
- modify users and user settings
- modify her own personal settings
The CASUAL ADMIN (mist theme) can:
- load protocols we define and ship
- run tests
- add, delete modify lab equipment
- modify users and user settings
- modify her personal settings