{5} Assigned, Active Tickets by Owner (Full Description) (14 matches)

List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.

fcheslack (No matches found.)

Ticket Summary Component Milestone Type Created
Description

jpontell (1 match)

Ticket Summary Component Milestone Type Created
Description
#826 JSDoc support misc task 11/09/07

Convert all comments to JSDoc 2 format and generate HTML docs.

dstillman (No matches found.)

Ticket Summary Component Milestone Type Created
Description

fcheslack (No matches found.)

Ticket Summary Component Milestone Type Created
Description

mcburton (1 match)

Ticket Summary Component Milestone Type Created
Description
#755 Support Endeca OPAC translators enhancement 09/11/07

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.

simon (4 matches)

Ticket Summary Component Milestone Type Created
Description
#832 Handle title case/sentence case properly export enhancement 11/16/07

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.

#1432 Add context-menu "add item by identifier" interface enhancement 04/13/09

User should be able to highlight text and right-click to trigger lookup.

#1673 don't iterate across XPCOM boundaries in integration plug-ins word integration enhancement 06/21/10

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.

#1808 Build snapshots from DOM elements ingester enhancement 04/02/11

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.

dstillman (2 matches)

Ticket Summary Component Milestone Type Created
Description
#1572 Better handling of N1 field in RIS export defect 09/15/09

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 - <p>Notes line 1.</p> <p>Notes line 2.</p> <p>Notes line 3.</p>

Is imported as <p>Notes line 1. Notes line 2. Notes line 3.</p>

For reference: ​http://forums.zotero.org/discussion/8673/

#1638 map filingDate to date submitted in CSL styles 2.1 Final defect 02/25/10

Bruce ​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

fcheslack (No matches found.)

Ticket Summary Component Milestone Type Created
Description
Note: See TracReports for help on using and creating reports.