Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to retrieve downloadUrl of derived images? #506

Closed
phorward opened this issue Sep 12, 2022 · 3 comments
Closed

How to retrieve downloadUrl of derived images? #506

phorward opened this issue Sep 12, 2022 · 3 comments
Labels
Priority: High After critical issues are fixed, these should be dealt with before any further issues.

Comments

@phorward
Copy link
Member

phorward commented Sep 12, 2022

This topic was discussed lately. A FileBone has derives, but in the json-renderer there's no way to get these derived downloadUrls except for the original file which is injected along with the dlkey. There's currently no solution or workaround. In the html-renderer, there's a built-in Jinja function to retrieve derived URLs for a given file. A solution for this needs to be found for json-renderer or by using an externally callable function for retrieving the URL.

@phorward phorward added the help wanted Extra attention is needed label Sep 12, 2022
@phorward phorward removed the help wanted Extra attention is needed label Jul 6, 2023
@phorward phorward added this to the ViUR-core v3.7 milestone Feb 26, 2024
@theVAX
Copy link
Member

theVAX commented Feb 26, 2024

In my opinion, for files that are public, i.e. have no expiry period, the signed download urls, including those of the preview images etc., should be stored directly on the filebone and also be part of the server response. Otherwise, paths should be provided under which the download urls can be retrieved.

@phorward
Copy link
Member Author

phorward commented Oct 7, 2024

Is this fixed by #1241?

@phorward phorward added Priority: High After critical issues are fixed, these should be dealt with before any further issues. viur-meeting Issues to discuss in the next ViUR meeting labels Oct 7, 2024
@phorward phorward removed the viur-meeting Issues to discuss in the next ViUR meeting label Oct 28, 2024
@phorward
Copy link
Member Author

Seen as fixed by #1305, but #1290 also refers to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: High After critical issues are fixed, these should be dealt with before any further issues.
Projects
None yet
Development

No branches or pull requests

4 participants