Re: [Dspace-tech] DSpace 1.6.2 issue date format

2010-08-08 Thread Clive Gould
Hi Stuart

The problem with the issue date truncation on DSpace 1.6.2 has been solved :)

Thanks for all your invaluable assistance in locating the source of the problem.

It appears that the patch http://jira.dspace.org/jira/browse/DS-469
had not been applied to DCDate.java in the 1.6.2 source code.

I applied the patch and rebuilt and updated DSpace and the issue date
on the test server is now being displayed correctly :-

http://standbyvle.bromley.ac.uk/dspace/browse?type=dateissued

I have updated my blog to include the relevant patch instructions :-

http://dspacebromley.blogspot.com/2010/08/dspace-162-upgrade-procedure.html

Any chance someone could update the source file on sourceforge?

Thanks again

Clive

--
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
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


Re: [Dspace-tech] DSpace 1.6.2 issue date format

2010-08-08 Thread Stuart Lewis
Hi Clive,

 The problem with the issue date truncation on DSpace 1.6.2 has been solved :)

Excellent - glad it works! :)

 It appears that the patch http://jira.dspace.org/jira/browse/DS-469
 had not been applied to DCDate.java in the 1.6.2 source code.

I've just worked out what's happened here by trawling though the subversion 
commit logs: The patch was applied to 'trunk' (which will become 1.7) but NOT 
to the 1_6_x branch which was used to make 1.6.1 and 1.6.2.

At least together we have worked this out :)  Therefore if it comes up again, 
we know how to fix it! If for some reason we do release a 1.6.3, then we can 
make sure it gets included.

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
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


Re: [Dspace-tech] DSpace 1.6.2 issue date format

2010-08-07 Thread Clive Gould
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 Human, Resources
dc date   accessioned 2009-04-29T05:37:47Z
dc date   available 2009-04-29T05:37:47Z
dc date   issued 2009-04-29T05:37:47Z
dc identifier   uri http://hdl.handle.net/2045/12
dc description   abstract Teaching staff are required to contact their
School Administrator to report sickness absence and Business Support
staff should contact their immediate Line Manager.
dc description   provenance Submitted by Clive Gould
(xx...@bromley.ac.uk) on 2009-04-29T05:37:47Z
No. of bitstreams: 1
sickness-absence_reporting.doc: 76800 bytes, checksum:
f1174340c8eb1dc64f63efa0c7c625d6 (MD5)
dc description   provenance Made available in DSpace on
2009-04-29T05:37:47Z (GMT). No. of bitstreams: 1
sickness-absence_reporting.doc: 76800 bytes, checksum:
f1174340c8eb1dc64f63efa0c7c625d6 (MD5)

It is possible to edit each item record individually and remove the
T05:37:47Z at which point DSpace dsiplays the date correctly.

Any suggestions what might be causing this?

Could it be that the SQL script has corruputed the database, or is
there something in how DSpace is displaying dates held by postgresql?

Thanks very much

Clive


On Fri, Aug 6, 2010 at 9:40 AM, Clive Gould cli...@gmail.com wrote:
 Hi everyone

 I have just upgraded our production server to DSpace 1.6.2 and the
 issue date field is now truncated to display only the year:

 http://vle.bromley.ac.uk/dspace/browse?type=dateissued

 Is this normal with DSpace 1.6.2 ???

 I have blogged the upgrade procedure I followed here:

 http://dspacebromley.blogspot.com/

 Has anyone else who has successfully upgraded got the full issue date
 displayed??

 Thanks

 Clive


--
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
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


Re: [Dspace-tech] DSpace 1.6.2 issue date format

2010-08-07 Thread Rajshekhar Pandey
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, 6 Aug 2010 09:40:41 +0100
 From: Clive Gould cli...@gmail.com
 Subject: Re: [Dspace-tech] DSpace 1.6.2 issue date format
 To: TAYLOR Robin robin.tay...@ed.ac.uk
 Cc: dspace-tech@lists.sourceforge.net
 Message-ID:

 aanlktimu57qjyg2jeuufa+qi_ucw0cz5_rcej-g2w...@mail.gmail.comaanlktimu57qjyg2jeuufa%2bqi_ucw0cz5_rcej-g2w...@mail.gmail.com
 
 Content-Type: text/plain; charset=ISO-8859-1

 Hi everyone

 I have just upgraded our production server to DSpace 1.6.2 and the
 issue date field is now truncated to display only the year:

 http://vle.bromley.ac.uk/dspace/browse?type=dateissued

 Is this normal with DSpace 1.6.2 ???

 I have blogged the upgrade procedure I followed here:

 http://dspacebromley.blogspot.com/

 Has anyone else who has successfully upgraded got the full issue date
 displayed??

 Thanks

 Clive

 On Thu, Aug 5, 2010 at 6:59 AM, Clive Gould cli...@gmail.com wrote:
  Hi Robin
 
  Appended are the appropriate sections from dspace.cfg.
 
  Note that these sections are derived unchanged from the default
  configuration files that came with DSpace 1.5.2 and 1.6.2
  respectively.
 
  Any suggestions most welcome.
 
  Thanks :)
 
  Clive
 
 
  ## Browse Configuration 1.5.2 ##
  # Issue Date is displayed in full
 
  webui.browse.index.1 = dateissued:item:dateissued
  webui.browse.index.2 = author:metadata:dc.contributor.*:text
  webui.browse.index.3 = title:item:title
  webui.browse.index.4 = subject:metadata:dc.subject.*:text
 
  webui.itemlist.sort-option.1 = title:dc.title:title
  webui.itemlist.sort-option.2 = dateissued:dc.date.issued:date
  webui.itemlist.sort-option.3 = dateaccessioned:dc.date.accessioned:date
 
  plugin.named.org.dspace.sort.OrderFormatDelegate= \
  ? ? ? ?org.dspace.sort.OrderFormatTitleMarc21=title
 
  webui.browse.link.1 = author:dc.contributor.*
 
 
   Additional configuration for Recent Submissions code 
 
  recent.submissions.sort-option = dateaccessioned
 
  recent.submissions.count = 5
 
  plugin.sequence.org.dspace.plugin.CommunityHomeProcessor = \
  ? ? ? ?org.dspace.app.webui.components.RecentCommunitySubmissions
 
  plugin.sequence.org.dspace.plugin.CollectionHomeProcessor = \
  ? ? ? ?org.dspace.app.webui.components.RecentCollectionSubmissions
 
 
 
  ## Browse Configuration 1.6.2 ##
  # Issue date is truncated to just the year
 
  webui.browse.index.1 = dateissued:item:dateissued
  webui.browse.index.2 = author:metadata:dc.contributor.*,dc.creator:text
  webui.browse.index.3 = title:item:title
  webui.browse.index.4 = subject:metadata:dc.subject.*:text
 
  webui.itemlist.sort-option.1 = title:dc.title:title
  webui.itemlist.sort-option.2 = dateissued:dc.date.issued:date
  webui.itemlist.sort-option.3 = dateaccessioned:dc.date.accessioned:date
 
  plugin.named.org.dspace.sort.OrderFormatDelegate= \
  ? ? ? ?org.dspace.sort.OrderFormatTitleMarc21=title
 
  webui.browse.link.1 = author:dc.contributor.*
 
   Additional configuration for Recent Submissions code 
 
  recent.submissions.sort-option = dateaccessioned
 
  recent.submissions.count = 5
 
  plugin.sequence.org.dspace.plugin.CommunityHomeProcessor = \
  ? ? ? ?org.dspace.app.webui.components.RecentCommunitySubmissions
 
  plugin.sequence.org.dspace.plugin.CollectionHomeProcessor = \
  ? ? ? ?org.dspace.app.webui.components.RecentCollectionSubmissions
 
  plugin.named.org.dspace.content.license.LicenseArgumentFormatter = \
  ? ? ? ?org.dspace.content.license.SimpleDSpaceObjectLicenseFormatter
  = collection, \
  ? ? ? ?org.dspace.content.license.SimpleDSpaceObjectLicenseFormatter =
 item, \
  ? ? ? ?org.dspace.content.license.SimpleDSpaceObjectLicenseFormatter =
 eperson
 
 
 
  On Wed, Aug 4, 2010 at 1:51 PM, TAYLOR Robin robin.tay...@ed.ac.uk
 wrote:
  Hi Clive,
 
  Could you post to the list the contents of the ## Browse
 Configuration ## section from dspace.cfg ?
 
  Thanks.
 
  Robin Taylor
  Main Library
  University of Edinburgh
  Tel. 0131 6513808
 
  -Original Message-
  From: Clive Gould [mailto:cli...@gmail.com]
  Sent: 04 August 2010 12:54
  To: dspace-tech@lists.sourceforge.net
  Subject: Re: [Dspace-tech] DSpace 1.6.2 issue date format
 
  Hi Robin
 
  1.5.2 production repository:-
 
  http://vle.bromley.ac.uk/dspace/browse?type=dateissued
 
  1.6.2 test repository:-
 
  http://standbyvle.bromley.ac.uk/dspace/browse?type=dateissued
 
  Thanks :)
 
  Clive
 
 
  On Wed, Aug 4, 2010 at 10:27 AM, TAYLOR Robin
  robin.tay...@ed.ac.uk wrote:
   Hi Clive,
  
   Do you have a url for the item so I could have a look at it ?
  
   Thanks, Robin.
  
  
   Robin Taylor
   Main Library
   University of Edinburgh
   Tel. 0131 6513808
  
   -Original

Re: [Dspace-tech] DSpace 1.6.2 issue date format

2010-08-07 Thread Stuart Lewis
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 normal. See: 
http://en.wikipedia.org/wiki/ISO_8601#UTC

Basically it is a way of describing date / time fields in a timezone neutral 
way.

year-month-day T (to denote the start of the Time part) hour:minute:second Z 
(zulu time)

Therefore the contents of your database appear to be fine. When you view an 
item, are the dates correct in there - is it just the browse screens that 
appear wrong?

Since upgrading, have you re-indexed your browse tables? Step 10 of the upgrade 
instructions (http://www.dspace.org/1_6_2Documentation/ch04.html#N10FE6) says 
to run:

 - [dspace]/bin/dspace index-init

You could look in your browse index tables bi_* and see what values they are 
holding. Are they holding the expected dates in the format you would expect?

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
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


Re: [Dspace-tech] DSpace 1.6.2 issue date format

2010-08-07 Thread Clive Gould
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 see the difference in the issue date display format.

Do you know off hand the postgres commands l need to use to view the
tables or is it better I reinstall phpPgAdmin?

Thanks very much

Clive





On Sat, Aug 7, 2010 at 9:32 AM, Stuart Lewis s.le...@auckland.ac.nz wrote:
 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 normal. See: 
 http://en.wikipedia.org/wiki/ISO_8601#UTC

 Basically it is a way of describing date / time fields in a timezone neutral 
 way.

 year-month-day T (to denote the start of the Time part) hour:minute:second Z 
 (zulu time)

 Therefore the contents of your database appear to be fine. When you view an 
 item, are the dates correct in there - is it just the browse screens that 
 appear wrong?

 Since upgrading, have you re-indexed your browse tables? Step 10 of the 
 upgrade instructions 
 (http://www.dspace.org/1_6_2Documentation/ch04.html#N10FE6) says to run:

  - [dspace]/bin/dspace index-init

 You could look in your browse index tables bi_* and see what values they are 
 holding. Are they holding the expected dates in the format you would expect?

 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
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


Re: [Dspace-tech] DSpace 1.6.2 issue date format

2010-08-07 Thread Rajshekhar Pandey
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 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 see the difference in the issue date display format.

 Do you know off hand the postgres commands l need to use to view the
 tables or is it better I reinstall phpPgAdmin?

 Thanks very much

 Clive





 On Sat, Aug 7, 2010 at 9:32 AM, Stuart Lewis s.le...@auckland.ac.nz
 wrote:
  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 normal. See:
 http://en.wikipedia.org/wiki/ISO_8601#UTC
 
  Basically it is a way of describing date / time fields in a timezone
 neutral way.
 
  year-month-day T (to denote the start of the Time part)
 hour:minute:second Z (zulu time)
 
  Therefore the contents of your database appear to be fine. When you view
 an item, are the dates correct in there - is it just the browse screens that
 appear wrong?
 
  Since upgrading, have you re-indexed your browse tables? Step 10 of the
 upgrade instructions (
 http://www.dspace.org/1_6_2Documentation/ch04.html#N10FE6) says to run:
 
   - [dspace]/bin/dspace index-init
 
  You could look in your browse index tables bi_* and see what values they
 are holding. Are they holding the expected dates in the format you would
 expect?
 
  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
 
 




-- 
Regards,
Rajshekhar Pandey
Software Programmer
Webinito Networks.
--
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
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


Re: [Dspace-tech] DSpace 1.6.2 issue date format

2010-08-07 Thread Clive Gould
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 Edit item, but as before truncated
everywhere else under issue date.

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, \
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

I then updated dspace, rebuilt the indexes and restarted tomcat.

The full, unabridged issue date is now shown as you can see below:

http://standbyvle.bromley.ac.uk/dspace/handle/2045/16

So what is it about (date) ???

Thanks ;)

Clive


On Sat, Aug 7, 2010 at 10:11 AM, Stuart Lewis s.le...@auckland.ac.nz wrote:
 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
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


Re: [Dspace-tech] DSpace 1.6.2 issue date format

2010-08-07 Thread Clive Gould
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:-

http://standbyvle.bromley.ac.uk/dspace/handle/2045/22

Thanks

Clive


On Sat, Aug 7, 2010 at 11:01 AM, Clive Gould cli...@gmail.com wrote:
 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 Edit item, but as before truncated
 everywhere else under issue date.

 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, \
                            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

 I then updated dspace, rebuilt the indexes and restarted tomcat.

 The full, unabridged issue date is now shown as you can see below:

 http://standbyvle.bromley.ac.uk/dspace/handle/2045/16

 So what is it about (date) ???

 Thanks ;)

 Clive


--
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
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


Re: [Dspace-tech] DSpace 1.6.2 issue date format

2010-08-07 Thread Stuart Lewis
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, \
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
 
 The full, unabridged issue date is now shown as you can see below:
 
 So what is it about (date) ???

Adding (date) to a field in that list tells DSpace that you want to display the 
date as a data, rather than as the raw string that it retrieves from the 
database in the 'simple item view'. Typically this will involve stripping off 
the time, and, depending on the original date you entered, displaying just the 
year, month and year, or day month and year. So the suggestion to remove it was 
to check that it was getting the correct data - not as a fix to the other 
problems. We need to work out why the date isn't being 

The class that does this is DCDate.java, and we know this class has a few 
issues and limitations in the way it does this, and we have some open issues in 
our JIRA bug tracking system to look at this and address it.

I've had a quick look around our JIRA system, and there are some other reports 
of the same problem, for example this one:

 - http://jira.dspace.org/jira/browse/DS-469

However this suggests it was fixed in 1.6.1. Are you using the source or binary 
distribution of DSpace 1.6.2?

I'll try and find some time to big into this a bit further.

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
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


Re: [Dspace-tech] DSpace 1.6.2 issue date format

2010-08-07 Thread Clive
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 s.le...@auckland.ac.nz wrote:

 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, \
   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

 The full, unabridged issue date is now shown as you can see below:

 So what is it about (date) ???

 Adding (date) to a field in that list tells DSpace that you want to  
 display the date as a data, rather than as the raw string that it  
 retrieves from the database in the 'simple item view'. Typically  
 this will involve stripping off the time, and, depending on the  
 original date you entered, displaying just the year, month and year,  
 or day month and year. So the suggestion to remove it was to check  
 that it was getting the correct data - not as a fix to the other  
 problems. We need to work out why the date isn't being

 The class that does this is DCDate.java, and we know this class has  
 a few issues and limitations in the way it does this, and we have  
 some open issues in our JIRA bug tracking system to look at this and  
 address it.

 I've had a quick look around our JIRA system, and there are some  
 other reports of the same problem, for example this one:

 - http://jira.dspace.org/jira/browse/DS-469

 However this suggests it was fixed in 1.6.1. Are you using the  
 source or binary distribution of DSpace 1.6.2?

 I'll try and find some time to big into this a bit further.

 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
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


Re: [Dspace-tech] DSpace 1.6.2 issue date format

2010-08-05 Thread Clive Gould
Hi Robin

Appended are the appropriate sections from dspace.cfg.

Note that these sections are derived unchanged from the default
configuration files that came with DSpace 1.5.2 and 1.6.2
respectively.

Any suggestions most welcome.

Thanks :)

Clive


## Browse Configuration 1.5.2 ##
# Issue Date is displayed in full

webui.browse.index.1 = dateissued:item:dateissued
webui.browse.index.2 = author:metadata:dc.contributor.*:text
webui.browse.index.3 = title:item:title
webui.browse.index.4 = subject:metadata:dc.subject.*:text

webui.itemlist.sort-option.1 = title:dc.title:title
webui.itemlist.sort-option.2 = dateissued:dc.date.issued:date
webui.itemlist.sort-option.3 = dateaccessioned:dc.date.accessioned:date

plugin.named.org.dspace.sort.OrderFormatDelegate= \
org.dspace.sort.OrderFormatTitleMarc21=title

webui.browse.link.1 = author:dc.contributor.*


 Additional configuration for Recent Submissions code 

recent.submissions.sort-option = dateaccessioned

recent.submissions.count = 5

plugin.sequence.org.dspace.plugin.CommunityHomeProcessor = \
org.dspace.app.webui.components.RecentCommunitySubmissions

plugin.sequence.org.dspace.plugin.CollectionHomeProcessor = \
org.dspace.app.webui.components.RecentCollectionSubmissions



## Browse Configuration 1.6.2 ##
# Issue date is truncated to just the year

webui.browse.index.1 = dateissued:item:dateissued
webui.browse.index.2 = author:metadata:dc.contributor.*,dc.creator:text
webui.browse.index.3 = title:item:title
webui.browse.index.4 = subject:metadata:dc.subject.*:text

webui.itemlist.sort-option.1 = title:dc.title:title
webui.itemlist.sort-option.2 = dateissued:dc.date.issued:date
webui.itemlist.sort-option.3 = dateaccessioned:dc.date.accessioned:date

plugin.named.org.dspace.sort.OrderFormatDelegate= \
org.dspace.sort.OrderFormatTitleMarc21=title

webui.browse.link.1 = author:dc.contributor.*

 Additional configuration for Recent Submissions code 

recent.submissions.sort-option = dateaccessioned

recent.submissions.count = 5

plugin.sequence.org.dspace.plugin.CommunityHomeProcessor = \
org.dspace.app.webui.components.RecentCommunitySubmissions

plugin.sequence.org.dspace.plugin.CollectionHomeProcessor = \
org.dspace.app.webui.components.RecentCollectionSubmissions

plugin.named.org.dspace.content.license.LicenseArgumentFormatter = \
org.dspace.content.license.SimpleDSpaceObjectLicenseFormatter
= collection, \
org.dspace.content.license.SimpleDSpaceObjectLicenseFormatter = item, \
org.dspace.content.license.SimpleDSpaceObjectLicenseFormatter = eperson



On Wed, Aug 4, 2010 at 1:51 PM, TAYLOR Robin robin.tay...@ed.ac.uk wrote:
 Hi Clive,

 Could you post to the list the contents of the ## Browse Configuration 
 ## section from dspace.cfg ?

 Thanks.

 Robin Taylor
 Main Library
 University of Edinburgh
 Tel. 0131 6513808

 -Original Message-
 From: Clive Gould [mailto:cli...@gmail.com]
 Sent: 04 August 2010 12:54
 To: dspace-tech@lists.sourceforge.net
 Subject: Re: [Dspace-tech] DSpace 1.6.2 issue date format

 Hi Robin

 1.5.2 production repository:-

 http://vle.bromley.ac.uk/dspace/browse?type=dateissued

 1.6.2 test repository:-

 http://standbyvle.bromley.ac.uk/dspace/browse?type=dateissued

 Thanks :)

 Clive


 On Wed, Aug 4, 2010 at 10:27 AM, TAYLOR Robin
 robin.tay...@ed.ac.uk wrote:
  Hi Clive,
 
  Do you have a url for the item so I could have a look at it ?
 
  Thanks, Robin.
 
 
  Robin Taylor
  Main Library
  University of Edinburgh
  Tel. 0131 6513808
 
  -Original Message-
  From: Clive Gould [mailto:cli...@gmail.com]
  Sent: 04 August 2010 08:01
  To: dspace-tech@lists.sourceforge.net
  Subject: [Dspace-tech] DSpace 1.6.2 issue date format
 
  Hi everyone
 
  Just wondering why the date display format appears to have changed
  with DSpace 1.6.2 when browsing by issue date and title?
 
  With DSpace 1.5.2 the issue date appears in the format:
 
   29-Apr-2009
 
  With DSpace 1.6.2 the same items issue date appears in the format:
 
  2009
 
  Any ideas what I have done wrong in the configuration settings?
 
  Thanks
 
  Clive
 
  --
  
  The Palm PDK Hot Apps Program offers developers who use
 the Plug-In
  Development Kit to bring their C/C++ apps to Palm for a
 share of $1
  Million in cash or HP Products. Visit us here for more details:
  http://p.sf.net/sfu/dev2dev-palm
  ___
  DSpace-tech mailing list
  DSpace-tech@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/dspace-tech
 
  --
  The University of Edinburgh is a charitable body, registered in
  Scotland, with registration number SC005336.
 
 

 --
 
 The Palm PDK Hot Apps Program offers developers who use the
 Plug-In Development Kit to bring

[Dspace-tech] DSpace 1.6.2 issue date format

2010-08-04 Thread Clive Gould
Hi everyone

Just wondering why the date display format appears to have changed
with DSpace 1.6.2 when browsing by issue date and title?

With DSpace 1.5.2 the issue date appears in the format:

 29-Apr-2009

With DSpace 1.6.2 the same items issue date appears in the format:

2009

Any ideas what I have done wrong in the configuration settings?

Thanks

Clive

--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


Re: [Dspace-tech] DSpace 1.6.2 issue date format

2010-08-04 Thread TAYLOR Robin
Hi Clive,

Do you have a url for the item so I could have a look at it ?

Thanks, Robin.


Robin Taylor
Main Library
University of Edinburgh
Tel. 0131 6513808  

 -Original Message-
 From: Clive Gould [mailto:cli...@gmail.com] 
 Sent: 04 August 2010 08:01
 To: dspace-tech@lists.sourceforge.net
 Subject: [Dspace-tech] DSpace 1.6.2 issue date format
 
 Hi everyone
 
 Just wondering why the date display format appears to have 
 changed with DSpace 1.6.2 when browsing by issue date and title?
 
 With DSpace 1.5.2 the issue date appears in the format:
 
  29-Apr-2009
 
 With DSpace 1.6.2 the same items issue date appears in the format:
 
 2009
 
 Any ideas what I have done wrong in the configuration settings?
 
 Thanks
 
 Clive
 
 --
 
 The Palm PDK Hot Apps Program offers developers who use the 
 Plug-In Development Kit to bring their C/C++ apps to Palm for 
 a share of $1 Million in cash or HP Products. Visit us here 
 for more details:
 http://p.sf.net/sfu/dev2dev-palm
 ___
 DSpace-tech mailing list
 DSpace-tech@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-tech
 
-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.


--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


Re: [Dspace-tech] DSpace 1.6.2 issue date format

2010-08-04 Thread Clive Gould
Hi Robin

1.5.2 production repository:-

http://vle.bromley.ac.uk/dspace/browse?type=dateissued

1.6.2 test repository:-

http://standbyvle.bromley.ac.uk/dspace/browse?type=dateissued

Thanks :)

Clive


On Wed, Aug 4, 2010 at 10:27 AM, TAYLOR Robin robin.tay...@ed.ac.uk wrote:
 Hi Clive,

 Do you have a url for the item so I could have a look at it ?

 Thanks, Robin.


 Robin Taylor
 Main Library
 University of Edinburgh
 Tel. 0131 6513808

 -Original Message-
 From: Clive Gould [mailto:cli...@gmail.com]
 Sent: 04 August 2010 08:01
 To: dspace-tech@lists.sourceforge.net
 Subject: [Dspace-tech] DSpace 1.6.2 issue date format

 Hi everyone

 Just wondering why the date display format appears to have
 changed with DSpace 1.6.2 when browsing by issue date and title?

 With DSpace 1.5.2 the issue date appears in the format:

  29-Apr-2009

 With DSpace 1.6.2 the same items issue date appears in the format:

 2009

 Any ideas what I have done wrong in the configuration settings?

 Thanks

 Clive

 --
 
 The Palm PDK Hot Apps Program offers developers who use the
 Plug-In Development Kit to bring their C/C++ apps to Palm for
 a share of $1 Million in cash or HP Products. Visit us here
 for more details:
 http://p.sf.net/sfu/dev2dev-palm
 ___
 DSpace-tech mailing list
 DSpace-tech@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-tech

 --
 The University of Edinburgh is a charitable body, registered in
 Scotland, with registration number SC005336.



--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


Re: [Dspace-tech] DSpace 1.6.2 issue date format

2010-08-04 Thread TAYLOR Robin
Hi Clive,

Could you post to the list the contents of the ## Browse Configuration 
## section from dspace.cfg ?

Thanks.

Robin Taylor
Main Library
University of Edinburgh
Tel. 0131 6513808  

 -Original Message-
 From: Clive Gould [mailto:cli...@gmail.com] 
 Sent: 04 August 2010 12:54
 To: dspace-tech@lists.sourceforge.net
 Subject: Re: [Dspace-tech] DSpace 1.6.2 issue date format
 
 Hi Robin
 
 1.5.2 production repository:-
 
 http://vle.bromley.ac.uk/dspace/browse?type=dateissued
 
 1.6.2 test repository:-
 
 http://standbyvle.bromley.ac.uk/dspace/browse?type=dateissued
 
 Thanks :)
 
 Clive
 
 
 On Wed, Aug 4, 2010 at 10:27 AM, TAYLOR Robin 
 robin.tay...@ed.ac.uk wrote:
  Hi Clive,
 
  Do you have a url for the item so I could have a look at it ?
 
  Thanks, Robin.
 
 
  Robin Taylor
  Main Library
  University of Edinburgh
  Tel. 0131 6513808
 
  -Original Message-
  From: Clive Gould [mailto:cli...@gmail.com]
  Sent: 04 August 2010 08:01
  To: dspace-tech@lists.sourceforge.net
  Subject: [Dspace-tech] DSpace 1.6.2 issue date format
 
  Hi everyone
 
  Just wondering why the date display format appears to have changed 
  with DSpace 1.6.2 when browsing by issue date and title?
 
  With DSpace 1.5.2 the issue date appears in the format:
 
   29-Apr-2009
 
  With DSpace 1.6.2 the same items issue date appears in the format:
 
  2009
 
  Any ideas what I have done wrong in the configuration settings?
 
  Thanks
 
  Clive
 
  --
  
  The Palm PDK Hot Apps Program offers developers who use 
 the Plug-In 
  Development Kit to bring their C/C++ apps to Palm for a 
 share of $1 
  Million in cash or HP Products. Visit us here for more details:
  http://p.sf.net/sfu/dev2dev-palm
  ___
  DSpace-tech mailing list
  DSpace-tech@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/dspace-tech
 
  --
  The University of Edinburgh is a charitable body, registered in 
  Scotland, with registration number SC005336.
 
 
 
 --
 
 The Palm PDK Hot Apps Program offers developers who use the 
 Plug-In Development Kit to bring their C/C++ apps to Palm for 
 a share of $1 Million in cash or HP Products. Visit us here 
 for more details:
 http://p.sf.net/sfu/dev2dev-palm
 ___
 DSpace-tech mailing list
 DSpace-tech@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-tech
 
-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.


--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech