Code4Lib - User contributions [en]

2011talks Submissions

2010-11-04T17:27:22Z

Doporter:

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.

Please follow the formatting guidelines:

<pre>
== Talk Title: ==

* Speaker's name, affiliation, and email address
* Second speaker's name, affiliation, email address, if second speaker

Abstract of no more than 500 words.
</pre>

== How "great" are the Great Books? ==

* Eric Lease Morgan, University of Notre Dame (emorgan at nd.edu)

In the 1960s a set of books called the Great Books of the Western World was published. It was supposed to represent the best of Western literature and enable the reader to further their liberal arts education. Sixty volumes in all, it included works by Plato, Aristotle, Shakespeare, Milton, Galileo, Kepler, Melville, Darwin, etc. These great books were selected based on the way they discussed a set of 102 "great ideas" such as art, astronomy, beauty, evil, evolution, mind, nature, poetry, revolution, science, will, wisdom, etc. How "great" are these books, and how "great" are the ideas expressed in them?

Given full text versions of these books it is almost trivial to use the "great ideas" as input and apply relevancy ranking algorithms against the texts thus creating a sort of score -- a "Great Ideas Coefficient". Term Frequency/Inverse Document Frequency (TFIDF) is a well-established algorithm for computing just this sort of thing:

relevancy = ( c / t ) * log( d / f ) where:

* c = number of times a given word appears in a document
* t = total number of words in a document
* d = total number of documents in a corpus
* f = total number of documents containing a given word

Thus, to calculate our Great Ideas Coefficient I sum the relevancy score for each "great idea" for each "great book". Plato's Republic might have a cumulative score of 525 while Aristotle's On The History Of Animals might have a cumulative score of 251. Books with a larger Coefficient could be considered greater. Given such a score a person could measure a book's "greatness". We could then compare the score to the scores of other books. Which book is the "greatest"? We could compare the score to other measurable things such as book's length or date to see if there were correlations. Are "great books" longer or shorter than others? Do longer books contain more "great ideas"? Are there other books that were not included in the set that maybe should have been included?

The first part of this talk describes the different steps involved in the text pre-processing to calculate an accurate TFIDF value for each item of the corpus. The results and statistical analysis are discussed in the second part. Finally I will outline the remaining work such as refining the analysis and extending the current quantitative process to a web implementation.

== UNR BookFinder: Leveraging Google Books to Move Beyond Catalog Search ==
* Will Kurt, University of Nevada, Reno, (wkurt at unr.edu)
Google Books is a great tool, but it lacks an easy method allowing users to access the items they find through their library. The UNR BookFinder is a mashup of the Google Books and WorldCat APIs (and some ugly hacks) which allows users to search for items with the power of Google’s fulltext search while eliminating the need to search all of the library’s various resources to find an item. The UNR BookFinder automatically searches the catalog and consortial ILL for the item, if these fail an ILLiad request form as automatically filled out. The end result is that the user can explore an universe of books and access them as fast as possible through the university library. A video of the alpha version can be found [http://www.youtube.com/watch?v=qaqcUSTtdVk here].

== Moving a large multi-tiered search architecture from dedicated hosts to the cloud ==
* Peter Ciuffetti, Senior Software Engineer, Credo Reference Ltd. (pete at credoreference.com)
So you want to move a large production search service from dedicated hosts to the cloud? The flexibility is enticing, the costs are attractive, the geek cred is undeniable. Our cloud adventure came with many undocumented surprises ranging from mysterious server behavior to sales engineers suggesting that 'maybe the cloud isn't for you'. We eventually made it all work and our production service is now on the cloud. This talk will cover what the cloud product FAQs don't say, what their tech support doesn't know (or won't say) and mistakes you can avoid by talking to the guys with the arrows in their backs.

== VuFind Beyond MARC: Discovering Everything Else ==
* Demian Katz, Library Technology Development Specialist, Villanova University (demian dot katz at villanova dot edu)
The VuFind[http://vufind.org] discovery layer has been providing a user-friendly interface to MARC records for several years now. However, library data consists of more than just MARC records, and VuFind has grown to accommodate just about anything you can throw at it. This presentation will examine the new workflows and tools that enable discovery of non-MARC resources and some of the non-traditional applications of VuFind that they make possible. Technologies covered will include OAI-PMH, XSLT, Aperture, Solr and, of course, VuFind itself.

== Linked data apps for medical professionals ==
* Rurik Thomas Greenall, NTNU Library, (rurik dot greenall at ub dot ntnu dot no)
The promise of linked data for libraries has yet to be realized, as a demonstration of the power of RDF, HTTP-URIs and SPARQL, NTNU Library together with the Norwegian Electronic Health Library produced a linked data representation of MeSH and created a small translation app that can be used to help health professionals identify the right term and apply it in their database searches. This talk presents the simple ways in which the core technologies and concepts in linked data provide a solid, time-saving way of developing usable applications.

== fiwalk With Me: Building Emergent Pre-Ingest Workflows for Digital Archival Records using Open Source Forensic Software ==
* Mark A. Matienzo, Manuscripts and Archives, Yale University Library (mark at matienzo dot org)
Many of the complications of born-digital records involve preparing them for transfer into a storage or preservation environment. Digital evidence of any kind is easily susceptible to unintentional and intentional modification. This presentation will describe the use of open source forensic software in pre-ingest workflows for digital archives. Digital archivists and other digital curation practitioners can develop emergent processes to prepare records for ingest and transfer using a combination of relatively simple tools. The granularity and simplicity of these tools and procedures provides the possibility for their smooth integration into a digital curation environment built on micro-services.
== Why (Code4) Libraries Exist ==
* Eric Hellman, President, Gluejar, Inc. (eric at hellman dot net)
Libraries have historically delivered value to society by facilitating the sharing of books. The library "brand" is built around the building and exploitation of their collections. These collections have been acquired and owned. As ebook readers become the preferred consumption platform for books, libraries are beginning to come to terms with the fact that they don't own their digital collections, and can't share books as they'd like to. Yet libraries continue to be valuable in many ways. In this transitional period, only one thing can save libraries from irrelevance and dissipation: Code.
== The Story of TILE: Making Modular & Reusable Tools ==
* Doug Reside, MITH, University of Maryland (dougreside at gmail dot com)

The Text Image Linking Environment (TILE) is a collaborative project between the Maryland Institute for Technology in the Humanities (MITH), the Digital Library Program at Indiana University, and the School of Library and Information Science at Indiana University Bloomington. Since May 2009, the TILE project team has been developing through NEH Research & Development funding a web-based, modular, image markup tool for both semi-automated linking between encoded text and image of text, and image annotation. The software will be complete and ready for release in June 2011.

The basic functionality of TILE is to create links between images and text that relates to that image – either annotations or transcriptions. We have paid particular attention to linking between image of text and transcription of text. These links may be made manually, but the project also includes an algorithm, written in JavaScript, for recognizing text within an image and automatically associating the coordinates with a Unicode transcription. Additionally, the tool can import and export transcriptions and links from and to a variety of metadata formats (TEI, METS, OWL) and will provide an API for developers to write mappings for additional formats. Of course, this functionality is immediately useful to a relatively limited set of editors of digital materials, but we have made modularity and extensibility primary goals of the project.

Many members of the TILE development team are also members of the Open Annotation Collaboration (OAC), and have therefore attempted to develop TILE’s annotation features to be OAC compliant. Like OAC, TILE assumes that the text and the images to be linked may exist at separate and completely unconnected servers. When a user starts the TILE tool for the first time, she is prompted to supply a URI to a TILE compliant JSON file.

TILE’s JSON is simple and thoroughly documented, and we provide several translators to map common existing metadata formats to the format. We have already created a PHP script that will generate TILE JSON from a TEI P5 document and are currently working to do the same for the METS files used in the Indiana University’s METS navigator tool.

Additionally, TILE provides a modular exporting tool that allows users to run the work they’ve done in TILE through an external translator and then download the result to the client computer. For example, a user may import a set of images and transcripts from a METS file at the Library of Congress, use TILE to link images and text, and then export the result as a TEI file. The TEI file may then be reimported to TILE at a later data to further edit or convert the file.

At Code4Lib, we will demonstrate the functionality of TILE and display a poster and provide handouts that describe the thinking behind TILE, how it is intended to be used, and details on how TILE is built and functions.

C4L2011planning

2010-10-27T19:40:48Z

Doporter: /* Draft Timeline */

'''This page is currently under development'''

== 20 Minute Talks ==
* [[2011talkscall Call for Submissions]]
* [[2011talks Submissions]]

== Tasks ==
* sponsorships (see [[2011 committees sign-up page]])
* keynote speakers (see [[2011 committees sign-up page]] and [[2011 nominations list]])
** CHANGE FOR 2011: how to address (or not address) nomination of past keynoters?
** CHANGE FOR 2011: figure out in advance what will be the official channel for nominations (e-mail thread, wiki page, some other webapp, etc.)
** CHANGE FOR 2011: ensure every nomination includes a nominee and a biographic paragraph
* program committee (20-minute talks) (see [[2011 committees sign-up page]])
** CHANGE FOR 2011: decide on program structure EARLIER. should know how many prepped talks (if doing prepped talks) will be accepted in advance of the vote.
* scholarship committee (see [[2011 committees sign-up page]])
* documentation/how-to group (keep records of this year, consolidate with "best practices" so that it's easier in the future) (see [[How To Plan A Code4LibCon]] )
* T-shirt committee (see [[2011 committees sign-up page]])
* [[C4L2011 social activities|social activities]] (see [[2011 committees sign-up page]])
* voting coordination (see [[2011 committees sign-up page]])
* wifi
* non-wifi technology (e.g. mbklein's kickass 3-in-1 computer system)
* logistics (e.g. Coordinate airport transportation)
* MC and on-the-ground coordination/liasoning

== Draft Timeline==
Monday February 22 (preconference) – Thursday February 25

'''Calls and posts are to code4lib listserv unless otherwise specified'''

May to June: Choose Conference planners

May to June: Negotiate Hotel contract

May to June: Touch base with sponsors

July 10:
Share dates and hotel info on code4lib with reminder about code4libcon for those interesting in planning, #c4l10
On code4libcon, ask for volunteers for contacting sponsors

July 15th – Call for keynote speaker suggestions(with blurbs) see also [[2011_nominations_list]]

July 15th – Formally solicit sponsors

August 17th – Tally of keynote speaker suggestions, final call to code4lib list

August 20th – Follow up with sponsors

Sept 9th-Septh18th – keynote speaker vote

Sept 22nd – Keynote speaker invitations begin

Oct 15 – Call for 20-minute talk proposals, preconference proposals

Oct 30 —Posted reminder with presenter-guarantee policy

Nov 13 – 20-minute talk proposals due

Nov 14-Nov 22 – voting on 20-minute talk proposals

Nov 15 – Begin testing registration

Nov 16th – Reminder: registration opens Dec 2nd

Nov 19 - preconference proposals due

Nov 28th – List of top 22ish talk titles posted

Nov 29th – Scholarship announcement ***post beyond code4lib list???***

Dec 1 – Draft schedule posted for comment (no titles – just placeholders for 22ish talks)

Dec 1 – Reminder, Registration opens Dec 2

Dec 2 – Registration opens

Dec 2 – Post when registration opens

Dec 2 – Share waitlist & preconf count info???

Dec 7—Registration deadline for presenter-reserved spots

Jan 5 – Scholarship deadline

Jan 5 – ask code4libcon to set requirements for 2011 hosting proposals

Jan 5 – Call for t-shirt design submissions

Jan 12 – Scholarship recipients notified

Jan 12 – call for code4lib2011 hosting proposals

Jan 15 – T-shirt design deadline

Jan 20-28 T-shirt vote

Feb 8 – discussion of volunteer needs

Feb 12 – deadline for code4lib2011 hosting proposals

Feb 15 – Call for Breakout Session ideas

Feb 15 – Call for conference volunteers

Feb 17 – Reminder to participants with travel info, conference social info

Feb 17-24 – vote for 2011 host

March 1-31–Videos converted, compressed, uploaded, and linked

==When do these things happen?==

*Making T-shirts
*Planning conference menus
*Arranging videotaping
*Securing conference networking
*Getting A/V supplies
*Arranging 3 OS laptop for presenters (ask mbklein)

==Other things to be done?==

==Random stuff==
[http://digital.library.appstate.edu/code4lib2010.html Original Proposal]

[http://vote.code4lib.org/election/results/9 Voting results]
[[Category: Code4Lib2011]]

2011 Breakout Sessions

2010-10-19T14:43:36Z

Doporter: New page: Those interested in the same project/problem can hang out in a space together for 70 minute blocks. Generally the person who suggests the topic will take on the role as moderator to begin ...

Those interested in the same project/problem can hang out in a space together for 70 minute blocks. Generally the person who suggests the topic will take on the role as moderator to begin and moderate the discussion. Anyone can propose a breakout session - please think about whether you would want a session to be held on Tuesday or Wednesday, depending on the order of talks and who you hope will attend. There are a lot of rooms available each day, including the large meeting room, and we will route different proposed sessions to the different rooms depending on a quick show-of-hands survey just before each one begins.

This page will list any sessions proposed, but there will also be flip charts outside the meeting room where more sessions can be proposed. '''Please include your name when proposing a session.'''

2011 Lightning Talks Signup

2010-10-19T14:12:31Z

Doporter:

Lightning talks are scheduled on all three days of the conference. A lightning talk is a fast-paced 5 minute talk on a topic of your choosing.

Mark Jason Dominus has a nice page [http://perl.plover.com/lt/lightning-talks.html about lightning talks], which includes this summary of why you might want to do one:

Maybe you've never given a talk before, and you'd like to start small. For a Lightning Talk, you don't need to make slides, and if you do decide to make slides, you only need to make three.

Maybe you're nervous and you're afraid you'll mess up. It's a lot easier to plan and deliver a five minute talk than it is to deliver a long talk. And if you do mess up, at least the painful part will be over quickly.

Maybe you don't have much to say. Maybe you just want to ask a question, or invite people to help you with your project, or boast about something you did, or tell a short cautionary story. These things are all interesting and worth talking about, but there might not be enough to say about them to fill up thirty minutes.

You might also like Mark Fowler's's [http://www.perl.com/pub/2004/07/30/lightningtalk.html Advice for Giving a Lightning Talk]

Note to presenters: Projector resolution is 1024x768

2011 Lightning Talks Signup

2010-10-19T14:08:37Z

Doporter:

Lightning talks are scheduled on all three days of the conference. A lightning talk is a fast-paced 5 minute talk on a topic of your choosing.

Needed: volunteer to ensure presentation files get added to this page.

Mark Jason Dominus has a nice page [http://perl.plover.com/lt/lightning-talks.html about lightning talks], which includes this summary of why you might want to do one:

Maybe you've never given a talk before, and you'd like to start small. For a Lightning Talk, you don't need to make slides, and if you do decide to make slides, you only need to make three.

Maybe you're nervous and you're afraid you'll mess up. It's a lot easier to plan and deliver a five minute talk than it is to deliver a long talk. And if you do mess up, at least the painful part will be over quickly.

Maybe you don't have much to say. Maybe you just want to ask a question, or invite people to help you with your project, or boast about something you did, or tell a short cautionary story. These things are all interesting and worth talking about, but there might not be enough to say about them to fill up thirty minutes.

You might also like Mark Fowler's's [http://www.perl.com/pub/2004/07/30/lightningtalk.html Advice for Giving a Lightning Talk]

Note to presenters: Projector resolution is 1024x768

2011 Lightning Talks Signup

2010-10-19T14:05:34Z

Doporter: New page: [http://code4lib.org/conference/2011/lightning Code4Lib page about lightning talks] Note to presenters: Projector resolution is 1024x768

[http://code4lib.org/conference/2011/lightning Code4Lib page about lightning talks]

Note to presenters: Projector resolution is 1024x768

2011talks Submissions

2010-10-19T01:15:07Z

Doporter: New page: Deadline for talk submission was Friday, November 13. Edits to existing proposals are no longer allowed as these are being processed for the voting system. Please follow the formatting gu...

Deadline for talk submission was Friday, November 13. Edits to existing proposals are no longer allowed as these are being processed for the voting system.

Please follow the formatting guidelines:

== Talk Title: ==

* Speaker's name, affiliation, and email address
* Second speaker's name, affiliation, email address, if second speaker

Abstract of no more than 500 words.

2011 Preconference Proposals

2010-10-19T01:01:30Z

Doporter:

== Proposals for 2011 Code4LibCon Preconferences ==

Proposals will close Friday November 19 so we can finalize the list and add them to registration!

'''Please include a "Contact/Responsible Individual" name and email address so we know who is willing to put on the proposed precon.'''

2011 Preconference Proposals

2010-10-19T01:00:32Z

Doporter: New page: == Proposals for 2011 Code4LibCon Preconferences == ''' Proposals will close Friday November 19 so we can finalize the list and add them to registration!'''

== Proposals for 2011 Code4LibCon Preconferences ==

'''
Proposals will close Friday November 19 so we can finalize the list and add them to registration!'''

2011talkscall Call for Submissions

2010-10-18T16:34:51Z

Doporter:

== Call for Proposals ==

'''The Code4Lib 2011 conference'''

Code4Lib 2011 is a conference for library technologists to commune, gather/create/share ideas and software, be inspired, and forge collaborations. It is also an outgrowth of the Access HackFest, wrapped into a conference-like format. It is *the* event for technologists building digital libraries and digital information systems, tools, and software.

The conference will be held Monday February 7th - Thursday February 10th, 2011 in Bloomington, IN. More information can be found at http://code4lib.org/conference/2011/.

'''Prepared talks'''

Prepared talks are 20 minutes, and must focus on one or more of the following areas:

* "tools" (some cool new software, software library or integration platform)
* "specs" (how to get the most out of some protocols, or proposals for new ones)
* "challenges" (one or more big problems we should collectively address)

The community will vote on proposals using the criteria of:

* usefulness
* newness
* geekiness
* diversity of topics

We cannot accept every prepared talk proposal, but multiple lightning talk sessions should provide everyone who wishes to present with an opportunity to do so.

'''Schedule'''

Proposals can be submitted through ''November 13''. Voting will commence soon thereafter and be open through ''December 1st''. Successful candidates will be notified by ''December 3rd''. The submitter (and if necessary a second presenter) will be guaranteed an opportunity to register for the conference through ''December 21st''.

'''Guidelines for Proposals and Submissions'''

Proposal abstracts must be '''no longer than 500 words'''. Include your '''name''' and '''email address'''. All proposals should be [[2011talks_Submissions|submitted on the wiki page]].

[[Category:Code4Lib2011]]

2011talkscall Call for Submissions

2010-10-18T16:24:17Z

Doporter: New page: == Call for Proposals == '''The Code4Lib 2011 conference''' Code4Lib 2011 is a conference for library technologists to commune, gather/create/share ideas and software, be inspired, and f...

== Call for Proposals ==

'''The Code4Lib 2011 conference'''

Code4Lib 2011 is a conference for library technologists to commune, gather/create/share ideas and software, be inspired, and forge collaborations. It is also an outgrowth of the Access HackFest, wrapped into a conference-like format. It is *the* event for technologists building digital libraries and digital information systems, tools, and software.

The conference will be held Monday February 7th - Thursday February 10th, 2010 in Bloomington, IN. More information can be found at http://code4lib.org/conference/2011/.

'''Prepared talks'''

Prepared talks are 20 minutes, and must focus on one or more of the following areas:

* "tools" (some cool new software, software library or integration platform)
* "specs" (how to get the most out of some protocols, or proposals for new ones)
* "challenges" (one or more big problems we should collectively address)

The community will vote on proposals using the criteria of:

* usefulness
* newness
* geekiness
* diversity of topics

We cannot accept every prepared talk proposal, but multiple lightning talk sessions should provide everyone who wishes to present with an opportunity to do so.

'''Schedule'''

Proposals can be submitted through ''November 13''. Voting will commence soon thereafter and be open through ''December 1st''. Successful candidates will be notified by ''December 3rd''. The submitter (and if necessary a second presenter) will be guaranteed an opportunity to register for the conference through ''December 21st''.

'''Guidelines for Proposals and Submissions'''

Proposal abstracts must be '''no longer than 500 words'''. Include your '''name''' and '''email address'''. All proposals should be [[2011talks_Submissions|submitted on the wiki page]].

[[Category:Code4Lib2011]]