__group__ ticket summary component milestone type created _description_ _changetime _reporter
mcburton 755 Support Endeca OPAC translators enhancement 2007-09-11T12:34:51-04:00 "Endeca is used by the Florida state system and NC state. There are significant discrepancies between FSU's and NCSU's catalogs, perhaps because of version or implementation differences. FSU, for example, just requires flipping a flag in the URL to display a MARC record (change V=D to V=M). NCSU requires the generation of a URL like
{{{
http://catalog.lib.ncsu.edu/web2/tramp2.exe/download_hitlist/A0r3evn1.001/NCSUCatResults.mrc?server=1home&format=MARC&server=1home&item=1&item_source=1home
}}}
where ""A0r3evn1.001"" is a randomly generated key that appears only once the item record is displayed. NCSU generates a MARC binary." 2009-01-15T21:14:36-05:00 stakats
dstillman 1638 map filingDate to date submitted in CSL styles 2.1 Final defect 2010-02-25T00:49:44-05:00 "Bruce [http://bitbucket.org/bdarcus/csl-schema/issue/19/filing-date-variable-for-patents added] a ""submitted"" date variable to CSL that needs be mapped to filingDate in csl.js
I started fixing this with r5788 but not sure what to do next, especially since I don't know the purpose of the temporary fix in r5649" 2010-02-25T00:52:37-05:00 erazlogo
jpontell 826 JSDoc support misc task 2007-11-09T20:36:33-05:00 Convert all comments to JSDoc 2 format and generate HTML docs. 2010-11-11T19:51:37-05:00 dstillman
simon 832 Handle title case/sentence case properly export enhancement 2007-11-16T09:26:08-05:00 "Some styles require title case (""Article Title Here""), while others require sentence case (""Article title here""). At the moment, a transform to title case is implemented (although it's not customizable). Unfortunately, sentence case is a much harder situation. Transforming titles like ""Glycogen: a Trojan horse for neurons"" and ""Characterization of the SKN7 ortholog of Aspergillus fumigatus"" from their title case equivalents will not be possible by algorithms alone.
Suppose we provide an icon to toggle between title/sentence case in the edit pane. Then, if the user modifies something beyond the capitalization in either form, we determine the minimum number of deletes and inserts to transform it (classic dynamic programming problem), and if this includes insertion of a new word, we capitalize it/put it in lower case as appropriate. This will require some modifications to the database schema, but is, as far as I can tell, the most intuitive all-encompassing solution.
Alternatively, we could leave the entry UI as is, and use BibTeX-style curly braces to specify that letters should be capitalized as they are. This is the easier solution, but is somewhat lacking in terms of usability." 2010-11-11T19:51:37-05:00 codec
simon 1673 don't iterate across XPCOM boundaries in integration plug-ins word integration enhancement 2010-06-21T04:01:39-04:00 Should be possible, and should speed things up a little bit (although not all that much, since the big overhead comes from the API calls), but will be a little painful to implement. 2010-06-21T04:01:57-04:00 simon
simon 1808 Build snapshots from DOM elements ingester enhancement 2011-04-02T12:37:04-04:00 "For many sites, there are a few well-defined blocks of content that are of interest. It would save network burden and simplify translator authoring to allow extracted DOM elements to be saved in a separately generated document. The attached patches against the trunk illustrate the approach. The files are:
Diff-enable-dom-object-save.patch
This provides a ""document:"" slot on the translator attachments object, which accepts a DOM document object.
Diff-dom-translator-utility.patch
This is a utility for use in translators, that does the heavy lifting of building a simple web page with DOM elements provided to the function as content.
Diff-mainichi-translator.patch
This is a sample translator that works against news articles at mainichi.jp (both the English and the Japanese sites).
This work follows on from earlier discussions that took place on zotero-dev:
http://groups.google.com/group/zotero-dev/browse_thread/thread/7d4ed9d1710ac897
If it is feasible, it would be very convenient to have this facility available in translators." 2011-07-28T16:17:32-04:00 fbennett
dstillman 1572 Better handling of N1 field in RIS export defect 2009-09-15T08:05:37-04:00 "Currently Zotero's RIS import ignores returns within notes. This is even true of notes created inside Zotero and exported and imported. I would guess we haven't touched this since we added HTML for rich text in notes?
Currently
N1 - Notes line 1.
Notes line 2.
Notes line 3.
Is imported as
Notes line 1. Notes line 2. Notes line 3.
For reference: http://forums.zotero.org/discussion/8673/" 2009-09-16T10:57:18-04:00 tjowens
simon 1432 "Add context-menu ""add item by identifier""" interface enhancement 2009-04-13T10:46:52-04:00 User should be able to highlight text and right-click to trigger lookup. 2011-02-14T02:55:25-05:00 stakats