Uploaded image for project: 'DSpace'
  1. DSpace
  2. DS-862

Add ability to rename bitstreams (filenames) in XMLUI



    • Type: Improvement
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2, 1.7.0, 1.7.1
    • Fix Version/s: 1.8.0
    • Component/s: XMLUI
    • Labels:
    • Attachments:
    • Comments:
    • Documentation Status:
      Not Required


      Add ability to edit a bitstream's filename as well as description, format, etc. in XMLUI's EditBitstream form.

      This is a trivial change and helps keep parity with JSPUI. There are implications to renaming bitstreams – none severe, but worth considering.

      1. Bitstream links are usually displayed with the filename included.
      Since handle and sequence ID are what actually matches the request to the item+bitstream, this is not a problem. Old/cached/indexed links will still work.
      For this reason, editing bitstream filename in the EditBitstream form is actually safer than deleting and re-uploading the bitstream, which would generate a new sequence ID and cause old links to be unusable (a lot of repository managers use this as a workaround currently)

      2. Bitstreams derived from filter-media processes (eg. THUMBNAIL/image.jpg.jpg and TEXT/document.txt.txt) will, in practice, become orphaned, and on the next filter-media run, the derived bitstreams will be regenerated and added to the TEXT, THUMBNAIL. etc. bundles. This is potentially a problem, in terms of storage space, search term boosting, thumbnail duplication could affect display of item lists, and so on.

      It could be possible to programatically search for the derived bitstreams (eg. search for oldname.*.txt) and rename to fit the renaming of the ORIGINAL bitstream, but my opinion is that this is something that should be left up to repository managers/administrators, and that as long as we clearly document a recommended renaming procedure (we could even display a javascript warning alert or something, if necessary), the "human touch" will always be better than the interface trying to guess what other bitstreams to touch.

      Attaching patch that's tested internally at my institution, but will not commit until vote at dev meeting has been taken and others have had a chance to comment.




            kshepherd Kim Shepherd
            kshepherd Kim Shepherd
            Yin Yin Latt
            0 Vote for this issue
            0 Start watching this issue