/usr/share/gmod/chado/chado-module-metadata.xml is in libchado-perl 1.23-2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 | <?xml version="1.0" encoding="ISO-8859-1"?>
<!-- $Id: chado-module-metadata.xml,v 1.25 2009-08-31 14:25:35 scottcain Exp $ -->
<schema_metadata id='chado'>
<title>Chado: A generic model organism database schema</title>
<description>
Chado is a modular schema for biological data
</description>
<about>
This is a metadata file describing chado and its components,
specified in XML. The path to each module SQL file is described,
as well as other files which that module may require or use
</about>
<!-- source types -->
<!-- dir: a directory relative to the chado root dir -->
<!-- sql: SQL DDL statements that are largely DBMS neutral-->
<!-- plpgsql: PostgreSQL functions and triggers -->
<!-- bridge-xml: Can be converted with chado/bin/create-bridge-sql.pl -->
<!-- sqlapi: Pseudo-SQL public function interface declarations -->
<!-- -->
<modules>
<source type='dir' path='modules'/>
<module id='general' required='true'>
<description>
General purpose tables, including dbxrefs
</description>
<source type='sql' path='general/general.sql'/>
<component id='general-report' type='views' required='true'>
<description>
Standard Chado SQL Reports for the general module
</description>
<source type='sql' path='general/views/general-report.sql'/>
</component>
<component id='general-loading-api' type='dbapi'>
<description>
A DBMS API for the general module's loading functions
</description>
<source type='sqli' path='general/functions/general-loading.sqlapi'/>
</component>
<component id='general-loading' type='code'>
<description>
Postgres code for helping with loading the general module
</description>
<implements to='general-loading-api'/>
<source type='plpgsql' path='general/functions/general-loading.plpgsql'/>
</component>
</module>
<module id='cv' required='true'>
<dependency to='general'/>
<description>
Controlled vocabularies and ontologies
</description>
<source type='sql' path='cv/cv.sql'/>
<component id='cv-views' type='views' required='true'>
<description>
Standard Chado SQL Views for the cv module
</description>
<source type='sql' path='cv/views/cv-views.sql'/>
</component>
<component id='cv-report' type='views' required='true'>
<description>
Standard Chado SQL Reports for the cv module
</description>
<source type='sql' path='cv/views/cv-report.sql'/>
</component>
<component id='cv-dbapi' type='dbapi'>
<description>
A DBMS API for the cv module
</description>
<source type='sqli' path='cv/cv-dbapi.sqli'/>
</component>
<component id='cv-subj-obj' type='code'>
<description>
Postgres code for finding parent and child cvterms
</description>
<source type='plpgsql' path='cv/functions/get_subj_obj_ids.plpgsql'/>
</component>
<component id='cv-funcs' type='code'>
<description>
Postgres code for populating the cvtermpath table
</description>
<implements to='cv-dbapi'/>
<source type='plpgsql' path='cv/functions/fill_cvtermpath.plpgsql'/>
</component>
<component id='cv-cycle' type='code'>
<description>
Postgres code for working with cvterm cycles
</description>
<source type='plpgsql' path='cv/functions/detect_cycle.plpgsql'/>
</component>
</module>
<module id='pub' required='true'>
<dependency to='general'/>
<dependency to='cv'/>
<description>
Bibliographic data on publications
</description>
<source type='sql' path='pub/pub.sql'/>
</module>
<module id='organism' required='true'>
<dependency to='general'/>
<dependency to='cv'/>
<description>
Species data - does not include phylogeny
</description>
<source type='sql' path='organism/organism.sql'/>
<component id='organism-dbapi' type='dbapi'>
<description>
A DBMS API for the organism module
</description>
<source type='sqli' path='organism/functions/organism.sqlapi'/>
</component>
<component id='organism-funcs' type='code'>
<description>
Postgres code retrieving organism data
</description>
<implements to='organism-dbapi'/>
<source type='plpgsql' path='organism/functions/organism.plpgsql'/>
</component>
<component id='organism-loading' type='code'>
<description>
Postgres code for helping with loading organism data
</description>
<source type='plpgsql' path='organism/functions/organism-loading.plpgsql'/>
</component>
</module>
<module id='sequence' required='true'>
<dependency to='general'/>
<dependency to='organism'/>
<dependency to='cv'/>
<dependency to='pub'/>
<description>
Sequence and sequence features, their localization and properties
</description>
<source type='sql' path='sequence/sequence.sql'/>
<component id='sequence-report' type='views' required='true'>
<description>
Standard Chado SQL Reports for the sequence module
</description>
<source type='sql' path='sequence/views/sequence-report.sql'/>
</component>
<component id='gencode' type='sql' required='true'>
<description>
Genetic code - maps codons to amino acids according to
species specific translation table
</description>
<source type='sql' path='sequence/gencode/gencode.sql'/>
<source type='sqldump' path='sequence/gencode/gencode_data.sql'/>
</component>
<component id='sequence-dbapi' type='dbapi'>
<dependency to='gencode'/>
<description>
A SQL/DBMS API for the sequence module. Currently only plpgsql
implementations exist
</description>
<!-- subcomponents -->
<component id='sequence-dbapi-range' type='dbapi'>
<description>
Functions for operating on interval ranges
</description>
<source type='sqlapi' path='sequence/functions/range.sqlapi'/>
<source type='plpgsql' path='sequence/functions/range.plpgsql'/>
</component>
<component id='sequence-dbapi-sequtil' type='dbapi'>
<dependency to='gencode'/>
<description>
Utility functions for biological sequences
</description>
<source type='sqlapi' path='sequence/functions/sequtil.sqlapi'/>
<source type='plpgsql' path='sequence/functions/sequtil.plpgsql'/>
</component>
<component id='sequence-dbapi-locgraph' type='dbapi'>
<description>
Projections on graph defined by featureloc
</description>
<source type='sqlapi' path='sequence/functions/locgraph.sqlapi'/>
<source type='plpgsql' path='sequence/functions/locgraph.plpgsql'/>
</component>
<component id='sequence-dbapi-cv-helper' type='dbapi'>
<description>
feature types
</description>
<source type='sqlapi' path='sequence/functions/sequence-cv-helper.sqlapi'/>
<source type='plpgsql' path='sequence/functions/sequence-cv-helper.plpgsql'/>
</component>
</component>
<component id='feature-util-api' type='dbapi'>
<description>
A DBMS API for general feature queries
</description>
<source type='sqli' path='sequence/functions/feature.sqlapi'/>
</component>
<component id='feature-util' type='code'>
<dependency to='sequence-dbapi'/>
<description>
Postgres code for general feature queries
</description>
<implements to='feature-util-api' />
<source type='plpgsql' path='sequence/functions/feature.plpgsql'/>
</component>
<component id='sequence_opt' type='optimizations'>
<description>
Optional optimizations to be applied to the sequence module
</description>
<source type='sql-in-xml' path='sequence/sequence_opt.xml'/>
</component>
<component id='godb-bridge' type='bridge'>
<description>
Views that let Chado masquerade as a GO Database.
Note that this is a component of the sequence module, as the
views are over both cv and sequence modules
</description>
<status code='alpha'>
Requires testing with AmiGO
</status>
<source type='bridge-xml' path='cv/bridges/godb-bridge.sql.xml'/>
</component>
<component id='chaos-bridge' type='bridge'>
<description>
Chaos is a simplified layer over chado
</description>
<status code='alpha'/>
<source type='bridge-xml' path='sequence/bridges/chaos-bridge.sql'/>
</component>
<component id='so-bridge' type='view' required='true'>
<description>
Provides a view for every type in the SO ontology. This
means you can do queries such as "SELECT * FROM gene" etc
</description>
<source type='sql' path='sequence/bridges/so-bridge.sql'/>
</component>
<component id='implicit-feature-views' type='views' required='true'>
<dependency to='sofa-bridge' />
<description>
This enhances the SOFA layer with additional queries for
complex feature types, such as those can be inferred from
other features.
</description>
<source type='sql' path='sequence/views/implicit-feature-views.sql'/>
</component>
<component id='sequence-loading-api' type='dbapi'>
<description>
A DBMS API for loading feature tables
</description>
<source type='sqli' path='sequence/functions/sequence-loading.plpgsql'/>
</component>
<component id='sequence-loading' type='code'>
<description>
Postgres code for loading feature tables
</description>
<implements to='sequence-loading-api' />
<source type='plpgsql' path='sequence/functions/sequence-loading.plpgsql'/>
</component>
<component id='subsequence-api' type='dbapi'>
<description>
A DBMS API for doing subsequence queries
</description>
<source type='sqli' path='sequence/functions/subsequence.sqlapi'/>
</component>
<component id='subsequence' type='code'>
<description>
Postgres code for doing subsequence queries
</description>
<implements to='subsequence-api' />
<source type='plpgsql' path='sequence/functions/subsequence.plpgsql'/>
</component>
<component id='feature_subalignments' type='code'>
<description>
Postgres code for doing something with feature subalignments,
but I don't remember what. Allen?
</description>
<source type='plpgsql' path='sequence/functions/feature_subalignments.plpgsql'/>
</component>
<component id='frange' type='code'>
<description>
Postgres code for fast feature 'contains' query, requried
for the DAS2 server (right?)
</description>
<source type='plpgsql' path='sequence/functions/frange.plpgsql'/>
</component>
<component id='create_soi' type='code'>
<description>
Postgres code to flatten feature relationships; it is in some
ways similar to frange.
</description>
<source type='plpgsql' path='sequence/functions/create_soi.plpgsql'/>
</component>
<component id='feature_ids_fx' type='code'>
<description>
Postgres code to simplify feature relationship queries
</description>
<source type='plpgsql' path='sequence/functions/feature_ids_fx.plpgsql'/>
</component>
</module>
<module id='companalysis' required='true'>
<!--added required, since sequence_views is requred and it depends on companalysis-->
<dependency to='general'/>
<dependency to='sequence'/>
<dependency to='cv'/>
<description>
Augments sequence module with descriptions of computational
analyses and features resulting from those analyses
</description>
<source type='sql' path='companalysis/companalysis.sql'/>
<component id='companalysis-loading-api' type='dbapi'>
<description>
A DBMS API for the companalysis module's loading functions
</description>
<source type='sqli' path='companalysis/functions/companalysis-loading.sqlapi'/>
</component>
<component id='companalysis-loading' type='code'>
<description>
Postgres code for helping with loading the companalysis module
</description>
<implements to='companalysis-loading-api'/>
<source type='plpgsql' path='companalysis/functions/companalysis-loading.plpgsql'/>
</component>
</module>
<module id='phenotype'>
<dependency to='general'/>
<dependency to='sequence'/>
<dependency to='cv'/>
<dependency to='pub'/>
<status code='beta'>
In use right now in FlyBase
</status>
<description>
Entity-attribute-value phenotypic character descriptions
</description>
<source type='sql' path='phenotype/phenotype.sql'/>
</module>
<module id='genetic'>
<dependency to='general'/>
<dependency to='sequence'/>
<dependency to='cv'/>
<dependency to='pub'/>
<dependency to='phenotype'/>
<status code='beta'>
In use right now in FlyBase
</status>
<description>
Genotypes and mutant alleles
</description>
<source type='sql' path='genetic/genetic.sql'/>
</module>
<module id='map'>
<dependency to='sequence'/>
<dependency to='cv'/>
<dependency to='pub'/>
<status code='alpha'>
Not yet in production use anywhere?
</status>
<description>
Non-sequence maps: genetic, radiation hybrid, cytogenetic, etc
</description>
<source type='sql' path='map/map.sql'/>
</module>
<!--
This module isn't in cvs
<module id='event'>
<dependency to='sequence'/>
<dependency to='cv'/>
<dependency to='pub'/>
<status code='pre-alpha'>
discussion stage
</status>
<description>
Pathways and quantitative models
</description>
<source type='sql' path='event/event.sql'/>
</module>
-->
<module id='phylogeny'>
<dependency to='sequence'/>
<dependency to='cv'/>
<dependency to='pub'/>
<dependency to='general'/>
<dependency to='organism'/>
<dependency to='companalysis'/>
<status code='beta'>
In use at IRRI
</status>
<description>
For representing phylogenetic trees; the trees represent the
phylogeny of some some kind of sequence feature (mainly
proteins) or actual organism taxonomy trees
</description>
<source type='sql' path='phylogeny/phylogeny.sql'/>
<component id='phylogeny-dbapi' type='dbapi'>
<description>
A DBMS API for the phylogeny module
</description>
<source type='sqli' path='phylogeny/functions/phylo.sqlapi'/>
</component>
<component id='phylogeny-funcs' type='code'>
<description>
Postgres code retrieving phylogeny data
</description>
<implements to='phylogeny-dbapi'/>
<source type='plpgsql' path='phylogeny/functions/phylo.plpgsql'/>
</component>
</module>
<module id='contact'>
<dependency to='cv'/>
<dependency to='general'/>
<status code='alpha'>
In use at UCLA/Allen Day
</status>
<description>
model persons, institutes, groups, organizations, etc
</description>
<source type='sql' path='contact/contact.sql'/>
</module>
<module id='expression'>
<dependency to='sequence'/>
<dependency to='cv'/>
<dependency to='pub'/>
<dependency to='general'/>
<status code='alpha'>
In use at FlyBase
</status>
<description>
transcript or protein expression data
</description>
<source type='sql' path='expression/expression.sql'/>
</module>
<module id='project'>
<dependency to="cv"/>
<dependency to="contact"/>
<dependency to="pub"/>
<status code='beta'>
</status>
<description>
The project table has been moved from general to its own module and has been
expanded to provide properties, publications and contacts.
</description>
<source type='sql' path='project/project.sql'/>
</module>
<module id='mage'>
<dependency to='sequence'/>
<dependency to='cv'/>
<dependency to='pub'/>
<dependency to='general'/>
<dependency to='organism'/>
<dependency to='contact'/>
<dependency to='companalysis'/>
<dependency to='project'/>
<status code='beta'>
In use at UCLA/Allen Day
</status>
<description>
Alternative expression module, based on MAGE model
</description>
<source type='sql' path='mage/mage.sql'/>
</module>
<module id='stock'>
<dependency to='genetic'/>
<dependency to='cv'/>
<dependency to='pub'/>
<dependency to='general'/>
<dependency to='contact'/>
<status code='beta'>
In use at ParameciumDB
</status>
<description>
For tracking stock collections
</description>
<source type='sql' path='stock/stock.sql'/>
</module>
<module id='library'>
<dependency to='sequence'/>
<dependency to='cv'/>
<dependency to='pub'/>
<dependency to='organism'/>
<status code='beta'>
</status>
<description>
For describing molecular libraries
</description>
<source type='sql' path='library/library.sql'/>
</module>
<module id='cell_line'>
<dependency to='sequence'/>
<dependency to='cv'/>
<dependency to='pub'/>
<dependency to='organism'/>
<dependency to='library'/>
<status code='beta'>
</status>
<description>
For describing cell lines
</description>
<source type='sql' path='cell_line/cell_line.sql'/>
</module>
<module id='composite'>
<status code='beta'>
</status>
<description>
A collection of bridge codes that have multiple dependencies
so they don't happily go where is most obvious.
</description>
<component id='gff-bridge' type='bridge'>
<dependency to='pub'/>
<dependency to='sequence'/>
<dependency to='companalysis'/>
<dependency to='cv'/>
<dependency to='sequence-dbapi'/>
<description>
A GFF-view over chado. Required by Gbrowse
</description>
<source type='sql' path='sequence/gff-bridge/sequence-gff-views.sql'/>
<source type='plpgsql' path='sequence/gff-bridge/sequence-gff-funcs.plpgsql'/>
</component>
<component id='sequence-views' type='views' required='true'>
<dependency to='sequence'/>
<dependency to='companalysis'/>
<dependency to='cv'/>
<description>
Standard Chado SQL Views for the sequence module
</description>
<source type='sql' path='sequence/sequence_views.sql'/>
<component id='range-views' type='views' required='true'>
<description>
Views for operating on featureloc ranges. Overlap,
intersection, union, difference etc
</description>
<source type='sql' path='sequence/views/range-views.sql'/>
</component>
</component>
</module>
<module id='natural-diversity'>
<dependency to='sequence'/>
<dependency to='cv'/>
<dependency to='pub'/>
<dependency to='phenotype'/>
<dependency to='organism'/>
<dependency to='genetic'/>
<dependency to='contact'/>
<dependency to='general'/>
<dependency to='stock'/>
<dependency to='project'/>
<status code='beta'>
</status>
<description>
Natural diversity module for dealing with populations, samples, genotypes,
phenotypes and results of other assays.
</description>
<source type='sql' path='natural_diversity/natural_diversity.sql'/>
</module>
<!--
Since this is dynamically generated from a given schema, this should
either be done at a later step, or if requested, dynamically generated
at run time after the rest of the schema has been generated
<module id='audit'>
<dependency to='sequence'/>
<dependency to='cv'/>
<dependency to='pub'/>
<dependency to='general'/>
<dependency to='companalysis'/>
<dependency to='contact'/>
<dependency to='expression'/>
<dependency to='event'/>
<dependency to='genetic'/>
<dependency to='library'/>
<dependency to='map'/>
<dependency to='organism'/>
<dependency to='phylogeny'/>
<dependency to='rad'/>
<dependency to='project'/>
<dependency to='natural-diversity'/>
<status code='beta'>
In use at...?
</status>
<description>
Table auditing for whole database; autogenerated tables
</description>
<source type='sql' path='audit/audit_tables.sql'/>
</module>
-->
</modules>
</schema_metadata>
|