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
HAPI needs the ability to report where the data came from. Ideally this would be a DOI, and those are universal enough that we could add a field for that in the info response.
This means we should maybe revisit the ability for the server to return just the data with no header. Because it’s the header for a specific data request that should contain the DOI, or maybe a list of DOIs. Currently, most people don't really request the info for a specific time range - they just get it once to se what the parameters are. And some datasets use one DOI per file, or group of files. This one-DOI-per-file is not what is currently recommended by IHDEA, but actually there is not a solid agreement on that yet.
Maybe having a provenance block, and offer a list of suggested keywords:
DOI (can be list)
version (also a list?)
modification date
dependencies (can of worms)
The text was updated successfully, but these errors were encountered:
HAPI needs the ability to report where the data came from. Ideally this would be a DOI, and those are universal enough that we could add a field for that in the info response.
This means we should maybe revisit the ability for the server to return just the data with no header. Because it’s the header for a specific data request that should contain the DOI, or maybe a list of DOIs. Currently, most people don't really request the info for a specific time range - they just get it once to se what the parameters are. And some datasets use one DOI per file, or group of files. This one-DOI-per-file is not what is currently recommended by IHDEA, but actually there is not a solid agreement on that yet.
Maybe having a provenance block, and offer a list of suggested keywords:
The text was updated successfully, but these errors were encountered: