Menu
▾
▴
Re: [Treebase-devel] Understanding OAI-PMH Verbs
|
From: William P. <wil...@ya...> - 2011-05-16 19:02:12
|
Hi Rutger: I notice that all the examples given for date searches in CQL use ISO 8601 date styles: http://www.loc.gov/standards/sru/resources/cql-context-set-v1-2.html But both of these queries throw exceptions: http://treebase-dev.nescent.org/treebase-web/phylows/study/find?query=prism.creationDate>"2011-05-05" http://treebase-dev.nescent.org/treebase-web/phylows/study/find?query=prism.creationDate>2011-05-05 => java.text.ParseException: Unparseable date: "2011-05-05" at com.ibm.icu.text.DateFormat.parse(DateFormat.java:390) at... ... but conforming to ISO 8601 has various advantages, including the ability to include the time zone. Our OAI-PMH service seems to understand ISO 8601, e.g.: ?verb=ListRecords&metadataPrefix=oai_dc&from=2011-05-05T00:00:00Z Can the date parser for phylows be made more intelligent? bp On May 12, 2011, at 9:40 AM, Rutger Vos wrote: > http://treebase-dev.nescent.org/treebase-web/phylows/study/find?query=prism.creationDate>"May 5, 2011"&format=rss1 > > http://treebase-dev.nescent.org/treebase-web/phylows/study/find?query=prism.modificationDate>"May 5, 2011"&format=rss1 > > http://treebase-dev.nescent.org/treebase-web/phylows/study/find?query=prism.publicationDate>"May 5, 2011"&format=rss1 > > still ironing out the bugs with prism.publicationDate, but > prism.modificationDate seems to work. |
