Date parsing bug

Rintze · October 1, 2010

Saving http://onlinelibrary.wiley.com/doi/10.1002/bit.22856/abstract with the DOI translator in Zotero 2.0.8 fills the date field with "09/2010", which gets parsed into "2010-00-09" (y d). This should be "2010-09-00" (y m).

dstillman · October 2, 2010

Ticket created.

fbennett · October 2, 2010

In case it's of use, there is a date parser in the citeproc-js source that handles flexible human-readable input of ranges and some other things. It is accompanied by a human-readable test source file, a test grinder, and a copy of the ground-up tests (in JS for dojo DOH). The parser itself is contained in the file util_dateparser.js in the citeproc-js source archive. The tests can be run in the citeproc-js sources with the command:./test.py -p dateparse

ajlyon · October 2, 2010

While going to an in-house solution for date parsing has its drawbacks, moving to the same one as citeproc-js has some obvious pluses. Note also that we get date ranges, seasons, and fuzziness for free by switching to util_dateparser.js.

dstillman · April 13, 2011

Fixed for 2.1.6.

chritogjon · April 13, 2011

Thank you!