In an attempt lately to cull out offensive bitstreams in our DSpace 1.7.2 (OS : RHEL Server 5.7), we have:
- Used the CLI export tool to write item exports. - Added target bitstream_id(s) to each 'delete_contents' file in the export structure - Invoked updateitem -D (which successfully remove the bitstreams from the repository). This works swimmingly for most instances. If the last bitstream in a bundle is removed, however, the 'updateitem' tool does not appear to perform the additional step of removing the unreferenced bundle from the database. Deleting a similar 'final' item of a bundle through the admin interface does not appear to cause this problem. Has anyone else observed this behavior? Jake -- Jacob Sanford Developer, Electronic Text Center University of New Brunswick Libraries (Fredericton) [email protected] (506)447-3458 ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
