-
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
Create a table of all included phyloreferences #34
Comments
This should also include a list of all OWL/RDF properties associated with phyloreferences in OWL, which would help identify data that is being incorrectly lost in the JSON-to-OWL transformation. |
A good first step here would just be counts of the number of phyloreferences tested, which we should be able to obtain from the TAP status line at the end of each |
gaurav
added a commit
that referenced
this issue
Jul 17, 2018
Since the name and role of this repository has changed (#19), we no longer refer to these as testcases but as PHYX files. I've updated the README file to reflect this (closes #30) and renamed some of the directories in this repository to make their purpose clearer, as well as cleaning out some out-of-date information that no longer needs to be stored outside the PHYX file itself. Individual lists of phyloreferences have been removed, and will eventually be replaced by an automatically generated table that provides information on the types of included phyloreferences (#34).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This table should provide a list of all the PHYX files currently included as well as lists of all defined phyloreferences, broken down by the types of phyloreferences, the state of each phyloreference (draft, submitted, etc.), and the taxa included in specifiers. This would allow us to get a high-level picture of what phyloreferences we have already curated and what gaps we might have in our curation effort.
This could be a Markdown file that is generated automatically during testing and stored in the repository.
The text was updated successfully, but these errors were encountered: