Resolvind via UUID is not possible any more after version update

Open Diederka opened this issue 4 years ago • 1 comments

A library which uses our Data via OAI asked me my why our link resolver don't work anymore. The link resolver uses our object UUIDs and via the resolver the respective entitiy could be linked to. An example for the UUID: ad43d7fc-6067-4c98-a977-874c477a0f60

https://classicmayan.kor.de.dariah.eu/blaze#/entities/ad43d7fc-6067-4c98-a977-874c477a0f60 I know that the "blaze" isn't used in our URLs anymore since the database update. But when I skip them nevertheless a resolving of the uuid is not possible. https://classicmayan.kor.de.dariah.eu/#/entities/ad43d7fc-6067-4c98-a977-874c477a0f60 Is the resolving of UUIDs not anymore possible with the new version (4.1.0-pre) of the kor software? Is there an alternative to create links via the uuids? Can you help me out?

Nov 21 '21 18:11 Diederka

Hey!

Yes, the link resolver is still there, it uses other urls though: With a browser, you might want to use https://classicmayan.kor.de.dariah.eu/resolve/uuid/ad43d7fc-6067-4c98-a977-874c477a0f60

then you are redirected to the entity page.

When using the JSON API, you can either use the same url with a .json format specifier at the end https://classicmayan.kor.de.dariah.eu/resolve/uuid/ad43d7fc-6067-4c98-a977-874c477a0f60.json

this redirects to the default JSON url for the entity. You can also use the Accept: application/json http header instead of the format specifier.

In the specific case of the uuid, you can also use https://classicmayan.kor.de.dariah.eu/entities/ad43d7fc-6067-4c98-a977-874c477a0f60

which also returns the JSON.

Nov 21 '21 19:11 moritzschepp