On Fri, Aug 2, 2013 at 2:08 PM, Evans, Kevin <kevin.ev...@exeter.ac.uk> wrote: > at > org.dspace.app.bulkedit.MetadataExport.main(MetadataExport.java:260)
OK, that should help. Let's see: https://github.com/DSpace/DSpace/blob/dspace-1.8.2/dspace-api/src/main/java/org/dspace/app/bulkedit/MetadataExport.java#L260 So "csv" is null here. We got the csv from exporter.export() above, which is an instance of this class (exporter = new MetadataExport(c, (Community)dso, exportAll);), so this is the method which returns that null: https://github.com/DSpace/DSpace/blob/dspace-1.8.2/dspace-api/src/main/java/org/dspace/app/bulkedit/MetadataExport.java#L124 The obvious case here (barring any non-obvious cases) is that _any_ exception is caught and null returned. That is not nice, because it hides the cause of the problem from us. If you can, remove the whole catch statement and let that Exception be raised, so that we can see the error message. Of course, do this in a testing environment with a copy of the production database. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
