search

IIIF / api

Source for API and model specifications documents (api and model)
http://iiif.io/api
107 stars 54 forks source link

How to connect previous versions of IIIF resources across time? #2213

Open azaroth42 opened 1 year ago

azaroth42 commented 1 year ago

For example, as we migrate between systems, identifiers will change which will break annotations (and so on).

While it's not the spec's job to /solve/ persistent identifiers, we could add a field to Prezi to capture the previous identifier used for the resource. For example, we could add via to Prezi (see https://www.w3.org/TR/annotation-model/#other-identities)

While not directly used by the viewer, perhaps, it would be good to manage with the entity, in the same way as we do with seeAlso

(Thanks to Dreiss at Ghent)

azaroth42 commented 5 months ago

Eds to discuss on a call.

caitlinPerry commented 1 week ago

FYI - this issue has come up again in the NL. The Utrecht University Library is planning a migration to a system, and the change in the image identifiers is going to break many, many cross-institutional projects.

glenrobson commented 1 week ago

Note the only mention of persistance I could find is in 6.1. URI Recommendations where it says:

"Once published, they should be as persistent and unchanging as possible."

As the effect of URIs changing can be so devastating to users, could we make this statment stronger?