Skip to content
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

Update study and tree properties that describe tree status vs. synthesis #12

Open
jimallman opened this issue Sep 29, 2016 · 1 comment

Comments

@jimallman
Copy link
Member

jimallman commented Sep 29, 2016

These changes are described in OpenTreeOfLife/phylesystem-api#191. For useful behavior for interpreting the old properties, see this code in the curation app that tries to modify incoming Nexson using information known to the client. (N.B. this code uses the wrong property name and values, should be tree['^ot:candidateForSynthesis'] instead of tree['^ot:readyForSynthesis'])

A server-side process can probably do a better job by detecting which trees are already in collections that contribute to synthesis, and therefore should have their ot:candidateForSynthesis property set to ot:include.

@jimallman
Copy link
Member Author

This is implemented in OpenTreeOfLife/opentree#1068 and working now on devtree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant