[MGNLDMS-155] Better mechanism to distinguish between inline viewing and direct downloads Created: 23/Jan/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Document Management System (closed)
Component/s: None
Affects Version/s: 1.3
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
supersession
supersedes MGNLDMS-100 DMSDownloadServlet should allow inlin... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Sorry for all the forth and back in that topic. After a few quite minutes I think that the following solution might be best:

  • if you want to perform a direct download or view the content in the browser depends on the usecase and not on the file type
  • showing the content in the browser should be the default behavior (pdf, images, flash, word, ...)
  • to trigger a direct download the system provides a specific url or parameter
    • a) download=true
    • b) /dms/file.download.ext (for cachability)
    • c) /dms-download/file
  • the dms dialog uses the direct download link
  • the dms dialog shows the image (similar to the binary control in normal dialogs)


 Comments   
Comment by Philipp Bracher [ 23/Jan/09 ]

It might actually be that we don't have to change anything on the implementation but just change the default configuration:

  • voter based on the download parameter
  • virtual uri mapping which transforms: /dms/*/filename.download.ext -> /dms/*/filename.ext?download=true
Comment by Jan Haderka [ 23/Jan/09 ]

Sounds as reasonable solution and indeed having voters in place it would be easy to do. Still we would need to modify all the places where we have links in the dialogs ... File Control for sure, perhaps something in DMSDialog as wel, maybe dataFile control as well ... anything else?

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 00:48:57 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.