During handle creation for an item, you're passing a collection where an item is expected.
It seems to me that during item creation it's checked whether that handle already exists and it's found to exist (this shouldn't happen!) and it is a collection. Run [dspace]/etc/postgres/update-sequences.sql to reset handle_seq to the value of the highest handle postfix you have. That should ensure that DSpace doesn't try to assign a handle that was already assigned once. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&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
