Guidance Checklist¶

‘R’ - Required; ‘D’ - Desired; ‘O’ - Optional

Base checklist¶

	Requirement
R	Hardware
R	Software
R	Skills
R	User account [1] on host server
O	Component restart on reboot, e.g. `cron`’s `@reboot`, `SysV`

See also

	Requirement
R	Read-only site assay database account for `AP-Portal`
R	Determine assays (e.g PatchXpress, QSAR), assay grouping
R	Determine if dose-response data fitting required
R	Determine ion channels, e.g. CaV1.2, hERG
R	Determine CellML models (and the default) to use, e.g. Shannon, ten Tusscher
R	Determine default units, e.g. pIC50, IC50
R	Determine strategies for selecting pIC50 [2] to use
R	SQL [3] to retrieve assay, ion channel, etc., data
R	Details of services, e.g. WSs, which supply additional data
R	IT personnel to implement Java/Spring code

See also

	Requirement
D	Company logo image [7]
D	Company login and logout mechanism [7]
D	Company “contact” information (e.g. local contact emails) [7]
D	X.509 certificates (optional self-signed [4]) for HTTPS
O	IT personnel to implement Java/Spring code [6]
O	Generate and populate usernames and passwords SQL file [5] [7]

Footnotes

[1]	No need for elevated privileges user account on the native filesystem (although need to consider auto-restarting component services or use of TCP ports 80 and 443!).

[2]	Different sites have data of varying characteristics requiring specific actions.

[3]	Assuming that the data is held in an SQL database!

[4]	(1, 2) Use of self-signed certificates generate threatening browser warnings!

[5]	(1, 2) Not “Required” if you’re just trying things out!

[6]	If you wish to restrict access `AP-Portal`

[7]	(1, 2, 3, 4, 5, 6, 7, 8) These operations should take place in `client-shared`.