Hi, I just wondered if this were a known issue. Using Dspace 6.3 with xmlui (I have tried both Mirage and Mirage2).
An instance example is we have an entry with the a pdf bit stream. The file name has a square bracket in it. DRI shows the record stored as (I have partially anonymised this): <metadata element="citation_pdf_url"> http://.../xmlui/bitstream/1/19765/6/Text%20Text%20v20%28S2XX-2018%29%20%5b2019%5d%20XXX%201.pdf </metadata> Note the correctly encoded square brackets. %5b and %5d. This is of course the URL seen in the xmlui GUI. However the link does not work (blank browser page, tomcat local access log shows 404 being returned). BUT this link http://.../xmlui/bitstream/1/19765/6/Text%20Text%20v20%28S2XX-2018%29%202019%20XXX%201.pdf does work (i.e. just remove the %5b and %5d). My current thought is just to dig into the dspace code and remove the %5b and %5d from the query but I thought I should check if this is a known issue and/or if there is a 'better' fix. -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-community. For more options, visit https://groups.google.com/d/optout.
