SOPs

From Wiki

(Difference between revisions)
Jump to: navigation, search
Line 16: Line 16:
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
-
each associated link or file as an owner and a description
+
-
see [[SopHttpLink]] and [[SopDataFile]]
+

Revision as of 18:34, 20 March 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
Personal tools