Hi helix84
I found that it was the bitstream.size_bytes field that prevented the
download from opening correctly. I changed my script to update the
database with the correct filesize as well as the md5sum, and it work
perfectly. Thanks for your help.
Kind Regards.
Shaun Donovan
On 11/01/201
On Thu, Nov 1, 2012 at 6:12 PM, Shaun Donovan wrote:
> I actually did look at ItemUpdate. This still requires that you delete one
> bitstream and add another. The delete option requires a bitstream ID, which
> I have no way of knowing by iterating the filesystem.
>
> Unless the internal_id in the
Thanks for the (very) fast response helix84.
I actually did look at ItemUpdate. This still requires that you delete
one bitstream and add another. The delete option requires a bitstream
ID, which I have no way of knowing by iterating the filesystem.
Unless the internal_id in the bitstream table
You don't have to make it so complicated, DSpace data structures are
very sane as opposed to some other systems. After you replaced the
files in the assetstore, calculate a new MD5 checksum for them and
store it to the bitstream table. Notice that bitstream file name in
asset store is not equal to
Hi all.
I am trying to replace PDF files that are currently in the system with
newer versions of those same PDF's. In essence, I have written a perl
script to iterate through the assetstore, and look for PDF files. When I
find one, I check to see if it is password protected (I have been asked
5 matches
Mail list logo
