On Thu, Mar 28, 2013 at 2:32 PM, Alain Tschanz <atsch...@njstatelib.org> wrote: > I finally figured out the problem. The owner of the versionhistory and > versionitem tables and versionhistory_seq and versionitem_seq sequences was > changed from dspace to postgres, effectively preventing us from adding any > new items to DSpace or from backing up the database.
Hi Alain, I'm glad you were able to figure out the problem. > Does anybody have any suggestions as to how to harden DSpace? Do you mean in terms of security? Here's an overview: https://wiki.duraspace.org/display/DSPACE/SecuringDspace If you need something more specific, please provide details. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d _______________________________________________ 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
