SOPs
From Wiki
(Difference between revisions)
Line 18: | Line 18: | ||
associated http links (internal or external) | associated http links (internal or external) | ||
associated data files within the Genoret Database | associated data files within the Genoret Database | ||
+ | each associated link or file as an owner and a description | ||
+ | see [[SopHttpLink]] and [[SopDataFile]] |
Revision as of 12:48, 15 November 2005
For the "official" web site see "Genoret SOPs"
This page explains what is a SOP and how editors, examiners and approval manage them.
SOPs are organized as a tree. Each SOP has a parent SOP. The root SOP is SOPsList.
Each SOP has
a SopCode (one word without blank) a Title (not to long) a Description (text who describes briefly the purpose of this SOP) an Editor (one or more EVI-Genoret members) an Examiner (one or more EVI-Genoret members) an Approval (one or more EVI-Genoret members) a WorkGroup (several EVI-Genoret members directly concerned by this SOP) a Parent SOP
it is precisely decribed through
associated http links (internal or external) associated data files within the Genoret Database
each associated link or file as an owner and a description
see SopHttpLink and SopDataFile