-
Notifications
You must be signed in to change notification settings - Fork 0
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
Autogenerated web documentation should include a minimal table of all terms on it's own page #4
Comments
This would be highly appreciated and it does not have to be overly complex or extensive. Most people use for example only the generic package but they might have additional metadata that has been used in other well defined packages. To have such a general overview in which they can apply basic |
@jjkoehorst can you elaborate on the "generic package"? That isn't anything that is defined in this schema. |
I agree that this will be useful and can easily be implemented, but only as a new, extremely large section on the schema's landing page The challenge will be building it on another page and providing a link on either the right (section-oriented) menu or the left (open-ended) menu |
I am mostly familiar with the ENA submission procedures https://www.ebi.ac.uk/ena/browser/view/ERC000011 for which only date and location is obligatory and used in a lot of cases |
Move types section to separate page also rename some of the sections |
sort elements in tables alphabetically packages -> externsions |
emphasize usability to a wide audience over comprehensiveness |
Where/how will all of the documentation from this repo be integrated with the GSC website? |
The terms page should be separate from the page that lists all the classes, since it is such a long list. It should include at least the term label, ID, and definition (linkml description). |
The terms are listed on the gensc.org website at present: |
No description provided.
The text was updated successfully, but these errors were encountered: