GeoConnnect: Can map restricted files and restrict mapped files but anyone can download from WorldMap

[kcondon]

While testing World Map, it was discovered that the generic username "dataverse_user" is displayed as a link on the map page. Clicking on it lists all mapped files generated by dataverse using that generic user.

This was unexpected but not viewed as a problem because there is an assumption that all data is public -mapped data is required to be published and assumed to not be restricted.

Core Issue (Dataverse codebase change):

"However you can map restricted files and restrict mapped files, giving the impression of controlled access. This is mostly true from the Dataverse side but not from the World Map side via the owner link. You can use the Download function to download the data in csv format."

Fix

• Do not allow mapping of restricted files (even if formerly public).
• Question: If a formerly unrestricted and published file has a map, is that OK? e.g. Should it be removed from the WorldMap?

[raprasad]

Answer to question at end of issue:

---

YES, delete the newly restricted file from WorldMap

Upon a mapped file being restricted, Dataverse makes an API call to Geoconnect.

A new Geoconnect endpoint will:

1. Receive datafile id + installation name from Dataverse
2. Make an API call to WorldMap to:
   • Verify that this is a Dataverse-created layer on WorldMap (existing WorldMap endpoint)
3. Deletes the layer (existing WorldMap endpoint)

Note: Step 1 above can be made into a two step process:

1. Dataverse sends a callback url to geoconnect with a token
2. Geoconnect uses the callback + token to retrieve the datafile id + installation name from Dataverse