pdurbin
commented
5 years ago Here's the quick and dirty one liner I wrote a while ago for determining the version of Dataverse that is being run by installations on the map:
curl -s https://services.dataverse.harvard.edu/miniverse/map/installations-json | jq '.installations[].url' -r | while read i; do echo -n "$i "; curl -s $i/api/info/version | jq '.data.version' -r; done
The problem is that the output is a mess:
https://dvn.library.ubc.ca/dvn/ https://dataverse.ada.edu.au/ 4.6.1 https://data.aussda.at/ 4.6.2 https://dataverse.bhp.org.bw/ null https://catalogues.cdsp.sciences-po.fr/ 4.8.5 https://data.cifor.org 4.14 http://data.cimmyt.org/ parse error: Invalid numeric literal at line 1, column 10 https://dataverse.cirad.fr/ 4.8.4 https://dataverse.library.dal.ca parse error: Invalid numeric literal at line 1, column 10 https://data.inra.fr/ 4.9.2 https://dataspace.ust.hk/ parse error: Invalid numeric literal at line 1, column 6 (23) Failed writing body https://edatos.consorciomadrono.es/ 4.11 https://dataverse.nl/ 4.10.1 https://dataverse.no/ 4.11 https://researchdata.ntu.edu.sg 4.9.4 https://dvn.fudan.edu.cn/home/ https://data.gro.uni-goettingen.de/ 4.14 https://dataverse.harvard.edu 4.15 https://heidata.uni-heidelberg.de/ 4.14 https://repositoriopesquisas.ibict.br/ parse error: Invalid numeric literal at line 1, column 6 http://dataverse.icrisat.org/ 4.8.6 https://dataverse.mpi-sws.org/dataverse/icwsm parse error: Invalid numeric literal at line 1, column 6 https://research-data.ifsttar.fr/dataverse/data parse error: Invalid numeric literal at line 1, column 6 https://datasets.socialhistory.org/ parse error: Invalid numeric literal at line 1, column 6 https://data.cipotato.org/dataverse.xhtml parse error: Invalid numeric literal at line 1, column 6 https://archive.data.jhu.edu/ 4.13 https://dataverse.lib.virginia.edu/ 4.12 https://data.lipi.go.id 4.14 http://dataverse.acg.maine.edu/dvn/ parse error: Invalid numeric literal at line 1, column 6 http://data.mel.cgiar.org 4.8.5 https://researchdata.nie.edu.sg 4.10.1 http://opendata.pku.edu.cn/ 4.14 https://data.qdr.syr.edu 4.14-qdr2 http://dataverse.ufabc.edu.br 4.8.5 http://dataverse.ileel.ufu.br 4.11 http://research-data.urosario.edu.co/ 4.9.4 https://dataverse.scholarsportal.info/ v4.10.1.5-SP https://dataverse.tdl.org/ 4.9.4-tdl https://dataverse.library.ualberta.ca/dvn/ parse error: Invalid numeric literal at line 1, column 6 https://dataverse.ucla.edu/dataverse/dataverse parse error: Invalid numeric literal at line 1, column 6 https://dataverse.lib.unb.ca/ 4.14 https://dataverse.unc.edu/ 4.9.4 https://dataverse.unimi.it/ 4.14 https://dataverse.lib.umanitoba.ca/ null http://dataverse.sta.uwi.edu/ parse error: Invalid numeric literal at line 1, column 10 https://dataverse.vtti.vt.edu/ null
donsizemore
skasberger
As of this writing there are 46 installations of Dataverse on the map at https://dataverse.org
Currently there are 17 installations of Dataverse listed at https://dataverse.org/metrics
The list of URLs of installations on the map is available in JSON format: https://services.dataverse.harvard.edu/miniverse/map/installations-json
The list of URLs of installations configured for metrics gathering is also available in JSON format: https://dataversemetrics.odum.unc.edu/dataverse-metrics/config.json
For any given installation, you can check the version by visiting, for example, https://dataverse.harvard.edu/api/info/version
The task for this issue is to write a script that reports the version of Dataverse that's being run by each installation on the map. It should also report whether or not it has been configured for metrics gathering or not.
One goal is to continue to add installations running Dataverse 4.9 or higher to the metrics aggregator. The process for this to currently to ping @donsizemore at http://chat.dataverse.org . I suspect that some of the 29 installations of Dataverse that aren't being polled for metrics are running 4.9 or higher.
Another goal is to simply get a sense of what versions the community is running.