-
Notifications
You must be signed in to change notification settings - Fork 5
[215] health scanner unify ES #216
base: dev
Are you sure you want to change the base?
Conversation
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.
first pass
"nih": "placeName_country_organisation" | ||
}, | ||
"country_id": { | ||
TODO: iso2, iso3 or isoNumeric. Pick one? |
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.
Yes. iso2
as it's the shortest?
"meetup": "terms_mesh_group", | ||
"nih": "terms_mesh_abstract" | ||
}, | ||
"sdg_labels": { |
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.
I think this should be terms_sdg
to signify this is an array of strings, or we can change the convention and use array_*
if terms is too specific for some keys?
}, | ||
"funding_entity": { | ||
"nih": "title_of_funder" | ||
}, |
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.
I think this comma will give an error
"title": { | ||
"nih": "title_of_project" | ||
}, | ||
"start_date": { |
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.
I changed my mind, I think we should use date_*
for time related keys:
date_start
date_end
date_update
"update_date": { | ||
"crunchbase": "datetime_updated_organisation" | ||
}, | ||
"continent": { |
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.
also I wanted to propose a geo_*
namespace as we'd also have funding_*
, terms|array_*
, url_*
#215