Mark Wilkinson (Sep 25 2023 at 07:37): Mark Wilkinson (Sep 25 2023 at 07:37):Hi all! I'm looking at the new Signposting features. I am getting an unexpected message format when I follow the linkset links.
curl -v -H "Accept: application/linkset+json" https://dataverse.harvard.edu/api/datasets/:persistentId/versions/1.0/linkset?persistentId=doi:10.7910/DVN/Z2JD58
{"status":"OK","data":{"linkset":[{"anchor":"https://dataverse.harvard.edu/dataset.xhtml?persistentId=doi:10.7910/DVN/Z2JD58","cite-as"......
The "status OK, data" portion is unexpected. The Signposting benchmark for a linkset returns as follows:
curl -v -H "Accept: application/linkset+json" https://s11.no/2022/a2a-fair-metrics/07-http-describedby-citeas-linkset-json/linkset.json
{ "linkset": [ { "anchor": "https://s11.no/2022/a2a-fair-metrics/07-http-describedby-citeas-linkset-json/", "cite-as": ......
Which one is correctd? Or are they both correct, and my code needs to detect which format is being returned? I don't see the extra key/values in the examples at https://www.rfc-editor.org/rfc/rfc9264.html#name-json-document-format-applic
Any advice appreciated!
Mark
Philip Durbin 🚀 (Sep 25 2023 at 12:35):That status OK data pattern is common throughout Dataverse's "native" API. If it should be absent in the context of Signposting, please feel free to create an issue at https://github.com/IQSS/dataverse/issues
Mark Wilkinson (Sep 25 2023 at 13:26):Philip Durbin said:
That status OK data pattern is common throughout Dataverse's "native" API. If it should be absent in the context of Signposting, please feel free to create an issue at https://github.com/IQSS/dataverse/issues
done
Philip Durbin 🚀 (Sep 25 2023 at 13:56):#9953 is looking good! Thanks!
Last updated: Oct 30 2025 at 06:21 UTC