Hi Clive,
> Here is an item in our restored 1.5.2 production server:
>
> http://vle.bromley.ac.uk/dspace/handle/2045/22
>
> and here is the same item in our 1.6.2 test server:
>
> http://standbyvle.bromley.ac.uk/dspace/handle/2045/22
OK - so looks like the data is definitely fine in the database because when you
compare the 'full item view' in both, the date stamps are the same. So the DB
seems fine.
There were some large-ish changes made to a class called DCDate in the 1.5.2 ->
1.6 upgrade, and this may be causing the problem, however we've not had this
problem reported before (I think!) other than by yourself and Rajshekar.
What do you have in dpsace.cfg for:
webui.itemdisplay.default = dc.title, dc.title.alternative, dc.contributor.*, \
dc.subject, dc.date.issued(date), dc.publisher, \
dc.identifier.citation, dc.relation.ispartofseries,
\
dc.description.abstract, dc.description, \
dc.identifier.govdoc, dc.identifier.uri(link), \
dc.identifier.isbn, dc.identifier.issn, \
dc.identifier.ismn, dc.identifier
By default this section is commented out. I wonder what happens if you remove
the '(date)' from dc.date.issued, (and uncomment it if needed) and try
restarting tomcat. This may help us narrow down where the problem is, as it
will display the date as a raw string, rather than as a formatted date.
Thanks,
Stuart Lewis
IT Innovations Analyst and Developer
Te Tumu Herenga The University of Auckland Library
Auckland Mail Centre, Private Bag 92019, Auckland 1142, New Zealand
Ph: +64 (0)9 373 7599 x81928
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
