<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.code4lib.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Willkurt</id>
		<title>Code4Lib - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.code4lib.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Willkurt"/>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/Special:Contributions/Willkurt"/>
		<updated>2026-04-30T20:13:36Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.26.2</generator>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2011talks_Submissions&amp;diff=6208</id>
		<title>2011talks Submissions</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2011talks_Submissions&amp;diff=6208"/>
				<updated>2010-10-21T17:50:46Z</updated>
		
		<summary type="html">&lt;p&gt;Willkurt: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;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].&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
== Talk Title: ==&lt;br /&gt;
 &lt;br /&gt;
* Speaker's name, affiliation, and email address&lt;br /&gt;
* Second speaker's name, affiliation, email address, if second speaker&lt;br /&gt;
&lt;br /&gt;
Abstract of no more than 500 words.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== How &amp;quot;great&amp;quot; are the Great Books? ==&lt;br /&gt;
 &lt;br /&gt;
* Eric Lease Morgan, University of Notre Dame (emorgan at nd.edu)&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;great ideas&amp;quot; such as art, astronomy, beauty, evil, evolution, mind, nature, poetry, revolution, science, will, wisdom, etc. How &amp;quot;great&amp;quot; are these books, and how &amp;quot;great&amp;quot; are the ideas expressed in them?&lt;br /&gt;
&lt;br /&gt;
Given full text versions of these books it is almost trivial to use the &amp;quot;great ideas&amp;quot; as input and apply relevancy ranking algorithms against the texts thus creating a sort of score -- a &amp;quot;Great Ideas Coefficient&amp;quot;. Term Frequency/Inverse Document Frequency (TFIDF) is a well-established algorithm for computing just this sort of thing:&lt;br /&gt;
&lt;br /&gt;
relevancy = ( c / t ) * log( d / f ) where:&lt;br /&gt;
&lt;br /&gt;
* c = number of times a given word appears in a document&lt;br /&gt;
* t = total number of words in a document&lt;br /&gt;
* d = total number of documents in a corpus&lt;br /&gt;
* f = total number of documents containing a given word&lt;br /&gt;
&lt;br /&gt;
Thus, to calculate our Great Ideas Coefficient I sum the relevancy score for each &amp;quot;great idea&amp;quot; for each &amp;quot;great book&amp;quot;. 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 &amp;quot;greatness&amp;quot;. We could then compare the score to the scores of other books. Which book is the &amp;quot;greatest&amp;quot;? We could compare the score to other measurable things such as book's length or date to see if there were correlations. Are &amp;quot;great books&amp;quot; longer or shorter than others? Do longer books contain more &amp;quot;great ideas&amp;quot;? Are there other books that were not included in the set that maybe should have been included?&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== UNR BookFinder: Leveraging Google Books to Move Beyond Catalog Search ==&lt;br /&gt;
* Will Kurt, University of Nevada, Reno, (wkurt at unr.edu)&lt;br /&gt;
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].&lt;/div&gt;</summary>
		<author><name>Willkurt</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2011_Preconference_Proposals&amp;diff=6204</id>
		<title>2011 Preconference Proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2011_Preconference_Proposals&amp;diff=6204"/>
				<updated>2010-10-20T18:38:39Z</updated>
		
		<summary type="html">&lt;p&gt;Willkurt: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Proposals for 2011 Code4LibCon Preconferences ==&lt;br /&gt;
&lt;br /&gt;
Proposals will close Friday November 19 so we can finalize the list and add them to registration!&lt;br /&gt;
&lt;br /&gt;
We'll have space for up to 3 full-day pre-conferences and 3-6 half-day pre-conferences.&lt;br /&gt;
&lt;br /&gt;
'''Please include a &amp;quot;Contact/Responsible Individual&amp;quot; name and email address so we know who is willing to put on the proposed precon.'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Text mining ==&lt;br /&gt;
* Description: This workshop will describe and demonstrate the principles of text mining and other digital humanities computing techniques. With the advent of so much full text content available in libraries, and with the increasing ease in which people can find content, the question to ask one's self is, &amp;quot;What do I do with all of this content?&amp;quot; Or, as Gregory Crane said, [http://www.dlib.org/dlib/march06/crane/03crane.html &amp;quot;What do you do with a million books?&amp;quot;] Text mining, visualization, concordancing are some of the answers -- process for making sense of large full text corpora -- something often called &amp;quot;distant reading&amp;quot;. Participants will go away with a better understanding of what the digital humanities are and how they can applied in a library setting.&lt;br /&gt;
* Duration: half-day&lt;br /&gt;
* Speaker Bio: Eric Lease Morgan considers himself a librarian first and a computer user second. His professional goal is to discover new ways to use computer to provide better library services. Some of his more notable projects included Mr. Serials, Index Morganagus, the Alex Catalogue of Electronic Texts, and MyLibrary. Currently he spends his time investigating the digital humanities and integrating them into VUFind.&lt;br /&gt;
* Contact: Eric Lease Morgan (emorgan at nd.edu)&lt;br /&gt;
&lt;br /&gt;
== What's New In Solr ==&lt;br /&gt;
* Description: The library world is fired up about Solr.  Practically every next-gen catalog is using it (via Blacklight, VuFind, or other technologies).  Solr has continued improving in some dramatic ways, including geospatial support, field collapsing/grouping, extended dismax query parsing, pivot/grid/matrix/tree faceting, autosuggest, and more.  This session will cover all of these new features, showcasing live examples of them all, including anything new that is implemented prior to the conference.&lt;br /&gt;
* Duration: half-day&lt;br /&gt;
* Speaker Bio: Erik has spoken at several code4lib conferences (Keynoted Athens '07 along with the infamous pioneering Solr preconference, presented at Providence '09, and pre-conferenced Asheville '10).  Erik co-authored &amp;quot;Lucene in Action&amp;quot;, and he's a Lucene and Solr committer.  His library world claims to fame are founding and naming Blacklight, original developer on Collex and the Rossetti Archive search.&lt;br /&gt;
* Contact: Erik Hatcher (erik.hatcher at lucidimagination.com)&lt;br /&gt;
&lt;br /&gt;
== Intro to Functional Programming with JavaScript (and a little Haskell) ==&lt;br /&gt;
* Description: Functional programming is a topic that is becoming increasingly important for programmers to be aware of. Unfortunately it also has the reputation of being an area of programming that is particularly difficult and academic. Languages like Haskell, while being very powerful, certainly live up to this reputation. However many of the essential features of functional programming can be explored through a language as simple and commonplace as JavaScript.&lt;br /&gt;
&lt;br /&gt;
:This preconference talk will cover what makes a language ‘functional’ and the usage and implementation of essential features of functional programming: first-class functions, lambda functions, higher order functions, closures, and function currying. It will show how many of the powerful abstractions in a language like Haskell can also be implemented in a language like JavaScript, this will include a discussion of the trade offs between purity and performance.&lt;br /&gt;
&lt;br /&gt;
:The aim of this talk is to prepare participants to both implement functional techniques in everyday programming, as well as start exploring the topic more academically. Even if you never plan on coding in a purely functional style this workshop will give you an understanding of topics that should improve your programming in other languages with functional features such as Ruby, Python, and C#.  At the very least after this workshop you can go to the bar and throw around words like “lambda function”, “closure” and “currying” with confidence!&lt;br /&gt;
* Duration: half-day&lt;br /&gt;
* Speaker Bio: Will Kurt is the Applications Development Librarian at the University of Nevada, Reno, where he is also working on a master’s in Computer Science.  He has spoken at several library conferences including Computers in Libraries and Internet Librarian on topics including the Microsoft Surface and Visualizing Information.&lt;br /&gt;
* Contact: Will Kurt (wkurt at unr.edu)&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2011]]&lt;/div&gt;</summary>
		<author><name>Willkurt</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=Working_with_MARC&amp;diff=5761</id>
		<title>Working with MARC</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=Working_with_MARC&amp;diff=5761"/>
				<updated>2010-04-08T00:09:17Z</updated>
		
		<summary type="html">&lt;p&gt;Willkurt: /* MARC Programming Libraries */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Working with MARC ==&lt;br /&gt;
&lt;br /&gt;
MARC stands for Machine Readable Cataloging, and many folks in the code4lib community find themselves working with MARC records at some point. This page is meant to be a round-up of the tools for working with MARC. If you want a general introduction to the standard, [http://en.wikipedia.org/wiki/MARC_standards the wikipedia article] is a good place to start.&lt;br /&gt;
&lt;br /&gt;
=== Desktop tools ===&lt;br /&gt;
MarcEdit http://people.oregonstate.edu/~reeset/marcedit/html/index.php&lt;br /&gt;
&lt;br /&gt;
=== Getting Marc Indexed for Search Engines ===&lt;br /&gt;
&lt;br /&gt;
==== MARC in Solr ====&lt;br /&gt;
&lt;br /&gt;
SolrMarc http://code.google.com/p/solrmarc/&lt;br /&gt;
&lt;br /&gt;
Solr http://lucene.apache.org/solr&lt;br /&gt;
&lt;br /&gt;
==== MARC in Zebra ====&lt;br /&gt;
&lt;br /&gt;
Getting Started with Zebra http://wiki.code4lib.org/index.php/Getting_Started_with_Zebra&lt;br /&gt;
&lt;br /&gt;
Zebra  http://www.indexdata.com/zebra&lt;br /&gt;
&lt;br /&gt;
=== MARC Programming Libraries ===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
! Project !! Language !! class=&amp;quot;unsortable&amp;quot; | Links !! class=&amp;quot;unsortable&amp;quot; | Notes&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| MARC4J || Java || http://marc4j.tigris.org/ || &lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| javamarc || Java || http://github.com/billdueber/javamarc || Fork of MARC4J&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| MARC/pm || Perl || http://marcpm.sf.net || Umbrella project; see also [http://search.cpan.org/search?query=marc&amp;amp;mode=all CPAN]&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| pymarc || Python || http://github.com/edsu/pymarc/ || &lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| File_MARC || PHP || http://pear.php.net/package/File_MARC/ || PEAR package; sanctioned fork of PHP-MARC&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| PHP-MARC || PHP || http://www.emilda.org/index.php?q=php-marc || Abandoned(?)&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| ruby-marc || Ruby || http://rubyforge.org/projects/marc/ &amp;lt;br/&amp;gt; http://wiki.code4lib.org/index.php/Ruby-marc ||&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot; &lt;br /&gt;
| enhanced-marc || Ruby || http://github.com/rsinger/enhanced-marc || Convenience methods for ruby-marc&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot; &lt;br /&gt;
| marc21 || Scheme || http://code.google.com/p/marc21 ||&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| marcerl || Erlang || svn://pubserv.oclc.org/marcerl|| Very alpha code&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| Scala-MARC || Scala || http://github.com/achelous/Scala-MARC || &lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| CSharp Marc || C# || http://bitbucket.org/mattgrayson/csharp-marc ||&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| MARC.NET || C# || http://github.com/willkurt/MARC.NET || basic start, not thoroughly 'real world' tested&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Getting Sample Data ===&lt;br /&gt;
&lt;br /&gt;
One common question is where to get sample MARC records for testing or playing around with. If you work at a library, chances are good that you can get some records out of your ILS (go ask your systems librarian if you don't know how to do this yourself). If you don't work in a library, you can get MARC bibliographic records from the Internet Archive at [http://www.archive.org/details/marcrecords http://www.archive.org/details/marcrecords]. &lt;br /&gt;
&lt;br /&gt;
There is a nascent movement within the code4lib community to establish a test set of problematic MARC records, especially records that are representative of the kinds of weirdness that is encountered in real libraries. It is hoped that this could eventually become a test corpus against which to run various MARC processing implementations. For more information, watch [http://www.archive.org/details/MARCTHULU Simon Spero's excellent talk from Code4LibCon 2010].&lt;br /&gt;
&lt;br /&gt;
MARC records for authority data are more common. The [http://www.getty.edu/research/conducting_research/vocabularies/download.html Getty Vocabularies] makes both the The Art &amp;amp; Architecture Thesaurus (AAT) and The Union List of Artist Names (ULAN) freely available. The [http://www.library.northwestern.edu/public/gsafd/ Guidelines On Subject Access To Individual Works Of Fiction, Drama, Etc.] records are available from Northwestern University. The [http://www.nlm.nih.gov/mesh/filelist.html Medical Subject Headings (MeSH)] are available in many formats, one of them being MARC.&lt;/div&gt;</summary>
		<author><name>Willkurt</name></author>	</entry>

	</feed>