another implementation

[Herbert Van de Sompel]

Hi all,

It's a good day! Martin Fenner just tweeted that Uwe Schindler at Pangea just implemented some Signposting patterns. He used "identifier", "describedby", "author", and "item" relation types on landing pages.  

For example:

curl -I https://doi.pangaea.de/10.1594/PANGAEA.269663

HTTP/1.1 200 OK
Server: PANGAEA/1.0
Date: Mon, 14 Nov 2016 15:04:38 GMT
Link: <https://doi.org/10.1594/PANGAEA.269663>;rel="identifier", <https://doi.pangaea.de/10.1594/PANGAEA.269663?format=citation_ris>;rel="describedby";type="application/x-research-info-systems", <https://doi.pangaea.de/10.1594/PANGAEA.269663?format=citation_bibtex>;rel="describedby";type="application/x-bibtex", <http://store.pangaea.de/Publications/poster/pangaea-scar.pdf>;rel="item", <http://orcid.org/0000-0002-4133-2218>;rel="author", <http://orcid.org/0000-0002-9175-884X>;rel="author", <http://orcid.org/0000-0003-3096-6829>;rel="author"
X-robots-tag: index,follow,archive
Content-type: text/html;charset=UTF-8
Content-length: 24630
Set-cookie: JSESSIONID=D4E3E36B61FD6DCE1EFAFD021D196A98; Path=/; Secure; HttpOnly
X-ua-compatible: IE=Edge
X-content-type-options: nosniff

In case of this "item" link, it would be nice to have a "type" attribute with value application/pdf to convey the media type of the item.

I do not see "identifier" and "collection" relations yet at the content resource, e.g.:

curl -I http://store.pangaea.de/Publications/poster/pangaea-scar.pdf

HTTP/1.1 200 OK
Server: PANGAEA/1.0
Date: Mon, 14 Nov 2016 15:09:40 GMT

Content-type: application/pdf
Last-modified: Fri, 13 May 2005 06:23:18 GMT
Content-length: 2200936
Etag: "219568-428447d6"
Accept-ranges: bytes
X-ua-compatible: IE=Edge
X-content-type-options: nosniff

This could become:

curl -I http://store.pangaea.de/Publications/poster/pangaea-scar.pdf

HTTP/1.1 200 OK
Server: PANGAEA/1.0
Date: Mon, 14 Nov 2016 15:09:40 GMT

Link: <https://doi.org/10.1594/PANGAEA.269663>; rel="identifier", <https://doi.pangaea.de/10.1594/PANGAEA.269663>; rel="collection"
Content-type: application/pdf
Last-modified: Fri, 13 May 2005 06:23:18 GMT
Content-length: 2200936
Etag: "219568-428447d6"
Accept-ranges: bytes
X-ua-compatible: IE=Edge
X-content-type-options: nosniff

Cheers

Herbert

--

Herbert Van de Sompel
Digital Library Research & Prototyping
Los Alamos National Laboratory, Research Library
http://public.lanl.gov/herbertv/
http://orcid.org/0000-0002-0715-6126

==

[Uwe Schindler]

Hi,

Thank you for the comments!

Am Montag, 14. November 2016 16:15:30 UTC+1 schrieb Herbert Van de Sompel:

Hi all,

It's a good day! Martin Fenner just tweeted that Uwe Schindler at Pangea just implemented some Signposting patterns. He used "identifier", "describedby", "author", and "item" relation types on landing pages.  

For example:

curl -I https://doi.pangaea.de/10.1594/PANGAEA.269663

HTTP/1.1 200 OK
Server: PANGAEA/1.0
Date: Mon, 14 Nov 2016 15:04:38 GMT
Link: <https://doi.org/10.1594/PANGAEA.269663>;rel="identifier", <https://doi.pangaea.de/10.1594/PANGAEA.269663?format=citation_ris>;rel="describedby";type="application/x-research-info-systems", <https://doi.pangaea.de/10.1594/PANGAEA.269663?format=citation_bibtex>;rel="describedby";type="application/x-bibtex", <http://store.pangaea.de/Publications/poster/pangaea-scar.pdf>;rel="item", <http://orcid.org/0000-0002-4133-2218>;rel="author", <http://orcid.org/0000-0002-9175-884X>;rel="author", <http://orcid.org/0000-0003-3096-6829>;rel="author"
X-robots-tag: index,follow,archive
Content-type: text/html;charset=UTF-8
Content-length: 24630
Set-cookie: JSESSIONID=D4E3E36B61FD6DCE1EFAFD021D196A98; Path=/; Secure; HttpOnly
X-ua-compatible: IE=Edge
X-content-type-options: nosniff

In case of this "item" link, it would be nice to have a "type" attribute with value application/pdf to convey the media type of the item.

This was already added:

Uwe Schindler@VEGA:~ > curl -I https://doi.pangaea.de/10.1594/PANGAEA.269663

HTTP/1.1 200 OK

Server: PANGAEA/1.0

Date: Mon, 14 Nov 2016 22:28:10 GMT

Link: <https://doi.org/10.1594/PANGAEA.269663>;rel="identifier", <https://doi.pangaea.de/10.1594/PANGAEA.269663?format=citation_ris>;rel="describedby";type="application/x-research-info-systems", <https://doi.pangaea.de/10.1594/PANGAEA.269663?format=citation_bibtex>;rel="describedby";type="application/x-bibtex", <http://store.pangaea.de/Publications/poster/pangaea-scar.pdf>;rel="item";type="application/pdf", <http://orcid.org/0000-0002-4133-2218>;rel="author", <http://orcid.org/0000-0002-9175-884X>;rel="author", <http://orcid.org/0000-0003-3096-6829>;rel="author"

X-robots-tag: index,follow,archive

Content-type: text/html;charset=UTF-8

Content-length: 24653

Set-cookie: JSESSIONID=0911233CF1EB0F78200B1C5C11D4D96C; Path=/; Secure; HttpOnly

X-ua-compatible: IE=Edge

X-content-type-options: nosniff

 

I do not see "identifier" and "collection" relations yet at the content resource, e.g.:

 

We do not have the backlinks, as the store.pangaea.de location is just a datastore :-)

[Uwe Schindler]

This is a better example:

Uwe Schindler@VEGA:~ > curl -IL https://doi.org/10.1594/PANGAEA.867908

HTTP/1.1 303 See Other

Server: Apache-Coyote/1.1

Vary: Accept

Location: https://doi.pangaea.de/10.1594/PANGAEA.867908

Expires: Mon, 14 Nov 2016 21:15:55 GMT

Content-Type: text/html;charset=utf-8

Content-Length: 175

Date: Mon, 14 Nov 2016 21:09:55 GMT

HTTP/1.1 200 OK

Server: PANGAEA/1.0

Date: Mon, 14 Nov 2016 21:09:56 GMT

Link: <https://doi.org/10.1594/PANGAEA.867908>;rel="identifier", <https://doi.pangaea.de/10.1594/PANGAEA.867908?format=citation_ris>;rel="describedby";type="application/x-research-info-systems", <https://doi.pangaea.de/10.1594/PANGAEA.867908?format=citation_bibtex>;rel="describedby";type="application/x-bibtex", <https://doi.pangaea.de/10.1594/PANGAEA.867908?format=zip>;rel="item";type="application/zip", <http://orcid.org/0000-0003-1291-8524>;rel="author"

X-robots-tag: index,follow,archive

Content-type: text/html;charset=UTF-8

Content-length: 37800

Set-cookie: JSESSIONID=26FB959658CC552DD3F1209B40D3C84B; Path=/; Secure; HttpOnly

X-ua-compatible: IE=Edge

X-content-type-options: nosniff

Uwe Schindler@VEGA:~ > curl -I https://doi.pangaea.de/10.1594/PANGAEA.867908?format=citation_ris

HTTP/1.1 200 OK

Server: PANGAEA/1.0

Date: Mon, 14 Nov 2016 21:10:08 GMT

Link: <https://doi.org/10.1594/PANGAEA.867908>;rel="identifier", <https://doi.pangaea.de/10.1594/PANGAEA.867908>;rel="describes"

X-robots-tag: noindex,nofollow,noarchive

Content-disposition: attachment; filename=Bohleber-etal_2016.ris

Content-type: application/x-research-info-systems

Content-length: 2241

Set-cookie: JSESSIONID=FD0CF2E1275A65DE77C58509BC6BAA16; Path=/; Secure; HttpOnly

X-ua-compatible: IE=Edge

X-content-type-options: nosniff

Uwe Schindler@VEGA:~ > curl -I https://doi.pangaea.de/10.1594/PANGAEA.867908?format=zip

HTTP/1.1 200 OK

Server: PANGAEA/1.0

Date: Mon, 14 Nov 2016 21:10:11 GMT

Link: <https://doi.org/10.1594/PANGAEA.867908>;rel="identifier", <https://doi.pangaea.de/10.1594/PANGAEA.867908?format=citation_ris>;rel="describedby";type="application/x-research-info-systems", <https://doi.pangaea.de/10.1594/PANGAEA.867908?format=citation_bibtex>;rel="describedby";type="application/x-bibtex", <https://doi.pangaea.de/10.1594/PANGAEA.867908>;rel="collection", <http://orcid.org/0000-0003-1291-8524>;rel="author"

Content-disposition: attachment; filename=Bohleber-etal_2016.zip

X-robots-tag: noindex,nofollow,noarchive

Content-type: application/zip

Content-length: 305289

Set-cookie: JSESSIONID=726B8944DE7A7966023877345A0752C7; Path=/; Secure; HttpOnly

X-ua-compatible: IE=Edge

X-content-type-options: nosniff

I implemented this today in a workshop about Scholix!

The implementation details on our side is just plain stupid servlet-api programming...

But it was quite easy to implement using PANGAEA's server/metadata infrastructure! We have all information available: ORCID IDs. It will be easy to add the datacite metadata stuff soon! PANGAEA is working on updating its mapping from PANGAEA's internal metadata schema to DataCite V4... stay tuned!

FYI, the PANGAEA OAI-PMH implementation is based on Elasticsearch's REST API and just a slim wrapper on top: https://ws.pangaea.de/oai/, but that's just another one! Maybe I can make the impl availabe on Github at some point (currently, its source code is not public).