Code4Lib - User contributions [en]

2013 journal breakout

2013-02-14T17:30:38Z

Gsf:

We had a nice discussion about the journal, with 15 or so attending. About a third of those present are on the editorial committee, including Peter Murray, Shawn Averkamp, Andrew Darby, Jonathan Rochkind, Terry Reese, and Gabriel Farrell.

=== Topics of discussion ===

Too many articles per issue? Maybe.
Many agreed with the statement that 10 seemed about the right number. Too many more and it becomes difficult to find time to read the articles.
There was an explicit desire from the non-editors in the group to keep to a quarterly issue schedule versus a pipeline where articles were published when they were ready.

Call for new editors? Sometime soon.

We need to make the deadline for complete drafts more important to give other editors a chance to get involved earlier in the process.

Our pseudo-peer-review process works pretty well for the most part.
Do we want to open up the submission discussion process broadly (while still reserving the voting for the identified editors)?
(As an aside, if we did this, could this be used to solicit adjunct editors for articles on topics that we don't have a depth of experience on the editorial committee?)

2013 journal breakout

2013-02-13T23:32:27Z

Gsf: Created page with "We had a nice discussion about the journal, with 13 or so attending. About half of those present are on the editorial committee, including Peter Murray, Shawn Averkamp, Andrew Da..."

We had a nice discussion about the journal, with 13 or so attending. About half of those present are on the editorial committee, including Peter Murray, Shawn Averkamp, Andrew Darby, Jonathan Rochkind, Terry Reese, and Gabriel Farrell.

=== Topics of discussion ===

Too many articles per issue? Maybe.

Call for new editors? Sometime soon.

We need to make the deadline for complete drafts more important to give other editors a chance to get involved earlier in the process.

Our pseudo-peer-review process works pretty well for the most part.

2013 breakout sessions reports

2013-02-13T23:13:41Z

Gsf: /* Tuesday, Feb.12, 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''' [[2013_journal_breakout]]
* 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''' [http://okfnpad.org/c4l2013-ol notes]
* VuFind Update / Discussion -- '''main room front left''' [http://lullapad.com/84oT6fXhM6]
* 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 -- '''epic note fail, may be a while before I can recreate them (tshearerlib)'''
[[Category:Code4Lib2013]]

2013 social activities

2013-02-12T22:57:32Z

Gsf: /* Non-beery get together */

== Ideas ==

* Aviary: super-crazy cocktails. http://www.molecularrecipes.com/molecular-mixology/aviary-cocktails/ . List your name if you're interested, whether Sunday, Monday, and/or Tuesday (after newcomer dinners) work, and whether you're just interested in stopping by, or doing a 7 cocktail tasting flight.*
** statsfool: sunday/monday/tuesday, either drinks or flight.
** Amyhannah: monday/tuesday, drinks, probably not the flight.
** anarchivist: sunday/monday, prefer drinks over flight but could be convinced
** [[User:highermath|highermath]]: monday (could use 10 cocktails after Drupal subCon, I am sure). Uber now works in Chicago, so I would do the flight.
** [[User:pberry|pberry]]: any night but Wednesday (that's Goose Island night) and I'd be up for drinks or flight, although leaning away from flight.
** [[User:thatandromeda|thatandromeda]] oh my gosh yes, any time, probably not the flight.
** [[User:Gdave|gdave]] beautiful site, I would be interested, Sun,Mon,Tues. either drink or flight.
** [[User:shawnc12|shawnc12]]: sunday/monday, either drink or flight
** wdenton: any night, either drink or flight
** beatricep: sunday/monday drink, highly susceptible to flight by peer pressure..
** ryan hess: sunday/monday drink or flight
** infosoph: sunday/monday yes/yes!!
** [[User:Pfeeley|Pfeeley]]: sunday/monday/tuesday, either drink or flight
** [[User:Ksprague|Ksprague]]: tuesday, drink or flight
** [[User:schwartzray|schwartzray]]: anything on any day
* Brewery tour - some possible candidates would be Goose Island, Brew Bus http://www.chicagobrewbus.com/, Piece, Revolution, Half Acre.
* Library field trips - because we're library geeks. Possible places include Newberry and Read/Write.--Read/Write Library confirmed for February 11.--Newberry Library confirmed for February 14.
* Art Institute of Chicago - Only open until 5pm, but possible for people coming in early enough on Sunday. There seems to be enough interest here to actually have a group, when and where should we meet? I added my email so that we could discuss details off the wiki.
** escowles: I'm getting in around noon on Sunday, and interested in this.
** pgrayove at gmail dot com: I'm getting in around noon on Sunday too. I'm interested.
** ranti: And I am.
** tshearerlib: Coming in at around the same time and hope to get to the museum by 1:00. Lunch first?
* Local Option http://localoptionbier.com/ - So you've heard of Hopleaf, you've heard of Maproom. Come to Chicago's *ahem* best kept secret for good food and an evening session on Monday. We will need a tally to make requisite arrangements. Target for arrival at bar: 7ish. Probably a group gathering to head north around 6:30 in hotel lobby (if you want to take the #8 Halsted bus that is).
** kayiwa
** Linda Ballinger
** Courtney Greene
** John Pillans
** +6 from NCSU incl one Bret Davidson
** Megan Kudzia
** Andrew Darby
** erinrwhite
** Will Clarke
** Cody Hanson
** Jesse Brown
** Matt Cordial +1 (my friend and I were already planning a Monday trip here)
** Ray Schwartz
** Eric Larson
** David Cliff
** Ken Irwin
** Dileshni Jayasinghe

== Planned Events ==

===Read/Write Library Field Trip, Monday 2/11===
Field trip to the [http://readwritelibrary.org/ Read/Write Library] 6:30PM-9PM

Drop in whenever during this time.

Come help catalog the Read/Write Library catalog and hack on the library catalog. We will get food or go to a nearby restaurant depending on interest. We will also invite friends from Code for America to hang out and talk civic data. Bring your laptop along if you have one.

Let us know if you are coming so we can figure out food:
* Margaret Heller
* Ranti Junus
* Wayne Schneider
* jrochkind will try to make it
* emily shaw (may be a little late)
* <strike>kenirwin - bailed on acct of pre-conf brain death</strike>
* Andromeda - yes, unless someone gets Aviary reservations
* Chris Clement - may attend
(hey, there are great bars in that neighborhood!)
* wdenton

'''Directions to the library from UIC:'''

''Bus''

Take the #8 Halsted Bus north to Chicago (Bus will say "#8 Halsted/79th North to Broadway/Waveland")
Take the #66 Chicago Bus west to California (Bus will say either "#66 Chicago west to Austin" or "#66 Chicago West to Pulaski." You can take either one because both Austin and Pulaski are further west than we are so both stop at California)
The Chicago bus stops on the west side of California, which is the side of the street we're on. On California, walk a block north to Walton.

''Train + Bus (slightly faster/more reliable, but only by about 5-10 minutes)''

Walk to the UIC/Halsted Blue Line
Take the O'Hare train (toward the Loop) and go all the way through the Loop and back west. Get off at Chicago and use the exit that says "North side of Chicago Ave" (or something similar — I don't remember exactly).
Take the #66 Chicago Bus west to California (Bus will say either "#66 Chicago west to Austin" or "#66 Chicago West to Pulaski." You can take either one because both Austin and Pulaski are further west than we are so both stop at California)
The Chicago bus stops on the west side of California, which is the side of the street we're on. On California, walk a block north to Walton.

=== Newcomer Dinner, Tuesday 2/12 ===

First time at code4lib? Join fellow c4l newbies and veterans for an evening of food, socializing, and stimulating <strike>discussions about</strike> demonstrations of the many uses of <strike>bacon</strike> <strike>dongles</strike> XML.

Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!

'''Plans'''
* When: Tuesday evening (2/12)
* Time: 6 PM (ish) or whenever you can get your group together
* Mastermind (if you have any questions): [mailto:yoosebec@grinnell.edu Becky Yoose]

''Guidelines:''
*Max of '''6''' per group
**Please, no waitlisting
*ID yourselves so we can get a good mix of new people and veterans in each group
**New folks - n
**c4l vets - v
*One leader needed for each location (declare yourself! - '''Vets are highly encouraged to lead the group''')
**Leader duties
***Make reservations if required; otherwise make sure that the restaurant can handle a group of 6 rowdy library tech type folks
***Herd folks from hotel to restaurant (know where you're going!)

'''Restaurants'''

'''Restaurants within .25 miles of the hotel'''

[http://www.athenarestaurantchicago.com/index.php Athena] (Greek)

* Al Cornish - v (leader)
* Carolyn Cole - n
* Dileshni Jayasinghe - v
* Will Clark - n
* Adam Constabaris - v
* Patrick Hogan - n
* '''Capped at 6'''
We will meet in the hotel lobby. Leave at 6:15 PM, reservation for six at the Athena at 6:30 PM. It is a short walk down Halstead.

[http://www.dinerestaurant.com/ Dine] (Contemporary)

<del>[http://www.girlandthegoat.com/ Girl and the Goat] (American) Top Chef fans take note! This is Stephanie Izard's award-winning resto.</del> Totally booked.

[http://littlegoatchicago.com/ Little Goat]

Izard just opened a diner across the street from G&G that is walk-in only. (very good, probably a wait but they also have a bar in the back --wickr)

We'll meet in the lobby of the hotel at 6:30 and walk over. No reservations.

* Mark Matienzo (leader) - v
* Andromeda Yelton - n
* Hillel Arnold (intern) - veteran newbie
* Kelly Lucas (will meet at restaurant) - n
* Chris Clement - n
* Erin Fahey (will meet at restaurant) -n
* Beatrice Pulliam - n
* '''CAPPED AT 7'''

[http://www.haymarketbrewing.com/ Haymarket Pub & Brewery] (Pub food) - Reservations at 6:30pm. Meet in conference hotel lobby at 6:10pm

* Ryan Wick (leader) - v
* Sean Purcell - v
* Dan Fehrenbach - n
* Pierre Nault - n
* Minh-Quang Nguyen - n
* Matt Bernhardt - n
* David Gonzalez - n
* '''Capped at 7'''

[http://www.karynsongreen.com/ Karyn’s on Green] (Vegan)
Completely vegan and close to the conference hotel. We'll meet in the conference hotel at around 6:45 (reservation at 7:00 for 6). Google maps says it is a 5 minute walk.

*Jason Ronallo (leader)- v
*Alicia Cozine - n
*Mark Mounts - v
*Amy Deschenes - n
*Adam Strohm - n
*Jacob Reed - n
* '''Capped at 6'''

[http://niarestaurant.com/nia-restaurant-mediterranean-cuisine/ Nia] (Mediterranean tapas)

[http://www.pegasuschicago.com/index.php Pegasus] (Greek) - reservation at 6:30 for 6. We'll meet in the hotel lobby at 6:15 and walk down.
*Erin White (leader) - v
* Don Mennerich -n
* John MacGillivray
* Santi Thompson - n
* Jan Waterhouse - n
* Nell Taylor - v
*'''Capped at 6'''

[http://www.roditys.com/index.html Roditys] (Greek) -- Reservations made for 6:30pm. Let's meet in the hotel lobby at 6pm and walk over from there. Its ok if you're a bit late to the lobby, we'll wait. If you have any questions email Rosalyn (Rosy) rosalynmetz at gmail dot com

* Rosalyn Metz (leader) - v
* [[User:highermath|Cary Gordon]] - v
* [[User:Jacobandresen|Jacob Andresen]] - n
* Karen Miller - n
* Dre - v
* Mahria Lebow - n
* '''Capped at 6'''

'''Restaurants between .25 miles and .5 miles of the hotel'''

Code4lib Chicago Celery Salt Society - [http://www.alsbeef.com/ Al's Beef]

* Jason Casden (leader) - v - No reservations. We can walk from the hotel at 7.
* Charlie Morris - n
* Cory Lown - v
* Carolina Garcia - n
* Cody Hanson - n
* Ken Varnum - v
* '''Capped at 6'''

[http://avecrestaurant.com/# Avec] (Small plate)
Family-style small plate and tapas. Great Yelp reviews. We'll meet in the conference hotel at 6:00 <strike>6:45</strike> (they don't take reservations, but have stuff to sip on if there's a wait). Less than 10 minute walk from hotel.

* Shaun Ellis (leader) - v
* Jon Stroop - v
* Paula Gray-Overtoom - n
* Emily Zervas - n
* Cynthia Ng - neither
* Sarah Dooley - n
* '''Capped at 6'''

[http://www.babavillage.com/ Baba’s Village] (Indian/Pakistani)

[http://blackbirdrestaurant.com/ Blackbird] (Contemporary)

(Since the reservation is late, does anyone want to meet for drink in the hotel bar beforehand? There's really no place to wait at the restaurant, and there's no nice bar nearby that I can recall. cm)
* Justin Coyne (reserver) - v - Reservation for Blackbird for 6 at 8:30pm (justin at curationexperts.com)
* Matt Cordial - v
* [http://wiki.code4lib.org/index.php/User:Camcclure Christine McClure - n]
* Devin Higgins - n (devinhiggins at gmail)
* Ken Irwin
* Tad Merchant - n (tadoneus @ gmail)
* '''Capped at 6'''

[http://www.carnivalechicago.com/menu Carnivale] (Nuevo Latino)
* Nettie Lagace - n/v - reservation is at 8 pm; let's meet at the hotel bar beforehand and merge with the Blackbird group for a bit. I have a red sweater and purple glasses / nettiel at gmail dot com
* Rebecca Jones - n/v
* Ben Burbridge - n
* Andrea Schurr - n/v
*
* James Staub - n > v
* '''Capped at 6'''

[http://decero.hellotacos.com/ De Cero] (Mexican)

[http://www.dragonflymandarin.com/ Dragonfly] (Chinese, sushi)

[http://giordanos.com/ Giordano's] (Chicago Style Pizza) This place should be able to handle multiple groups...

* Andrew Nagy (leader) - v
* Virginia Schilling - n
* Jane Sandberg - n
* Richard Aroksaar - n
* Jesse Brown - n (jfbrown78 at gmail dot com)
* Bob Haschart -v
* Alicia Morris
* Ayla Stein - n
* Sharona Ginsberg - n
* Andrew Myers - n
* Jim LeFager - n
* Stephen Eisenhauer - n
* hnayak -n
* Xiaoming Wang -n
* Greg Murry -n

[http://www.grangehallburgerbar.com/ Grange Hall Burger Bar] (Local food)

[http://www.idreamoffalafel.com/ I Dream of Falafel] (Mediterranean) -- No reservations -- this is a casual place. Supposed to be an 8 minute walk from the hotel. Let's meet at 6:20pm in the Crowne Plaza lobby. I have chin-length brown hair and probably will be holding a paper scribbled with 'falafel.'

* Emily Lynema (leader) - v
* Christie Peterson - n
* James Stuart - v
* Emily Shaw - n (emilyfshaw at gmail dot com)
* Ian Chan - n (ichan@csusm.edu)
* Zeno Tajoli - n
* '''Capped at 6'''

[http://www.jaipurchicago.com/ Jaipur] (Indian; Reservation made for 6 at 6:30)
-- Let's meet in the crowne plaza lobby @ 6:15; it's supposed to be a 6 minute walk

* Andrew Darby (leader) - v
* Josh Wilson (joshwilsonnc at gmail) - n
* Tim Thompson - n
* Mariela Hristova - n
* ryan hess - n
* Patrick Feeley - n
* '''Capped at 6'''

[http://lasardine.com/ La Sardine] (French)

[http://www.mythaitakumi.com/index.html MyThai Takumi] (Japanese Thai) Reservation at 6:15. Meet in the hotel lobby at 6 pm. Look for the women in a trench coat and hat.

*Becky Yoose (leader) b dot yoose at gmail - v
*May Chan - n
*David Anderson - newby
*Terry Brady - new
* Dave Menninger - n
*Shawn Carraway -n
* '''Capped at 6'''

[http://www.nellcoterestaurant.com/ Nellcôte] (French)

[http://chicago.provincerestaurant.com/ Province] (American with Central/South American/Spanish influence)

[http://thepublicanrestaurant.com/ The Publican] (Seafood)

* Jay Luker (eater) - v - Rezzie is for 8pm
* <del>Mark Matienzo (tweeter) - v</del> started a new newcomer dinner!
* Devon Smith (pickle eater) - repeat offender
* Chris Sharp (dead horse beater) - v
* Michael B. Klein (greeter) - v
* Bill McMillin (meeter) - n
* Tom Johnson
* '''Capped at 6'''

[http://saigonsisters.tumblr.com/ Saigon Sisters] (Vietnamese) Reservation for 6:15, meet in hotel lobby
* Margaret Heller - v and leader
* Sharon Clapp - n
* Meghan Finch - n
* Maccabee Levine - v
* James Griffin - n
* Maura Byrne - n

[http://www.thaiurbankitchen.com/ Thai Urban Kitchen] (Thai, sushi)

[http://www.trattoriaisabellachicago.com/rest.html Trattoria Isabella] (Italian)

[http://www.vivo-chicago.com/homepage-2 Vivo] (Italian)

[http://www.wishbonechicago.com/dining/westloop/ Wishbone] (Southern Reconstruction)

* Rachel Shaevel (herder, self-proclaimed dictator, and reservation maker) - n (we're on for 6:15! Meet by the women's restroom when the sessions are over.)
* Myrna E Morales (follower) - n
* Sarah Thorngate - n
* Steven Marsden - n
* David Lacy - v
* Luke Gaudreau - n
* '''Capped at 6'''

'''Restaurants between .5 miles and .75 miles of the hotel'''

[http://currentsontheriver.com/ Currents on the River] (Eclectic)

[http://n9ne.com/ N9NE Steakhouse] (Steak)

[http://www.verachicago.com/menu Vera Chicago] (Spanish)

'''Restaurants between .75 miles and 1 mile of the hotel'''

[http://www.theberghoff.com/default.aspx The Berghoff] (German)
* Declan Fleming - v (leader) I checked reservations, and for 6 people, the first time open after the conf is 7:30, so I grabbed that.
** Let's meet in the lobby at 7p and walk over!
* Dave Green - n
* Steven Villereal - n
* Peter Murray - v
* Trey Terrell - n
* Mike Giarlo - v
* '''Capped at 6'''

[http://www.yelp.com/biz/frontera-grill-chicago Frontera] (a Rick Bayliss Mex-American restaurant) Reservations are for 7:30, so perhaps the group could get a drink in the lobby beforehand. Either way, we'll depart at 7pm.
: (''note: the drinks at the bar at frontera are very tasty.'')
*Dan Suchy (leader and over-eater) - v
*Matt Critchlow - v
*Carmen Mitchell - v
*Maureen Callahan - n
*David Cliff - n
* Patrick Berry - 3rd year red-shirt freshman
* '''Capped at 6'''

[http://www.nativefoods.com/ Native Foods] (Vegan) lots of vegan, vegetarian, gluten free options. No reservations needed. We could meet near the convention center or Daley library around 6 and take the train together. Lots of places to get drinks afterwards.

I will wait at 5:30 at outside the UIC forum for anyone who wants to meet here. We'll pick up everyone else at Daley library at 6, then walk to the train station together.

*Annie Pho(potential leader) - n
*Lauren Magnuson - n
*Bennett Magnino - n (meeting outside the Daley library sounds good)
*Kelly Thompson - n
*Audrey Altman - n
*Mackenzie Brooks - n
*Steven Bassett - n (Can't wait! Native Foods is awesome!).
* '''Capped at 7''' Unless you can handle more folks!

'''Restaurants more than 1 mile from the hotel'''

[http://www.greenzebrachicago.com/index.html Green Zebra] (Vegan)

[http://honkytonkbbqchicago.com/ Honky Tonk Barbeque] (BBQ) ---- I'm interested in Game Night this evening, so I'll make reservations for early dinner at lunch time (when there's some hope of the HT answering the phone). Please let me know if 6:30 is not OK. Lets leave from the UIC Library (front door) at 6:10. It's a moderate walk (a bit less than a mile) from campus; I also have a car, and can drive a couple people if you want.
*Allan Berry (leader) - n
*Jason Raitz - n (The #60 bus looks like it would save those of us with a bus pass the walk.)
*Brian Wu - n (pwu14 at illinois dot edu)(EDIT: Plans sound good. I am also interested in game night. If somehow we don't make it, I have a 4 player game in my hotel room.)
*Gary Maixner - n
*Keith Nickum -v
*
* '''Capped at 6'''

[http://www.karynraw.com/cooked Karyn’s Cooked] (Vegan)

[http://www.latabernatapas.com/ La Taberna Tapas] (Mediterranean)

[http://www.morganschicago.com/ Morgan's on Maxwell] (Pub food)

[http://www.chezjoelbistro.com/ Chez Joël] (French/Tangiers food) I am leaning towards an early dinner of 6:15 as I have to take-off to make sure the Game Night takes off without a hitch. So leave the conference hotel by 5:45 if it is walk weather or 6PM if it is taxi weather.

* Francis Kayiwa (knackered leader) - v
* Megan O'Neill Kudzia - n
* Esther Verreau - n
* Michael Neidhardt - n
* Rikke Willer - n
* Esme Cowles - v
* '''Capped at 6'''

=== Veg*n Dinner ===

Let's have dinner at a veg*n-friendly place one night of the conference. Folks of all eating styles welcome.

Max *6* people per party this year.

'''Party #1: Chicago Diner''', Wednesday Night http://www.veggiediner.com/ "meat free since '83"
Will they easily be able to accommodate 6 folks walking in?
We'll plan on meeting in the conference hotel at 6pm and taking the 8 bus up there (3411 N. Halsted St Chicago, IL 60657).
# Jason Ronallo (jronallo@gmail.com)
# Linda Ballinger (linda dot ballinger at gmail)
# May Chan (msuicat at gmail dot com)
# Demian Katz (demian DOT katz AT villanova DOT edu)
# David Uspal (david dot uspal at villanova dot edu) In for the Country Fried StAEk and/or the Soul Bowl. Ex-Vegetarian (which may make it a crime for me to go), so if the list is full and you still want in, feel free to email me and I'll gladly turn over my spot to an actual Veg*n.
# Cynthia Ng (cynthia dot s dot ng at gmail)
Capped at 6

=== Code4lib/Goose Island Brewing Pull Request ===
'''When:''' Wednesday, 2/13, 8:00 PM to 11:00 PM

More information and sign up at [https://code4lib2013-estw.eventbrite.com/|https://code4lib2013-estw.eventbrite.com/]

=== Bourbon and barbecue ===
'''When:''' Wednesday, 2/13, 7:00 PM

Friend of mine tells me his cousin manages a Chicago restaurant, Chicago q, and I should go there and tell him my friend sent me. [http://www.chicagoqrestaurant.com/menus/dinner.php Menu] keeps talking about artisanal barbecue and extensive bourbon options. DONE.

Reservation is at 7 for a party of 8. Add yourselves.

We can take the number 20 bus to the Red Line. We should plan to meet in the lobby at 6:10; that way we can work with the bus tracker and make a leisurely trip over.

* Andromeda Yelton
* Chris Day [cday2 at saic.edu]
* Abigail Goben
* Rosalyn Metz [rosalynmetz at gmail dot com]
* Dileshni Jayasinghe [d dot jayasinghe at utoronto dot ca]
* Ray Mathew
* Dre (Barbecue, yes. Bourbon... well, we'll see.) akorphan at ncsu.edu
* Sean Chen schen at law.duke.edu

=== Non-beery get together ===
'''When:''' Wednesday, 2/13, Meet at hotel lobby at around 6:30 (and take public transport over to the park) OR meet us at the rink at 6:45, skating rink closes at 8 PM

'''Where:''' [https://www.cityofchicago.org/city/en/depts/dca/supp_info/ice_skating_at_themccormicktribuneicerink.html McCormick Tribune Ice Rink]

'''Contact:''' @dchud, @ranti, @yo_bj (b dot yoose at gmail), @wendyrlibrarian

'''Cost:''' $10 skate rental, people watching free

Come and (attempt to) skate with us! This is also a good people watching opportunity, so if you don't want to skate, there will be places to hang out around the rink and the park. There is a [http://www.parkgrillchicago.com/cafe/food-menu cafe] near the rink as well, with hot drinks and food.

FYI - For those of you who want something else to munch on while hanging out, there's a [http://www.garrettpopcorn.com/chicago-locations/4-east-madison-street/ Garrett Popcorn Shop] a couple blocks away.

# Chris Sharp (indicating interest)
# Becky Yoose (ready to fall on her butt repeatedly for the entertainment of others)
# Peter Murray
# Shawn Carraway
# Karen Coombs
# Michael Levy
# Christie Peterson
# Andrew Pasterfield
# Virginia Schilling
# Al Cornish
# Sibyl Schaefer
# Kalee Sprague
# Luis Baquera (ready to distract everyone with his own fantastic wipeouts while Becky composes herself)
# Maccabee Levine
# Sarah Shealy (I'm pretty sure I'll fall spectacularly as well :) )
# Emily Lynema (interested!)
# Gabriel Farrell

=== Flying Trapeze ===
'''When:''' Monday, 2/11, TBD

'''Contact:''' rosalynmetz at gmail dot com

'''Class is full.'''

No this is not a joke. If you haven't heard Rosy is an aspiring trapeze artists and wants to bring the fun to her friends in Code4Lib. There is a trapeze rig in Chicago and she plans on visiting it and hopes that some of you can come along as well. If its your first time taking a trapeze class, they'll start you off learning [http://www.youtube.com/watch?v=_oqPi_zuX7A a knee hang] and depending on how that goes you might be able to catch it at the end of class. If you have any questions about whether or not this is for you, [http://chicago.trapezeschool.com/classes/trapeze.php TSNY Chicago's website] should have the answer, if not feel free to contact Rosy.

Trapeze classes are $57, last 2 hours, and are limited to 10 people. Currently TSNY Chicago hasn't release their class schedule for February -- they should be doing that around Jan. 1. If we can get enough people interested before then, we can buy out a whole class. If not it'll be first come, first serve (along with the general public).

If you're interested in signing up, feel free to add your name and contact info to the list below.

'''''Sign Up List'''''
# Jay Luker (first!)
# Bill McMillin
# Bess Sadler
# Karen Coyle
# Sibyl Schaefer
# Rosalyn Metz (because I'm organizing)
# Alicia Cozine
# Gabriel Farrell

=== Game Night! ===

See the http://wiki.code4lib.org/index.php/2013_game_night page for the latest details and to sign up for individual games or add games you're willing to lead/teach!

Moved this from idea to an actual event. Still getting some details, but here's what we know:

Game Night! Type of games might vary due to interest and what people bring. Looks like interest right now is mostly on light to mediumish games with a dash of abstracts ;).

Rough Schedule:
* 7:30 setup
* 7:45 start playing games!
* 10:00 start winding down (don't start new games)
* 10:30 all done, turn off the lights

* I highly recommend that people walk in groups to get back to their respective lodgings. I'll ask folks still around at the end to help me clean up so we can walk back to the conference hotel*

Please bring your badge with. (You don't need to wear it on the way, but that'll help us make sure everyone in the room is supposed to be there.)

We have a conference room at the UIC library (Richard J. Daley Library MC 234, 801 S. Morgan, Chicago) reserved for 7:30 on Tuesday the 11th. I'll try to show up at the lobby and hang out there for at about 7:15. I'll be the guy with a code4lib nametag and a box of games ;). Not sure how late we'll play, it looks like the library is open till 1:00am, but I suspect I will for now put a rough ending time of 11pm.

(Note, there's also some discussion on Cards Against Humanity. I will try to make sure there's an alternative game, but I don't know if I want to prohibit any games. I would say though to remember to be respectful and courteous to those around you. I will probably be pondering this issue for a while)

The original list of people who signed up is below.

I (Jon Gorman) will bring some board games and pick up some cards. Add your name to the list below if you're interested in attending. Also not if you can bring games. Bringing games is NOT REQUIRED. If you can bring a game you can teach, that's great and will make sure we're not just stuck playing the games I bring.

(I've added some comments to the game lists below)
* jtgorman, aka Jon Gorman: I'll bring Time's Up: Total Recall, Tsuro, Hey, That's My Fish, Hive, and some more I haven't decided on yet. (My profile over at http://www.boardgamegeek.com/ is jtgorman as well if you want to browse my games and make requests)
* yo_bj: I have some games I can bring as well (Kill Doctor Lucky, Fluxx, Godzilla: Stomp, Munchkin Zombies, etc.). Monday doesn't have anything major planned...
*danwho: I 'll bring the Cards Against Humanity set.
*escowles (Mon/Tue preferred): I've got lots of games I could bring like Settlers of Catan, Carcassonne, Ticket to Ride, Age of Renaissance, Elfenland, Agricola, Le Havre, Smallworld, RoboRally, etc. etc.
** Take your pick! All good games. I'll try to finalize my list of games before Friday - JonG
*jen_young: I'm local and I have quite a few games. Just about every version of Fluxx, Bananagrams, Gloom, Munchkin Cthulu,Cards Against Humanity, Apples to Apples, Risk, Last Night on Earth, etc.)
**All good games! If you don't mind bringing a box that would be awesome. I particularly like Apples to Apples, Last Night on Earth and Gloom - JonG
* decasm: Interested in Go (aka igo, weiqi, baduk) anytime, not just game night. I can do Catan as well. (And as much as I love it, Cards Against Humanity is probably a violation of the new Code of Conduct.)
** I look forward to losing my first game of Go to you ;) - JonG
** I'd love to learn Go. <del>Perhaps after the newcomer dinner?</del> Oof... won't make for Tues. But would still be interested to learn. --ranti.
* csharp: I'm interested in playing games - whatever people bring. I almost always travel with a pack or two of playing cards ;-). Monday or Tuesday nights are fine.
* moneill: I would love to join in! I have a version of Catchphrase floating around somewhere, and I think I have Battleship...I need to go weed around in that drawer and see what else presents itself. Tuesday would be my preferred night, but I will make it work!
** Don't worry too much about bringing a game if transportation is a problem. One thing I've done w/ stuff like catchphrase is not take the box but to put pieces and cards in a bag - JOn G
* demiankatz: I'm always up for a game. I'm hoping to travel light so probably shouldn't bring anything, but if there's a local game shop, I might be persuaded to pick up something new as a souvenir.
** Don't worry, I think there will be plenty of games - JonG
* sekjal: I've got [http://boardgamegeek.com/boardgame/36218/dominion Dominion], [http://boardgamegeek.com/boardgame/68448/7-wonders 7 Wonders], [http://boardgamegeek.com/boardgame/30933/bang-the-bullet Bang!], [http://boardgamegeek.com/boardgame/18333/ecofluxx EcoFluxx] and [http://boardgamegeek.com/boardgame/116/guillotine Guillotine] that I can bring. ++ on Cards against Humanity! Prefer non-conflict with beer night.
** Also all good games. I have 7 Wonders, but can bring some other games if you bring that. - Jon G
* arty: so totally interested. Unfortunately, I have no games to contribute.
** No prob.
* sanderson: I would be interested. I can bring [http://boardgamegeek.com/boardgame/478/citadels Citadels] (2-7 players)
** Citadels would be awesome and means I don't have to bring it ;) - JonG
* dvdndrsn: Definitely in! Can bring Innovation, Tichu, Dominion, but Cards Against Humanity sounds good.
** I'll put in a vote for Tichu, heard good things about it - Jon G
* smkiewel: I'm likely to join. Can bring Arkham Horror and Munchkin.
** Arkham Horror seems rather bulky to travel with, but if you want to play bring it ;) - Jon G
** mbutler: If someone actually brings Arkham Horror I'd throw down. Otherwise, whateve.
* jkwilson: I'd like to attend Monday or Tuesday. I have a bunch of games but I'd prefer not to travel with them, and anyway it sounds like they're covered above. I'll bring the 5-6 player Catan extension.
* ejlynema: Interested, but will probably attend Newcomer dinner on Tuesday. Like Dominion and 7 Wonders, but probably don't have room to bring in suitcase. Anyone bringing Tsuro?
** I can bring Tsuro - Jon G
* Christie Peterson (save4use): Also interested, but also probably attending newcomer dinner on Tuesday. Can bring [http://boardgamegeek.com/boardgame/11/bohnanza Bohnanza] and one deck of [http://en.wikipedia.org/wiki/Set_%28game%29 Set].
**Bohnanza and Set would be awesome - JonG
**Done! I will bring them both -- C
* dgcliff: I'd be interested. Can bring Ticket to Ride.
* mbklein: definitely interested. Will check on my (currently unpacked) games. I am dying to play Cards Against Humanity. If we can't find a way to reconcile it with the Code of Conduct, we need a different Code of Conduct.
** Considering that this is a public event, and that no one knows everyone's sensitivity levels in the room, it might not be a good idea to break out a crass, adult version of apples to apples in the middle of the gaming room. :cP (yo_bj)
* duspal: In. My board game collection is small but mighty (Arkham Horror, Catan, Vampire: Prince of the City, Deadlands: Battle for Slaughter Gulch, Arabian Nights, Diplomacy, Shogun, and Cosmic Encounter off the top of my head, amongst a few others). Let me know ahead of time if anyone is interested, since they're all relatively big...
** If you really want to play Cosmic Encounter, I can bring my copy (Fantasy Flight edition, 3 expansions), just let me know - JonG
*librarywebchic: I'm willing to bring a set and teach folks how to play Majhong. Need at least three to play though.
**beatricep: Uno gets no respect. ;-) @librarywebchic: I have always wanted to learn to play Majhong. If you're still bringing it, I'm in!
** Agreed, I don't know Majhong and I love learning new games. - JonG
** I actually know a few different rule sets. It's too bad I don't have a travel set or I'd bring a 2nd one -Arty
** I'm local and can bring a mahjong set. I've had no one to play with for years, so have probably forgotten how. -Linda B
* jcraitz: I'm in after the newcomer dinner. I'll bring Citadels and Bang!
**I think someone higher in the list offered to bring citadels, but won't hurt to have two copies just in case one of you don't show ;) - JonG
**Aww no. left my games at the office. Looks like I'll have to jump in someone else's game.
* julia: I'll be the freeloader who showed up and didn't bring any games.
* kenirwin: interested in attending
* sdellis: attending
* ianc: interested in attending, a little rusty but definitely up for a couple rounds of Mahjong, also want to try something new too!
* haschart: Interested in attending, if I can make it work with the newcomer dinner. Big fan of Dominion lately, but probably cannot bring it `cause the "Big Box" with the base game and two expansion sets is bigger than my suitcase. I could bring "Race for the Galaxy" if there's any interest.
* jessebrown: Interested in attending. I can bring Set and Zombie Fluxx.
* terrywbrady: I would like to attend
* dan fehrenbach (dnfehren): I would like to attend, can bring Pandemic if anyone is interested.
* dileshni: interested in attending.
* Corey Harper: definitely interested in attending if space allows.
* saverkamp: interested in attending.
* Emily Shaw: I like games.
* Alan Dyck: I play Carcassonne and Munchkin among others. I see those listed so I'm bringing a game some friends and I have been creating: Wandering Monster.
* Heidi Frank (hf36@nyu.edu) - I love card games like gin/rummy, but am open to anything.
* Sibyl Schaefer - attending, and will bring anything that fits in my carry-on
* cpsarason - I'm up for whatever!

-- *Please, please, please, if you're signing up on this list, also sign up for a paritcular game slot to start out the evening or put your game in: http://wiki.code4lib.org/index.php/2013_game_night
we're having so many people sign up after Jan. 14th we're in risk of overflowing the room. (I should have put in a cap limit, but given how late I realized this, I haven't *

I have to confess, I started trying to organize what games certain people were bringing, but it got confusing fast and I don't want anyone to feel compelled to bring anything or feel bad if they can't make it. So if there is something you're dying to play, let me know and I'll try to bring it if I have it.

== Social Map - Places of Interest==

https://maps.google.com/maps/ms?msid=213549257652679418473.0004ce6c25e6cdeb0319d&msa=0

== Layar: augmented reality Code4Lib view of Chicago ==

There's a "Code4Lib 2013" layer in [http://www.layar.com/ Layar], an augmented reality app that runs on both Android and iOS. You can use it to scan around the city to see two kinds of things: 1) tweets using the #c4l13 or #code4lib hashtag (if the tweets are geolocated so they can be
nailed to a point) and 2) points of interest from the [https://maps.google.com/maps/ms?msid=213549257652679418473.0004ce6c25e6cdeb0319d&msa=0 shared Google Map].

To use it:

* install Layar on your phone
* run it and click to go into Geo Layers mode
* search for "code4lib 2013"
* launch the layer and look around

See Code4Lib people and events overlaid on top of Chicago, in real time! See an alternate view of the city that's all about libraries and coders!

To make your own tweets appear, use the #c4l13 hashtag and make sure the tweet is geolocated. In Twitter's client you need to do this by enabling geolocation in settings and then enabling it for each tweet.

Source code running this: [https://github.com/wdenton/laertes Laertes]. Bill Denton set it up and is very curious to find out if it's useful, so let him know if you try it out.

== Local Events ==
Events Listings
* Chicago Reader http://www.chicagoreader.com/
* The City of Chicago’s Events Guide: http://www.choosechicago.com/
* Metromix Chicago: http://chicago.metromix.com/events
* Timeout Chicago: http://timeoutchicago.com/
* Chicago Studio Club's [http://www.google.com/calendar/embed?title=LIVE%20MUSIC%20in%20Chicagoland%20via%20Chicago%20Studio%20Club!%20&height=1000&wkst=1&hl=en&bgcolor=%2399ff99&src=info%40chicagostudioclub.net&color=%237A367A&ctz=America%2FChicago Live Music Google Calendar]

== Local Food ==
== Local Drinks ==
==Chicago Events Feb 10-14==

=== Sunday February 10===
Theater - [http://www.neofuturists.org/ Too Much Light Makes the Baby Go Blind] "...with its ever-changing "menu," is an attempt to perform 30 plays in 60 minutes. " 7pm.

Theater - [http://www.chicagoreader.com/chicago/chunks/Event?oid=8557720 Chunks] : Funny, Heartbreaking, Gross. 7pm & BYOB!

===Monday February 11===

Music - [http://www.hideoutchicago.com/event/208497-robbie-fulks-michael-miles-chicago/ Robbie Fulks at the Hideout]

[http://fedora4lib.org/ fedora4lib] - 7 pm to whenever

===Tuesday, February 12===

Concert - [http://www.thefatbabies.com/ The Fat Babies] playing at an awesome venue, [http://greenmilljazz.com/ The Green Mill].

[http://fedora4lib.org/ fedora4lib] - 7 pm to whenever

===Wednesday, February 13===
===Thursday, February 14===
Tour of the [http://www.newberry.org/ Newberry Library] -- 3:30 p.m.
This will be a special tour for Code4Lib attendees, so please sign up below if you are interested, as I'll need to give the tour guide an estimate of how many people will come. Details on how to get to the Newberry will follow. Questions? Contact ballingerl at newberry dot org

'''''Directions: '''''
The Newberry is at 60 W Walton St. It could take half an hour to get there from the conference hotel via CTA, so those of you who wish to take public transit as a group can meet me in the hotel lobby by 3:00. We will then go to the UIC-Halsted El stop (5 blocks from hotel), change trains in the Loop, then walk 3-4 blocks to the Newberry. Otherwise, plan on making your preferred way there and meet in the Newberry lobby by 3:30.

'''''Sign Up List'''''
# Michael Doran - doran@uta.edu
# William Denton - wtd@pobox.com
# Wayne Schneider - wschneider@hclib.org
# Matt Cordial - rev3lator [at] gmail.com
# ryan hess - mhess8 [at] depaul.edu
# [[User:ianc|Ian Chan]] ichan@csusm.edu
# Richard Aroksaar - richard_aroksaar@nps.gov
# [name] - [email address]
# Laurie Lee Moses - lmoses [at] colum.edu
# Ray Schwartz - schwartzr2@wpunj.edu

== Music ==

There's a [http://www.rdio.com/people/wdenton/playlists/2229053/Code4Lib_2013_in_Chicago/ Code4Lib 2013 in Chicago] collaborative playlist on Rdio. If you're a subscriber, have a look, and add something you think everyone would like to hear or use as their personal soundtrack while they're hacking and exploring Chicago.

[[Category:Code4Lib2013]]

2013 social activities

2013-02-06T15:27:23Z

Gsf: /* Flying Trapeze */

2013 room ride share

2013-01-22T21:24:42Z

Gsf: /* Roommates */

=== O'hare 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?
|-
| yourname/email|| date/time || yes/no|| yes/no || yes/no || who's the driver?||yes/no||# of people you can take
|-
|}

'''Departures'''
{| border="1" cellpadding="5" class="sortable"
|- style="text-align: left;"
! Name !! Flight Departing !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?
|-
| yourname/email|| date/time || yes/no|| yes/no || yes/no || who's the driver?||yes/no||# of people you can take
|-

|}

=== Midway 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?
|-
| yourname/email|| date/time || yes/no|| yes/no || yes/no || who's the driver?||yes/no||# of people you can take
|-
|}

'''Departures'''
{| border="1" cellpadding="5" class="sortable"
|- style="text-align: left;"
! Name !! Flight Departing !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?
|-
| yourname/email|| date/time || yes/no|| yes/no || yes/no || who's the driver?||yes/no||# of people you can take
|-

|}

=== Roommates ===
==== Looking ====

==== Offering ====

* '''TAKEN''' Monday-Thursday Conference Hotel with [https://github.com/gsf Gabriel Farrell]
* '''TAKEN''' Monday PM - Thursday AM Conference Hotel - Looking for a female roommate to split costs with me. I've booked a room for Monday night checking out Thursday morning. Contact me at ejlynema at ncsu dot edu.

=== Other places to stay ===

====Nearby====

[[Category:Code4Lib2013]]

2013 room ride share

2013-01-21T16:56:26Z

Gsf: /* Offering */

=== O'hare 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?
|-
| yourname/email|| date/time || yes/no|| yes/no || yes/no || who's the driver?||yes/no||# of people you can take
|-
|}

'''Departures'''
{| border="1" cellpadding="5" class="sortable"
|- style="text-align: left;"
! Name !! Flight Departing !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?
|-
| yourname/email|| date/time || yes/no|| yes/no || yes/no || who's the driver?||yes/no||# of people you can take
|-

|}

=== Midway 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?
|-
| yourname/email|| date/time || yes/no|| yes/no || yes/no || who's the driver?||yes/no||# of people you can take
|-
|}

'''Departures'''
{| border="1" cellpadding="5" class="sortable"
|- style="text-align: left;"
! Name !! Flight Departing !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?
|-
| yourname/email|| date/time || yes/no|| yes/no || yes/no || who's the driver?||yes/no||# of people you can take
|-

|}

=== Roommates ===
==== Looking ====

==== Offering ====

Monday-Thursday Conference Hotel with [https://github.com/gsf Gabriel Farrell]

===== Sunday - Thursday Conference Hotel Split (half of $115 + tax a night) =====
* '''TAKEN''' Monday PM - Thursday AM Conference Hotel - Looking for a female roommate to split costs with me. I've booked a room for Monday night checking out Thursday morning. Contact me at ejlynema at ncsu dot edu.

=== Other places to stay ===

*'''Free crash space for one female attendee''', in Lincoln Park neighborhood (i.e., not near conference site, but near mass transit). Caveats include: my apartment is on the 3rd floor, it's a bit on the under-heated side, and I have a cat who is very generous with her fur. Bonuses include: the air mattress is normal-bed high, there are plenty of blankets, and I'm less than a block from the El (okay, maybe that's a caveat too, I'm used to the sound of trains). ''ballingerl at newberry dot org''

====Nearby====

[[Category:Code4Lib2013]]

Code4Lib Journal Recruit New Editors

2012-02-10T06:18:43Z

Gsf: /* Very Brief Application */

[[Category: Code4Lib Journal]]

== Very Brief Application ==

Answer each question with just a few sentences:

1) What is your vision for the Code4Lib Journal? Why are you interested
in it?

2) How can you contribute to the Code4Lib Journal? What do you have to
offer?

Code4Lib Journal Recruit New Editors

2012-02-10T06:10:20Z

Gsf: /* Very Brief Application */

[[Category: Code4Lib Journal]]

== Very Brief Application ==

Answer each question with a few sentences, no more than a paragraph:

1) What is your vision for the Code4Lib Journal? Why are you interested
in it?

2) How can you contribute to the Code4Lib Journal? What do you have to
offer?

Code4Lib Journal Recruit New Editors

2012-02-10T06:09:44Z

Gsf: /* Very Brief Application */

Code4Lib Journal Recruit New Editors

2012-02-10T06:07:43Z

Gsf: /* Very Brief Application */

[[Category: Code4Lib Journal]]

== Very Brief Application ==

Answer each question with a few sentences or no more than a paragraph:

1) What is your vision for the Code4Lib Journal? Why are you interested
in it?

2) How can you contribute to the Code4Lib Journal, what do you have to
offer?

2012 Lightning Talks Signup

2012-02-07T18:27:11Z

Gsf:

'''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 at 10 am on Tuesday, February 7, 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].

'''LIGHTNING TALK SIGNUPS OPEN AT 10 AM PST ON FEBRUARY 7'''

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

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

# Al Cornish / XTF in 300 seconds
# Makoto OKamoto / [http://savemlak.jp/wiki/saveMLAK/en?lang=en&uselang=en saveMLAK] - Aid activities for the Great East Japan Earthquake through collaboration via Wiki
# Andrew Nagy / Vendors Suck
# akorphan - Heat maps... not just for input analysis
# Gabriel Farrell / ElasticSearch
# nettie lagace - identifying and solving interoperability problems through cooperation
#
# adam wead / Blacklight at the Rock Hall
# Kelley McGrath -- FRBR, facets, moving images
# Bohyun Kim -- Web Usability in terms of words
# Simon Spero. - Restriction Classes, Bitches
# Cynthia Ng / Processing & ProcessingJS

=== Wednesday, 4:00-5:00pm [12 slots] ===

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

# Scott Hanrath -- Zotero and SHERPA/RoMEO API mashup
# [[User:DataGazetteer|Peter Murray]] -- Introducing FOSS4LIB.org
# @anarchivist -- something something something
# Mike Durbin -- Edge Cases - Digitizing and delivering undescribed items in EAD
# David Walker -- Basic Learning Tool Interoperability (LTI) Protocol
# Ryuuji Yoshimoto -- Introducing CALIL.JP ,scraping all of OPAC in japan!
# ''Kåre Fiedler Christiansen'' -- ''Chucking all the software components in a library together to present recorded radio and tv''
# Joel Richard -- introducing Macaw metadata collection tool
#Rachel Frick - LOD-LAM Incubator Project
#
#
#

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

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

# David Uspal -- Rapid Deployment Projects
#
# Jeremy Nelson -- Aristotle a Django based Discovery Layer
# Dennis Schafroth - Turbo MARC in YAZ Library
#
#
#
#
#

[[Category:Code4Lib2012]]

C4l2012 rideshare

2012-02-05T19:28:59Z

Gsf: /* Offering */

=== Seattle Tacoma International Airport ===

See also [http://orbiscascade.org/index/c4l-transportation travel advice from the hosts]

'''Arrivals'''
{| border="1" cellpadding="5" class="sortable"
|- style="text-align: left;"
! Name !! Flight Arriving !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?
|-
| yourname/email|| date/time || yes/no|| yes/no || yes/no || who's the driver?||yes/no||# of people you can take
|-
|}

'''Departures'''
{| border="1" cellpadding="5" class="sortable"
|- style="text-align: left;"
! Name !! Flight Departing !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?
|-
| yourname/email|| date/time || yes/no|| yes/no || yes/no || who's the driver?||yes/no||# of people you can take
|-

|}

===Public Transit from the Airport===
Light Rail: The [http://www.soundtransit.org/Schedules/Central-Link-light-rail.xml Central Link Light Rail station] will be located near the northeast corner of the main airport parking garage, directly connecting pedestrians to the airport ticketing concourse and SeaTac's City Center. The light rail offers a 36-minute ride from the airport to Downtown Seattle.

Get off at the Pioneer Square station. The hotel is 7 blocks from the station (0.4 miles) and the walk includes a steep hill, so plan to take a bus, a cab, or be out of breath by the time you get to the hotel. The easiest transit connection is to walk up Third to Marion, and take the #12 up the hill. It's a free ride till 7 p.m. Trolley stops across the street (6th Ave) from the hotel.

Fare: <$3 for light rail

=== Roommates ===
==== Looking ====

==== Offering ====
* <s> [https://twitter.com/#!/skome samk] -- Have 2 double beds at the conference hotel, need only one. Human male, typically easy going.</s>
* <s> [http://therolfeblog.blogspot.com Alex Rolfe] I also have 2 double beds at the conference hotel, for the 5th-8th, and would be happy to have a roommate for all or part of it. Human male, also easygoing. Contact me at arolfe@georgefox.edu.</s>
* <s>[mailto:bobbi_fox@harvard.edu Bobbi Fox] -- Have reservation (Sunday eve. through Thurs .am.) at conference hotel, woman looking for another woman to share</s>
* <s> [mailto:tclarke@muhlenberg.edu Tim Clarke] -- I also have a reservation at the Renaissance Seattle for 2 double beds, only need one. (Sunday 3 p.m. through Friday Noon.) I expect to bring [http://victorybeer.com Victory] and [http://weyerbacher.com/ Weyerbacher] to share, so I'll seem easygoing. Please email [mailto:tclarke@muhlenberg.edu tclarke@muhlenberg.edu].</s>
* [mailto:gsf747@gmail.com Gabriel Farrell] Human male, easy going, extra double bed, conference hotel, tonight (Sunday) through Thursday.

=== Other places to stay ===
[http://www.tripadvisor.com/Hotels-g60878-Seattle_Washington-Hotels.html| TripAdvisor]
Also if anyone has suggestions.

====Nearby====
* [http://www.monaco-seattle.com/ Hotel Monaco] - .2 mi (1101 4th Avenue, Seattle, WA)
* [http://www.greentortoise.net/ Green Tortise Hostel], $28.50 - $32.50/person in shared dorm rooms - .6 mi (105 1/2 Pike St)
* [http://www.executivehotels.net/downtownseattlehotel/s_seattle_accommodation.cgi Executive Hotel Pacific] $99 (Also available a 20% discount with advance purchase - full payment upfront required) - .1 miles (400 Spring St).
** These guys have free wifi if you book the "executive" package, which is $109 (which was the only option available when I looked).
* [http://www.kimptonhotels.com/hotels/factsheets/hotel-vintage-park-seattle/ Hotel Vintage Park], $153 (king) and $143 (queen) with AAA discount. Might have government rates, not sure.

====Bus distance====
* College Inn (bus ride away)

2012 preconference proposals

2012-01-16T16:18:30Z

Gsf: /* Interest in Attending */

=Proposals for 2012 Code4LibCon Preconferences=
Proposals closed Sunday, November 20, 2011, so we can finalize the list and add them to registration! (The deadline for preconference proposals has passed.)

Spaces available: main meeting room (max 275) + 5 breakout rooms (max 30-50).

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

=== Hacking Content ===

What is the future of getting library information and resources into users’ hands at the right time and with appropriate context and relevancy. Learning management systems, library guides, Web-scale discovery systems-plenty of tools to choose from and still we see lots of opportunities for improvement. Let’s pick them apart and brainstorm ideas for projects that could address weaknesses in one or all of these systems. If you’re interested in these issues, challenges and conundrums join us for a day of thinking, dreaming and scheming. All skill sets and backgrounds needed.

Speakers/Facilitators will be:
- Thom Cox - Manager of Library Information Technology Services - Tufts University
- Ken Varnum – Web Systems Manager - University of Michigan Libraries
- Evviva Weinraub – Director, Emerging Technologies and Services - Oregon State University Libraries

Contact: Margaret Mellinger - margaret dot mellinger at oregonstate dot edu

==== Interest in Attending ====

*David Uspal (david DOT uspal AT villanova DOT edu)
*Tammy Allgood Wolf

=== Developing applications using REST web services ===

Been hearing about web services but don’t know where to start to build something? Have you built applications that use read services but are stumped by OAuth, Content Negotiation and HTTP Headers? Come dig in and learn how to build applications that interact with both read and write REST services. We’ll cover the basic principles and practices of REST services and discuss the Atom Publishing Protocol as a REST service and its extensibility. The group will examine and test the CouchDB HTTP API by building a simple list creation tool. You’ll learn how OCLC’s platform web services leverage Atom to expose the data and business processes from OCLC’s library systems. By the end of the session, you’ll know the basic principles of REST services, be able to perform Create, Read, Update and Delete operations via REST and be able to authenticate to REST services via API keys and OAuth.

Come ready to learn and code!

Presenter: Karen Coombs - coombsk at oclc dot org

==== Interest in Attending ====

*Sam Kome
*Ray Schwartz
*Jim Robinson
*David Bucknum
*Jean Rainwater
*Laney McGlohon
*Joshua Gomez
*Wayne Schneider
*Andy Kohler
*Michael North
* Tom Keays (keaysht at lemoyne dot edu)
*Charlie Morris
*Michael Lindsey

==Half Day Morning==

=== Linkfest ===

We've had talks and sessions galore about Linked Data at code4lib in past years. Let's focus on linking. Bring data you want to publish and link to or link from and your ideas about new ways we can push data linking into being part of our regular approach to how we put our libraries' content and services on the web. At the start of the session we'll run a quick poll to see who wants to link to what and how, and we'll pair or group up and get to work from there. May a kajillion links bloom!

If you need an "intro to linked data" we can prep a good list of readings/talks to review before you come. But please come ready to link!

Organizer type person: Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu

==== Interest in Attending ====
*Becky Yoose
*Tom Johnson
*Ed Summers
* bernardo gomez ( bgomez at emory dot edu )
* William Gunn
* Jason Ronallo
* Keri Thompson
* David Lacy
* Corey A Harper
* Matt Phillips (mphillips@law.harvard.edu)
* Declan Fleming

=== What's New in Solr ===

This session will bring folks up to speed on the latest developments in Lucene and Solr. There's always a lot of new capabilities as well as tips and tricks on using Solr in clever and powerful ways.

Presenter: Erik Hatcher - erik . hatcher @ lucidimagination dot com

==== Interest in Attending ====
* "Gabriel Farrell" <gsf24@drexel.edu>
* "Erik Hetzner" <erik.hetzner AT ucop BORK edu>
* "Kevin S. Clarke" <ksclarke@gmail>
* "Michael B. Klein" <mbklein@gmail>
* Demian Katz (demian DOT katz AT villanova DOT edu)
* "Mark Mounts" <mark.mounts@dartmouth.edu>
* Anoop Atre ~ anoop.atre AT mnsu . edu
* David Isaak <david.isaak@kpchr.org>
* John Pillans <jpillan@indiana.edu>
* John Wynstra (john.wynstra@uni.edu)
* mark a. matienzo (mark at matienzo dot oh are gee)

==Half Day Afternoon==

=== Git -r done ===

A session to cover all things Git, everyone's favorite distributed version control system. This session should cover a little bit of the history of Git, how it works, and how it's different than other version controls systems like SVN. Practical application should also be covered, including how to clone existing repos and contribute code back to them, how to host your own repository, and best practices for setting up a distributed network.

Looking for attendees with real-life Git experience to share it, so we can all broaden our understanding of possible use-cases and nifty advanced features.

Coordinator: Ian Walls, ByWater Solutions, @sekjal or ian.walls at bywatersolutions com

Helper: Cary Gordon, Cherry Hill Company, @highermath / cgordon@chillco.com

==== Interest in Attending ====

* Patrick Berry (pberry@csuchico.edu)
* Chris Sharp (csharp@georgialibraries.org)
* Matt Critchlow (mcritchlow@ucsd.edu)
* Peter Murray (Peter.Murray@lyrasis.org)
* Margaret Heller (mheller@dom.edu)
* Kevin S. Clarke (ksclarke@gmail)
* Michael B. Klein (mbklein@gmail)
* Demian Katz (demian DOT katz AT villanova DOT edu)
* Benjamin Shum (bshum@biblio.org)
* Sibyl Schaefer (sschaefer@rockarch.org)
* Tammy Allgood Wolf (tammy.allgood@asu.edu)
* Chad Nelson (cnelson17 AT gsu DOT edu)
* Lisa Kurt (lkurt@unr.edu)
* Matt Phillips (mphillips@law.harvard.edu)
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)
* John Wynstra (john.wynstra@uni.edu)
* Declan Fleming

=== Blacklight ===

This session will be walk-through of the architecture of Blacklight and what we have been improving since the rails 3 upgrade. In addition to the architecture of the software, we will also briefly discuss the architecture of the Blacklight community and what has made it successful so far.

For part of the session we will install Blacklight live and get it up and running. This install demo will include a How-To on basic customizations in Blacklight using a test-driven approach (one of the cornerstones of the Blacklight community).

For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ). We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.

Presenters: Jessie Keck, Stanford University - jkeck at stanford dot edu | Molly Pickral, University of Virginia - mpc3c at virginia dot edu

==== Interest in Attending ====
* bernardo gomez ( bgomez at emory dot edu )
* Mark Mounts <mark.mounts@dartmouth.edu>
* Sibyl Schaefer (sschaefer@rockarch.org)
* John Pillans (jpillan@indiana.edu)
* Mang Sun (mang.dot sun at rice dot edu)
* Emily Lynema (emily_lynema at ncsu dot edu)
* mark a. matienzo (mark at matienzo dot oh are gee)
* Daniel Lovins (daniel dot lovins at nyu dot edu)

=== DACS and EAD Overview ===

This session will look at what DACS (Describing Archives: a Content Standard) is and describe the ten required elements. Then there will be an overview of what EAD is, how it works, and the required elements. The final part will be a practice session on taking a paper finding aid and coding it using DACS and EAD.

Presenter: Doris Munson, Eastern Washington University, dmunson at ewu dot edu
(please feel free to contact me if you are interested in being a co-presenter)

==== Interest in Attending ====
* Francis Kayiwa ( kayiwa@ YouEyeSee dot edu )
* Carmen Mitchell (carmenmitchell at gmail dot com)

=== [[Digging into metadata: context, code, and collaboration]] ===

Working with library/archival metadata is difficult. This preconference will tackle pressing questions and will show some of the intricacies of metadata (including AACR2/MARC) with exercises to demonstrate why inconsistencies exist in the data. What steps can the cataloging & metadata community take to help improve the quality of this data? What tools & techniques could help? Rules have evolved over time leaving dirty legacy data. Systems have impacted--and will continue to impact--data structure & design. How can this data be aggregated and refined for use in a new emerging data environments? What assumptions can safely be made and when do you need to inquire about local practice? We will end with a hack-fest where you can ask questions of experienced catalogers and get help with your metadata related problems. Bring your laptops and data.

Person Herder: Becky Yoose, Grinnell College, yoosebec at grinnell dot edu

Collaborators/Facilitators: Corey Harper, New York University - corey dot harper at nyu dot edu | Shana L. McDanold, University of Pennsylvania -
mcdanold at pobox dot upenn dot edu | Laura Smart, Caltech - laura at library dot caltech dot edu

==== Interest in Attending ====
* Jen Weintraub (jweintraub@library.ucla.edu)
* Peter Green (pmgreen@princeton.edu)
* David Isaak (david.isaak@kpchr.org)
* Alex Rolfe (arolfe@georgefox.edu)
* mark a. matienzo (mark at matienzo dot oh are gee)

=== "Geo" ===
This session will explore, we hope collaboratively, the presentation of objects on maps. There will be a section on workflow, a section on discovering objects via "geobrowse," a section discovery of objects via "geosearch," and an exploration of the discovery and presentation of geo-referenced images (e.g. historic maps). There will be open discussion on other approaches to map-based discovery. Emphasis will be placed on simplicity of workflow and implementation. Technologies include: Atom, Django, Solr, and OpenLayers.

Presenters: Mike Graves, UNC Chapel Hill, gravm at email dot unc dot edu; Tim Shearer, UNC Chapel Hill, tshearer at email dot unc dot edu
(please feel free to contact Tim if you are interested in being a co-presenter)

==== Interest in Attending ====
* "Gabriel Farrell" <gsf24@drexel.edu>
* Anoop Atre ~ anoop.atre AT mnsu . edu
* Chad Nelson (cnelson17 AT gsu DOT edu)
* Jason Casden (jmcasden AT ncsu DOT edu
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)
* Sepehr Mavedati (sepehr DOT mavedati AT utoronto DOT ca)

== Half-day Evening ==

=== Microsoft Campus Visit ===
Join us for a trip across Lake Washington to Microsoft Headquarters. Bus will depart from the conference hotel at 4:15pm on Monday. We will visit the Microsoft Home and the Envisioning Lab. The we'll head over to Microsoft Research for drinks and appetizers, and you'll see some great demos of some cool new (and free!) technologies coming out of MSR. Bus will get back to hotel by 9:00pm, plenty of time to hit a pub. You'll learn about:

1. Layerscape -[http://communities.worldwidetelescope.org/]

2. ChronoZoom - [http://research.microsoft.com/chronozoom/]

3. F# - [http://www.tryfsharp.org]

4. Microsoft Academic Search - [http://academic.research.microsoft.com]

Space is limited, so reserve your seat today Email Alex at the address below.

Coordinator: Alex Wade, Microsoft Research, awade at microsoft dot com

Presenters: Rob Fatland; Christophe Poulain; Michael Zyskowski

==== Interest in Attending ====
* Declan Fleming
* Matt Critchlow
* Tom Keays (keaysht at lemoyne dot edu)
* Jason Ronallo
* mark a. matienzo (mark at matienzo dot oh are gee)
* Mark Mounts <mark.mounts@dartmouth.edu>
* Kyle Banerjee <banerjek@uoregon.edu>
* Evviva Weinraub
* Emily Lynema <emily_lynema at ncsu dot edu>
* Jason Casden <jmcasden AT ncsu DOT edu>
* Daniel Lovins <daniel.lovins@nyu.edu>
* Cynthia Ng
* "Gabriel Farrell" <gsf24@drexel.edu>

[[Category: Code4Lib2012]]

2012 preconference proposals

2012-01-12T01:46:23Z

Gsf: /* Interest in Attending */

=Proposals for 2012 Code4LibCon Preconferences=
Proposals closed Sunday, November 20, 2011, so we can finalize the list and add them to registration! (The deadline for preconference proposals has passed.)

Spaces available: main meeting room (max 275) + 5 breakout rooms (max 30-50).

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

=== Hacking Content ===

What is the future of getting library information and resources into users’ hands at the right time and with appropriate context and relevancy. Learning management systems, library guides, Web-scale discovery systems-plenty of tools to choose from and still we see lots of opportunities for improvement. Let’s pick them apart and brainstorm ideas for projects that could address weaknesses in one or all of these systems. If you’re interested in these issues, challenges and conundrums join us for a day of thinking, dreaming and scheming. All skill sets and backgrounds needed.

Speakers/Facilitators will be:
- Thom Cox - Manager of Library Information Technology Services - Tufts University
- Ken Varnum – Web Systems Manager - University of Michigan Libraries
- Evviva Weinraub – Director, Emerging Technologies and Services - Oregon State University Libraries

Contact: Margaret Mellinger - margaret dot mellinger at oregonstate dot edu

==== Interest in Attending ====

=== Developing applications using REST web services ===

Been hearing about web services but don’t know where to start to build something? Have you built applications that use read services but are stumped by OAuth, Content Negotiation and HTTP Headers? Come dig in and learn how to build applications that interact with both read and write REST services. We’ll cover the basic principles and practices of REST services and discuss the Atom Publishing Protocol as a REST service and its extensibility. The group will examine and test the CouchDB HTTP API by building a simple list creation tool. You’ll learn how OCLC’s platform web services leverage Atom to expose the data and business processes from OCLC’s library systems. By the end of the session, you’ll know the basic principles of REST services, be able to perform Create, Read, Update and Delete operations via REST and be able to authenticate to REST services via API keys and OAuth.

Come ready to learn and code!

Presenter: Karen Coombs - coombsk at oclc dot org

==== Interest in Attending ====

*Sam Kome
*Ray Schwartz
*Jim Robinson

==Half Day Morning==

=== Linkfest ===

We've had talks and sessions galore about Linked Data at code4lib in past years. Let's focus on linking. Bring data you want to publish and link to or link from and your ideas about new ways we can push data linking into being part of our regular approach to how we put our libraries' content and services on the web. At the start of the session we'll run a quick poll to see who wants to link to what and how, and we'll pair or group up and get to work from there. May a kajillion links bloom!

If you need an "intro to linked data" we can prep a good list of readings/talks to review before you come. But please come ready to link!

Organizer type person: Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu

==== Interest in Attending ====
*Becky Yoose
*Tom Johnson
*Ed Summers
* bernardo gomez
* William Gunn

=== What's New in Solr ===

This session will bring folks up to speed on the latest developments in Lucene and Solr. There's always a lot of new capabilities as well as tips and tricks on using Solr in clever and powerful ways.

Presenter: Erik Hatcher - erik . hatcher @ lucidimagination dot com

==== Interest in Attending ====
* "Gabriel Farrell" <gsf24@drexel.edu>

==Half Day Afternoon==

=== Git -r done ===

A session to cover all things Git, everyone's favorite distributed version control system. This session should cover a little bit of the history of Git, how it works, and how it's different than other version controls systems like SVN. Practical application should also be covered, including how to clone existing repos and contribute code back to them, how to host your own repository, and best practices for setting up a distributed network.

Looking for attendees with real-life Git experience to share it, so we can all broaden our understanding of possible use-cases and nifty advanced features.

Coordinator: Ian Walls, ByWater Solutions, @sekjal or ian.walls at bywatersolutions com

Helper: Cary Gordon, Cherry Hill Company, @highermath / cgordon@chillco.com

==== Interest in Attending ====

* Patrick Berry (pberry@csuchico.edu)
* Chris Sharp (csharp@georgialibraries.org)
* Matt Critchlow (mcritchlow@ucsd.edu)

=== Blacklight ===

This session will be walk-through of the architecture of Blacklight and what we have been improving since the rails 3 upgrade. In addition to the architecture of the software, we will also briefly discuss the architecture of the Blacklight community and what has made it successful so far.

For part of the session we will install Blacklight live and get it up and running. This install demo will include a How-To on basic customizations in Blacklight using a test-driven approach (one of the cornerstones of the Blacklight community).

For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ). We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.

Presenters: Jessie Keck, Stanford University - jkeck at stanford dot edu | Molly Pickral, University of Virginia - mpc3c at virginia dot edu

==== Interest in Attending ====
* bernardo gomez

=== DACS and EAD Overview ===

This session will look at what DACS (Describing Archives: a Content Standard) is and describe the ten required elements. Then there will be an overview of what EAD is, how it works, and the required elements. The final part will be a practice session on taking a paper finding aid and coding it using DACS and EAD.

Presenter: Doris Munson, Eastern Washington University, dmunson at ewu dot edu
(please feel free to contact me if you are interested in being a co-presenter)

==== Interest in Attending ====

=== [[Digging into metadata: context, code, and collaboration]] ===

Working with library/archival metadata is difficult. This preconference will tackle pressing questions and will show some of the intricacies of metadata (including AACR2/MARC) with exercises to demonstrate why inconsistencies exist in the data. What steps can the cataloging & metadata community take to help improve the quality of this data? What tools & techniques could help? Rules have evolved over time leaving dirty legacy data. Systems have impacted--and will continue to impact--data structure & design. How can this data be aggregated and refined for use in a new emerging data environments? What assumptions can safely be made and when do you need to inquire about local practice? We will end with a hack-fest where you can ask questions of experienced catalogers and get help with your metadata related problems. Bring your laptops and data.

Person Herder: Becky Yoose, Grinnell College, yoosebec at grinnell dot edu

Collaborators/Facilitators: Corey Harper, New York University - corey dot harper at nyu dot edu | Shana L. McDanold, University of Pennsylvania -
mcdanold at pobox dot upenn dot edu | Laura Smart, Caltech - laura at library dot caltech dot edu

==== Interest in Attending ====

=== "Geo" ===
This session will explore, we hope collaboratively, the presentation of objects on maps. There will be a section on workflow, a section on discovering objects via "geobrowse," a section discovery of objects via "geosearch," and an exploration of the discovery and presentation of geo-referenced images (e.g. historic maps). There will be open discussion on other approaches to map-based discovery. Emphasis will be placed on simplicity of workflow and implementation. Technologies include: Atom, Django, Solr, and OpenLayers.

Presenters: Mike Graves, UNC Chapel Hill, gravm at email dot unc dot edu; Tim Shearer, UNC Chapel Hill, tshearer at email dot unc dot edu
(please feel free to contact Tim if you are interested in being a co-presenter)

==== Interest in Attending ====
* "Gabriel Farrell" <gsf24@drexel.edu>

[[Category: Code4Lib2012]]

2012 preconference proposals

2012-01-12T01:46:03Z

Gsf: /* Interest in Attending */

=Proposals for 2012 Code4LibCon Preconferences=
Proposals closed Sunday, November 20, 2011, so we can finalize the list and add them to registration! (The deadline for preconference proposals has passed.)

Spaces available: main meeting room (max 275) + 5 breakout rooms (max 30-50).

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

=== Hacking Content ===

What is the future of getting library information and resources into users’ hands at the right time and with appropriate context and relevancy. Learning management systems, library guides, Web-scale discovery systems-plenty of tools to choose from and still we see lots of opportunities for improvement. Let’s pick them apart and brainstorm ideas for projects that could address weaknesses in one or all of these systems. If you’re interested in these issues, challenges and conundrums join us for a day of thinking, dreaming and scheming. All skill sets and backgrounds needed.

Speakers/Facilitators will be:
- Thom Cox - Manager of Library Information Technology Services - Tufts University
- Ken Varnum – Web Systems Manager - University of Michigan Libraries
- Evviva Weinraub – Director, Emerging Technologies and Services - Oregon State University Libraries

Contact: Margaret Mellinger - margaret dot mellinger at oregonstate dot edu

==== Interest in Attending ====

=== Developing applications using REST web services ===

Been hearing about web services but don’t know where to start to build something? Have you built applications that use read services but are stumped by OAuth, Content Negotiation and HTTP Headers? Come dig in and learn how to build applications that interact with both read and write REST services. We’ll cover the basic principles and practices of REST services and discuss the Atom Publishing Protocol as a REST service and its extensibility. The group will examine and test the CouchDB HTTP API by building a simple list creation tool. You’ll learn how OCLC’s platform web services leverage Atom to expose the data and business processes from OCLC’s library systems. By the end of the session, you’ll know the basic principles of REST services, be able to perform Create, Read, Update and Delete operations via REST and be able to authenticate to REST services via API keys and OAuth.

Come ready to learn and code!

Presenter: Karen Coombs - coombsk at oclc dot org

==== Interest in Attending ====

*Sam Kome
*Ray Schwartz
*Jim Robinson

==Half Day Morning==

=== Linkfest ===

We've had talks and sessions galore about Linked Data at code4lib in past years. Let's focus on linking. Bring data you want to publish and link to or link from and your ideas about new ways we can push data linking into being part of our regular approach to how we put our libraries' content and services on the web. At the start of the session we'll run a quick poll to see who wants to link to what and how, and we'll pair or group up and get to work from there. May a kajillion links bloom!

If you need an "intro to linked data" we can prep a good list of readings/talks to review before you come. But please come ready to link!

Organizer type person: Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu

==== Interest in Attending ====
*Becky Yoose
*Tom Johnson
*Ed Summers
* bernardo gomez
* William Gunn

=== What's New in Solr ===

This session will bring folks up to speed on the latest developments in Lucene and Solr. There's always a lot of new capabilities as well as tips and tricks on using Solr in clever and powerful ways.

Presenter: Erik Hatcher - erik . hatcher @ lucidimagination dot com

==== Interest in Attending ====
* "Gabriel Farrell" <gsf24@drexel.edu>

==Half Day Afternoon==

=== Git -r done ===

A session to cover all things Git, everyone's favorite distributed version control system. This session should cover a little bit of the history of Git, how it works, and how it's different than other version controls systems like SVN. Practical application should also be covered, including how to clone existing repos and contribute code back to them, how to host your own repository, and best practices for setting up a distributed network.

Looking for attendees with real-life Git experience to share it, so we can all broaden our understanding of possible use-cases and nifty advanced features.

Coordinator: Ian Walls, ByWater Solutions, @sekjal or ian.walls at bywatersolutions com

Helper: Cary Gordon, Cherry Hill Company, @highermath / cgordon@chillco.com

==== Interest in Attending ====

* Patrick Berry (pberry@csuchico.edu)
* Chris Sharp (csharp@georgialibraries.org)
* Matt Critchlow (mcritchlow@ucsd.edu)

=== Blacklight ===

This session will be walk-through of the architecture of Blacklight and what we have been improving since the rails 3 upgrade. In addition to the architecture of the software, we will also briefly discuss the architecture of the Blacklight community and what has made it successful so far.

For part of the session we will install Blacklight live and get it up and running. This install demo will include a How-To on basic customizations in Blacklight using a test-driven approach (one of the cornerstones of the Blacklight community).

For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ). We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.

Presenters: Jessie Keck, Stanford University - jkeck at stanford dot edu | Molly Pickral, University of Virginia - mpc3c at virginia dot edu

==== Interest in Attending ====
* bernardo gomez

=== DACS and EAD Overview ===

This session will look at what DACS (Describing Archives: a Content Standard) is and describe the ten required elements. Then there will be an overview of what EAD is, how it works, and the required elements. The final part will be a practice session on taking a paper finding aid and coding it using DACS and EAD.

Presenter: Doris Munson, Eastern Washington University, dmunson at ewu dot edu
(please feel free to contact me if you are interested in being a co-presenter)

==== Interest in Attending ====

=== [[Digging into metadata: context, code, and collaboration]] ===

Working with library/archival metadata is difficult. This preconference will tackle pressing questions and will show some of the intricacies of metadata (including AACR2/MARC) with exercises to demonstrate why inconsistencies exist in the data. What steps can the cataloging & metadata community take to help improve the quality of this data? What tools & techniques could help? Rules have evolved over time leaving dirty legacy data. Systems have impacted--and will continue to impact--data structure & design. How can this data be aggregated and refined for use in a new emerging data environments? What assumptions can safely be made and when do you need to inquire about local practice? We will end with a hack-fest where you can ask questions of experienced catalogers and get help with your metadata related problems. Bring your laptops and data.

Person Herder: Becky Yoose, Grinnell College, yoosebec at grinnell dot edu

Collaborators/Facilitators: Corey Harper, New York University - corey dot harper at nyu dot edu | Shana L. McDanold, University of Pennsylvania -
mcdanold at pobox dot upenn dot edu | Laura Smart, Caltech - laura at library dot caltech dot edu

==== Interest in Attending ====

=== "Geo" ===
This session will explore, we hope collaboratively, the presentation of objects on maps. There will be a section on workflow, a section on discovering objects via "geobrowse," a section discovery of objects via "geosearch," and an exploration of the discovery and presentation of geo-referenced images (e.g. historic maps). There will be open discussion on other approaches to map-based discovery. Emphasis will be placed on simplicity of workflow and implementation. Technologies include: Atom, Django, Solr, and OpenLayers.

Presenters: Mike Graves, UNC Chapel Hill, gravm at email dot unc dot edu; Tim Shearer, UNC Chapel Hill, tshearer at email dot unc dot edu
(please feel free to contact Tim if you are interested in being a co-presenter)

==== Interest in Attending ====
* Gabriel Farrell (gsf24@drexel.edu)

[[Category: Code4Lib2012]]

2012 preconference proposals

2012-01-12T01:45:08Z

Gsf: /* Interest in Attending */

2012 preconference proposals

2012-01-12T01:43:30Z

Gsf: /* Interest in Attending */

2012 preconference proposals

2012-01-12T01:42:50Z

Gsf: /* Interest in Attending */

Conference Financial History At A Glance

2011-11-09T22:46:20Z

Gsf: Created page

==2011==
Registration cost: $130 + $30 pre-conf

==2010==
Registration cost: $120 + $25 pre-conf

==2009==
Registration cost: $125

==2008==
Registration cost: $125

==2007==
Registration cost: $100

==2006==
Registration cost: $125

Main Page

2011-11-09T22:43:56Z

Gsf: /* Earlier Conferences and events */ Added financial history link

{|align=right
|__TOC__
|}

== About Code4Lib ==

* [[About Code4Lib]] - Background and history of the community
* [[A Guide for the Perplexed]] - Building skills for working with library technologies

== Code4Lib 2012 Conference ==

''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2012 Code4lib2012 category]''

* [[2012_committees_sign-up_page|Volunteer to help plan 2012 conference]]
* [[2012_nominations_list|2012 Keynote speaker suggestions]]
* [[2012_preconference_proposals|2012 Preconference Proposals]]
* [[2012_talks_proposals|2012 Talk Proposals]]
* [[2012_lightning_talks_signup|2012 Lightning Talks Signup]]
* [[ideas_for_2012|Put your ideas for 2012 here!]]
* [http://sites.google.com/site/code4lib2012seattle/ Seattle proposal.]
* [[C4L2012_Call_For_Host|2012 Call For Host]]

== Local / Regional Groups ==

* [[NYC|Code4LibNYC]] - NYC and surrounding areas
* [[NEC4L|New England Code4lib]] - New England
* [http://se.code4lib.org Southeastern Code4lib] - North Carolina, Virginia, Tennessee, etc.
* [[NL|Code4Bib]] - Dutch Code4Bib
* [[MDC|Code4libMDC]] - Maryland, Washington D.C and surrounding areas
* [http://groups.google.com/group/pnwcode4lib?hl=en PNWCode4Lib] - Pacific Northwest
* [[North|code4lib North]] - Ontario and surrounding areas ''(new for Jan 2010!)''
* [[Midwest|Code4Lib Midwest]] - Wherever that is...
* [http://groups.google.com/group/ikr-fejlesztok/ Code4lib.hu] - Group of Hungarian library developers
* [http://www.code4lib.jp/ Code4Lib Japan] - ''(new in 2010!)'', see also [http://twitter.com/yesonline/statuses/28561046501 tweet from Jerry Lee]
* [http://groups.google.com/group/code4glam Code4GLAM Australia] - coders, hackers, developers and technologists in the Australian GLAM (Galleries, Libraries, Archives & Museums) sector.

== Interest Groups ==

* [[ILS_Interop|ILS Interoperability]] - A group working to develop an infrastructure for interoperating between discovery layers and integrated library systems.
* [[Open_Source_Book_Widgets|Open Source Book Widgets]] - A list of open source book widgets
* [[Discovery|Open Source Discovery]] - Open Source application to enhance and support "discovery" in libraries
* [[Mobile_Apps|Mobile Applications]] - A group interested in mobile web and native application development for libraries
* [[Sources_Of_Metadata|Sources Of Metadata]] - list of api's and sources of interest to libraries

== Software Usage and Documentation ==

* [[Umlaut]] - OpenURL link resolving middleware
* [[:Category:Patterns|Patterns for Collaborative Code]] - Patterns to make your open source 'more open', more amenable to distributed development and use at multiple institutions without forking.
* [[ILS Documentation]]
* [[OSS Directory]]
* [[Working with MaRC]]
* [[Rogue]] - principles for standards creation

== Code4Lib Journal ==

* [[:Category:Code4Lib Journal|Code4Lib Journal]] - information and working documents

== Current topics ==

* [[OCLC Policy Change]]
* [[SirsiDynix: Integrated Library System Platforms on Open Source]]
* [[Parsing Library Data]]

== Other Code4Lib Sites ==

* [http://www.code4lib.org/ code4lib.org]
* [http://planet.code4lib.org planet.code4lib.org]

== Earlier Conferences and events ==
[[Conference Financial History At A Glance]]

=== Code4Lib 2011 Conference ===
''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2011 Code4lib2011 category]''

* [http://code4lib.org/conference/2011 C4L2011 Home]
* [[C4L2011_registration | Registration Information!]]
* [[2011_committees_sign-up_page | 2011 Committees Sign-Up]] - '''Volunteer to help'''
* [[How To Plan A Code4LibCon]]
* [[C4L2011_social_activities|Social Activities]] - ideas & sign-up
* [[C4L2011_planning_wishlist|'''Put your ideas for 2011 here!''']]
* [http://www.facebook.com/event.php?eid=161853827200024 Facebook Event Page]
* [http://events.linkedin.com/Code4Lib-2011/pub/448897 LinkedIn Event Page]

* [[C4L2011_rideshare|Airport Ride Share and Carpooling]]
* [[C4L2011_roomshare | Hotel room share]]

=== Code4Lib 2010 Conference ===

''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2010 Code4lib2010 category]''
* [http://code4lib.org/conference/2010/schedule Finalized schedule]
* [[2010 Lightning Talks Signup]] - sign up to give a lightning talk
* [[2010 Breakout Sessions]] - suggest a breakout here
* '''[[2010 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff'''
* [[C4L2010_social_activities|Social Activities]] - ideas & sign-up
* [[Committees sign-up page]] - '''Volunteer to help'''
* [[C4L2011_planning_wishlist|'''Put your ideas for 2011 here!''']]
* [[Asheville Airport to Hotel Van Manifest]]
* [[C4L2010rideshare|General shared travel/transportation planning]]
* [[C4L2010planning:RoommatesRidesEtc|Roommates, Rides, Etc]]
* [[C4L2010_manning_discount|Manning Publications Discount]] - discount code (40% off) for use by attendees through Feb. 28, 2010
* Thanks also to our other sponsors!
* [[C4L2010planning|2010 Planning]]
* [[C4L2010planning:_wishlist | 2010 Planning Wishlist]] - planning page for issues, expectations, etc. for the 2010 conference

=== Code4Lib 2009 Conference ===

* [[BookRaffle]] - coordinate begging publishers for books to raffle off at the conference
* [http://inkdroid.org/c4l2009/attendees Get FOAFed] - add your FOAF profile to the network of c4l2009 attendees
* PreConferences:
** [[GIS_preconf_code4libcon2009]] - Open source GIS just like mom used to make
** [[LinkedData]] - A proposal for a linked-data code4lib2009 pre-conference
** [[LibX_Preconference]] - Proposal for a half-day pre-conference targeted at developers who wish to use the LibX 2.0 platform
** [http://code4lib.org/2009/oclc-precon OCLC Grid Services Preconference]
* [[RoommatesRidesEtc]] - Find roommates for Code4Lib 2009, share rides, etc.
* [[2009 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff

=== Other workshops ===
* [http://barcamp.org/SearchCampDC SearchCampDC] - barcamp style event in DC with usual suspects from code4lib
* [[code4lib/elag2010]] - 1-day code4lib preconference at elag2010

== Archived topics ==

* [[Logo Design Process]]

[[AdminToDo]] - ideas and tasks for maintaining the Code4Lib sites

2012 committees sign-up page

2011-10-31T16:54:28Z

Gsf: /* IRC Evangelists */

= Code4Lib 2012 Committees =

If you are interested in helping out with a particular part of the Code4Lib 2012 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.

== Book Give-Away Committee ==

* Kevin S. Clarke (ksclarke@gmail.com) -- McHenry Library, UC Santa Cruz -- Asking O'Reilly
* Chandos Publishing. Yes.
* Anjanette -- Asking Manning (via Erik Hatcher)
* No Starch. Yes.
* [http://www.seattletechnicalbooks.com Ada's Technical Books]. Woohoo.
* Andrew Nagy -- oXygen XML Editor (5 Licenses to give away)
* [[BookRaffle|Suggestions for Book Raffle.]]

== Sponsorships Committee ==

This committee organizes the sponsorship activities. Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.

* Kyle Banerjee (banerjek@uoregon.edu) -- Orbis Cascade Alliance
* Anjanette Young -- University of Washington
* Mike Giarlo -- Penn State
* [[User:DataGazetteer|Peter Murray]] -- LYRASIS (likely sponsor)
* Andrew Nagy -- Serials Solutions
* Roy Tennant -- OCLC

== Keynote Speakers Committee ==

This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community) and work with the speakers to arrange their travel and arrangements.

* Ann Lally (alally at uw dot edu) University of Washington
* Dre (akorphan at ncsu dot edu) North Carolina State University

== Program Committee ==

This committee plans the structure of the program, arranges the voting on presentations, etc. These folks will also announce speakers, etc.

* Jeremy Frumkin (frumkinj at u dot library dot arizona dot edu) - University of Arizona
* Ranti Junus (ranti.junus at gmail) - Michigan State University
* John Fink (john.fink at gmail) - McMaster University
* Tom Johnson (thomas dot johnson at oregonstate dot edu) - Oregon State University
* [[User:DataGazetteer|Peter Murray]] - LYRASIS

== Scholarships Committee ==

This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.

* Jeremy Frumkin (frumkinj at u dot library dot arizona dot edu) - University of Arizona
* Jodi Schneider - DERI, NUI Galway

== T-Shirt Committee ==

This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes.

* Ann Lally (alally at uw dot edu) University of Washington
* Angie Beiriger (beiriger at reed dot edu) Reed college

== Social Activities Committee ==

The committee plans, proposes, and organizes the evening activities.

* Jennifer Ward (jlward1 at uw dot edu) -- University of Washington
* Jeff Sherwood (jeffs3 at uw dot edu) -- University of Washington

== Voting Activities Committee ==

This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.

== Hospitality Suite Committee ==

This committee makes arrangements for any hospitality suite amenities (technology, snacks, games, icebreakers...) we may want

* Mike Giarlo -- Penn State [Glad to be a keyholder, room-sitter, and general tidier-upper]
* Tom Johnson -- Oregon State University
* Lisa Kurt [lkurt at unr dot edu]-- University of Nevada, Reno
* Carmen Mitchell -- California State University San Marcos

== Welcome Wagon Committee ==

Offers conference newcomers an opportunity to self-identify; offers oldtimers an opportunity to meet newcomers. May also want to constitute a year-round variation for #code4lib.

* Becky Yoose(b.yoose at gmail dot com) -- Grinnell College
* Bohyun Kim(kimb at fiu dot edu) -- Florida International University

== Social Networking ==
Responsible for non-IRC social networking presence.

*Rowena McKernan (rmckernan at whatcom dot ctc dot edu) ~ Whatcom Community College

== IRC Evangelists ==
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.

* Sam Kome (skome) Claremont Colleges
* Gabriel Farrell (gsf) (gsf747@gmail.com) Drexel University

== IRC Access ==
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful.

* Cary Gordon (cgordon at chillco.com) -- The Cherry Hill Company

==Registration Desk Volunteers==
We need 1-2 volunteers to hang out at the registration desk for 2-hour shifts. Also on Monday and Tuesday, an additional volunteer with wireless access knowledge would be helpful on the Registration Desk to answer tech questions.

* Dan Suchy (dansuchy at gmail) -- UC San Diego

== Microphone Runners==

Run wireless handheld microphones to audience members asking questions.

== Session Timer Volunteers ==

People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop with a stopwatch program).

* Ann Gleason (amwhit24 at uw dot edu) - University of Washington
* Carmen Mitchell (carmenmitchell at gmail dot com) - California State University San Marcos

'''Schedule for Session Timers'''

== Raffles ==
(calling awardees)
(backup)
(program)

= Documentation =
To help with documention, no need to sign up, just start editing.
* [[How To Plan A Code4LibCon]]

== Documentation Interest Group ==
Promote ongoing documentation efforts.

[[Category: Code4Lib2012]]

Code4Lib Journal WordPress Input Guidelines

2011-07-01T22:40:09Z

Gsf: /* Proofs for Authors */ point to Administrivia

Please follow the guidelines below when creating or editing Code4Lib Journal articles in WordPress. Enter all articles as "Posts".

==The WP Admin Interface==
To get to WordPress interface for entering an article, choose 'Site Admin' from the footer of any Journal page, login if necessary, and then choose Write//Write Post from the WP admin menus. (Alternatively, go to http://journal.code4lib.org/wp/wp-admin/). If you don't have a WordPress editor login and need one, talk to our web admin (Jon Brinley).

==Proofs for Authors==
A read-only login that is shared with authors can be found in the Administrivia tab.

==Title==
Title, including the subtitle, goes in the "Title" field.

==Article Content==
The body of the article goes in the "Post" field. The top-level header (<code><h1></code>) is used for the title of the post, so start with second-level headers (<code><h2></code>) for sections of the article. Any header from second- to sixth-level may be used as appropriate. Use HTML markup appropriately and semantically, ''e.g.'', <code></code> for emphasized text, <code></code> for strongly emphasized text, <code><blockquote></code> when quoting blocks of text. Avoid such monstrosities as <code></code> and <code><blink></code>.

===Pasting from Word===

If you just paste content from Word into WP, it ends up with REALLY BAD html. Fortunately, WP has a built-in feature to help with this. Open the 'advanced toolbar' in editing GUI (right-most link), then click on the paste-from-word icon. This transforms Word's html into really nice pretty html.

===Images and Attached Content===
In-line images should be no wider than 500px.

The caption for an image should be entered in a p with class="caption":
<nowiki>Figure 1. How to Caption an Image.
</nowiki>
In general, we bold the figure / table label using the strong tag:
<nowiki>Figure 1. How to Caption an Image.
</nowiki>

'''Uploading files manually'''

To upload images or other attached media / files, you will need to upload the content to our ibiblio host site manually.

To do that, sftp to ibiblio.org. See the Administrivia tab in the shared "C4LJ Article Tracking" doc for the username and password.

Change directory to:
/public/vhost/c/c4lj/html/media

in there you'll find an "issue1" subdir (or issueX subdir--if you don't, create one or ask for help creating one!). Inside THERE, create a subdir with the last name of the first author, and put all your image and other attached content in there. It will now have this sort of url:
http://journal.code4lib.org/media/issue1/smith/imagename.png

Add to your img src or a href's as desired. You can use this not just for images, but for extended code attachments, etc.

'''Uploading media via WordPress'''

Before uploading files to WordPress, you will need to change permissions on the directory where you are putting the files.
# Login to c4ljeditor@login.ibiblio.org. Ask jrochkind for the password for the c4ljeditor account (or see this [http://groups.google.com/group/c4lj-articles/msg/fad004416f12ac25 post] on c4lj-articles).
# Change the directory to /public/vhost/c/c4lj/html/wp-content/uploads/
# WordPress tries to write the files to /public/vhost/c/c4lj/html/wp-content/uploads/[current year]/[current month]. If the current year or month directory does not yet exist, create them, "mkdir [current year]" or mkdir "[current month]" in the appropriate directory. Creating the directory while logged in makes the owner and group of the directory c4ljeditor and c4lj respectively. Wordpress will create the directories as nobody/nobody.
# Change the permissions on the [current month] directory from 755 to 777, "chmod 777 [current month]".
# In the WordPress editor, click the "Add an Image" button.
# Browse to and select your image/file.
# Click the Upload button.
# File in the Alternate text and Caption fields.
# Select the size of the image you want to display in the article.
# Click "Insert into Post".
# On the ibiblio.org server, change the permissions on the current month's directory back to 775, "chmod 775 [current month]"

===Code===

Put all code in <code><pre></code> tags.

====Code Highlighting====

If the code is in a supported language, we can do syntax highlighting.

ibiblio has a PHPS extensionm, so if you an "s" on the end of .php files, e.g.,
<filename>.phps
it does syntax highlighting for you.

We're still deciding if we like the syntax highlighting, don't feel compelled to make it work if it's not working for you (but please let other editors know what your experience is). To make this work, you still wrap your code in <code><pre></code> tags. Inside of the <code><pre></code> tags, but around your code, include
[sourcecode language='langcode']...[/sourcecode]

Replace <code>langcode</code> with the appropriate code from the following list (if more than one option for a language, any one will work).

{|
!Language!!Code
|-
|C++||cpp, c, c++
|-
|C#||c#, c-sharp, csharp
|-
|CSS||css
|-
|Delphi||delphi, pascal
|-
|Java||java
|-
|JavaScript||js, jscript, javascript
|-
|PHP||php
|-
|Python||py, python
|-
|Ruby||rb, ruby, rails, ror
|-
|SQL||sql
|-
|VB||vb, vb.net
|-
|XML/HTML||xml, html, xhtml, xslt
|}

Example:
<pre>[sourcecode language='css']body {
font-size: 0.625em;
background-color: #0000ff;
color: #ffff00;
}[/sourcecode]</pre>

====Ampersand Issues====
We've had some problems with ampersand handling in the sourcecode sections. If you notice extra amp;s in your article, such as "&amp;amp;" and "&amp;amp;amp;", and you're comfortable using only the HTML editor for article entry, try checking the "Disable the visual editor when writing" box on your profile page in the admin.

==Abstract==

While you are editing the article, there is a box labeled "Optional Excerpt" a little ways below the "Post" field. Put the abstract here. Use HTML markup as appropriate. What you put in this field is what will be distributed in our syndication feed and what will appear before the article as the abstract.

Assigned editors are ultimately responsible for a good abstract. Authors aren't always the best at writing good abstracts for their articles, you should probably revise or even write a new one from scratch as necessary, even when the author has provided one. Some of the abstracts for my assigned articles haven't even mentioned what I consider the most significant features of the article.

Since indexes (like EBSCO) may end up indexing abstracts and not full text (and even full text indexes may weigh abstracts more highly), the abstract should probably include any important terms that should 'hit' on the article, such as key technologies or concepts.

I've found that extracting sentences or clauses from the article itself is a good way to build an abstract that will represent the article as the authors intended. The conclusion section is often a good place to look for such key sentences/clauses.

Final abstracts should be passed by the authors for approval.

==Bibliographies/Endnotes==
We would like to provide COinS information with every appropriate citation that does not have a publically accessible url.
* Recommended COinS generator: http://generator.ocoins.info/ .
** If using this generator, enter '(COinS)' in the box for COinS Default Text and 'http://journal.code4lib.org/coins' in the box for COinS Default Link at the bottom.
** Paste the output provided at the end of the reference in HTML. You will need to delete the line breaks inserted into the output created by the generator for it to work properly.
* Another option is to use the WP COinS plugin. Open the Code tab, put the cursor before the citation, and click COinS. Enter the appropriate information. This works so-so for journals, and not at all for books.
* COinS should really always have an ISSN or ISBN.
* Inside the span tag, put the string "(COinS)" with a link to our coins explanation page. Ie:

<pre><a href="http://journal.code4lib.org/coins">(COinS)</a></pre>

This is so the user without a browser extension will see that something is there she might be interested in, and get an explanation of COinS and how to make use of it.

===Endnotes style and HTML coding===
* Endnote number in text: The number is the link which appears in square brackets. Square brackets themselves are not part of the link. HTML coding for the text: '''[<a id="ref1" href="#note1">1</a>]'''

* The link should work both ways. So, the endnote will link back to the text. HTML coding for the endnote: '''[<a id="note1" href="#ref1">1</a>]'''

==Author Information==

Start off each article with a paragraph stating the name(s) of the author(s). Something simple like "By Jonathan Rochkind". If desired, the author's name can be a link to something appropriate.

End each article with a second-level header that says "About the Author(s)", with class="abouttheauthor" set. Then give a short paragraph about each author. We do want to have some kind of contact information published (personal web page, email address (obscured if desired), etc.) for each author.

There is a box beneath the article-editing box with the label "Author(s)". Anything you put in this field will be treated as the author of the article. This will show up in the ToC and in the syndication feeds. If you don't populate this field, WordPress will use the username of the editor, instead.

==Categories/Tags==
Posts will have "Uncagetorized" checked by default. Uncheck that box, and check the box next to the current issue, which will be a subcategory of "Issues." Do not check the "Issues" category. We generally do not add tags, except for Conference reviews

==WordPress Buttons==

;Save
:Saves the article, sets the post status to whatever option is selected in the Publish Status form.
;Publish
:Saves the article, sets the post status to Pending Review and assigns a timestamp to the article.

If an issue is not yet published, setting the post status to "Published" or clicking the "Publish" button will set the article to "Pending Review" status. If the issue is already published, this would actually publish the article.

==WordPress Post Status==
An article has four possible statuses. However, only the first three statuses are available to editors.
;Draft
:Use for not yet complete articles. Only editors can see these.
;Pending Review
:Use for sharing the article with authors. Editors and anyone logged in with user ID 17 (i.e., the author account) can see these. See this [http://groups.google.com/group/c4lj-articles/browse_thread/thread/1231b06c09f1289f post] on c4lj-articles for the login information for the author account (username: author).
;Private
:We don't use this option anymore.
;Published
:A published post is visible to everyone. It is part of the RSS feed. If you're editing an already published post, don't select anything in the post status form, just hit Save.

==Publishing an Issue==

# Let everyone on the c4lj-articles list know you are getting ready to publish (so they can save and close any open articles).
# Log in to WordPress
# Make sure that all articles for the issue have the correct issue category selected and have been set to 'Pending Review'. Make sure that the "Uncategorized" and "Issues" categories are unchecked (only the specific issue should be selected).
# Sanity check: count the number of posts which should appear in the publish list
# Click on Posts -> Issues (on the left side)
# Click on "Publish" for the issue you'd like to publish.
## You'll get a list of every "Pending Review" article in that issue. Make sure the number of articles in the list matches your previous count. Don't see all the articles you think you should see? They could be still in Draft status, or not in the correct Issue category, or still have "Uncategorized" selected, or someone may still have it in edit mode. Go back to the posts list and make any necessary changes, and start from #5 again.
# Drag and drop the article titles until they're in the order you want. The order you see there is the order you'll see on the home page (and probably the opposite of the order you'll see in your feed reader).
## Note: It's the coordinating editor's responsibility to decide what order he or she would like the articles to show up in, and order them appropriately when publishing the issue. In general, we try to put the articles with the widest appeal first, and special types (columns, special reports, book reviews, etc.) at the end.
# Click "Publish Issue" (optionally setting the publication time, first). Setting the time should only have an impact on readers who are not logged into the c4lj site. Editors will be able to see the published articles.
# Go to the Journal front page; check the number of articles is correct (again) and that they are in the right order. If there is a problem, go back to the admin interface, click on Posts -> Issues and click Unpublish for the issue. Make whatever corrections are needed and proceed from #5 again.
# Once the issue is finally published, go to [[Code4Lib_Journal_Entries_in_Directory_of_Open_Access_Journals]] and follow the directions to upload the issue metadata to DOAJ.
# Send out announcements (see [[Code4Lib_Journal_Publicity_Venues]])

==Corrections==
See [http://groups.google.com/group/c4lj-articles/browse_thread/thread/8eaabcff2d9c000d/a0aeeb9367fcea5f?lnk=gst&q=errata#a0aeeb9367fcea5f|the editors' list] for how to make corrections. Generally, use an Errata or Correction section at the end with information about the change that was made and have the actual text link down to that section. See also [[Code4Lib_Corrections]]

[[Category:Code4Lib Journal]]

Code4Lib Journal WordPress Input Guidelines

2011-07-01T22:10:17Z

Gsf: /* Images and Attached Content */

Please follow the guidelines below when creating or editing Code4Lib Journal articles in WordPress. Enter all articles as "Posts".

==The WP Admin Interface==
To get to WordPress interface for entering an article, choose 'Site Admin' from the footer of any Journal page, login if necessary, and then choose Write//Write Post from the WP admin menus. (Alternatively, go to http://journal.code4lib.org/wp/wp-admin/). If you don't have a WordPress editor login and need one, talk to our web admin (Jon Brinley).

==Proofs for Authors==
A read-only login that is shared with authors can be found in [http://groups.google.com/group/c4lj-articles/msg/88ffb388fe0419e8?hl=en this message] on the c4lj-articles listserv.

==Title==
Title, including the subtitle, goes in the "Title" field.

==Article Content==
The body of the article goes in the "Post" field. The top-level header (<code><h1></code>) is used for the title of the post, so start with second-level headers (<code><h2></code>) for sections of the article. Any header from second- to sixth-level may be used as appropriate. Use HTML markup appropriately and semantically, ''e.g.'', <code></code> for emphasized text, <code></code> for strongly emphasized text, <code><blockquote></code> when quoting blocks of text. Avoid such monstrosities as <code></code> and <code><blink></code>.

===Pasting from Word===

If you just paste content from Word into WP, it ends up with REALLY BAD html. Fortunately, WP has a built-in feature to help with this. Open the 'advanced toolbar' in editing GUI (right-most link), then click on the paste-from-word icon. This transforms Word's html into really nice pretty html.

===Images and Attached Content===
In-line images should be no wider than 500px.

The caption for an image should be entered in a p with class="caption":
<nowiki>Figure 1. How to Caption an Image.
</nowiki>
In general, we bold the figure / table label using the strong tag:
<nowiki>Figure 1. How to Caption an Image.
</nowiki>

'''Uploading files manually'''

To upload images or other attached media / files, you will need to upload the content to our ibiblio host site manually.

To do that, sftp to ibiblio.org. See the Administrivia tab in the shared "C4LJ Article Tracking" doc for the username and password.

Change directory to:
/public/vhost/c/c4lj/html/media

in there you'll find an "issue1" subdir (or issueX subdir--if you don't, create one or ask for help creating one!). Inside THERE, create a subdir with the last name of the first author, and put all your image and other attached content in there. It will now have this sort of url:
http://journal.code4lib.org/media/issue1/smith/imagename.png

Add to your img src or a href's as desired. You can use this not just for images, but for extended code attachments, etc.

'''Uploading media via WordPress'''

Before uploading files to WordPress, you will need to change permissions on the directory where you are putting the files.
# Login to c4ljeditor@login.ibiblio.org. Ask jrochkind for the password for the c4ljeditor account (or see this [http://groups.google.com/group/c4lj-articles/msg/fad004416f12ac25 post] on c4lj-articles).
# Change the directory to /public/vhost/c/c4lj/html/wp-content/uploads/
# WordPress tries to write the files to /public/vhost/c/c4lj/html/wp-content/uploads/[current year]/[current month]. If the current year or month directory does not yet exist, create them, "mkdir [current year]" or mkdir "[current month]" in the appropriate directory. Creating the directory while logged in makes the owner and group of the directory c4ljeditor and c4lj respectively. Wordpress will create the directories as nobody/nobody.
# Change the permissions on the [current month] directory from 755 to 777, "chmod 777 [current month]".
# In the WordPress editor, click the "Add an Image" button.
# Browse to and select your image/file.
# Click the Upload button.
# File in the Alternate text and Caption fields.
# Select the size of the image you want to display in the article.
# Click "Insert into Post".
# On the ibiblio.org server, change the permissions on the current month's directory back to 775, "chmod 775 [current month]"

===Code===

Put all code in <code><pre></code> tags.

====Code Highlighting====

If the code is in a supported language, we can do syntax highlighting.

ibiblio has a PHPS extensionm, so if you an "s" on the end of .php files, e.g.,
<filename>.phps
it does syntax highlighting for you.

We're still deciding if we like the syntax highlighting, don't feel compelled to make it work if it's not working for you (but please let other editors know what your experience is). To make this work, you still wrap your code in <code><pre></code> tags. Inside of the <code><pre></code> tags, but around your code, include
[sourcecode language='langcode']...[/sourcecode]

Replace <code>langcode</code> with the appropriate code from the following list (if more than one option for a language, any one will work).

{|
!Language!!Code
|-
|C++||cpp, c, c++
|-
|C#||c#, c-sharp, csharp
|-
|CSS||css
|-
|Delphi||delphi, pascal
|-
|Java||java
|-
|JavaScript||js, jscript, javascript
|-
|PHP||php
|-
|Python||py, python
|-
|Ruby||rb, ruby, rails, ror
|-
|SQL||sql
|-
|VB||vb, vb.net
|-
|XML/HTML||xml, html, xhtml, xslt
|}

Example:
<pre>[sourcecode language='css']body {
font-size: 0.625em;
background-color: #0000ff;
color: #ffff00;
}[/sourcecode]</pre>

====Ampersand Issues====
We've had some problems with ampersand handling in the sourcecode sections. If you notice extra amp;s in your article, such as "&amp;amp;" and "&amp;amp;amp;", and you're comfortable using only the HTML editor for article entry, try checking the "Disable the visual editor when writing" box on your profile page in the admin.

==Abstract==

While you are editing the article, there is a box labeled "Optional Excerpt" a little ways below the "Post" field. Put the abstract here. Use HTML markup as appropriate. What you put in this field is what will be distributed in our syndication feed and what will appear before the article as the abstract.

Assigned editors are ultimately responsible for a good abstract. Authors aren't always the best at writing good abstracts for their articles, you should probably revise or even write a new one from scratch as necessary, even when the author has provided one. Some of the abstracts for my assigned articles haven't even mentioned what I consider the most significant features of the article.

Since indexes (like EBSCO) may end up indexing abstracts and not full text (and even full text indexes may weigh abstracts more highly), the abstract should probably include any important terms that should 'hit' on the article, such as key technologies or concepts.

I've found that extracting sentences or clauses from the article itself is a good way to build an abstract that will represent the article as the authors intended. The conclusion section is often a good place to look for such key sentences/clauses.

Final abstracts should be passed by the authors for approval.

==Bibliographies/Endnotes==
We would like to provide COinS information with every appropriate citation that does not have a publically accessible url.
* Recommended COinS generator: http://generator.ocoins.info/ .
** If using this generator, enter '(COinS)' in the box for COinS Default Text and 'http://journal.code4lib.org/coins' in the box for COinS Default Link at the bottom.
** Paste the output provided at the end of the reference in HTML. You will need to delete the line breaks inserted into the output created by the generator for it to work properly.
* Another option is to use the WP COinS plugin. Open the Code tab, put the cursor before the citation, and click COinS. Enter the appropriate information. This works so-so for journals, and not at all for books.
* COinS should really always have an ISSN or ISBN.
* Inside the span tag, put the string "(COinS)" with a link to our coins explanation page. Ie:

<pre><a href="http://journal.code4lib.org/coins">(COinS)</a></pre>

This is so the user without a browser extension will see that something is there she might be interested in, and get an explanation of COinS and how to make use of it.

===Endnotes style and HTML coding===
* Endnote number in text: The number is the link which appears in square brackets. Square brackets themselves are not part of the link. HTML coding for the text: '''[<a id="ref1" href="#note1">1</a>]'''

* The link should work both ways. So, the endnote will link back to the text. HTML coding for the endnote: '''[<a id="note1" href="#ref1">1</a>]'''

==Author Information==

Start off each article with a paragraph stating the name(s) of the author(s). Something simple like "By Jonathan Rochkind". If desired, the author's name can be a link to something appropriate.

End each article with a second-level header that says "About the Author(s)", with class="abouttheauthor" set. Then give a short paragraph about each author. We do want to have some kind of contact information published (personal web page, email address (obscured if desired), etc.) for each author.

There is a box beneath the article-editing box with the label "Author(s)". Anything you put in this field will be treated as the author of the article. This will show up in the ToC and in the syndication feeds. If you don't populate this field, WordPress will use the username of the editor, instead.

==Categories/Tags==
Posts will have "Uncagetorized" checked by default. Uncheck that box, and check the box next to the current issue, which will be a subcategory of "Issues." Do not check the "Issues" category. We generally do not add tags, except for Conference reviews

==WordPress Buttons==

;Save
:Saves the article, sets the post status to whatever option is selected in the Publish Status form.
;Publish
:Saves the article, sets the post status to Pending Review and assigns a timestamp to the article.

If an issue is not yet published, setting the post status to "Published" or clicking the "Publish" button will set the article to "Pending Review" status. If the issue is already published, this would actually publish the article.

==WordPress Post Status==
An article has four possible statuses. However, only the first three statuses are available to editors.
;Draft
:Use for not yet complete articles. Only editors can see these.
;Pending Review
:Use for sharing the article with authors. Editors and anyone logged in with user ID 17 (i.e., the author account) can see these. See this [http://groups.google.com/group/c4lj-articles/browse_thread/thread/1231b06c09f1289f post] on c4lj-articles for the login information for the author account (username: author).
;Private
:We don't use this option anymore.
;Published
:A published post is visible to everyone. It is part of the RSS feed. If you're editing an already published post, don't select anything in the post status form, just hit Save.

==Publishing an Issue==

# Let everyone on the c4lj-articles list know you are getting ready to publish (so they can save and close any open articles).
# Log in to WordPress
# Make sure that all articles for the issue have the correct issue category selected and have been set to 'Pending Review'. Make sure that the "Uncategorized" and "Issues" categories are unchecked (only the specific issue should be selected).
# Sanity check: count the number of posts which should appear in the publish list
# Click on Posts -> Issues (on the left side)
# Click on "Publish" for the issue you'd like to publish.
## You'll get a list of every "Pending Review" article in that issue. Make sure the number of articles in the list matches your previous count. Don't see all the articles you think you should see? They could be still in Draft status, or not in the correct Issue category, or still have "Uncategorized" selected, or someone may still have it in edit mode. Go back to the posts list and make any necessary changes, and start from #5 again.
# Drag and drop the article titles until they're in the order you want. The order you see there is the order you'll see on the home page (and probably the opposite of the order you'll see in your feed reader).
## Note: It's the coordinating editor's responsibility to decide what order he or she would like the articles to show up in, and order them appropriately when publishing the issue. In general, we try to put the articles with the widest appeal first, and special types (columns, special reports, book reviews, etc.) at the end.
# Click "Publish Issue" (optionally setting the publication time, first). Setting the time should only have an impact on readers who are not logged into the c4lj site. Editors will be able to see the published articles.
# Go to the Journal front page; check the number of articles is correct (again) and that they are in the right order. If there is a problem, go back to the admin interface, click on Posts -> Issues and click Unpublish for the issue. Make whatever corrections are needed and proceed from #5 again.
# Once the issue is finally published, go to [[Code4Lib_Journal_Entries_in_Directory_of_Open_Access_Journals]] and follow the directions to upload the issue metadata to DOAJ.
# Send out announcements (see [[Code4Lib_Journal_Publicity_Venues]])

==Corrections==
See [http://groups.google.com/group/c4lj-articles/browse_thread/thread/8eaabcff2d9c000d/a0aeeb9367fcea5f?lnk=gst&q=errata#a0aeeb9367fcea5f|the editors' list] for how to make corrections. Generally, use an Errata or Correction section at the end with information about the change that was made and have the actual text link down to that section. See also [[Code4Lib_Corrections]]

[[Category:Code4Lib Journal]]

Code4Lib Journal WordPress Input Guidelines

2011-07-01T22:05:54Z

Gsf: /* Article Content */ changed pointer for sftp password

Please follow the guidelines below when creating or editing Code4Lib Journal articles in WordPress. Enter all articles as "Posts".

==The WP Admin Interface==
To get to WordPress interface for entering an article, choose 'Site Admin' from the footer of any Journal page, login if necessary, and then choose Write//Write Post from the WP admin menus. (Alternatively, go to http://journal.code4lib.org/wp/wp-admin/). If you don't have a WordPress editor login and need one, talk to our web admin (Jon Brinley).

==Proofs for Authors==
A read-only login that is shared with authors can be found in [http://groups.google.com/group/c4lj-articles/msg/88ffb388fe0419e8?hl=en this message] on the c4lj-articles listserv.

==Title==
Title, including the subtitle, goes in the "Title" field.

==Article Content==
The body of the article goes in the "Post" field. The top-level header (<code><h1></code>) is used for the title of the post, so start with second-level headers (<code><h2></code>) for sections of the article. Any header from second- to sixth-level may be used as appropriate. Use HTML markup appropriately and semantically, ''e.g.'', <code></code> for emphasized text, <code></code> for strongly emphasized text, <code><blockquote></code> when quoting blocks of text. Avoid such monstrosities as <code></code> and <code><blink></code>.

===Pasting from Word===

If you just paste content from Word into WP, it ends up with REALLY BAD html. Fortunately, WP has a built-in feature to help with this. Open the 'advanced toolbar' in editing GUI (right-most link), then click on the paste-from-word icon. This transforms Word's html into really nice pretty html.

===Images and Attached Content===
In-line images should be no wider than 500px.

The caption for an image should be entered in a p with class="caption":
<nowiki>Figure 1. How to Caption an Image.
</nowiki>
In general, we bold the figure / table label using the strong tag:
<nowiki>Figure 1. How to Caption an Image.
</nowiki>

'''Uploading files manually'''

To upload images or other attached media / files, you will need to upload the content to our ibiblio host site manually.

To do that, sftp to c4ljeditor@login.ibiblio.org. See the administrivia tab in the shared "C4LJ Article Tracking" doc for the password.

Change directory to:
/public/vhost/c/c4lj/html/media

in there you'll find an "issue1" subdir (or issueX subdir--if you don't, create one or ask for help creating one!). Inside THERE, create a subdir with the last name of the first author, and put all your image and other attached content in there. It will now have this sort of url:
http://journal.code4lib.org/media/issue1/smith/imagename.png

Add to your img src or a href's as desired. You can use this not just for images, but for extended code attachments, etc.

'''Uploading media via WordPress'''

Before uploading files to WordPress, you will need to change permissions on the directory where you are putting the files.
# Login to c4ljeditor@login.ibiblio.org. Ask jrochkind for the password for the c4ljeditor account (or see this [http://groups.google.com/group/c4lj-articles/msg/fad004416f12ac25 post] on c4lj-articles).
# Change the directory to /public/vhost/c/c4lj/html/wp-content/uploads/
# WordPress tries to write the files to /public/vhost/c/c4lj/html/wp-content/uploads/[current year]/[current month]. If the current year or month directory does not yet exist, create them, "mkdir [current year]" or mkdir "[current month]" in the appropriate directory. Creating the directory while logged in makes the owner and group of the directory c4ljeditor and c4lj respectively. Wordpress will create the directories as nobody/nobody.
# Change the permissions on the [current month] directory from 755 to 777, "chmod 777 [current month]".
# In the WordPress editor, click the "Add an Image" button.
# Browse to and select your image/file.
# Click the Upload button.
# File in the Alternate text and Caption fields.
# Select the size of the image you want to display in the article.
# Click "Insert into Post".
# On the ibiblio.org server, change the permissions on the current month's directory back to 775, "chmod 775 [current month]"

===Code===

Put all code in <code><pre></code> tags.

====Code Highlighting====

If the code is in a supported language, we can do syntax highlighting.

ibiblio has a PHPS extensionm, so if you an "s" on the end of .php files, e.g.,
<filename>.phps
it does syntax highlighting for you.

We're still deciding if we like the syntax highlighting, don't feel compelled to make it work if it's not working for you (but please let other editors know what your experience is). To make this work, you still wrap your code in <code><pre></code> tags. Inside of the <code><pre></code> tags, but around your code, include
[sourcecode language='langcode']...[/sourcecode]

Replace <code>langcode</code> with the appropriate code from the following list (if more than one option for a language, any one will work).

{|
!Language!!Code
|-
|C++||cpp, c, c++
|-
|C#||c#, c-sharp, csharp
|-
|CSS||css
|-
|Delphi||delphi, pascal
|-
|Java||java
|-
|JavaScript||js, jscript, javascript
|-
|PHP||php
|-
|Python||py, python
|-
|Ruby||rb, ruby, rails, ror
|-
|SQL||sql
|-
|VB||vb, vb.net
|-
|XML/HTML||xml, html, xhtml, xslt
|}

Example:
<pre>[sourcecode language='css']body {
font-size: 0.625em;
background-color: #0000ff;
color: #ffff00;
}[/sourcecode]</pre>

====Ampersand Issues====
We've had some problems with ampersand handling in the sourcecode sections. If you notice extra amp;s in your article, such as "&amp;amp;" and "&amp;amp;amp;", and you're comfortable using only the HTML editor for article entry, try checking the "Disable the visual editor when writing" box on your profile page in the admin.

==Abstract==

While you are editing the article, there is a box labeled "Optional Excerpt" a little ways below the "Post" field. Put the abstract here. Use HTML markup as appropriate. What you put in this field is what will be distributed in our syndication feed and what will appear before the article as the abstract.

Assigned editors are ultimately responsible for a good abstract. Authors aren't always the best at writing good abstracts for their articles, you should probably revise or even write a new one from scratch as necessary, even when the author has provided one. Some of the abstracts for my assigned articles haven't even mentioned what I consider the most significant features of the article.

Since indexes (like EBSCO) may end up indexing abstracts and not full text (and even full text indexes may weigh abstracts more highly), the abstract should probably include any important terms that should 'hit' on the article, such as key technologies or concepts.

I've found that extracting sentences or clauses from the article itself is a good way to build an abstract that will represent the article as the authors intended. The conclusion section is often a good place to look for such key sentences/clauses.

Final abstracts should be passed by the authors for approval.

==Bibliographies/Endnotes==
We would like to provide COinS information with every appropriate citation that does not have a publically accessible url.
* Recommended COinS generator: http://generator.ocoins.info/ .
** If using this generator, enter '(COinS)' in the box for COinS Default Text and 'http://journal.code4lib.org/coins' in the box for COinS Default Link at the bottom.
** Paste the output provided at the end of the reference in HTML. You will need to delete the line breaks inserted into the output created by the generator for it to work properly.
* Another option is to use the WP COinS plugin. Open the Code tab, put the cursor before the citation, and click COinS. Enter the appropriate information. This works so-so for journals, and not at all for books.
* COinS should really always have an ISSN or ISBN.
* Inside the span tag, put the string "(COinS)" with a link to our coins explanation page. Ie:

<pre><a href="http://journal.code4lib.org/coins">(COinS)</a></pre>

This is so the user without a browser extension will see that something is there she might be interested in, and get an explanation of COinS and how to make use of it.

===Endnotes style and HTML coding===
* Endnote number in text: The number is the link which appears in square brackets. Square brackets themselves are not part of the link. HTML coding for the text: '''[<a id="ref1" href="#note1">1</a>]'''

* The link should work both ways. So, the endnote will link back to the text. HTML coding for the endnote: '''[<a id="note1" href="#ref1">1</a>]'''

==Author Information==

Start off each article with a paragraph stating the name(s) of the author(s). Something simple like "By Jonathan Rochkind". If desired, the author's name can be a link to something appropriate.

End each article with a second-level header that says "About the Author(s)", with class="abouttheauthor" set. Then give a short paragraph about each author. We do want to have some kind of contact information published (personal web page, email address (obscured if desired), etc.) for each author.

There is a box beneath the article-editing box with the label "Author(s)". Anything you put in this field will be treated as the author of the article. This will show up in the ToC and in the syndication feeds. If you don't populate this field, WordPress will use the username of the editor, instead.

==Categories/Tags==
Posts will have "Uncagetorized" checked by default. Uncheck that box, and check the box next to the current issue, which will be a subcategory of "Issues." Do not check the "Issues" category. We generally do not add tags, except for Conference reviews

==WordPress Buttons==

;Save
:Saves the article, sets the post status to whatever option is selected in the Publish Status form.
;Publish
:Saves the article, sets the post status to Pending Review and assigns a timestamp to the article.

If an issue is not yet published, setting the post status to "Published" or clicking the "Publish" button will set the article to "Pending Review" status. If the issue is already published, this would actually publish the article.

==WordPress Post Status==
An article has four possible statuses. However, only the first three statuses are available to editors.
;Draft
:Use for not yet complete articles. Only editors can see these.
;Pending Review
:Use for sharing the article with authors. Editors and anyone logged in with user ID 17 (i.e., the author account) can see these. See this [http://groups.google.com/group/c4lj-articles/browse_thread/thread/1231b06c09f1289f post] on c4lj-articles for the login information for the author account (username: author).
;Private
:We don't use this option anymore.
;Published
:A published post is visible to everyone. It is part of the RSS feed. If you're editing an already published post, don't select anything in the post status form, just hit Save.

==Publishing an Issue==

# Let everyone on the c4lj-articles list know you are getting ready to publish (so they can save and close any open articles).
# Log in to WordPress
# Make sure that all articles for the issue have the correct issue category selected and have been set to 'Pending Review'. Make sure that the "Uncategorized" and "Issues" categories are unchecked (only the specific issue should be selected).
# Sanity check: count the number of posts which should appear in the publish list
# Click on Posts -> Issues (on the left side)
# Click on "Publish" for the issue you'd like to publish.
## You'll get a list of every "Pending Review" article in that issue. Make sure the number of articles in the list matches your previous count. Don't see all the articles you think you should see? They could be still in Draft status, or not in the correct Issue category, or still have "Uncategorized" selected, or someone may still have it in edit mode. Go back to the posts list and make any necessary changes, and start from #5 again.
# Drag and drop the article titles until they're in the order you want. The order you see there is the order you'll see on the home page (and probably the opposite of the order you'll see in your feed reader).
## Note: It's the coordinating editor's responsibility to decide what order he or she would like the articles to show up in, and order them appropriately when publishing the issue. In general, we try to put the articles with the widest appeal first, and special types (columns, special reports, book reviews, etc.) at the end.
# Click "Publish Issue" (optionally setting the publication time, first). Setting the time should only have an impact on readers who are not logged into the c4lj site. Editors will be able to see the published articles.
# Go to the Journal front page; check the number of articles is correct (again) and that they are in the right order. If there is a problem, go back to the admin interface, click on Posts -> Issues and click Unpublish for the issue. Make whatever corrections are needed and proceed from #5 again.
# Once the issue is finally published, go to [[Code4Lib_Journal_Entries_in_Directory_of_Open_Access_Journals]] and follow the directions to upload the issue metadata to DOAJ.
# Send out announcements (see [[Code4Lib_Journal_Publicity_Venues]])

==Corrections==
See [http://groups.google.com/group/c4lj-articles/browse_thread/thread/8eaabcff2d9c000d/a0aeeb9367fcea5f?lnk=gst&q=errata#a0aeeb9367fcea5f|the editors' list] for how to make corrections. Generally, use an Errata or Correction section at the end with information about the change that was made and have the actual text link down to that section. See also [[Code4Lib_Corrections]]

[[Category:Code4Lib Journal]]

Code4Lib Journal

2011-01-14T15:42:11Z

Gsf:

* [http://journal.code4lib.org/ Code4Lib Journal] (homepage)
* [[Code4Lib Editorial Committee Introduction]]
* [[Code4Lib Journal Deadlines]]
* [[Code4Lib Journal Voting]]
* [[Code4Lib Journal Publicity Venues]]
* [[Code4Lib Style Guide]]
* [[Code4Lib Corrections]]
* [[Code4Lib Contact and Mailing List Setup]]
* [[Code4Lib Journal Email Templates]]
* [[Code4Lib Journal WordPress Input Guidelines]]
** [[COinS (layman's description)]]
* [[Code4Lib Journal WordPress Customizations]]

 

[[Code4Lib Journal Entries in Directory of Open Access Journals]]

[[Code4Lib Journal PDFs]]

[[Category: Code4Lib Journal]]

Code4Lib Journal Email Templates

2010-12-29T17:36:54Z

Gsf: /* Proposal Accepted */

''See also [[Code4Lib_Journal_Deadlines]]''

== Call for proposals ==

Post to the [[Code4Lib Journal Publicity Venues]].

<pre>
Call for Papers (and apologies for cross-posting):

The Code4Lib Journal (C4LJ) exists to foster community and share
information among those interested in the intersection of libraries,
technology, and the future.

We are now accepting proposals for publication in our <nth> issue.
Don't miss out on this opportunity to share your ideas and experiences.
To be included in the <nth> issue, which is scheduled for publication
in mid <Month YYYY>, please submit articles, abstracts, or proposals at
http://journal.code4lib.org/submit-proposal or to journal@code4lib.org
by Friday, <Month DD, YYYY>. When submitting, please include the title
or subject of the proposal in the subject line of the email message.

C4LJ encourages creativity and flexibility, and the editors welcome
submissions across a broad variety of topics that support the mission
of the journal. Possible topics include, but are not limited to:

* Practical applications of library technology (both actual and
hypothetical)
* Technology projects (failed, successful, or proposed), including
how they were done and challenges faced
* Case studies
* Best practices
* Reviews
* Comparisons of third party software or libraries
* Analyses of library metadata for use with technology
* Project management and communication within the library environment
* Assessment and user studies

C4LJ strives to promote professional communication by minimizing the
barriers to publication. While articles should be of a high quality,
they need not follow any formal structure. Writers should aim for the
middle ground between blog posts and articles in traditional refereed
journals. Where appropriate, we encourage authors to submit code
samples, algorithms, and pseudo-code. For more information, visit
C4LJ's Article Guidelines or browse articles from the first <n> issues
published on our website: http://journal.code4lib.org.

Remember, for consideration for the <nth> issue, please send proposals,
abstracts, or draft articles to journal@code4lib.org no later than
Friday, <Month DD, YYYY>.

Send in a submission. Your peers would like to hear what you are doing.

Code4Lib Journal Editorial Committee
</pre>

== Submission Acknowledgement ==

<pre>
Thank you for submitting a proposal to the Code4Lib Journal. We
appreciate your participation in the Code4Lib community. The editors
have received your proposal and should be in touch with you in 2-4
weeks regarding its appropriateness for publication in C4LJ. We will
notify you if we need additional information to make this decision.
Please feel free to contact us at journal@code4lib.org if you have
additional questions.
</pre>

== Need More Information ==

<pre>
Thank you for your interest in publishing in the Code4Lib Journal.
The Journal is primarily focused on technological issues in libraries.
In order to help the editors determine if your proposal is appropriate
for this publication, could you share more details about the intended
audience for the article and how it will address issues surrounding
technology in libraries? Please respond to journal@code4lib.org with
the additional information requested.

You may also contact the editors at journal@code4lib.org if you have
any additional questions. We look forward to hearing from you.
</pre>

== Proposal Accepted ==

See also [[Code4Lib Journal Deadlines]].

<pre>
I'm pleased to tell you that your recent proposal for an article about
<topic/title> has been provisionally accepted to the Code4Lib Journal.
The editorial committee is interested in your proposal, and would like
to see a draft.

<Additional comments about focus we'd like to see in the article or
editorial committee concerns. Sample language: "We're especially
interested in X, and we'd like you to make sure to flesh this out when
you write the article." or "We're interested in this proposal if you
can do X, Y, or Z.">

As a member of the Code4Lib Journal editorial committee, I will be
your contact for this article, and will work with you to get it ready
for publication.

We hope to publish your article in issue <n> of the Journal, which is
scheduled to appear mid <Month YYYY>. The deadline for submission
of a complete draft is Friday, <Month DD, YYYY>, but the sooner you
can get us a draft the better, and the more likely we'll be able to
get your article into issue <n>. Upon receipt of the draft, I will
work with you to address any changes recommended by the Editorial
Committee. More information about our author guidelines may be found
at http://journal.code4lib.org/article-guidelines.

Please note that final drafts must be approved by a vote of the
Editorial Committee before being published.

We also require all authors to agree to US CC-BY licensing for the
articles we publish in the journal. We recommend that any included
code also have some type of code-specific open source license (such as
the GPL).

We look forward to seeing a complete draft and hope to include it in
the Journal. Thank you for submitting to us, and feel free to contact
me directly with any questions.

If you could drop me a line acknowledging receipt of this email, that
would be great.
</pre>

== Proposal Rejected ==

<pre>
We regret to inform you that your recent proposal to the Code4Lib
Journal for an article about <topic/title> has not been accepted for
publication. The Editorial Committee determined that it was not an
appropriate match for the audience, mission, or scope of the Code4Lib
Journal. [optional - comment about why it's not appropriate]

For more information about the mission of the Code4Lib Journal,
please see http://journal.code4lib.org/mission/.

Thanks for considering us, and please do not hesitate to contact the
editors at journal@code4lib.org in the future with a new or revised
proposal.
</pre>

[[Category: Code4Lib Journal]]

Code4Lib Journal Publicity Venues

2010-12-22T05:04:09Z

Gsf: /* Distributing Call for Submissions */

== Distributing Call for Submissions ==

* [http://listserv.syr.edu/archives/autocat.html AUTOCAT] autocat@listserv.syr.edu
* [https://listserv.nd.edu/cgi-bin/wa?A0=CODE4LIB Code4Lib] code4lib@listserv.nd.edu
* [http://listserv.uic.edu/htbin/wa?A0=drupal4lib Drupal4Lib] drupal4lib@listserv.uic.edu
* [http://lists.ala.org/wws/arc/lita-l LITA-L] lita-l@ala.org
* [http://metadatalibrarians.monarchos.com/ Metadatalibrarians] metadatalibrarians@lists.monarchos.com
* [https://listserv.nd.edu/cgi-bin/wa?A0=NGC4LIB NGC4Lib] ngc4lib@listserv.nd.edu
* <s>[http://mail.archive.org/pipermail/ol-lib/ Open Library] ol-lib@archive.org</s>
* [http://lists.sourceforge.net/lists/listinfo/oss4lib-discuss OSS4Lib] oss4lib-discuss@lists.sourceforge.net
* [https://listserv.nd.edu/cgi-bin/wa?A0=Usability4Lib Usability4Lib] usability4lib@listserv.nd.edu,
* [http://lists.webjunction.org/web4lib/ Web4Lib] web4lib@webjunction.org
* <s>[http://lists.webjunction.org/xml4lib/ XML4Lib] xml4lib@webjunction.org</s>

Web Sites

* [http://liswire.com/ LISWire]. Go to the "[http://liswire.com/node/5 Submit a Release]" page and log in on the right side of the page. See [http://groups.google.com/group/c4lj-articles/t/e0b406daa4599c47 c4lj-articles] group for login information.

== Announcing Publication ==

Announce at above mailing lists and the code4lib website.

== Twitter Hashtag ==

Use #c4lj - its use is tracked in Twapper Keeper: http://twapperkeeper.com/hashtag/c4lj

[[Category: Code4Lib Journal]]

Code4Lib Journal Publicity Venues

2010-12-22T04:57:33Z

Gsf: /* Announcing Publication */

== Distributing Call for Submissions ==

* [http://listserv.syr.edu/archives/autocat.html AUTOCAT] autocat@listserv.syr.edu
* [https://listserv.nd.edu/cgi-bin/wa?A0=CODE4LIB Code4Lib] code4lib@listserv.nd.edu
* <s>[http://listserv.uic.edu/htbin/wa?A0=drupal4lib Drupal4Lib] drupal4lib@listserv.uic.edu</s>
* [http://lists.ala.org/wws/arc/lita-l LITA-L] lita-l@ala.org
* [http://metadatalibrarians.monarchos.com/ Metadatalibrarians] metadatalibrarians@lists.monarchos.com
* [https://listserv.nd.edu/cgi-bin/wa?A0=NGC4LIB NGC4Lib] ngc4lib@listserv.nd.edu
* <s>[http://mail.archive.org/pipermail/ol-lib/ Open Library] ol-lib@archive.org</s>
* [http://lists.sourceforge.net/lists/listinfo/oss4lib-discuss OSS4Lib] oss4lib-discuss@lists.sourceforge.net
* [https://listserv.nd.edu/cgi-bin/wa?A0=Usability4Lib Usability4Lib] usability4lib@listserv.nd.edu,
* [http://lists.webjunction.org/web4lib/ Web4Lib] web4lib@webjunction.org
* <s>[http://lists.webjunction.org/xml4lib/ XML4Lib] xml4lib@webjunction.org</s>

Web Sites

* [http://liswire.com/ LISWire]. Go to the "[http://liswire.com/node/5 Submit a Release]" page and log in on the right side of the page. See [http://groups.google.com/group/c4lj-articles/t/e0b406daa4599c47 c4lj-articles] group for login information.

== Announcing Publication ==

Announce at above mailing lists and the code4lib website.

== Twitter Hashtag ==

Use #c4lj - its use is tracked in Twapper Keeper: http://twapperkeeper.com/hashtag/c4lj

[[Category: Code4Lib Journal]]

Code4Lib Journal Publicity Venues

2010-12-22T04:57:07Z

Gsf: /* Announcing Publication */ Dropped list

== Distributing Call for Submissions ==

* [http://listserv.syr.edu/archives/autocat.html AUTOCAT] autocat@listserv.syr.edu
* [https://listserv.nd.edu/cgi-bin/wa?A0=CODE4LIB Code4Lib] code4lib@listserv.nd.edu
* <s>[http://listserv.uic.edu/htbin/wa?A0=drupal4lib Drupal4Lib] drupal4lib@listserv.uic.edu</s>
* [http://lists.ala.org/wws/arc/lita-l LITA-L] lita-l@ala.org
* [http://metadatalibrarians.monarchos.com/ Metadatalibrarians] metadatalibrarians@lists.monarchos.com
* [https://listserv.nd.edu/cgi-bin/wa?A0=NGC4LIB NGC4Lib] ngc4lib@listserv.nd.edu
* <s>[http://mail.archive.org/pipermail/ol-lib/ Open Library] ol-lib@archive.org</s>
* [http://lists.sourceforge.net/lists/listinfo/oss4lib-discuss OSS4Lib] oss4lib-discuss@lists.sourceforge.net
* [https://listserv.nd.edu/cgi-bin/wa?A0=Usability4Lib Usability4Lib] usability4lib@listserv.nd.edu,
* [http://lists.webjunction.org/web4lib/ Web4Lib] web4lib@webjunction.org
* <s>[http://lists.webjunction.org/xml4lib/ XML4Lib] xml4lib@webjunction.org</s>

Web Sites

* [http://liswire.com/ LISWire]. Go to the "[http://liswire.com/node/5 Submit a Release]" page and log in on the right side of the page. See [http://groups.google.com/group/c4lj-articles/t/e0b406daa4599c47 c4lj-articles] group for login information.

== Announcing Publication ==

Announce at above lists and the code4lib website.

== Twitter Hashtag ==

Use #c4lj - its use is tracked in Twapper Keeper: http://twapperkeeper.com/hashtag/c4lj

[[Category: Code4Lib Journal]]

Code4Lib Journal Publicity Venues

2010-12-21T21:36:05Z

Gsf: /* Announcing Publication */

== Distributing Call for Submissions ==

* [http://listserv.syr.edu/archives/autocat.html AUTOCAT] autocat@listserv.syr.edu
* [https://listserv.nd.edu/cgi-bin/wa?A0=CODE4LIB Code4Lib] code4lib@listserv.nd.edu
* <s>[http://listserv.uic.edu/htbin/wa?A0=drupal4lib Drupal4Lib] drupal4lib@listserv.uic.edu</s>
* [http://lists.ala.org/wws/arc/lita-l LITA-L] lita-l@ala.org
* [http://metadatalibrarians.monarchos.com/ Metadatalibrarians] metadatalibrarians@lists.monarchos.com
* [https://listserv.nd.edu/cgi-bin/wa?A0=NGC4LIB NGC4Lib] ngc4lib@listserv.nd.edu
* <s>[http://mail.archive.org/pipermail/ol-lib/ Open Library] ol-lib@archive.org</s>
* [http://lists.sourceforge.net/lists/listinfo/oss4lib-discuss OSS4Lib] oss4lib-discuss@lists.sourceforge.net
* [https://listserv.nd.edu/cgi-bin/wa?A0=Usability4Lib Usability4Lib] usability4lib@listserv.nd.edu,
* [http://lists.webjunction.org/web4lib/ Web4Lib] web4lib@webjunction.org
* <s>[http://lists.webjunction.org/xml4lib/ XML4Lib] xml4lib@webjunction.org</s>

Web Sites

* [http://liswire.com/ LISWire]. Go to the "[http://liswire.com/node/5 Submit a Release]" page and log in on the right side of the page. See [http://groups.google.com/group/c4lj-articles/t/e0b406daa4599c47 c4lj-articles] group for login information.

== Announcing Publication ==

Lists, blogs, etc., where issue 7 was publicized:

#Autocat (Chris)
#code4lib (Tom)
#<s>drupal4lib (Tom)</s>
#LISWire (Chris)
#lita-l (Chris)
#Metadatalibrarians (Chris)
#ngc4lib (Tom)
#<s>ol-lib (Tom)</s>
#oss4lib (Tom)
#usability4lib (Tom)
#web4lib (Tom)
#<s>xml4lib (Tom)</s>

Still to do:

#code4lib website (?)

== Twitter Hashtag ==

Use #c4lj - its use is tracked in Twapper Keeper: http://twapperkeeper.com/hashtag/c4lj

[[Category: Code4Lib Journal]]

Code4Lib Journal Publicity Venues

2010-12-21T21:34:09Z

Gsf:

== Distributing Call for Submissions ==

* [http://listserv.syr.edu/archives/autocat.html AUTOCAT] autocat@listserv.syr.edu
* [https://listserv.nd.edu/cgi-bin/wa?A0=CODE4LIB Code4Lib] code4lib@listserv.nd.edu
* <s>[http://listserv.uic.edu/htbin/wa?A0=drupal4lib Drupal4Lib] drupal4lib@listserv.uic.edu</s>
* [http://lists.ala.org/wws/arc/lita-l LITA-L] lita-l@ala.org
* [http://metadatalibrarians.monarchos.com/ Metadatalibrarians] metadatalibrarians@lists.monarchos.com
* [https://listserv.nd.edu/cgi-bin/wa?A0=NGC4LIB NGC4Lib] ngc4lib@listserv.nd.edu
* <s>[http://mail.archive.org/pipermail/ol-lib/ Open Library] ol-lib@archive.org</s>
* [http://lists.sourceforge.net/lists/listinfo/oss4lib-discuss OSS4Lib] oss4lib-discuss@lists.sourceforge.net
* [https://listserv.nd.edu/cgi-bin/wa?A0=Usability4Lib Usability4Lib] usability4lib@listserv.nd.edu,
* [http://lists.webjunction.org/web4lib/ Web4Lib] web4lib@webjunction.org
* <s>[http://lists.webjunction.org/xml4lib/ XML4Lib] xml4lib@webjunction.org</s>

Web Sites

* [http://liswire.com/ LISWire]. Go to the "[http://liswire.com/node/5 Submit a Release]" page and log in on the right side of the page. See [http://groups.google.com/group/c4lj-articles/t/e0b406daa4599c47 c4lj-articles] group for login information.

== Announcing Publication ==

Lists, blogs, etc., where issue 7 was publicized:

#Autocat (Chris)
#code4lib (Tom)
#drupal4lib (Tom)
#LISWire (Chris)
#lita-l (Chris)
#Metadatalibrarians (Chris)
#ngc4lib (Tom)
#<s>ol-lib (Tom)</s>
#oss4lib (Tom)
#usability4lib (Tom)
#web4lib (Tom)
#xml4lib (Tom)

Still to do:

#code4lib website (?)

== Twitter Hashtag ==

Use #c4lj - its use is tracked in Twapper Keeper: http://twapperkeeper.com/hashtag/c4lj

[[Category: Code4Lib Journal]]

Code4Lib Journal Email Templates

2010-12-21T16:31:29Z

Gsf: /* Need More Information */

''See also [[Code4Lib_Journal_Deadlines]]''

== Call for proposals ==

Post to the [[Code4Lib Journal Publicity Venues]].

<pre>
Call for Papers (and apologies for cross-posting):

The Code4Lib Journal (C4LJ) exists to foster community and share
information among those interested in the intersection of libraries,
technology, and the future.

We are now accepting proposals for publication in our <nth> issue.
Don't miss out on this opportunity to share your ideas and experiences.
To be included in the <nth> issue, which is scheduled for publication
in mid <Month YYYY>, please submit articles, abstracts, or proposals at
http://journal.code4lib.org/submit-proposal or to journal@code4lib.org
by Friday, <Month DD, YYYY>. When submitting, please include the title
or subject of the proposal in the subject line of the email message.

C4LJ encourages creativity and flexibility, and the editors welcome
submissions across a broad variety of topics that support the mission
of the journal. Possible topics include, but are not limited to:

* Practical applications of library technology (both actual and
hypothetical)
* Technology projects (failed, successful, or proposed), including
how they were done and challenges faced
* Case studies
* Best practices
* Reviews
* Comparisons of third party software or libraries
* Analyses of library metadata for use with technology
* Project management and communication within the library environment
* Assessment and user studies

C4LJ strives to promote professional communication by minimizing the
barriers to publication. While articles should be of a high quality,
they need not follow any formal structure. Writers should aim for the
middle ground between blog posts and articles in traditional refereed
journals. Where appropriate, we encourage authors to submit code
samples, algorithms, and pseudo-code. For more information, visit
C4LJ's Article Guidelines or browse articles from the first <n> issues
published on our website: http://journal.code4lib.org.

Remember, for consideration for the <nth> issue, please send proposals,
abstracts, or draft articles to journal@code4lib.org no later than
Friday, <Month DD, YYYY>.

Send in a submission. Your peers would like to hear what you are doing.

Code4Lib Journal Editorial Committee
</pre>

== Submission Acknowledgement ==

<pre>
Thank you for submitting a proposal to the Code4Lib Journal. We
appreciate your participation in the Code4Lib community. The editors
have received your proposal and should be in touch with you in 2-4
weeks regarding its appropriateness for publication in C4LJ. We will
notify you if we need additional information to make this decision.
Please feel free to contact us at journal@code4lib.org if you have
additional questions.
</pre>

== Need More Information ==

<pre>
Thank you for your interest in publishing in the Code4Lib Journal.
The Journal is primarily focused on technological issues in libraries.
In order to help the editors determine if your proposal is appropriate
for this publication, could you share more details about the intended
audience for the article and how it will address issues surrounding
technology in libraries? Please respond to journal@code4lib.org with
the additional information requested.

You may also contact the editors at journal@code4lib.org if you have
any additional questions. We look forward to hearing from you.
</pre>

== Proposal Accepted ==

See also [[Code4Lib Journal Deadlines]].

<pre>
I'm pleased to tell you that your recent proposal for an article about
<topic/title> has been provisionally accepted to the Code4Lib Journal.
The editorial committee is interested in your proposal, and would like
to see a draft.

<Additional comments about focus we'd like to see in the article or
editorial committee concerns. Sample language: "We're especially
interested in X, and we'd like you to make sure to flesh this out when
you write the article." or "We're interested in this proposal if you
can do X, Y, or Z.">

As a member of the Code4Lib Journal editorial committee, I will be
your contact for this article, and will work with you to get it ready
for publication.

We hope to publish your article in issue <n> of the Journal, which is
scheduled to appear mid <Month YYYY>. The deadline for submission
of a complete draft is <Friday, Month DD, YYYY>, but the sooner you
can get us a draft the better, and the more likely we'll be able to
get your article into issue <n>. Upon receipt of the draft, I will
work with you to address any changes recommended by the Editorial
Committee. More information about our author guidelines may be found
at http://journal.code4lib.org/article-guidelines.

Please note that final drafts must be approved by a vote of the
Editorial Committee before being published.

We also require all authors to agree to US CC-BY licensing for the
articles we publish in the journal. We recommend that any included
code also have some type of code-specific open source license (such as
the GPL).

We look forward to seeing a complete draft and hope to include it in
the Journal. Thank you for submitting to us, and feel free to contact
me directly with any questions.

If you could drop me a line acknowledging receipt of this email, that
would be great.
</pre>

== Proposal Rejected ==

<pre>
We regret to inform you that your recent proposal to the Code4Lib
Journal for an article about <topic/title> has not been accepted for
publication. The Editorial Committee determined that it was not an
appropriate match for the audience, mission, or scope of the Code4Lib
Journal. [optional - comment about why it's not appropriate]

For more information about the mission of the Code4Lib Journal,
please see http://journal.code4lib.org/mission/.

Thanks for considering us, and please do not hesitate to contact the
editors at journal@code4lib.org in the future with a new or revised
proposal.
</pre>

[[Category: Code4Lib Journal]]

Code4Lib Journal WordPress Input Guidelines

2010-12-20T23:56:35Z

Gsf: /* Ampersand Issues */

Please follow the guidelines below when creating or editing Code4Lib Journal articles in WordPress. Enter all articles as "Posts".

==The WP Admin Interface==
To get to WordPress interface for entering an article, choose 'Site Admin' from the footer of any Journal page, login if necessary, and then choose Write//Write Post from the WP admin menus. (Alternatively, go to http://journal.code4lib.org/wp/wp-admin/). If you don't have a WordPress editor login and need one, talk to our web admin (Jon Brinley).

==Proofs for Authors==
A read-only login that is shared with authors can be found in [http://groups.google.com/group/c4lj-articles/msg/88ffb388fe0419e8?hl=en this message] on the c4lj-articles listserv.

==Title==
Title, including the subtitle, goes in the "Title" field.

==Article Content==
The body of the article goes in the "Post" field. The top-level header (<code><h1></code>) is used for the title of the post, so start with second-level headers (<code><h2></code>) for sections of the article. Any header from second- to sixth-level may be used as appropriate. Use HTML markup appropriately and semantically, ''e.g.'', <code></code> for emphasized text, <code></code> for strongly emphasized text, <code><blockquote></code> when quoting blocks of text. Avoid such monstrosities as <code></code> and <code><blink></code>.

===Pasting from Word===

If you just paste content from Word into WP, it ends up with REALLY BAD html. Fortunately, WP has a built-in feature to help with this. Open the 'advanced toolbar' in editing GUI (right-most link), then click on the paste-from-word icon. This transforms Word's html into really nice pretty html.

===Images and Attached Content===
In-line images should be no wider than 500px.

The caption for an image should be entered in a p with class="caption":
<nowiki>Figure 1. How to Caption an Image.
</nowiki>
In general, we bold the figure / table label using the strong tag:
<nowiki>Figure 1. How to Caption an Image.
</nowiki>

'''Uploading files manually'''

To upload images or other attached media / files, you will need to upload the content to our ibiblio host site manually.

To do that, sftp to c4ljeditor@login.ibiblio.org. Ask jrochkind for the password for the c4ljeditor account (or see this [http://groups.google.com/group/c4lj-articles/msg/fad004416f12ac25 post] on c4lj-articles).

Change directory to:
/public/vhost/c/c4lj/html/media

in there you'll find an "issue1" subdir (or issueX subdir--if you don't, create one or ask for help creating one!). Inside THERE, create a subdir with the last name of the first author, and put all your image and other attached content in there. It will now have this sort of url:
http://journal.code4lib.org/media/issue1/smith/imagename.png

Add to your img src or a href's as desired. You can use this not just for images, but for extended code attachments, etc.

'''Uploading media via WordPress'''

Before uploading files to WordPress, you will need to change permissions on the directory where you are putting the files.
# Login to c4ljeditor@login.ibiblio.org. Ask jrochkind for the password for the c4ljeditor account (or see this [http://groups.google.com/group/c4lj-articles/msg/fad004416f12ac25 post] on c4lj-articles).
# Change the directory to /public/vhost/c/c4lj/html/wp-content/uploads/
# WordPress tries to write the files to /public/vhost/c/c4lj/html/wp-content/uploads/[current year]/[current month]. If the current year or month directory does not yet exist, create them, "mkdir [current year]" or mkdir "[current month]" in the appropriate directory. Creating the directory while logged in makes the owner and group of the directory c4ljeditor and c4lj respectively. Wordpress will create the directories as nobody/nobody.
# Change the permissions on the [current month] directory from 755 to 777, "chmod 777 [current month]".
# In the WordPress editor, click the "Add an Image" button.
# Browse to and select your image/file.
# Click the Upload button.
# File in the Alternate text and Caption fields.
# Select the size of the image you want to display in the article.
# Click "Insert into Post".
# On the ibiblio.org server, change the permissions on the current month's directory back to 775, "chmod 775 [current month]"

===Code===

Put all code in <code><pre></code> tags.

====Code Highlighting====

If the code is in a supported language, we can do syntax highlighting.

ibiblio has a PHPS extensionm, so if you an "s" on the end of .php files, e.g.,
<filename>.phps
it does syntax highlighting for you.

We're still deciding if we like the syntax highlighting, don't feel compelled to make it work if it's not working for you (but please let other editors know what your experience is). To make this work, you still wrap your code in <code><pre></code> tags. Inside of the <code><pre></code> tags, but around your code, include
[sourcecode language='langcode']...[/sourcecode]

Replace <code>langcode</code> with the appropriate code from the following list (if more than one option for a language, any one will work).

{|
!Language!!Code
|-
|C++||cpp, c, c++
|-
|C#||c#, c-sharp, csharp
|-
|CSS||css
|-
|Delphi||delphi, pascal
|-
|Java||java
|-
|JavaScript||js, jscript, javascript
|-
|PHP||php
|-
|Python||py, python
|-
|Ruby||rb, ruby, rails, ror
|-
|SQL||sql
|-
|VB||vb, vb.net
|-
|XML/HTML||xml, html, xhtml, xslt
|}

Example:
<pre>[sourcecode language='css']body {
font-size: 0.625em;
background-color: #0000ff;
color: #ffff00;
}[/sourcecode]</pre>

====Ampersand Issues====
We've had some problems with ampersand handling in the sourcecode sections. If you notice extra amp;s in your article, such as "&amp;amp;" and "&amp;amp;amp;", and you're comfortable using only the HTML editor for article entry, try checking the "Disable the visual editor when writing" box on your profile page in the admin.

==Abstract==

While you are editing the article, there is a box labeled "Optional Excerpt" a little ways below the "Post" field. Put the abstract here. Use HTML markup as appropriate. What you put in this field is what will be distributed in our syndication feed and what will appear before the article as the abstract.

Assigned editors are ultimately responsible for a good abstract. Authors aren't always the best at writing good abstracts for their articles, you should probably revise or even write a new one from scratch as necessary, even when the author has provided one. Some of the abstracts for my assigned articles haven't even mentioned what I consider the most significant features of the article.

Since indexes (like EBSCO) may end up indexing abstracts and not full text (and even full text indexes may weigh abstracts more highly), the abstract should probably include any important terms that should 'hit' on the article, such as key technologies or concepts.

I've found that extracting sentences or clauses from the article itself is a good way to build an abstract that will represent the article as the authors intended. The conclusion section is often a good place to look for such key sentences/clauses.

Final abstracts should be passed by the authors for approval.

==Bibliographies/Endnotes==
We would like to provide COinS information with every appropriate citation that does not have a publically accessible url.
* Recommended COinS generator: http://generator.ocoins.info/ .
** If using this generator, enter '(COinS)' in the box for COinS Default Text and 'http://journal.code4lib.org/coins' in the box for COinS Default Link at the bottom.
** Paste the output provided at the end of the reference in HTML. You will need to delete the line breaks inserted into the output created by the generator for it to work properly.
* Another option is to use the WP COinS plugin. Open the Code tab, put the cursor before the citation, and click COinS. Enter the appropriate information. This works so-so for journals, and not at all for books.
* COinS should really always have an ISSN or ISBN.
* Inside the span tag, put the string "(COinS)" with a link to our coins explanation page. Ie:

<pre><a href="http://journal.code4lib.org/coins">(COinS)</a></pre>

This is so the user without a browser extension will see that something is there she might be interested in, and get an explanation of COinS and how to make use of it.

===Endnotes style and HTML coding===
* Endnote number in text: The number is the link which appears in square brackets. Square brackets themselves are not part of the link. HTML coding for the text: '''[<a id="ref1" href="#note1">1</a>]'''

* The link should work both ways. So, the endnote will link back to the text. HTML coding for the endnote: '''[<a id="note1" href="#ref1">1</a>]'''

==Author Information==

Start off each article with a paragraph stating the name(s) of the author(s). Something simple like "By Jonathan Rochkind". If desired, the author's name can be a link to something appropriate.

End each article with a second-level header that says "About the Author(s)", with class="abouttheauthor" set. Then give a short paragraph about each author. We do want to have some kind of contact information published (personal web page, email address (obscured if desired), etc.) for each author.

There is a box beneath the article-editing box with the label "Author(s)". Anything you put in this field will be treated as the author of the article. This will show up in the ToC and in the syndication feeds. If you don't populate this field, WordPress will use the username of the editor, instead.

==Categories/Tags==
Posts will have "Uncagetorized" checked by default. Uncheck that box, and check the box next to the current issue, which will be a subcategory of "Issues." Do not check the "Issues" category. We generally do not add tags, except for Conference reviews

==WordPress Buttons==

;Save
:Saves the article, sets the post status to whatever option is selected in the Publish Status form.
;Publish
:Saves the article, sets the post status to Pending Review and assigns a timestamp to the article.

If an issue is not yet published, setting the post status to "Published" or clicking the "Publish" button will set the article to "Pending Review" status. If the issue is already published, this would actually publish the article.

==WordPress Post Status==
An article has four possible statuses. However, only the first three statuses are available to editors.
;Draft
:Use for not yet complete articles. Only editors can see these.
;Pending Review
:Use for sharing the article with authors. Editors and anyone logged in with user ID 17 (i.e., the author account) can see these. See this [http://groups.google.com/group/c4lj-articles/browse_thread/thread/1231b06c09f1289f post] on c4lj-articles for the login information for the author account (username: author).
;Private
:We don't use this option anymore.
;Published
:A published post is visible to everyone. It is part of the RSS feed. If you're editing an already published post, don't select anything in the post status form, just hit Save.

==Publishing an Issue==

# Let everyone on the c4lj-articles list know you are getting ready to publish (so they can save and close any open articles).
# Log in to WordPress
# Make sure that all articles for the issue have the correct issue category selected and have been set to 'Pending Review'. Make sure that the "Uncategorized" and "Issues" categories are unchecked (only the specific issue should be selected).
# Sanity check: count the number of posts which should appear in the publish list
# Click on Posts -> Issues (on the left side)
# Click on "Publish" for the issue you'd like to publish.
## You'll get a list of every "Pending Review" article in that issue. Make sure the number of articles in the list matches your previous count. Don't see all the articles you think you should see? They could be still in Draft status, or not in the correct Issue category, or still have "Uncategorized" selected, or someone may still have it in edit mode. Go back to the posts list and make any necessary changes, and start from #5 again.
# Drag and drop the article titles until they're in the order you want. The order you see there is the order you'll see on the home page (and probably the opposite of the order you'll see in your feed reader).
## Note: It's the coordinating editor's responsibility to decide what order he or she would like the articles to show up in, and order them appropriately when publishing the issue. In general, we try to put the articles with the widest appeal first, and special types (columns, special reports, book reviews, etc.) at the end.
# Click "Publish Issue" (optionally setting the publication time, first). Setting the time should only have an impact on readers who are not logged into the c4lj site. Editors will be able to see the published articles.
# Go to the Journal front page; check the number of articles is correct (again) and that they are in the right order. If there is a problem, go back to the admin interface, click on Posts -> Issues and click Unpublish for the issue. Make whatever corrections are needed and proceed from #5 again.
# Once the issue is finally published, go to [[Code4Lib_Journal_Entries_in_Directory_of_Open_Access_Journals]] and follow the directions to upload the issue metadata to DOAJ.
# Send out announcements (see [[Code4Lib_Journal_Publicity_Venues]])

==Corrections==
See [http://groups.google.com/group/c4lj-articles/browse_thread/thread/8eaabcff2d9c000d/a0aeeb9367fcea5f?lnk=gst&q=errata#a0aeeb9367fcea5f|the editors' list] for how to make corrections. Generally, use an Errata or Correction section at the end with information about the change that was made and have the actual text link down to that section. See also [[Code4Lib_Corrections]]

[[Category:Code4Lib Journal]]

Code4Lib Journal WordPress Input Guidelines

2010-12-20T23:55:55Z

Gsf: /* Article Content */ ampersands

Please follow the guidelines below when creating or editing Code4Lib Journal articles in WordPress. Enter all articles as "Posts".

==The WP Admin Interface==
To get to WordPress interface for entering an article, choose 'Site Admin' from the footer of any Journal page, login if necessary, and then choose Write//Write Post from the WP admin menus. (Alternatively, go to http://journal.code4lib.org/wp/wp-admin/). If you don't have a WordPress editor login and need one, talk to our web admin (Jon Brinley).

==Proofs for Authors==
A read-only login that is shared with authors can be found in [http://groups.google.com/group/c4lj-articles/msg/88ffb388fe0419e8?hl=en this message] on the c4lj-articles listserv.

==Title==
Title, including the subtitle, goes in the "Title" field.

==Article Content==
The body of the article goes in the "Post" field. The top-level header (<code><h1></code>) is used for the title of the post, so start with second-level headers (<code><h2></code>) for sections of the article. Any header from second- to sixth-level may be used as appropriate. Use HTML markup appropriately and semantically, ''e.g.'', <code></code> for emphasized text, <code></code> for strongly emphasized text, <code><blockquote></code> when quoting blocks of text. Avoid such monstrosities as <code></code> and <code><blink></code>.

===Pasting from Word===

If you just paste content from Word into WP, it ends up with REALLY BAD html. Fortunately, WP has a built-in feature to help with this. Open the 'advanced toolbar' in editing GUI (right-most link), then click on the paste-from-word icon. This transforms Word's html into really nice pretty html.

===Images and Attached Content===
In-line images should be no wider than 500px.

The caption for an image should be entered in a p with class="caption":
<nowiki>Figure 1. How to Caption an Image.
</nowiki>
In general, we bold the figure / table label using the strong tag:
<nowiki>Figure 1. How to Caption an Image.
</nowiki>

'''Uploading files manually'''

To upload images or other attached media / files, you will need to upload the content to our ibiblio host site manually.

To do that, sftp to c4ljeditor@login.ibiblio.org. Ask jrochkind for the password for the c4ljeditor account (or see this [http://groups.google.com/group/c4lj-articles/msg/fad004416f12ac25 post] on c4lj-articles).

Change directory to:
/public/vhost/c/c4lj/html/media

in there you'll find an "issue1" subdir (or issueX subdir--if you don't, create one or ask for help creating one!). Inside THERE, create a subdir with the last name of the first author, and put all your image and other attached content in there. It will now have this sort of url:
http://journal.code4lib.org/media/issue1/smith/imagename.png

Add to your img src or a href's as desired. You can use this not just for images, but for extended code attachments, etc.

'''Uploading media via WordPress'''

Before uploading files to WordPress, you will need to change permissions on the directory where you are putting the files.
# Login to c4ljeditor@login.ibiblio.org. Ask jrochkind for the password for the c4ljeditor account (or see this [http://groups.google.com/group/c4lj-articles/msg/fad004416f12ac25 post] on c4lj-articles).
# Change the directory to /public/vhost/c/c4lj/html/wp-content/uploads/
# WordPress tries to write the files to /public/vhost/c/c4lj/html/wp-content/uploads/[current year]/[current month]. If the current year or month directory does not yet exist, create them, "mkdir [current year]" or mkdir "[current month]" in the appropriate directory. Creating the directory while logged in makes the owner and group of the directory c4ljeditor and c4lj respectively. Wordpress will create the directories as nobody/nobody.
# Change the permissions on the [current month] directory from 755 to 777, "chmod 777 [current month]".
# In the WordPress editor, click the "Add an Image" button.
# Browse to and select your image/file.
# Click the Upload button.
# File in the Alternate text and Caption fields.
# Select the size of the image you want to display in the article.
# Click "Insert into Post".
# On the ibiblio.org server, change the permissions on the current month's directory back to 775, "chmod 775 [current month]"

===Code===

Put all code in <code><pre></code> tags.

====Code Highlighting====

If the code is in a supported language, we can do syntax highlighting.

ibiblio has a PHPS extensionm, so if you an "s" on the end of .php files, e.g.,
<filename>.phps
it does syntax highlighting for you.

We're still deciding if we like the syntax highlighting, don't feel compelled to make it work if it's not working for you (but please let other editors know what your experience is). To make this work, you still wrap your code in <code><pre></code> tags. Inside of the <code><pre></code> tags, but around your code, include
[sourcecode language='langcode']...[/sourcecode]

Replace <code>langcode</code> with the appropriate code from the following list (if more than one option for a language, any one will work).

{|
!Language!!Code
|-
|C++||cpp, c, c++
|-
|C#||c#, c-sharp, csharp
|-
|CSS||css
|-
|Delphi||delphi, pascal
|-
|Java||java
|-
|JavaScript||js, jscript, javascript
|-
|PHP||php
|-
|Python||py, python
|-
|Ruby||rb, ruby, rails, ror
|-
|SQL||sql
|-
|VB||vb, vb.net
|-
|XML/HTML||xml, html, xhtml, xslt
|}

Example:
<pre>[sourcecode language='css']body {
font-size: 0.625em;
background-color: #0000ff;
color: #ffff00;
}[/sourcecode]</pre>

====Ampersand Issues====
We've had some problems with ampersand handling in the sourcecode sections. If you notice extra amp;s in your article, such as "&amp;" and "&amp;amp;", and you're comfortable using only the HTML editor for article entry, try checking the "Disable the visual editor when writing" box on your profile page in the admin.

==Abstract==

While you are editing the article, there is a box labeled "Optional Excerpt" a little ways below the "Post" field. Put the abstract here. Use HTML markup as appropriate. What you put in this field is what will be distributed in our syndication feed and what will appear before the article as the abstract.

Assigned editors are ultimately responsible for a good abstract. Authors aren't always the best at writing good abstracts for their articles, you should probably revise or even write a new one from scratch as necessary, even when the author has provided one. Some of the abstracts for my assigned articles haven't even mentioned what I consider the most significant features of the article.

Since indexes (like EBSCO) may end up indexing abstracts and not full text (and even full text indexes may weigh abstracts more highly), the abstract should probably include any important terms that should 'hit' on the article, such as key technologies or concepts.

I've found that extracting sentences or clauses from the article itself is a good way to build an abstract that will represent the article as the authors intended. The conclusion section is often a good place to look for such key sentences/clauses.

Final abstracts should be passed by the authors for approval.

==Bibliographies/Endnotes==
We would like to provide COinS information with every appropriate citation that does not have a publically accessible url.
* Recommended COinS generator: http://generator.ocoins.info/ .
** If using this generator, enter '(COinS)' in the box for COinS Default Text and 'http://journal.code4lib.org/coins' in the box for COinS Default Link at the bottom.
** Paste the output provided at the end of the reference in HTML. You will need to delete the line breaks inserted into the output created by the generator for it to work properly.
* Another option is to use the WP COinS plugin. Open the Code tab, put the cursor before the citation, and click COinS. Enter the appropriate information. This works so-so for journals, and not at all for books.
* COinS should really always have an ISSN or ISBN.
* Inside the span tag, put the string "(COinS)" with a link to our coins explanation page. Ie:

<pre><a href="http://journal.code4lib.org/coins">(COinS)</a></pre>

This is so the user without a browser extension will see that something is there she might be interested in, and get an explanation of COinS and how to make use of it.

===Endnotes style and HTML coding===
* Endnote number in text: The number is the link which appears in square brackets. Square brackets themselves are not part of the link. HTML coding for the text: '''[<a id="ref1" href="#note1">1</a>]'''

* The link should work both ways. So, the endnote will link back to the text. HTML coding for the endnote: '''[<a id="note1" href="#ref1">1</a>]'''

==Author Information==

Start off each article with a paragraph stating the name(s) of the author(s). Something simple like "By Jonathan Rochkind". If desired, the author's name can be a link to something appropriate.

End each article with a second-level header that says "About the Author(s)", with class="abouttheauthor" set. Then give a short paragraph about each author. We do want to have some kind of contact information published (personal web page, email address (obscured if desired), etc.) for each author.

There is a box beneath the article-editing box with the label "Author(s)". Anything you put in this field will be treated as the author of the article. This will show up in the ToC and in the syndication feeds. If you don't populate this field, WordPress will use the username of the editor, instead.

==Categories/Tags==
Posts will have "Uncagetorized" checked by default. Uncheck that box, and check the box next to the current issue, which will be a subcategory of "Issues." Do not check the "Issues" category. We generally do not add tags, except for Conference reviews

==WordPress Buttons==

;Save
:Saves the article, sets the post status to whatever option is selected in the Publish Status form.
;Publish
:Saves the article, sets the post status to Pending Review and assigns a timestamp to the article.

If an issue is not yet published, setting the post status to "Published" or clicking the "Publish" button will set the article to "Pending Review" status. If the issue is already published, this would actually publish the article.

==WordPress Post Status==
An article has four possible statuses. However, only the first three statuses are available to editors.
;Draft
:Use for not yet complete articles. Only editors can see these.
;Pending Review
:Use for sharing the article with authors. Editors and anyone logged in with user ID 17 (i.e., the author account) can see these. See this [http://groups.google.com/group/c4lj-articles/browse_thread/thread/1231b06c09f1289f post] on c4lj-articles for the login information for the author account (username: author).
;Private
:We don't use this option anymore.
;Published
:A published post is visible to everyone. It is part of the RSS feed. If you're editing an already published post, don't select anything in the post status form, just hit Save.

==Publishing an Issue==

# Let everyone on the c4lj-articles list know you are getting ready to publish (so they can save and close any open articles).
# Log in to WordPress
# Make sure that all articles for the issue have the correct issue category selected and have been set to 'Pending Review'. Make sure that the "Uncategorized" and "Issues" categories are unchecked (only the specific issue should be selected).
# Sanity check: count the number of posts which should appear in the publish list
# Click on Posts -> Issues (on the left side)
# Click on "Publish" for the issue you'd like to publish.
## You'll get a list of every "Pending Review" article in that issue. Make sure the number of articles in the list matches your previous count. Don't see all the articles you think you should see? They could be still in Draft status, or not in the correct Issue category, or still have "Uncategorized" selected, or someone may still have it in edit mode. Go back to the posts list and make any necessary changes, and start from #5 again.
# Drag and drop the article titles until they're in the order you want. The order you see there is the order you'll see on the home page (and probably the opposite of the order you'll see in your feed reader).
## Note: It's the coordinating editor's responsibility to decide what order he or she would like the articles to show up in, and order them appropriately when publishing the issue. In general, we try to put the articles with the widest appeal first, and special types (columns, special reports, book reviews, etc.) at the end.
# Click "Publish Issue" (optionally setting the publication time, first). Setting the time should only have an impact on readers who are not logged into the c4lj site. Editors will be able to see the published articles.
# Go to the Journal front page; check the number of articles is correct (again) and that they are in the right order. If there is a problem, go back to the admin interface, click on Posts -> Issues and click Unpublish for the issue. Make whatever corrections are needed and proceed from #5 again.
# Once the issue is finally published, go to [[Code4Lib_Journal_Entries_in_Directory_of_Open_Access_Journals]] and follow the directions to upload the issue metadata to DOAJ.
# Send out announcements (see [[Code4Lib_Journal_Publicity_Venues]])

==Corrections==
See [http://groups.google.com/group/c4lj-articles/browse_thread/thread/8eaabcff2d9c000d/a0aeeb9367fcea5f?lnk=gst&q=errata#a0aeeb9367fcea5f|the editors' list] for how to make corrections. Generally, use an Errata or Correction section at the end with information about the change that was made and have the actual text link down to that section. See also [[Code4Lib_Corrections]]

[[Category:Code4Lib Journal]]

Main Page

2010-12-20T23:49:45Z

Gsf: /* Code4lib Journal */ CapitAls

{|align=right
|__TOC__
|}

== About Code4Lib ==

* [[About Code4Lib]] - Background and history of the community
* [[A Guide for the Perplexed]] - Building skills for working with library technologies

== Code4Lib 2011 Conference ==
''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2011 Code4lib2011 category]''

* [[C4L2011_registration | Registration Information!]]
* [[2011_committees_sign-up_page | 2011 Committees Sign-Up]] - '''Volunteer to help'''
* [[How To Plan A Code4LibCon]]
* [[C4L2011_social_activities|Social Activities]] - ideas & sign-up
* [[C4L2011_planning_wishlist|'''Put your ideas for 2011 here!''']]

=== Transportation ===
* [[C4L2011_rideshare|Airport Ride Share]]

== Local / Regional Groups ==

* [[NYC|Code4LibNYC]] - NYC and surrounding areas
* [[NEC4L|New England Code4lib]] - New England
* [http://se.code4lib.org Southeastern Code4lib] - North Carolina, Virginia, Tennessee, etc.
* [[NL|Code4Bib]] - Dutch Code4Bib
* [[MDC|Code4libMDC]] - Maryland, Washington D.C and surrounding areas
* [http://groups.google.com/group/pnwcode4lib?hl=en PNWCode4Lib] - Pacific Northwest
* [[North|code4lib North]] - Ontario and surrounding areas ''(new for Jan 2010!)''
* [[Midwest|Code4Lib Midwest]] - Wherever that is...
* [http://groups.google.com/group/ikr-fejlesztok/ Code4lib.hu] - Group of Hungarian library developers
* [http://www.code4lib.jp/ Code4Lib Japan] - ''(new in 2010!)'', see also [http://twitter.com/yesonline/statuses/28561046501 tweet from Jerry Lee]

== Interest Groups ==

* [[ILS_Interop|ILS Interoperability]] - A group working to develop an infrastructure for interoperating between discovery layers and integrated library systems.
* [[Open_Source_Book_Widgets|Open Source Book Widgets]] - A list of open source book widgets
* [[Discovery|Open Source Discovery]] - Open Source application to enhance and support "discovery" in libraries
* [[Mobile_Apps|Mobile Applications]] - A group interested in mobile web and native application development for libraries
* [[Sources_Of_Metadata|Sources Of Metadata]] - list of api's and sources of interest to libraries

== Software Usage and Documentation ==

* [[Umlaut]] - OpenURL link resolving middleware
* [[:Category:Patterns|Patterns for Collaborative Code]] - Patterns to make your open source 'more open', more amenable to distributed development and use at multiple institutions without forking.
* [[ILS Documentation]]
* [[OSS Directory]]
* [[Working with MaRC]]
* [[Rogue]] - principles for standards creation

== Code4Lib Journal ==

* [[:Category:Code4Lib Journal|Code4Lib Journal]] - information and working documents

== Current topics ==

* [[OCLC Policy Change]]
* [[SirsiDynix: Integrated Library System Platforms on Open Source]]

== Other Code4Lib Sites ==

* [http://www.code4lib.org/ code4lib.org]
* [http://planet.code4lib.org planet.code4lib.org]

== Code4Lib 2012 Conference ==
''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2012 Code4lib2012 category]''

* [[C4L2012_Call_For_Host|'''2012 Call For Host''']]

== Earlier Conferences and events ==

== Code4libcon 2010 ==
''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2010 Code4lib2010 category]''
* [http://code4lib.org/conference/2010/schedule Finalized schedule]
* [[2010 Lightning Talks Signup]] - sign up to give a lightning talk
* [[2010 Breakout Sessions]] - suggest a breakout here
* '''[[2010 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff'''
* [[C4L2010_social_activities|Social Activities]] - ideas & sign-up
* [[Committees sign-up page]] - '''Volunteer to help'''
* [[C4L2011_planning_wishlist|'''Put your ideas for 2011 here!''']]

=== Transportation ===
* [[Asheville Airport to Hotel Van Manifest]]
* [[C4L2010rideshare|General shared travel/transportation planning]]
* [[C4L2010planning:RoommatesRidesEtc|Roommates, Rides, Etc]]

=== Deals ===
* [[C4L2010_manning_discount|Manning Publications Discount]] - discount code (40% off) for use by attendees through Feb. 28, 2010
* Thanks also to our other sponsors!

=== Asheville planning ===
* [[C4L2010planning|2010 Planning]]
* [[C4L2010planning:_wishlist | 2010 Planning Wishlist]] - planning page for issues, expectations, etc. for the 2010 conference

== Code4libcon 2009 ==
* [[BookRaffle]] - coordinate begging publishers for books to raffle off at the conference
* [http://inkdroid.org/c4l2009/attendees Get FOAFed] - add your FOAF profile to the network of c4l2009 attendees
* PreConferences:
** [[GIS_preconf_code4libcon2009]] - Open source GIS just like mom used to make
** [[LinkedData]] - A proposal for a linked-data code4lib2009 pre-conference
** [[LibX_Preconference]] - Proposal for a half-day pre-conference targeted at developers who wish to use the LibX 2.0 platform
** [http://code4lib.org/2009/oclc-precon OCLC Grid Services Preconference]
* [[RoommatesRidesEtc]] - Find roommates for Code4Lib 2009, share rides, etc.
* [[2009 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff

=== Other workshops ===
* [http://barcamp.org/SearchCampDC SearchCampDC] - barcamp style event in DC with usual suspects from code4lib
* [[code4lib/elag2010]] - 1-day code4lib preconference at elag2010

== Archived topics ==

* [[Logo Design Process]]

[[AdminToDo]] - ideas and tasks for maintaining the Code4Lib sites

Code4Lib Journal Email Templates

2010-11-12T20:39:50Z

Gsf: /* Submission Acknowledgement */

''See also [[Code4Lib_Journal_Deadlines]]''

== Call for proposals ==

'''Change what's in bold...'''

----

Call for Papers (and apologies for cross-posting):

The Code4Lib Journal (C4LJ) exists to foster community and share
information among those interested in the intersection of libraries,
technology, and the future.

The Code4Lib Journal is now accepting proposals for publication in its
8th issue. Don't miss out on this opportunity to share your ideas and
experiences. To be included in the '''8th issue''', which is scheduled for
publication in '''mid November 2009''', please submit articles, abstracts,
or proposals at http://journal.code4lib.org/submit-proposal or to journal@code4lib.org by '''Friday, August 14, 2009'''.
When submitting, please include the title or subject of the
proposal in the subject line of the email message.

C4LJ encourages creativity and flexibility, and the editors welcome
submissions across a broad variety of topics that support the mission
of the journal. Possible topics include, but are not limited to:

* Practical applications of library technology (both actual and hypothetical)
* Technology projects (failed, successful, or proposed), including how they were done and challenges faced
* Case studies
* Best practices
* Reviews
* Comparisons of third party software or libraries
* Analyses of library metadata for use with technology
* Project management and communication within the library environment
* Assessment and user studies

C4LJ strives to promote professional communication by minimizing the
barriers to publication. While articles should be of a high quality,
they need not follow any formal structure. Writers should aim for the
middle ground between blog posts and articles in traditional refereed
journals. Where appropriate, we encourage authors to submit code
samples, algorithms, and pseudo-code. For more information, visit
C4LJ's Article Guidelines or browse articles from the first '''7''' issues
published on our website: http://journal.code4lib.org.

Remember, for consideration for the '''8th issue''', please send proposals,
abstracts, or draft articles to journal@code4lib.org no
later than '''Friday, August 14, 2009'''.

Send in a submission. Your peers would like to hear what you are doing.

Code4Lib Journal Editorial Committee

== Submission Acknowledgement ==

Thank you for submitting a proposal to the Code4Lib Journal. We appreciate your participation in the Code4Lib community. The editors have received your proposal and should be in touch with you in 2-4 weeks regarding its appropriateness for publication in C4LJ. We will notify you if we need additional information to make this decision. Please feel free to contact us at journal@code4lib.org if you have additional questions.

== Need More Information ==

Thank you for your interest in publishing in the Code4Lib Journal. The Journal is primarily focused on technological issues in libraries. In order to help the editors determine if your proposal is appropriate for this publication, could you share more details about the intended audience for the the article and how it will address issues surrounding technology in libraries? Please respond to journal@code4lib.org with the additional information requested.

You may also contact the editors at journal@code4lib.org if you have any additional questions. We look forward to hearing from you.

== Proposal Accepted ==

'''See also [[Code4Lib_Journal_Deadlines]]'''

I'm pleased to tell you that your recent proposal for an article about
<insert topic/title> has been provisionally accepted to the Code4Lib
Journal. The editorial committee is interested in your proposal, and
would like to see a draft.

<insert any additional comments about focus we'd like to see in the
article or editorial committee concerns. Sample language "We're
especially interested in X, and we'd like you to make sure to flesh
this out when you write the article." "We're interested in this
proposal if you can do X, Y, or Z.">

As a member of the Code4Lib Journal editorial committee, I will be
your contact for this article, and will work with you to get it ready
for publication.

We hope to publish your article in issue <#> of the Journal, which is
scheduled to appear on <insert date here>. The deadline for submission
of a complete draft is <deadline for draft>, but the sooner you can
get us a draft the better, and the more likely we'll be able to get
your article into issue <#>. Upon receipt of the draft, I will work
with you to address any changes recommended by the Editorial
Committee. More information about our author guidelines may be found
at http://journal.code4lib.org/article-guidelines.

Please note that final drafts must be approved by a vote of the
Editorial Committee before being published.

We also require all authors to agree to US CC-BY licensing for the
articles we publish in the journal. We recommend that any included
code also have some type of code-specific open source license (such as
the GPL).

We look forward to seeing a complete draft and hope to include it in
the Journal. Thank you for submitting to us, and feel free to contact
me directly with any questions.

If you could drop me a line acknowledging receipt of this email, that would be great.

== Proposal Rejected ==

We regret to inform you that your recent proposal to the Code4Lib Journal for an article about <insert topic/title> has not been accepted for publication. This is likely because the Editorial Committee determined that it was not an appropriate match for the audience, mission, or scope of the Code4Lib Journal. [optional - insert comment here about why it's not appropriate]

For more information about the mission of the Code4Lib Journal, please see http://journal.code4lib.org/mission/.

Thanks for considering us, and please do not hesitate to contact the editors at journal@code4lib.org in the future with a new or revised proposal.

[[Category: Code4Lib Journal]]

2011talks Submissions

2010-11-12T19:54:26Z

Gsf: /* Beyond Sacrilege: A CouchApp Catalog */

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.

See the [http://wiki.code4lib.org/index.php/2011talkscall_Call_for_Submissions Call for Submissions] for guidelines on appropriate topic talks and the criteria on which submissions are evaluated.

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.

== We Don’t Server Their Kind : Managing E-resources with Flat-File Databases ==
* Junior Tidal, Multimedia and Web Services Librarian, New York City College of Technology, CUNY (jtidal at citytech dot cuny dot edu)
Managing E-resources can be a daunting challenge. URLs, database names, and even vendors can change, go down, or simply cease to exist. My proposal involves the use of a PHP-based, flat-file database driven web tool for database management. The design of this program was to fulfill two needs: ease of use for librarians with a lack of programming experience and to meet the security and technical restrictions placed by the college’s IT department. My presentation will explore the development of this tool, challenges within its development, and future improvements. PHP code and the flat-file database will also be explained and provided to attendees. For a working demonstration feel free to visit the New York City College of Technology’s A-Z database [http://library.citytech.cuny.edu/research/AToZ/index.php page] or the subject database [http://library.citytech.cuny.edu/research/subject/index.php page].

== Drupal 7 as a Rapid Application Development Tool ==

* Cary Gordon, President, The Cherry Hill Company & Board Member, The Drupal Association (cgordon at chillco dawt com)
Five years ago, I discovered that the Drupal CMS had a programming framework disguised as an API, and learned that I could use it to solve problems.

Drupal 7 builds on that to provide a powerful toolset for interfacing with, manipulating and presenting data. It empowers tool-builders by providing a minimal install option, along with a more powerful installation profile system makes it easier for developers to package and distribute their applications.

== Helping Open Source Succeed ==

* [[User:DataGazetteer|Peter Murray]], LYRASIS, [mailto:Peter.Murray@lyrasis.org Peter.Murray@lyrasis.org]
* Tim Daniels, LYRASIS, [mailto:Tim.Daniels@lyrasis.org Tim.Daniels@lyrasis.org]

Deciding if open source is an option for your institution, or what open source software matches your institution’s needs and capabilities, is a complex decision. LYRASIS is developing a new area of focus to assist libraries with decision tools and an open source software registry. We want to learn from the creators of open source software what questions institutions have when considering the adoption of open source software and what information you would like to see in a registry that compares various open source tools. A summary of topics discussed in this session will be openly published as part of LYRASIS’ program development plans and decision support resources.

The mission of the new and emerging LYRASIS Technology Services area is to serve members and the broader library community as a provider of expertise and capacity in open source based technology solutions. We think that viable roles for an organization supporting open source software are to: a) Increase understanding of open source technology within the library community, including value, benefits, risks, and costs; b) Assist in decision-making by providing resources to help libraries evaluate open source technologies, institutional readiness, and capacity for adoption; c) Support adoption and use of open source technologies and systems within libraries and consortia; d) Foster integration of open source software tools to expand the ability of existing programs to meet a range of library user needs; e) Develop and test new open source software programs, and contribute to the development of existing programs; f) Support long-term sustainability of viable, library-based open source software and systems. We recognize that these roles exist to some extent on a continuum, with latter services related to development and sustainability building on the knowledge and experience gained through deployment of existing open source systems. In turn, effective adoption and use depends on understanding open source systems and having resources to assist in decision-making and implementation.

With open source software in the “innovator” and “early adopter” stages in the library community, we intend to focus its initial efforts on roles A-D in the above list: increased understanding, decision-support, and effective adoption and integration of existing library-focused open source systems. This session is focused on the decision-support services area of activity.

The impact of this session is expected to be far reaching, if initially subtle. With most of the session time devoted to discussion and interaction among peers on questions surrounding the adoption of open source software, participants will take away a deeper understanding of topics each institution should consider when looking at open source software. These findings, along with that of similar sessions around the country, will inform the creation and expansion of the free decision support tools being developed by LYRASIS.

== Letting in the light: using Solr as an external search component ==

* Jay Luker, IT Specialist, ADS (jluker at cfa dot harvard dot edu)
* Benoit Thiell, software developer, ADS (bthiell at cfa dot harvard dot edu)

It’s well-established that [http://lucene.apache.org/solr/ Solr] provides an excellent foundation for building a faceted search engine. But what if your application’s foundation has already been constructed? How do you add Solr as a federated, fulltext search component to an existing system that already provides a full set of well-crafted scoring and ranking mechanisms?

This talk will describe a work-in-progress project at the [http://adswww.harvard.edu/ Smithsonian/NASA Astrophysics Data System] to migrate its aging search platform to [http://invenio-software.org/ Invenio], an open-source institutional repository and digital library system originally developed at CERN, while at the same time incorporating Solr as an external component for both faceting and fulltext search.

In this presentation we'll start with a short introduction of Invenio and then move on to the good stuff: an in-depth exploration of our use of Solr. We'll explain the challenges that we faced, what we learned about some particular Solr internals, interesting paths we chose not to follow, and the solutions we finally developed, including the creation of custom Solr request handlers and query parser classes.

This presentation will be quite technical and will show a measure of horrible Java code. Benoit will probably run away during that part.

== Working with DuraCloud: How to preserve your data in the cloud ==

* Bill Branan, DuraSpace, bbranan at duraspace dot org
* Andrew Woods, DuraSpace, awoods at duraspace dot org

Ever expanding digital collections have become the norm in academic libraries. As the size of collections grow, the need for simple-to-deploy yet powerful preservation strategies becomes increasingly important. The [http://duracloud.org DuraCloud] project, a cloud-hosted service for data management and preservation, is committed to bringing the availability and elasticity of the cloud to bear on the issue of digital preservation. This session will discuss the APIs and tools which can be used to communicate and integrate with the DuraCloud platform, providing an immediate connection to scalable storage available from multiple cloud storage providers, configurable services which can be run over your content out-of-the-box, and a development platform which can serve as the basis for ongoing data mining and analysis.

== Visualizing Library Data ==

* Karen Coombs, OCLC, coombsk at oclc dot org

Visualizations can be powerful tools to give context to library users
and to provide a clear picture for data-driven decision-making in
libraries. Map mashups, tag clouds and timelines can be used to show
information to users in new ways and help them locate materials to meet
their needs. QR codes can help link users to materials that libraries
have in their collections. Charts and graphs can be used to help analyze
library collections (holdings) and compare them to other libraries. This
session will show prototypes which combine tools like Google Chart API,
Protovis and Simile Widgets with data from WorldCat, WorldCat Registry,
Classify, Terminology Services, and Dewey.info to create vivid
illustrations in library user interfaces and administration tools.

== Kuali OLE: Architecture for Diverse and Linked Data ==

* Tim McGeary, Lehigh University, Kuali OLE Functional Council, tim dot mcgeary at lehigh dot edu
* Brad Skiles, Project Manager, Kuali OLE, Indiana University, bradskil at indiana dot edu

With programming scheduled to be begin in January 2011 on the Kuali Open Library Environment (OLE), the Kuali OLE Functional Council is developing the requirements for an architecture for diverse data sets and linked data. With no frontrunner for one bibliographic data standard, and local requirements on what data will be accompanying or linked to the main record store, Kuali OLE needs to build a flexible environment for records management and access.

We will present the concepts of our planned architecture, a multi-repository framework, using a document repository, a semantic repository, and a relational repository, brokered on top of the enterprise service bus of Kuali Rice. As a community source project, this is an opportunity for the Kuali OLE partners to present our plans for discussion with the community, and we look forward to feedback, questions, and comments.

== One Week | One Tool: ultra-rapid open source development among strangers ==

* Scott Hanrath, University of Kansas Libraries, shanrath at ku dot edu
* Jason Casden, North Carolina State University Libraries, jason_casden at ncsu dot edu

In summer 2010, the Center for History and New Media at George Mason University, supported by an NEH Summer Institute grant, gathered 12 'digital humanists' for an intense week of collaboration they dubbed 'One Week | One Tool: a digital humanities barn raising.' The group -- several of whom hang their professional hats in libraries and most of whom were previously unacquainted -- was asked to spend one week together brainstorming, specifying, building, publicizing, and releasing an open source software tool of use to the digital humanities community. The result was Anthologize, a free, open-source, plugin that transforms WordPress into a platform for publishing electronic texts in formats including PDF, ePub, and TEI; in other words, a "blog-to-book" tool. This presentation will focus on how One Week | One Tool addressed the challenges of collaborative open source development. From the perspectives of two library coders on the team, we will describe and provide lessons learned from the One Week development process including: how the group structured itself without predefined roles; how the one week time frame and makeup of the group -- which included scholars, grad students, librarians, museum professionals, instructional technologists, and more -- influenced planning and development decisions; the roles of user experience and outreach efforts; the life of Anthologize since the end of the week; and thoughts on what a one week, one 'library' tool could look like.

== Improving the presentation of library data using FRBR and linked data ==

* Anne-Lena Westrum, Oslo Public Library (annelena at deichman dot no)
* Asgeir Rekkavik, Oslo Public Library (asgeirr at deichman dot no)

The Pode project at Oslo Public Library has experimented on the automated FRBRizing of catalogue records, as well as expressing bibliographic descriptions as linked data to enrich catalogue browsing with information from external sources.

When a library enduser searches the online catalogue for works by a particular author, he will typically get a long list that contain all the different translations and editions of all the books by that author, sorted by title or date of issue. The Pode project applied a method of automated FRBRizing, based on the information contained in MARC records, RDF representation and SPARQL queries, to demonstrate how an author's complete production can be presented as a lucid list of unique works, that can easily be browsed by their different expressions and manifestations. Furthermore, by linking instances in the dataset to matching or corresponding instances in external sets, the presentation can be enriched with additional information about authors and works, as well as links to electronic full-text representations.

The talk will also present the work on making an RDF representation of the catalogue records for the whole collection of non-fiction documents at the Norwegian Multilingual library, linking subject headings and Dewey classes, and allowing endusers to browse the collection by the multilingual Dewey class labels published by OCLC at http://dewey.info.

The talk will focus on the challenges technological progresses such as these raise for cataloguers, to deliver consistent and standardized catalogue records. Many cataloguers have a local and pragmatic focus on the library's own and already existing services. Attitudes like this might represent a problem when emerging technologies find new applications for library catalogue data, as well as when the library wants to use data submitted by others to enrich their own services.

== Touch and go: building a touch screen kiosk with software you already own ==

* Andreas K. Orphanides, North Carolina State University Libraries, akorphan at ncsu dot edu

In October 2010, the NCSU Libraries debuted its first public touch-screen information kiosk, designed to provide on-demand access to useful and commonly consulted real-time displays of library information. With the exception of the touchscreen itself, the system was created using commonly available free software and off-the-shelf hardware. In this presentation, I will describe the process for creating the touchscreen interface that is used in this kiosk. I will walk through the challenges of developing for a touch-optimized environment in HTML and JavaScript; I will describe how free utilities and web browser plugins may be combined to secure a public touchscreen kiosk; and I will present a data analysis of touchscreen usage since the kiosk's rollout to evaluate content selection and interface design.

== Next-L Enju, NDL Search and library geeks in Japan ==

* Kosuke Tanabe, Keio University, tanabe at mwr dot mediacom dot keio dot ac dot jp

[http://github.com/next-l Next-L Enju ] is an open source integrated library system developed by Project Next-L, the library geek community in Japan launched on November 2006. It is built on open-source software (Ruby on Rails, PostgreSQL/MySQL and Solr) and supports modern ILS features (e.g. FRBR structure and RESTful WebAPI).

Enju has been inplemented by some libraries, which include National Diet Library (NDL), the largest library in Japan. NDL has chosen Enju to provide a new search engine, called "NDL Search" and added some extra features (e.g. automatic FRBRization and providing bibliographic data in a Linked Data format) . The development version is available at http://iss.ndl.go.jp/ .

I'm one of the authors of Next-L Enju. I'd like to talk about the overview and structure of Next-L Enju, NDL Search and the activities of our project.

== A community based approach to developing a Digital Exhibit at Notre Dame using the Hydra Framework ==

* Rick Johnson, University of Notre Dame, (rick dot johnson at nd dot edu)
* Dan Brubaker Horst, University of Notre Dame (dbrubak1 at nd dot edu)

It was clear to us early on that the scope of managing, preserving, and interacting with digital content is too much for any one institution to conquer by itself. We realized that we need help.

We were already fairly convinced using Fedora, Solr, and ActiveFedora were solid choices because of their strong development community and flexible robust solutions. We were also exploring Blacklight for search and browse for the same reasons. The open questions were:

* What is the best way to put the pieces together?
* How do you tackle the heterogenous content types and workflows without getting bogged down in each individual solution?

Enter Code4Lib2010...

After connecting with folks from the Hydra project at Code4Lib it was immediately clear that we had many things in common:
* The same architectural choices: Fedora, Solr, ActiveFedora, Blacklight
* Similar design philosophies
* A need to work together
* Too many shared use cases to ignore

So, we jumped on board and have adopted the Hydra Framework for all of our Digital Repository efforts.

In our presentation we will cover:
* Why we chose to adopt the Hydra Framework instead of creating our own solution
* Why the community based approach is so appealing
* How we were welcomed into the Hydra development community
* Why we chose to create something beyond basic Blacklight search and facet browse
* How to create your own Digital Exhibit using Hydra including
** Metadata management
** Custom Browse and Search

The Hydra Project is actively seeking partnerships with other institutions to extend its efforts. Will your institution be next?

More about the [https://wiki.duraspace.org/display/hydra/The+Hydra+Project Hydra Project]

== Mendeley's API and University Libraries: 3 examples to create value ==

* Jan Reichelt, Co-Founder, 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.

Based on this platform and data, I will present three examples of how Mendeley is working to support university libraries and contribute to opening up academic research:
1) Mendeley’s integration as a workflow tool with institutional repositories with the aim of increasing IR deposit rates;
2) Application examples building on Mendeley’s API to showcase what is possible with the newly available type of usage data Mendeley is aggregating;
3) Preview of Mendeley’s library dashboard that will reveal content usage within an institution.

I would also hope that a subsequent discussion can address how you (the attendees) could envision Mendeley’s future in the library tech community.

== ArticlesPlus: Summon API Client Implementation and Integration with Drupal 6 ==

* Albert Bertram, University of Michigan (bertrama@umich.edu)

On September 27, 2010, the University of Michigan launched ArticlesPlus, an application for web-scale article discovery using the Serials Solutions' Summon service as its search engine. Rather than providing a search box which sent our patrons to the interface provided by Serials Solutions, we used Summon's API to integrate the search as a feature of our library's website. In addition to Summon as the search engine, we used our Drupal instance for the interface engine.

I propose to talk about how we implemented the Summon API, the Drupal module we developed in to access the Summon API, problems with implementing an interface ourselves, benefits of implementing the interface ourselves, and plans for future expansion or improved integration in our website.

== Let's Get Small: A Microservices Approach to Library Websites ==

* Sean Hannan, Johns Hopkins University, shannan at jhu dot edu

Most, if not all, library websites are housed and maintained in singular, monolithic content management systems. This is fantastic if the library website is the one place your users go for library information. But it isn't. Users are going to Facebook, checking mobile applications, browsing portals as well as checking the library website. Wouldn't it be great if you could update the information on all of these sites from a single source? Why maintain the library hours in five different places?

In this talk, I will show how breaking the construction of the library website into as-needed, swappable microservices can free your content to live where it needs to, as well as free you from the maintenance headaches usually involved. What kind of microservices, you ask? Well, basic templating and styling is a given, but how about a microservice that gracefully degrades your layouts for older browsers? Or enforces highfalutin typographic rules? Or optimizes your site assets to improve load times? All wonderful little black boxes that allow you to focus on the website and its content, and not the details.

I promise at least one diagram. That will burn your eyes.

[[Category:Code4Lib2011]]

== Sharing Between Data Repositories ==

* Kevin S. Clarke, NESCent/Dryad Data Repository, ksclarke at nescent dot org

Dryad (http://datadryad.org) is a generic subject repository that shares author submitted data with other scientific repositories. In a
part "how we done it" and part "things to consider" talk, I'll discuss 1) why we chose BagIt and OAI-ORE as mechanisms for sharing our data, 2) how
we've integrated with TreeBASE (http://www.treebase.org/ -- a subject repository of phylogenetic information), and 3) the possibility of this
method of data sharing being adopted by other repositories within the larger DataONE community.

There will be cake.

== Hey, Dilbert. Where’s my data?! ==

* Tommy Barker, University of Pennsylvania, tbarker at pobox dot upenn dot edu

Libraries are notorious for maintaining data in massively disparate systems such as databases, flat files, xml and web services. The data is rich and valuable to assessment, but extracting value from multiple systems is complex and time consuming. Yes, there are open source and commercial solutions available, but libraries have unique requirements that can be difficult to integrate into these products. Commercial options also tend to be overly complex or the cool features require an expensive enterprise edition.

With funding from the Institute of Museum and Library Services, UPenn is developing MetriDoc to address data integration headaches within the library, and support reporting requirements from management. MetriDoc’s mission is to provide an open source API / tool set where users can specify dataflows and use library based services to solve integration problems while MetriDoc worries about scalability and performance. MetriDoc accomplishes this with no complex xml configuration or scary SOA middleware, but instead uses a simple DSL where possible. Eventually the project will also include dashboards to assist with complex job management and data flow monitoring.

The first half the presentation briefly discusses MetriDoc’s architecture while the remainder of the presentation will include code samples to illustrate problems it can solve. Information on how to contribute or download MetriDoc will be provided as well.

== Open Data and the Biodiversity Heritage Library experience ==

* Trish Rose-Sandler, Missouri Botanical Gardens, trish dot rose dash sandler at mobot dot org

The Biodiversity Heritage Library (BHL) is an international consortium of the world’s leading natural history museum libraries, botanical libraries, and research institutions organized to digitize, serve, and preserve the legacy literature of biodiversity. From the beginning the BHL partners conceived of the BHL collection as being “open” – available to anyone regardless of geographic location or affiliation and a linked into a global Biodiversity Commons. This talk will discuss the basic principles of open data and use BHL as one example of how those principles have played out in a real world context.

What does it mean for data to be “open” and what tools or services can enable this? Our metadata is purposely “open” so that others can harvest it and repurpose it in different contexts. We make it available through both OAI-PMH and APIs.

If you “open” your data will they come? In some cases yes. BHL can give examples of scientists and science services, who have taken our data and exploited it for other purposes (e.g. BioStor, Earthcape, EOL, ZipcodeZoo) Yet, in a recent BHL survey we learned that of our frequent users, 42% were not aware that we provided APIs and 31% did not understand what APIs were. Clearly promotion of your open data is a key activity to making it truly useful.

What are some advantages to open data? Harvestable data allows that data which was created for a specific purpose and audience (e.g. historic texts, nomenclatural services, encyclopedias) to interact with other data and serve new, previously unimagined, roles. For BHL, opening our data it was a desire to do three things 1) make biodiversity data available to foster scientific research 2) support the public use of these data and 3) build a web of science.

== The Road to SRFdom: OpenSRF as Curation Microservices Architecture ==

* Dan Coughlin, Digital Library Technologies, Penn State University ITS (danny@psu.edu)
* Mike Giarlo, Digital Library Technologies, Penn State University ITS (michael@psu.edu)

OpenSRF is the XMPP-based framework that underlies the Evergreen ILS, providing a service-oriented architecture with failover, load-balancing, and high availability. Curation microservices represent a new approach to digital curation in which typical repository functions such as storage, versioning, and fixity-checking are implemented as small, independent services. Put them together and what do you have?

The next phase of Penn State's institutional digital stewardship program will involve prototyping a suite of curation services to enable users to manage and enrich their digital content -- we’re just about to get started on this, at the time this proposal was written. The curation services will be implemented following the microservices philosophy, and they will be stitched together via OpenSRF. We will talk about why we chose the “road to SRFdom,” colliding the ILS world with the repository world, how we implemented the curation services & architecture, and how OpenSRF might be helpful to you. Code will be shown, beware.

== Enhancing the Performance and Extensibility of the XC’s MetadataServicesToolkit ==

* [http://tech.benanderson.us Ben Anderson], [http://www.extensiblecatalog.org/ eXtensible Catalog Organization], banderson@library.rochester.edu

Learn how we increased the performance of the [http://code.google.com/p/xcmetadataservicestoolkit/ XC Metadata Services Toolkit] (MST) by over 900%. The MST is an open-source Java application, that uses SOLR and MySQL to harvest (OAI-PMH) library metadata (MARC, DC), clean it up, convert and frbrize, and then make new metadata (RDA flavor, XC Schema) available for harvesting. Our first release performed too slowly with degrading performance with large record batches and we needed to enable the MST to process a library’s entire catalog in a reasonable amount of time on a common server. The MST was also intended to be extensible. Libraries will almost certainly want to customize this process in some way. Thus our second goal was to make it is as easy as possible for a developer to write a service which can be plugged into the MST.

In the spring of ‘10 we set out to accomplish our 2 goals. The first task was to establish how close the existing MST was to these goals. More concretely, our goal was to be able to process 1M MARC records/hr and have little to no degradation as the MST processed several million records. The first service in our chain of services, the normalization service, served as our initial metric. The normalization service was processing records at a speed of 125k/hr, much slower than we hoped for. On top of that, before processing 2M records, the MST essentially crawled to a halt. We were about an order of magnitude off and we needed to increase scalability in a substantial way as well. Also, examining the steps involved in writing a new service for the MST showed us that it was not easy to do so. Internals of the MST were exposed to the service developer and the developer was expected to re-implement much of this internal code with no instructions on how to do so. Much work needed to be done to abstract the implementation of the MST away from the service developer.

Working hard over the course of several months, we were able to accomplish both of our goals. The MST is now processing records at a speed of 1.2M records/hr with no degradation on a set of 6M records on a less than optimal server (1.5GHz cpu). In this talk, I will detail the specifics of the strategies we used to accomplish this major speed enhancement (such as a shift from Apache SOLR to a hybrid SOLR/MySQL approach). In regards to our second goal, third party developers can now download an MST development environment, write a few lines of code, and package their service for deployment into the MST. Third party developers need not concern themselves with the details of the internal MST implementation. In this talk, I will also walk through [http://code.google.com/p/xcmetadataservicestoolkit/wiki/HowToImplementService the steps] required to write a service for the MST.

== Free my DSpace Data! How to get your data out of DSpace 1.7 and restore your content after a disaster. ==

* Tim Donohue, DuraSpace, tdonohue at duraspace dot org

For a while, [http://www.dspace.org DSpace] has provided many means to get content into the system (or create new content in the system), e.g. basic ingest packages, user interfaces, SWORD. However, getting your content out of DSpace, especially for backups or migrations has often been problematic. In the past, although individual Items could be exported in standard formats, entire Collections or Communities (and the relationships between them) could not be as easily exported.

DSpace 1.7.0 provides a new [https://wiki.duraspace.org/display/DSDOC/AipBackupRestore AIP Backup & Restore feature] which allows DSpace to export '''all''' of its contents (Communities, Collections, Items, Groups, People, Permissions, and relationships between all objects) into a series of METS-based Archival Information Packages (AIPs). As these AIPs are just zip files, they can be backed up using your normal backup practices (e.g. to tape, hard-drive, or even to the cloud via a service like DuraCloud). As these AIPs also fully describe your DSpace contents, they can be used to restore your entire DSpace after a local server crash or larger disaster.

DSpace created AIPs use standard library metadata formats like MODS, PREMIS and METSRights (along with a few DSpace-specific ones where a "standard format" doesn't yet exist) to describe all the content housed in your DSpace installation. This comes in handy, should you ever decide to migrate some or all of your contents to another DSpace instance or another system altogether.

This talk will describe this new DSpace AIP Backup & Restore feature, provide hints/tips on how it can be used to backup/restore/migrate data. Time permitting, I can also touch on the DSpace Roadmap and other ideas/plans to "free your DSpace data".

== Using cloud-based services to leverage open source software ==

* Erik Mitchell, Wake Forest University, mitcheet at wfu dot edu

Open source software and cloud computing systems are perceived as enticing technologies for both IT staff and IT/Academic administrators. The implementation of open source software or adoption of cloud services is often met with resistance however because of lack of technical expertise in smaller organizations or lack of perceived benefit in larger organizations. Although these technologies are not necessarily related when combined they offer easy deployment of services without significant organization investment or local expertise [http://cloud.lib.wfu.edu/blog/gazette/2010/11/04/finding-ways-to-combine-cloud-computing-and-open-source-software/]. This ability allows organizations to leverage open source systems without the overhead typically associated with "free as in a free kitten."

While there are some large national projects looking at using cloud platforms to deliver new services there is an opportunity for a grassroots effort to develop and support pre-configured application servers that are simple to deploy and maintain. These 'disposable' servers would serve the needs of both small and large libraries by enabling them to adopt open source software without taking on the requirement of local infrastructure, configuration, or detailed support.

This presentation will cover the technical details and lessons learned from efforts to create this type of service [http://cloud.lib.wfu.edu/blog/tech/2010/11/01/running-the-zsr-vufind-application-server/] on the Amazon EC2 platform and discuss the impact of this approach on open software adoption and its potential impact on IT support in libraries.

== VIVO: Enabling National Networking of Scientists ==

* Brian Keese, Indiana University, bkeese at indiana dot edu
* Brian Lowe, Cornell University, bjl23 at cornell 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.

== Mass Moves with Worldcat APIs ==
* Sam Kome, Claremont Colleges Library, sam.kome at cuc dot claremont dot edu

Claremont needed to perform a mass evaluation of item level records to facilitate large scale collection moves and de-accession. Our de-accession criteria, for example, include that 3 or more copies of any book must be available in the 50+ libraries in our Link+ network. We addressed our requirements with the help of the OCLC Worldcat Search and xID APIs and a couple simple python scripts. The process was ultimately a success. We will present our approach, code, and the lessons learned as we discovered limits inherent in the APIs and in our own coding (in)experience. Bonus sub-topic: the use of OCLC Work ID to identify and coalesce alternative ISBNs.

== A Simple Algorithm for User Query Classification & Resource Recommendation ==
* Josh Bishoff, University of Illinois, bishoff2 at illinois dot edu

One of the longstanding problems in library services is how we might automatically direct users to the most appropriate personnel, databases or facilities to meet their information need. Utilizing the faceted navigation features of various next-gen catalogs, we can efficiently & very accurately assign subject domains to user search queries.

For example: if a user searches “Gallium Arsenide” in the library discovery layer, we can first broadcast this query to a suitably large OPAC and receive the following subject distribution:

-Engineering & Technology: 45%

-Physical Sciences: 21%

-Education: 9%

…and so on.

By leveraging the cataloging efforts that have classified large collections, we can efficiently classify queries with a high rate of accuracy. By applying this approach to the library discovery layer, we can offer users tailored result sets from subject-specific A & I services. We can also recommend subject specialists & most appropriate campus libraries.

This presentation will discuss the technical challenges of implementing such a system and the trouble with mapping traditional subject classifications to non-book resources (databases, people, buildings, etc.). The dangers of ''incorrect'' automatic query classification will be discussed, along with strategies to combat this. A functional system will be demonstrated and code will be made available.

== Beyond Sacrilege: A CouchApp Catalog ==
* Gabriel Farrell, Drexel University, g@grrawr.com
At Code4LibCon2008 Dan Scott gave us a taste of yummy CouchDB, a document-oriented database with a RESTful JSON API (http://couchdb.org/). Since then, CouchDB has passed the 1.0 mark and landed on desktops, the cloud, and mobile devices. With the advent of CouchApps (web apps served directly from CouchDB) applications can be built that are as easy to install as the replicating of databases (which is super easy!). I'll discuss the advantages and challenges in designing a CouchApp to be used as a catalog, repository, or directory of resources. Some things are made fairly simple, such as site templating, the outputting of documents in different formats, and the attachment of binary objects to documents. Some things, like document versioning and the modeling of data, are a little trickier, but still straightforward. And some things, such as granular authentication and the integration of search, are tangled enough to produce some head-on-wall banging. But hey, take it easy. It’s time to relax.

Check out some code at http://github.com/gsf/catlg.

2011talks Submissions

2010-11-12T19:53:48Z

Gsf: /* Beyond Sacrilege: A CouchApp Catalog */

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.

See the [http://wiki.code4lib.org/index.php/2011talkscall_Call_for_Submissions Call for Submissions] for guidelines on appropriate topic talks and the criteria on which submissions are evaluated.

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.

== We Don’t Server Their Kind : Managing E-resources with Flat-File Databases ==
* Junior Tidal, Multimedia and Web Services Librarian, New York City College of Technology, CUNY (jtidal at citytech dot cuny dot edu)
Managing E-resources can be a daunting challenge. URLs, database names, and even vendors can change, go down, or simply cease to exist. My proposal involves the use of a PHP-based, flat-file database driven web tool for database management. The design of this program was to fulfill two needs: ease of use for librarians with a lack of programming experience and to meet the security and technical restrictions placed by the college’s IT department. My presentation will explore the development of this tool, challenges within its development, and future improvements. PHP code and the flat-file database will also be explained and provided to attendees. For a working demonstration feel free to visit the New York City College of Technology’s A-Z database [http://library.citytech.cuny.edu/research/AToZ/index.php page] or the subject database [http://library.citytech.cuny.edu/research/subject/index.php page].

== Drupal 7 as a Rapid Application Development Tool ==

* Cary Gordon, President, The Cherry Hill Company & Board Member, The Drupal Association (cgordon at chillco dawt com)
Five years ago, I discovered that the Drupal CMS had a programming framework disguised as an API, and learned that I could use it to solve problems.

Drupal 7 builds on that to provide a powerful toolset for interfacing with, manipulating and presenting data. It empowers tool-builders by providing a minimal install option, along with a more powerful installation profile system makes it easier for developers to package and distribute their applications.

== Helping Open Source Succeed ==

* [[User:DataGazetteer|Peter Murray]], LYRASIS, [mailto:Peter.Murray@lyrasis.org Peter.Murray@lyrasis.org]
* Tim Daniels, LYRASIS, [mailto:Tim.Daniels@lyrasis.org Tim.Daniels@lyrasis.org]

Deciding if open source is an option for your institution, or what open source software matches your institution’s needs and capabilities, is a complex decision. LYRASIS is developing a new area of focus to assist libraries with decision tools and an open source software registry. We want to learn from the creators of open source software what questions institutions have when considering the adoption of open source software and what information you would like to see in a registry that compares various open source tools. A summary of topics discussed in this session will be openly published as part of LYRASIS’ program development plans and decision support resources.

The mission of the new and emerging LYRASIS Technology Services area is to serve members and the broader library community as a provider of expertise and capacity in open source based technology solutions. We think that viable roles for an organization supporting open source software are to: a) Increase understanding of open source technology within the library community, including value, benefits, risks, and costs; b) Assist in decision-making by providing resources to help libraries evaluate open source technologies, institutional readiness, and capacity for adoption; c) Support adoption and use of open source technologies and systems within libraries and consortia; d) Foster integration of open source software tools to expand the ability of existing programs to meet a range of library user needs; e) Develop and test new open source software programs, and contribute to the development of existing programs; f) Support long-term sustainability of viable, library-based open source software and systems. We recognize that these roles exist to some extent on a continuum, with latter services related to development and sustainability building on the knowledge and experience gained through deployment of existing open source systems. In turn, effective adoption and use depends on understanding open source systems and having resources to assist in decision-making and implementation.

With open source software in the “innovator” and “early adopter” stages in the library community, we intend to focus its initial efforts on roles A-D in the above list: increased understanding, decision-support, and effective adoption and integration of existing library-focused open source systems. This session is focused on the decision-support services area of activity.

The impact of this session is expected to be far reaching, if initially subtle. With most of the session time devoted to discussion and interaction among peers on questions surrounding the adoption of open source software, participants will take away a deeper understanding of topics each institution should consider when looking at open source software. These findings, along with that of similar sessions around the country, will inform the creation and expansion of the free decision support tools being developed by LYRASIS.

== Letting in the light: using Solr as an external search component ==

* Jay Luker, IT Specialist, ADS (jluker at cfa dot harvard dot edu)
* Benoit Thiell, software developer, ADS (bthiell at cfa dot harvard dot edu)

It’s well-established that [http://lucene.apache.org/solr/ Solr] provides an excellent foundation for building a faceted search engine. But what if your application’s foundation has already been constructed? How do you add Solr as a federated, fulltext search component to an existing system that already provides a full set of well-crafted scoring and ranking mechanisms?

This talk will describe a work-in-progress project at the [http://adswww.harvard.edu/ Smithsonian/NASA Astrophysics Data System] to migrate its aging search platform to [http://invenio-software.org/ Invenio], an open-source institutional repository and digital library system originally developed at CERN, while at the same time incorporating Solr as an external component for both faceting and fulltext search.

In this presentation we'll start with a short introduction of Invenio and then move on to the good stuff: an in-depth exploration of our use of Solr. We'll explain the challenges that we faced, what we learned about some particular Solr internals, interesting paths we chose not to follow, and the solutions we finally developed, including the creation of custom Solr request handlers and query parser classes.

This presentation will be quite technical and will show a measure of horrible Java code. Benoit will probably run away during that part.

== Working with DuraCloud: How to preserve your data in the cloud ==

* Bill Branan, DuraSpace, bbranan at duraspace dot org
* Andrew Woods, DuraSpace, awoods at duraspace dot org

Ever expanding digital collections have become the norm in academic libraries. As the size of collections grow, the need for simple-to-deploy yet powerful preservation strategies becomes increasingly important. The [http://duracloud.org DuraCloud] project, a cloud-hosted service for data management and preservation, is committed to bringing the availability and elasticity of the cloud to bear on the issue of digital preservation. This session will discuss the APIs and tools which can be used to communicate and integrate with the DuraCloud platform, providing an immediate connection to scalable storage available from multiple cloud storage providers, configurable services which can be run over your content out-of-the-box, and a development platform which can serve as the basis for ongoing data mining and analysis.

== Visualizing Library Data ==

* Karen Coombs, OCLC, coombsk at oclc dot org

Visualizations can be powerful tools to give context to library users
and to provide a clear picture for data-driven decision-making in
libraries. Map mashups, tag clouds and timelines can be used to show
information to users in new ways and help them locate materials to meet
their needs. QR codes can help link users to materials that libraries
have in their collections. Charts and graphs can be used to help analyze
library collections (holdings) and compare them to other libraries. This
session will show prototypes which combine tools like Google Chart API,
Protovis and Simile Widgets with data from WorldCat, WorldCat Registry,
Classify, Terminology Services, and Dewey.info to create vivid
illustrations in library user interfaces and administration tools.

== Kuali OLE: Architecture for Diverse and Linked Data ==

* Tim McGeary, Lehigh University, Kuali OLE Functional Council, tim dot mcgeary at lehigh dot edu
* Brad Skiles, Project Manager, Kuali OLE, Indiana University, bradskil at indiana dot edu

With programming scheduled to be begin in January 2011 on the Kuali Open Library Environment (OLE), the Kuali OLE Functional Council is developing the requirements for an architecture for diverse data sets and linked data. With no frontrunner for one bibliographic data standard, and local requirements on what data will be accompanying or linked to the main record store, Kuali OLE needs to build a flexible environment for records management and access.

We will present the concepts of our planned architecture, a multi-repository framework, using a document repository, a semantic repository, and a relational repository, brokered on top of the enterprise service bus of Kuali Rice. As a community source project, this is an opportunity for the Kuali OLE partners to present our plans for discussion with the community, and we look forward to feedback, questions, and comments.

== One Week | One Tool: ultra-rapid open source development among strangers ==

* Scott Hanrath, University of Kansas Libraries, shanrath at ku dot edu
* Jason Casden, North Carolina State University Libraries, jason_casden at ncsu dot edu

In summer 2010, the Center for History and New Media at George Mason University, supported by an NEH Summer Institute grant, gathered 12 'digital humanists' for an intense week of collaboration they dubbed 'One Week | One Tool: a digital humanities barn raising.' The group -- several of whom hang their professional hats in libraries and most of whom were previously unacquainted -- was asked to spend one week together brainstorming, specifying, building, publicizing, and releasing an open source software tool of use to the digital humanities community. The result was Anthologize, a free, open-source, plugin that transforms WordPress into a platform for publishing electronic texts in formats including PDF, ePub, and TEI; in other words, a "blog-to-book" tool. This presentation will focus on how One Week | One Tool addressed the challenges of collaborative open source development. From the perspectives of two library coders on the team, we will describe and provide lessons learned from the One Week development process including: how the group structured itself without predefined roles; how the one week time frame and makeup of the group -- which included scholars, grad students, librarians, museum professionals, instructional technologists, and more -- influenced planning and development decisions; the roles of user experience and outreach efforts; the life of Anthologize since the end of the week; and thoughts on what a one week, one 'library' tool could look like.

== Improving the presentation of library data using FRBR and linked data ==

* Anne-Lena Westrum, Oslo Public Library (annelena at deichman dot no)
* Asgeir Rekkavik, Oslo Public Library (asgeirr at deichman dot no)

The Pode project at Oslo Public Library has experimented on the automated FRBRizing of catalogue records, as well as expressing bibliographic descriptions as linked data to enrich catalogue browsing with information from external sources.

When a library enduser searches the online catalogue for works by a particular author, he will typically get a long list that contain all the different translations and editions of all the books by that author, sorted by title or date of issue. The Pode project applied a method of automated FRBRizing, based on the information contained in MARC records, RDF representation and SPARQL queries, to demonstrate how an author's complete production can be presented as a lucid list of unique works, that can easily be browsed by their different expressions and manifestations. Furthermore, by linking instances in the dataset to matching or corresponding instances in external sets, the presentation can be enriched with additional information about authors and works, as well as links to electronic full-text representations.

The talk will also present the work on making an RDF representation of the catalogue records for the whole collection of non-fiction documents at the Norwegian Multilingual library, linking subject headings and Dewey classes, and allowing endusers to browse the collection by the multilingual Dewey class labels published by OCLC at http://dewey.info.

The talk will focus on the challenges technological progresses such as these raise for cataloguers, to deliver consistent and standardized catalogue records. Many cataloguers have a local and pragmatic focus on the library's own and already existing services. Attitudes like this might represent a problem when emerging technologies find new applications for library catalogue data, as well as when the library wants to use data submitted by others to enrich their own services.

== Touch and go: building a touch screen kiosk with software you already own ==

* Andreas K. Orphanides, North Carolina State University Libraries, akorphan at ncsu dot edu

In October 2010, the NCSU Libraries debuted its first public touch-screen information kiosk, designed to provide on-demand access to useful and commonly consulted real-time displays of library information. With the exception of the touchscreen itself, the system was created using commonly available free software and off-the-shelf hardware. In this presentation, I will describe the process for creating the touchscreen interface that is used in this kiosk. I will walk through the challenges of developing for a touch-optimized environment in HTML and JavaScript; I will describe how free utilities and web browser plugins may be combined to secure a public touchscreen kiosk; and I will present a data analysis of touchscreen usage since the kiosk's rollout to evaluate content selection and interface design.

== Next-L Enju, NDL Search and library geeks in Japan ==

* Kosuke Tanabe, Keio University, tanabe at mwr dot mediacom dot keio dot ac dot jp

[http://github.com/next-l Next-L Enju ] is an open source integrated library system developed by Project Next-L, the library geek community in Japan launched on November 2006. It is built on open-source software (Ruby on Rails, PostgreSQL/MySQL and Solr) and supports modern ILS features (e.g. FRBR structure and RESTful WebAPI).

Enju has been inplemented by some libraries, which include National Diet Library (NDL), the largest library in Japan. NDL has chosen Enju to provide a new search engine, called "NDL Search" and added some extra features (e.g. automatic FRBRization and providing bibliographic data in a Linked Data format) . The development version is available at http://iss.ndl.go.jp/ .

I'm one of the authors of Next-L Enju. I'd like to talk about the overview and structure of Next-L Enju, NDL Search and the activities of our project.

== A community based approach to developing a Digital Exhibit at Notre Dame using the Hydra Framework ==

* Rick Johnson, University of Notre Dame, (rick dot johnson at nd dot edu)
* Dan Brubaker Horst, University of Notre Dame (dbrubak1 at nd dot edu)

It was clear to us early on that the scope of managing, preserving, and interacting with digital content is too much for any one institution to conquer by itself. We realized that we need help.

We were already fairly convinced using Fedora, Solr, and ActiveFedora were solid choices because of their strong development community and flexible robust solutions. We were also exploring Blacklight for search and browse for the same reasons. The open questions were:

* What is the best way to put the pieces together?
* How do you tackle the heterogenous content types and workflows without getting bogged down in each individual solution?

Enter Code4Lib2010...

After connecting with folks from the Hydra project at Code4Lib it was immediately clear that we had many things in common:
* The same architectural choices: Fedora, Solr, ActiveFedora, Blacklight
* Similar design philosophies
* A need to work together
* Too many shared use cases to ignore

So, we jumped on board and have adopted the Hydra Framework for all of our Digital Repository efforts.

In our presentation we will cover:
* Why we chose to adopt the Hydra Framework instead of creating our own solution
* Why the community based approach is so appealing
* How we were welcomed into the Hydra development community
* Why we chose to create something beyond basic Blacklight search and facet browse
* How to create your own Digital Exhibit using Hydra including
** Metadata management
** Custom Browse and Search

The Hydra Project is actively seeking partnerships with other institutions to extend its efforts. Will your institution be next?

More about the [https://wiki.duraspace.org/display/hydra/The+Hydra+Project Hydra Project]

== Mendeley's API and University Libraries: 3 examples to create value ==

* Jan Reichelt, Co-Founder, 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.

Based on this platform and data, I will present three examples of how Mendeley is working to support university libraries and contribute to opening up academic research:
1) Mendeley’s integration as a workflow tool with institutional repositories with the aim of increasing IR deposit rates;
2) Application examples building on Mendeley’s API to showcase what is possible with the newly available type of usage data Mendeley is aggregating;
3) Preview of Mendeley’s library dashboard that will reveal content usage within an institution.

I would also hope that a subsequent discussion can address how you (the attendees) could envision Mendeley’s future in the library tech community.

== ArticlesPlus: Summon API Client Implementation and Integration with Drupal 6 ==

* Albert Bertram, University of Michigan (bertrama@umich.edu)

On September 27, 2010, the University of Michigan launched ArticlesPlus, an application for web-scale article discovery using the Serials Solutions' Summon service as its search engine. Rather than providing a search box which sent our patrons to the interface provided by Serials Solutions, we used Summon's API to integrate the search as a feature of our library's website. In addition to Summon as the search engine, we used our Drupal instance for the interface engine.

I propose to talk about how we implemented the Summon API, the Drupal module we developed in to access the Summon API, problems with implementing an interface ourselves, benefits of implementing the interface ourselves, and plans for future expansion or improved integration in our website.

== Let's Get Small: A Microservices Approach to Library Websites ==

* Sean Hannan, Johns Hopkins University, shannan at jhu dot edu

Most, if not all, library websites are housed and maintained in singular, monolithic content management systems. This is fantastic if the library website is the one place your users go for library information. But it isn't. Users are going to Facebook, checking mobile applications, browsing portals as well as checking the library website. Wouldn't it be great if you could update the information on all of these sites from a single source? Why maintain the library hours in five different places?

In this talk, I will show how breaking the construction of the library website into as-needed, swappable microservices can free your content to live where it needs to, as well as free you from the maintenance headaches usually involved. What kind of microservices, you ask? Well, basic templating and styling is a given, but how about a microservice that gracefully degrades your layouts for older browsers? Or enforces highfalutin typographic rules? Or optimizes your site assets to improve load times? All wonderful little black boxes that allow you to focus on the website and its content, and not the details.

I promise at least one diagram. That will burn your eyes.

[[Category:Code4Lib2011]]

== Sharing Between Data Repositories ==

* Kevin S. Clarke, NESCent/Dryad Data Repository, ksclarke at nescent dot org

Dryad (http://datadryad.org) is a generic subject repository that shares author submitted data with other scientific repositories. In a
part "how we done it" and part "things to consider" talk, I'll discuss 1) why we chose BagIt and OAI-ORE as mechanisms for sharing our data, 2) how
we've integrated with TreeBASE (http://www.treebase.org/ -- a subject repository of phylogenetic information), and 3) the possibility of this
method of data sharing being adopted by other repositories within the larger DataONE community.

There will be cake.

== Hey, Dilbert. Where’s my data?! ==

* Tommy Barker, University of Pennsylvania, tbarker at pobox dot upenn dot edu

Libraries are notorious for maintaining data in massively disparate systems such as databases, flat files, xml and web services. The data is rich and valuable to assessment, but extracting value from multiple systems is complex and time consuming. Yes, there are open source and commercial solutions available, but libraries have unique requirements that can be difficult to integrate into these products. Commercial options also tend to be overly complex or the cool features require an expensive enterprise edition.

With funding from the Institute of Museum and Library Services, UPenn is developing MetriDoc to address data integration headaches within the library, and support reporting requirements from management. MetriDoc’s mission is to provide an open source API / tool set where users can specify dataflows and use library based services to solve integration problems while MetriDoc worries about scalability and performance. MetriDoc accomplishes this with no complex xml configuration or scary SOA middleware, but instead uses a simple DSL where possible. Eventually the project will also include dashboards to assist with complex job management and data flow monitoring.

The first half the presentation briefly discusses MetriDoc’s architecture while the remainder of the presentation will include code samples to illustrate problems it can solve. Information on how to contribute or download MetriDoc will be provided as well.

== Open Data and the Biodiversity Heritage Library experience ==

* Trish Rose-Sandler, Missouri Botanical Gardens, trish dot rose dash sandler at mobot dot org

The Biodiversity Heritage Library (BHL) is an international consortium of the world’s leading natural history museum libraries, botanical libraries, and research institutions organized to digitize, serve, and preserve the legacy literature of biodiversity. From the beginning the BHL partners conceived of the BHL collection as being “open” – available to anyone regardless of geographic location or affiliation and a linked into a global Biodiversity Commons. This talk will discuss the basic principles of open data and use BHL as one example of how those principles have played out in a real world context.

What does it mean for data to be “open” and what tools or services can enable this? Our metadata is purposely “open” so that others can harvest it and repurpose it in different contexts. We make it available through both OAI-PMH and APIs.

If you “open” your data will they come? In some cases yes. BHL can give examples of scientists and science services, who have taken our data and exploited it for other purposes (e.g. BioStor, Earthcape, EOL, ZipcodeZoo) Yet, in a recent BHL survey we learned that of our frequent users, 42% were not aware that we provided APIs and 31% did not understand what APIs were. Clearly promotion of your open data is a key activity to making it truly useful.

What are some advantages to open data? Harvestable data allows that data which was created for a specific purpose and audience (e.g. historic texts, nomenclatural services, encyclopedias) to interact with other data and serve new, previously unimagined, roles. For BHL, opening our data it was a desire to do three things 1) make biodiversity data available to foster scientific research 2) support the public use of these data and 3) build a web of science.

== The Road to SRFdom: OpenSRF as Curation Microservices Architecture ==

* Dan Coughlin, Digital Library Technologies, Penn State University ITS (danny@psu.edu)
* Mike Giarlo, Digital Library Technologies, Penn State University ITS (michael@psu.edu)

OpenSRF is the XMPP-based framework that underlies the Evergreen ILS, providing a service-oriented architecture with failover, load-balancing, and high availability. Curation microservices represent a new approach to digital curation in which typical repository functions such as storage, versioning, and fixity-checking are implemented as small, independent services. Put them together and what do you have?

The next phase of Penn State's institutional digital stewardship program will involve prototyping a suite of curation services to enable users to manage and enrich their digital content -- we’re just about to get started on this, at the time this proposal was written. The curation services will be implemented following the microservices philosophy, and they will be stitched together via OpenSRF. We will talk about why we chose the “road to SRFdom,” colliding the ILS world with the repository world, how we implemented the curation services & architecture, and how OpenSRF might be helpful to you. Code will be shown, beware.

== Enhancing the Performance and Extensibility of the XC’s MetadataServicesToolkit ==

* [http://tech.benanderson.us Ben Anderson], [http://www.extensiblecatalog.org/ eXtensible Catalog Organization], banderson@library.rochester.edu

Learn how we increased the performance of the [http://code.google.com/p/xcmetadataservicestoolkit/ XC Metadata Services Toolkit] (MST) by over 900%. The MST is an open-source Java application, that uses SOLR and MySQL to harvest (OAI-PMH) library metadata (MARC, DC), clean it up, convert and frbrize, and then make new metadata (RDA flavor, XC Schema) available for harvesting. Our first release performed too slowly with degrading performance with large record batches and we needed to enable the MST to process a library’s entire catalog in a reasonable amount of time on a common server. The MST was also intended to be extensible. Libraries will almost certainly want to customize this process in some way. Thus our second goal was to make it is as easy as possible for a developer to write a service which can be plugged into the MST.

In the spring of ‘10 we set out to accomplish our 2 goals. The first task was to establish how close the existing MST was to these goals. More concretely, our goal was to be able to process 1M MARC records/hr and have little to no degradation as the MST processed several million records. The first service in our chain of services, the normalization service, served as our initial metric. The normalization service was processing records at a speed of 125k/hr, much slower than we hoped for. On top of that, before processing 2M records, the MST essentially crawled to a halt. We were about an order of magnitude off and we needed to increase scalability in a substantial way as well. Also, examining the steps involved in writing a new service for the MST showed us that it was not easy to do so. Internals of the MST were exposed to the service developer and the developer was expected to re-implement much of this internal code with no instructions on how to do so. Much work needed to be done to abstract the implementation of the MST away from the service developer.

Working hard over the course of several months, we were able to accomplish both of our goals. The MST is now processing records at a speed of 1.2M records/hr with no degradation on a set of 6M records on a less than optimal server (1.5GHz cpu). In this talk, I will detail the specifics of the strategies we used to accomplish this major speed enhancement (such as a shift from Apache SOLR to a hybrid SOLR/MySQL approach). In regards to our second goal, third party developers can now download an MST development environment, write a few lines of code, and package their service for deployment into the MST. Third party developers need not concern themselves with the details of the internal MST implementation. In this talk, I will also walk through [http://code.google.com/p/xcmetadataservicestoolkit/wiki/HowToImplementService the steps] required to write a service for the MST.

== Free my DSpace Data! How to get your data out of DSpace 1.7 and restore your content after a disaster. ==

* Tim Donohue, DuraSpace, tdonohue at duraspace dot org

For a while, [http://www.dspace.org DSpace] has provided many means to get content into the system (or create new content in the system), e.g. basic ingest packages, user interfaces, SWORD. However, getting your content out of DSpace, especially for backups or migrations has often been problematic. In the past, although individual Items could be exported in standard formats, entire Collections or Communities (and the relationships between them) could not be as easily exported.

DSpace 1.7.0 provides a new [https://wiki.duraspace.org/display/DSDOC/AipBackupRestore AIP Backup & Restore feature] which allows DSpace to export '''all''' of its contents (Communities, Collections, Items, Groups, People, Permissions, and relationships between all objects) into a series of METS-based Archival Information Packages (AIPs). As these AIPs are just zip files, they can be backed up using your normal backup practices (e.g. to tape, hard-drive, or even to the cloud via a service like DuraCloud). As these AIPs also fully describe your DSpace contents, they can be used to restore your entire DSpace after a local server crash or larger disaster.

DSpace created AIPs use standard library metadata formats like MODS, PREMIS and METSRights (along with a few DSpace-specific ones where a "standard format" doesn't yet exist) to describe all the content housed in your DSpace installation. This comes in handy, should you ever decide to migrate some or all of your contents to another DSpace instance or another system altogether.

This talk will describe this new DSpace AIP Backup & Restore feature, provide hints/tips on how it can be used to backup/restore/migrate data. Time permitting, I can also touch on the DSpace Roadmap and other ideas/plans to "free your DSpace data".

== Using cloud-based services to leverage open source software ==

* Erik Mitchell, Wake Forest University, mitcheet at wfu dot edu

Open source software and cloud computing systems are perceived as enticing technologies for both IT staff and IT/Academic administrators. The implementation of open source software or adoption of cloud services is often met with resistance however because of lack of technical expertise in smaller organizations or lack of perceived benefit in larger organizations. Although these technologies are not necessarily related when combined they offer easy deployment of services without significant organization investment or local expertise [http://cloud.lib.wfu.edu/blog/gazette/2010/11/04/finding-ways-to-combine-cloud-computing-and-open-source-software/]. This ability allows organizations to leverage open source systems without the overhead typically associated with "free as in a free kitten."

While there are some large national projects looking at using cloud platforms to deliver new services there is an opportunity for a grassroots effort to develop and support pre-configured application servers that are simple to deploy and maintain. These 'disposable' servers would serve the needs of both small and large libraries by enabling them to adopt open source software without taking on the requirement of local infrastructure, configuration, or detailed support.

This presentation will cover the technical details and lessons learned from efforts to create this type of service [http://cloud.lib.wfu.edu/blog/tech/2010/11/01/running-the-zsr-vufind-application-server/] on the Amazon EC2 platform and discuss the impact of this approach on open software adoption and its potential impact on IT support in libraries.

== VIVO: Enabling National Networking of Scientists ==

* Brian Keese, Indiana University, bkeese at indiana dot edu
* Brian Lowe, Cornell University, bjl23 at cornell 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.

== Mass Moves with Worldcat APIs ==
* Sam Kome, Claremont Colleges Library, sam.kome at cuc dot claremont dot edu

Claremont needed to perform a mass evaluation of item level records to facilitate large scale collection moves and de-accession. Our de-accession criteria, for example, include that 3 or more copies of any book must be available in the 50+ libraries in our Link+ network. We addressed our requirements with the help of the OCLC Worldcat Search and xID APIs and a couple simple python scripts. The process was ultimately a success. We will present our approach, code, and the lessons learned as we discovered limits inherent in the APIs and in our own coding (in)experience. Bonus sub-topic: the use of OCLC Work ID to identify and coalesce alternative ISBNs.

== A Simple Algorithm for User Query Classification & Resource Recommendation ==
* Josh Bishoff, University of Illinois, bishoff2 at illinois dot edu

One of the longstanding problems in library services is how we might automatically direct users to the most appropriate personnel, databases or facilities to meet their information need. Utilizing the faceted navigation features of various next-gen catalogs, we can efficiently & very accurately assign subject domains to user search queries.

For example: if a user searches “Gallium Arsenide” in the library discovery layer, we can first broadcast this query to a suitably large OPAC and receive the following subject distribution:

-Engineering & Technology: 45%

-Physical Sciences: 21%

-Education: 9%

…and so on.

By leveraging the cataloging efforts that have classified large collections, we can efficiently classify queries with a high rate of accuracy. By applying this approach to the library discovery layer, we can offer users tailored result sets from subject-specific A & I services. We can also recommend subject specialists & most appropriate campus libraries.

This presentation will discuss the technical challenges of implementing such a system and the trouble with mapping traditional subject classifications to non-book resources (databases, people, buildings, etc.). The dangers of ''incorrect'' automatic query classification will be discussed, along with strategies to combat this. A functional system will be demonstrated and code will be made available.

== Beyond Sacrilege: A CouchApp Catalog ==
* Gabriel Farrell, Drexel University, g@grrawr.com
At Code4LibCon2008 Dan Scott gave us a taste of yummy CouchDB, a document-oriented database with a RESTful JSON API (http://couchdb.org/). Since then, CouchDB has passed the 1.0 mark and landed on desktops, the cloud, and mobile devices. With the advent of CouchApps (web apps served directly from CouchDB) applications can be built that are as easy to install as the replicating of databases (which is super easy!). I’ll discuss the advantages and challenges in designing a CouchApp to be used as a catalog, repository, or directory of resources. Some things are made fairly simple, such as site templating, the outputting of documents in different formats, and the attachment of binary objects to documents. Some things, like document versioning and the modeling of data, are a little trickier, but still straightforward. And some things, such as granular authentication and the integration of search, are tangled enough to produce some head-on-wall banging. But hey, take it easy. It’s time to relax.

Check out some code at http://github.com/gsf/catlg.

2011talks Submissions

2010-11-12T19:53:04Z

Gsf: Added talk

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.

See the [http://wiki.code4lib.org/index.php/2011talkscall_Call_for_Submissions Call for Submissions] for guidelines on appropriate topic talks and the criteria on which submissions are evaluated.

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.

== We Don’t Server Their Kind : Managing E-resources with Flat-File Databases ==
* Junior Tidal, Multimedia and Web Services Librarian, New York City College of Technology, CUNY (jtidal at citytech dot cuny dot edu)
Managing E-resources can be a daunting challenge. URLs, database names, and even vendors can change, go down, or simply cease to exist. My proposal involves the use of a PHP-based, flat-file database driven web tool for database management. The design of this program was to fulfill two needs: ease of use for librarians with a lack of programming experience and to meet the security and technical restrictions placed by the college’s IT department. My presentation will explore the development of this tool, challenges within its development, and future improvements. PHP code and the flat-file database will also be explained and provided to attendees. For a working demonstration feel free to visit the New York City College of Technology’s A-Z database [http://library.citytech.cuny.edu/research/AToZ/index.php page] or the subject database [http://library.citytech.cuny.edu/research/subject/index.php page].

== Drupal 7 as a Rapid Application Development Tool ==

* Cary Gordon, President, The Cherry Hill Company & Board Member, The Drupal Association (cgordon at chillco dawt com)
Five years ago, I discovered that the Drupal CMS had a programming framework disguised as an API, and learned that I could use it to solve problems.

Drupal 7 builds on that to provide a powerful toolset for interfacing with, manipulating and presenting data. It empowers tool-builders by providing a minimal install option, along with a more powerful installation profile system makes it easier for developers to package and distribute their applications.

== Helping Open Source Succeed ==

* [[User:DataGazetteer|Peter Murray]], LYRASIS, [mailto:Peter.Murray@lyrasis.org Peter.Murray@lyrasis.org]
* Tim Daniels, LYRASIS, [mailto:Tim.Daniels@lyrasis.org Tim.Daniels@lyrasis.org]

Deciding if open source is an option for your institution, or what open source software matches your institution’s needs and capabilities, is a complex decision. LYRASIS is developing a new area of focus to assist libraries with decision tools and an open source software registry. We want to learn from the creators of open source software what questions institutions have when considering the adoption of open source software and what information you would like to see in a registry that compares various open source tools. A summary of topics discussed in this session will be openly published as part of LYRASIS’ program development plans and decision support resources.

The mission of the new and emerging LYRASIS Technology Services area is to serve members and the broader library community as a provider of expertise and capacity in open source based technology solutions. We think that viable roles for an organization supporting open source software are to: a) Increase understanding of open source technology within the library community, including value, benefits, risks, and costs; b) Assist in decision-making by providing resources to help libraries evaluate open source technologies, institutional readiness, and capacity for adoption; c) Support adoption and use of open source technologies and systems within libraries and consortia; d) Foster integration of open source software tools to expand the ability of existing programs to meet a range of library user needs; e) Develop and test new open source software programs, and contribute to the development of existing programs; f) Support long-term sustainability of viable, library-based open source software and systems. We recognize that these roles exist to some extent on a continuum, with latter services related to development and sustainability building on the knowledge and experience gained through deployment of existing open source systems. In turn, effective adoption and use depends on understanding open source systems and having resources to assist in decision-making and implementation.

With open source software in the “innovator” and “early adopter” stages in the library community, we intend to focus its initial efforts on roles A-D in the above list: increased understanding, decision-support, and effective adoption and integration of existing library-focused open source systems. This session is focused on the decision-support services area of activity.

The impact of this session is expected to be far reaching, if initially subtle. With most of the session time devoted to discussion and interaction among peers on questions surrounding the adoption of open source software, participants will take away a deeper understanding of topics each institution should consider when looking at open source software. These findings, along with that of similar sessions around the country, will inform the creation and expansion of the free decision support tools being developed by LYRASIS.

== Letting in the light: using Solr as an external search component ==

* Jay Luker, IT Specialist, ADS (jluker at cfa dot harvard dot edu)
* Benoit Thiell, software developer, ADS (bthiell at cfa dot harvard dot edu)

It’s well-established that [http://lucene.apache.org/solr/ Solr] provides an excellent foundation for building a faceted search engine. But what if your application’s foundation has already been constructed? How do you add Solr as a federated, fulltext search component to an existing system that already provides a full set of well-crafted scoring and ranking mechanisms?

This talk will describe a work-in-progress project at the [http://adswww.harvard.edu/ Smithsonian/NASA Astrophysics Data System] to migrate its aging search platform to [http://invenio-software.org/ Invenio], an open-source institutional repository and digital library system originally developed at CERN, while at the same time incorporating Solr as an external component for both faceting and fulltext search.

In this presentation we'll start with a short introduction of Invenio and then move on to the good stuff: an in-depth exploration of our use of Solr. We'll explain the challenges that we faced, what we learned about some particular Solr internals, interesting paths we chose not to follow, and the solutions we finally developed, including the creation of custom Solr request handlers and query parser classes.

This presentation will be quite technical and will show a measure of horrible Java code. Benoit will probably run away during that part.

== Working with DuraCloud: How to preserve your data in the cloud ==

* Bill Branan, DuraSpace, bbranan at duraspace dot org
* Andrew Woods, DuraSpace, awoods at duraspace dot org

Ever expanding digital collections have become the norm in academic libraries. As the size of collections grow, the need for simple-to-deploy yet powerful preservation strategies becomes increasingly important. The [http://duracloud.org DuraCloud] project, a cloud-hosted service for data management and preservation, is committed to bringing the availability and elasticity of the cloud to bear on the issue of digital preservation. This session will discuss the APIs and tools which can be used to communicate and integrate with the DuraCloud platform, providing an immediate connection to scalable storage available from multiple cloud storage providers, configurable services which can be run over your content out-of-the-box, and a development platform which can serve as the basis for ongoing data mining and analysis.

== Visualizing Library Data ==

* Karen Coombs, OCLC, coombsk at oclc dot org

Visualizations can be powerful tools to give context to library users
and to provide a clear picture for data-driven decision-making in
libraries. Map mashups, tag clouds and timelines can be used to show
information to users in new ways and help them locate materials to meet
their needs. QR codes can help link users to materials that libraries
have in their collections. Charts and graphs can be used to help analyze
library collections (holdings) and compare them to other libraries. This
session will show prototypes which combine tools like Google Chart API,
Protovis and Simile Widgets with data from WorldCat, WorldCat Registry,
Classify, Terminology Services, and Dewey.info to create vivid
illustrations in library user interfaces and administration tools.

== Kuali OLE: Architecture for Diverse and Linked Data ==

* Tim McGeary, Lehigh University, Kuali OLE Functional Council, tim dot mcgeary at lehigh dot edu
* Brad Skiles, Project Manager, Kuali OLE, Indiana University, bradskil at indiana dot edu

With programming scheduled to be begin in January 2011 on the Kuali Open Library Environment (OLE), the Kuali OLE Functional Council is developing the requirements for an architecture for diverse data sets and linked data. With no frontrunner for one bibliographic data standard, and local requirements on what data will be accompanying or linked to the main record store, Kuali OLE needs to build a flexible environment for records management and access.

We will present the concepts of our planned architecture, a multi-repository framework, using a document repository, a semantic repository, and a relational repository, brokered on top of the enterprise service bus of Kuali Rice. As a community source project, this is an opportunity for the Kuali OLE partners to present our plans for discussion with the community, and we look forward to feedback, questions, and comments.

== One Week | One Tool: ultra-rapid open source development among strangers ==

* Scott Hanrath, University of Kansas Libraries, shanrath at ku dot edu
* Jason Casden, North Carolina State University Libraries, jason_casden at ncsu dot edu

In summer 2010, the Center for History and New Media at George Mason University, supported by an NEH Summer Institute grant, gathered 12 'digital humanists' for an intense week of collaboration they dubbed 'One Week | One Tool: a digital humanities barn raising.' The group -- several of whom hang their professional hats in libraries and most of whom were previously unacquainted -- was asked to spend one week together brainstorming, specifying, building, publicizing, and releasing an open source software tool of use to the digital humanities community. The result was Anthologize, a free, open-source, plugin that transforms WordPress into a platform for publishing electronic texts in formats including PDF, ePub, and TEI; in other words, a "blog-to-book" tool. This presentation will focus on how One Week | One Tool addressed the challenges of collaborative open source development. From the perspectives of two library coders on the team, we will describe and provide lessons learned from the One Week development process including: how the group structured itself without predefined roles; how the one week time frame and makeup of the group -- which included scholars, grad students, librarians, museum professionals, instructional technologists, and more -- influenced planning and development decisions; the roles of user experience and outreach efforts; the life of Anthologize since the end of the week; and thoughts on what a one week, one 'library' tool could look like.

== Improving the presentation of library data using FRBR and linked data ==

* Anne-Lena Westrum, Oslo Public Library (annelena at deichman dot no)
* Asgeir Rekkavik, Oslo Public Library (asgeirr at deichman dot no)

The Pode project at Oslo Public Library has experimented on the automated FRBRizing of catalogue records, as well as expressing bibliographic descriptions as linked data to enrich catalogue browsing with information from external sources.

When a library enduser searches the online catalogue for works by a particular author, he will typically get a long list that contain all the different translations and editions of all the books by that author, sorted by title or date of issue. The Pode project applied a method of automated FRBRizing, based on the information contained in MARC records, RDF representation and SPARQL queries, to demonstrate how an author's complete production can be presented as a lucid list of unique works, that can easily be browsed by their different expressions and manifestations. Furthermore, by linking instances in the dataset to matching or corresponding instances in external sets, the presentation can be enriched with additional information about authors and works, as well as links to electronic full-text representations.

The talk will also present the work on making an RDF representation of the catalogue records for the whole collection of non-fiction documents at the Norwegian Multilingual library, linking subject headings and Dewey classes, and allowing endusers to browse the collection by the multilingual Dewey class labels published by OCLC at http://dewey.info.

The talk will focus on the challenges technological progresses such as these raise for cataloguers, to deliver consistent and standardized catalogue records. Many cataloguers have a local and pragmatic focus on the library's own and already existing services. Attitudes like this might represent a problem when emerging technologies find new applications for library catalogue data, as well as when the library wants to use data submitted by others to enrich their own services.

== Touch and go: building a touch screen kiosk with software you already own ==

* Andreas K. Orphanides, North Carolina State University Libraries, akorphan at ncsu dot edu

In October 2010, the NCSU Libraries debuted its first public touch-screen information kiosk, designed to provide on-demand access to useful and commonly consulted real-time displays of library information. With the exception of the touchscreen itself, the system was created using commonly available free software and off-the-shelf hardware. In this presentation, I will describe the process for creating the touchscreen interface that is used in this kiosk. I will walk through the challenges of developing for a touch-optimized environment in HTML and JavaScript; I will describe how free utilities and web browser plugins may be combined to secure a public touchscreen kiosk; and I will present a data analysis of touchscreen usage since the kiosk's rollout to evaluate content selection and interface design.

== Next-L Enju, NDL Search and library geeks in Japan ==

* Kosuke Tanabe, Keio University, tanabe at mwr dot mediacom dot keio dot ac dot jp

[http://github.com/next-l Next-L Enju ] is an open source integrated library system developed by Project Next-L, the library geek community in Japan launched on November 2006. It is built on open-source software (Ruby on Rails, PostgreSQL/MySQL and Solr) and supports modern ILS features (e.g. FRBR structure and RESTful WebAPI).

Enju has been inplemented by some libraries, which include National Diet Library (NDL), the largest library in Japan. NDL has chosen Enju to provide a new search engine, called "NDL Search" and added some extra features (e.g. automatic FRBRization and providing bibliographic data in a Linked Data format) . The development version is available at http://iss.ndl.go.jp/ .

I'm one of the authors of Next-L Enju. I'd like to talk about the overview and structure of Next-L Enju, NDL Search and the activities of our project.

== A community based approach to developing a Digital Exhibit at Notre Dame using the Hydra Framework ==

* Rick Johnson, University of Notre Dame, (rick dot johnson at nd dot edu)
* Dan Brubaker Horst, University of Notre Dame (dbrubak1 at nd dot edu)

It was clear to us early on that the scope of managing, preserving, and interacting with digital content is too much for any one institution to conquer by itself. We realized that we need help.

We were already fairly convinced using Fedora, Solr, and ActiveFedora were solid choices because of their strong development community and flexible robust solutions. We were also exploring Blacklight for search and browse for the same reasons. The open questions were:

* What is the best way to put the pieces together?
* How do you tackle the heterogenous content types and workflows without getting bogged down in each individual solution?

Enter Code4Lib2010...

After connecting with folks from the Hydra project at Code4Lib it was immediately clear that we had many things in common:
* The same architectural choices: Fedora, Solr, ActiveFedora, Blacklight
* Similar design philosophies
* A need to work together
* Too many shared use cases to ignore

So, we jumped on board and have adopted the Hydra Framework for all of our Digital Repository efforts.

In our presentation we will cover:
* Why we chose to adopt the Hydra Framework instead of creating our own solution
* Why the community based approach is so appealing
* How we were welcomed into the Hydra development community
* Why we chose to create something beyond basic Blacklight search and facet browse
* How to create your own Digital Exhibit using Hydra including
** Metadata management
** Custom Browse and Search

The Hydra Project is actively seeking partnerships with other institutions to extend its efforts. Will your institution be next?

More about the [https://wiki.duraspace.org/display/hydra/The+Hydra+Project Hydra Project]

== Mendeley's API and University Libraries: 3 examples to create value ==

* Jan Reichelt, Co-Founder, 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.

Based on this platform and data, I will present three examples of how Mendeley is working to support university libraries and contribute to opening up academic research:
1) Mendeley’s integration as a workflow tool with institutional repositories with the aim of increasing IR deposit rates;
2) Application examples building on Mendeley’s API to showcase what is possible with the newly available type of usage data Mendeley is aggregating;
3) Preview of Mendeley’s library dashboard that will reveal content usage within an institution.

I would also hope that a subsequent discussion can address how you (the attendees) could envision Mendeley’s future in the library tech community.

== ArticlesPlus: Summon API Client Implementation and Integration with Drupal 6 ==

* Albert Bertram, University of Michigan (bertrama@umich.edu)

On September 27, 2010, the University of Michigan launched ArticlesPlus, an application for web-scale article discovery using the Serials Solutions' Summon service as its search engine. Rather than providing a search box which sent our patrons to the interface provided by Serials Solutions, we used Summon's API to integrate the search as a feature of our library's website. In addition to Summon as the search engine, we used our Drupal instance for the interface engine.

I propose to talk about how we implemented the Summon API, the Drupal module we developed in to access the Summon API, problems with implementing an interface ourselves, benefits of implementing the interface ourselves, and plans for future expansion or improved integration in our website.

== Let's Get Small: A Microservices Approach to Library Websites ==

* Sean Hannan, Johns Hopkins University, shannan at jhu dot edu

Most, if not all, library websites are housed and maintained in singular, monolithic content management systems. This is fantastic if the library website is the one place your users go for library information. But it isn't. Users are going to Facebook, checking mobile applications, browsing portals as well as checking the library website. Wouldn't it be great if you could update the information on all of these sites from a single source? Why maintain the library hours in five different places?

In this talk, I will show how breaking the construction of the library website into as-needed, swappable microservices can free your content to live where it needs to, as well as free you from the maintenance headaches usually involved. What kind of microservices, you ask? Well, basic templating and styling is a given, but how about a microservice that gracefully degrades your layouts for older browsers? Or enforces highfalutin typographic rules? Or optimizes your site assets to improve load times? All wonderful little black boxes that allow you to focus on the website and its content, and not the details.

I promise at least one diagram. That will burn your eyes.

[[Category:Code4Lib2011]]

== Sharing Between Data Repositories ==

* Kevin S. Clarke, NESCent/Dryad Data Repository, ksclarke at nescent dot org

Dryad (http://datadryad.org) is a generic subject repository that shares author submitted data with other scientific repositories. In a
part "how we done it" and part "things to consider" talk, I'll discuss 1) why we chose BagIt and OAI-ORE as mechanisms for sharing our data, 2) how
we've integrated with TreeBASE (http://www.treebase.org/ -- a subject repository of phylogenetic information), and 3) the possibility of this
method of data sharing being adopted by other repositories within the larger DataONE community.

There will be cake.

== Hey, Dilbert. Where’s my data?! ==

* Tommy Barker, University of Pennsylvania, tbarker at pobox dot upenn dot edu

Libraries are notorious for maintaining data in massively disparate systems such as databases, flat files, xml and web services. The data is rich and valuable to assessment, but extracting value from multiple systems is complex and time consuming. Yes, there are open source and commercial solutions available, but libraries have unique requirements that can be difficult to integrate into these products. Commercial options also tend to be overly complex or the cool features require an expensive enterprise edition.

With funding from the Institute of Museum and Library Services, UPenn is developing MetriDoc to address data integration headaches within the library, and support reporting requirements from management. MetriDoc’s mission is to provide an open source API / tool set where users can specify dataflows and use library based services to solve integration problems while MetriDoc worries about scalability and performance. MetriDoc accomplishes this with no complex xml configuration or scary SOA middleware, but instead uses a simple DSL where possible. Eventually the project will also include dashboards to assist with complex job management and data flow monitoring.

The first half the presentation briefly discusses MetriDoc’s architecture while the remainder of the presentation will include code samples to illustrate problems it can solve. Information on how to contribute or download MetriDoc will be provided as well.

== Open Data and the Biodiversity Heritage Library experience ==

* Trish Rose-Sandler, Missouri Botanical Gardens, trish dot rose dash sandler at mobot dot org

The Biodiversity Heritage Library (BHL) is an international consortium of the world’s leading natural history museum libraries, botanical libraries, and research institutions organized to digitize, serve, and preserve the legacy literature of biodiversity. From the beginning the BHL partners conceived of the BHL collection as being “open” – available to anyone regardless of geographic location or affiliation and a linked into a global Biodiversity Commons. This talk will discuss the basic principles of open data and use BHL as one example of how those principles have played out in a real world context.

What does it mean for data to be “open” and what tools or services can enable this? Our metadata is purposely “open” so that others can harvest it and repurpose it in different contexts. We make it available through both OAI-PMH and APIs.

If you “open” your data will they come? In some cases yes. BHL can give examples of scientists and science services, who have taken our data and exploited it for other purposes (e.g. BioStor, Earthcape, EOL, ZipcodeZoo) Yet, in a recent BHL survey we learned that of our frequent users, 42% were not aware that we provided APIs and 31% did not understand what APIs were. Clearly promotion of your open data is a key activity to making it truly useful.

What are some advantages to open data? Harvestable data allows that data which was created for a specific purpose and audience (e.g. historic texts, nomenclatural services, encyclopedias) to interact with other data and serve new, previously unimagined, roles. For BHL, opening our data it was a desire to do three things 1) make biodiversity data available to foster scientific research 2) support the public use of these data and 3) build a web of science.

== The Road to SRFdom: OpenSRF as Curation Microservices Architecture ==

* Dan Coughlin, Digital Library Technologies, Penn State University ITS (danny@psu.edu)
* Mike Giarlo, Digital Library Technologies, Penn State University ITS (michael@psu.edu)

OpenSRF is the XMPP-based framework that underlies the Evergreen ILS, providing a service-oriented architecture with failover, load-balancing, and high availability. Curation microservices represent a new approach to digital curation in which typical repository functions such as storage, versioning, and fixity-checking are implemented as small, independent services. Put them together and what do you have?

The next phase of Penn State's institutional digital stewardship program will involve prototyping a suite of curation services to enable users to manage and enrich their digital content -- we’re just about to get started on this, at the time this proposal was written. The curation services will be implemented following the microservices philosophy, and they will be stitched together via OpenSRF. We will talk about why we chose the “road to SRFdom,” colliding the ILS world with the repository world, how we implemented the curation services & architecture, and how OpenSRF might be helpful to you. Code will be shown, beware.

== Enhancing the Performance and Extensibility of the XC’s MetadataServicesToolkit ==

* [http://tech.benanderson.us Ben Anderson], [http://www.extensiblecatalog.org/ eXtensible Catalog Organization], banderson@library.rochester.edu

Learn how we increased the performance of the [http://code.google.com/p/xcmetadataservicestoolkit/ XC Metadata Services Toolkit] (MST) by over 900%. The MST is an open-source Java application, that uses SOLR and MySQL to harvest (OAI-PMH) library metadata (MARC, DC), clean it up, convert and frbrize, and then make new metadata (RDA flavor, XC Schema) available for harvesting. Our first release performed too slowly with degrading performance with large record batches and we needed to enable the MST to process a library’s entire catalog in a reasonable amount of time on a common server. The MST was also intended to be extensible. Libraries will almost certainly want to customize this process in some way. Thus our second goal was to make it is as easy as possible for a developer to write a service which can be plugged into the MST.

In the spring of ‘10 we set out to accomplish our 2 goals. The first task was to establish how close the existing MST was to these goals. More concretely, our goal was to be able to process 1M MARC records/hr and have little to no degradation as the MST processed several million records. The first service in our chain of services, the normalization service, served as our initial metric. The normalization service was processing records at a speed of 125k/hr, much slower than we hoped for. On top of that, before processing 2M records, the MST essentially crawled to a halt. We were about an order of magnitude off and we needed to increase scalability in a substantial way as well. Also, examining the steps involved in writing a new service for the MST showed us that it was not easy to do so. Internals of the MST were exposed to the service developer and the developer was expected to re-implement much of this internal code with no instructions on how to do so. Much work needed to be done to abstract the implementation of the MST away from the service developer.

Working hard over the course of several months, we were able to accomplish both of our goals. The MST is now processing records at a speed of 1.2M records/hr with no degradation on a set of 6M records on a less than optimal server (1.5GHz cpu). In this talk, I will detail the specifics of the strategies we used to accomplish this major speed enhancement (such as a shift from Apache SOLR to a hybrid SOLR/MySQL approach). In regards to our second goal, third party developers can now download an MST development environment, write a few lines of code, and package their service for deployment into the MST. Third party developers need not concern themselves with the details of the internal MST implementation. In this talk, I will also walk through [http://code.google.com/p/xcmetadataservicestoolkit/wiki/HowToImplementService the steps] required to write a service for the MST.

== Free my DSpace Data! How to get your data out of DSpace 1.7 and restore your content after a disaster. ==

* Tim Donohue, DuraSpace, tdonohue at duraspace dot org

For a while, [http://www.dspace.org DSpace] has provided many means to get content into the system (or create new content in the system), e.g. basic ingest packages, user interfaces, SWORD. However, getting your content out of DSpace, especially for backups or migrations has often been problematic. In the past, although individual Items could be exported in standard formats, entire Collections or Communities (and the relationships between them) could not be as easily exported.

DSpace 1.7.0 provides a new [https://wiki.duraspace.org/display/DSDOC/AipBackupRestore AIP Backup & Restore feature] which allows DSpace to export '''all''' of its contents (Communities, Collections, Items, Groups, People, Permissions, and relationships between all objects) into a series of METS-based Archival Information Packages (AIPs). As these AIPs are just zip files, they can be backed up using your normal backup practices (e.g. to tape, hard-drive, or even to the cloud via a service like DuraCloud). As these AIPs also fully describe your DSpace contents, they can be used to restore your entire DSpace after a local server crash or larger disaster.

DSpace created AIPs use standard library metadata formats like MODS, PREMIS and METSRights (along with a few DSpace-specific ones where a "standard format" doesn't yet exist) to describe all the content housed in your DSpace installation. This comes in handy, should you ever decide to migrate some or all of your contents to another DSpace instance or another system altogether.

This talk will describe this new DSpace AIP Backup & Restore feature, provide hints/tips on how it can be used to backup/restore/migrate data. Time permitting, I can also touch on the DSpace Roadmap and other ideas/plans to "free your DSpace data".

== Using cloud-based services to leverage open source software ==

* Erik Mitchell, Wake Forest University, mitcheet at wfu dot edu

Open source software and cloud computing systems are perceived as enticing technologies for both IT staff and IT/Academic administrators. The implementation of open source software or adoption of cloud services is often met with resistance however because of lack of technical expertise in smaller organizations or lack of perceived benefit in larger organizations. Although these technologies are not necessarily related when combined they offer easy deployment of services without significant organization investment or local expertise [http://cloud.lib.wfu.edu/blog/gazette/2010/11/04/finding-ways-to-combine-cloud-computing-and-open-source-software/]. This ability allows organizations to leverage open source systems without the overhead typically associated with "free as in a free kitten."

While there are some large national projects looking at using cloud platforms to deliver new services there is an opportunity for a grassroots effort to develop and support pre-configured application servers that are simple to deploy and maintain. These 'disposable' servers would serve the needs of both small and large libraries by enabling them to adopt open source software without taking on the requirement of local infrastructure, configuration, or detailed support.

This presentation will cover the technical details and lessons learned from efforts to create this type of service [http://cloud.lib.wfu.edu/blog/tech/2010/11/01/running-the-zsr-vufind-application-server/] on the Amazon EC2 platform and discuss the impact of this approach on open software adoption and its potential impact on IT support in libraries.

== VIVO: Enabling National Networking of Scientists ==

* Brian Keese, Indiana University, bkeese at indiana dot edu
* Brian Lowe, Cornell University, bjl23 at cornell 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.

== Mass Moves with Worldcat APIs ==
* Sam Kome, Claremont Colleges Library, sam.kome at cuc dot claremont dot edu

Claremont needed to perform a mass evaluation of item level records to facilitate large scale collection moves and de-accession. Our de-accession criteria, for example, include that 3 or more copies of any book must be available in the 50+ libraries in our Link+ network. We addressed our requirements with the help of the OCLC Worldcat Search and xID APIs and a couple simple python scripts. The process was ultimately a success. We will present our approach, code, and the lessons learned as we discovered limits inherent in the APIs and in our own coding (in)experience. Bonus sub-topic: the use of OCLC Work ID to identify and coalesce alternative ISBNs.

== A Simple Algorithm for User Query Classification & Resource Recommendation ==
* Josh Bishoff, University of Illinois, bishoff2 at illinois dot edu

One of the longstanding problems in library services is how we might automatically direct users to the most appropriate personnel, databases or facilities to meet their information need. Utilizing the faceted navigation features of various next-gen catalogs, we can efficiently & very accurately assign subject domains to user search queries.

For example: if a user searches “Gallium Arsenide” in the library discovery layer, we can first broadcast this query to a suitably large OPAC and receive the following subject distribution:

-Engineering & Technology: 45%

-Physical Sciences: 21%

-Education: 9%

…and so on.

By leveraging the cataloging efforts that have classified large collections, we can efficiently classify queries with a high rate of accuracy. By applying this approach to the library discovery layer, we can offer users tailored result sets from subject-specific A & I services. We can also recommend subject specialists & most appropriate campus libraries.

This presentation will discuss the technical challenges of implementing such a system and the trouble with mapping traditional subject classifications to non-book resources (databases, people, buildings, etc.). The dangers of ''incorrect'' automatic query classification will be discussed, along with strategies to combat this. A functional system will be demonstrated and code will be made available.

== Beyond Sacrilege: A CouchApp Catalog ==
* Gabriel Farrell, Drexel University, g@grrawr.com
At Code4LibCon2008 Dan Scott gave us a taste of yummy CouchDB, a document-oriented database with a RESTful JSON API ([http://couchdb.org/]). Since then, CouchDB has passed the 1.0 mark and landed on desktops, the cloud, and mobile devices. With the advent of CouchApps (web apps served directly from CouchDB) applications can be built that are as easy to install as the replicating of databases (which is super easy!). I’ll discuss the advantages and challenges in designing a CouchApp to be used as a catalog, repository, or directory of resources. Some things are made fairly simple, such as site templating, the outputting of documents in different formats, and the attachment of binary objects to documents. Some things, like document versioning and the modeling of data, are a little trickier, but still straightforward. And some things, such as granular authentication and the integration of search, are tangled enough to produce some head-on-wall banging. But hey, take it easy. It’s time to relax.

Check out some code at [http://github.com/gsf/catlg].

Main Page

2010-11-04T19:13:49Z

Gsf: /* Code4libcon 2009 */ Higher level of heading

__NOTOC__
= Code4Lib Wiki =

== About Code4Lib ==

* [[About Code4Lib]] - Background and history of the community
* [[A Guide for the Perplexed]] - Building skills for working with library technologies

== Local / Regional Groups ==

* [[NYC|Code4LibNYC]] - NYC and surrounding areas
* [[NEC4L|New England Code4lib]] - New England
* [http://se.code4lib.org Southeastern Code4lib] - North Carolina, Virginia, Tennessee, etc.
* [[NL|Code4Bib]] - Dutch Code4Bib
* [[MDC|Code4libMDC]] - Maryland, Washington D.C and surrounding areas
* [http://groups.google.com/group/pnwcode4lib?hl=en PNWCode4Lib] - Pacific Northwest
* [[North|code4lib North]] - Ontario and surrounding areas ''(new for Jan 2010!)''
* [[Midwest|Code4Lib Midwest]] - Wherever that is...
* [http://groups.google.com/group/ikr-fejlesztok/ Code4lib.hu] - Group of Hungarian library developers
* [http://www.code4lib.jp/ Code4Lib Japan] - ''(new in 2010!)'', see also [http://twitter.com/yesonline/statuses/28561046501 tweet from Jerry Lee]

== Interest Groups ==

* [[ILS_Interop|ILS Interoperability]] - A group working to develop an infrastructure for interoperating between discovery layers and integrated library systems.
* [[Open_Source_Book_Widgets|Open Source Book Widgets]] - A list of open source book widgets
* [[Discovery|Open Source Discovery]] - Open Source application to enhance and support "discovery" in libraries
* [[Mobile_Apps|Mobile Applications]] - A group interested in mobile web and native application development for libraries
* [[Sources_Of_Metadata|Sources Of Metadata]] - list of api's and sources of interest to libraries

== Software Usage and Documentation ==

* [[Umlaut]] - OpenURL link resolving middleware
* [[:Category:Patterns|Patterns for Collaborative Code]] - Patterns to make your open source 'more open', more amenable to distributed development and use at multiple institutions without forking.
* [[ILS Documentation]]
* [[OSS Directory]]
* [[Working with MaRC]]
* [[Rogue]] - principles for standards creation

== Code4lib Journal ==

* [[:Category:Code4Lib Journal|Code4Lib Journal]] - information and working documents

== Current topics ==

* [[OCLC Policy Change]]
* [[SirsiDynix: Integrated Library System Platforms on Open Source]]

== Other Code4Lib Sites ==

* [http://www.code4lib.org/ code4lib.org]
* [http://planet.code4lib.org planet.code4lib.org]

== Code4Lib 2011 Conference ==
''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2011 Code4lib2011 category]''

* [[2011_nominations_list|Keynote Nominations]] and [http://vote.code4lib.org/election/index/16 Vote]
* [[2011talkscall_Call_for_Submissions]] - sign up to give a prepared talk
* [[2011_Preconference_Proposals]] - sign up to present a day long or half-day preconference
* [[2011 Lightning Talks Signup]] - sign up to give a lightning talk
* [[2011 Breakout Sessions]] - suggest a breakout here
* '''[[2011 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff'''
* [[C4L2011_social_activities|Social Activities]] - ideas & sign-up
* [[2011_committees_sign-up_page | 2011 Committees Sign-Up]] - '''Volunteer to help'''
* [[C4L2011_planning_wishlist|'''Put your ideas for 2011 here!''']]

== Earlier Conferences and events ==

== Code4libcon 2010 ==
''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2010 Code4lib2010 category]''
* [http://code4lib.org/conference/2010/schedule Finalized schedule]
* [[2010 Lightning Talks Signup]] - sign up to give a lightning talk
* [[2010 Breakout Sessions]] - suggest a breakout here
* '''[[2010 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff'''
* [[C4L2010_social_activities|Social Activities]] - ideas & sign-up
* [[Committees sign-up page]] - '''Volunteer to help'''
* [[C4L2011_planning_wishlist|'''Put your ideas for 2011 here!''']]

=== Transportation ===
* [[Asheville Airport to Hotel Van Manifest]]
* [[C4L2010rideshare|General shared travel/transportation planning]]
* [[C4L2010planning:RoommatesRidesEtc|Roommates, Rides, Etc]]

=== Deals ===
* [[C4L2010_manning_discount|Manning Publications Discount]] - discount code (40% off) for use by attendees through Feb. 28, 2010
* Thanks also to our other sponsors!

=== Asheville planning ===
* [[C4L2010planning|2010 Planning]]
* [[C4L2010planning:_wishlist | 2010 Planning Wishlist]] - planning page for issues, expectations, etc. for the 2010 conference

== Code4libcon 2009 ==
* [[BookRaffle]] - coordinate begging publishers for books to raffle off at the conference
* [http://inkdroid.org/c4l2009/attendees Get FOAFed] - add your FOAF profile to the network of c4l2009 attendees
* PreConferences:
** [[GIS_preconf_code4libcon2009]] - Open source GIS just like mom used to make
** [[LinkedData]] - A proposal for a linked-data code4lib2009 pre-conference
** [[LibX_Preconference]] - Proposal for a half-day pre-conference targeted at developers who wish to use the LibX 2.0 platform
** [http://code4lib.org/2009/oclc-precon OCLC Grid Services Preconference]
* [[RoommatesRidesEtc]] - Find roommates for Code4Lib 2009, share rides, etc.
* [[2009 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff

=== Other workshops ===
* [http://barcamp.org/SearchCampDC SearchCampDC] - barcamp style event in DC with usual suspects from code4lib
* [[code4lib/elag2010]] - 1-day code4lib preconference at elag2010

== Archived topics ==

* [[Logo Design Process]]

[[AdminToDo]] - ideas and tasks for maintaining the Code4Lib sites

Code4Lib Journal Deadlines

2010-10-27T13:56:39Z

Gsf: /* Deadlines for Issues */ Added deadlines for issue 13

''See also [[Code4Lib Journal Voting]]''

== Formula for calculating deadlines ==

A rough guideline based on recent issues:

{| border="1" cellpadding="2" cellspacing="0"
|-
! Weeks before
! Task
! Day offset
! On
|-
| style="text-align:right" | '''-18'''
| Call for proposals
| style="text-align:right" | -126
| Monday
|-
| style="text-align:right" | '''-14'''
| Proposals due
| style="text-align:right" | -94
| Friday
|-
| style="text-align:right" | '''-13'''
| Publication of previous issue
| style="text-align:right" | -91
| Monday
|-
| style="text-align:right" | '''-13'''
| Finish voting on proposals; notify authors
| style="text-align:right" | -87
| Friday
|-
| style="text-align:right" | '''-9'''
| First draft due
| style="text-align:right" | -59
| Friday
|-
| style="text-align:right" | '''-5'''
| Second draft due
| style="text-align:right" | -31
| Friday
|-
| style="text-align:right" | '''0'''
| Publication
| style="text-align:right" | 0
| Monday
|}

'''Note:''' Week numbers assume week begins on Monday.

'''See also:''' [[Code4Lib_Journal_Email_Templates]] (formerly at [http://groups.google.com/group/c4lj-articles/web/templates-for-email-responses Templates for Email Responses])

== Deadlines for Issues ==
Editors: see also http://tomkeays.com/library/c4ljpubdate/ for Tom's calculator

===Thirteenth issue===

* Call for proposals: Monday, December 6, 2010
* Proposals due: Friday, January 7, 2011
* Proposals accepted: Friday, January 14, 2011
* First draft due: Friday, February 11, 2011
* Second draft due: Friday, March 11, 2011
* Publication date: Monday, April 11, 2011

===Twelfth issue===

* Call for proposals: Monday, August 16, 2010
* Proposals due: Friday, September 17, 2010
* Proposals accepted: Friday, September 24, 2010
* First draft due: Friday, October 22, 2010
* Second draft due: Friday, November 19, 2010
* Publication date: Monday, December 20, 2010

===Eleventh issue===

* Call for proposals: Monday, May 17, 2010
* Proposals due: Friday, June 18, 2010
* Proposals accepted: Friday, June 25, 2010
* First draft due: Friday, July 23, 2010
* Second draft due: Friday, August 20, 2010
* Publication date: Monday, September 20, 2010

=== Tenth issue ===

* Call for proposals: Monday, February 15, 2010
* Proposals due: Friday, March 19, 2010
* Proposals accepted: Friday, March 26, 2010
* First draft due: Friday, April 23, 2010
* Second draft due: Friday, May 21, 2010
* Publication date: Monday, June 21, 2010

=== Ninth issue ===

* Monday, November 9, 2009 -- Call for proposals
* Friday, December 11, 2009 -- Proposals due
* Friday, December 18, 2009 -- Finish voting on proposals, notify authors
* Friday, January 15, 2010 -- First draft due
* Friday, February 12, 2010 -- Second draft due
* Monday, March 15, 2010 -- Publication date

=== Eighth issue ===

* Monday, July 27 -- call for proposals
* Friday, August 14 -- proposals due
* Friday, August 21 -- finish voting on proposals; notify authors
* Friday, September 25 -- first draft due
* Friday, October 23 -- second draft due
* Monday, November 23 -- publication

=== Seventh issue ===

* Monday, February 16 -- call for proposals
* Friday, March 20 -- proposals due
* Monday, March 30 -- publication of issue 6
* Friday, March 27 -- finish voting on proposals; notify authors
* Friday, April 24 -- first draft due
* Friday, May 22 -- second draft due
* Monday, June 22 -- publication

=== Sixth issue ===

* Monday, November 10 -- call for proposals
* Friday, December 12 -- proposals due
* Monday, December 15 -- publication of issue 5
* Friday, December 19 -- finish voting on proposals; notify authors
* Friday, January 23 -- first draft due
* Friday, February 20 -- second draft due
* Monday, March 30 -- publication (originally scheduled for March 23)

=== Fifth issue ===

* Monday, August 18 -- call for proposals
* Friday, September 12 -- proposals due
* Friday, September 19 -- finish voting on proposals; notify authors
* Monday, September 22 -- issue 4 published
* Friday, October 17 -- first draft due
* Friday, November 14 -- second draft due
* Monday, December 15 -- publication

=== Fourth issue ===

* Friday, May 16 -- call for proposals
* Friday, June 20 -- extended proposal deadline (originally 6/13, before issue 3 is published)
* Friday, July 18 -- first draft due
* Friday, August 15 -- second draft due
* Monday, September 22 -- publication

=== Third issue ===

* Wednesday February 13th -- call for proposals
* Friday March 14th -- proposals due (after con, before issue 2)
* Friday April 25 -- first draft due
* Saturday June 21 -- publication (tentative)

=== Second issue ===

* Friday November 9th -- call for proposals
* Friday January 11 -- article draft deadline (or Thurs Jan 21, from EM)
* Thursday February 21 -- revisions/second draft deadline
* Friday March 21 -- publication (tentative)

=== First issue ===

* Friday August 31st -- call for proposals
* Friday October 12th -- article draft deadline
* Monday December 17th -- publication

[[Category: Code4Lib Journal]]

Code4Lib Contact and Mailing List Setup

2010-09-10T21:08:16Z

Gsf: New page: Setup to be written about here.

Setup to be written about here.

Code4Lib Journal

2010-09-10T20:27:11Z

Gsf:

* [http://journal.code4lib.org/ Code4Lib Journal] (homepage)

* [[Code4Lib Editorial Committee Introduction]]

* [[Code4Lib Journal Deadlines]]

* [[Code4Lib Journal Voting]]

* [[Code4Lib Journal Publicity Venues]]

* [[Code4Lib Style Guide]]

* [[Code4Lib Corrections]]

* [[Code4Lib Contact and Mailing List Setup]]

==WordPress==

* [[Code4Lib Journal WordPress Input Guidelines]]
** [[COinS (layman's description)]]

* [[Code4Lib Journal WordPress Customizations]]
* [[Code4Lib Journal Email Templates]]

 
[[Code4Lib Journal Entries in Directory of Open Access Journals]]

[[Code4Lib Journal PDFs]]

[[Category: Code4Lib Journal]]

Citation Format Recommendations

2010-07-21T13:43:19Z

Gsf: /* Voting on Recommended Style: */

[[Category: Code4Lib Journal]]

==== Recommended Reference Style Information: ====

Tim McGeary proposes that the Editorial Committee chose a recommended style for all authors. Authors that do not choose recommended style need to follow another documented style and communicate that to their assigned editor. Using a documented style will provide a clear editorial guidelines for consistency, and ensure proper citations and references of literature and resources.

[http://owl.english.purdue.edu/owl/resource/560/10/ APA Style Example (Purdue)]

[http://www.library.cornell.edu/resrch/citmanage/mla MLA Style Example (Cornell)]

[http://library.osu.edu/help/research-strategies/cite-references/cse/ CSE Style Example (Ohio State)]

jrochkind's proposal: Citations should be clear and unambiguous, and reasonably consistent within an article. Authors are welcome but not required to use a formal style. Editors will ensure readability, clarity, and reasonable consistency of citations, but will not check citations for compliance with stylebooks.

==== Voting on Recommended Style: ====
{| border="1" cellpadding="5" class="sortable"
|- style="text-align: left;"

!Name !! Recommend Style? (Y/N) !! Which Style? (Vote even if N)
|-
| Tim McGeary || Y || CSE
|-
| J Rochkind || N ||
|-
| Carol Bean || Y || CSE
|-
| Staurt Yeates || N || RFC
|-
| MJ Suhonos || N ||
|-
| Ron Peterson || N ||
|-
| Andrew Darby || Y || APA
|-
| Edward Corrado || Y || CSE
|-
| Kelley McGrath || Y || CSE
|-
| Tim Lepczyk || Y || APA
|-
| Tod Olson || Y || CSE
|-
| Tom Keays || Y || CSE
|-
| Gabriel Farrell || Y || CSE
|}

C4L2010planning:RoommatesRidesEtc

2009-12-18T19:43:05Z

Gsf: finally not deleting everything. stupid computers.

== Rides ==

[[Image:Code4lib_bus.jpg|code4lib bus]]

=== Offering ===
Yitzchak Schaffer is tentatively (as of 16 Dec 09, waiting for word on funding approval) organizing a carpool from or through the NYC area to the con in Asheville, NC. See [http://groups.google.com/group/code4libcon/browse_thread/thread/e6dc1df4805cde59] for the original proposal, the idea being to rent a car/van, or use someone's if possible. I do '''not''' plan on attending the precons. Parties expressing interest:

* <strike>Mark Matienzo (NYC)</strike>
* Bess Sadler (VA)
* Mike Giarlo (State College, PA, but can take train to Philly)
* Jennifer (Boston MA, has car)
* Erin White (Richmond, VA)
* Kevin Reiss (New Jersey - Exit 10)

A new section for precon people:
* Anna Headley (Philly PA) have car but not attached to using it (won't fit 5 if we want to avoid violence -- 4 max)
* Gabriel Farrell (Philly, PA) have truck but it's old and doesn't get great mileage (ain't no tesla roadster)

Rates for full-size car (driver + 4) and van as of Dec. 9, 2009 from NY/NJ, '''without precon''':
* Budget: 303 / 446 (7 pass)
* Avis: 369 / 459 (7 pass)
* Hertz: 340 / 501 (7 pass)
* Enterprise: mileage limitation

Esme Cowles is planning to drive up from Gainesville, FL and could take up to 3 others from Florida, South Carolina or Georgia (depending on route). Anyone interested?

Michael Klein has created a [[C4L2010rideshare]] page for more general rideshare/airport ground transportation/other Asheville-bound travel planning.

== Roommates ==

=== Looking ===

<strike>Cody Hennesy is looking to be a roommate arriving Feb 21 departing Feb 25. chennesy at cca dot edu.</strike>

=== Offering ===

<strike>Becky Yoose - Looking for a roommate... Room booked from Sunday 2/21 to Thursday 2/25. Email me at yoosebj at muohio dot edu if interested.</strike>

Gwen Exner - Looking for a roommate. Room booked from Monday 2/22 to Thursday 2/25. Email me at gwenexner at gmail dot com if interested.
[[Category: Code4Lib2010]]

2010talks Submissions

2009-11-13T21:59:03Z

Gsf:

Edit this page to submit your proposal for a 20-minute talk at the Code4Lib 2010 Conference. For more information, see the [[2010talkscall_Call_for_Submissions|Call for submissions]].

'''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>

== Mobile Web App Design: Getting Started ==

* Michael Doran, University of Texas at Arlington, doran@uta.edu, http://rocky.uta.edu/doran/

Creating or adapting library web applications for mobile devices such as the iPhone, Android, and Palm Pre is not hard, but it does require learning some new tools, new techniques, and new approaches. From the Tao of mobile web app design to using mobile device SDKs for their emulators, this presentation will give you a jump-start on mobile cross-platform design, development, and testing. And all illustrated with a real-world mobile library web application.

== Drupal 7: A more powerful platform for building library applications ==

* Cary Gordon, The Cherry Hill Company, cgordon@chillco.com

The release of Drupal 7 brings with it a big increase in utility for this already very useful and well-accepted content management framework. Specifically, the addition of fields in core, the inclusion of RDFa, the use of the PHP_db abstraction layer, and the promotion of files to first class objects facilitate the development of richer applications directly in Drupal without the need to integrate external products.

== Fiwalk with Me: Using Automatic Forensics Tools and Python for Digital Curation Triage ==

* Mark Matienzo, The New York Public Library, mark@matienzo.org

Building on Simson Garfinkel's work in Automated Document and Media Exploitation (ADOMEX), this project investigates digital curation applications of open source tools used in digital forensics. Specifically, we will be using [http://afflib.org AFFLib]'s fiwalk ("file and inode walk") application and its corresponding Python library to develop a basic triage workflow for accessioned hard drives, removable media, or disk images. These tools will allow us to create a simple, Web-based "digital curation workbench" application to do preliminary analysis and processing of this data.

== Do it Yourself Cloud Computing with Apache and R ==

* Harrison Dekker, University of California, Berkeley, hdekker@library.berkeley.edu

R is a powerful and extensible open source statistical analysis application. Rapache, software developed at Vanderbilt University, allows web developers to leverage the numeric processing and graphical capabilities of R in real-time through simple Apache server requests. This presentation will provide an overview of both R and rapache and will explore how these tools are relevant to the library community.

== Metadata editing - a truly extensible solution ==

* David Kennedy, Duke University, david.kennedy@duke.edu
* David Chandek-Stark, Duke University, david.chandek.stark@duke.edu

http://library.duke.edu/trac/dc/wiki/Trident

We set out in the Trident project to create a metadata tool that scales. In doing so we have conceived of the metadata application profile, a profile which provides instructions for software on how to edit metadata. We have built a set of web services and some web-based tools for editing metadata. The metadata application profile allows these tools to extend across different metadata schemes, and allows for different rules to be established for editing items of different collections. Some features of the tools include integration with authority lists, auto-complete fields, validation and clean integration of batch editing with Excel. I know, I know, Excel, but in the right hands, this is a powerful tool for cleanup and batch editing.

In this talk, we want to introduce the concepts of the metadata application profile, and gather feedback on its merits, as well as demonstrate some of the tools we have developed and how they work together to manage the metadata in our Fedora repository.

== Flickr'ing the Switch ==

* Dianne Dietrich, Cornell University Library, dd388@cornell.edu

We started out with a simple dream — to pilot a handful of images from our collection in Flickr. Since June 2009, we've grown that dream from its humble beginnings into something bigger: we now have a Flickr collection of over two thousand images. We added geocoding and tags, repurposed our awesome structured metadata, and screenscraped the rest. This talk will focus on the code, which made most of this possible.

This includes (and is certainly not limited to) using the Python Flickr API, various geocoding tools, crafting Flickr metadata by restructuring XML data from Luna Insight, screenscraping any descriptive text we could get our hands on, negotiating naming conventions for thousands of images, thinking cleverly in order to batch update images on Flickr at a later point (we had to do this more than once), using digital forensic tools to save malformed tifs (that were digitized in 1998!), and, finally, our efforts at scaling everything up so we can integrate our Flickr project into the regular workflow at technical services.

== library/mobile: Developing a Mobile Catalog ==

* Kim Griggs, Oregon State University Libraries, kim.griggs@oregonstate.edu

The increased use of mobile devices provides an untapped resource for delivering library resources to patrons. The mobile catalog is the next step for libraries in providing universal access to resources and information.

This talk will share Oregon State University (OSU) Libraries' experience creating a custom mobile catalog. The discussion will first make the case for mobile catalogs, discuss the context of mobile search, and give an overview of vendor and custom mobile catalogs. The second half of the talk will look under the hood of OSU Libraries' custom mobile catalog to provide implementation strategies and discuss tools, techniques, requirements, and guidelines for creating an optimal mobile catalog experience that offers services that support time critical and location sensitive activities.

== Enhancing discoverability with virtual shelf browse ==

* Andreas Orphanides, NCSU Libraries, andreas_orphanides@ncsu.edu
* Cory Lown, NCSU Libraries, cory_lown@ncsu.edu
* Emily Lynema, NCSU Libraries, emily_lynema@ncsu.edu

With collections turning digital, and libraries transforming into collaborative spaces, the physical shelf is disappearing. NCSU Libraries has implemented a virtual shelf browse tool, re-creating the benefits of physical browsing in an online environment and enabling users to explore digital and physical materials side by side. We hope that this is a first step towards enabling patrons familiar with Amazon and Netflix recommendations to "find more" in the library.

We will provide an overview of the architecture of the front-end application, which uses Syndetics cover images to provide a "cover flow" view and allows the entire "shelf" to be browsed dynamically. We will describe what we learned while wrangling multiple jQuery plugins, manipulating an ever-growing (and ever-slower) DOM, and dealing with unpredictable response times of third-party services. The front-end application is supported by a web service that provides access to a shelf-ordered index of our catalog. We will discuss our strategy for extracting data from the catalog, processing it, and storing it to create a queryable shelf order index.

== Where do mobile apps go when they die? or, The app with a thousand faces. ==

* Jason Casden, North Carolina State University Libraries, jason_casden@ncsu.edu

New capabilities in both native and web-based mobile platforms are rapidly expanding the possibilities for mobile library services. In addition to developing small-screen versions of our current services, at NCSU Libraries we attempt to develop new services that take unique advantage of the mobile user context. Some of these ideas may require capabilities that are not exposed to the mobile browser. Smart technical planning can help to make sound development decisions when experimenting with mobile-enhanced development, while remaining agile when faced with constantly changing technical and non-technical restraints and opportunities.

This talk will be based on my experience as a developer of both native iPhone and web-based mobile library apps at NCSU Libraries, and with the effort to port our geo-mobile WolfWalk iPhone app to the web. I will also discuss some opportunities being created by other platforms, particularly Android-based devices.

== Using Google Voice for Library SMS ==

* Eric Sessoms, Nub Games, Inc., nubgames@gmail.com
* Pam Sessoms, UNC Chapel Hill, psessoms@gmail.com

The LibraryH3lp Google Voice/SMS gateway (free, full AGPL source available at http://github.com/esessoms/gvgw, works with any XMPP server, LibraryH3lp subscription not required) enables libraries to easily integrate texting services into their normal IM workflow. This talk will review the challenges we faced, especially issues involved with interfacing to a Google service lacking a published API, and will outline the design of the software with particular emphasis on features that help the gateway to be more responsive to users. Because the gateway is written in the Clojure programming language, we'll close by highlighting which features of the language and available tools had the greatest positive and negative impacts on our development process.

== Building a discovery system with Meresco open source components ==

* Karin Clavel, TU Delft Library, The Netherlands, c.l.clavel@tudelft.nl
* Etienne Posthumus, TU Delft Library, The Netherlands, e.posthumus@tudelft.nl

TU Delft Library uses Meresco, an open source component library for metadata management, to implement a custom integrated search solution called [http://discover.tudelft.nl/ Discover]).
In Discover, different Meresco components are configured to work together in an efficient observer pattern, defined in what is called Meresco DNA (written in Python). The process is as follows: metadata is harvested from different sources using the Meresco harvester. It is then cross-walked into (any format you like, but we chose) MODS, then normalized, stored and indexed in three distinct but integrated indexes: a full-text Lucene index, a facet index and N-gram index for suggestions and fixing spelling mistakes. The facet index supports multiple algoritmes: drilldown, Jaccard, Mutual Information (or Information Gain) and ÃŽÂ§Ã‚Â². One of the facets is used to cluster the search results by subject by using the Jaccard and Mutual Information algorithms. 

The query parser component automatically detects and supports Google-like, Boolean and field-specific queries. Different XML documents describing the same content item coalesce to provide the user interface with an easy way to access metadata from either the original or normalized metadata or from user generated metadata such as ratings or tags. Other Meresco components provide an SRU and a RSS interface. 

Discover currently holds all catalogue records, the institutional repository metadata, an architecture bibliography and a test-set of Science Direct articles. In 2010, it is expected to grow to over 10 million records with content from Elsevier, IEEE and Springer (subject to negotiatons with these publishers) and various open access resources. We will also add the university's multimedia collection, ranging from digitized historical maps, drawing and photographs to recent (vod- and) podcasts. 

In the proposed session, we would like to show you some examples of above mentioned functionality and explain how Meresco components work together to create this flexible system.

== Take control of library metadata and websites using the eXtensible Catalog ==

* Jennifer Bowen, University of Rochester, jbowen@library.rochester.edu

The eXtensible Catalog Project has developed four open-source software toolkits that enable libraries to build and share their own web- and metadata-focused applications on top of a service-oriented architecture that incorporates Solr in Drupal, a robust metadata management platform, and OAI-PMH and NCIP-compatible tools that interact with legacy library systems in real-time.

XC's robust metadata management platform allows libraries to orchestrate and sequence metadata processing services on large batches of metadata. Libraries can build their own services using the available "service-writers toolkit" or choose from our initial set of metadata services that clean up and "FRBRize" MARC metadata. Another service will aggregate metadata from multiple repositories to prepare it for use in unified discovery applications. XC software provides an RDA metadata test bed and a Solr-based metadata "navigator" that can aggregate and browse metadata (or data) in any XML format. XC's user interface platform is the first suite of Drupal modules that treat both web content and library metadata as native Drupal nodes, allowing libraries to build web-applications that interact with metadata from library catalogs and institutional repositories as well as with library web pages. XC's Drupal modules enable Solr in a FRBRized data environment, as a first step toward a full implementation of RDA. Other currently-available XC toolkits expose legacy ILS metadata, circulation, and patron functionality via web services for III, Voyager and Aleph (to date) using standard protocols (OAI-PMH and NCIP), allowing libraries to easily and regularly extract MARC data from an ILS in valid MARCXML and keep the metadata in their discovery applications "in sync" with source repositories.

This presentation will showcase XC's metadata processing services, the metadata "navigator" and the Drupal user interface platform. The presentation will also describe how libraries and their developers can get started using and contributing to the XC code.

== I Am Not Your Mother: Write Your Test Code ==

* Naomi Dushay, Stanford University, ndushay@stanford.edu
* Willy Mene, Stanford University, wmene@stanford.edu
* Jessie Keck, Stanford University, jkeck@stanford.edu

How is it worth it to slow down your code development to write tests? Won't it take you a long time to learn how to write tests? Won't it take longer if you have to write tests AND develop new features, fix bugs? Isn't it hard to write test code? To maintain test code? We will address these questions as we talk about how test code is crucial for our software. By way of illustration, we will show how it has played a vital role in making Blacklight a true community collaboration, as well as how it has positively impacted coding projects in the Stanford Libraries.

== How To Implement A Virtual Bookshelf With Solr ==

* Naomi Dushay, Stanford University, ndushay@stanford.edu
* Jessie Keck, Stanford University, jkeck@stanford.edu

Browsing bookshelves has long been a useful research technique as well as an activity many users enjoy. As larger and larger portions of our physical library materials migrate to offsite storage, having a browse-able virtual shelf organized by call number is a much-desired feature. I will talk about how we implemented nearby-on-shelf in Blacklight at Stanford, using Solr and SolrMarc:
# the code to get shelfkeys out of call numbers
# the code to lop volume data off the end of call numbers to avoid clutter in the browse
# what I indexed in Solr given we have
## multiple call numbers for a single bib record
## multiple bib records for a single call number
# Solr configuration, requests and responses to get call numbers before and after a given starting point as well as the desired information for display.
# Other code needed to implement this feature in Blacklight (concepts easily ported to other UIs).

This virtual shelf is not only browsable across locations, but includes any item with a call number in our collection (digital or physical materials).

All code is available, or will be by Code4Lib 2010.

== A Better Advanced Search ==

* Naomi Dushay, Stanford University, ndushay@stanford.edu
* Jessie Keck, Stanford University, jkeck@stanford.edu

Even though we'd love to get basic searches working so well that advanced search wouldn't be necessary, there will always be a small set of users that want it, and there will always be some library searching needs that basic searching can't serve. Our user interface designer was dissatisfied with many aspects of advanced search as currently available in most library discovery software; the form she designed was excellent but challenging to implement. See http://searchworks.stanford.edu/advanced
We'll share details of how we implemented Advanced Search in Blacklight:
# non-techie designed html form for the user
# boolean syntax while using Solr dismax magic (dismax does not speak Boolean)
# checkbox facets (multiple facet value selection)
# fielded searching while using Solr dismax magic (dismax allows complex weighting formulae across multiple author/title/subject/... fields, but does not allow "fielded" searching in the way lucene does)
## easily configured in solrconfig.xml
# manipulating user entered queries before sending them to Solr
# making advanced search results look like other search results: breadcrumbs, selectable facets, and other fun.

== Scholarly annotation services using AtomPub and Fedora ==

* Andrew Ashton, Brown University, andrew_ashton@brown.edu

We are building a framework for doing granular annotations of objects housed in Brown's Digital Repository. Beginning with our TEI-encoded text collections, and eventually expanding to other media, these scholarly annotations are themselves objects stored and preserved in the repository. They are linked to other resources via URI references, and deployed using AtomPub services as part of Fedora's Service/Dissemination model.

This effort stems from the recognition that standard web annotation techniques (e.g. tagging, Google Sidebar, page-level commenting, etc.) are not flexible or persistent enough to handle scholarly annotations as an organic part of natively digital research collections. We are developing solutions to several challenges that arise with this approach; particularly, how do we address highly granular portions of digital objects in a way that is applicable to different types of media (encoded texts, images, video, etc.). This presentation will provide an overview of the architecture, a discussion of the possibilities and problems we face in implementing this framework, and a demo of a live project using Atom annotations with a digital research collection.

== With Great Power... Managing an Open-Source ILS in a state-wide consortium. ==

* Emily A. Almond, Software Development Manager, PINES/Georgia Public Library Service, ealmond@georgialibraries.org

Using agile software development methodology + project management to achieve a balance of support and expertise. Lessons learned after implementation that inform how the consortium should evolve so that you can utilize your new ILS for the benefit of all stakeholders.
Topics covered:
-- troubleshooting and help desk support
-- development project plans
-- roles and responsibility shifts
-- re-branding the ILS and related organizations.

== Data Modeling; Logical Versus Physical; Why Do I Care? ==

* Steve Dressler, Georgia Public Library Services, sdressler@georgialibraries.org

I am sure we have all been in the situation of having mountains of data stored in our database, needing a piece of information and yet being unable to determine how to get what we need. Computerized databases have been around for decades now and there are several architectures available; however, the ability of a database developer, regardless of the architecture, to store data in a format that is comprehensible to a businessperson yet readily accessible through software applications remains an impossible challenge.

Topics to be discussed include
o Components comprising a logical model, how it is developed and how is it used?
o Components comprising a physical model, how it is developed and how is it used?
o What does a logical model look like?
o What does a physical model look like?
o Who works with a logical model and why?
o Who works with a physical model and why?
o What is the relationship between the logical model and the physical model?
o What kind of a time investment is required to develop and maintain logical and physical models?
o What are the challenges of keeping the two models in sync as the software application evolves?

Although data modeling is a huge discipline and presents research topics for millions of theses and dissertations, this twenty-minute snapshot view will allow anyone, technical or business, to sit through a development meeting and be able to grasp what is being discussed as well as gain a better understanding of logical and physical business flows.

== Media, Blacklight, and viewers like you. ==

* Chris Beer, WGBH, chris_beer@wgbh.org

There are many shared problems (and solutions) for libraries and archives in the interest of helping the user. There are also many "new" developments in the archives world that the library communities have been working on for ages, including item-level cataloging, metadata standards, and asset management. Even with these similarities, media archives have additional issues that are less relevant to libraries: the choice of video players, large file sizes, proprietary file formats, challenges of time-based media, etc. In developing a web presence, many archives, including the WGBH Media Library and Archives, have created custom digital library applications to expose material online. In 2008, we began a prototyping phase for developing scholarly interfaces by creating a custom-written PHP front-end to our Fedora repository.

In late 2009, we finally saw the (black)light, and after some initial experimentation, decided to build a new, public website to support our IMLS-funded /Vietnam: A Television History/ archive (as well as existing legacy content). In this session, we will share our experience of and challenges with customizing Blacklight as an archival interface, including work in rights management, how we integrated existing Ruby on Rails user-generated content plugins, and the development of media components to support a rich user experience.

== DAMS PAS - Digital Asset Management System, Public Access System ==

* Declan Fleming, University of California, San Diego, dfleming@ucsd.edu
* Esmé Cowles, University of California, San Diego, ecowles@ucsd.edu

After years of describing our DAMS with Powerpoint, we finally have a public access system that we can show our mothers. And code4lib! The UCSD Libraries DAMS is an RDF based asset repository containing over 250,000 items and their derivatives. We describe the core system, the metadata and storage challenges involved in managing hundreds of thousands of items, and the interesting political aspects involved in releasing subsets to the public. We also describe the caching approach we used to ensure performance and access control.

== You Either Surf or You Fight: Integrating Library Services with Google Wave ==

* Sean Hannan, Sheridan Libaries, Johns Hopkins University, shannan@jhu.edu

So Google Wave is a new shiny web toy, but did you know that it's also a great platform for collaboration and research? (I bet you did.) ...And what platform for collaboration and research would not be complete without some library tools to aid and abet that process? I will talk about how to take your library web services and integrate them with Google Wave to create bots that users can interact with to get at your resources as part of their social and collaborative work.

== The Linked Library Data Cloud: Stop talking and start doing ==

* Ross Singer, Talis, ross.singer@talis.com

A year later and how far has Linked Library Data come? With the emergence of large, centralized sources (id.loc.gov/authorities/, viaf.org, among others) entry to the Linked Data cloud might be easier than you think. This presentation will describe various projects that are out in the wild that can bridge the gap between our legacy data and the semantic web, incremental steps we can take modeling our data, why linked data matters and a demonstration of how a small template changes can contribute to the Linked Data cloud.

== A code4lib Manifesto ==

* Dan Chudnov, No Fixed Hairstyle, dchud at umich edu

code4lib started with a half dozen library hackers and a list and it ain't like that anymore. I come to code4lib with strong opinions about why it's a positive force in my professional and personal life, but they're probably different from your opinions. I will share these opinions rudely yet succinctly to challenge everyone to think and argue about why code4lib works and what we need to do to keep it working.

== Cloud4lib ==

* Jeremy Frumkin, University of Arizona, frumkinj at u library arizona edu
* Terry Reese, Oregon State University, terry.reese at oregonstate edu

Major library vendors are creating proprietary platforms for libraries. We will propose that the code4lib community pursue the cloud4lib, a open digital library platform based on open source software and open services. This platform would provide common service layers for libraries, not only via code, but also allow libraries to easily utilize tools and systems through cloud services. Instead of a variety of competing cloud services and proprietary platforms, cloud4lib will attempt to be a unifying force that will allow libraries to be consumer of the services built on top of it as well as allow developers / researchers / code4lib'ers to hack, extend, and enhance the platform as it matures.

== Iterative development done simply ==

* Emily Lynema, North Carolina State University Libraries, emily_lynema@ncsu.edu

With a small IT unit and a wide array of projects to support, requests for development from business stakeholders in the library can quickly spiral out of control. To help make sense of the chaos, increase the transparency of the IT "black box," and shorten time lag between requirements definition and functional releases, we have implemented a modified Agile/SCRUM methodology within the development group in the IT department at NCSU Libraries.

This presentation will provide a brief overview of the Agile methodology as an introduction to our simplified approach to iteratively handling multiple projects across a small team. This iterative approach allows us to regularly re-evaluate requested enhancements against institutional priorities and more accurately estimate timelines for specific units of functionality. The presentation will highlight how we approach each development cycle (from planning to estimating to re-aligning) as well as some of the actual tools and techniques we use to manage work (like JIRA and Greenhopper). It will identify some challenges faced in applying an established development methodology to a small team of multi-tasking developers, the outcomes we've seen, and the areas we'd like to continue improving. These types of iterative planning/development techniques could be adapted by even a single developer to help manage a chaotic workplace.

== Public Datasets in the Cloud ==

* Rosalyn Metz, Wheaton College, metz_rosalyn@wheatoncollege.edu
* Michael B. Klein, Oregon State University, Michael.Klein@oregonstate.edu

When most people think about cloud computing (if they think about it at all), it usually takes one of two forms: Infrastructure Services, such as Amazon EC2 and GoGrid, which provide raw, elastic computing capacity in the form of virtual servers, and Platform Services, such as Google App Engine and Heroku, which provide preconfigured application stacks and specialized deployment tools.

Several providers, however, offer access to large public datasets that would be impractical for most organizations to download and work with locally. From a 67-gigabyte dump of DBpedia's structured information store to the 180-gigabyte snapshot of astronomical data from the Sloan Digital Sky Survey, chemistry and biology to economic and geographic data, these datasets are available instantly and backed by enough pay-as-you-go server capacity to make good use of them.

We will present an overview of currently-available datasets, what it takes to create and use snapshots of the data, and explore how the library community might push some of its own large stores of data and metadata into the cloud.

== Codename Arctika ==

* Toke Eskildsen, The State and University Library of Denmark, te@statsbiblioteket.dk

There's something missing in the state of Denmark. Most of our web based copyright deposit material is trapped in a dark archive. After a successful pilot; money and time has been allocated to open part of the data. We tried NutchWAX and it worked well, but we wanted more. Proper integrated search with existing library material, extraction of names etc. Therefore we propose the following recipe: Take a slice of a dark archive with copyright deposit material. Get permission to publish it (the tricky bit). Add an ARC reader to get the bits, Tika to get the text and Summa to get large-scale index and faceting. We mixed it up and we will show what happened.

== JeromeDL - an open source social semantic digital library ==

* Sebastian Ryszard Kruk, Knowledge Hives, sebastian.kruk@knowledgehives.com
* Jodi Schneider, DERI NUI Galway, jschneider@pobox.com

JeromeDL is an open source e-library with semantics. A fully functional digital library, JeromeDL uses linked data: using standard "Web3.0" vocabularies such as SIOC, FOAF, and WordNet, JeromeDL publishes RDF descriptions of the e-library contents. Jerome DL uses FOAF to manage users--meaning that access privileges can be naturally assigned to a social network, in addition to individuals or all WWW users. Users can also share annotations, promoting collaborative browsing and collaborative filtering. To encourage users to provide meaningful annotations (beyond just tags), JeromeDL uses a WordNet-based vocabulary service. The system also leverages full-text indexing with Lucene and allows filtering with the SIMILE project's Exhibit. In short, JeromeDL is a social semantic digital library--allowing users to collect, publish, and share their library with their social network on the semantic web.

*[http://www.jeromedl.org/ JeromeDL homepage]
*[http://bleedingedge.jeromedl.org/preview?show=techreport JeromeDL demo site]

== Kill the search button ==

* Michael Poltorak Nielsen, State and University Library, Denmark, mn@statsbiblioteket.dk
* Jørn Thøgersen, State and University Library, Denmark, jt@statsbiblioteket.dk

We demo three concepts that eliminate the search button.

1. Instant search. Why wait for tiresome page reloads when searching? Instant search updates the search result on every key-press. We will show how we integrated this feature into our own library search system with minimal changes to the existing setup.

2. Index lookup. Ever dreamed of your own inline instant index lookup?
We demo an instant index lookup feature that requires no search button and no page refreshes - and without ever leaving the search field.

3. Slide your data. Sliders are an alternative way to fit search results to the user's search context.
Examples are sliders that move search results priorities between title and subject and between books by an author and books about the author.

== Controlling the flood: Re-plumbing fittings between a New Titles List and other services with Yahoo! Pipes. ==

* Jon Gorman, University of Illinois, jtgorman@illinois.edu

About four years ago the University of Illinois decided to create a New Titles service (http://www.library.illinois.edu/newtitles/) that could provide RSS feeds. At the time a balance was struck between complexity of options and limited development time. Currently a feed is created by adding options, each option narrowing the scope of a feed. Selecting a date range, Unit Library and a call number range will retrieve material that match all three of the criteria. It was hoped that at some point a generic tool would be able to further manipulate and combine feeds produced by the simple options to customize very specific feed. Yahoo! Pipes has emerged to fill that niche.

The talk will cover pipes that range from filter for a keyword in one feed to combining the New Titles List with services like the LibraryThing API or Worldcat APIs. Examples will also be given in how to integrate the output of Yahoo! Pipes into webpages and how we have put them into our CMS (OpenCMS). The talk will make sure to address areas where Yahoo! Pipes either fails or is cumbersome and simpler CSS and Javascript solutions have worked.

== Vampires vs. Werewolves: Ending the War Between Developers and Sysadmins with Puppet ==

* Bess Sadler, University of Virginia, bess@virginia.edu

Developers need to be able to write software and deploy it, and often require cutting edge software tools and system libraries. Sysadmins are
charged with maintaining stability in the production environment, and so are often resistant to rapid upgrade cycles. This has traditionally pitted us against each other, but it doesn't have to be that way. Using tools like puppet for maintaining and testing server configuration, nagios for monitoring, and hudson for continuous code integration, UVA has brokered a peace that has given us the ability to maintain stable production environment with a rapid upgrade cycle. I'll discuss both the individual tools, our server configuration, and the social engineering that got us here.

== Building customizable themes for DSpace ==

* Elias Tzoc, Miami University of Ohio, tzoce@muohio.edu

The popularity of DSpace (should I say DuraSpace?) continues to grow!
Many universities and research institutions are using DSpace to create and provide access to digital content — including documents, images, audio, and video. With the variety of content, one of the challenges is "how to create customizable themes for different types of content?"

In 2007, Manakin was developed as a user interface for DSpace based on themes. Now users have the ability to customize the web interface for DSpace collections by editing CSS, XML, and XSLT files. Best of all, a singular theme can be applied to individual communities, collections or items.

This talk will be based on my work creating themes for DSpace, as well as tips & tricks for customizing the look-and-feel for individual communities and collections.
Who knows, maybe someday a group of code4lib developers can create a whole library of themes for DuraSpace — similar to the WordPress or Drupal theme idea!

== HIVE: a new tool for working with vocabularies ==

* Ryan Scherle, National Evolutionary Synthesis Center, rscherle@nescent.org
* Jose Aguera, Universitty of North Carolina, jose.aguera@gmail.com

HIVE is a toolkit that assists users in selecting vocabulary and ontology terms to annotate digital content. The HIVE approach promises to combine the ease of folksonomies with the rigor of traditional vocabularies.

Users can search and browse through terms from a variety of vocabularies and ontologies in one integrated tool. Documents can be submitted to HIVE for automatic analysis, resulting in a set of suggested vocabulary terms.

Your system can interact with common vocabularies such as LCSH and MESH via the central HIVE server, or you can install a local copy of HIVE with your own custom set of vocabularies. This talk will give an overview of the current features of HIVE and describe how to build tools that use the HIVE services.

== Implementing Metasearch and a Unified Index with Masterkey ==

* [[User:DataGazetteer|Peter Murray]], OhioLINK, peter@OhioLINK.edu

Index Data's suite of metasearch and local indexing tools under the product name Masterkey are a powerful way to provide access to a diverse set of databases. In 2009, OhioLINK contracted with Index Data to help build a new metasearch platform and a unified index of locally-loaded records.

By the time conference rolls around, the user interface and the metasearch infrastructure will be set up and live. This part of the presentation will dive into the innards of the AJAX-powered end-user interface, the configuration back-end, and possibly a view of the Gecko-driven Index Data Connector Framework.

It is hard to predict at the point this talk is being proposed what the state of the unified index will be. At the very least, there will be broad system diagrams and a description of how intend to eventually bring 250 million records into one index. With luck, there might even be running code to show.

== Adding Solr-based Search to Evergreen's OPAC ==

* Alexander O'Neill, Robertson Library, University of Prince Edward Island, aoneill@upei.ca

The current way the Evergreen OPAC searches records is to use it's database back-end's search system, with heavy use of caching layers to compensate for the relatively long wait to perform a new search.

This is a personal project to adapt the Evergreen search results page to use the Solr and Lucene search engine stack - integrating the external search function as closely as possible with Evergreen's existing look and feel. This is a possible alternative to replacing an entire OPAC just to take advantage of the very desirable features offered by the Solr stack as Evergreen does offer a very well-designed extensible JavaScript interface which we and others have already gotten great results customizing and adding features to such as integrated Google Books previews and incorporating LibraryThing's social features. Adapting the leading open source search technology into this very powerful stack is one more feature to add to Evergreen's very compelling list of selling points.

It is still possible to use Evergreen's OpenSRF messaging system to get live information about each book's current availability status without having to push all of this information into the Solr index.

I will show how I used SolrMarc to import records from Evergreen, taking advantage of the fact that the VuFind and Blacklight projects have collaborated to create a general import utility that is usable by third-party projects. I will discuss some of the hurdles I encountered while using SolrMarc and the resulting changes to SolrMarc's design that this use case helped to motivate.

I'll also make an effort to take measurements of performance when hosting both Solr and Evergreen on the same server compared with putting Solr on a separate server. It will also be informative to see how much of an Evergreen server's system load is devoted to processing user searches.

==Matching Dirty Data - Yet another wheel==

* Anjanette Young, University of Washington Libraries, younga3 at u washington edu
* Jeff Sherwood, University of Washington Libraries, jeffs3 at u washington edu

Regular expressions is a powerful tool to identify matching data between similar files. When one or both of these files has inconsistent data due to differing character encodings or miskeying, the use of regular expressions to find matches becomes impractically complex.

The Levenshtein distance (LD) algorithm is a basic sequence comparison technique that can be used to measure word similarity more flexibly. Employing the LD to calculate difference eliminates the need to identify and code into regex patterns all of the ways in which otherwise matching strings might be inconsistent. Instead, a similarity threshold is tuned to identify close matches while eliminating false positives.

Recently, the UW Libraries began an effort to store Electronic Theses and Dissertations (ETD) in our institutional repository which runs on DSpace. We received 6,756 PDFs along with a file of UMI-created MARC records which needed to be matched to our library's custom MARC records (60,175 records). Once matched, merged information from both records would be used to create the dublin_core.xml file needed for batch ingest into DSpace. Unfortunately, records within the MARC data had no common unique identifiers to facilitate matching. Direct matching by title or author was impractical due to slight inconsistencies in data entry. Additionally, one of the files had "flattened" characters in title and author fields to ASCII. We successfully employed LD to match records between the two files before merging them.

This talk demonstrates one method of matching sets of MARC records that lack common unique identifiers and might contain slight differences in the matching fields. It will cover basic usage of several python tools. No large stack traces, just the comfort of pure python and basic computational algorithms in a step-by-step presentation on dealing with an old library task: matching dirty data. While much literature exists on matching/merging duplicate bibliographic records, most of this literature does not specify how to accomplish the task, just reports on the efficiency of the tools used to accomplish the task, often within a larger system such as an ILS.

==Automating Git to create your own open-source Dropbox clone==

* Ian Walls, System Integration Librarian, NYU Health Sciences Libraries, Ian.Walls at med.nyu.edu

Dropbox is a great tool for synchronizing files across pretty much any machine you’re working on. Unfortunately, it has some drawbacks:
# Monthly fees for more than 2GB
# The server isn’t yours
# The server-side scripting isn’t open source
However, using the [http://git-scm.com/ Git distributed version control system], file event APIs, and your favourite scripting language, it is possible to create a file synchronization system (with full replication and multiple histories) that connects all your computers to your own server.

These scripts would allow library developers to collaborate and work on multiple machines with ease, while benefiting from the robust version control of Git. An active internet connection is not required to have access to the full history of the repository, making it easier to work on the go. This also keeps your data more private and secure by only hosting it on machines you trust (important if you’re dealing with sensitive patron information).

== Becoming Truly Innovative: Migrating from Millennium to Koha==

* Ian Walls, System Integration Librarian, NYU Health Sciences Libraries, Ian.Walls at med.nyu.edu

On Sept. 1st, 2009, the NYU Health Sciences Libraries made the unprecedented move from their Millennium ILS to Koha. The migration was done over the course of 3 months, without assistance from either Innovative Interfaces, Inc. or any Koha vendor. The in-house script, written in Perl and XSLT, can be used with any Millennium installation, regardless of which modules have been purchased, and can be adapted to work for migration to systems other than Koha. Helper scripts were also developed to capture the current circulation state (checkouts, holds and fines), and do minor data cleanup.

This presentation will cover the planning and scheduling of the migration, as well as an overview of the code that was written for it. Opportunities for systems integration and development made newly available by having an open source platform are also discussed.

== 7 Ways to Enhance Library Interfaces with OCLC Web Services ==

* Karen A. Coombs, librarywebchic@gmail.com

OCLC Web Services such as xISSN, WorldCat Search API, WorldCat Identities, and the WorldCat Registry provide a variety of data which can be used to enhance and improve current library interfaces. This talk will discuss several simple ideas to improve current users interfaces using data from these services.

Javascript and PHP code to add journal of table of contents information, peer-reviewed journal designation, links to other libraries in the area with a book, also available ..., and info about this author will be discussed.

== Adventures with Facebook Open Platform ==

* Kenny Ketner, Texas Tech University Libraries, kenny.ketner@ttu.edu

Developing with the facebook platform can be both exciting and something that you wouldn’t wish on your worst enemy. This talk will chronicle the Texas Tech Libraries Development Team experimentation with Facebook Open Platform (fbOpen) as we attempt to create a facebook-like social media application Texas Tech University Libraries, hopefully expanding to the Texas Digital Library (TDL).

More than just a facebook app or page, fbOpen is a complete implementation of the facebook system on a LAMP stack – Linux, Apache, MySQL, PHP – which must be maintained by the institution itself. This project is at an early stage, so emphasis will be placed on the challenges of installation, configuration, and testing, as well as the pros and cons for institutions that are considering taking on a similar project.

== Kurrently Kochief ==

* Gabriel Farrell, Drexel University Libraries, gsf24@drexel.edu

Kochief is a discovery interface and catalogue manager. It rests on Solr and a
Python stack including Django, pymarc, and rdflib. We're using it to highlight
a few collections at Drexel. They live at http://sets.library.drexel.edu.

I'll talk about the latest and greatest, including advances in the install and
configuration, details considered in the searcher's experience, and the
sourcing and exposing of Linked Data.

2010talks Submissions

2009-11-13T21:54:36Z

Gsf: Added proposal

User:Gsf

2009-11-13T18:59:29Z

Gsf: New page: Gabriel Farrell, Drexel University

Gabriel Farrell, Drexel University

2010talks Submissions

2009-11-13T18:34:18Z

Gsf: Fixed some encoding issues.

Edit this page to submit your proposal for a 20-minute talk at the Code4Lib 2010 Conference. For more information, see the [[2010talkscall_Call_for_Submissions|Call for submissions]].

'''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>

== Mobile Web App Design: Getting Started ==

* Michael Doran, University of Texas at Arlington, doran@uta.edu, http://rocky.uta.edu/doran/

Creating or adapting library web applications for mobile devices such as the iPhone, Android, and Palm Pre is not hard, but it does require learning some new tools, new techniques, and new approaches. From the Tao of mobile web app design to using mobile device SDKs for their emulators, this presentation will give you a jump-start on mobile cross-platform design, development, and testing. And all illustrated with a real-world mobile library web application.

== Drupal 7: A more powerful platform for building library applications ==

* Cary Gordon, The Cherry Hill Company, cgordon@chillco.com

The release of Drupal 7 brings with it a big increase in utility for this already very useful and well-accepted content management framework. Specifically, the addition of fields in core, the inclusion of RDFa, the use of the PHP_db abstraction layer, and the promotion of files to first class objects facilitate the development of richer applications directly in Drupal without the need to integrate external products.

== Fiwalk with Me: Using Automatic Forensics Tools and Python for Digital Curation Triage ==

* Mark Matienzo, The New York Public Library, mark@matienzo.org

Building on Simson Garfinkel's work in Automated Document and Media Exploitation (ADOMEX), this project investigates digital curation applications of open source tools used in digital forensics. Specifically, we will be using [http://afflib.org AFFLib]'s fiwalk ("file and inode walk") application and its corresponding Python library to develop a basic triage workflow for accessioned hard drives, removable media, or disk images. These tools will allow us to create a simple, Web-based "digital curation workbench" application to do preliminary analysis and processing of this data.

== Do it Yourself Cloud Computing with Apache and R ==

* Harrison Dekker, University of California, Berkeley, hdekker@library.berkeley.edu

R is a powerful and extensible open source statistical analysis application. Rapache, software developed at Vanderbilt University, allows web developers to leverage the numeric processing and graphical capabilities of R in real-time through simple Apache server requests. This presentation will provide an overview of both R and rapache and will explore how these tools are relevant to the library community.

== Metadata editing - a truly extensible solution ==

* David Kennedy, Duke University, david.kennedy@duke.edu
* David Chandek-Stark, Duke University, david.chandek.stark@duke.edu

http://library.duke.edu/trac/dc/wiki/Trident

We set out in the Trident project to create a metadata tool that scales. In doing so we have conceived of the metadata application profile, a profile which provides instructions for software on how to edit metadata. We have built a set of web services and some web-based tools for editing metadata. The metadata application profile allows these tools to extend across different metadata schemes, and allows for different rules to be established for editing items of different collections. Some features of the tools include integration with authority lists, auto-complete fields, validation and clean integration of batch editing with Excel. I know, I know, Excel, but in the right hands, this is a powerful tool for cleanup and batch editing.

In this talk, we want to introduce the concepts of the metadata application profile, and gather feedback on its merits, as well as demonstrate some of the tools we have developed and how they work together to manage the metadata in our Fedora repository.

== Flickr'ing the Switch ==

* Dianne Dietrich, Cornell University Library, dd388@cornell.edu

We started out with a simple dream — to pilot a handful of images from our collection in Flickr. Since June 2009, we've grown that dream from its humble beginnings into something bigger: we now have a Flickr collection of over two thousand images. We added geocoding and tags, repurposed our awesome structured metadata, and screenscraped the rest. This talk will focus on the code, which made most of this possible.

This includes (and is certainly not limited to) using the Python Flickr API, various geocoding tools, crafting Flickr metadata by restructuring XML data from Luna Insight, screenscraping any descriptive text we could get our hands on, negotiating naming conventions for thousands of images, thinking cleverly in order to batch update images on Flickr at a later point (we had to do this more than once), using digital forensic tools to save malformed tifs (that were digitized in 1998!), and, finally, our efforts at scaling everything up so we can integrate our Flickr project into the regular workflow at technical services.

== library/mobile: Developing a Mobile Catalog ==

* Kim Griggs, Oregon State University Libraries, kim.griggs@oregonstate.edu

The increased use of mobile devices provides an untapped resource for delivering library resources to patrons. The mobile catalog is the next step for libraries in providing universal access to resources and information.

This talk will share Oregon State University (OSU) Libraries' experience creating a custom mobile catalog. The discussion will first make the case for mobile catalogs, discuss the context of mobile search, and give an overview of vendor and custom mobile catalogs. The second half of the talk will look under the hood of OSU Libraries' custom mobile catalog to provide implementation strategies and discuss tools, techniques, requirements, and guidelines for creating an optimal mobile catalog experience that offers services that support time critical and location sensitive activities.

== Enhancing discoverability with virtual shelf browse ==

* Andreas Orphanides, NCSU Libraries, andreas_orphanides@ncsu.edu
* Cory Lown, NCSU Libraries, cory_lown@ncsu.edu
* Emily Lynema, NCSU Libraries, emily_lynema@ncsu.edu

With collections turning digital, and libraries transforming into collaborative spaces, the physical shelf is disappearing. NCSU Libraries has implemented a virtual shelf browse tool, re-creating the benefits of physical browsing in an online environment and enabling users to explore digital and physical materials side by side. We hope that this is a first step towards enabling patrons familiar with Amazon and Netflix recommendations to "find more" in the library.

We will provide an overview of the architecture of the front-end application, which uses Syndetics cover images to provide a "cover flow" view and allows the entire "shelf" to be browsed dynamically. We will describe what we learned while wrangling multiple jQuery plugins, manipulating an ever-growing (and ever-slower) DOM, and dealing with unpredictable response times of third-party services. The front-end application is supported by a web service that provides access to a shelf-ordered index of our catalog. We will discuss our strategy for extracting data from the catalog, processing it, and storing it to create a queryable shelf order index.

== Where do mobile apps go when they die? or, The app with a thousand faces. ==

* Jason Casden, North Carolina State University Libraries, jason_casden@ncsu.edu

New capabilities in both native and web-based mobile platforms are rapidly expanding the possibilities for mobile library services. In addition to developing small-screen versions of our current services, at NCSU Libraries we attempt to develop new services that take unique advantage of the mobile user context. Some of these ideas may require capabilities that are not exposed to the mobile browser. Smart technical planning can help to make sound development decisions when experimenting with mobile-enhanced development, while remaining agile when faced with constantly changing technical and non-technical restraints and opportunities.

This talk will be based on my experience as a developer of both native iPhone and web-based mobile library apps at NCSU Libraries, and with the effort to port our geo-mobile WolfWalk iPhone app to the web. I will also discuss some opportunities being created by other platforms, particularly Android-based devices.

== Using Google Voice for Library SMS ==

* Eric Sessoms, Nub Games, Inc., nubgames@gmail.com
* Pam Sessoms, UNC Chapel Hill, psessoms@gmail.com

The LibraryH3lp Google Voice/SMS gateway (free, full AGPL source available at http://github.com/esessoms/gvgw, works with any XMPP server, LibraryH3lp subscription not required) enables libraries to easily integrate texting services into their normal IM workflow. This talk will review the challenges we faced, especially issues involved with interfacing to a Google service lacking a published API, and will outline the design of the software with particular emphasis on features that help the gateway to be more responsive to users. Because the gateway is written in the Clojure programming language, we'll close by highlighting which features of the language and available tools had the greatest positive and negative impacts on our development process.

== Building a discovery system with Meresco open source components ==

* Karin Clavel, TU Delft Library, The Netherlands, c.l.clavel@tudelft.nl
* Etienne Posthumus, TU Delft Library, The Netherlands, e.posthumus@tudelft.nl

TU Delft Library uses Meresco, an open source component library for metadata management, to implement a custom integrated search solution called [http://discover.tudelft.nl/ Discover]).
In Discover, different Meresco components are configured to work together in an efficient observer pattern, defined in what is called Meresco DNA (written in Python). The process is as follows: metadata is harvested from different sources using the Meresco harvester. It is then cross-walked into (any format you like, but we chose) MODS, then normalized, stored and indexed in three distinct but integrated indexes: a full-text Lucene index, a facet index and N-gram index for suggestions and fixing spelling mistakes. The facet index supports multiple algoritmes: drilldown, Jaccard, Mutual Information (or Information Gain) and ÃŽÂ§Ã‚Â². One of the facets is used to cluster the search results by subject by using the Jaccard and Mutual Information algorithms. 

The query parser component automatically detects and supports Google-like, Boolean and field-specific queries. Different XML documents describing the same content item coalesce to provide the user interface with an easy way to access metadata from either the original or normalized metadata or from user generated metadata such as ratings or tags. Other Meresco components provide an SRU and a RSS interface. 

Discover currently holds all catalogue records, the institutional repository metadata, an architecture bibliography and a test-set of Science Direct articles. In 2010, it is expected to grow to over 10 million records with content from Elsevier, IEEE and Springer (subject to negotiatons with these publishers) and various open access resources. We will also add the university's multimedia collection, ranging from digitized historical maps, drawing and photographs to recent (vod- and) podcasts. 

In the proposed session, we would like to show you some examples of above mentioned functionality and explain how Meresco components work together to create this flexible system.

== Take control of library metadata and websites using the eXtensible Catalog ==

* Jennifer Bowen, University of Rochester, jbowen@library.rochester.edu

The eXtensible Catalog Project has developed four open-source software toolkits that enable libraries to build and share their own web- and metadata-focused applications on top of a service-oriented architecture that incorporates Solr in Drupal, a robust metadata management platform, and OAI-PMH and NCIP-compatible tools that interact with legacy library systems in real-time.

XC's robust metadata management platform allows libraries to orchestrate and sequence metadata processing services on large batches of metadata. Libraries can build their own services using the available "service-writers toolkit" or choose from our initial set of metadata services that clean up and "FRBRize" MARC metadata. Another service will aggregate metadata from multiple repositories to prepare it for use in unified discovery applications. XC software provides an RDA metadata test bed and a Solr-based metadata "navigator" that can aggregate and browse metadata (or data) in any XML format. XC's user interface platform is the first suite of Drupal modules that treat both web content and library metadata as native Drupal nodes, allowing libraries to build web-applications that interact with metadata from library catalogs and institutional repositories as well as with library web pages. XC's Drupal modules enable Solr in a FRBRized data environment, as a first step toward a full implementation of RDA. Other currently-available XC toolkits expose legacy ILS metadata, circulation, and patron functionality via web services for III, Voyager and Aleph (to date) using standard protocols (OAI-PMH and NCIP), allowing libraries to easily and regularly extract MARC data from an ILS in valid MARCXML and keep the metadata in their discovery applications "in sync" with source repositories.

This presentation will showcase XC's metadata processing services, the metadata "navigator" and the Drupal user interface platform. The presentation will also describe how libraries and their developers can get started using and contributing to the XC code.

== I Am Not Your Mother: Write Your Test Code ==

* Naomi Dushay, Stanford University, ndushay@stanford.edu

How is it worth it to slow down your code development to write tests? Won't it take you a long time to learn how to write tests? Won't it take longer if you have to write tests AND develop new features, fix bugs? Isn't it hard to write test code? To maintain test code? I will try to answer these questions as I talk about how test code is crucial for our software. By way of illustration, I will show how it has played a vital role in making Blacklight a true community collaboration, as well as how it has positively impacted coding projects in the Stanford Libraries.

== How To Implement A Virtual Bookshelf With Solr ==

* Naomi Dushay, Stanford University, ndushay@stanford.edu
* Jessie Keck, Stanford University, jkeck@stanford.edu

Browsing bookshelves has long been a useful research technique as well as an activity many users enjoy. As larger and larger portions of our physical library materials migrate to offsite storage, having a browse-able virtual shelf organized by call number is a much-desired feature. I will talk about how we implemented nearby-on-shelf in Blacklight at Stanford, using Solr and SolrMarc:
# the code to get shelfkeys out of call numbers
# the code to lop volume data off the end of call numbers to avoid clutter in the browse
# what I indexed in Solr given we have
## multiple call numbers for a single bib record
## multiple bib records for a single call number
# Solr configuration, requests and responses to get call numbers before and after a given starting point as well as the desired information for display.
# Other code needed to implement this feature in Blacklight (concepts easily ported to other UIs).

This virtual shelf is not only browsable across locations, but includes any item with a call number in our collection (digital or physical materials).

All code is available, or will be by Code4Lib 2010.

== A Better Advanced Search? ==

* Naomi Dushay, Stanford University, ndushay@stanford.edu
* Jessie Keck, Stanford University, jkeck@stanford.edu

Even though we'd like to get basic searches working so well that advanced search wouldn't be necessary, there will always be a small set of users that want it, and there will always be some library searching needs that basic searching can't serve. Our user interface designer was dissatisfied with many aspects of advanced search as currently available in most library discovery software; the form she designed was excellent but challenging to implement. See http://searchworks.stanford.edu/advanced
We'll share details of how we implemented Advanced Search in Blacklight:
# thoughtfully designed html form for the user (NOT done by techies!)
# boolean syntax while using Solr dismax magic (dismax does not speak Boolean)
# checkbox facets (multiple facet value selection)
# fielded searching while using Solr dismax magic (dismax allows complex weighting formulae across multiple author/title/subject/... fields, but does not allow "fielded" searching in the way lucene does)
## easily configured in solrconfig.xml
# manipulating user entered queries before sending them to Solr
# making advanced search results look like other search results: breadcrumbs, selectable facets, and other fun.

== Scholarly annotation services using AtomPub and Fedora ==

* Andrew Ashton, Brown University, andrew_ashton@brown.edu

We are building a framework for doing granular annotations of objects housed in Brown's Digital Repository. Beginning with our TEI-encoded text collections, and eventually expanding to other media, these scholarly annotations are themselves objects stored and preserved in the repository. They are linked to other resources via URI references, and deployed using AtomPub services as part of Fedora's Service/Dissemination model.

This effort stems from the recognition that standard web annotation techniques (e.g. tagging, Google Sidebar, page-level commenting, etc.) are not flexible or persistent enough to handle scholarly annotations as an organic part of natively digital research collections. We are developing solutions to several challenges that arise with this approach; particularly, how do we address highly granular portions of digital objects in a way that is applicable to different types of media (encoded texts, images, video, etc.). This presentation will provide an overview of the architecture, a discussion of the possibilities and problems we face in implementing this framework, and a demo of a live project using Atom annotations with a digital research collection.

== With Great Power... Managing an Open-Source ILS in a state-wide consortium. ==

* Emily A. Almond, Software Development Manager, PINES/Georgia Public Library Service, ealmond@georgialibraries.org

Using agile software development methodology + project management to achieve a balance of support and expertise. Lessons learned after implementation that inform how the consortium should evolve so that you can utilize your new ILS for the benefit of all stakeholders.
Topics covered:
-- troubleshooting and help desk support
-- development project plans
-- roles and responsibility shifts
-- re-branding the ILS and related organizations.

== Data Modeling; Logical Versus Physical; Why Do I Care? ==

* Steve Dressler, Georgia Public Library Services, sdressler@georgialibraries.org

I am sure we have all been in the situation of having mountains of data stored in our database, needing a piece of information and yet being unable to determine how to get what we need. Computerized databases have been around for decades now and there are several architectures available; however, the ability of a database developer, regardless of the architecture, to store data in a format that is comprehensible to a businessperson yet readily accessible through software applications remains an impossible challenge.

Topics to be discussed include
o Components comprising a logical model, how it is developed and how is it used?
o Components comprising a physical model, how it is developed and how is it used?
o What does a logical model look like?
o What does a physical model look like?
o Who works with a logical model and why?
o Who works with a physical model and why?
o What is the relationship between the logical model and the physical model?
o What kind of a time investment is required to develop and maintain logical and physical models?
o What are the challenges of keeping the two models in sync as the software application evolves?

Although data modeling is a huge discipline and presents research topics for millions of theses and dissertations, this twenty-minute snapshot view will allow anyone, technical or business, to sit through a development meeting and be able to grasp what is being discussed as well as gain a better understanding of logical and physical business flows.

== Media, Blacklight, and viewers like you. ==

* Chris Beer, WGBH, chris_beer@wgbh.org

There are many shared problems (and solutions) for libraries and archives in the interest of helping the user. There are also many "new" developments in the archives world that the library communities have been working on for ages, including item-level cataloging, metadata standards, and asset management. Even with these similarities, media archives have additional issues that are less relevant to libraries: the choice of video players, large file sizes, proprietary file formats, challenges of time-based media, etc. In developing a web presence, many archives, including the WGBH Media Library and Archives, have created custom digital library applications to expose material online. In 2008, we began a prototyping phase for developing scholarly interfaces by creating a custom-written PHP front-end to our Fedora repository.

In late 2009, we finally saw the (black)light, and after some initial experimentation, decided to build a new, public website to support our IMLS-funded /Vietnam: A Television History/ archive (as well as existing legacy content). In this session, we will share our experience of and challenges with customizing Blacklight as an archival interface, including work in rights management, how we integrated existing Ruby on Rails user-generated content plugins, and the development of media components to support a rich user experience.

== DAMS PAS - Digital Asset Management System, Public Access System ==

* Declan Fleming, University of California, San Diego, dfleming@ucsd.edu
* Esmé Cowles, University of California, San Diego, ecowles@ucsd.edu

After years of describing our DAMS with Powerpoint, we finally have a public access system that we can show our mothers. And code4lib! The UCSD Libraries DAMS is an RDF based asset repository containing over 250,000 items and their derivatives. We describe the core system, the metadata and storage challenges involved in managing hundreds of thousands of items, and the interesting political aspects involved in releasing subsets to the public. We also describe the caching approach we used to ensure performance and access control.

== You Either Surf or You Fight: Integrating Library Services with Google Wave ==

* Sean Hannan, Sheridan Libaries, Johns Hopkins University, shannan@jhu.edu

So Google Wave is a new shiny web toy, but did you know that it's also a great platform for collaboration and research? (I bet you did.) ...And what platform for collaboration and research would not be complete without some library tools to aid and abet that process? I will talk about how to take your library web services and integrate them with Google Wave to create bots that users can interact with to get at your resources as part of their social and collaborative work.

== The Linked Library Data Cloud: Stop talking and start doing ==

* Ross Singer, Talis, ross.singer@talis.com

A year later and how far has Linked Library Data come? Outside of the Swedish National Library's LIBRIS (which already existed), the return of lcsh.info as http://id.loc.gov/authorities/ and LC's Chronicling America, not much. But entry to the Linked Data cloud might be easier than you think. This presentation will describe various projects that are out in the wild that can bridge the gap between our legacy data and the semantic web, incremental steps we can take modeling our data, why linked data matters and a demonstration of how a small template changes can contribute to the Linked Data cloud.

== A code4lib Manifesto ==

* Dan Chudnov, No Fixed Hairstyle, dchud at umich edu

code4lib started with a half dozen library hackers and a list and it ain't like that anymore. I come to code4lib with strong opinions about why it's a positive force in my professional and personal life, but they're probably different from your opinions. I will share these opinions rudely yet succinctly to challenge everyone to think and argue about why code4lib works and what we need to do to keep it working.

== Cloud4lib ==

* Jeremy Frumkin, University of Arizona, frumkinj at u library arizona edu
* Terry Reese, Oregon State University, terry.reese at oregonstate edu

Major library vendors are creating proprietary platforms for libraries. We will propose that the code4lib community pursue the cloud4lib, a open digital library platform based on open source software and open services. This platform would provide common service layers for libraries, not only via code, but also allow libraries to easily utilize tools and systems through cloud services. Instead of a variety of competing cloud services and proprietary platforms, cloud4lib will attempt to be a unifying force that will allow libraries to be consumer of the services built on top of it as well as allow developers / researchers / code4lib'ers to hack, extend, and enhance the platform as it matures.

== Iterative development done simply ==

* Emily Lynema, North Carolina State University Libraries, emily_lynema@ncsu.edu

With a small IT unit and a wide array of projects to support, requests for development from business stakeholders in the library can quickly spiral out of control. To help make sense of the chaos, increase the transparency of the IT "black box," and shorten time lag between requirements definition and functional releases, we have implemented a modified Agile/SCRUM methodology within the development group in the IT department at NCSU Libraries.

This presentation will provide a brief overview of the Agile methodology as an introduction to our simplified approach to iteratively handling multiple projects across a small team. This iterative approach allows us to regularly re-evaluate requested enhancements against institutional priorities and more accurately estimate timelines for specific units of functionality. The presentation will highlight how we approach each development cycle (from planning to estimating to re-aligning) as well as some of the actual tools and techniques we use to manage work (like JIRA and Greenhopper). It will identify some challenges faced in applying an established development methodology to a small team of multi-tasking developers, the outcomes we've seen, and the areas we'd like to continue improving. These types of iterative planning/development techniques could be adapted by even a single developer to help manage a chaotic workplace.

== Public Datasets in the Cloud ==

* Rosalyn Metz, Wheaton College, metz_rosalyn@wheatoncollege.edu
* Michael B. Klein, Oregon State University, Michael.Klein@oregonstate.edu

When most people think about cloud computing (if they think about it at all), it usually takes one of two forms: Infrastructure Services, such as Amazon EC2 and GoGrid, which provide raw, elastic computing capacity in the form of virtual servers, and Platform Services, such as Google App Engine and Heroku, which provide preconfigured application stacks and specialized deployment tools.

Several providers, however, offer access to large public datasets that would be impractical for most organizations to download and work with locally. From a 67-gigabyte dump of DBpedia's structured information store to the 180-gigabyte snapshot of astronomical data from the Sloan Digital Sky Survey, chemistry and biology to economic and geographic data, these datasets are available instantly and backed by enough pay-as-you-go server capacity to make good use of them.

We will present an overview of currently-available datasets, what it takes to create and use snapshots of the data, and explore how the library community might push some of its own large stores of data and metadata into the cloud.

== Codename Arctika ==

* Toke Eskildsen, The State and University Library of Denmark, te@statsbiblioteket.dk

There's something missing in the state of Denmark. Most of our web based copyright deposit material is trapped in a dark archive. After a successful pilot; money and time has been allocated to open part of the data. We tried NutchWAX and it worked well, but we wanted more. Proper integrated search with existing library material, extraction of names etc. Therefore we propose the following recipe: Take a slice of a dark archive with copyright deposit material. Get permission to publish it (the tricky bit). Add an ARC reader to get the bits, Tika to get the text and Summa to get large-scale index and faceting. We mixed it up and we will show what happened.

== JeromeDL - an open source social semantic digital library ==

* Sebastian Ryszard Kruk, Knowledge Hives, sebastian.kruk@knowledgehives.com
* Jodi Schneider, DERI NUI Galway, jschneider@pobox.com

We will tell about the idea of binding together semantics coming from two sources: legacy, well-crafted annotations provided by librarians, and less organized/structured annotations provided by the community of library users. We will present <a href="http://www.jeromedl.org/">JeromeDL system</a> that enables users to provide and manage such annotations; it also implements a number of information discovery solutions that utilize these combined annotations, including collaborative browsing, natural language query templates and collaborative filtering. We will also talk about a vocabulary service used by JeromeDL that encourages users to provide more meaningful annotations than just tags. Finally, we will show how JeromeDL-based libraries contribute to the Web 3.0 linked data by utilizing standard vocabularies, such as SIOC, FOAF, and WordNet, and publishing RDF description of library content.

== Kill the search button ==

* Michael Poltorak Nielsen, State and University Library, Denmark, mn@statsbiblioteket.dk
* Jørn Thøgersen, State and University Library, Denmark, jt@statsbiblioteket.dk

We demo three concepts that eliminate the search button.

1. Instant search. Why wait for tiresome page reloads when searching? Instant search updates the search result on every key-press. We will show how we integrated this feature into our own library search system with minimal changes to the existing setup.

2. Index lookup. Ever dreamed of your own inline instant index lookup?
We demo an instant index lookup feature that requires no search button and no page refreshes - and without ever leaving the search field.

3. Slide your data. Sliders are an alternative way to fit search results to the user's search context.
Examples are sliders that move search results priorities between title and subject and between books by an author and books about the author.

== Controlling the flood: Re-plumbing fittings between a New Titles List and other services with Yahoo! Pipes. ==

* Jon Gorman, University of Illinois, jtgorman@illinois.edu

About four years ago the University of Illinois decided to create a New Titles service (http://www.library.illinois.edu/newtitles/) that could provide RSS feeds. At the time a balance was struck between complexity of options and limited development time. Currently a feed is created by adding options, each option narrowing the scope of a feed. Selecting a date range, Unit Library and a call number range will retrieve material that match all three of the criteria. It was hoped that at some point a generic tool would be able to further manipulate and combine feeds produced by the simple options to customize very specific feed. Yahoo! Pipes has emerged to fill that niche.

The talk will cover pipes that range from filter for a keyword in one feed to combining the New Titles List with services like the LibraryThing API or Worldcat APIs. Examples will also be given in how to integrate the output of Yahoo! Pipes into webpages and how we have put them into our CMS (OpenCMS). The talk will make sure to address areas where Yahoo! Pipes either fails or is cumbersome and simpler CSS and Javascript solutions have worked.

== Vampires vs. Werewolves: Ending the War Between Developers and Sysadmins with Puppet ==

* Bess Sadler, University of Virginia, bess@virginia.edu

Developers need to be able to write software and deploy it, and often require cutting edge software tools and system libraries. Sysadmins are
charged with maintaining stability in the production environment, and so are often resistant to rapid upgrade cycles. This has traditionally pitted us against each other, but it doesn't have to be that way. Using tools like puppet for maintaining and testing server configuration, nagios for monitoring, and hudson for continuous code integration, UVA has brokered a peace that has given us the ability to maintain stable production environment with a rapid upgrade cycle. I'll discuss both the individual tools, our server configuration, and the social engineering that got us here.

== Building customizable themes for DSpace ==

* Elias Tzoc, Miami University of Ohio, tzoce@muohio.edu

The popularity of DSpace (should I say DuraSpace?) continues to grow!
Many universities and research institutions are using DSpace to create and provide access to digital content — including documents, images, audio, and video. With the variety of content, one of the challenges is "how to create customizable themes for different types of content?"

In 2007, Manakin was developed as a user interface for DSpace based on themes. Now users have the ability to customize the web interface for DSpace collections by editing CSS, XML, and XSLT files. Best of all, a singular theme can be applied to individual communities, collections or items.

This talk will be based on my work creating themes for DSpace, as well as tips & tricks for customizing the look-and-feel for individual communities and collections.
Who knows, maybe someday a group of code4lib developers can create a whole library of themes for DuraSpace — similar to the WordPress or Drupal theme idea!

== HIVE: a new tool for working with vocabularies ==

* Ryan Scherle, National Evolutionary Synthesic Center, rscherle@nescent.org
* Jose Aguera, Universitty of North Carolina, jose.aguera@gmail.com

HIVE is a toolkit that assists users in selecting vocabulary and ontology terms to annotate digital content. The HIVE approach promises to combine the ease of folksonomies with the rigor of traditional vocabularies.

Users can search and browse through terms from a variety of vocabularies and ontologies in one integrated tool. Documents can be submitted to HIVE for automatic analysis, resulting in a set of suggested vocabulary terms.

Your system can interact with common vocabularies such as LCSH and MESH via the central HIVE server, or you can install a local copy of HIVE with your own custom set of vocabularies. This talk will give an overview of the current features of HIVE and describe how to build tools that use the HIVE services.