You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to have an embedded version of a JBrowse on a feature-based page. This should be able to be specific to the organism at the least (e.g. Show the Lentil JBrowse if on a Lentil Marker page and show a Chickpea JBrowse if on a Chickpea page).
The text was updated successfully, but these errors were encountered:
To provide good integration with this module, you would likely want to add this field in the tripal_jbrowse_page sub-module. This allows you to use a similar approach to that used in the current page integration.
Specifically, here is the code that builds the URL for embedding a specific JBrowse instance created through the management module. This would go in the Tripal field class.
Then this page template renders the JBrowse metadata and iFrame. This would go in the Tripal field formatter class.
There is also some CSS here which controls the iFrame size.
You'll likely want some extra methods in the field class to determine the organism_id or analysis_id based on the given page. Personally, I would do this by looking at the base chado table associated with the Tripal content type the field is attached to. Then you can set up rules based on that table and use the Chado Schema Documentation to determine what information is available to you.
It would be nice to have an embedded version of a JBrowse on a feature-based page. This should be able to be specific to the organism at the least (e.g. Show the Lentil JBrowse if on a Lentil Marker page and show a Chickpea JBrowse if on a Chickpea page).
The text was updated successfully, but these errors were encountered: