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

Diff of /Sprout/SproutDBD.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.12, Tue Sep 13 03:50:59 2005 UTC revision 1.40, Wed Sep 27 12:58:18 2006 UTC
# Line 36  Line 36 
36                      <DataGen pass="2">join('; ', (RandParam('bacteria', 'archaea', 'eukaryote', 'virus', 'environmental'),                      <DataGen pass="2">join('; ', (RandParam('bacteria', 'archaea', 'eukaryote', 'virus', 'environmental'),
37                                                    ListGen('PKVKVKVK', 5), $this->{genus}, $this->{species}))</DataGen>                                                    ListGen('PKVKVKVK', 5), $this->{genus}, $this->{species}))</DataGen>
38                  </Field>                  </Field>
39                    <Field name="primary-group" type="name-string">
40                        <Notes>The primary NMPDR group for this organism. There is always exactly one NMPDR group
41                        (either based on the organism name or the default value "Supporting"), whereas there can be
42                        multiple named groups or even none.</Notes>
43                    </Field>
44                  <Field name="group-name" type="name-string" relation="GenomeGroups">                  <Field name="group-name" type="name-string" relation="GenomeGroups">
45                      <Notes>The group identifies a special grouping of organisms that would be displayed on a particular                      <Notes>The group identifies a special grouping of organisms that would be displayed on a particular
46                      page or of particular interest to a research group or web site. A single genome can belong to multiple                      page or of particular interest to a research group or web site. A single genome can belong to multiple
# Line 43  Line 48 
48                  </Field>                  </Field>
49              </Fields>              </Fields>
50              <Indexes>              <Indexes>
51                  <Index>                  <Index Unique="false">
52                      <Notes>This index allows the applications to find all genomes associated with                      <Notes>This index allows the applications to find all genomes associated with
53                      a specific access code, so that a complete list of the genomes users can view                      a specific access code, so that a complete list of the genomes users can view
54                      may be generated.</Notes>                      may be generated.</Notes>
# Line 55  Line 60 
60                      </IndexFields>                      </IndexFields>
61                  </Index>                  </Index>
62                  <Index Unique="false">                  <Index Unique="false">
63                        <Notes>This index allows the applications to find all genomes associated with
64                        a specific primary (NMPDR) group.</Notes>
65                        <IndexFields>
66                            <IndexField name="primary-group" order="ascending" />
67                            <IndexField name="genus" order="ascending" />
68                            <IndexField name="species" order="ascending" />
69                            <IndexField name="unique-characterization" order="ascending" />
70                        </IndexFields>
71                    </Index>
72                    <Index Unique="false">
73                      <Notes>This index allows the applications to find all genomes for a particular                      <Notes>This index allows the applications to find all genomes for a particular
74                      species.</Notes>                      species.</Notes>
75                      <IndexFields>                      <IndexFields>
# Line 111  Line 126 
126                  </Field>                  </Field>
127              </Fields>              </Fields>
128          </Entity>          </Entity>
129          <Entity name="Feature" keyType="name-string">          <Entity name="Feature" keyType="id-string">
130              <Notes>A [i]feature[/i] is a part of a genome that is of special interest. Features              <Notes>A [i]feature[/i] is a part of a genome that is of special interest. Features
131              may be spread across multiple contigs of a genome, but never across more than              may be spread across multiple contigs of a genome, but never across more than
132              one genome. Features can be assigned to roles via spreadsheet cells,              one genome. Features can be assigned to roles via spreadsheet cells,
# Line 121  Line 136 
136                      <Notes>Code indicating the type of this feature.</Notes>                      <Notes>Code indicating the type of this feature.</Notes>
137                      <DataGen>RandParam('peg','rna')</DataGen>                      <DataGen>RandParam('peg','rna')</DataGen>
138                  </Field>                  </Field>
139                  <Field name="alias" type="name-string" relation="FeatureAlias">                  <Field name="alias" type="medium-string" relation="FeatureAlias">
140                      <Notes>Alternative name for this feature. A feature can have many aliases.</Notes>                      <Notes>Alternative name for this feature. A feature can have many aliases.</Notes>
141                      <DataGen testCount="3">StringGen('Pgi|99999', 'Puni|XXXXXX', 'PAAAAAA999')</DataGen>                      <DataGen testCount="3">StringGen('Pgi|99999', 'Puni|XXXXXX', 'PAAAAAA999')</DataGen>
142                  </Field>                  </Field>
# Line 141  Line 156 
156                      <Notes>TRUE if this feature is still considered valid, FALSE if it has been logically deleted.</Notes>                      <Notes>TRUE if this feature is still considered valid, FALSE if it has been logically deleted.</Notes>
157                      <DataGen>1</DataGen>                      <DataGen>1</DataGen>
158                  </Field>                  </Field>
159                    <Field name="assignment" type="text">
160                        <Notes>This is the primary functional assignment for the feature.</Notes>
161                    </Field>
162                  <Field name="link" type="text" relation="FeatureLink">                  <Field name="link" type="text" relation="FeatureLink">
163                      <Notes>Web hyperlink for this feature. A feature have no hyperlinks or it can have many. The                      <Notes>Web hyperlink for this feature. A feature have no hyperlinks or it can have many. The
164                      links are to other websites that have useful about the gene that the feature represents, and                      links are to other websites that have useful about the gene that the feature represents, and
# Line 159  Line 177 
177                  </Index>                  </Index>
178              </Indexes>              </Indexes>
179          </Entity>          </Entity>
180            <Entity name="SynonymGroup" keyType="id-string">
181                <Notes>A [i]synonym group[/i] represents a group of features. Substantially identical features
182                are mapped to the same synonym group, and this information is used to expand similarities.</Notes>
183            </Entity>
184          <Entity name="Role" keyType="string">          <Entity name="Role" keyType="string">
185              <Notes>A [i]role[/i] describes a biological function that may be fulfilled by a feature.              <Notes>A [i]role[/i] describes a biological function that may be fulfilled by a feature.
186              One of the main goals of the database is to record the roles of the various features.</Notes>              One of the main goals of the database is to record the roles of the various features.</Notes>
187              <Fields>              <Fields>
188                  <Field name="name" type="string" relation="RoleName">                  <Field name="EC" type="string" relation="RoleEC">
189                      <Notes>Expanded name of the role. This value is generally only available for roles                      <Notes>EC code for this role.</Notes>
                     that are encoded as EC numbers.</Notes>  
190                      <DataGen testCount="1">StringGen(IntGen(20,40)) . "(" . $this->{id} . ")"</DataGen>                      <DataGen testCount="1">StringGen(IntGen(20,40)) . "(" . $this->{id} . ")"</DataGen>
191                  </Field>                  </Field>
192                    <Field name="abbr" type="name-string">
193                        <Notes>Abbreviated name for the role, generally non-unique, but useful
194                        in column headings for HTML tables.</Notes>
195                    </Field>
196              </Fields>              </Fields>
197                <Indexes>
198                    <Index>
199                        <Notes>This index allows the user to find the role corresponding to
200                        an EC number.</Notes>
201                        <IndexFields>
202                            <IndexField name="EC" order="ascending" />
203                        </IndexFields>
204                    </Index>
205                </Indexes>
206          </Entity>          </Entity>
207          <Entity name="Annotation" keyType="name-string">          <Entity name="Annotation" keyType="name-string">
208              <Notes>An [i]annotation[/i] contains supplementary information about a feature. Annotations              <Notes>An [i]annotation[/i] contains supplementary information about a feature. Annotations
209              are currently the only objects that may be inserted directly into the database. All other              are currently the only objects that may be inserted directly into the database. All other
210              information is loaded from data exported by the SEED.              information is loaded from data exported by the SEED.</Notes>
             [p]Each annotation is associated with a target [b]Feature[/b]. The key of the annotation  
             is the target feature ID followed by a timestamp.</Notes>  
211              <Fields>              <Fields>
212                  <Field name="time" type="date">                  <Field name="time" type="date">
213                      <Notes>Date and time of the annotation.</Notes>                      <Notes>Date and time of the annotation.</Notes>
# Line 184  Line 216 
216                      <Notes>Text of the annotation.</Notes>                      <Notes>Text of the annotation.</Notes>
217                  </Field>                  </Field>
218              </Fields>              </Fields>
219                <Indexes>
220                    <Index>
221                        <Notes>This index allows the user to find recent annotations.</Notes>
222                        <IndexFields>
223                            <IndexField name="time" order="descending" />
224                        </IndexFields>
225                    </Index>
226                </Indexes>
227            </Entity>
228            <Entity name="Reaction" keyType="key-string">
229                <Notes>A [i]reaction[/i] is a chemical process catalyzed by a protein. The reaction ID
230                is generally a small number preceded by a letter.</Notes>
231                <Fields>
232                    <Field name="url" type="string" relation="ReactionURL">
233                        <Notes>HTML string containing a link to a web location that describes the
234                        reaction. This field is optional.</Notes>
235                    </Field>
236                    <Field name="rev" type="boolean">
237                        <Notes>TRUE if this reaction is reversible, else FALSE</Notes>
238                    </Field>
239                </Fields>
240            </Entity>
241            <Entity name="Compound" keyType="name-string">
242                <Notes>A [i]compound[/i] is a chemical that participates in a reaction.
243                All compounds have a unique ID and may also have one or more names.</Notes>
244                <Fields>
245                    <Field name="name-priority" type="int" relation="CompoundName">
246                        <Notes>Priority of a compound name. The name with the loweset
247                        priority is the main name of this compound.</Notes>
248                    </Field>
249                    <Field name="name" type="name-string" relation="CompoundName">
250                        <Notes>Descriptive name for the compound. A compound may
251                        have several names.</Notes>
252                    </Field>
253                    <Field name="cas-id" type="name-string" relation="CompoundCAS">
254                        <Notes>Chemical Abstract Service ID for this compound (optional).</Notes>
255                    </Field>
256                    <Field name="label" type="name-string">
257                        <Notes>Name used in reaction display strings.
258                        It is the same as the name possessing a priority of 1, but it is placed
259                        here to speed up the query used to create the display strings.</Notes>
260                    </Field>
261                </Fields>
262                <Indexes>
263                    <Index>
264                        <Notes>This index allows the user to find the compound corresponding to
265                        the specified name.</Notes>
266                        <IndexFields>
267                            <IndexField name="name" order="ascending" />
268                        </IndexFields>
269                    </Index>
270                    <Index>
271                        <Notes>This index allows the user to find the compound corresponding to
272                        the specified CAS ID.</Notes>
273                        <IndexFields>
274                            <IndexField name="cas-id" order="ascending" />
275                        </IndexFields>
276                    </Index>
277                    <Index>
278                        <Notes>This index allows the user to access the compound names in
279                        priority order.</Notes>
280                        <IndexFields>
281                            <IndexField name="id" order="ascending" />
282                            <IndexField name="name-priority" order="ascending" />
283                        </IndexFields>
284                    </Index>
285                </Indexes>
286          </Entity>          </Entity>
287          <Entity name="Subsystem" keyType="string">          <Entity name="Subsystem" keyType="string">
288              <Notes>A [i]subsystem[/i] is a collection of roles that work together in a cell. Identification of subsystems              <Notes>A [i]subsystem[/i] is a collection of roles that work together in a cell. Identification of subsystems
289              is an important tool for recognizing parallel genetic features in different organisms.</Notes>              is an important tool for recognizing parallel genetic features in different organisms.</Notes>
290                <Fields>
291                    <Field name="curator" type="string">
292                        <Notes>Name of the person currently in charge of the subsystem.</Notes>
293                    </Field>
294                    <Field name="notes" type="text">
295                        <Notes>Descriptive notes about the subsystem.</Notes>
296                    </Field>
297                    <Field name="classification" type="string" relation="SubsystemClass">
298                        <Notes>General classification data about the subsystem.</Notes>
299                    </Field>
300                </Fields>
301            </Entity>
302            <Entity name="RoleSubset" keyType="string">
303                <Notes>A [i]role subset[/i] is a named collection of roles in a particular subsystem. The
304                subset names are generally very short, non-unique strings. The ID of the parent
305                subsystem is prefixed to the subset ID in order to make it unique.</Notes>
306            </Entity>
307            <Entity name="GenomeSubset" keyType="string">
308                <Notes>A [i]genome subset[/i] is a named collection of genomes that participate
309                in a particular subsystem. The subset names are generally very short, non-unique
310                strings. The ID of the parent subsystem is prefixed to the subset ID in order
311                to make it unique.</Notes>
312          </Entity>          </Entity>
313          <Entity name="SSCell" keyType="name-string">          <Entity name="SSCell" keyType="hash-string">
314              <Notes>Part of the process of locating and assigning features is creating a spreadsheet of              <Notes>Part of the process of locating and assigning features is creating a spreadsheet of
315              genomes and roles to which features are assigned. A [i]spreadsheet cell[/i] represents one              genomes and roles to which features are assigned. A [i]spreadsheet cell[/i] represents one
316              of the positions on the spreadsheet.</Notes>              of the positions on the spreadsheet.</Notes>
# Line 270  Line 391 
391                      </Field>                      </Field>
392                  </Fields>                  </Fields>
393          </Entity>          </Entity>
394          <Entity name="Coupling" keyType="medium-string">          <Entity name="Coupling" keyType="id-string">
395              <Notes>A coupling is a relationship between two features. The features are              <Notes>A coupling is a relationship between two features. The features are
396              physically close on the contig, and there is evidence that they generally              physically close on the contig, and there is evidence that they generally
397              belong together. The key of this entity is formed by combining the coupled              belong together. The key of this entity is formed by combining the coupled
# Line 286  Line 407 
407                  </Field>                  </Field>
408              </Fields>              </Fields>
409          </Entity>          </Entity>
410          <Entity name="PCH" keyType="string">          <Entity name="PCH" keyType="counter">
411              <Notes>A PCH (physically close homolog) connects a clustering (which is a              <Notes>A PCH (physically close homolog) connects a clustering (which is a
412              pair of physically close features on a contig) to a second pair of physically              pair of physically close features on a contig) to a second pair of physically
413              close features that are similar to the first. Essentially, the PCH is a              close features that are similar to the first. Essentially, the PCH is a
# Line 294  Line 415 
415              are similar to the second clustering's features. The simplest model for              are similar to the second clustering's features. The simplest model for
416              this would be to simply relate clusterings to each other; however, not all              this would be to simply relate clusterings to each other; however, not all
417              physically close pairs qualify as clusterings, so we relate a clustering to              physically close pairs qualify as clusterings, so we relate a clustering to
418              a pair of features. The key is the clustering key followed by the IDs              a pair of features. The key a unique ID number.</Notes>
             of the features in the second pair.</Notes>  
419              <Fields>              <Fields>
420                  <Field name="used" type="boolean">                  <Field name="used" type="boolean">
421                      <Notes>TRUE if this PCH is used in scoring the attached clustering,                      <Notes>TRUE if this PCH is used in scoring the attached clustering,
# Line 306  Line 426 
426                  </Field>                  </Field>
427              </Fields>              </Fields>
428          </Entity>          </Entity>
429            <Entity name="Family" keyType="id-string">
430                <Notes>A family is a group of homologous PEGs believed to have the same function. Protein
431                families provide a mechanism for verifying the accuracy of functional assignments
432                and are also used in determining phylogenetic trees.</Notes>
433                <Fields>
434                    <Field name="function" type="text">
435                        <Notes>The functional assignment expected for all PEGs in this family.</Notes>
436                    </Field>
437                    <Field name="size" type="int">
438                        <Notes>The number of proteins in this family. This may be larger than the
439                        number of PEGs included in the family, since the family may also contain external
440                        IDs.</Notes>
441                    </Field>
442                </Fields>
443            </Entity>
444      </Entities>      </Entities>
445      <Relationships>      <Relationships>
446            <Relationship name="IsFamilyForFeature" from="Family" to="Feature" arity="MM">
447                <Notes>This relationship connects a protein family to all of its PEGs and connects
448                each PEG to all of its protein families.</Notes>
449            </Relationship>
450          <Relationship name="ParticipatesInCoupling" from="Feature" to="Coupling" arity="MM">          <Relationship name="ParticipatesInCoupling" from="Feature" to="Coupling" arity="MM">
451              <Notes>This relationship connects a feature to all the functional couplings              <Notes>This relationship connects a feature to all the functional couplings
452              in which it participates. A functional coupling is a recognition of the fact              in which it participates. A functional coupling is a recognition of the fact
# Line 328  Line 467 
467                  </IndexFields>                  </IndexFields>
468              </ToIndex>              </ToIndex>
469          </Relationship>          </Relationship>
470            <Relationship name="IsSynonymGroupFor" from="SynonymGroup" to="Feature" arity="1M">
471                <Notes>This relation connects a synonym group to the features that make it
472                up.</Notes>
473            </Relationship>
474            <Relationship name="HasFeature" from="Genome" to="Feature" arity="1M">
475                <Notes>This relationship connects a genome to all of its features. This
476                relationship is redundant in a sense, because the genome ID is part
477                of the feature ID; however, it makes the creation of certain queries more
478                convenient because you can drag in filtering information for a feature's
479                genome.</Notes>
480                <Fields>
481                    <Field name="type" type="key-string">
482                        <Notes>Feature type (eg. peg, rna)</Notes>
483                    </Field>
484                </Fields>
485                <FromIndex>
486                    <Notes>This index enables the application to view the features of a
487                    Genome sorted by type.</Notes>
488                    <IndexFields>
489                        <IndexField name="type" order="ascending" />
490                    </IndexFields>
491                </FromIndex>
492            </Relationship>
493          <Relationship name="IsEvidencedBy" from="Coupling" to="PCH" arity="1M">          <Relationship name="IsEvidencedBy" from="Coupling" to="PCH" arity="1M">
494              <Notes>This relationship connects a functional coupling to the physically              <Notes>This relationship connects a functional coupling to the physically
495              close homologs (PCHs) which affirm that the coupling is meaningful.</Notes>              close homologs (PCHs) which affirm that the coupling is meaningful.</Notes>
# Line 398  Line 560 
560              <Notes>This relationship connects subsystems to the genomes that use              <Notes>This relationship connects subsystems to the genomes that use
561              it. If the subsystem has been curated for the genome, then the subsystem's roles will also be              it. If the subsystem has been curated for the genome, then the subsystem's roles will also be
562              connected to the genome features through the [b]SSCell[/b] object.</Notes>              connected to the genome features through the [b]SSCell[/b] object.</Notes>
563                <Fields>
564                    <Field name="variant-code" type="key-string">
565                        <Notes>Code indicating the subsystem variant to which this
566                        genome belongs. Each subsystem can have multiple variants. A variant
567                        code of [b]-1[/b] indicates that the genome does not have a functional
568                        variant of the subsystem. A variant code of [b]0[/b] indicates that
569                        the genome's participation is considered iffy.</Notes>
570                    </Field>
571                </Fields>
572                <ToIndex>
573                    <Notes>This index enables the application to find all of the genomes using
574                    a subsystem in order by variant code, which is how we wish to display them
575                    in the spreadsheets.</Notes>
576                    <IndexFields>
577                        <IndexField name="variant-code" order="ascending" />
578                    </IndexFields>
579                </ToIndex>
580          </Relationship>          </Relationship>
581          <Relationship name="OccursInSubsystem" from="Role" to="Subsystem" arity="MM">          <Relationship name="OccursInSubsystem" from="Role" to="Subsystem" arity="MM">
582              <Notes>This relationship connects roles to the subsystems that implement them. </Notes>              <Notes>This relationship connects roles to the subsystems that implement them. </Notes>
583                <Fields>
584                    <Field name="column-number" type="int">
585                        <Notes>Column number for this role in the specified subsystem's
586                        spreadsheet.</Notes>
587                    </Field>
588                </Fields>
589                <ToIndex>
590                    <Notes>This index enables the application to see the subsystem roles
591                    in column order. The ordering of the roles is usually significant,
592                    so it is important to preserve it.</Notes>
593                    <IndexFields>
594                        <IndexField name="column-number" order="ascending" />
595                    </IndexFields>
596                </ToIndex>
597          </Relationship>          </Relationship>
598          <Relationship name="IsGenomeOf" from="Genome" to="SSCell" arity="1M">          <Relationship name="IsGenomeOf" from="Genome" to="SSCell" arity="1M">
599              <Notes>This relationship connects a subsystem's spreadsheet cell to the              <Notes>This relationship connects a subsystem's spreadsheet cell to the
# Line 413  Line 606 
606          <Relationship name="ContainsFeature" from="SSCell" to="Feature" arity="MM">          <Relationship name="ContainsFeature" from="SSCell" to="Feature" arity="MM">
607              <Notes>This relationship connects a subsystem's spreadsheet cell to the              <Notes>This relationship connects a subsystem's spreadsheet cell to the
608              features assigned to it.</Notes>              features assigned to it.</Notes>
609                <Fields>
610                    <Field name="cluster-number" type="int">
611                        <Notes>ID of this feature's cluster. Clusters represent families of
612                        related proteins participating in a subsystem.</Notes>
613                    </Field>
614                </Fields>
615            </Relationship>
616            <Relationship name="IsAComponentOf" from="Compound" to="Reaction" arity="MM">
617                <Notes>This relationship connects a reaction to the compounds that participate
618                in it.</Notes>
619                <Fields>
620                    <Field name="product" type="boolean">
621                        <Notes>TRUE if the compound is a product of the reaction, FALSE if
622                        it is a substrate. When a reaction is written on paper in
623                        chemical notation, the substrates are left of the arrow and the
624                        products are to the right. Sorting on this field will cause
625                        the substrates to appear first, followed by the products. If the
626                        reaction is reversible, then the notion of substrates and products
627                        is not at intuitive; however, a value here of FALSE still puts the
628                        compound left of the arrow and a value of TRUE still puts it to the
629                        right.</Notes>
630                    </Field>
631                    <Field name="stoichiometry" type="key-string">
632                        <Notes>Number of molecules of the compound that participate in a
633                        single instance of the reaction. For example, if a reaction
634                        produces two water molecules, the stoichiometry of water for the
635                        reaction would be two. When a reaction is written on paper in
636                        chemical notation, the stoichiometry is the number next to the
637                        chemical formula of the compound.</Notes>
638                    </Field>
639                    <Field name="main" type="boolean">
640                        <Notes>TRUE if this compound is one of the main participants in
641                        the reaction, else FALSE. It is permissible for none of the
642                        compounds in the reaction to be considered main, in which
643                        case this value would be FALSE for all of the relevant
644                        compounds.</Notes>
645                    </Field>
646                    <Field name="loc" type="key-string">
647                        <Notes>An optional character string that indicates the relative
648                        position of this compound in the reaction's chemical formula. The
649                        location affects the way the compounds present as we cross the
650                        relationship from the reaction side. The product/substrate flag
651                        comes first, then the value of this field, then the main flag.
652                        The default value is an empty string; however, the empty string
653                        sorts first, so if this field is used, it should probably be
654                        used for every compound in the reaction.</Notes>
655                    </Field>
656                    <Field name="discriminator" type="int">
657                        <Notes>A unique ID for this record. The discriminator does not
658                        provide any useful data, but it prevents identical records from
659                        being collapsed by the SELECT DISTINCT command used by ERDB to
660                        retrieve data.</Notes>
661                    </Field>
662                </Fields>
663                <ToIndex>
664                    <Notes>This index presents the compounds in the reaction in the
665                    order they should be displayed when writing it in chemical notation.
666                    All the substrates appear before all the products, and within that
667                    ordering, the main compounds appear first.</Notes>
668                    <IndexFields>
669                        <IndexField name="product" order="ascending" />
670                        <IndexField name="loc" order="ascending" />
671                        <IndexField name="main" order="descending" />
672                    </IndexFields>
673                </ToIndex>
674          </Relationship>          </Relationship>
675          <Relationship name="IsLocatedIn" from="Feature" to="Contig" arity="MM">          <Relationship name="IsLocatedIn" from="Feature" to="Contig" arity="MM">
676              <Notes>This relationship connects a feature to the contig segments that work together              <Notes>This relationship connects a feature to the contig segments that work together
# Line 457  Line 715 
715                  </IndexFields>                  </IndexFields>
716              </ToIndex>              </ToIndex>
717          </Relationship>          </Relationship>
         <Relationship name="IsBidirectionalBestHitOf" from="Feature" to="Feature" arity="MM">  
             <Notes>This relationship is one of two that relate features to each other. It  
             connects features that are very similar but on separate genomes. A  
             bidirectional best hit relationship exists between two features [b]A[/b]  
             and [b]B[/b] if [b]A[/b] is the best match for [b]B[/b] on [b]A[/b]'s genome  
             and [b]B[/b] is the best match for [b]A[/b] on [b]B[/b]'s genome. </Notes>  
             <Fields>  
                 <Field name="genome" type="name-string">  
                     <Notes>ID of the genome containing the target (to) feature.</Notes>  
                 </Field>  
                 <Field name="sc" type="float">  
                     <Notes>score for this relationship</Notes>  
                 </Field>  
             </Fields>  
             <FromIndex>  
                 <Notes>This index allows the application to find a feature's best hit for  
                 a specific target genome.</Notes>  
                 <IndexFields>  
                     <IndexField name="genome" order="ascending" />  
                 </IndexFields>  
             </FromIndex>  
         </Relationship>  
718          <Relationship name="HasProperty" from="Feature" to="Property" arity="MM">          <Relationship name="HasProperty" from="Feature" to="Property" arity="MM">
719              <Notes>This relationship connects a feature to its known property values.              <Notes>This relationship connects a feature to its known property values.
720              The relationship contains text data that indicates the paper or organization              The relationship contains text data that indicates the paper or organization
# Line 512  Line 748 
748              If no trusted users are specified in the database, the user              If no trusted users are specified in the database, the user
749              also implicitly trusts the user [b]FIG[/b].</Notes>              also implicitly trusts the user [b]FIG[/b].</Notes>
750          </Relationship>          </Relationship>
751            <Relationship name="ConsistsOfRoles" from="RoleSubset" to="Role" arity="MM">
752                <Notes>This relationship connects a role subset to the roles that it covers.
753                A subset is, essentially, a named group of roles belonging to a specific
754                subsystem, and this relationship effects that. Note that will a role
755                may belong to many subsystems, a subset belongs to only one subsystem,
756                and all roles in the subset must have that subsystem in common.</Notes>
757            </Relationship>
758            <Relationship name="ConsistsOfGenomes" from="GenomeSubset" to="Genome" arity="MM">
759                <Notes>This relationship connects a subset to the genomes that it covers.
760                A subset is, essentially, a named group of genomes participating in a specific
761                subsystem, and this relationship effects that. Note that while a genome
762                may belong to many subsystems, a subset belongs to only one subsystem,
763                and all genomes in the subset must have that subsystem in common.</Notes>
764            </Relationship>
765            <Relationship name="HasRoleSubset" from="Subsystem" to="RoleSubset" arity="1M">
766                <Notes>This relationship connects a subsystem to its constituent
767                role subsets. Note that some roles in a subsystem may not belong to a
768                subset, so the relationship between roles and subsystems cannot be
769                derived from the relationships going through the subset.</Notes>
770            </Relationship>
771            <Relationship name="HasGenomeSubset" from="Subsystem" to="GenomeSubset" arity="1M">
772                <Notes>This relationship connects a subsystem to its constituent
773                genome subsets. Note that some genomes in a subsystem may not belong to a
774                subset, so the relationship between genomes and subsystems cannot be
775                derived from the relationships going through the subset.</Notes>
776            </Relationship>
777            <Relationship name="Catalyzes" from="Role" to="Reaction" arity="MM">
778                <Notes>This relationship connects a role to the reactions it catalyzes.
779                The purpose of a role is to create proteins that trigger certain
780                chemical reactions. A single reaction can be triggered by many roles,
781                and a role can trigger many reactions.</Notes>
782            </Relationship>
783            <Relationship name="HasRoleInSubsystem" from="Feature" to="Subsystem" arity="MM">
784                <Notes>This relationship connects a feature to the subsystems in which it
785                participates. This is technically redundant information, but it is used
786                so often that it deserves its own table.</Notes>
787                <Fields>
788                    <Field name="genome" type="name-string">
789                        <Notes>ID of the genome containing the feature</Notes>
790                    </Field>
791                    <Field name="type" type="key-string">
792                        <Notes>Feature type (eg. peg, rna)</Notes>
793                    </Field>
794                </Fields>
795                <ToIndex>
796                    <Notes>This index enables the application to view the features of a
797                    subsystem sorted by genome and feature type.</Notes>
798                    <IndexFields>
799                        <IndexField name="genome" order="ascending" />
800                        <IndexField name="type" order="ascending" />
801                    </IndexFields>
802                </ToIndex>
803            </Relationship>
804      </Relationships>      </Relationships>
805  </Database>  </Database>

Legend:
Removed from v.1.12  
changed lines
  Added in v.1.40

MCS Webmaster
ViewVC Help
Powered by ViewVC 1.0.3