SOPs
From Wiki
(Difference between revisions)
| Line 18: | Line 18: | ||
a [[WorkGroup]] (several EVI-Genoret members directly concerned by this SOP) | a [[WorkGroup]] (several EVI-Genoret members directly concerned by this SOP) | ||
a parent SOP | a parent SOP | ||
| - | and it is precisely decribed through | + | and it is '''precisely decribed through''' |
associated [[HttpLink]]s (internal or external) | associated [[HttpLink]]s (internal or external) | ||
associated [[Datafile]]s within the Genoret Database | associated [[Datafile]]s within the Genoret Database | ||
Revision as of 18:43, 20 March 2006
See the hierarchical tree of SOPs "Genoret SOPs"
This page explains what is a SOP and how Editors, Examiners and Approvals manage them.
Each SOP has a parent SOP. SOPs are organized as a tree. This means that a SOP can contain other SOPs. The root SOP is SOPsList.
Normally a SOP has one or more Datafiles (.doc or .PDF .html or .txt) describing it.
Each SOP has
a SopCode (one word without blank) a SopTitle (not to long, maximum 255 characters) a SopDescription (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
and it is precisely decribed through
associated HttpLinks (internal or external) associated Datafiles within the Genoret Database
