Skip to content
Please note that GitHub no longer supports your web browser.

We recommend upgrading to the latest Google Chrome or Firefox.

Learn more

/citeas-api

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Leverage links with the "cite-as" relation type #58

Open
hvdsomp opened this issue Dec 20, 2019 · 1 comment
Open

Leverage links with the "cite-as" relation type #58

hvdsomp opened this issue Dec 20, 2019 · 1 comment

Comments

@hvdsomp
Copy link

@hvdsomp hvdsomp commented Dec 20, 2019

RFC8574 defines the "cite-as" link relation type that can, among others, be used to point from a landing page URI to the URI that should be used for citation purposes. A major motivation for defining the relation type was that research found that a very significant number of resources that have a DOI are not cited by means of their DOI but rather by means of their landing page URI [1].

A link with the "cite-as" relation type would typically be provided in the HTTP Link header of the landing page. For example, using the landing page https://easy.dans.knaw.nl/ui/datasets/id/easy-dataset:61891 for a dataset in the DANS EASY collection:

curl -I https://easy.dans.knaw.nl/ui/datasets/id/easy-dataset:61891

HTTP/1.1 200 OK
Date: Fri, 20 Dec 2019 08:28:07 GMT
Link: <https://doi.org/10.17026/dans-zm3-nkk4> ; rel="cite-as"
Content-Type: text/html;charset=UTF-8
Content-Language: en-US

The "cite-as" approach is part of the broader Signposting effort aimed at clarifying common landing page patterns to machines by using utterly simple REST/HATEOAS techniques. Early Signposting adopters typically implement "cite-as" with priority. As such:

  • It would be nice if the CiteAs service could take "cite-as" links provided on landing page URIs into account
  • It would be great if the CiteAs effort would promote the use of "cite-as" links

[1] Van de Sompel, H., Klein, M., and Shawn, J. (2016) Persistent URIs Must Be Used To Be Persistent. Poster at WWW 2016; arXiv preprint at http://arxiv.org/1602.09102
@hvdsomp

This comment has been minimized.

Sign in to view
Copy link
Author

@hvdsomp hvdsomp commented Dec 20, 2019

Note that other Signposting patterns can also be leveraged by the citeas.org service. Links with the "describedby" relation type provided by the landing page URI lead to bibliographic information about the artifact the landing page is about. Using the same landing page as above, the complete HTTP Link header is as follows:

curl -I https://easy.dans.knaw.nl/ui/datasets/id/easy-dataset:61891

HTTP/1.1 200 OK
Date: Fri, 20 Dec 2019 08:28:07 GMT
Link: <https://doi.org/10.17026/dans-zm3-nkk4> ; rel="cite-as",
 <https://doi.org/10.17026/dans-zm3-nkk4> ; rel="describedby" ; type="application/vnd.datacite.datacite+xml",
 <https://doi.org/10.17026/dans-zm3-nkk4> ; rel="describedby" ; type="application/vnd.citationstyles.csl+json"
Content-Type: text/html;charset=UTF-8
Content-Language: en-US

The bibliographic information that is linked to is - in this case - obviously also available from the DOI API. But that requires the client to have out-of-bound knowledge about that API. With the above "describedby" links, a client can just follow its nose to the metadata.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@hvdsomp
You can’t perform that action at this time.