Startseite Erkunden Hilfe
Anmelden
zhxd2
/
tripal
1
0
Fork 0
Dateien Issues 0 Pull-Requests 0 Wiki
Struktur: b5f3999095
Branches Tags
tripal
/
docs
/
extensions
/
in_development.rst

in_development.rst 2.6 KB
Verlauf Originalformat

123456789101112131415161718192021222324252627282930 
  1. 

  2. In Development
    3. 

  3. ==============
    4. 

  4. 

  5. The following modules are not yet ready for production or not fully Tripal 3 compatible.
    6. 

  6. 

  7. 

  8. TripalMap
    9. 

  9. -----------
    10. 

  10. 

  11. TripalMap MapViewer module displays map data stored in Chado. MapViewer provides interfaces to view all linkage groups of a map, choose a linkage group and zoom in to a specific region of a linkage group, compare maps that share the same markers and change colors of markers/QTL. The interface can be integrated into Tripal map page and hyperlinked to/from any Tripal page that are displayed in maps (marker, QTL, heritable morphological marker and/or gene). The admin page allows site developers some flexibility in the display pattern.
    12. 

  12. 

  13. `Documentation <https://gitlab.com/mainlabwsu/tripal_map/blob/master/README.md>`__
    14. 

  14. `Repository <https://gitlab.com/mainlabwsu/tripal_map>`__
    15. 

  15. 

  16. Tripal Apollo
    17. 

  17. --------------
    18. 

  18. 

  19. Tripal Apollo lets you manage user accounts for your JBrowse Apollo instances on your Tripal site.  Provides a form to request apollo access, an Apollo instance content type that connects to Chado Organisms, and an administrative interface for managing requests.
    20. 

  20. 

  21. `Documentation <https://tripal-apollo.readthedocs.io/en/latest/>`__
    22. 

  22. `Repository <https://github.com/NAL-i5K/tripal_apollo>`__
    23. 

  23. 

  24. Tripal Multi-Chado
    25. 

  25. ------------------
    26. 

  26. 

  27. The Multi-Chado module is an extension for Tripal 2.x and 3.x (dev branch under testing) that can be used to install more than one Chado instance across different schemata of your choice and it also enables the use of different PostgreSQL database credentials allowing the administrator to do fine tuning of database accesses. For instance, with this module, you can host on a *same Drupal instance* (config, tools and users) both a *public* and one or more *private* Chado instances. You could also have different public instances for *different releases* of a same genome sequencing or event *different species*. It can also alow you do provide a Chado *sandbox* to allow users to safely modify Chado data and see the changes on the site. It can be used to run *tests* against a blank Chado instance (see https://github.com/tripal/tripal_simpletest/). And you may even think of other kind of uses (dev-staging-prod, etc.)... The dev branch is supposed to work well with Tripal 3 but has not been extensively tested yet. A companion module (tripal_mc_selector) is provided to allow easy Chado instance switching. Several hooks are available for module developers in order to automatically switch Chado instance according to a given context.
    28. 

  28. 

  29. `Documentation <http://cgit.drupalcode.org/tripal_mc/plain/README.md?h=7.x-1.x>`__
    30. 

  30. `Repository <https://www.drupal.org/project/tripal_mc>`__
    31.