Code4Lib - User contributions [en]

Category:Code4Lib2016

2016-01-11T19:05:08Z

Rsinger: Link to Local Planning Committee; remove TBDs

{{Conference
|URL=http://2016.code4lib.org/
|Start Date=March 7 2016
|End Date=March 10 2016
|Location=Philadelphia
|Contact=[[2016_Conference_Committees#Local_Planning_Committee|Local Planning Committee]]
}}
*[[2016 Hosting Proposals]]
*[[2016 Conference Committees]]

*[[2016 Lessons Learned]] ([[2015 Lessons Learned]])

[[Category:Conferences]]

Category:Code4Lib2016

2016-01-11T18:36:09Z

Rsinger: Update conference url

{{Conference
|URL=http://2016.code4lib.org/
|Start Date=March 7 2016
|End Date=March 10 2016
|Location=Philadelphia
|Coordinates=TBD
|Organizers=TBD
|Contact=http://c4l-phl.github.io/
}}
*[[2016 Hosting Proposals]]
*[[2016 Conference Committees]]

*[[2016 Lessons Learned]] ([[2015 Lessons Learned]])

[[Category:Conferences]]

2013 project rideshare breakout

2013-02-13T22:40:55Z

Rsinger: /* Next steps */

== Overview ==

The goal of the "Project Rideshare Board" was to create an application/environment/community to help enable institutions to collaborate on software development projects and foster technology mentorship/learning opportunities amongst libraries.

One analogy of the project would be akin to http://kickstarter.com/, although rather than soliciting financial contribution (although that ''may'' be what a particular institution wishes to contribute, say, for contracting some work, etc.) institutions would pledge what expertise, roles, and time commitment they could provide to help bring the project to fruition.

There was discussion over what the overall scope of what such an endeavor would entail; if and how libraries would break out of their current cultural habits of always going it alone; what technologies currently exist that could handle the needs of this; how participants would manage and mediate projects; and what would be needed to get started.

At the end, we decided what is necessary is a system that allows a project proposer to:

# Describe the project: what it is, some functional requirements, what "completion" means
# What you're bringing to the table
# What you need

There would also be some best practices documentation to improve the chances of project success, usefulness to the broadest audience (without losing the needs of the original proposers), least duplication of effort, and reusability of code/features.

We discussed the possibility of a core of volunteers that would keep an eye on projects and try to help keep the projects aligned with the best practices (if applicable) and perhaps lend guidance for certain groups.

== Participants ==

* Ross Singer

== Next steps ==

* Start a Google Group : DONE! [https://groups.google.com/forum/?fromgroups#!aboutgroup/code4lib-project-rideshare]
* ???
* Launch the Rideshare Board!

2013 project rideshare breakout

2013-02-13T22:28:45Z

Rsinger: /* Overview */

2013 project rideshare breakout

2013-02-13T22:15:40Z

Rsinger:

2013 project rideshare breakout

2013-02-13T22:13:02Z

Rsinger:

The goal of the "Project Rideshare Board" was to create an application/environment/community to help enable institutions to collaborate on software development projects and foster technology mentorship/learning opportunities amongst libraries.

One analogy of the project would be akin to http://kickstarter.com/, although rather than soliciting financial contribution (although that ''may'' be what a particular institution wishes to contribute, say, for contracting some work, etc.) institutions would pledge what expertise, roles, and time commitment they could provide to help bring the project to fruition.

2013 project rideshare breakout

2013-02-13T22:12:17Z

Rsinger:

The goal of the "Project Rideshare Board" was to create an application/environment/community to help enable institutions to collaborate on software development projects and foster technology mentorship/learning opportunities amongst libraries.

One analogy of the project would be akin to [[http://kickstarter.com/|Kickstarter]], although rather than soliciting financial contribution (although that ''may'' be what a particular institution wishes to contribute, say, for contracting some work, etc.) institutions would pledge what expertise, roles, and time commitment they could provide to help bring the project to fruition.

2013 project rideshare breakout

2013-02-13T22:08:20Z

Rsinger:

The goal of the "Project Rideshare Board" was to create an application/environment/community to help enable institutions to collaborate on software development projects and foster technology mentorship/learning opportunities amongst libraries.

One analogy of the project would be akin to [http://kickstarter.com/], although rather than soliciting financial contribution (although that ''may'' be what a particular institution wishes to contribute, say, for contracting some work, etc.) institutions would pledge what expertise, roles, and time commitment they could provide to help bring the project to fruition.

2013 project rideshare breakout

2013-02-13T22:07:39Z

Rsinger: Created page with "The goal of the "Project Rideshare Board" was to create an application/environment/community to help enable institutions to collaborate on software development projects and foste..."

The goal of the "Project Rideshare Board" was to create an application/environment/community to help enable institutions to collaborate on software development projects and foster technology mentorship/learning opportunities amongst libraries.

One analogy of the project would be akin to [http://kickstarter.com/|Kickstarter], although rather than soliciting financial contribution (although that ''may'' be what a particular institution wishes to contribute, say, for contracting some work, etc.) institutions would pledge what expertise, roles, and time commitment they could provide to help bring the project to fruition.

2013 breakout sessions reports

2013-02-13T22:01:45Z

Rsinger: /* Wednesday, Feb.13, 2013 */

== Tuesday, Feb.12, 2013 ==
* CodeCraft - Writing better code - '''location: Room D''' [[2013_codecraft_breakout]]
* Code4Lib Journal discussion of editorial process (open to anyone) - '''Main Room, front right corner'''
* Tools for instruction: Guide on the Side, LMS integration, subject / course guides, etc. - '''Main Room, rear right corner''' Minutes: [[2013_instruction_breakout]]
* Marc4J, SolrMarc, and MARC -> Solr in general -- Next steps - '''Room E''' Minutes: [[2013_marc_breakout]]
* Building / Keeping relevant skills - How do you access training, develop skills, and keep current while still doing your day job - '''Room F''' Minutes: [[2013_breakout_remaining_relevant]]
* Cupcakes4Lib -- A Pilgrimage - '''Registration Table''' -- We ate cupcakes. It was amazing. We felt that we chose the right break out session. Photos of the yumminess can be found here. https://www.dropbox.com/sc/qe7uh2jmrs2mhmm/PJ3FjjMR9r
* relevance ranking and testing - '''Main room, left rear corner'''
* Fedora4Lib: Developer Challenge! (http://fedora4lib.org/hack/) - '''Main room, left front corner'''
* Nap4Lib: [http://www.youtube.com/watch?v=CVmGBoPx6Ms zzzzzzzzzzzzzzzzzzzzz]

== Wednesday, Feb.13, 2013 ==
* CORAL meetup: Are you using CORAL -- '''main room center back (by Francis' recording platform)''' [[2013_coral_meetup]]
* Open Library: status, needs, and infogami as a platform for experimentation -- '''Room F'''
* VuFind Update / Discussion -- '''main room front left'''
* Project Ride Sharing Board -- '''main room back left''' [[2013_project_rideshare_breakout]]
* Use cases, relevancy, and usability -- '''Room D''' [https://docs.google.com/document/d/1KtQlPIqdppw4a6HkrX7dfX1SxU3k6h9hFNVzpMeKKvg/edit notes]
* Lone technologists at small libraries -- '''Room E'''
* [https://docs.google.com/document/d/1BFaBIfhEctcVLUuQiwsKvJdWTN8Mujj8L88Wy7T39Ng/edit Archival Description Discovery Systems (EAD+beyond)] -- '''main room front right'''
* BorrowDirect, CIC, other lending cooperatives using Relais and IndexData tools -- '''main room back right'''
* Internally facing tools for institutional staff -- '''main room center front'''
[[Category:Code4Lib2013]]

2013 Lightning Talks Signup

2013-02-12T16:12:54Z

Rsinger:

'''Sign up for Lightning Talks!!'''

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. Sign-ups for lightning talks will open immediately following the first keynote.

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].

Have something to add but didn't get a chance to do it in Chicago? Consider signing up to present at the [[Virtual Lightning Talks]] on April 3rd, 2013.

'''LIGHTNING TALK SIGNUPS OPEN AT 10 AM EST ON FEBRUARY 12'''

Those who already have presentation slots, please hold off and give those without slots lightning talk chances, to spread around the opportunity to talk to the conference.

=== Tuesday, 4:20-5:20pm [12 slots] ===

Enter ''Name'' -- ''Title of Talk''

# Cynthia Ng / RULA Bookfinder
# Julien Gibert - turning a solr response into a rdf file
# Bill Dueber -- Datamart report generator at UMich
# Jonathan Rochkind -- bento_search
# Ross Singer - How are you managing copyright?
#
#
#
#
#
#
#

=== Wenesday, 4:20-5:20pm [12 slots] ===

Enter ''Name'' -- ''Title of Talk''

#
#
#
# Rachel Frick -- LODLAM Summit 2013 and Challenge
#
#
#
#
#
#
#
#

=== Thursday, 10:15-11:00am [9 slots] ===

Enter ''Name'' -- ''Title of Talk''

#
#
#
#
#
#
#
#
#

[[Category:Code4Lib2013]]

2013 preconference proposals

2012-11-29T15:49:15Z

Rsinger: /* RailsBridge Intro to Ruby on Rails */

Proposals '''now closed'''.

Spaces available: 4+ Rooms

Please follow the formatting guidelines:
<pre>
=== Talk Title ===

* Presenter/Leader, affiliation (optional), and email address (mandatory!)
* Second Presenter/Leader, affiliation, email address, if applicable

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com or
* [[User:cdmo|Charlie Morris]], NCSU Libraries, cdmorris@ncsu.edu

This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.

If we run out of topics, we will pay homage to the project by testing patches for Drupal 8. It is easy, and we will show you how to do this invaluable task.

Local Drupal uber-ninja Larry Garfield will stop by to answer questions and give us some guidance.

==Half Day Morning==

=== Open space session ===

* Dan Chudnov, dchud at gwu edu

The rest of code4libcon is pretty well structured these days; come in the morning for a few hours of old-school [http://en.wikipedia.org/wiki/Open-space_technology open space technology] unconference. Bring a rough talk or idea you want to share or questions you have or something you want to learn about or discuss with other people, and be ready to tell us about it. Use it as extra prep time for your upcoming prepared or lightning talk if you want. We'll plan the morning out a little bit at the beginning, but not too much. What we do will be up to the people there in the room.

If there's interest, we could start with a "welcome to code4lib" introductory session for newcomers.

=== Delivery services ===

* Ted Lawless, Brown University Library, tlawless at brown edu.

Are you interested in making it easier for users to obtain copies of known items? Do you feel your OpenURL and Interlibrary Loan software could be streamlined? This pre-conference workshop will focus on providing services that deliver content to users. Discovery systems are doing a better job of exposing library holdings but there's still a lot of work to do actually get the content in the users hands.

Possible topics/activities include:

* panel discussion of what some libraries have done in this area
* comparisons of different approaches to addressing delivery
* overview of tools available
* sharing of strategies and experiences
* time to work with and review open source code in this area. Some possible tools to install and test out [https://github.com/team-umlaut/umlaut Umlaut], [https://github.com/lawlesst/py360link Py360 Link].

Resources and background information:

* [https://github.com/team-umlaut/umlaut/wiki/What-is-Umlaut-anyway What-is-Umlaut-anyway]
* [http://journal.code4lib.org/articles/7308 Hacking 360 Link: A hybrid approach]
* [http://journal.code4lib.org/articles/108 Auto-Populating an ILL form with the Serial Solutions Link Resolver API]
* [http://lawlesst.github.com/notebook/delivery.html Focusing on Delivery]

=== Intro to Blacklight ===

* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, University of Virginia, WGBH, Johns Hopkins University, the Rock and Roll hall of fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

* Note: this workshop can be a standalone intro, or attendees can follow up with the intro to hydra workshop in the afternoon.
* Duration: half-day, morning

=== RailsBridge Intro to Ruby on Rails ===

* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)
* Shaun Ellis, Princeton University Library, shaune@princeton.edu
* Ross Singer, Talis, rossfsinger@gmail.com
* Anyone else want to come and help folks? Contact Jason.

RailsBridge comes to code4lib! We'll follow the RailsBridge curriculum (http://railsbridge.org) to provide a gentle introduction to Ruby on Rails. Topics covered include an introduction to the Ruby language, the Rails framework, and version control with git. Participants will build a working Rails application.

There will be some pre-preconference preparation needed so that we can effectively use our time. Details to come.

* Note: Attendees can follow up with the Intro to Blacklight afternoon session, which will be tailored for folks new to Ruby

===Intro to NoSQL Databases===
* Joshua Gomez, George Washington University, jngomez at gwu edu

Since Google published its paper on BigTable in 2006, alternatives to the traditional relational database model have been growing in both variety and popularity. These new databases (often referred to as NoSQL databases) excel at handling problems faced by modern information systems that the traditional relational model cannot. They are particularly popular among organizations tackling the so-called "Big Data" problems. However, there are always tradeoffs involved when making such dramatic changes. Understanding how these different kinds of databases are designed and what they can offer is essential to the decision making process. In this precon I will discuss some of the various types of new databases (key-value, columnar, document, graph) and walk through examples or exercises using some of their open source implementations like Riak, HBase, CouchDB, and Neo4j.

==Half Day Afternoon==
=== Data Visualization Hackfest ===
* Chris Beer, cabeer at stanford.edu
* Dan Chudnov, dchud at gwu edu

* Description: Want to hack/design/plan/document on a team of people who enjoy learning by creating? Interested in data visualization? Well, this hackfest is for you. Not familiar with the concept of a hackfest? See Roy Tennant's [http://www.libraryjournal.com/article/CA332564.html "Where Librarians Go To Hack"] and the page for the [http://access2010.lib.umanitoba.ca/node/3.html Access 2010 Hackfest]. We propose a half-day hackfest with a focus on visualization library data -- think stuff like library catalog data, access/circulation statistics, etc. Here's how it works, roughly:
- we'll (you'll!) do lightning tutorials for some data visualization tools, toolkits (R? d3js? ?), datasets.
- we'll separate into groups and hack on stuff.
- at the end of the day, we'll present our progress.

Not a code hacker? No worries; all skill sets and backgrounds are valuable!

* Duration: half-day

=== Intro to Hydra ===
* Adam Wead, Rock and Roll Hall of Fame (amsterdamos at gmail.com)
* Mike Giarlo, Penn State Information Technology Services (michael at psu.edu)
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)

Hydra (http://projecthydra.org) is a free and open source repository solution that is being used by institutions on both sides of the North Atlantic to provide access to their digital content. Hydra provides a versatile and feature rich environment for end-users and repository administrators alike. Leveraging Blacklight as its front end discovery interface, the hydra project provides a suite of software components, data models, and design patterns for building a robust and sustainable digital repository, as well as a community of support for ongoing development. This workshop will provide an introduction to the hydra project and its software components. Attendees will leave with enough knowledge to get started building their own local repository solutions. This workshop will be led by Adam Wead of the Rock and Roll Hall of Fame.

* Duration: half-day, afternoon

=== Intro to Blacklight ===

* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Justin Coyne, MediaShelf (justin.coyne at yourmediashelf.com)
* Jason Ronallo, NC State (jronallo at gmail.com)
* Shaun Ellis, Princeton University Library, (shaune@princeton.edu)

Blacklight (http://projectblacklight.org) is a free and open source discovery interface built on solr and ruby on rails. It is used by institutions such as Stanford University, NC State, WGBH, Johns Hopkins University, the Rock and Roll Hall of Fame, and an ever expanding community of adopters and contributors. Blacklight can be used as a front-end discovery solution for an ILS, or the contents of a digital repository, or to provide a unified discovery solution for many siloed collections. In this workshop we will cover the basics of solr indexing and searching, setting up and customizing Blacklight, and leave time for Q&A around local issues people might encounter.

* Note: this workshop will be tailored as a follow-on to the morning's RailsBridge Intro to Ruby on Rails workshop, but everyone is welcome
* Duration: half-day, afternoon

=== DPLA Intro/Hacking ===

* Presenter(s)/Leader(s): TBD
* Guy Who'd Be Interested in Helping: Jay Luker, Smithsonian Astrophysics Data System (jluker at cfa.harvard.edu)

This is a stub proposal entered solely to beat the submission deadline. I think there's be sufficient interest in this session, but only thought of it yesterday and haven't had time to coordinate with actual DPLA'ers and confirm that any of them are definitely coming.

=== Fail4lib ===
* Jason Casden, NCSU Libraries (jmcasden at ncsu.edu)

The Code4lib community is full of driven people who embrace the risks that are often associated with new projects. While these traits lead to the incredible projects that are presented at Code4lib, creative technical work also often leads to unexpected, vexing, or disappointing results even from eventually successful projects (however you define the term). Learning more about how our colleagues deal with failure in various contexts could lead to the development of better methods for communicating the value of productive failure, modifying project plans ("The Pivot"), and failing more cheaply.

Hopefully we can define the format as a group, but a fairly high level of participation is crucial if this is to be a worthwhile preconference. Some possible agenda items that could be mixed and matched to fill the afternoon:

# Given willing presenters, a series of 10-20 minute presentations that go into some depth about specific failures.
# Depending on the number of participants, either a multi- or single-track series of unconference-like themed discussions on various aspects of failure, possibly including themes like:
#* Technical failure
#* Failure to effectively address a real user need
#* Overinvestment
#* Outreach/Promotion failure
#* Design/UX failure
#* Project team communication failure
#* Missed opportunities (risk-averse failure)
#* Successes gleaned from failures
# A panel of participants who have prepared in advance to answer moderator and audience questions about their experience with failure.
# A prepared reading assignment that we could all forget to read, creating a shared fail in order to start the preconference on the right foot.

I'll serve as a moderator (if needed) and participant and would welcome more organizers. I am happy to be outvoted by participants on any of these points--I just want to get us talking about our screw-ups, blind spots, and anvils dropping from the sky.

==Half Day Evening==

=== Solr 4 In Depth ===

* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format.

* Duration: half-day
* Note: I put this under "Half Day Evening" only because I didn't want to conflict with the other great half day sessions already proposed here. However it makes the most sense to arrange the sessions is fine with me though.

[[Category:Code4Lib2013]]

Mentorship

2012-06-04T17:48:48Z

Rsinger:

We're looking to try out a mentorship program through the #code4lib channel on IRC Freenode. The idea is that experienced people who are willing to volunteer some time would provide 1-on-1 mentoring to those who would like to learn during an "Office hours" period, once a week. The idea is sort-of modelled on the Drupal project's [http://drupal.org/node/1242856 Core Office Hours]. If this sounds like something you'd like to contribute to, don't hesitate to add your name!

{| border="1" cellspacing="0" cellpadding="5" align="center"
! Mentor name
! IRC name
! Social
! Willing to help with
! Office hours
|-
| [[User:Mdm|Matt McCollow]]
| mdm_
|
| Javascript
| Fridays, 1-2 pm EST
|-
| [http://ruebot.net Nick Ruest]
| ruebot
| [http://twitter.com/ruebot Twitter] [https://plus.google.com/107824412266039153440 G+]
| Islandora
| Fridays, 1-2 pm EST (pls ping in advance)
|-
| [http://jbfink.github.com John Fink]
| jbfink
|
| git
| Fridays, 1-2pm EST
|-
| [http://lackoftalent.org/michael/ Mike Giarlo]
| mjgiarlo
|
| Repository technology and architecture, Ruby, Git, Project Hydra, "Persistent identifiers"
| Fridays, 1-2 pm EST (though pls ping in advance)
|-
| [http://kennison.name/ Brian Kennison]
| briankenn
|
| xslt
| Fridays, 1-2pm EST (let me know what works for you)
|-
|}

C4L2011 rideshare

2010-12-17T23:51:52Z

Rsinger: /* Chattanooga, TN (via Nashville, Bowling Green & Louisville) */

=== Indianapolis International Airport ===

'''Arrivals'''
{| border="1" cellpadding="5" class="sortable"
|- style="text-align: left;"
! Name !! Flight Arriving !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?
|-
| [mailto:andrew.nagy@serialssolutions.com Andrew Nagy] || 2011-02-06 20:00 (Sunday; 8pm) || Yes || No || No || Me || No || 1. 2. 3.
|-
| [mailto:cgordon@chillco.com Cary Gordon] || 2011-02-06 18:00 (Sunday; 6pm) || Yes || ? || ? || Me || ? || 1. 2. 3.
|}

'''Departures'''
{| border="1" cellpadding="5" class="sortable"
|- style="text-align: left;"
! Name !! Flight Departing !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?
|-
| [mailto:andrew.nagy@serialssolutions.com Andrew Nagy] || 2011-02-10 15:00 (Thursday; 3pm) || Yes || No || No || Me || No || 1. 2. 3.
|-
| [mailto:cgordon@chillco.com Cary Gordon] || 2011-02-10 19:00 (Thursday; 7pm) || Yes || ? || ? || Me || ? || 1. 2. 3.
|}

=== Northwest Columbus, OH ===
'''Arrivals'''
{| border="1" cellpadding="5" class="sortable"
|- style="text-align: left;"
! Name !! Departing Columbus !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?
|-
| [[User:DataGazetteer|Peter Murray]] || 2011-02-07 08:00 (Monday, 8am) || Yes || No || No || Yes || No || 1. 2. 3.
|}

'''Departures'''
{| border="1" cellpadding="5" class="sortable"
|- style="text-align: left;"
! Name !! Departing Bloomington !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?
|-
| [[User:DataGazetteer|Peter Murray]] || 2011-02-10 12:00 (Thursday, noon) || Yes || No || No || Yes || No || 1. 2. 3.
|}

=== Chattanooga, TN (via Nashville, Bowling Green & Louisville) ===
'''Arrivals'''
{| border="1" cellpadding="5" class="sortable"
|- style="text-align: left;"
! Name !! Departing Chattanooga !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?
|-
| [[User:Rsinger|Ross Singer]] || 2011-02-07 (Monday AM) || No || No || If you're willing || Yes || No || 1. 2. 3.
|}

'''Departures'''
{| border="1" cellpadding="5" class="sortable"
|- style="text-align: left;"
! Name !! Departing Bloomington !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?
|-
| [[User:Rsinger|Ross Singer]] || 2011-02-10 12:00 (Thursday PM) || No || No || Your call || Yes || No || 1. 2. 3.
|}

Zen of Web

2010-11-29T23:06:50Z

Rsinger:

This is a collaborative effort to document the subtleties of building applications on the Web. The idea took inspiration from the [http://www.python.org/dev/peps/pep-0020/ Zen of Python]. Please feel free to edit/add items below:

* Default to open
* Less is more
* Everything is broken
* View the source Luke
* Keep it simple
* Nobody knows if you are a dog
* Explicit is better than implicit
* Pave the cowpaths
* Small pieces, loosely joined
* de facto usually beats de jure
* No permission needed
* Be conservative in what you send; be liberal in what you accept.
* Follow your nose
* Everything is intertwingled
* The world is your audience
* You GET what you need
* You can't always GET what you want
* Resource-oriented (vs. service-oriented)
* Tagsoup tastes good
* A resource can be anything
* Caching is your friend
* Media types are one honking great idea -- let's do more of those!

If it turns into a useful list it could be turned into a collaborative code4lib2011 lightning talk or something.

How "great" are the Great Books

2010-11-15T19:34:31Z

Rsinger: Code4Lib2011TalksProposals/How "great" are the Great Books moved to How "great" are the Great Books

== 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.

[[Category:Code4Lib2011TalksProposals]]

Code4Lib2011TalksProposals/How "great" are the Great Books

2010-11-15T19:34:31Z

Rsinger: Code4Lib2011TalksProposals/How "great" are the Great Books moved to How "great" are the Great Books

#REDIRECT [[How "great" are the Great Books]]

How "great" are the Great Books

2010-11-15T19:30:23Z

Rsinger: /* How "great" are the Great Books? */

How "great" are the Great Books

2010-11-15T19:26:53Z

Rsinger: New page: == 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 publ...

Category:Code4Lib2011TalksProposals

2010-11-15T19:25:10Z

Rsinger: New page: Presentation Proposals for Code4Lib 2011

Presentation Proposals for Code4Lib 2011