SOPs
From Wiki
(Difference between revisions)
| Line 10: | Line 10: | ||
To a SOP can also be associated other SOPs. For that reason we introduce the SOPs tree organisation. | To a SOP can also be associated other SOPs. For that reason we introduce the SOPs tree organisation. | ||
| - | |||
===The SOPs tree organisation=== | ===The SOPs tree organisation=== | ||
| Line 16: | Line 15: | ||
The root SOP is SOPsList. | The root SOP is SOPsList. | ||
| - | ===Database attributes of SOPs | + | ===Database attributes of SOPs=== |
Each SOP has | Each SOP has | ||
* a [[SopCode]] (one word without blank) | * a [[SopCode]] (one word without blank) | ||
Revision as of 20:11, 24 January 2007
A SOP is a Standard Operation Procedure
(notice that a SOP is the node of the SOPs tree and/or the files describing it)
Contents |
Description of a SOP
To each SOP are associated one or more files (Word, Powerpoint, .html, text, Movies, Photographs, Pictures, etc.) describing the SOP.
These files can be uploaded by the Genoret Members.
To a SOP can also be associated other SOPs. For that reason we introduce the SOPs tree organisation.
The SOPs tree organisation
SOPs are organized as a tree. Each SOP has a parent SOP and can contain children SOPs. The root SOP is SOPsList.
Database attributes of SOPs
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)
- a parent SOP
and it is precisely decribed through
Links
See the hierarchical tree of SOPs "Genoret SOPs"
