-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Derive subsets page automatically from metadata #102
Comments
It's totally possible but we selected GitHub pages to avoid dynamic content, this tech is not really design for that.. We discussed this problem at Stanley Hall with Chris & Seth, and I still think this sort of "dynamic" page (changing with every release) should be produced by the pipeline which would update automatically a specific markdown file of the site. @kltm tagging Seth on that. The other solution would be to create a HTML page within the new site, fetching data through http requests and using possibly jquery to create the dynamic content. |
Either in the pipeline (and the site grabs the pages) or Jenkins can trigger and update the repo automatically on metadata updates, both viable in my opinion. |
I still favor the later (jenkins triggers update to this repo to update a specific file anytime there is a new release). We could use the same strategy for filling the stats number on the upper right corner of the site:
|
For clarification, this fix will affect both the Subset and the Downloads pages (http://current.geneontology.org/products/pages/downloads.html) |
Likely solution: site will fetch, perhaps from a file or perhaps from API- redo both dynamic pages |
Metadata:
https://github.com/geneontology/go-ontology/tree/master/src/ontology/subsets
Of course this is in a different repo. go.gh.io should have a Makefile that syncs upstream metadata into the _config.yml. See the obo site for examples
Would avoid issues like: geneontology/helpdesk#167
The text was updated successfully, but these errors were encountered: