Feature #1933
closed
API: Display images without extension in URL
Description
Display images endpoint need the ID of the file and the extension of the image file. It would be easier to handle the endpoint for clients if they don't need to know the file extension.
Objective
Old:
../api/display/12345.jpg
New:
../api/display/12345
Updated by Alexander Watzinger over 1 year ago
I'm not sure how the client would be able to find out the extensions themselves. In the backend we do it with basically searching in the folder, which the client has no access to.
Updated by Bernhard Koschiček-Krombholz over 1 year ago
That is the point. The client has to use the link provided by the API. But if the client has only the image ID, it can not get the file. Therefore, the display_image function has to adopted that it can process IDs without file extension.
Updated by Alexander Watzinger over 1 year ago
But how does this work than with existing frontends work, e.g. Shahi? Anyway, I linked the image issue of the new OpenAtlas Discovery so we can figure this out together with the frontend team.
Updated by Alexander Watzinger over 1 year ago
- Related to Feature #1931: Display images added
Updated by Bernhard Koschiček-Krombholz over 1 year ago
- Status changed from Acknowledged to Closed
- Assignee set to Bernhard Koschiček-Krombholz
- Target version changed from Wishlist to 7.10.0
Currently, OpenAtlas Discovery retrieves the entity as Linked Places JSON. There is a key, depiction, with the link to the file entity and to the display URL (ID + extension) if the file has a license.
But some projects, e.g. THANADOS, just has the ID for the image and not the extension. So it was asked if it can be changed.