SOPs
From Wiki
(Difference between revisions)
| Line 7: | Line 7: | ||
Each SOP has | Each SOP has | ||
a [[SopCode]] (one word without blank) | a [[SopCode]] (one word without blank) | ||
| - | a [[SopTitle]] (not to long) | + | a [[SopTitle]] (not to long, maximum 255 characters) |
a SopDescription (text who describes briefly the purpose of this SOP) | a SopDescription (text who describes briefly the purpose of this SOP) | ||
an [[Editor]] (one or more EVI-Genoret members) | an [[Editor]] (one or more EVI-Genoret members) | ||
Revision as of 10:20, 20 January 2006
For the "official" web site see "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. The root SOP is SOPsList.
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
each associated link or file as an owner and a description
see SopHttpLink and SopDataFile
