Curations using INDRA DB REST API #200
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dianakolusheva
force-pushed
the
curations
branch
from
abe6e28
to
8525de1
Compare
dianakolusheva
force-pushed
the
curations
branch
2 times, most recently
from
10c8e3c
to
b41c7ff
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the usage of methods to get and submit curations. New approach is to use functions in
indra.sources.indra_db_restinstead of querying the database directly. On EMMAA service side, this PR also puts listing the individual curations (curator email, tag and date) behind the login (badges with curation colors/counts are still available without login). This PR goes together with sorgerlab/indra#1228