Contents
Related Help Documents
- Procedural Details Batch Procedure: Describes how to enter procedural details into the database form multiple procedures.
- Experiment Annotation: Information about the tools available in the database to annotate experiments.
A Protocol has a
| Name: The name should be unique and max. 120 characters long. | |
| Protocol Number: A number unique to a protocol. Used by the database and not accessible to users. | |
| Description: The description of the protocol. This should be plain text (that can be formatted) and max. 4000 characters long. A protocol must contain a description to be accepted by the database. | |
| URI: Optional web-address of the protocol if available. | |
| Procedure: A protocol must be associated to a procedure existing in PUMAdb (see Procedures for a list of the available Procedures). | |
| Owner: The userid of the owner of the protocol. | |
A protocol can be either edited or cloned. During 'cloning', a second protocol is created based on a previously existing one. The new protocol must have a new, unique name to be accepted by the database. No new protocol is created during 'editing', but an already existing protocol is modified.
Only the owner of the protocol can 'edit' the protocol and only if no other user associated experiments to the protocol. If such a shared protocol needs to be modified, please contact the curators at: array@princeton.edu, they can do this for you. If a user can see the protocol (s)he can also clone it.
A protocol can be edited/cloned after selecting the appropriate 'edit' icon on the list of available Protocols. The same constraints as the ones listed above apply: the resulting protocol name has to be unique; description, userid, name are all required; the length of the fields should be less than the allowed limit.