Dataverse Installation Data Spreadsheet

[TaniaSchlatter]

The goal of this issue is to document and structure an effort to create a spreadsheet for the Dataverse product team to use for contact information and as a source for basic, consistent installation data. The Crowdsourced data from the community is the most accurate in terms of name, description, hostname. the goal is to get a complete list of installations with the most accurate name and hostname possible, as well as most up to date contact email.

• copy name, description, hostname, contact from the community crowd-sourced spreadsheet, and create a new spreadsheet
• Review Danny's spreadsheet that he uses for sending emails (Mapped, Unmapped...). and add name, description, hostname, contact that are missing from the newly created spreadsheet. Do not overwrite data. Note conflicts, and track sources. Ask Danny what to do about former installations – if they should be included or not in this list.
• add the same data from the most recent, up to date installation archetype work (Tool Tips - Help Tip Rollover Popups Populated from User Guides #99). Again, do not overwrite data. Note conflicts, and track sources. The result should be a list of all installations on one tab of a spreadsheet.
• review what data we have that is not included (from Dataverse Installation Archetypes dataverse.harvard.edu#99), and determine what data we want to track in this spreadsheet.
• determine ownership
• determine process for updating

[TaniaSchlatter]

Questions to answer:

How does an installation get recognized/made "official"?

• Determine a process for tracking installations. There are multiple starting points and multiple spreadsheets. Define a process for an official list that meets our needs.

• who to contact
• etc.

[jggautier]

I think the spreadsheet is at https://docs.google.com/spreadsheets/d/1UZXIMmmj7xcML2p-C_5VGlkdP60ETlTGpZmS-ZNkToo.

It's out of date so the last two tasks about ownership and updating are still standing.

The extra context about each installation, such as archetypes and configurations that give us some information about the types of installations out there, can be very helpful for ux research, so I would like to retain and update this information as much as possible, although I think it would be better to not have to maintain overlapping information in this and the "crowdsourced" spreadsheet, which has continued to be up to date since it feeds the map and metrics pages on dataverse.org.

About determining a process for tracking installations, the process for updating the "crowdsourced" spreadsheet isn't perfect, but it's worked well enough for a few years now. Maybe that process could be used to also update and maintain the more contextual information about each installation. And we could do survey each installation every year.

[pdurbin]

Sure, using the crowdsourced spreadsheet sounds fine. Related:

• capture ideas from the Dataverse Installation Personas poster by @janetm dataverse-installations#16