Hi,
I am in the process of upgrading from DSpace 1.5.1 to 1.7.1. I am almost
done and am running index-init, but I’ve just noticed a problem. With previous
versions of DSpace, if a “bad” date was encountered in one of the date fields
(issue date, accession date, publication date), DSpace just ignored it. Now,
it seems it is unable to either display the Item page or the Browse screen if
encounters one of these records. Here’s an example:
One of our items has the following invalid issue and publication date that our
Users have never gotten around to correcting:
"Washington, D.C. :1955."
If I try to display the Item, the screen is blank and the following message
displays in the dspace.log file:
2011-08-18 12:07:14,232 WARN org.dspace.content.DCDate @ Mangled date:
Washington, D.C. :1955. ..failed all attempts to parse as date.
The same message displays if I try to browse by issue date.
I know the “right” thing to do is to clean up our data, but I also know we have
quite a few of these old bad dates and am wondering why DSpace is now having a
problem with it.
Thanks,
Sue
Sue Walker-Thornton
Software Developer/Database Administrator
NASA Langley Research Center|LITES Contract
SGT, Inc.|130 Research Drive
Hampton, Va. 23666
Office: (757) 224-4074
Mobile: (757) 506-9903
Fax: (757) 224-4001
[email protected]
------------------------------------------------------------------------------
Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
user administration capabilities and model configuration. Take
the hassle out of deploying and managing Subversion and the
tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
