Hi, At the moment, I've an archive_directory of 51Gb occupying 89Gb of assetstore in DSpace.
The archive_directory is like the one shown in dspace-1.4.2-source/docs/application.html#itemimporter and is a copy of all packages successfully imported in 1.4.2 DSpace with 8.1 Postgresql. When the archive_directory grew from 50-51Gb, that 1Gb difference grew the DSpace assetstore by 4Gb, is that supposed to happen? or are failed import attempts (and retries) responsible for leaving clutter in the assetstore? or are package replacement operations (and many repeats) responsible for leaving earlier duplicate copies of bitstreams behind? I was expecting a successful 1Gb feed to DSpace would grow the assetstore by about 1Gb plus & minus a little bit. Any `clue' is much appreciated. -- Van Ly
------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
