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
{{ message }}
This repository has been archived by the owner on Sep 22, 2019. It is now read-only.
Clients who use the taxonomy may want to know the taxonomy version. Clients
who use a study or collection may want to know the study or collection
version. The latter is implemented in an idiosyncratic way in the
phylesystem-api. I'm not sure what the otindex support for versioning is.
It would be better if versioning wasn't added in a different way for each
data type. There ought to be some common architecture, so that there is
less to learn.
I gather that there will be a drawn-out discussion on the best way forward by people who understand the best practices. For me, how versions are assigned is something that needs thought, and I would argue for consistency (but that isn't always seen as necessary). But reporting existing version numbers in query responses seems very straightforward. This is extremely relevant information (as is the taxonomy version), and I cannot fathom why would ever not provide it. We could satisfy @arlin's request immediately by reversing these commits:
Please note: I only put this here for easy reference for the issue at hand. I know I didn't understand the issues last time around, and am not looking to be told how wrong I am. Whatever solution is best is best.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Clients or users who employ subtree and induced_subtree may wish to have the synth tree version. This would be useful for the phylotastic project.
Add synth_id to response from subtree, induced_subtree, and any other services that return results dependent on the synth tree.
The text was updated successfully, but these errors were encountered: