Bureaucrat, sudo, administrator
417
edits
Changes
m
* Brian Lowe, Cornell University, bjl23 at cornell dot edu
Protected "2011talks Submissions" [edit=autoconfirmed:move=autoconfirmed]
'''UPDATE:''' The submission deadline has passed and voting on the talks has commenced at http://vote.code4lib.org/election/index/17
----
Deadline for talk submission is ''Saturday, November 13''. See [http://www.mail-archive.com/code4lib@listserv.nd.edu/msg08878.html this mailing list post for more details], or the general [http://code4lib.org/conference/2011 Code4Lib 2011] page.
<pre>
== Talk Title: ==
== Mendeley's API and University Libraries: 3 examples to create value ==
* Jan Reichelt, Co-FounderIan Mulvany, Mendeley
Mendeley (http://www.mendeley.com) is a technology startup that is helping to revolutionize the way research is done. Used by more than 600,000 academics and industry researchers, Mendeley enables researchers to arrange collaborative projects, work and discuss in groups, as well as share data across its web platform. Launched in London in December 2008, Mendeley is already the world’s largest research collaboration platform. Through this platform, we anonymously pools users’ research paper collections, creating a crowd-sourced research database with a unique layer of social information - each research paper is connected with socio-demographic information about its audience.
* Brian Keese, Indiana University, bkeese at indiana dot edu
VIVO is an open-source semantic Web application that enables the discovery of research and scholarship across disciplines at an institution. Originally developed from 2003-2009 by Cornell University, in September 2009 the National Institute of Health's National Center for Research Resources made a grant to the University of Florida [http://vivo.ufl.edu], Cornell University [http://vivo.cornell.edu], Indiana University Bloomington [http://vivo.iu.edu], and four implementation partners to use VIVO to create a national network for scientists[http://www.vivoweb.org]. This network will allow researchers to discover potential collaborators with specific expertise, based on authoritative information on projects, grants, publications, affiliations, and research interests, essentially creating a social network for browsing, visualizing, and discovering scientists. This talk will give an overview of the technical underpinnings of VIVO, describe how it integrates with the larger semantic Web, sketch out the plans for enabling discovery across the national network of VIVO sites, and explore the role of libraries in implementing VIVO at all the partner sites. Additionally we will demonstrate some experiments in federated searching that have been undertaken by the VIVO network and the NIH funded Clinical and Translational Science Awards (CTSA) consortium network of networks.
This talk will show you how you can easily write these tests from your hidden goldmine of human vetted relevancy rankings.
== LibX 2.0 and the LibX Libapp Builder ==
* Godmar Back, Virginia Tech, godmar@gmail.com
* Brian Nicholson, Virginia Tech, brn@vt.edu
LibX is a platform for delivering library services that require a client-side presence, such as toolbars,
context menus, and content scripts. These services integrate library-related resources (links, results, tutorials)
into those web pages your users use when they don't go through the library's portals. While LibX 1.5 was mostly
used as a toolbar to represent a library's OPAC, LibX 2.0's focus is on simplifying the creation and distribution
of content scripts, which we call LibApps. The LibX Edition Builder allows librarians, even those who
prefer not to program, to independently create and distribute LibX editions for their user communities.
In a similar vein, the LibX LibApp Builder allows librarians to independently create and manage LibApps
for their user communities and share them with others. This talk will discuss the design and implementation
of the LibApp builder. We will also show how LibApps can be created to link the user's web experience to
modern discovery systems such as Summon in a smart and non-obtrusive way.
== Describing Digital Collections at the Free Library ==
* Daria Norris, Free Library of Philadelphia, norrisla at freelibrary dot org
The Free Library of Philadelphia has developed a Digital Collections content management system and search engine to describe the scholarly and historical items we are digitizing and making available on our web site. This application has evolved into a highly customizable way of setting up the metadata requirements of each individual collection while also conforming to the Dublin Core standard. The collections are diverse and include scans of medieval manuscripts, historical photographs of Philadelphia, Pennsylvania German fraktur, automobile reference photos and more. Development has also included the integration of authorities like the Getty Thesauri and the LOC's Thesaurus for Graphic Materials in a library that can also be used in other applications. I'll also discuss our future plans for the project.
== Lessons from the Hydra Community: cultivating a large, distributed, agile, open source developer network ==
* Matt Zumwalt, MediaShelf & Hydra Project, matt.zumwalt at yourmediashelf dot com
* Bess Sadler, Stanford University, Hydra Project & Project Blacklight, bess at stanford dot edu
When we set out to create the [http://wiki.duraspace.org/display/hydra/The+Hydra+Project Hydra framework] in 2009, we knew that building a strong developer community would be as important as releasing quality code. By August 2010 when we released the Beta version of [http://wiki.duraspace.org/display/hydra/Hydrangea Hydrangea] (the Hydra reference implementation) Ohloh already rated our committers as "one of the largest open-source teams in the world" and placed it "in the top 2% of all project teams on Ohloh." [see [http://www.ohloh.net/p/hydrangea/factoids/3944567 ohloh.com]] In the 3 months following that release, the number of active committers jumped even higher and the number of subsidiary projects quadrupled. This early success is the product of a concerted, collaborative effort that has incorporated input from many participants and advisors.
Over these first 18 months of work on Hydra, we have cobbled together a formidable list of principles and best practices for developers and for our whole community. Many of these best practices easily translate to any development effort. They are especially applicable to distributed open source teams using agile development methodologies.
Building and sustaining a community is an ongoing learning process. We have already learned a great amount -- most Hydra participants agree that working on this project has made us better at our jobs. We would like to share what we have learned thus far and get feedback about where to go from here.
== Opinionated Metadata (OM): Bringing a bit of sanity to the world of XML Metadata ==
* Matt Zumwalt, MediaShelf & Hydra Project, matt.zumwalt at yourmediashelf dot com
[http://rubygems.org/gems/om Opinionated Metadata] (OM) grew from discussions at Code4Lib 2010. It's now an integral component in the [http://wiki.duraspace.org/display/hydra/The+Hydra+Framework+and+its+Parts Hydra Framework]. Unlike most XML solutions, which start from schemas and build outwards, OM allows you to start from the natural vocabulary that emerges in user stories. Based on the terms that show up in those user stories, you can use OM to create a Terminology that maps each term to nodes in schema-driven XML. This Terminology then serves as a Domain Specific Language (DSL) for your code to rely on. Using that Terminology, you can:
* Generate absolute and relative xpath queries for each term
* Generate complex xpath queries for nested terms (ie. query a mods document for the "first name" of the second "person" entry OR query for all of the "person" entries whose "role" is "creator")
* Validate xml documents against a schema (if one is associated with the Terminology)
* Query an xml document for all values corresponding to a given term
* Update the values in an xml document corresponding to a given term
* Insert new nodes corresponding to a given term into an xml document
* Generate solr field names appropriate for indexing a term
OM borrows some characteristics from the XUpdate Language and is in part inspired by XForms. It is also strongly influenced by the agile, user-driven development methodologies of tools like Ruby on Rails. It puts the strengths of these technologies at your disposal in flexible, maintainable ways.
Internally, OM works as an extension to Nokogiri (a complete Ruby wrapper for the libxml2 and libxslt libraries). It gives you access to the full power of those underlying libraries, including a complete XPath implementation, while transparently handling the idiosyncrasies of those libraries and the XPath language for you.
While OM is just a library, it can be used in a web application to create, retrieve, update and delete XML documents. Within Hydra, we have implemented a full stack that uses OM to read XML documents, populate an HTML form, accept updates via a REST API, and update the XML accordingly.
