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

Annotation of /Sprout/SproutDBD.xml

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.46 - (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 :     </Field>
11 :     <Field name="species" type="name-string">
12 : parrello 1.8 <Notes>Species of the relevant organism.</Notes>
13 :     </Field>
14 : parrello 1.1 <Field name="unique-characterization" type="medium-string">
15 : parrello 1.8 <Notes>The unique characterization identifies the particular organism instance from which the
16 :     genome is taken. It is possible to have in the database more than one genome for a
17 : parrello 1.1 particular species, and every individual organism has variations in its DNA.</Notes>
18 :     </Field>
19 :     <Field name="access-code" type="key-string">
20 : parrello 1.8 <Notes>The access code determines which users can look at the data relating to this genome.
21 :     Each user is associated with a set of access codes. In order to view a genome, one of
22 :     the user's access codes must match this value.</Notes>
23 :     </Field>
24 : parrello 1.15 <Field name="complete" type="boolean">
25 :     <Notes>TRUE if the genome is complete, else FALSE</Notes>
26 :     </Field>
27 : parrello 1.8 <Field name="taxonomy" type="text">
28 :     <Notes>The taxonomy string contains the full taxonomy of the organism, while individual elements
29 :     separated by semi-colons (and optional white space), starting with the domain and ending with
30 :     the disambiguated genus and species (which is the organism's scientific name plus an
31 :     identifying string).</Notes>
32 :     </Field>
33 : parrello 1.37 <Field name="primary-group" type="name-string">
34 :     <Notes>The primary NMPDR group for this organism. There is always exactly one NMPDR group
35 :     (either based on the organism name or the default value "Supporting"), whereas there can be
36 :     multiple named groups or even none.</Notes>
37 :     </Field>
38 : parrello 1.8 <Field name="group-name" type="name-string" relation="GenomeGroups">
39 :     <Notes>The group identifies a special grouping of organisms that would be displayed on a particular
40 :     page or of particular interest to a research group or web site. A single genome can belong to multiple
41 :     such groups or none at all.</Notes>
42 :     </Field>
43 : parrello 1.1 </Fields>
44 :     <Indexes>
45 : parrello 1.45 <Index>
46 : parrello 1.1 <Notes>This index allows the applications to find all genomes associated with
47 :     a specific access code, so that a complete list of the genomes users can view
48 :     may be generated.</Notes>
49 :     <IndexFields>
50 :     <IndexField name="access-code" order="ascending" />
51 :     <IndexField name="genus" order="ascending" />
52 :     <IndexField name="species" order="ascending" />
53 :     <IndexField name="unique-characterization" order="ascending" />
54 :     </IndexFields>
55 :     </Index>
56 : parrello 1.45 <Index>
57 : parrello 1.37 <Notes>This index allows the applications to find all genomes associated with
58 :     a specific primary (NMPDR) group.</Notes>
59 :     <IndexFields>
60 :     <IndexField name="primary-group" order="ascending" />
61 :     <IndexField name="genus" order="ascending" />
62 :     <IndexField name="species" order="ascending" />
63 :     <IndexField name="unique-characterization" order="ascending" />
64 :     </IndexFields>
65 :     </Index>
66 : parrello 1.45 <Index>
67 : parrello 1.1 <Notes>This index allows the applications to find all genomes for a particular
68 :     species.</Notes>
69 :     <IndexFields>
70 :     <IndexField name="genus" order="ascending" />
71 :     <IndexField name="species" order="ascending" />
72 :     <IndexField name="unique-characterization" order="ascending" />
73 :     </IndexFields>
74 :     </Index>
75 :     </Indexes>
76 :     </Entity>
77 :     <Entity name="Source" keyType="medium-string">
78 :     <Notes>A [i]source[/i] describes a place from which genome data was taken. This can be an organization
79 :     or a paper citation.</Notes>
80 :     <Fields>
81 :     <Field name="URL" type="string" relation="SourceURL">
82 : parrello 1.8 <Notes>URL the paper cited or of the organization's web site. This field optional.</Notes>
83 :     </Field>
84 : parrello 1.1 <Field name="description" type="text">
85 : parrello 1.8 <Notes>Description the source. The description can be a street address or a citation.</Notes>
86 :     </Field>
87 : parrello 1.1 </Fields>
88 :     </Entity>
89 :     <Entity name="Contig" keyType="name-string">
90 :     <Notes>A [i]contig[/i] is a contiguous run of residues. The contig's ID consists of the
91 :     genome ID followed by a name that identifies which contig this is for the parent genome. As
92 :     is the case with all keys in this database, the individual components are separated by a
93 :     period.
94 :     [p]A contig can contain over a million residues. For performance reasons, therefore,
95 :     the contig is split into multiple pieces called [i]sequences[/i]. The sequences
96 :     contain the characters that represent the residues as well as data on the quality of
97 :     the residue identification.</Notes>
98 :     </Entity>
99 :     <Entity name="Sequence" keyType="name-string">
100 :     <Notes>A [i]sequence[/i] is a continuous piece of a [i]contig[/i]. Contigs are split into
101 :     sequences so that we don't have to have the entire contig in memory when we are
102 :     manipulating it. The key of the sequence is the contig ID followed by the index of
103 :     the begin point.</Notes>
104 :     <Fields>
105 :     <Field name="sequence" type="text">
106 : parrello 1.8 <Notes>String consisting of the residues. Each residue is described by a single
107 :     character in the string.</Notes>
108 :     </Field>
109 : parrello 1.1 <Field name="quality-vector" type="text">
110 : parrello 1.9 <Notes>String describing the quality data for each base pair. Individual values will
111 : parrello 1.8 be separated by periods. The value represents negative exponent of the probability
112 :     of error. Thus, for example, a quality of 30 indicates the probability of error is
113 :     10^-30. A higher quality number a better chance of a correct match. It is possible
114 : parrello 1.9 that the quality data is not known for a sequence. If that is the case, the quality
115 : parrello 1.8 vector will contain the [b]unknown[/b].</Notes>
116 :     </Field>
117 : parrello 1.1 </Fields>
118 :     </Entity>
119 : parrello 1.25 <Entity name="Feature" keyType="id-string">
120 : parrello 1.1 <Notes>A [i]feature[/i] is a part of a genome that is of special interest. Features
121 :     may be spread across multiple contigs of a genome, but never across more than
122 :     one genome. Features can be assigned to roles via spreadsheet cells,
123 :     and are the targets of annotation.</Notes>
124 :     <Fields>
125 :     <Field name="feature-type" type="string">
126 : parrello 1.8 <Notes>Code indicating the type of this feature.</Notes>
127 :     </Field>
128 : parrello 1.14 <Field name="alias" type="medium-string" relation="FeatureAlias">
129 : parrello 1.9 <Notes>Alternative name for this feature. A feature can have many aliases.</Notes>
130 : parrello 1.8 </Field>
131 : parrello 1.1 <Field name="translation" type="text" relation="FeatureTranslation">
132 : parrello 1.8 <Notes>[i](optional)[/i] A translation of this feature's residues into character
133 :     codes, formed by concatenating the pieces of the feature together. For a
134 :     protein encoding group, this is the protein characters. For other types
135 :     it is the DNA characters.</Notes>
136 :     </Field>
137 : parrello 1.1 <Field name="upstream-sequence" type="text" relation="FeatureUpstream">
138 : parrello 1.8 <Notes>Upstream sequence the feature. This includes residues preceding the feature as well as some of
139 :     the feature's initial residues.</Notes>
140 :     </Field>
141 : parrello 1.42 <Field name="assignment" type="text">
142 :     <Notes>Default functional assignment for this feature.</Notes>
143 :     </Field>
144 : parrello 1.1 <Field name="active" type="boolean">
145 : parrello 1.11 <Notes>TRUE if this feature is still considered valid, FALSE if it has been logically deleted.</Notes>
146 : parrello 1.8 </Field>
147 : parrello 1.41 <Field name="keywords" type="text" searchable="1">
148 :     <Notes>This is a list of search keywords for the feature. It includes the
149 :     functional assignment, subsystem roles, and special properties.</Notes>
150 : parrello 1.36 </Field>
151 : parrello 1.8 <Field name="link" type="text" relation="FeatureLink">
152 :     <Notes>Web hyperlink for this feature. A feature have no hyperlinks or it can have many. The
153 :     links are to other websites that have useful about the gene that the feature represents, and
154 :     are coded as raw HTML, using [b]&lt;a href="[i]link[/i]"&gt;[i]text[/i]&lt;/a&gt;[/b] notation.</Notes>
155 :     </Field>
156 : parrello 1.41 <Field name="conservation" type="float" relation="FeatureConservation">
157 :     <Notes>A number between 0 and 1 that indicates the degree to which this feature's DNA is
158 :     conserved in related genomes. A value of 1 indicates perfect conservation. A value less
159 :     than 1 is a reflect of the degree to which gap characters interfere in the alignment
160 :     between the feature and its close relatives.</Notes>
161 :     </Field>
162 : parrello 1.45 <Field name="essential" type="text" relation="FeatureEssential" special="property_search">
163 :     <Notes>A value indicating the essentiality of the feature, coded as HTML. In most
164 :     cases, this will be a word describing whether the essentiality is confirmed (essential)
165 :     or potential (potential-essential), hyperlinked to the document from which the
166 :     essentiality was curated. If a feature is not essential, this field will have no
167 :     values; otherwise, it may have multiple values.</Notes>
168 :     </Field>
169 :     <Field name="virulent" type="text" relation="FeatureVirulent" special="property_search">
170 :     <Notes>A value indicating the virulence of the feature, coded as HTML. In most
171 :     cases, this will be a phrase or SA number hyperlinked to the document from which
172 :     the virulence information was curated. If the feature is not virulent, this field
173 :     will have no values; otherwise, it may have multiple values.</Notes>
174 :     </Field>
175 :     <Field name="iedb" type="text" relation="FeatureIEDB" special="property_search">
176 :     <Notes>A value indicating whether or not the feature can be found in the
177 :     Immune Epitope Database. If the feature has not been matched to that database,
178 :     this field will have no values. Otherwise, it will have an epitope name and/or
179 :     sequence, hyperlinked to the database.</Notes>
180 :     </Field>
181 : parrello 1.1 </Fields>
182 : parrello 1.8 <Indexes>
183 :     <Index>
184 :     <Notes>This index allows the user to find the feature corresponding to
185 :     the specified alias name.</Notes>
186 :     <IndexFields>
187 :     <IndexField name="alias" order="ascending" />
188 :     </IndexFields>
189 :     </Index>
190 :     </Indexes>
191 : parrello 1.1 </Entity>
192 : parrello 1.27 <Entity name="SynonymGroup" keyType="id-string">
193 :     <Notes>A [i]synonym group[/i] represents a group of features. Substantially identical features
194 :     are mapped to the same synonym group, and this information is used to expand similarities.</Notes>
195 :     </Entity>
196 : parrello 1.1 <Entity name="Role" keyType="string">
197 :     <Notes>A [i]role[/i] describes a biological function that may be fulfilled by a feature.
198 :     One of the main goals of the database is to record the roles of the various features.</Notes>
199 : parrello 1.8 <Fields>
200 : parrello 1.18 <Field name="EC" type="string" relation="RoleEC">
201 :     <Notes>EC code for this role.</Notes>
202 : parrello 1.8 </Field>
203 : parrello 1.15 <Field name="abbr" type="name-string">
204 :     <Notes>Abbreviated name for the role, generally non-unique, but useful
205 :     in column headings for HTML tables.</Notes>
206 :     </Field>
207 : parrello 1.8 </Fields>
208 : parrello 1.18 <Indexes>
209 :     <Index>
210 :     <Notes>This index allows the user to find the role corresponding to
211 :     an EC number.</Notes>
212 :     <IndexFields>
213 :     <IndexField name="EC" order="ascending" />
214 :     </IndexFields>
215 :     </Index>
216 :     </Indexes>
217 : parrello 1.1 </Entity>
218 :     <Entity name="Annotation" keyType="name-string">
219 :     <Notes>An [i]annotation[/i] contains supplementary information about a feature. Annotations
220 : parrello 1.8 are currently the only objects that may be inserted directly into the database. All other
221 : parrello 1.24 information is loaded from data exported by the SEED.</Notes>
222 : parrello 1.8 <Fields>
223 :     <Field name="time" type="date">
224 :     <Notes>Date and time of the annotation.</Notes>
225 :     </Field>
226 :     <Field name="annotation" type="text">
227 :     <Notes>Text of the annotation.</Notes>
228 :     </Field>
229 : parrello 1.1 </Fields>
230 : parrello 1.26 <Indexes>
231 :     <Index>
232 :     <Notes>This index allows the user to find recent annotations.</Notes>
233 :     <IndexFields>
234 :     <IndexField name="time" order="descending" />
235 :     </IndexFields>
236 :     </Index>
237 :     </Indexes>
238 : parrello 1.1 </Entity>
239 : parrello 1.15 <Entity name="Reaction" keyType="key-string">
240 :     <Notes>A [i]reaction[/i] is a chemical process catalyzed by a protein. The reaction ID
241 :     is generally a small number preceded by a letter.</Notes>
242 :     <Fields>
243 :     <Field name="url" type="string" relation="ReactionURL">
244 :     <Notes>HTML string containing a link to a web location that describes the
245 :     reaction. This field is optional.</Notes>
246 :     </Field>
247 :     <Field name="rev" type="boolean">
248 :     <Notes>TRUE if this reaction is reversible, else FALSE</Notes>
249 :     </Field>
250 :     </Fields>
251 :     </Entity>
252 :     <Entity name="Compound" keyType="name-string">
253 :     <Notes>A [i]compound[/i] is a chemical that participates in a reaction.
254 :     All compounds have a unique ID and may also have one or more names.</Notes>
255 :     <Fields>
256 :     <Field name="name-priority" type="int" relation="CompoundName">
257 :     <Notes>Priority of a compound name. The name with the loweset
258 :     priority is the main name of this compound.</Notes>
259 :     </Field>
260 :     <Field name="name" type="name-string" relation="CompoundName">
261 :     <Notes>Descriptive name for the compound. A compound may
262 :     have several names.</Notes>
263 :     </Field>
264 :     <Field name="cas-id" type="name-string" relation="CompoundCAS">
265 :     <Notes>Chemical Abstract Service ID for this compound (optional).</Notes>
266 :     </Field>
267 : parrello 1.19 <Field name="label" type="name-string">
268 :     <Notes>Name used in reaction display strings.
269 :     It is the same as the name possessing a priority of 1, but it is placed
270 :     here to speed up the query used to create the display strings.</Notes>
271 :     </Field>
272 : parrello 1.15 </Fields>
273 :     <Indexes>
274 :     <Index>
275 :     <Notes>This index allows the user to find the compound corresponding to
276 :     the specified name.</Notes>
277 :     <IndexFields>
278 :     <IndexField name="name" order="ascending" />
279 :     </IndexFields>
280 :     </Index>
281 :     <Index>
282 : parrello 1.17 <Notes>This index allows the user to find the compound corresponding to
283 :     the specified CAS ID.</Notes>
284 :     <IndexFields>
285 :     <IndexField name="cas-id" order="ascending" />
286 :     </IndexFields>
287 :     </Index>
288 :     <Index>
289 : parrello 1.15 <Notes>This index allows the user to access the compound names in
290 :     priority order.</Notes>
291 :     <IndexFields>
292 :     <IndexField name="id" order="ascending" />
293 :     <IndexField name="name-priority" order="ascending" />
294 :     </IndexFields>
295 :     </Index>
296 :     </Indexes>
297 :     </Entity>
298 : parrello 1.5 <Entity name="Subsystem" keyType="string">
299 : parrello 1.1 <Notes>A [i]subsystem[/i] is a collection of roles that work together in a cell. Identification of subsystems
300 :     is an important tool for recognizing parallel genetic features in different organisms.</Notes>
301 : parrello 1.15 <Fields>
302 :     <Field name="curator" type="string">
303 :     <Notes>Name of the person currently in charge of the subsystem.</Notes>
304 :     </Field>
305 :     <Field name="notes" type="text">
306 :     <Notes>Descriptive notes about the subsystem.</Notes>
307 :     </Field>
308 : parrello 1.28 <Field name="classification" type="string" relation="SubsystemClass">
309 : parrello 1.44 <Notes>Classification string, colon-delimited. This string organizes the
310 : parrello 1.42 subsystems into a hierarchy.</Notes>
311 : parrello 1.28 </Field>
312 : parrello 1.15 </Fields>
313 :     </Entity>
314 :     <Entity name="RoleSubset" keyType="string">
315 :     <Notes>A [i]role subset[/i] is a named collection of roles in a particular subsystem. The
316 :     subset names are generally very short, non-unique strings. The ID of the parent
317 :     subsystem is prefixed to the subset ID in order to make it unique.</Notes>
318 :     </Entity>
319 :     <Entity name="GenomeSubset" keyType="string">
320 :     <Notes>A [i]genome subset[/i] is a named collection of genomes that participate
321 :     in a particular subsystem. The subset names are generally very short, non-unique
322 :     strings. The ID of the parent subsystem is prefixed to the subset ID in order
323 :     to make it unique.</Notes>
324 : parrello 1.1 </Entity>
325 : parrello 1.24 <Entity name="SSCell" keyType="hash-string">
326 : parrello 1.1 <Notes>Part of the process of locating and assigning features is creating a spreadsheet of
327 :     genomes and roles to which features are assigned. A [i]spreadsheet cell[/i] represents one
328 :     of the positions on the spreadsheet.</Notes>
329 :     </Entity>
330 :     <Entity name="SproutUser" keyType="name-string">
331 :     <Notes>A [i]user[/i] is a person who can make annotations and view data in the database. The
332 :     user object is keyed on the user's login name.</Notes>
333 :     <Fields>
334 : parrello 1.8 <Field name="description" type="string">
335 :     <Notes>Full name or description of this user.</Notes>
336 :     </Field>
337 : parrello 1.1 <Field name="access-code" type="key-string" relation="UserAccess">
338 : parrello 1.8 <Notes>Access code possessed by this
339 : parrello 1.1 user. A user can have many access codes; a genome is accessible to the user if its
340 :     access code matches any one of the user's access codes.</Notes>
341 : parrello 1.8 </Field>
342 : parrello 1.1 </Fields>
343 :     </Entity>
344 : parrello 1.8 <Entity name="Property" keyType="int">
345 :     <Notes>A [i]property[/i] is a type of assertion that could be made about the properties of
346 :     a particular feature. Each property instance is a key/value pair and can be associated
347 :     with many different features. Conversely, a feature can be associated with many key/value
348 :     pairs, even some that notionally contradict each other. For example, there can be evidence
349 :     that a feature is essential to the organism's survival and evidence that it is superfluous.</Notes>
350 :     <Fields>
351 :     <Field name="property-name" type="name-string">
352 :     <Notes>Name of this property.</Notes>
353 :     </Field>
354 :     <Field name="property-value" type="string">
355 :     <Notes>Value associated with this property. For each property
356 :     name, there must by a property record for all of its possible
357 :     values.</Notes>
358 :     </Field>
359 :     </Fields>
360 :     <Indexes>
361 :     <Index>
362 :     <Notes>This index enables the application to find all values for a specified property
363 :     name, or any given name/value pair.</Notes>
364 :     <IndexFields>
365 :     <IndexField name="property-name" order="ascending" />
366 :     <IndexField name="property-value" order="ascending" />
367 :     </IndexFields>
368 :     </Index>
369 :     </Indexes>
370 :     </Entity>
371 :     <Entity name="Diagram" keyType="name-string">
372 :     <Notes>A functional diagram describes the chemical reactions, often comprising a single
373 :     subsystem. A diagram is identified by a short name and contains a longer descriptive name.
374 :     The actual diagram shows which functional roles guide the reactions along with the inputs
375 :     and outputs; the database, however, only indicate which roles belong to a particular
376 :     map.</Notes>
377 :     <Fields>
378 :     <Field name="name" type="text">
379 :     <Notes>Descriptive name of this diagram.</Notes>
380 :     </Field>
381 :     </Fields>
382 :     </Entity>
383 :     <Entity name="ExternalAliasOrg" keyType="name-string">
384 :     <Notes>An external alias is a feature name for a functional assignment that is not a
385 :     FIG ID. Functional assignments for external aliases are kept in a separate section of
386 :     the database. This table contains a description of the relevant organism for an
387 :     external alias functional assignment.</Notes>
388 :     <Fields>
389 :     <Field name="org" type="text">
390 :     <Notes>Descriptive name of the target organism for this external alias.</Notes>
391 :     </Field>
392 :     </Fields>
393 :     </Entity>
394 :     <Entity name="ExternalAliasFunc" keyType="name-string">
395 :     <Notes>An external alias is a feature name for a functional assignment that is not a
396 :     FIG ID. Functional assignments for external aliases are kept in a separate section of
397 :     the database. This table contains the functional role for the external alias functional
398 :     assignment.</Notes>
399 :     <Fields>
400 :     <Field name="func" type="text">
401 :     <Notes>Functional role for this external alias.</Notes>
402 :     </Field>
403 :     </Fields>
404 :     </Entity>
405 : parrello 1.29 <Entity name="Coupling" keyType="id-string">
406 : parrello 1.6 <Notes>A coupling is a relationship between two features. The features are
407 :     physically close on the contig, and there is evidence that they generally
408 :     belong together. The key of this entity is formed by combining the coupled
409 : parrello 1.8 feature IDs with a space.</Notes>
410 : parrello 1.6 <Fields>
411 :     <Field name="score" type="int">
412 :     <Notes>A number based on the set of PCHs (pairs of close homologs). A PCH
413 :     indicates that two genes near each other on one genome are very similar to
414 :     genes near each other on another genome. The score only counts PCHs for which
415 :     the genomes are very different. (In other words, we have a pairing that persists
416 :     between different organisms.) A higher score implies a stronger meaning to the
417 :     clustering.</Notes>
418 :     </Field>
419 :     </Fields>
420 :     </Entity>
421 : parrello 1.30 <Entity name="PCH" keyType="counter">
422 : parrello 1.6 <Notes>A PCH (physically close homolog) connects a clustering (which is a
423 :     pair of physically close features on a contig) to a second pair of physically
424 :     close features that are similar to the first. Essentially, the PCH is a
425 :     relationship between two clusterings in which the first clustering's features
426 :     are similar to the second clustering's features. The simplest model for
427 :     this would be to simply relate clusterings to each other; however, not all
428 :     physically close pairs qualify as clusterings, so we relate a clustering to
429 : parrello 1.30 a pair of features. The key a unique ID number.</Notes>
430 : parrello 1.6 <Fields>
431 :     <Field name="used" type="boolean">
432 :     <Notes>TRUE if this PCH is used in scoring the attached clustering,
433 :     else FALSE. If a clustering has a PCH for a particular genome and many
434 :     similar genomes are present, then a PCH will probably exist for the
435 :     similar genomes as well. When this happens, only one of the PCHs will
436 :     be scored: the others are considered duplicates of the same evidence.</Notes>
437 :     </Field>
438 :     </Fields>
439 :     </Entity>
440 : parrello 1.31 <Entity name="Family" keyType="id-string">
441 :     <Notes>A family is a group of homologous PEGs believed to have the same function. Protein
442 :     families provide a mechanism for verifying the accuracy of functional assignments
443 :     and are also used in determining phylogenetic trees.</Notes>
444 :     <Fields>
445 : parrello 1.32 <Field name="function" type="text">
446 : parrello 1.31 <Notes>The functional assignment expected for all PEGs in this family.</Notes>
447 :     </Field>
448 : parrello 1.33 <Field name="size" type="int">
449 : parrello 1.31 <Notes>The number of proteins in this family. This may be larger than the
450 :     number of PEGs included in the family, since the family may also contain external
451 :     IDs.</Notes>
452 :     </Field>
453 :     </Fields>
454 :     </Entity>
455 : parrello 1.41 <Entity name="DrugProject" keyType="name-string">
456 :     <Notes>A drug project is a coherent sent of drug target data that came through the
457 :     pipeline. In other words, data is put into the database one drug project at a time.
458 :     This makes it easier to manage the incoming data and to track where a particular
459 :     piece of data originated.</Notes>
460 :     </Entity>
461 :     <Entity name="DrugTopic" keyType="int">
462 :     <Notes>A drug topic organizes the data in a project relating to a single organism
463 :     group's features as they apply to a specific category of activity. Categories include
464 :     features essential to the organism's survival, those that are targets or inhibitors
465 :     of anti-biotics, and those associated with virulence. Thus, a drug topic consists
466 :     of data from a single project for features that make good drug targets for the same
467 :     reason. Drug topics have an artificial, internally-generated key.</Notes>
468 :     <Fields>
469 :     <Field name="identifier" type="name-string">
470 :     <Notes>The topic identifier, consisting usually of a generalized organism name
471 :     (e.g. Staphylococcus) and the last name of the project's author. More than
472 :     one topic may have the same identifier, which is why this isn't the key.</Notes>
473 :     </Field>
474 : parrello 1.43 <Field name="tag" type="name-string">
475 : parrello 1.41 <Notes>A short phrase describing the topic.</Notes>
476 :     </Field>
477 :     <Field name="URL" type="string">
478 :     <Notes>A URL for the paper from which the topic was gathered.</Notes>
479 :     </Field>
480 :     <Field name="category" type="key-string">
481 :     <Notes>The code for this topic's activity category.</Notes>
482 :     </Field>
483 :     </Fields>
484 :     <Indexes>
485 :     <Index>
486 :     <Notes>This index enables the application to find all topics with a specified
487 : parrello 1.43 category, ordered by tag.</Notes>
488 : parrello 1.41 <IndexFields>
489 :     <IndexField name="category" order="ascending" />
490 : parrello 1.43 <IndexField name="tag" order="ascending" />
491 : parrello 1.41 </IndexFields>
492 :     </Index>
493 :     <Index>
494 :     <Notes>This index enables the application to find all topics with a specified
495 :     identifier, ordered by category.</Notes>
496 :     <IndexFields>
497 :     <IndexField name="identifier" order="ascending" />
498 :     <IndexField name="category" order="ascending" />
499 :     </IndexFields>
500 :     </Index>
501 :     </Indexes>
502 :     </Entity>
503 :     <Entity name="PDB" keyType="key-string">
504 :     <Notes>A PDB is a database of protein structure and related information of use
505 :     in drug targeting. The purpose of drug targeting is to analyze the ability
506 :     of drug molecules, or ligands, to bond to proteins. A PDB for a protein already
507 :     attached to a ligand is called a bound PDB. A PDB for the protein by itself is
508 :     called a free PDB. The key of the PDB is its code name on the Protein Data
509 :     Bank web site.</Notes>
510 :     <Fields>
511 :     <Field name="type" type="id-string">
512 :     <Notes>The type of PDB: "bound" or "free".</Notes>
513 :     </Field>
514 :     <Field name="title" type="string">
515 :     <Notes>The descriptive title of this PDB.</Notes>
516 :     </Field>
517 :     </Fields>
518 :     </Entity>
519 :     <Entity name="Ligand" keyType="string">
520 :     <Notes>A ligand is a molecule that can bind to a PDB. The CLIBE analysis
521 :     for a PDB is an attribute of the relationship between a PDB and a ligand.</Notes>
522 :     </Entity>
523 : parrello 1.1 </Entities>
524 :     <Relationships>
525 : parrello 1.41 <Relationship name="BindsWith" from="PDB" to="Ligand" arity="MM">
526 :     <Notes>This relationship describes the energy required for a ligand to bind
527 :     to the protein described by a PDB. The total energy required to bind
528 :     the ligand to the protein is described in this relationship by four
529 :     quantities. A negative value is energy released; a positive value is
530 :     energy required.</Notes>
531 :     <Fields>
532 :     <Field name="URL" type="string">
533 :     <Notes>URL for viewing the CLIBE data for this binding relationship.</Notes>
534 :     </Field>
535 :     <Field name="vanderwaals-energy" type="float">
536 :     <Notes>kCal/mol of energy due to Van der Waals force.</Notes>
537 :     </Field>
538 :     <Field name="hbond-energy" type="float">
539 :     <Notes>kCal/mol of energy due to hydrogen bonding.</Notes>
540 :     </Field>
541 :     <Field name="ionic-energy" type="float">
542 :     <Notes>kCal/mol of energy due to ionic bonding.</Notes>
543 :     </Field>
544 :     <Field name="solvation-energy" type="float">
545 :     <Notes>kCal/mol of energy due to attraction to the solvent in which
546 :     the ligand is immersed.</Notes>
547 :     </Field>
548 :     </Fields>
549 :     </Relationship>
550 : parrello 1.45 <Relationship name="ContainsAnalysisOf" from="DrugTopic" to="PDB" arity="MM">
551 : parrello 1.41 <Notes>This relationship describes the analysis of a free PDB as produced from a
552 :     particular topic.</Notes>
553 :     <Fields>
554 :     <Field name="pass-asp-info" type="int">
555 :     <Notes>The number of Active Site Points at which ligands can bind to
556 :     the protein.</Notes>
557 :     </Field>
558 :     <Field name="ramsol-file" type="string">
559 :     <Notes>The URL of a file that can be downloaded by the user and
560 :     passed to the Ramsol program for viewing the protein.</Notes>
561 :     </Field>
562 :     <Field name="pass-weight" type="float">
563 :     <Notes>A score for the largest pocket into which a ligand can bind. A
564 :     higher score makes for a better target.</Notes>
565 :     </Field>
566 :     <Field name="pass-file" type="string">
567 :     <Notes>The URL for a GIF file that shows the active sites on the protein.</Notes>
568 :     </Field>
569 :     </Fields>
570 :     </Relationship>
571 : parrello 1.45 <Relationship name="IncludesBound" from="DrugTopic" to="PDB" arity="MM">
572 : parrello 1.46 <Notes>This relationship connects a drug topic to its bound PDBs. (A separate
573 :     relationship is used to connect the free PDBs.)</Notes>
574 : parrello 1.45 </Relationship>
575 :     <Relationship name="IsBoundIn" from="PDB" to="PDB" arity="MM">
576 : parrello 1.46 <Notes>This relationship connects free PDBs to their bound counterparts.</Notes>
577 : parrello 1.41 </Relationship>
578 :     <Relationship name="DescribesProteinForFeature" from="PDB" to="Feature" arity="MM">
579 :     <Notes>This relationship connects a feature to a protein database (PDB) that
580 :     is relevant for determining drugs that target the feature.</Notes>
581 :     <Fields>
582 :     <Field name="score" type="float">
583 :     <Notes>The BLAST score for the feature as it relates to the PDB's
584 :     protein, expressed as a small positive number. Generally only a
585 :     very low BLAST score (1e-15 or less) indicates a good match.</Notes>
586 :     </Field>
587 :     <Field name="distance" type="float">
588 :     <Notes>A distance value indicating how far the PDB's protein is
589 :     from the feature's protein. A distance of 0 indicates a perfect
590 :     match.</Notes>
591 :     </Field>
592 :     </Fields>
593 :     <FromIndex>
594 :     <Notes>This index yields the Features for a PDB in order from best
595 :     score to worst.</Notes>
596 :     <IndexFields>
597 :     <IndexField name="score" order="ascending" />
598 :     </IndexFields>
599 :     </FromIndex>
600 :     <ToIndex>
601 :     <Notes>This index yields the Features for a PDB in order from best
602 :     score to worst.</Notes>
603 :     <IndexFields>
604 :     <IndexField name="score" order="ascending" />
605 :     </IndexFields>
606 :     </ToIndex>
607 :     </Relationship>
608 :     <Relationship name="ContainsTopic" from="DrugProject" to="DrugTopic" arity="1M">
609 :     <Notes>This relationship connects a drug target project to all of its
610 :     topics.</Notes>
611 :     </Relationship>
612 : parrello 1.34 <Relationship name="IsFamilyForFeature" from="Family" to="Feature" arity="MM">
613 : parrello 1.31 <Notes>This relationship connects a protein family to all of its PEGs and connects
614 :     each PEG to all of its protein families.</Notes>
615 :     </Relationship>
616 : parrello 1.6 <Relationship name="ParticipatesInCoupling" from="Feature" to="Coupling" arity="MM">
617 :     <Notes>This relationship connects a feature to all the functional couplings
618 :     in which it participates. A functional coupling is a recognition of the fact
619 :     that the features are close to each other on a chromosome, and similar
620 :     features in other genomes also tend to be close.</Notes>
621 :     <Fields>
622 :     <Field name="pos" type="int">
623 :     <Notes>Ordinal position of the feature in the coupling. Currently,
624 :     this is either "1" or "2".</Notes>
625 :     </Field>
626 :     </Fields>
627 :     <ToIndex>
628 :     <Notes>This index enables the application to view the features of
629 :     a coupling in the proper order. The order influences the way the
630 :     PCHs are examined.</Notes>
631 :     <IndexFields>
632 :     <IndexField name="pos" order="ascending" />
633 :     </IndexFields>
634 :     </ToIndex>
635 :     </Relationship>
636 : parrello 1.27 <Relationship name="IsSynonymGroupFor" from="SynonymGroup" to="Feature" arity="1M">
637 :     <Notes>This relation connects a synonym group to the features that make it
638 :     up.</Notes>
639 :     </Relationship>
640 : parrello 1.24 <Relationship name="HasFeature" from="Genome" to="Feature" arity="1M">
641 :     <Notes>This relationship connects a genome to all of its features. This
642 :     relationship is redundant in a sense, because the genome ID is part
643 :     of the feature ID; however, it makes the creation of certain queries more
644 :     convenient because you can drag in filtering information for a feature's
645 :     genome.</Notes>
646 :     <Fields>
647 :     <Field name="type" type="key-string">
648 :     <Notes>Feature type (eg. peg, rna)</Notes>
649 :     </Field>
650 :     </Fields>
651 : parrello 1.38 <FromIndex>
652 : parrello 1.24 <Notes>This index enables the application to view the features of a
653 :     Genome sorted by type.</Notes>
654 :     <IndexFields>
655 :     <IndexField name="type" order="ascending" />
656 :     </IndexFields>
657 : parrello 1.38 </FromIndex>
658 : parrello 1.24 </Relationship>
659 : parrello 1.6 <Relationship name="IsEvidencedBy" from="Coupling" to="PCH" arity="1M">
660 :     <Notes>This relationship connects a functional coupling to the physically
661 :     close homologs (PCHs) which affirm that the coupling is meaningful.</Notes>
662 :     </Relationship>
663 :     <Relationship name="UsesAsEvidence" from="PCH" to="Feature" arity="MM">
664 :     <Notes>This relationship connects a PCH to the features that represent its
665 :     evidence. Each PCH is connected to a parent coupling that relates two features
666 :     on a specific genome. The PCH's evidence that the parent coupling is functional
667 :     is the existence of two physically close features on a different genome that
668 :     correspond to the features in the coupling. Those features are found on the
669 :     far side of this relationship.</Notes>
670 :     <Fields>
671 :     <Field name="pos" type="int">
672 :     <Notes>Ordinal position of the feature in the coupling that corresponds
673 :     to our target feature. There is a one-to-one correspondence between the
674 :     features connected to the PCH by this relationship and the features
675 :     connected to the PCH's parent coupling. The ordinal position is used
676 :     to decode that relationship. Currently, this field is either "1" or
677 :     "2".</Notes>
678 :     </Field>
679 :     </Fields>
680 :     <FromIndex>
681 :     <Notes>This index enables the application to view the features of
682 :     a PCH in the proper order.</Notes>
683 :     <IndexFields>
684 :     <IndexField name="pos" order="ascending" />
685 :     </IndexFields>
686 :     </FromIndex>
687 :     </Relationship>
688 : parrello 1.1 <Relationship name="HasContig" from="Genome" to="Contig" arity="1M">
689 :     <Notes>This relationship connects a genome to the contigs that contain the actual genetic
690 :     information.</Notes>
691 :     </Relationship>
692 :     <Relationship name="ComesFrom" from="Genome" to="Source" arity="MM">
693 :     <Notes>This relationship connects a genome to the sources that mapped it. A genome can
694 :     come from a single source or from a cooperation among multiple sources.</Notes>
695 :     </Relationship>
696 :     <Relationship name="IsMadeUpOf" from="Contig" to="Sequence" arity="1M">
697 :     <Notes>A contig is stored in the database as an ordered set of sequences. By splitting the
698 :     contig into sequences, we get a performance boost from only needing to keep small portions
699 :     of a contig in memory at any one time. This relationship connects the contig to its
700 :     constituent sequences.</Notes>
701 :     <Fields>
702 :     <Field name="len" type="int">
703 : parrello 1.15 <Notes>Length of the sequence.</Notes>
704 :     </Field>
705 : parrello 1.1 <Field name="start-position" type="int">
706 : parrello 1.15 <Notes>Index (1-based) of the point in the contig where this
707 :     sequence starts.</Notes>
708 :     </Field>
709 : parrello 1.1 </Fields>
710 :     <FromIndex>
711 :     <Notes>This index enables the application to find all of the sequences in
712 : parrello 1.8 a contig in order, and makes it easier to find a particular residue section.</Notes>
713 : parrello 1.1 <IndexFields>
714 :     <IndexField name="start-position" order="ascending" />
715 :     <IndexField name="len" order="ascending" />
716 :     </IndexFields>
717 :     </FromIndex>
718 :     </Relationship>
719 :     <Relationship name="IsTargetOfAnnotation" from="Feature" to="Annotation" arity="1M">
720 :     <Notes>This relationship connects a feature to its annotations.</Notes>
721 :     </Relationship>
722 :     <Relationship name="MadeAnnotation" from="SproutUser" to="Annotation" arity="1M">
723 :     <Notes>This relationship connects an annotation to the user who made it.</Notes>
724 :     </Relationship>
725 :     <Relationship name="ParticipatesIn" from="Genome" to="Subsystem" arity="MM">
726 :     <Notes>This relationship connects subsystems to the genomes that use
727 :     it. If the subsystem has been curated for the genome, then the subsystem's roles will also be
728 :     connected to the genome features through the [b]SSCell[/b] object.</Notes>
729 : parrello 1.15 <Fields>
730 :     <Field name="variant-code" type="key-string">
731 : parrello 1.20 <Notes>Code indicating the subsystem variant to which this
732 : parrello 1.15 genome belongs. Each subsystem can have multiple variants. A variant
733 : parrello 1.20 code of [b]-1[/b] indicates that the genome does not have a functional
734 :     variant of the subsystem. A variant code of [b]0[/b] indicates that
735 :     the genome's participation is considered iffy.</Notes>
736 : parrello 1.15 </Field>
737 :     </Fields>
738 :     <ToIndex>
739 :     <Notes>This index enables the application to find all of the genomes using
740 :     a subsystem in order by variant code, which is how we wish to display them
741 :     in the spreadsheets.</Notes>
742 :     <IndexFields>
743 :     <IndexField name="variant-code" order="ascending" />
744 :     </IndexFields>
745 :     </ToIndex>
746 : parrello 1.1 </Relationship>
747 :     <Relationship name="OccursInSubsystem" from="Role" to="Subsystem" arity="MM">
748 :     <Notes>This relationship connects roles to the subsystems that implement them. </Notes>
749 : parrello 1.15 <Fields>
750 :     <Field name="column-number" type="int">
751 :     <Notes>Column number for this role in the specified subsystem's
752 :     spreadsheet.</Notes>
753 :     </Field>
754 :     </Fields>
755 :     <ToIndex>
756 :     <Notes>This index enables the application to see the subsystem roles
757 :     in column order. The ordering of the roles is usually significant,
758 :     so it is important to preserve it.</Notes>
759 :     <IndexFields>
760 :     <IndexField name="column-number" order="ascending" />
761 :     </IndexFields>
762 :     </ToIndex>
763 : parrello 1.1 </Relationship>
764 :     <Relationship name="IsGenomeOf" from="Genome" to="SSCell" arity="1M">
765 :     <Notes>This relationship connects a subsystem's spreadsheet cell to the
766 :     genome for the spreadsheet column.</Notes>
767 :     </Relationship>
768 :     <Relationship name="IsRoleOf" from="Role" to="SSCell" arity="1M">
769 :     <Notes>This relationship connects a subsystem's spreadsheet cell to the
770 :     role for the spreadsheet row.</Notes>
771 :     </Relationship>
772 :     <Relationship name="ContainsFeature" from="SSCell" to="Feature" arity="MM">
773 :     <Notes>This relationship connects a subsystem's spreadsheet cell to the
774 :     features assigned to it.</Notes>
775 : parrello 1.15 <Fields>
776 :     <Field name="cluster-number" type="int">
777 :     <Notes>ID of this feature's cluster. Clusters represent families of
778 :     related proteins participating in a subsystem.</Notes>
779 :     </Field>
780 :     </Fields>
781 :     </Relationship>
782 :     <Relationship name="IsAComponentOf" from="Compound" to="Reaction" arity="MM">
783 :     <Notes>This relationship connects a reaction to the compounds that participate
784 :     in it.</Notes>
785 :     <Fields>
786 :     <Field name="product" type="boolean">
787 :     <Notes>TRUE if the compound is a product of the reaction, FALSE if
788 :     it is a substrate. When a reaction is written on paper in
789 :     chemical notation, the substrates are left of the arrow and the
790 :     products are to the right. Sorting on this field will cause
791 :     the substrates to appear first, followed by the products. If the
792 :     reaction is reversible, then the notion of substrates and products
793 :     is not at intuitive; however, a value here of FALSE still puts the
794 :     compound left of the arrow and a value of TRUE still puts it to the
795 :     right.</Notes>
796 :     </Field>
797 : parrello 1.19 <Field name="stoichiometry" type="key-string">
798 : parrello 1.15 <Notes>Number of molecules of the compound that participate in a
799 :     single instance of the reaction. For example, if a reaction
800 : parrello 1.19 produces two water molecules, the stoichiometry of water for the
801 : parrello 1.15 reaction would be two. When a reaction is written on paper in
802 : parrello 1.19 chemical notation, the stoichiometry is the number next to the
803 : parrello 1.15 chemical formula of the compound.</Notes>
804 :     </Field>
805 :     <Field name="main" type="boolean">
806 :     <Notes>TRUE if this compound is one of the main participants in
807 :     the reaction, else FALSE. It is permissible for none of the
808 :     compounds in the reaction to be considered main, in which
809 :     case this value would be FALSE for all of the relevant
810 :     compounds.</Notes>
811 :     </Field>
812 :     <Field name="loc" type="key-string">
813 :     <Notes>An optional character string that indicates the relative
814 :     position of this compound in the reaction's chemical formula. The
815 :     location affects the way the compounds present as we cross the
816 :     relationship from the reaction side. The product/substrate flag
817 :     comes first, then the value of this field, then the main flag.
818 :     The default value is an empty string; however, the empty string
819 :     sorts first, so if this field is used, it should probably be
820 :     used for every compound in the reaction.</Notes>
821 :     </Field>
822 : parrello 1.19 <Field name="discriminator" type="int">
823 :     <Notes>A unique ID for this record. The discriminator does not
824 :     provide any useful data, but it prevents identical records from
825 :     being collapsed by the SELECT DISTINCT command used by ERDB to
826 :     retrieve data.</Notes>
827 :     </Field>
828 : parrello 1.15 </Fields>
829 :     <ToIndex>
830 :     <Notes>This index presents the compounds in the reaction in the
831 :     order they should be displayed when writing it in chemical notation.
832 :     All the substrates appear before all the products, and within that
833 :     ordering, the main compounds appear first.</Notes>
834 : parrello 1.19 <IndexFields>
835 :     <IndexField name="product" order="ascending" />
836 :     <IndexField name="loc" order="ascending" />
837 :     <IndexField name="main" order="descending" />
838 :     </IndexFields>
839 : parrello 1.15 </ToIndex>
840 : parrello 1.1 </Relationship>
841 :     <Relationship name="IsLocatedIn" from="Feature" to="Contig" arity="MM">
842 :     <Notes>This relationship connects a feature to the contig segments that work together
843 :     to effect it. The segments are numbered sequentially starting from 1. The database is
844 :     required to place an upper limit on the length of each segment. If a segment is longer
845 :     than the maximum, it can be broken into smaller bits.
846 :     [p]The upper limit enables applications to locate all features that contain a specific
847 :     residue. For example, if the upper limit is 100 and we are looking for a feature that
848 :     contains residue 234 of contig [b]ABC[/b], we can look for features with a begin point
849 :     between 135 and 333. The results can then be filtered by direction and length of the
850 :     segment.</Notes>
851 :     <Fields>
852 :     <Field name="locN" type="int">
853 : parrello 1.8 <Notes>Sequence number of this segment.</Notes>
854 :     </Field>
855 : parrello 1.1 <Field name="beg" type="int">
856 : parrello 1.8 <Notes>Index (1-based) of the first residue in the contig that
857 :     belongs to the segment.</Notes>
858 :     </Field>
859 : parrello 1.1 <Field name="len" type="int">
860 : parrello 1.8 <Notes>Number of residues in the segment. A length of 0 identifies
861 :     a specific point between residues. This is the point before the residue if the direction
862 :     is forward and the point after the residue if the direction is backward.</Notes>
863 :     </Field>
864 : parrello 1.1 <Field name="dir" type="char">
865 : parrello 1.8 <Notes>Direction of the segment: [b]+[/b] if it is forward and
866 :     [b]-[/b] if it is backward.</Notes>
867 :     </Field>
868 : parrello 1.1 </Fields>
869 : parrello 1.45 <FromIndex>
870 : parrello 1.1 <Notes>This index allows the application to find all the segments of a feature in
871 : parrello 1.8 the proper order.</Notes>
872 : parrello 1.1 <IndexFields>
873 :     <IndexField name="locN" order="ascending" />
874 :     </IndexFields>
875 :     </FromIndex>
876 :     <ToIndex>
877 :     <Notes>This index is the one used by applications to find all the feature
878 :     segments that contain a specific residue.</Notes>
879 :     <IndexFields>
880 :     <IndexField name="beg" order="ascending" />
881 :     </IndexFields>
882 :     </ToIndex>
883 :     </Relationship>
884 : parrello 1.8 <Relationship name="HasProperty" from="Feature" to="Property" arity="MM">
885 :     <Notes>This relationship connects a feature to its known property values.
886 :     The relationship contains text data that indicates the paper or organization
887 :     that discovered evidence that the feature possesses the property. So, for
888 :     example, if two papers presented evidence that a feature is essential,
889 :     there would be an instance of this relationship for both.</Notes>
890 :     <Fields>
891 :     <Field name="evidence" type="text">
892 :     <Notes>URL or citation of the paper or
893 :     institution that reported evidence of the relevant feature possessing
894 :     the specified property value.</Notes>
895 :     </Field>
896 :     </Fields>
897 :     </Relationship>
898 :     <Relationship name="RoleOccursIn" from="Role" to="Diagram" arity="MM">
899 :     <Notes>This relationship connects a role to the diagrams on which it
900 :     appears. A role frequently identifies an enzyme, and can appear in many
901 :     diagrams. A diagram generally contains many different roles.</Notes>
902 :     </Relationship>
903 :     <Relationship name="HasSSCell" from="Subsystem" to="SSCell" arity="1M">
904 :     <Notes>This relationship connects a subsystem to the spreadsheet cells
905 :     used to analyze and display it. The cells themselves can be thought of
906 :     as a grid with Roles on one axis and Genomes on the other. The
907 :     various features of the subsystem are then assigned to the cells.</Notes>
908 :     </Relationship>
909 :     <Relationship name="IsTrustedBy" from="SproutUser" to="SproutUser" arity="MM">
910 :     <Notes>This relationship identifies the users trusted by each
911 :     particular user. When viewing functional assignments, the
912 :     assignment displayed is the most recent one by a user trusted
913 :     by the current user. The current user implicitly trusts himself.
914 :     If no trusted users are specified in the database, the user
915 :     also implicitly trusts the user [b]FIG[/b].</Notes>
916 :     </Relationship>
917 : parrello 1.15 <Relationship name="ConsistsOfRoles" from="RoleSubset" to="Role" arity="MM">
918 :     <Notes>This relationship connects a role subset to the roles that it covers.
919 :     A subset is, essentially, a named group of roles belonging to a specific
920 :     subsystem, and this relationship effects that. Note that will a role
921 :     may belong to many subsystems, a subset belongs to only one subsystem,
922 :     and all roles in the subset must have that subsystem in common.</Notes>
923 :     </Relationship>
924 :     <Relationship name="ConsistsOfGenomes" from="GenomeSubset" to="Genome" arity="MM">
925 :     <Notes>This relationship connects a subset to the genomes that it covers.
926 :     A subset is, essentially, a named group of genomes participating in a specific
927 :     subsystem, and this relationship effects that. Note that while a genome
928 :     may belong to many subsystems, a subset belongs to only one subsystem,
929 :     and all genomes in the subset must have that subsystem in common.</Notes>
930 :     </Relationship>
931 :     <Relationship name="HasRoleSubset" from="Subsystem" to="RoleSubset" arity="1M">
932 :     <Notes>This relationship connects a subsystem to its constituent
933 :     role subsets. Note that some roles in a subsystem may not belong to a
934 :     subset, so the relationship between roles and subsystems cannot be
935 :     derived from the relationships going through the subset.</Notes>
936 :     </Relationship>
937 :     <Relationship name="HasGenomeSubset" from="Subsystem" to="GenomeSubset" arity="1M">
938 :     <Notes>This relationship connects a subsystem to its constituent
939 :     genome subsets. Note that some genomes in a subsystem may not belong to a
940 :     subset, so the relationship between genomes and subsystems cannot be
941 :     derived from the relationships going through the subset.</Notes>
942 :     </Relationship>
943 :     <Relationship name="Catalyzes" from="Role" to="Reaction" arity="MM">
944 :     <Notes>This relationship connects a role to the reactions it catalyzes.
945 :     The purpose of a role is to create proteins that trigger certain
946 :     chemical reactions. A single reaction can be triggered by many roles,
947 :     and a role can trigger many reactions.</Notes>
948 :     </Relationship>
949 : parrello 1.39 <Relationship name="HasRoleInSubsystem" from="Feature" to="Subsystem" arity="MM">
950 :     <Notes>This relationship connects a feature to the subsystems in which it
951 :     participates. This is technically redundant information, but it is used
952 :     so often that it deserves its own table.</Notes>
953 : parrello 1.40 <Fields>
954 :     <Field name="genome" type="name-string">
955 :     <Notes>ID of the genome containing the feature</Notes>
956 :     </Field>
957 :     <Field name="type" type="key-string">
958 :     <Notes>Feature type (eg. peg, rna)</Notes>
959 :     </Field>
960 :     </Fields>
961 :     <ToIndex>
962 :     <Notes>This index enables the application to view the features of a
963 :     subsystem sorted by genome and feature type.</Notes>
964 :     <IndexFields>
965 :     <IndexField name="genome" order="ascending" />
966 :     <IndexField name="type" order="ascending" />
967 :     </IndexFields>
968 :     </ToIndex>
969 : parrello 1.39 </Relationship>
970 : parrello 1.1 </Relationships>
971 :     </Database>

MCS Webmaster
ViewVC Help
Powered by ViewVC 1.0.3