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
EXAMPLE: 2016 LMISD DC Data Set & 2016 Overall LMISD DC could possibly be merged as one data-set or provide clarification as to why the overall results must be separate from the main 2016 LMISD Data-set.
The text was updated successfully, but these errors were encountered:
Devoncharles22
changed the title
remove any duplicate Datasets & merge similar datasets with only slightly differing content
remove duplicate data-sets & merge similar data-sets with slightly differing content
Sep 12, 2017
Thanks @Devoncharles22!
Important conversation here.
I put each one up individually for a few reasons, but most specifically to give each its own URL.
I think putting them all into one data-set makes things less opaque for users/can be overwhelming, as well as doing that then requires more upkeep because now all the data is tied to one another.
More clarification is always welcome, but I copy/pasted from the canonical source, so there's not much context that I can add to that.
I'm not saying that all of this is correct; I think it is, but opinion ! = fact.
Also, the broader conversation here is incredibly important, so thanks! We need to discuss/think our metadata approaches through. Essentially I've just been going off a workflow I developed over years uploading tons of data to CKAN instances.
EXAMPLE: 2016 LMISD DC Data Set & 2016 Overall LMISD DC could possibly be merged as one data-set or provide clarification as to why the overall results must be separate from the main 2016 LMISD Data-set.
The text was updated successfully, but these errors were encountered: