Jump to: navigation, search

2014 Prepared Talk Proposals

3,264 bytes added, 21:25, 8 November 2013
no edit summary
This architecture allows us to swap in the technology that best fits each part of the process, and it makes it easier to maintain the system. We use this to integrate and coordinate between tasks handled in Java, Ruby, and Go, and it provides an effective way to interoperate with these programming languages and the respective strengths that they bring to this system.
== Sustaining your Open Source project through training ==
* Bess Sadler (Stanford University Libraries) and Mark Bussey (Data Curation Experts) will discuss their experiences developing and delivering training for Project Hydra.
Topics covered:
* Working practices for developing training materials
* Sharing the work when there are no dedicated resources
* Inviting community (and student) input to create higher quality content
* Strategies to keep training docs up-to date
* Strategies to make training materials available to the widest-possible audience
* Using surveys (Survey Monkey) to assess the effectiveness of your training program
==Piwik: Open source web analytics==
While Google Analytics is synonymous with Web Analytics, fortunately today we have many other good options, and one option is Piwik, [|] a simple to install, open-source PHP/MySQL application with a tracking script that will sit alongside Google Analytics tracking the usual clicks, events and variables. In this presentation, I'd like to cover the usual analytics topics and also cover what makes Piwik powerful, such as importing and visualizing web logs from any system to incorporate both past and future data, easily tracking downloads, and the ability to write your own reports or dashboard. The visitor log data is stored securely on your own server so you have control over who looks at the data and how much or how little to keep. With an active and helpful developer community, Piwik has the potential for analytics which makes sense for libraries, not e-commerce.
== Next Generation Catalogue - RDF as a Basis for New Services ==
* How this has (or could) impact presentation of recommended items in our discovery layer.
== Questioning Authority: building a ruby gem to facilitate UI interactions with varied controlled vocabularies ==
* [[User:Mhbussey|Mark Bussey]], Data Curation Experts,
At a recent Hydra meeting, developers from five different institutions all realized that they had similar needs to constrain UI fields based on a variety of internal and external authorities in ways that minimized the need for custom coding for each vocabulary. During an intense three-day working session, they minted the initial release of the [ questioning authority] gem.
The talk will cover both how cross-institutional development helped speed development and how the gem can be used for accessing both external vocabularies like LCSH and LCNA and for presenting internal vocabulary lists. Although the developing institutions are all Hydra implementers, the gem itself doesn't have any Hydra dependencies and can be used in any Rails or Blacklight based application.
== Building Hydra, a framework; a community ==
Justin Coyne - Project Hydra contributor / Data Curation Experts - justin at
no previous C4L presentations
More than just a repository, the [ Hydra Project] is a community of cultural heritage institutions dedicated to pooling knowledge and resources. It is a completely open source project that has grown continuously for over 5 years. Within this vibrant community, a number of conventions and practices have emerged that we believe will benefit others attempting to cultivate support for their community oriented projects. The Hydra Project is now a mature initiative which is producing shareable, reusable and customizable components as well as complete repository solutions. In a time of tight budgets and growing demand for improved systems, we believe that "the Hydra way" is the exemplar case in the library community for how to work across institutions to deliver high quality services to our patrons. This talk will cover both the technical and human processes that have sustained Hydra's continued development and growth.
From []
In a Nutshell, Project Hydra...
* has had 8,364 commits made by 64 contributors representing 60,733 lines of code
* has a codebase with a long source history maintained by a very large development team with stable Y-O-Y commits
* took an estimated 15 years of effort (COCOMO model) starting with its first commit in October, 2009 ending with its most recent commit 7 days ago

Navigation menu