SOPs

From Wiki

(Difference between revisions)
Jump to: navigation, search
Current revision (17:30, 1 April 2007) (edit) (undo)
 
(11 intermediate revisions not shown.)
Line 1: Line 1:
-
See the hierarchical tree of SOPs [http://www-genoret.u-strasbg.fr/genoret/Project/phrame.php?action=doShowMainSopList "Genoret SOPs"]
+
A SOP is a Standard Operation Procedure
-
This page explains what is a SOP and how Editors, Examiners and Approvals manage them.
+
(notice that a SOP is the node of the SOPs tree and/or the files describing it)
-
Each SOP has a parent SOP. SOPs are organized as a tree. This means that a SOP can contain other SOPs.
+
Up to now we prepared the SOPs tree .. please contribute to describe each node)
 +
 
 +
===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 [[Upload your Datafiles|uploaded]] by annny [[EVI-Genoret member]].
 +
 
 +
Sub SOPs can also be associated to a SOP. 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.
The root SOP is SOPsList.
-
Normally a SOP has one or more Datafiles (.doc or .PDF .html or .txt) describing it.
+
The SOPs tree is a way to organize the SOPs. We decided to choose the Components as main organisation schema.
 +
Some foreseen directories are still empty. To visualize the availability of the existing SOPs we colorize the SOPs tree according to "full implemented", "empty" and "some, but not all, nodes are missing". Please, upload soon ...
 +
===Database attributes of SOPs===
Each SOP has
Each SOP has
-
a [[SopCode]] (one word without blank)
+
* a [[SopCode]] (one word without blank)
-
a [[SopTitle]] (not to long, maximum 255 characters)
+
* 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)
+
* a parent SOP
-
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'''
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
 +
 
 +
===Links===
 +
See the hierarchical tree of SOPs [http://www-genoret.u-strasbg.fr/genoret/Project/phrame.php?action=doShowMainSopList "Genoret SOPs"]

Current revision

A SOP is a Standard Operation Procedure

(notice that a SOP is the node of the SOPs tree and/or the files describing it)

Up to now we prepared the SOPs tree .. please contribute to describe each node)

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 annny EVI-Genoret member.

Sub SOPs can also be associated to a SOP. 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.

The SOPs tree is a way to organize the SOPs. We decided to choose the Components as main organisation schema.

Some foreseen directories are still empty. To visualize the availability of the existing SOPs we colorize the SOPs tree according to "full implemented", "empty" and "some, but not all, nodes are missing". Please, upload soon ...

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

  • associated HttpLinks (internal or external)
  • associated Datafiles within the Genoret Database

Links

See the hierarchical tree of SOPs "Genoret SOPs"

Personal tools