You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, bitstreams open in the main window if the file size is below the threshold value. It would be better to open it in a new tab.
Users go back and forth. As the bitstream and metadatas may differ, it would be better to see both at the same time in different tabs.
Hi @alanorth I understand that your issue proposes to open the bitstream inline instead of download. We can achive this by configuring a high value to the threshold parameter webui.content_disposition_threshold.
I offer to open it in browser always in a new tab. The users we talk go back and forth among the pdf and item page. That creates a bad user experience.
If that behaviour (opening the bitstream on the same page) has any benefit to user, this can be done by a parameter. But if there is no benefit of the user, I think that bitstreams must always open in new tab of browser if the file size is below the threshold value.
@erpnedir Ah yes you are right, I filed that issue over a year ago and forgot that it's slightly different. The bug is with the content-disposition header behaving differently in DSpace 7.
Regarding your suggestion to always open bitstreams in a new window, we should get more feedback from other repository administrators to see if their users feel the same. Currently the only links that DSpace opens in a new window are those that are external to the site (for example DOIs or other external links on the item view page).
Currently, bitstreams open in the main window if the file size is below the threshold value. It would be better to open it in a new tab.
Users go back and forth. As the bitstream and metadatas may differ, it would be better to see both at the same time in different tabs.
Some discussion may be seen on mail thread: https://groups.google.com/g/dspace-community/c/6DzqJsv2mcI/m/lmKlvI-xBgAJ
The text was updated successfully, but these errors were encountered: