SOPs

From Wiki

(Difference between revisions)
Jump to: navigation, search
Current revision (17:30, 1 April 2007) (edit) (undo)
 
(31 intermediate revisions not shown.)
Line 1: Line 1:
-
List of our SOPs and Protocols
+
A SOP is a Standard Operation Procedure
-
Patient explorations (SOPs)
+
 
-
Fundus Autofluorescence
+
(notice that a SOP is the node of the SOPs tree and/or the files describing it)
-
Angiography
+
 
-
Optical Coherence Tomography
+
Up to now we prepared the SOPs tree .. please contribute to describe each node)
-
Electrophysiology
+
 
-
Clinical Psychophysics
+
===Description of a SOP===
-
Digital photography
+
To each SOP are associated one or more files (Word, Powerpoint, .html, text, Movies, Photographs, Pictures, etc.)
-
Tissue harvesting and storage
+
describing the SOP.
-
Different species…
+
-
Retina explant preparation
+
These files can be [[Upload your Datafiles|uploaded]] by annny [[EVI-Genoret member]].
-
Different species…
+
 
-
RNA preparation (retina)
+
Sub SOPs can also be associated to a SOP. For that reason we introduce the SOPs tree organisation.
-
Human
+
 
-
Chicken
+
===The SOPs tree organisation===
-
Rat
+
SOPs are organized as a tree. Each SOP has a parent SOP and can contain children SOPs.
-
Mouse (SOP)
+
The root SOP is SOPsList.
-
Pig
+
 
-
Protein preparation (retina)
+
The SOPs tree is a way to organize the SOPs. We decided to choose the Components as main organisation schema.
-
Human
+
 
-
Chicken
+
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 ...
-
Rat
+
 
-
Mouse
+
===Database attributes of SOPs===
-
Pig
+
Each SOP has
-
Cell cultures
+
* a [[SopCode]] (one word without blank)
-
Primary culture (…)
+
* a [[SopTitle]] (not to long, maximum 255 characters)
-
….
+
* a [[SopDescription]] (text who describes briefly the purpose of this SOP)
-
Functional Assays
+
* a parent SOP
-
Immunohistochemistry
+
and it is '''precisely decribed through'''
-
Cell viability
+
* associated [[HttpLink]]s (internal or external)
-
Gene silencing
+
* 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"

Retrieved from "http://php5/WikiGenoret/index.php/SOPs"