418 |
</IndexFields> |
</IndexFields> |
419 |
</ToIndex> |
</ToIndex> |
420 |
</Relationship> |
</Relationship> |
421 |
|
<Relationship name="HasFeature" from="Genome" to="Feature" arity="1M"> |
422 |
|
<Notes>This relationship connects a genome to all of its features. This |
423 |
|
relationship is redundant in a sense, because the genome ID is part |
424 |
|
of the feature ID; however, it makes the creation of certain queries more |
425 |
|
convenient because you can drag in filtering information for a feature's |
426 |
|
genome.</Notes> |
427 |
|
<Fields> |
428 |
|
<Field name="type" type="key-string"> |
429 |
|
<Notes>Feature type (eg. peg, rna)</Notes> |
430 |
|
</Field> |
431 |
|
</Fields> |
432 |
|
<ToIndex> |
433 |
|
<Notes>This index enables the application to view the features of a |
434 |
|
Genome sorted by type.</Notes> |
435 |
|
<IndexFields> |
436 |
|
<IndexField name="type" order="ascending" /> |
437 |
|
</IndexFields> |
438 |
|
</ToIndex> |
439 |
|
</Relationship> |
440 |
<Relationship name="IsEvidencedBy" from="Coupling" to="PCH" arity="1M"> |
<Relationship name="IsEvidencedBy" from="Coupling" to="PCH" arity="1M"> |
441 |
<Notes>This relationship connects a functional coupling to the physically |
<Notes>This relationship connects a functional coupling to the physically |
442 |
close homologs (PCHs) which affirm that the coupling is meaningful.</Notes> |
close homologs (PCHs) which affirm that the coupling is meaningful.</Notes> |