[Bio] / Sprout / SproutDBD.xml Repository:
ViewVC logotype

Annotation of /Sprout/SproutDBD.xml

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.36 - (view) (download) (as text)

1 : parrello 1.1 <?xml version="1.0" encoding="utf-8" ?>
2 :     <Database>
3 :     <Title>Sprout Genome and Subsystem Database</Title>
4 :     <Entities>
5 :     <Entity name="Genome" keyType="name-string">
6 :     <Notes>A [i]genome[/i] contains the sequence data for a particular individual organism.</Notes>
7 :     <Fields>
8 :     <Field name="genus" type="name-string">
9 :     <Notes>Genus of the relevant organism.</Notes>
10 :     <DataGen pass="1">RandParam('streptococcus', 'staphyloccocus', 'felis', 'homo', 'ficticio', 'strangera', 'escherischia', 'carborunda')</DataGen>
11 :     </Field>
12 :     <Field name="species" type="name-string">
13 : parrello 1.8 <Notes>Species of the relevant organism.</Notes>
14 : parrello 1.1 <DataGen pass="1">StringGen('PKVKVKVKVKV')</DataGen>
15 : parrello 1.8 </Field>
16 : parrello 1.1 <Field name="unique-characterization" type="medium-string">
17 : parrello 1.8 <Notes>The unique characterization identifies the particular organism instance from which the
18 :     genome is taken. It is possible to have in the database more than one genome for a
19 : parrello 1.1 particular species, and every individual organism has variations in its DNA.</Notes>
20 : parrello 1.8 <DataGen>StringGen('PKVKVK999')</DataGen>
21 : parrello 1.1 </Field>
22 :     <Field name="access-code" type="key-string">
23 : parrello 1.8 <Notes>The access code determines which users can look at the data relating to this genome.
24 :     Each user is associated with a set of access codes. In order to view a genome, one of
25 :     the user's access codes must match this value.</Notes>
26 :     <DataGen>RandParam('low','medium','high')</DataGen>
27 :     </Field>
28 : parrello 1.15 <Field name="complete" type="boolean">
29 :     <Notes>TRUE if the genome is complete, else FALSE</Notes>
30 :     </Field>
31 : parrello 1.8 <Field name="taxonomy" type="text">
32 :     <Notes>The taxonomy string contains the full taxonomy of the organism, while individual elements
33 :     separated by semi-colons (and optional white space), starting with the domain and ending with
34 :     the disambiguated genus and species (which is the organism's scientific name plus an
35 :     identifying string).</Notes>
36 :     <DataGen pass="2">join('; ', (RandParam('bacteria', 'archaea', 'eukaryote', 'virus', 'environmental'),
37 :     ListGen('PKVKVKVK', 5), $this->{genus}, $this->{species}))</DataGen>
38 :     </Field>
39 :     <Field name="group-name" type="name-string" relation="GenomeGroups">
40 :     <Notes>The group identifies a special grouping of organisms that would be displayed on a particular
41 :     page or of particular interest to a research group or web site. A single genome can belong to multiple
42 :     such groups or none at all.</Notes>
43 :     </Field>
44 : parrello 1.1 </Fields>
45 :     <Indexes>
46 :     <Index>
47 :     <Notes>This index allows the applications to find all genomes associated with
48 :     a specific access code, so that a complete list of the genomes users can view
49 :     may be generated.</Notes>
50 :     <IndexFields>
51 :     <IndexField name="access-code" order="ascending" />
52 :     <IndexField name="genus" order="ascending" />
53 :     <IndexField name="species" order="ascending" />
54 :     <IndexField name="unique-characterization" order="ascending" />
55 :     </IndexFields>
56 :     </Index>
57 :     <Index Unique="false">
58 :     <Notes>This index allows the applications to find all genomes for a particular
59 :     species.</Notes>
60 :     <IndexFields>
61 :     <IndexField name="genus" order="ascending" />
62 :     <IndexField name="species" order="ascending" />
63 :     <IndexField name="unique-characterization" order="ascending" />
64 :     </IndexFields>
65 :     </Index>
66 :     </Indexes>
67 :     </Entity>
68 :     <Entity name="Source" keyType="medium-string">
69 :     <Notes>A [i]source[/i] describes a place from which genome data was taken. This can be an organization
70 :     or a paper citation.</Notes>
71 :     <Fields>
72 :     <Field name="URL" type="string" relation="SourceURL">
73 : parrello 1.8 <Notes>URL the paper cited or of the organization's web site. This field optional.</Notes>
74 :     <DataGen>"http://www.conservativecat.com/Ferdy/TestTarget.php?Source=" . $this->{id}</DataGen>
75 :     </Field>
76 : parrello 1.1 <Field name="description" type="text">
77 : parrello 1.8 <Notes>Description the source. The description can be a street address or a citation.</Notes>
78 :     <DataGen>$this->{id} . ': ' . StringGen(IntGen(50,200))</DataGen>
79 :     </Field>
80 : parrello 1.1 </Fields>
81 :     </Entity>
82 :     <Entity name="Contig" keyType="name-string">
83 :     <Notes>A [i]contig[/i] is a contiguous run of residues. The contig's ID consists of the
84 :     genome ID followed by a name that identifies which contig this is for the parent genome. As
85 :     is the case with all keys in this database, the individual components are separated by a
86 :     period.
87 :     [p]A contig can contain over a million residues. For performance reasons, therefore,
88 :     the contig is split into multiple pieces called [i]sequences[/i]. The sequences
89 :     contain the characters that represent the residues as well as data on the quality of
90 :     the residue identification.</Notes>
91 :     </Entity>
92 :     <Entity name="Sequence" keyType="name-string">
93 :     <Notes>A [i]sequence[/i] is a continuous piece of a [i]contig[/i]. Contigs are split into
94 :     sequences so that we don't have to have the entire contig in memory when we are
95 :     manipulating it. The key of the sequence is the contig ID followed by the index of
96 :     the begin point.</Notes>
97 :     <Fields>
98 :     <Field name="sequence" type="text">
99 : parrello 1.8 <Notes>String consisting of the residues. Each residue is described by a single
100 :     character in the string.</Notes>
101 :     <DataGen>RandChars("ACGT", IntGen(100,400))</DataGen>
102 :     </Field>
103 : parrello 1.1 <Field name="quality-vector" type="text">
104 : parrello 1.9 <Notes>String describing the quality data for each base pair. Individual values will
105 : parrello 1.8 be separated by periods. The value represents negative exponent of the probability
106 :     of error. Thus, for example, a quality of 30 indicates the probability of error is
107 :     10^-30. A higher quality number a better chance of a correct match. It is possible
108 : parrello 1.9 that the quality data is not known for a sequence. If that is the case, the quality
109 : parrello 1.8 vector will contain the [b]unknown[/b].</Notes>
110 :     <DataGen>unknown</DataGen>
111 :     </Field>
112 : parrello 1.1 </Fields>
113 :     </Entity>
114 : parrello 1.25 <Entity name="Feature" keyType="id-string">
115 : parrello 1.1 <Notes>A [i]feature[/i] is a part of a genome that is of special interest. Features
116 :     may be spread across multiple contigs of a genome, but never across more than
117 :     one genome. Features can be assigned to roles via spreadsheet cells,
118 :     and are the targets of annotation.</Notes>
119 :     <Fields>
120 :     <Field name="feature-type" type="string">
121 : parrello 1.8 <Notes>Code indicating the type of this feature.</Notes>
122 :     <DataGen>RandParam('peg','rna')</DataGen>
123 :     </Field>
124 : parrello 1.14 <Field name="alias" type="medium-string" relation="FeatureAlias">
125 : parrello 1.9 <Notes>Alternative name for this feature. A feature can have many aliases.</Notes>
126 : parrello 1.8 <DataGen testCount="3">StringGen('Pgi|99999', 'Puni|XXXXXX', 'PAAAAAA999')</DataGen>
127 :     </Field>
128 : parrello 1.1 <Field name="translation" type="text" relation="FeatureTranslation">
129 : parrello 1.8 <Notes>[i](optional)[/i] A translation of this feature's residues into character
130 :     codes, formed by concatenating the pieces of the feature together. For a
131 :     protein encoding group, this is the protein characters. For other types
132 :     it is the DNA characters.</Notes>
133 :     <DataGen testCount="0"></DataGen>
134 :     </Field>
135 : parrello 1.1 <Field name="upstream-sequence" type="text" relation="FeatureUpstream">
136 : parrello 1.8 <Notes>Upstream sequence the feature. This includes residues preceding the feature as well as some of
137 :     the feature's initial residues.</Notes>
138 :     <DataGen testCount="0"></DataGen>
139 :     </Field>
140 : parrello 1.1 <Field name="active" type="boolean">
141 : parrello 1.11 <Notes>TRUE if this feature is still considered valid, FALSE if it has been logically deleted.</Notes>
142 : parrello 1.8 <DataGen>1</DataGen>
143 :     </Field>
144 : parrello 1.36 <Field name="assignment" type="text">
145 :     <Notes>This is the primary functional assignment for the feature.</Notes>
146 :     </Field>
147 : parrello 1.8 <Field name="link" type="text" relation="FeatureLink">
148 :     <Notes>Web hyperlink for this feature. A feature have no hyperlinks or it can have many. The
149 :     links are to other websites that have useful about the gene that the feature represents, and
150 :     are coded as raw HTML, using [b]&lt;a href="[i]link[/i]"&gt;[i]text[/i]&lt;/a&gt;[/b] notation.</Notes>
151 :     <DataGen testCount="3">'http://www.conservativecat.com/Ferdy/TestTarget.php?Source=' . $this->{id} .
152 :     "&amp;Number=" . IntGen(1,99)</DataGen>
153 :     </Field>
154 : parrello 1.1 </Fields>
155 : parrello 1.8 <Indexes>
156 :     <Index>
157 :     <Notes>This index allows the user to find the feature corresponding to
158 :     the specified alias name.</Notes>
159 :     <IndexFields>
160 :     <IndexField name="alias" order="ascending" />
161 :     </IndexFields>
162 :     </Index>
163 :     </Indexes>
164 : parrello 1.1 </Entity>
165 : parrello 1.27 <Entity name="SynonymGroup" keyType="id-string">
166 :     <Notes>A [i]synonym group[/i] represents a group of features. Substantially identical features
167 :     are mapped to the same synonym group, and this information is used to expand similarities.</Notes>
168 :     </Entity>
169 : parrello 1.1 <Entity name="Role" keyType="string">
170 :     <Notes>A [i]role[/i] describes a biological function that may be fulfilled by a feature.
171 :     One of the main goals of the database is to record the roles of the various features.</Notes>
172 : parrello 1.8 <Fields>
173 : parrello 1.18 <Field name="EC" type="string" relation="RoleEC">
174 :     <Notes>EC code for this role.</Notes>
175 : parrello 1.8 <DataGen testCount="1">StringGen(IntGen(20,40)) . "(" . $this->{id} . ")"</DataGen>
176 :     </Field>
177 : parrello 1.15 <Field name="abbr" type="name-string">
178 :     <Notes>Abbreviated name for the role, generally non-unique, but useful
179 :     in column headings for HTML tables.</Notes>
180 :     </Field>
181 : parrello 1.8 </Fields>
182 : parrello 1.18 <Indexes>
183 :     <Index>
184 :     <Notes>This index allows the user to find the role corresponding to
185 :     an EC number.</Notes>
186 :     <IndexFields>
187 :     <IndexField name="EC" order="ascending" />
188 :     </IndexFields>
189 :     </Index>
190 :     </Indexes>
191 : parrello 1.1 </Entity>
192 :     <Entity name="Annotation" keyType="name-string">
193 :     <Notes>An [i]annotation[/i] contains supplementary information about a feature. Annotations
194 : parrello 1.8 are currently the only objects that may be inserted directly into the database. All other
195 : parrello 1.24 information is loaded from data exported by the SEED.</Notes>
196 : parrello 1.8 <Fields>
197 :     <Field name="time" type="date">
198 :     <Notes>Date and time of the annotation.</Notes>
199 :     </Field>
200 :     <Field name="annotation" type="text">
201 :     <Notes>Text of the annotation.</Notes>
202 :     </Field>
203 : parrello 1.1 </Fields>
204 : parrello 1.26 <Indexes>
205 :     <Index>
206 :     <Notes>This index allows the user to find recent annotations.</Notes>
207 :     <IndexFields>
208 :     <IndexField name="time" order="descending" />
209 :     </IndexFields>
210 :     </Index>
211 :     </Indexes>
212 : parrello 1.1 </Entity>
213 : parrello 1.15 <Entity name="Reaction" keyType="key-string">
214 :     <Notes>A [i]reaction[/i] is a chemical process catalyzed by a protein. The reaction ID
215 :     is generally a small number preceded by a letter.</Notes>
216 :     <Fields>
217 :     <Field name="url" type="string" relation="ReactionURL">
218 :     <Notes>HTML string containing a link to a web location that describes the
219 :     reaction. This field is optional.</Notes>
220 :     </Field>
221 :     <Field name="rev" type="boolean">
222 :     <Notes>TRUE if this reaction is reversible, else FALSE</Notes>
223 :     </Field>
224 :     </Fields>
225 :     </Entity>
226 :     <Entity name="Compound" keyType="name-string">
227 :     <Notes>A [i]compound[/i] is a chemical that participates in a reaction.
228 :     All compounds have a unique ID and may also have one or more names.</Notes>
229 :     <Fields>
230 :     <Field name="name-priority" type="int" relation="CompoundName">
231 :     <Notes>Priority of a compound name. The name with the loweset
232 :     priority is the main name of this compound.</Notes>
233 :     </Field>
234 :     <Field name="name" type="name-string" relation="CompoundName">
235 :     <Notes>Descriptive name for the compound. A compound may
236 :     have several names.</Notes>
237 :     </Field>
238 :     <Field name="cas-id" type="name-string" relation="CompoundCAS">
239 :     <Notes>Chemical Abstract Service ID for this compound (optional).</Notes>
240 :     </Field>
241 : parrello 1.19 <Field name="label" type="name-string">
242 :     <Notes>Name used in reaction display strings.
243 :     It is the same as the name possessing a priority of 1, but it is placed
244 :     here to speed up the query used to create the display strings.</Notes>
245 :     </Field>
246 : parrello 1.15 </Fields>
247 :     <Indexes>
248 :     <Index>
249 :     <Notes>This index allows the user to find the compound corresponding to
250 :     the specified name.</Notes>
251 :     <IndexFields>
252 :     <IndexField name="name" order="ascending" />
253 :     </IndexFields>
254 :     </Index>
255 :     <Index>
256 : parrello 1.17 <Notes>This index allows the user to find the compound corresponding to
257 :     the specified CAS ID.</Notes>
258 :     <IndexFields>
259 :     <IndexField name="cas-id" order="ascending" />
260 :     </IndexFields>
261 :     </Index>
262 :     <Index>
263 : parrello 1.15 <Notes>This index allows the user to access the compound names in
264 :     priority order.</Notes>
265 :     <IndexFields>
266 :     <IndexField name="id" order="ascending" />
267 :     <IndexField name="name-priority" order="ascending" />
268 :     </IndexFields>
269 :     </Index>
270 :     </Indexes>
271 :     </Entity>
272 : parrello 1.5 <Entity name="Subsystem" keyType="string">
273 : parrello 1.1 <Notes>A [i]subsystem[/i] is a collection of roles that work together in a cell. Identification of subsystems
274 :     is an important tool for recognizing parallel genetic features in different organisms.</Notes>
275 : parrello 1.15 <Fields>
276 :     <Field name="curator" type="string">
277 :     <Notes>Name of the person currently in charge of the subsystem.</Notes>
278 :     </Field>
279 :     <Field name="notes" type="text">
280 :     <Notes>Descriptive notes about the subsystem.</Notes>
281 :     </Field>
282 : parrello 1.28 <Field name="classification" type="string" relation="SubsystemClass">
283 :     <Notes>General classification data about the subsystem.</Notes>
284 :     </Field>
285 : parrello 1.15 </Fields>
286 :     </Entity>
287 :     <Entity name="RoleSubset" keyType="string">
288 :     <Notes>A [i]role subset[/i] is a named collection of roles in a particular subsystem. The
289 :     subset names are generally very short, non-unique strings. The ID of the parent
290 :     subsystem is prefixed to the subset ID in order to make it unique.</Notes>
291 :     </Entity>
292 :     <Entity name="GenomeSubset" keyType="string">
293 :     <Notes>A [i]genome subset[/i] is a named collection of genomes that participate
294 :     in a particular subsystem. The subset names are generally very short, non-unique
295 :     strings. The ID of the parent subsystem is prefixed to the subset ID in order
296 :     to make it unique.</Notes>
297 : parrello 1.1 </Entity>
298 : parrello 1.24 <Entity name="SSCell" keyType="hash-string">
299 : parrello 1.1 <Notes>Part of the process of locating and assigning features is creating a spreadsheet of
300 :     genomes and roles to which features are assigned. A [i]spreadsheet cell[/i] represents one
301 :     of the positions on the spreadsheet.</Notes>
302 :     </Entity>
303 :     <Entity name="SproutUser" keyType="name-string">
304 :     <Notes>A [i]user[/i] is a person who can make annotations and view data in the database. The
305 :     user object is keyed on the user's login name.</Notes>
306 :     <Fields>
307 : parrello 1.8 <Field name="description" type="string">
308 :     <Notes>Full name or description of this user.</Notes>
309 :     </Field>
310 : parrello 1.1 <Field name="access-code" type="key-string" relation="UserAccess">
311 : parrello 1.8 <Notes>Access code possessed by this
312 : parrello 1.1 user. A user can have many access codes; a genome is accessible to the user if its
313 :     access code matches any one of the user's access codes.</Notes>
314 : parrello 1.8 <DataGen testCount="2">RandParam('low', 'medium', 'high')</DataGen>
315 :     </Field>
316 : parrello 1.1 </Fields>
317 :     </Entity>
318 : parrello 1.8 <Entity name="Property" keyType="int">
319 :     <Notes>A [i]property[/i] is a type of assertion that could be made about the properties of
320 :     a particular feature. Each property instance is a key/value pair and can be associated
321 :     with many different features. Conversely, a feature can be associated with many key/value
322 :     pairs, even some that notionally contradict each other. For example, there can be evidence
323 :     that a feature is essential to the organism's survival and evidence that it is superfluous.</Notes>
324 :     <Fields>
325 :     <Field name="property-name" type="name-string">
326 :     <Notes>Name of this property.</Notes>
327 :     </Field>
328 :     <Field name="property-value" type="string">
329 :     <Notes>Value associated with this property. For each property
330 :     name, there must by a property record for all of its possible
331 :     values.</Notes>
332 :     </Field>
333 :     </Fields>
334 :     <Indexes>
335 :     <Index>
336 :     <Notes>This index enables the application to find all values for a specified property
337 :     name, or any given name/value pair.</Notes>
338 :     <IndexFields>
339 :     <IndexField name="property-name" order="ascending" />
340 :     <IndexField name="property-value" order="ascending" />
341 :     </IndexFields>
342 :     </Index>
343 :     </Indexes>
344 :     </Entity>
345 :     <Entity name="Diagram" keyType="name-string">
346 :     <Notes>A functional diagram describes the chemical reactions, often comprising a single
347 :     subsystem. A diagram is identified by a short name and contains a longer descriptive name.
348 :     The actual diagram shows which functional roles guide the reactions along with the inputs
349 :     and outputs; the database, however, only indicate which roles belong to a particular
350 :     map.</Notes>
351 :     <Fields>
352 :     <Field name="name" type="text">
353 :     <Notes>Descriptive name of this diagram.</Notes>
354 :     </Field>
355 :     </Fields>
356 :     </Entity>
357 :     <Entity name="ExternalAliasOrg" keyType="name-string">
358 :     <Notes>An external alias is a feature name for a functional assignment that is not a
359 :     FIG ID. Functional assignments for external aliases are kept in a separate section of
360 :     the database. This table contains a description of the relevant organism for an
361 :     external alias functional assignment.</Notes>
362 :     <Fields>
363 :     <Field name="org" type="text">
364 :     <Notes>Descriptive name of the target organism for this external alias.</Notes>
365 :     </Field>
366 :     </Fields>
367 :     </Entity>
368 :     <Entity name="ExternalAliasFunc" keyType="name-string">
369 :     <Notes>An external alias is a feature name for a functional assignment that is not a
370 :     FIG ID. Functional assignments for external aliases are kept in a separate section of
371 :     the database. This table contains the functional role for the external alias functional
372 :     assignment.</Notes>
373 :     <Fields>
374 :     <Field name="func" type="text">
375 :     <Notes>Functional role for this external alias.</Notes>
376 :     </Field>
377 :     </Fields>
378 :     </Entity>
379 : parrello 1.29 <Entity name="Coupling" keyType="id-string">
380 : parrello 1.6 <Notes>A coupling is a relationship between two features. The features are
381 :     physically close on the contig, and there is evidence that they generally
382 :     belong together. The key of this entity is formed by combining the coupled
383 : parrello 1.8 feature IDs with a space.</Notes>
384 : parrello 1.6 <Fields>
385 :     <Field name="score" type="int">
386 :     <Notes>A number based on the set of PCHs (pairs of close homologs). A PCH
387 :     indicates that two genes near each other on one genome are very similar to
388 :     genes near each other on another genome. The score only counts PCHs for which
389 :     the genomes are very different. (In other words, we have a pairing that persists
390 :     between different organisms.) A higher score implies a stronger meaning to the
391 :     clustering.</Notes>
392 :     </Field>
393 :     </Fields>
394 :     </Entity>
395 : parrello 1.30 <Entity name="PCH" keyType="counter">
396 : parrello 1.6 <Notes>A PCH (physically close homolog) connects a clustering (which is a
397 :     pair of physically close features on a contig) to a second pair of physically
398 :     close features that are similar to the first. Essentially, the PCH is a
399 :     relationship between two clusterings in which the first clustering's features
400 :     are similar to the second clustering's features. The simplest model for
401 :     this would be to simply relate clusterings to each other; however, not all
402 :     physically close pairs qualify as clusterings, so we relate a clustering to
403 : parrello 1.30 a pair of features. The key a unique ID number.</Notes>
404 : parrello 1.6 <Fields>
405 :     <Field name="used" type="boolean">
406 :     <Notes>TRUE if this PCH is used in scoring the attached clustering,
407 :     else FALSE. If a clustering has a PCH for a particular genome and many
408 :     similar genomes are present, then a PCH will probably exist for the
409 :     similar genomes as well. When this happens, only one of the PCHs will
410 :     be scored: the others are considered duplicates of the same evidence.</Notes>
411 :     </Field>
412 :     </Fields>
413 :     </Entity>
414 : parrello 1.31 <Entity name="Family" keyType="id-string">
415 :     <Notes>A family is a group of homologous PEGs believed to have the same function. Protein
416 :     families provide a mechanism for verifying the accuracy of functional assignments
417 :     and are also used in determining phylogenetic trees.</Notes>
418 :     <Fields>
419 : parrello 1.32 <Field name="function" type="text">
420 : parrello 1.31 <Notes>The functional assignment expected for all PEGs in this family.</Notes>
421 :     </Field>
422 : parrello 1.33 <Field name="size" type="int">
423 : parrello 1.31 <Notes>The number of proteins in this family. This may be larger than the
424 :     number of PEGs included in the family, since the family may also contain external
425 :     IDs.</Notes>
426 :     </Field>
427 :     </Fields>
428 :     </Entity>
429 : parrello 1.1 </Entities>
430 :     <Relationships>
431 : parrello 1.34 <Relationship name="IsFamilyForFeature" from="Family" to="Feature" arity="MM">
432 : parrello 1.31 <Notes>This relationship connects a protein family to all of its PEGs and connects
433 :     each PEG to all of its protein families.</Notes>
434 :     </Relationship>
435 : parrello 1.6 <Relationship name="ParticipatesInCoupling" from="Feature" to="Coupling" arity="MM">
436 :     <Notes>This relationship connects a feature to all the functional couplings
437 :     in which it participates. A functional coupling is a recognition of the fact
438 :     that the features are close to each other on a chromosome, and similar
439 :     features in other genomes also tend to be close.</Notes>
440 :     <Fields>
441 :     <Field name="pos" type="int">
442 :     <Notes>Ordinal position of the feature in the coupling. Currently,
443 :     this is either "1" or "2".</Notes>
444 :     </Field>
445 :     </Fields>
446 :     <ToIndex>
447 :     <Notes>This index enables the application to view the features of
448 :     a coupling in the proper order. The order influences the way the
449 :     PCHs are examined.</Notes>
450 :     <IndexFields>
451 :     <IndexField name="pos" order="ascending" />
452 :     </IndexFields>
453 :     </ToIndex>
454 :     </Relationship>
455 : parrello 1.27 <Relationship name="IsSynonymGroupFor" from="SynonymGroup" to="Feature" arity="1M">
456 :     <Notes>This relation connects a synonym group to the features that make it
457 :     up.</Notes>
458 :     </Relationship>
459 : parrello 1.24 <Relationship name="HasFeature" from="Genome" to="Feature" arity="1M">
460 :     <Notes>This relationship connects a genome to all of its features. This
461 :     relationship is redundant in a sense, because the genome ID is part
462 :     of the feature ID; however, it makes the creation of certain queries more
463 :     convenient because you can drag in filtering information for a feature's
464 :     genome.</Notes>
465 :     <Fields>
466 :     <Field name="type" type="key-string">
467 :     <Notes>Feature type (eg. peg, rna)</Notes>
468 :     </Field>
469 :     </Fields>
470 :     <ToIndex>
471 :     <Notes>This index enables the application to view the features of a
472 :     Genome sorted by type.</Notes>
473 :     <IndexFields>
474 :     <IndexField name="type" order="ascending" />
475 :     </IndexFields>
476 :     </ToIndex>
477 :     </Relationship>
478 : parrello 1.6 <Relationship name="IsEvidencedBy" from="Coupling" to="PCH" arity="1M">
479 :     <Notes>This relationship connects a functional coupling to the physically
480 :     close homologs (PCHs) which affirm that the coupling is meaningful.</Notes>
481 :     </Relationship>
482 :     <Relationship name="UsesAsEvidence" from="PCH" to="Feature" arity="MM">
483 :     <Notes>This relationship connects a PCH to the features that represent its
484 :     evidence. Each PCH is connected to a parent coupling that relates two features
485 :     on a specific genome. The PCH's evidence that the parent coupling is functional
486 :     is the existence of two physically close features on a different genome that
487 :     correspond to the features in the coupling. Those features are found on the
488 :     far side of this relationship.</Notes>
489 :     <Fields>
490 :     <Field name="pos" type="int">
491 :     <Notes>Ordinal position of the feature in the coupling that corresponds
492 :     to our target feature. There is a one-to-one correspondence between the
493 :     features connected to the PCH by this relationship and the features
494 :     connected to the PCH's parent coupling. The ordinal position is used
495 :     to decode that relationship. Currently, this field is either "1" or
496 :     "2".</Notes>
497 :     </Field>
498 :     </Fields>
499 :     <FromIndex>
500 :     <Notes>This index enables the application to view the features of
501 :     a PCH in the proper order.</Notes>
502 :     <IndexFields>
503 :     <IndexField name="pos" order="ascending" />
504 :     </IndexFields>
505 :     </FromIndex>
506 :     </Relationship>
507 : parrello 1.1 <Relationship name="HasContig" from="Genome" to="Contig" arity="1M">
508 :     <Notes>This relationship connects a genome to the contigs that contain the actual genetic
509 :     information.</Notes>
510 :     </Relationship>
511 :     <Relationship name="ComesFrom" from="Genome" to="Source" arity="MM">
512 :     <Notes>This relationship connects a genome to the sources that mapped it. A genome can
513 :     come from a single source or from a cooperation among multiple sources.</Notes>
514 :     </Relationship>
515 :     <Relationship name="IsMadeUpOf" from="Contig" to="Sequence" arity="1M">
516 :     <Notes>A contig is stored in the database as an ordered set of sequences. By splitting the
517 :     contig into sequences, we get a performance boost from only needing to keep small portions
518 :     of a contig in memory at any one time. This relationship connects the contig to its
519 :     constituent sequences.</Notes>
520 :     <Fields>
521 :     <Field name="len" type="int">
522 : parrello 1.15 <Notes>Length of the sequence.</Notes>
523 :     </Field>
524 : parrello 1.1 <Field name="start-position" type="int">
525 : parrello 1.15 <Notes>Index (1-based) of the point in the contig where this
526 :     sequence starts.</Notes>
527 :     </Field>
528 : parrello 1.1 </Fields>
529 :     <FromIndex>
530 :     <Notes>This index enables the application to find all of the sequences in
531 : parrello 1.8 a contig in order, and makes it easier to find a particular residue section.</Notes>
532 : parrello 1.1 <IndexFields>
533 :     <IndexField name="start-position" order="ascending" />
534 :     <IndexField name="len" order="ascending" />
535 :     </IndexFields>
536 :     </FromIndex>
537 :     </Relationship>
538 :     <Relationship name="IsTargetOfAnnotation" from="Feature" to="Annotation" arity="1M">
539 :     <Notes>This relationship connects a feature to its annotations.</Notes>
540 :     </Relationship>
541 :     <Relationship name="MadeAnnotation" from="SproutUser" to="Annotation" arity="1M">
542 :     <Notes>This relationship connects an annotation to the user who made it.</Notes>
543 :     </Relationship>
544 :     <Relationship name="ParticipatesIn" from="Genome" to="Subsystem" arity="MM">
545 :     <Notes>This relationship connects subsystems to the genomes that use
546 :     it. If the subsystem has been curated for the genome, then the subsystem's roles will also be
547 :     connected to the genome features through the [b]SSCell[/b] object.</Notes>
548 : parrello 1.15 <Fields>
549 :     <Field name="variant-code" type="key-string">
550 : parrello 1.20 <Notes>Code indicating the subsystem variant to which this
551 : parrello 1.15 genome belongs. Each subsystem can have multiple variants. A variant
552 : parrello 1.20 code of [b]-1[/b] indicates that the genome does not have a functional
553 :     variant of the subsystem. A variant code of [b]0[/b] indicates that
554 :     the genome's participation is considered iffy.</Notes>
555 : parrello 1.15 </Field>
556 :     </Fields>
557 :     <ToIndex>
558 :     <Notes>This index enables the application to find all of the genomes using
559 :     a subsystem in order by variant code, which is how we wish to display them
560 :     in the spreadsheets.</Notes>
561 :     <IndexFields>
562 :     <IndexField name="variant-code" order="ascending" />
563 :     </IndexFields>
564 :     </ToIndex>
565 : parrello 1.1 </Relationship>
566 :     <Relationship name="OccursInSubsystem" from="Role" to="Subsystem" arity="MM">
567 :     <Notes>This relationship connects roles to the subsystems that implement them. </Notes>
568 : parrello 1.15 <Fields>
569 :     <Field name="column-number" type="int">
570 :     <Notes>Column number for this role in the specified subsystem's
571 :     spreadsheet.</Notes>
572 :     </Field>
573 :     </Fields>
574 :     <ToIndex>
575 :     <Notes>This index enables the application to see the subsystem roles
576 :     in column order. The ordering of the roles is usually significant,
577 :     so it is important to preserve it.</Notes>
578 :     <IndexFields>
579 :     <IndexField name="column-number" order="ascending" />
580 :     </IndexFields>
581 :     </ToIndex>
582 : parrello 1.1 </Relationship>
583 :     <Relationship name="IsGenomeOf" from="Genome" to="SSCell" arity="1M">
584 :     <Notes>This relationship connects a subsystem's spreadsheet cell to the
585 :     genome for the spreadsheet column.</Notes>
586 :     </Relationship>
587 :     <Relationship name="IsRoleOf" from="Role" to="SSCell" arity="1M">
588 :     <Notes>This relationship connects a subsystem's spreadsheet cell to the
589 :     role for the spreadsheet row.</Notes>
590 :     </Relationship>
591 :     <Relationship name="ContainsFeature" from="SSCell" to="Feature" arity="MM">
592 :     <Notes>This relationship connects a subsystem's spreadsheet cell to the
593 :     features assigned to it.</Notes>
594 : parrello 1.15 <Fields>
595 :     <Field name="cluster-number" type="int">
596 :     <Notes>ID of this feature's cluster. Clusters represent families of
597 :     related proteins participating in a subsystem.</Notes>
598 :     </Field>
599 :     </Fields>
600 :     </Relationship>
601 :     <Relationship name="IsAComponentOf" from="Compound" to="Reaction" arity="MM">
602 :     <Notes>This relationship connects a reaction to the compounds that participate
603 :     in it.</Notes>
604 :     <Fields>
605 :     <Field name="product" type="boolean">
606 :     <Notes>TRUE if the compound is a product of the reaction, FALSE if
607 :     it is a substrate. When a reaction is written on paper in
608 :     chemical notation, the substrates are left of the arrow and the
609 :     products are to the right. Sorting on this field will cause
610 :     the substrates to appear first, followed by the products. If the
611 :     reaction is reversible, then the notion of substrates and products
612 :     is not at intuitive; however, a value here of FALSE still puts the
613 :     compound left of the arrow and a value of TRUE still puts it to the
614 :     right.</Notes>
615 :     </Field>
616 : parrello 1.19 <Field name="stoichiometry" type="key-string">
617 : parrello 1.15 <Notes>Number of molecules of the compound that participate in a
618 :     single instance of the reaction. For example, if a reaction
619 : parrello 1.19 produces two water molecules, the stoichiometry of water for the
620 : parrello 1.15 reaction would be two. When a reaction is written on paper in
621 : parrello 1.19 chemical notation, the stoichiometry is the number next to the
622 : parrello 1.15 chemical formula of the compound.</Notes>
623 :     </Field>
624 :     <Field name="main" type="boolean">
625 :     <Notes>TRUE if this compound is one of the main participants in
626 :     the reaction, else FALSE. It is permissible for none of the
627 :     compounds in the reaction to be considered main, in which
628 :     case this value would be FALSE for all of the relevant
629 :     compounds.</Notes>
630 :     </Field>
631 :     <Field name="loc" type="key-string">
632 :     <Notes>An optional character string that indicates the relative
633 :     position of this compound in the reaction's chemical formula. The
634 :     location affects the way the compounds present as we cross the
635 :     relationship from the reaction side. The product/substrate flag
636 :     comes first, then the value of this field, then the main flag.
637 :     The default value is an empty string; however, the empty string
638 :     sorts first, so if this field is used, it should probably be
639 :     used for every compound in the reaction.</Notes>
640 :     </Field>
641 : parrello 1.19 <Field name="discriminator" type="int">
642 :     <Notes>A unique ID for this record. The discriminator does not
643 :     provide any useful data, but it prevents identical records from
644 :     being collapsed by the SELECT DISTINCT command used by ERDB to
645 :     retrieve data.</Notes>
646 :     </Field>
647 : parrello 1.15 </Fields>
648 :     <ToIndex>
649 :     <Notes>This index presents the compounds in the reaction in the
650 :     order they should be displayed when writing it in chemical notation.
651 :     All the substrates appear before all the products, and within that
652 :     ordering, the main compounds appear first.</Notes>
653 : parrello 1.19 <IndexFields>
654 :     <IndexField name="product" order="ascending" />
655 :     <IndexField name="loc" order="ascending" />
656 :     <IndexField name="main" order="descending" />
657 :     </IndexFields>
658 : parrello 1.15 </ToIndex>
659 : parrello 1.1 </Relationship>
660 :     <Relationship name="IsLocatedIn" from="Feature" to="Contig" arity="MM">
661 :     <Notes>This relationship connects a feature to the contig segments that work together
662 :     to effect it. The segments are numbered sequentially starting from 1. The database is
663 :     required to place an upper limit on the length of each segment. If a segment is longer
664 :     than the maximum, it can be broken into smaller bits.
665 :     [p]The upper limit enables applications to locate all features that contain a specific
666 :     residue. For example, if the upper limit is 100 and we are looking for a feature that
667 :     contains residue 234 of contig [b]ABC[/b], we can look for features with a begin point
668 :     between 135 and 333. The results can then be filtered by direction and length of the
669 :     segment.</Notes>
670 :     <Fields>
671 :     <Field name="locN" type="int">
672 : parrello 1.8 <Notes>Sequence number of this segment.</Notes>
673 :     </Field>
674 : parrello 1.1 <Field name="beg" type="int">
675 : parrello 1.8 <Notes>Index (1-based) of the first residue in the contig that
676 :     belongs to the segment.</Notes>
677 :     </Field>
678 : parrello 1.1 <Field name="len" type="int">
679 : parrello 1.8 <Notes>Number of residues in the segment. A length of 0 identifies
680 :     a specific point between residues. This is the point before the residue if the direction
681 :     is forward and the point after the residue if the direction is backward.</Notes>
682 :     </Field>
683 : parrello 1.1 <Field name="dir" type="char">
684 : parrello 1.8 <Notes>Direction of the segment: [b]+[/b] if it is forward and
685 :     [b]-[/b] if it is backward.</Notes>
686 :     </Field>
687 : parrello 1.1 </Fields>
688 :     <FromIndex Unique="false">
689 :     <Notes>This index allows the application to find all the segments of a feature in
690 : parrello 1.8 the proper order.</Notes>
691 : parrello 1.1 <IndexFields>
692 :     <IndexField name="locN" order="ascending" />
693 :     </IndexFields>
694 :     </FromIndex>
695 :     <ToIndex>
696 :     <Notes>This index is the one used by applications to find all the feature
697 :     segments that contain a specific residue.</Notes>
698 :     <IndexFields>
699 :     <IndexField name="beg" order="ascending" />
700 :     </IndexFields>
701 :     </ToIndex>
702 :     </Relationship>
703 : parrello 1.8 <Relationship name="HasProperty" from="Feature" to="Property" arity="MM">
704 :     <Notes>This relationship connects a feature to its known property values.
705 :     The relationship contains text data that indicates the paper or organization
706 :     that discovered evidence that the feature possesses the property. So, for
707 :     example, if two papers presented evidence that a feature is essential,
708 :     there would be an instance of this relationship for both.</Notes>
709 :     <Fields>
710 :     <Field name="evidence" type="text">
711 :     <Notes>URL or citation of the paper or
712 :     institution that reported evidence of the relevant feature possessing
713 :     the specified property value.</Notes>
714 :     </Field>
715 :     </Fields>
716 :     </Relationship>
717 :     <Relationship name="RoleOccursIn" from="Role" to="Diagram" arity="MM">
718 :     <Notes>This relationship connects a role to the diagrams on which it
719 :     appears. A role frequently identifies an enzyme, and can appear in many
720 :     diagrams. A diagram generally contains many different roles.</Notes>
721 :     </Relationship>
722 :     <Relationship name="HasSSCell" from="Subsystem" to="SSCell" arity="1M">
723 :     <Notes>This relationship connects a subsystem to the spreadsheet cells
724 :     used to analyze and display it. The cells themselves can be thought of
725 :     as a grid with Roles on one axis and Genomes on the other. The
726 :     various features of the subsystem are then assigned to the cells.</Notes>
727 :     </Relationship>
728 :     <Relationship name="IsTrustedBy" from="SproutUser" to="SproutUser" arity="MM">
729 :     <Notes>This relationship identifies the users trusted by each
730 :     particular user. When viewing functional assignments, the
731 :     assignment displayed is the most recent one by a user trusted
732 :     by the current user. The current user implicitly trusts himself.
733 :     If no trusted users are specified in the database, the user
734 :     also implicitly trusts the user [b]FIG[/b].</Notes>
735 :     </Relationship>
736 : parrello 1.15 <Relationship name="ConsistsOfRoles" from="RoleSubset" to="Role" arity="MM">
737 :     <Notes>This relationship connects a role subset to the roles that it covers.
738 :     A subset is, essentially, a named group of roles belonging to a specific
739 :     subsystem, and this relationship effects that. Note that will a role
740 :     may belong to many subsystems, a subset belongs to only one subsystem,
741 :     and all roles in the subset must have that subsystem in common.</Notes>
742 :     </Relationship>
743 :     <Relationship name="ConsistsOfGenomes" from="GenomeSubset" to="Genome" arity="MM">
744 :     <Notes>This relationship connects a subset to the genomes that it covers.
745 :     A subset is, essentially, a named group of genomes participating in a specific
746 :     subsystem, and this relationship effects that. Note that while a genome
747 :     may belong to many subsystems, a subset belongs to only one subsystem,
748 :     and all genomes in the subset must have that subsystem in common.</Notes>
749 :     </Relationship>
750 :     <Relationship name="HasRoleSubset" from="Subsystem" to="RoleSubset" arity="1M">
751 :     <Notes>This relationship connects a subsystem to its constituent
752 :     role subsets. Note that some roles in a subsystem may not belong to a
753 :     subset, so the relationship between roles and subsystems cannot be
754 :     derived from the relationships going through the subset.</Notes>
755 :     </Relationship>
756 :     <Relationship name="HasGenomeSubset" from="Subsystem" to="GenomeSubset" arity="1M">
757 :     <Notes>This relationship connects a subsystem to its constituent
758 :     genome subsets. Note that some genomes in a subsystem may not belong to a
759 :     subset, so the relationship between genomes and subsystems cannot be
760 :     derived from the relationships going through the subset.</Notes>
761 :     </Relationship>
762 :     <Relationship name="Catalyzes" from="Role" to="Reaction" arity="MM">
763 :     <Notes>This relationship connects a role to the reactions it catalyzes.
764 :     The purpose of a role is to create proteins that trigger certain
765 :     chemical reactions. A single reaction can be triggered by many roles,
766 :     and a role can trigger many reactions.</Notes>
767 :     </Relationship>
768 : parrello 1.1 </Relationships>
769 :     </Database>

MCS Webmaster
ViewVC Help
Powered by ViewVC 1.0.3