My top-three list for things I'd like to see in Exhibit 3.0: 1. Closer integration with Zotero or other bibliographic programs. Such attention would be key, given how the official press releases are targeting the academic and library community, who are increasingly using, and wishing to display, data housed in reference management software. Currently we rely upon Babel to convert data exported from Zotero, and Babel has problems. (See a summary of the issues at http://www.zotero.org/support/kb/exhibit ) Zotero is very active, and I'm sure they would be happy to collaborate with the Exhibit team on a protocol that eliminates intermediaries.
2. Clearer documentation. The introduction to Exhibit 2.0 was clear, engaging, and effective, but once I got past the introductory features it was nigh impossible to learn more advanced features. Many explanations were written by a programmer for other programmers. Other basic features were omitted or relegated to innuendo. I added to the wiki when I figured out new tricks, but I had to wonder why such conventions weren't there to begin with. I hope some of the grant money can be used to corral talent in writing and editing. 3. More complexity in searching and accessing child, parent, and sibling nodes. I voiced this wish earlier but I think it was unintelligible. My project involves two json sets that need to talk to each other. (The number of sets could grow, should the stars align.) The first set is a list of all extant writings of a 4th century theologian. The second is a bibliography of modern scholarship. On the page listing the ancient writings (the 1st json set), I wish the lens to list modern studies (the 2nd json set) that translate or reproduce each writing. You'll see the result of that effort here: http://www.kalvesmaki.com/7bx24/corpus.htm (a temporary location; the site will not be made public for some time) The problem here is that under "editions" and "modern translations" the entire title of the bibliography item is listed. These titles are overly long; I'd like to shorten them to merely an author-date convention (or give the user the option to choose what to display). So in accessing the object I want also to choose what child node should serve as the displayed access text for that object. Plus I'd like to give the user the option to alter the sequence of the objects (chronologically, alpha by author/editor, and availability). Thanks MIT team for taking this on. -- You received this message because you are subscribed to the Google Groups "SIMILE Widgets" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/simile-widgets?hl=en.
