SOPs
From Wiki
(Difference between revisions)
| Line 1: | Line 1: | ||
| - | + | See the hierarchical tree of SOPs [http://www-genoret.u-strasbg.fr/genoret/ "Genoret SOPs"] | |
This page explains what is a SOP and how Editors, Examiners and Approvals manage them. | 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. The root SOP is SOPsList. | + | 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 | Each SOP has | ||
Revision as of 18:39, 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
