On Thu, Nov 1, 2012 at 6:12 PM, Shaun Donovan <sha...@teqcle.co.za> 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 bitstream table is unique and corresponds to > the filename as stored in assetstore, which it now looks likely to me. > > If that is true, then I should be able to use ItemUpdate by using the > filename that I am busy with to do a lookup of the bistream_id in the > bitstream table.
Yes, exactly. > The question then becomes, am I correct in assuming that the > bitstream.internal_id field is the actual filename? Sounds good. I never tried it, though. > If I am to use your other suggestion and calculate my own MD5 checksum and > insert it into the database, I will then also need to update the > bitstream.size_bytes field. Yes, I forgot about that one. > Both of these methods sound likely to work, but I think that the ItemUpdate > is safer. I will test both and let you know. I forgot to include the usual disclaimer and warning - backup your assetstore and database dump before you make any manual changes, update indexes and run checks after you do the changes. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
