OpenAtlas

• Use already existing backend functionality to add an external reference (URL) to a type. See e.g. https://demo.openatlas.eu/insert/external_reference/15781
• The API looks if there are URLs connected and takes the first one it finds
• We document somewhere (manual, type description, ...) this behavior

In case this is ok with you, Bernhard: just go for it :)

• We should keep in mind that not every license might be available online, e.g. a custom made license
• It is also possible to add a file to a type which might be linked to but it would only be served if:
  • The API is set to public
  • The file is set to public
  • The file has a license (but we could write an exception for that)

If we want to also use links to an attached file we would still have to think if we want to prioritize the external link or the file if both are available and, like with external links, there might be more than one.

For the purpose of IIIF licensing, one link is enough and more is not supported.
I don't know how many image licenses are not online available, maybe we postpone an implementation of files for the time, when it is needed.

Sure, lets concentrate on linking an external reference for now. I just wanted to share (and document) my thoughts about it ;)