Hi!
Here we had a soft launch of our IR for student submission last week. In
the Eperson table if there are empty records, the system gives an
"internal error" while accessing the eperson table from the admin
interface of DSpace 1.4.2. Is there a way to solve this issue since we
are using workflow for our submission approval process (2 stages) and
after the launch it so happened that this workflow members need to be
changed? We are using LDAP for staff (approval) and students
(submission). I have experienced that if we delete those empty records
(from DB) then accessing eperson from the interface would work fine. But
since our IR has already accepted submissions I would refrain from doing
so since working directly at DB is not an approach to be practicised.
Moreover after the soft launch around 500-600 students have logged in.
If anyone experienced this issue, please suggest the best approach to
follow at this stage?
Thanks, Jayan
.
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech