IQSS / dataverse-installations

In April 2023, Juan left a comment on the Google Sheet with a link to the repository's CoreTrustSeal certification. I just noticed this comment today. The link no longer works, but the list of certifications at https://amt.coretrustseal.org/certificates includes a link to the repository's certification:

The rather long link is https://ctscertificationbucket.s3.amazonaws.com/2023/4/2023-04-18-Consorcio-Madroño-e-cienciaDatos_final.pdf?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIA4ZTNLHN3BLBCAFWX%2F20230901%2Feu-central-1%2Fs3%2Faws4_request&X-Amz-Date=20230901T182100Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=host&X-Amz-Signature=cc78ea88ddd6ee9ff32f800d57b15e1434eb695f4bb89dc981ab2ca99c9cde22

I'll be updating the Dataverse worldmap now with the link to the repository's CoreTrustSeal certification. (On the online map, the URL isn't shown, just a clickable CTS logo, which takes users to the certification.)

I'm getting a certification error when I try to run update-data.py:

urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1129)>

The metrics_url in the code points to a page that Chrome also shows a NET::ERR_CERT_DATE_INVALID warning about.

dataverse-installations/update-data.py

Lines 13 to 14 in b04dc04

    
           metrics_url = 'https://metrics.dataverse.org/dataverse-metrics/config.json' 
        
           response = urlrequest.urlopen(metrics_url)

@donsizemore or @pdurbin, do you know what's going on? Could update-data.py be updated to ignore the certs error from the metrics_url?

Juan also let us know that the urls to the CoreTrustSeal certificates aren't stable and can and have changed.

Also I noticed that CoreTrustSeal certificates of other repositories on the worldmap have been updated.

@jggautier ah, thanks for the heads up. We recently got a new wildcard cert.

@donsizemore would you be able to put it on https://metrics.dataverse.org please?

@jggautier as for removing the SSL check, yes, it should be possible: https://stackoverflow.com/questions/36600583/python-3-urllib-ignore-ssl-certificate-verification

@pdurbin whoops! This was a config problem, and is fixed. Sorry about that.

@donsizemore no worries! One more thing to look at...

HMDC-beamish:dataverse-installations pdurbin$ curl https://metrics.dataverse.org/dataverse-metrics/config.json -k
<html>
<head><title>404 Not Found</title></head>
<body>
<center><h1>404 Not Found</h1></center>
<hr><center>nginx/1.20.1</center>
</body>
</html>
HMDC-beamish:dataverse-installations pdurbin$ curl -s https://metrics.dataverse.org/global/config.json | head
{
  "installations": [
    "http://dataverse.icrisat.org",
    "https://abacus.library.ubc.ca",
    "https://archaeology.datastations.nl",
    "https://archive.data.jhu.edu",
    "https://bonndata.uni-bonn.de",
    "https://borealisdata.ca",
    "https://dadosabertos.rnp.br",
    "https://dadosdepesquisa.fiocruz.br",

That is, in the code we have https://metrics.dataverse.org/dataverse-metrics/config.json hard coded. Now it's a 404.

Because https://metrics.dataverse.org/dataverse-metrics/config.json isn't working, I haven't been able to add or change anything on the Dataverse map, like the changes described in #205, #213, and #214.

@pdurbin and @donsizemore, should I open a new GitHub issue about this?

I just created one:

IQSS/dataverse-metrics#102

@jggautier for now do you want to use https://metrics.dataverse.org/global/config.json ?

Ah okay. So I'll replace the URL in my copy of update-data.py with https://metrics.dataverse.org/global/config.json and run the script again

	metrics_url = 'https://metrics.dataverse.org/dataverse-metrics/config.json'
	response = urlrequest.urlopen(metrics_url)

Add link to Dataverse e-cienciaDatos's CoreTrustSeal certification