Hi everyone
I have undertaken some further investigations and it appears that the
contents of every date field in each item record has been corrupted
since the upgrade from DSpace 1.5.2 to 1.6.2
Below is an example of a corrupted record: (The T05:37:47Z mystifies me)
dc contributor author
Hello,
I have tried your upgrade steps, and faced same problem.
I editted the item and I found dc.dspace.issued in 2010-07-26T06:34:42Z,
I eddited date to 2010-07-26 and it works for me
Thanks.
--
Message: 1
Date: Fri,
Hi Clive / Rajshekhar,
I notice that with DSpace 1.5.2 on our server the strange codes were
already there before the database upgrade:
dc date accessioned 2009-04-29T05:57:26Z
dc date available 2009-04-29T05:57:26Z
dc date issued 2009-04-29T05:57:26Z
These dates are completely
Hi Stuart :)
I've already run the index-init script several times.
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
You can clearly
Hello Clive Stuart,
I got the same output that Clive is getting, but when I change the issued
date of the item, by editing it, and remove the time zone, full date is
shown in issued date column.
Thanks.
On Sat, Aug 7, 2010 at 2:25 PM, Clive Gould cli...@gmail.com wrote:
Hi Stuart :)
I've
Hi Stuart
The section you mentioned was commented out.
1) I stopped tomcat, removed the comments from the relevant sectio of
dspace.cfg, updated dspace, rebuilt the indexes and restarted tomcat.
Following these modifications on the test server 1.6.2 the dates are
still shown correctly under
Hi
Sorry I provided a restricted access item URL on the 1.6.2 test server :(
If you now sort by issue date you still get the truncated date:-
http://standbyvle.bromley.ac.uk/dspace/browse?type=dateissued
But if you view a complete individual item record you now get the full
unformatted date:-
We had a publicly accessible collection of .pdf files in dspace for some
time and then local policy changed, so
we applied ip authentication. Now we require password authentication or
proxy server logon to access the collection.
Google has entries for quick views and Google Scholar has view as
Hello Ludwig,
http://scholar.google.com/intl/en/scholar/publishers.html#tech5
See technical question 5.
Hope that helps.
Regards,
~~helix84
--
This SF.net email is sponsored by
Make an app they can't live without
Hi All
My solr stats are not updating.
I make use of the Jakarta connector.
See:
http://ir.sun.ac.za/wiki/index.php/Prepare_Ubuntu#Step_6._Setup_Apache2_Tomcat_5.5_Jakarta_Connector
This is in the DSpace log.
2010-08-07 13:39:41,914 ERROR org.dspace.statistics.SolrLogger @ Service
Hi Clive,
2) I then stopped tomcat, and modified the line you mentioned in
dspace.cfg as follows:
webui.itemdisplay.default = dc.title, dc.title.alternative, dc.contributor.*,
\
dc.subject, dc.date.issued, dc.publisher, \
Hi Stuart
Thanks for this detailed explanation.
I'm using the source for DSpace 1.6.2 because of the custom ldap
special groups code.
Maybe the fix missed out on reaching the 1.6.2 source distribution??
Best wishes
Clive
Sent from my iPhone
On 7 Aug 2010, at 20:35, Stuart Lewis
12 matches
Mail list logo
