Moving Bitstreams to other Items?

47 views
Skip to first unread message

Chris Clawson

unread,
Apr 21, 2022, 8:45:53 AM4/21/22
to DSpace Technical Support
We have many items in our database which include single images.  Many of these should  be combined into groups and described by a single entry.

The new image viewer and image metadata (description) makes it much better for users to view a single item, containing larger groups of images. The viewer now permits gallery views or 'slide show' presentation and the user doesn't need to jump around database items to view a related group of images.

How can I move previously assigned  bitstreams to these newly created items?

Tim Donohue

unread,
Apr 22, 2022, 3:57:17 PM4/22/22
to DSpace Technical Support
Hi Chris,

At this time, I'm not aware of a way to move Bitstreams between Items... other than at the database level.   

Hypothetically, you should be able to move a Bitstream by changing the "bundle2bitstream" table in the database, as that table decides which Bundle each Bitstream belongs to.  So, it may be possible to move them by moving them from one Item's "ORIGINAL" Bundle to another Item's "ORIGINAL" Bundle. (The "ORIGINAL" Bundle is just the default Bundle that DSpace uses to store bitstreams).   If you move Bitstreams in this way, you will *have* to do a full reindex of the site (otherwise your search results will likely show the old location).  I'd also recommend trying this out in a test/staging environment first, as I've never done this before... so, you want to make sure it works with no side effects.

Unfortunately, I do not believe this is possible from the REST API or UI at this time.  (If I'm wrong about that, I hope someone corrects me!)  The only way to achieve something similar from the UI would be to download the file from one Item and then upload it to a different Item, but that'd be a very manual process.

Tim

Chris Clawson

unread,
Apr 23, 2022, 6:34:26 PM4/23/22
to DSpace Technical Support
Thanks for the answer. For now, it may be just safer to export AIPs and Community/Collection metadata, and then develop methods to build working directories offline for later import. Such exports will provide all the images and records of anything needed for future items and also make it possible to create a new CSV of obsolete items to delete later.
Reply all
Reply to author
Forward
0 new messages