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

DC1 - T2.2 - CKAN Data Collection #24

Closed
ghilbrae opened this issue Jan 22, 2020 · 11 comments
Closed

DC1 - T2.2 - CKAN Data Collection #24

ghilbrae opened this issue Jan 22, 2020 · 11 comments
Assignees
Labels
data help wanted Extra attention is needed validation validation realted issues

Comments

@ghilbrae
Copy link

We've tested the information provided by you in CKAN with special interest on the URLs provided for the Resources in the Datasets. The results can be seen in the attached file with the following structure:

DATASET: {dataset_name}

RESOURCE: {resource_name} (if there's a name)

URL {ERROR | EXISTS} -> {url} (if there's one)

dc1.txt

@ghilbrae ghilbrae added help wanted Extra attention is needed data labels Jan 22, 2020
@ghilbrae
Copy link
Author

ghilbrae commented Feb 20, 2020

In the attached sheet I've made an analysis of the data available in CKAN and added some comments on its status. None of the datasets in CKAN are good, they either lead to dead or nonexistent data, or they are wrong, please update them to the correct ones.
Also, take a look at it and address the comments.
You'll also need to delete any dataset that might not be in use anymore and add any new ones.

If you have changed anything in the last couple of days, those changes may not be reflected there yet, I've been working on verifying the data for a few days now. Please, let me know and update the comments anyway.

Status of DS+Resources available in CKAN_DC1.xlsx

@p-a-s-c-a-l p-a-s-c-a-l added the validation validation realted issues label Mar 30, 2020
@p-a-s-c-a-l
Copy link
Member

p-a-s-c-a-l commented Apr 1, 2020

The following datasets have been declared open data but are not (yet) available on Zenodo:

Moreover, the datasets are missing a description and no resources (data) are available for those datasets.

@stefanon Please provide a description as well as the data so that we can make the datasets available on Zenodo or declare the datasets as non-open data.

@p-a-s-c-a-l
Copy link
Member

Status of DS+Resources available in CKAN_DC1.xlsx

FYI: From data management perspective it is o.k. if both used and produced non-open data is stored on internal CLARITY sFTP.

@p-a-s-c-a-l
Copy link
Member

The dataset Historical heat waves temperature in Naples (moderate hazard) is declared as private. See also #27 (comment)

@p-a-s-c-a-l
Copy link
Member

Please have a look at the Data Management Validation Report and correct all errors.

@stefanon
Copy link

stefanon commented Apr 6, 2020

Dear Pascal, I've involved Martina and Simone that already contacted you for being enabled to editing on Ckan.

@p-a-s-c-a-l
Copy link
Member

Updated validation report: dc1.docx.

Some download URLs are missing for several private (non-open) resources. Shouldn't they point to the CLARITY sFTP? However, there are still are open questions regarding post-project data preservation of non-public data.

@p-a-s-c-a-l
Copy link
Member

There are 41 non-open datasets produced within the context of DC1. Most if not all of the related resources, e.g. Outdoor Heat wave local effect (j) map are lacking a download link. Which makes sense, as the data is not open :-)

However, there is this question about long-term preservation of non-public data produced by the project. So we have to find a pragmatic solution to keep this data accessible after the end of the project.

@p-a-s-c-a-l
Copy link
Member

The open-data datasets of DC1 lack a description and a download link. They have to be uploaded to Zenodo.

See also Denis' Mail:

We have to assure that all the (relevant) data produced in this project is preserved after the project end. For the public data, we simply need to put it on Zenodo. For the private data, we need the following:

  • To assure that a contact is defined for the relevant data sets.
  • A confirmation by the organisation that the data will be kept available for some time after the project ends.

@p-a-s-c-a-l
Copy link
Member

p-a-s-c-a-l commented May 5, 2020

There are only 5 datasets in the group open-data produced by DC1:

  • Redevelopment project of East Napoli areas (baseline)
  • Redevelopment project of West Napoli areas (baseline)
  • Redevelopment project of West Napoli areas (j)
  • Redevelopment project of East Napoli areas (j)
  • Historical heat wave temperature (local effects)

Questions to be answered for the upcoming DMP:

  • Are those really results produced within CLARITY? This looks more like input data for local models (MUKLIMO_3). Some of the datasets lack the tags input-data or output-data, so it's not clear whether it's input or output data.
  • are there really only 5 (potential, previous question) datasets produced by DC1 that can be released under an open license as opposed to 41 non-open output datasets?
  • The most interesting open dataset Historical heat wave temperature (local effects) lacks a proper description, its not clear how it has been produced (MUKLIMO?) based in which input data.

@mattia-leone
Copy link

Hi Pascal, sorry I was late to the telco today.
Please remove all those datasets. We don't need them at all, they are outdated.
Also the historical temperature can be removed, since now we get this directly from the EU datapackage

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data help wanted Extra attention is needed validation validation realted issues
Projects
None yet
Development

No branches or pull requests

5 participants