SOPs
From Wiki
(Difference between revisions)
Line 15: | Line 15: | ||
a parent SOP | a parent SOP | ||
and it is precisely decribed through | and it is precisely decribed through | ||
- | associated | + | associated [[HttpLink]]s (internal or external) |
- | associated | + | associated [[DataFile]]s within the Genoret Database |
each associated link or file as an owner and a description | each associated link or file as an owner and a description | ||
see [[SopHttpLink]] and [[SopDataFile]] | see [[SopHttpLink]] and [[SopDataFile]] |
Revision as of 18:21, 13 December 2005
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) 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