Zotero is a free, easy-to-use tool to help you collect, organize, cite, and share your research sources.
e73285ffc5
- Item.setField() stores dates in a multipart format beginning with an SQL date followed by the user's entry, so "November 3, 2006" becomes "2006-11-03 November 3, 2006" -- date field entries are parsed with Zotero.Date.strToDate() if not already in multipart format - Item.getField() returns just the user part unless passed the new second parameter, _unformatted_, which returns the field directly from DB without processing (e.g. the full multipart string) - Added SQLite triggers on the itemData table to enforce multipart format even if the table is modified outside the API - Migration step to update existing dates - Indicator next to date field to show what we've parsed and a tooltip over the date field to show the SQL date -- though I'm not sure how well the abbreviation part will localize (i.e. can you abbreviate 'month' in Chinese?) One obvious problem is how to handle date ranges when sorting or searching, which may end up rendering this whole method fairly useless (though I guess the multipart format could begin with two SQL dates instead of just one, at the cost of some storage space...). Other changes: - Utilities.lpad() handling for undefined value parameter - new Zotero.Date methods: strToMultipart(), isMultipart(), multipartToSQL(), multipartToStr(), isSQLDate(), sqlHasYear(), sqlHasMonth, sqlHasDay getLocaleDateOrder() (the last one unused for now) - try/catch around manual itemData INSERT execute() statements in Item.save() |
||
|---|---|---|
| chrome | ||
| components | ||
| defaults/preferences | ||
| chrome.manifest | ||
| install.rdf | ||
| license.txt | ||
| scrapers.sql | ||
| system.sql | ||
| update.rdf | ||
| userdata.sql | ||