update "return_to_dataverse_url" to use File landing page

[raprasad]

Summary: Geoconnect's "Return to Dataverse" button should go to dataset page or file page depending on the source.

Workflow

• User clicks "Map Data" and goes to Geoconnect
• Within Geoconnect, the User will click either the "Cancel" button or "Return to Dataverse" button
• Currently both options return the user to the Dataset landing page containing the file being mapped
• With the advent of the file page, the "Return to Dataverse" link should go back to where the user came from--either the file page or dataset page.

Work

• Send additional "dataverse_session_url" attribute to Geoconnect containing appropriate page to bring user
• Methods to look at for sending this info
  • mapDataFileTokenOnlyOption
  • getWorldMapDatafileInfo

Item 2: Decision

• WorldMap contains a Dataverse source url which is currently the Dataset page
• Should this change to the File page?
• What to change. Update this line in WorldMapRelatedData.java:

jsonData.add("return_to_dataverse_url", dset_version.getReturnToDatasetURL(serverName, dset));

• Return to Dataverse link
  • If map exists, always re-send metadata to Dataverse

---

Work

Link stored for WorldMap users

When mapping files, WorldMap stores a link back to the Dataset of that file.

With the new file page, the link can now go directly to the file page--by updating this line in WorldMapRelatedData.java:

jsonData.add("return_to_dataverse_url", dset_version.getReturnToDatasetURL(serverName, dset));

Link stored for Dataverse session

1.3.2017 - With the addition of the file page, a user may now map "from" a Dataset page or File page -- the source page must be passed to Geoconnect for a "clean return" back to dataverse

[djbrooke]

We discussed this in the sprint planning meeting yesterday, and the title and description of the issue was changed around a few times to capture the correct tasks here. These changes are in the Dataverse codebase.