On Tue, Dec 18, 2012 at 7:39 PM, Chris King <[email protected]> wrote:
> The .gz is a valid gzipped file and if I uncompress it then everything works
> again.

Don't forget to run the checksum checker, especially after you restore
all the missing items.

> Do you have any idea why some files have ended up being compressed? Is there
> anything in DSpace that would have done that or is it probably something
> else?

I don't know, I've never heard of such problem. As far as I know,
nothing in DSpace uses the gzip compression for bitstreams. My first
suspect would be some of the export methods like the packager, but I
think it uses only zip. So my best guess is that at some point,
probably during some migration, this was caused by manual tinkering by
the repo admin - you or a colleague of yours (for the record, I don't
have anything against tinkering).


Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Reply via email to