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

A method is needed for handling data which are "preliminary" #9

Open
DocOtak opened this issue Apr 29, 2015 · 0 comments
Open

A method is needed for handling data which are "preliminary" #9

DocOtak opened this issue Apr 29, 2015 · 0 comments

Comments

@DocOtak
Copy link
Member

DocOtak commented Apr 29, 2015

Currently there is no way on the site to indicate the "preliminaryness" of data. Some options with time to solution in parens:

  1. (fastest) Change the file metadata role to "preliminary", as is this would cause the file to not appear in the main data set, but rather with the "as received"/"merged" data. This would also cause the data to not be included in any bulk download options.
  2. (slower) Change the file metadata role to "preliminary" AND also modify the page to include the data in the main dataset, while somehow indicating the "preliminaryness" of the data (perhaps with a color code), optionally, also modify the bulk download to include preliminary data.
  3. (very slow) Include USHYDRO style parameter tracking with the file metadata to indicate not only that the data are preliminary, but which data are preliminary. The solution could have a lot of overhead in propagating the preliminary status across file metadata.

I prefer option 1 for "dataset" integrity reasons, that is, preliminary data would not be included with the main dataset which would allow us to be certain of the quality/finality of the data which is included in the main dataset. This is a bit of a departure from how we've operated in the past.

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