Dataverse Installation Data Spreadsheet
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
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 (#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 IQSS/dataverse.harvard.edu#99), and determine what data we want to track in this spreadsheet.
- determine ownership
- determine process for updating
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the community crowdsourced spreadsheet, Danny's Mapped/Unmapped spreadsheet, and the installation archetype work in #99. Compare the remaining data, record conflicts and sources, then document which fields belong in the consolidated installation list, who owns it, and how updates should happen.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100