I got DSpace 1.4 installed and running on my test server today. Cleaned up a problem with the front page (had to add DSpace-tag references to a couple of layout bits that hadn’t previously needed them; Eclipse was nobly trying to tell me I was b0rking things, but I didn’t realize what it was saying), thanked Ross Singer under my breath for reminding me to rehack display-item.jsp, then took a look at an item-display page and shrieked dismay.
All my metadata entries were doubled. Absolutely freakish.
I went over my code changes to ItemTag.java six ways from Sunday. Could not sort out where I’d managed to double the for loop. Replaced ItemTag.java with a fresh one straight from Sourceforge. No dice; metadata still doubled.
Hm, I said after the usual several hours of trying to figure out what the hell I could have done to the code. Let’s take a look at the database.
Sure enough, that was the source of the b0rkage. I had absentmindedly run the SQL upgrade script for DSpace 1.4 again, after running it the first time when the alpha came out last spring. I did not realize that was going to cause doubled metadata! Honestly, DSpace can’t move to AIPs fast enough for me.
Still, two lines of SQL fixed what my Daily Stupid did to the database, and now I can go on my merry way and b0rk lots of other stuff. This is why I have a test server, you know. I b0rk things.
