IQSS / IQSS/dataverse-installations

As a Dataverse installation admin or user, I'd like to know which and how many repositories are based in a location

Open
#81 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

When markers on the current Dataverse installations map are too close together, the overlapping can make it look like there's only one marker:

Screen Shot 2020-09-14 at 10 39 53 AM

It looks like there are five markers in Brazil, but there are six. We don't see and can't click on the sixth until we zoom in:

Screen Shot 2020-09-14 at 11 21 40 AM

The administrator of a Dataverse installation in Brazil thought the installation wasn't on the map because its marker was hidden behind another marker. This is probably already the case in areas with more markers, like western Europe.

Hidden markers will make it harder for people to find installations in locations with lots of markers. And as more markers are added and hidden, the map will become less of an indication of the growing number of Dataverse installations.

One solution for this using the current map are animated marker clusters. Leaflet has a customizable plugin at https://github.com/Leaflet/Leaflet.markercluster and links to an example at https://leaflet.github.io/Leaflet.markercluster/example/marker-clustering-realworld.388.html.

Other solutions might involve using a list or table of installations that people can navigate to find installations in an area or find a particular installation.

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 does not name files or tests. Start by locating the current Dataverse installations map implementation and its marker behavior, then compare Leaflet.markercluster with a navigable installations list or table. Done means users can identify and access all installations in locations where markers overlap.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.