Signposting implementation in DSpace 7.6

[Andrea Bollini]

Hi all,
the signposting implementation according to the FAIR profile has been merged in DSpace so it will be part of the coming 7.6 (expected on 27th June).

The current code is deployed on the public community demo so it would be appreciated a final check to verify that we haven't overseen anything.

These are two sample URLs

The publication landing page
 curl -v https://demo7.dspace.org/entities/publication/1974d7d3-9648-4dbe-b083-56374f5314e4 | more

> Link: <https://demo7.dspace.org/bitstreams/7193727d-5f9f-42a9-b1a6-521cc116e2b2/download> ; rel="item" ; type="application/pdf" , <https://demo7.dspace.org/handle/10673/248> ; rel="cite-as" , <https://schema.org/AboutPage> ; rel="type" ; type="text/html" , <https://schema.org/ScholarlyArticle> ; rel="type" ; type="text/html"

and so the file can be downloaded at

curl -v https://demo7.dspace.org/bitstreams/7193727d-5f9f-42a9-b1a6-521cc116e2b2/download

Link: <https://demo7.dspace.org/signposting/linksets/1974d7d3-9648-4dbe-b083-56374f5314e4> ; rel="linkset" ; type="application/linkset" , <https://demo7.dspace.org/signposting/linksets/1974d7d3-9648-4dbe-b083-56374f5314e4> ; rel="linkset" ; type="application/linkset" , <https://demo7.dspace.org/signposting/linksets/1974d7d3-9648-4dbe-b083-56374f5314e4/json> ; rel="linkset" ; type="application/linkset+json" , <https://demo7.dspace.org/signposting/linksets/1974d7d3-9648-4dbe-b083-56374f5314e4/json> ; rel="linkset" ; type="application/linkset+json" , <https://demo7.dspace.org/entities/publication/1974d7d3-9648-4dbe-b083-56374f5314e4> ; rel="collection" ; type="text/html" , <https://demo7.dspace.org/entities/publication/1974d7d3-9648-4dbe-b083-56374f5314e4> ; rel="collection" ; type="text/html"


Please note that we are already aware of a couple of issues, that will be solved over the next few days but I don't wont to postpone further the request for your double check:
1. in the landing page the rel="type" links should hanve not the mimetype (i.e. type="text/html"
2. https://demo7.dspace.org/signposting/linksets/1974d7d3-9648-4dbe-b083-56374f5314e4 only work if you specify the "Accept: application/linkset" Header in the request, this constrainst is going to be removed
3. the Link exposed for the file contains two times all the values
4. the file download is currently looking odd when you request it multiple times hitting the cache. You should get back a Location header redirecting you to the backend (i.e. https://api7.dspace.org/core/bitstreams/7193727d-5f9f-42a9-b1a6-521cc116e2b2/content

Thanks for your feedback on that,
Andrea

PS: this is the link to the current documentation on the DSpace side https://github.com/DSpace/RestContract/blob/main/signposting.md

[Herbert Van de Sompel]

Hi Andrea,

That’s great news!

A quick question: Since you are using Linksets, why is there no “linkset” link on the landing page? 

I’m currently on a tablet so can’t do curl with Accept header to look at the linkset but will do when I get to my laptop.

Greetings

Herbert

On Jun 15, 2023, at 16:38, 'Andrea Bollini' via signposting <signp...@googlegroups.com> wrote:

Hi all,

--
You received this message because you are subscribed to the Google Groups "signposting" group.
To unsubscribe from this group and stop receiving emails from it, send an email to signposting...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/signposting/f188c5b0-a071-4ebc-91e8-d1ab7d9a542bn%40googlegroups.com.

[Andrea Bollini]

Thanks for the quick feedback Herbert: added to the list of fixes.

The example 

https://signposting.org/FAIR/#examples2

on the signposting website is a bit misleading as there is not one related to the header of the landing page and the text says

"For the landing page, this can be done using the HTTP Link header and/or via <link> element's in the HTML's"

It is obvious for me what you are asking (and) but our developer, that is not so familiar with the topic has overseen that and chosen the "or" implementing them only in the html head section.

It could be useful for other to enhance this part in the website.

Andrea

[Herbert Van de Sompel]

Thanks a lot for the feedback! I’ll update the wording. When I’m on my laptop ;-)

Greetings 

Herbert 

On 15 Jun 2023, at 18:02, 'Andrea Bollini' via signposting <signp...@googlegroups.com> wrote:

Thanks for the quick feedback Herbert: added to the list of fixes.

To view this discussion on the web visit https://groups.google.com/d/msgid/signposting/a7573da4-d361-4d19-bc69-fbee74ec3cf6n%40googlegroups.com.

[Herbert Van de Sompel]

hi Andrea,

I had a look at the JSON linkset and see quite some issues:

{
  "linkset": [
    {
      "item": [
        {
          "href": "https://demo7.dspace.org/bitstreams/7193727d-5f9f-42a9-b1a6-521cc116e2b2/download",
          "type": "application/pdf"
        }
      ],
      "type": [
        {
          "href": "https://schema.org/AboutPage",
          "type": "text/html"
        },
        {
          "href": "https://schema.org/ScholarlyArticle",
          "type": "text/html"
        }
      ],
      "anchor": "https://demo7.dspace.org/entities/publication/1974d7d3-9648-4dbe-b083-56374f5314e4",
      "cite-as": [
        {
          "href": "https://demo7.dspace.org/handle/10673/248"
        }
      ]
    }
  ],
  "linksetNodes": []
}

1. no landing page "anchor" is declared. the landing page should be the anchor for the item, type, cite-as, describedby, author, license links.

2. describedby links are missing for the landing page

3. cite-as link is missing for the landing page

4. text/html should not be provided for the type links

5. the URI for the bitstream (anchor https://demo7.dspace.org/entities/publication/1974d7d3-9648-4dbe-b083-56374f5314e4) is not the same as the URI at the end of the item link (https://demo7.dspace.org/bitstreams/7193727d-5f9f-42a9-b1a6-521cc116e2b2/download)

6. describes links are missing, pointing from metadata record to landing page (anchor is URI of a metadata record)

7. cite-as is provided for the bitstream. the spec says that only needs to be done if the PID of the datastream is different than the PID at the landing page

8. I don't know what the linksetNodes element is

Greetings

Herbert

--

You received this message because you are subscribed to the Google Groups "signposting" group.
To unsubscribe from this group and stop receiving emails from it, send an email to signposting...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/signposting/f188c5b0-a071-4ebc-91e8-d1ab7d9a542bn%40googlegroups.com.

--

==================

Herbert Van de Sompel

https://hvdsomp.info

https://orcid.org/0000-0002-0715-6126

[Herbert Van de Sompel]

hi Andrea,

I have updated https://signposting.org/FAIR/#examples2 by including examples for providing links to support discovery of Link Sets using both HTTP Link and HTML <link>.

Greetings

Herbert

To view this discussion on the web visit https://groups.google.com/d/msgid/signposting/a7573da4-d361-4d19-bc69-fbee74ec3cf6n%40googlegroups.com.

[Andrea Bollini]

great thanks you. We are processing the issues that you have reported, I will keep you informed.

Andrea

[Andrea Bollini]

Hi,

we have (hopefully) processed your feedback so that the official DSpace 7.6 should now have a correct implementation of the signposting FAIR profile.

For the describeby right now we are only able to provide the metadata in a single format, based on the Datacite schema 3. Unfortunately this was what we have available out-of-box in plain DSpace but it is expected to be improved in new versions.

Please let me know If you found other issues so that they can be included in future dspace updates!

Best,

Andrea