map of Dataverse installations, installations as a dataset, launch year

[Philip Durbin]

Hello Dataverse enthusiasts!

In evenings and weekends I've been hacking on prototypes of a *new* map of Dataverse installations. I'm attaching a screenshot of what I have so far and I'd love feedback and ideas.

One of the main drivers for this is that I'd like the entire process to be more participatory and "hackable", if you will. By this I mean that instead of the map being powered by a centralized database controlled by Harvard (the current map), we could try crowdsourcing some of the data from Google spreadsheets and aggregate that data into JSON and/or tabular files for both creating a map and (eventually) publishing the tabular file in Dataverse itself, maybe under https://dataverse.harvard.edu/dataverse/open-source-at-harvard . It would be fun to play with the data in Data Explorer! I'm attaching a screenshot of that too. :)

Other ideas I have (and you can see some of these on the attached prototype map already):

- Give a badge to installations that are members of the Global Dataverse Community Consortium (GDCC): http://dataversecommunity.global

- Indicate which installations are represented on aggregate counts of datasets, downloads etc on https://dataverse.org/metrics (which means they are running a new enough version of Dataverse).

- Provide the data in an HTML table.

- Provide the data in a tabular file with a DOI in Dataverse.

- If the installation has created a board for prioritizing GitHub issues[1], link to it.

- Add columns to the crowdsourced spreadsheet that helps categorize installations in various ways. How are Dataverse installations similar? How are they different?

These are some of my ideas but I want to hear YOUR ideas! :)

Please reply here with any feedback you have!

Finally, if you'd like to play around with the concept of crowdsourcing the data, please see this new "Crowdsourced information about Dataverse Installations" spreadsheet at https://docs.google.com/spreadsheets/d/1bfsw7gnHlHerLXuk7YprUT68liHfcaMxs1rFciA-mEo/edit?usp=sharing

I'm especially interested in the "launch year" for each installation of Dataverse. By this I mean the year you went live with your installation of Dataverse. Once we have this data we can make an updated plot of growth over time, more installations year after year. I'll attach a version from 2018.

I hope this isn't too much at once!

Thanks!

Phil

p.s. On the technical side, right now I'm using Leaflet and OpenStreetMap. No database. Everything in the browser. I'm using Web Components and the new "template" tag for dynamically creating the table. Without any server side component to worry about (such as Django), the map becomes much more hackable. I do still have a dream of "eating our own dogfood" in the sense of having the map be created and powered by Geoconnect and WorldMap but it was easier for me to get started with Leaflet. The code is an absolute nightmare right now but if you want to see it, for now you can find it at http://tmp.greptilian.com/tmp/dataverse-installations/mymap.html

1. boards for prioritizing issues (for each installation of Dataverse) https://groups.google.com/d/msg/dataverse-community/z8ugn2KzNSc/zt7COeRYBQAJ

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

[Philip Durbin]

Me again with an update on my weekend hacking on a new map for the Dataverse community!

The "too long, didn't read" is this:

- Attached, please find a screenshot of how the new map looks now.

- I'm trying to provide "badges" for stuff like CoreTrustSeal, GDCC membership, etc.

- The map is now available at https://iqss.github.io/dataverse-installations/

- The code is now available at https://github.com/IQSS/dataverse-installations

Here's the longer version.

In the attached screenshot, I'm showing QDR as an example of the new popup because they earned a lot of "badges" on my new map. By "badge", all I mean is that when you click the dot for QDR on the map, the popup contains the following extra information:

- A link to QDR's CoreTrustSeal certification

- A link to QDR's advertised harvesting sets

- A link to QDR's project board of prioritized GitHub issues

- Mention of QDR's membership in the Global Dataverse Community Consortium (GDCC)

- Mention that QDR is included in https://dataverse.org/metrics (because their version of Dataverse is new enough)

I'll include a dump of the JSON for QDR below so you can see how I'm representing the data right now (subject to change). In addition, the following aren't exactly badges but the popup can also include:

- A "More..." link after the description if you have configured :NavbarAboutUrl

- The launch year for your installation

I'd like to crowdsource lots of information but I think for now I'm going to focus on gathering the year that all installations launched. So I'll probably start nagging you all for this information (separately, of course, not on this thread). To provide me the year that you launched your installation of Dataverse, please do one of the following:

- Email me directly

- Comment on https://github.com/IQSS/dataverse-installations/issues/7

- Comment on or request edit access to the new "Crowdsourced information about Dataverse installations" spreadsheet: https://docs.google.com/spreadsheets/d/1bfsw7gnHlHerLXuk7YprUT68liHfcaMxs1rFciA-mEo/edit?usp=sharing

If you're interested in the code (all client-side and no database to worry about!), probably the easiest place to reach me is http://chat.dataverse.org or you can open a GitHub issue at https://github.com/IQSS/dataverse-installations/issues

If you have any questions or comments about any of the above, please do not hesitate to ask or reply! Feedback is very welcome!

Thanks!

Phil

p.s. Here's a dump of info we have for QDR, for example, collected from a variety of sources (see the Python script in the repo) that we use to create the new map:

{
  "name": "QDR Main Collection",
  "description": "QDR curates, stores, preserves, publishes, and enables the download of digital data generated through qualitative and multi-method research in the social sciences. The repository develops and disseminates guidance for managing, sharing, citing, and reusing qualitative data, and contributes to the generation of common standards for doing so. QDR’s overarching goals are to make sharing qualitative data customary in the social sciences, to broaden access to social science data, and to strengthen qualitative and multi-method research.",
  "lat": 43.038013,
  "lng": -76.135566,
  "hostname": "data.qdr.syr.edu",
  "metrics": true,
  "country": "USA",
  "continent": "North America",
  "about_url": "https://qdr.syr.edu/about",
  "harvesting_sets": [
    "qdr_whole"
  ],
  "gdcc_member": true,
  "core_trust_seals": [
    "https://www.coretrustseal.org/wp-content/uploads/2018/11/Qualitative-Data-Repository.pdf"
  ],
  "doi_authority": "10.5064",
  "board": "https://github.com/orgs/IQSS/projects/6"
}

[Janet McDougall - Australian Data Archive]

Nice work there Phil, building up profiles (personas!)

[Philipp at UiT]

Great work, Phil! We use to show this map in presentations about our repository.

Best, Philipp

[Sebastian Karcher]

This is nice! Thanks Phil. And you picked such a good example ;)

I the spirit of linked data, how about including re3data and/or fairsharing DOIs, too?

10.17616/R3CS51 and 10.25504/FAIRsharing.bmz5ap for QDR, e.g.

[Philip Durbin]

Great idea, Sebastian. I haven't added those URLs to the map yet but the other day I did add columns in the "spreadsheet maintained by IQSS" spreadsheet and populated those columns for QDR and Harvard Dataverse. (To be honest, I'm not sure if I'd heard of FAIRsharing.) That spreadsheet is linked from the README at https://github.com/IQSS/dataverse-installations

In related news, two more installations were just added to the old map and I'm looking for a volunteer to run a Python 3 script and make a pull request to add these installations to the new map (and document the process if you are willing): https://github.com/IQSS/dataverse-installations/issues/14

To be clear, my plan is not to maintain two maps forever. If the community helps me make the new map better and better (the new map is much more lightweight and "hackable", if you will, than the old map), I can imagine the old map fading away. The Dataverse community deserves a better map and I'd like to thank Don Sizemore and Philipp Conzett for contributing already to the new map!

Finally, please do not forget to send me your launch year, if you haven't done so already! So far I have the launch year for 9 out of 50 installations.

Thanks!

Phil

p.s. Yes, that issue is flagged as a "Hacktoberfest" issue: https://groups.google.com/d/msg/dataverse-community/ootwCQL-4K4/00QO3__8CQAJ

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/672dfd9a-7d86-4c10-8c4a-41bbde32b8db%40googlegroups.com.

[Philip Durbin]

Thank you to Sherry Lake for making a pull request to copy the two new installations to the new map!

Here's a handy link to the new map, which now shows all 50 (!!!) installations of Dataverse: https://iqss.github.io/dataverse-installations/

If anyone else wants to hack on the map, please get in touch! :)

If you have ideas for the new map, please continue to reply to this thread (or start a fresh one) or open issues at https://github.com/IQSS/dataverse-installations/issues

Thanks!

Phil