-
Notifications
You must be signed in to change notification settings - Fork 13
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
feat(openchallenges): model input data types of challenges with EDAM #2557
feat(openchallenges): model input data types of challenges with EDAM #2557
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works on my end - thanks!
|
|
|
|
Closes #2551
Changelog
Challenge.inputDataTypes
as an array ofEdamData
objectssrc/main/resources/db
to share notes about how data are imported from CSV filesFuture Work
Preview
Search using the full-text search field
One challenge annotated with "Resource type" (
http://edamontology.org/data_0005
)Searching with EDAM preferred name:
Searching with short EDAM class ID:
Searching with full EDAM class ID:
Challenge.inputDataTypes
is now an array of EDAM Data objectsExample of challenge with input data type indexed in Elasticsearch
Notes
ES indexed values may be a single objects or an array
Note
What is describe below is not an issue. It is simply how ES index data. The property returned by the OC Challenge Service will still always be an array.
The property
Challenge.inputDataTypes
takes an array as value when the challenge has multiple types. However, this property takes the value of a single object when its has a single type. This property must always be an array.vs
cc: @vpchung @mdsage1 @gaiaandreoletti