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

Stats: Create a way to voluntarily, automatically record when a new Dataverse goes online. #2284

Closed
kcondon opened this issue Jun 18, 2015 · 5 comments
Labels
Component: Code Infrastructure formerly "Feature: Code Infrastructure" Feature: Installer Type: Suggestion an idea User Role: Superuser Has access to the superuser dashboard and cares about how the system is configured

Comments

@kcondon
Copy link
Contributor

kcondon commented Jun 18, 2015

People have asked about keeping track of Dataverse installations. Why don't we automate this but on a voluntary basis? Perhaps a "join the network" feature or register for news or something like that?

@kcondon kcondon added UX & UI: Design This issue needs input on the design of the UI and from the product owner Type: Suggestion an idea Status: Design labels Jun 18, 2015
@eaquigley
Copy link
Contributor

This could tie in with a request I've received to be able to check off if an installation wants to be harvested or not. If they allow harvesting then we will know about them and be able to aggregate installations that way.

On Jun 18, 2015, at 5:26 PM, kcondon <notifications@github.commailto:notifications@github.com> wrote:

People have asked about keeping track of Dataverse installations. Why don't we automate this but on a voluntary basis? Perhaps a "join the network" feature or register for news or something like that?


Reply to this email directly or view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_IQSS_dataverse_issues_2284&d=BQMCaQ&c=WO-RGvefibhHBZq3fL85hQ&r=Y9aY3P6kFFpmMLaYYO_id08dS3gL1xWMQuI2CZ74PoI&m=G_0PjxexrHUiB2N4-_BQ7Hjv_QNG_7FDMDCBjRaP0-0&s=c5HXp3DP0NaQkSX8QajiBXyeYo0kHIcv8ovkzIv1IbQ&e=.

@scolapasta scolapasta modified the milestone: In Review Jun 26, 2015
@mheppler mheppler added Component: Code Infrastructure formerly "Feature: Code Infrastructure" Feature: Installer and removed UX & UI: Design This issue needs input on the design of the UI and from the product owner labels Jan 27, 2016
@scolapasta scolapasta removed this from the Not Assigned to a Release milestone Jan 28, 2016
@mheppler
Copy link
Contributor

mheppler commented Sep 2, 2016

Related to: Metrics page for Dataverses #1971; and: Metrics: Display visualizations on dataverse.org #3230

@pdurbin pdurbin removed the Triaged label Jun 26, 2017
@pdurbin
Copy link
Member

pdurbin commented Jun 26, 2017

This could tie in with a request I've received to be able to check off if an installation wants to be harvested or not. If they allow harvesting then we will know about them and be able to aggregate installations that way.

I like this idea. See also this related thread: https://groups.google.com/d/msg/dataverse-community/fqyVxWZSDRA/q5mf4PvZBQAJ

Also, we'd like a description of the new installations as they come online according to IQSS/miniverse#52 .

@pdurbin pdurbin added the User Role: Superuser Has access to the superuser dashboard and cares about how the system is configured label Jul 12, 2017
@pdurbin
Copy link
Member

pdurbin commented Jul 19, 2019

People have asked about keeping track of Dataverse installations.

Right now installations are tracked in two locations:

  • The database behind the map on the https://dataverse.org . The code is in miniverse but I recently copied it over to https://github.com/IQSS/dataverse-installations and believe it should be maintained (hopefully with help from the community) as an independent project, especially since IQSS does not maintain miniverse anymore. The list of installations from this database is also reused for the list of installations at https://dataverse.org/metrics (so that the names match).
  • A Google spreadsheet internal to IQSS. This spreadsheet contains not only installations on the map but also installations that are in the processes of going live.

Under the "going live" section of the installation guide, we encourage installations to tell us they'd like to be added to the map: http://guides.dataverse.org/en/4.15.1/installation/config.html#putting-your-dataverse-installation-on-the-map-at-dataverse-org

@pdurbin
Copy link
Member

pdurbin commented Apr 12, 2022

https://github.com/IQSS/dataverse-installations is definitely what we're using these days to track installations. In my last comment (from 2019!) I mentioned miniverse but dataverse-installations is completely independent of it and has been for years.

Also, as of 5.8 and e9ea9b4 we started advertising the map (that datavese-installations repo) in all of our release notes.

@pdurbin pdurbin closed this as completed Nov 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Code Infrastructure formerly "Feature: Code Infrastructure" Feature: Installer Type: Suggestion an idea User Role: Superuser Has access to the superuser dashboard and cares about how the system is configured
Projects
None yet
Development

No branches or pull requests

5 participants