You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 15, 2020. It is now read-only.
The URL for any given Dash data record page often does not resolve from a direct link. I've noticed this behavior from email and from certain web tools such as wiki.
It has to do with the equals sign at the end—all Dash data landing pages have a similar URL, and it gets dropped when copying and pasting/following links all the time. If you add the “=” manually or just remove the whole “;query” string at the end, it resolves.
Of course the DOI can be used but that involves a DOI resolution service, it’s not something you can just plug in your browser to get to the record, or that someone can easily access via an email link etc., especially if they are unfamiliar with how DOIs work.
The text was updated successfully, but these errors were encountered:
The URL for any given Dash data record page often does not resolve from a direct link. I've noticed this behavior from email and from certain web tools such as wiki.
It has to do with the equals sign at the end—all Dash data landing pages have a similar URL, and it gets dropped when copying and pasting/following links all the time. If you add the “=” manually or just remove the whole “;query” string at the end, it resolves.
EX: https://dash.lib.uci.edu/xtf/view?docId=uci/ark%2B%3Db7280%3Dd1pk58/mrt-datacite.xml;query= (doesn't work from email/wiki, though it works from Github apparently)
https://dash.lib.uci.edu/xtf/view?docId=uci/ark%2B%3Db7280%3Dd1pk58/mrt-datacite.xml (works in all cases)
Of course the DOI can be used but that involves a DOI resolution service, it’s not something you can just plug in your browser to get to the record, or that someone can easily access via an email link etc., especially if they are unfamiliar with how DOIs work.
The text was updated successfully, but these errors were encountered: