IQSS / IQSS/dataverse-installations

What to do with an installation we find that isn't on the map?

Open
#145 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
HTML
Stars
6
Forks
13
Avg merge
25m
Merged PRs (30d)
1

Description

Hello,

checking on re3data I found a few Dataverse installations that are not listed on the map (as @pdurbin said, being on the map isn't mandatory and some of them could be in their demo phase).
What do we do with them? Could it be interesting to add a new sheet on the file about installations but specifying they are not on the map (for several reasons which maybe it is not right to explicitate)?
Give this matter an hand, please :)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no file, test, or entry point. Review the current map and installation data, then read the existing discussion to understand the proposed handling; done requires an agreed policy and an updated listing if the project decides to include these installations.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.