''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

===Forty-second issue===

Coordinating Editor: Andrew Darby
dates tbd

===Forty-first issue===

Coordinating Editor: Ron Peterson
*Call for proposals: Monday, April 17, 2017
*Second call for proposals: Monday, April 30, 2017 (if necessary)
*Proposals due: Friday, May 11, 2017
*Proposals accepted: Friday, May 18, 2017
*First draft due: Friday, June 8, 2017
*Second draft due: Friday, July 6, 2017
*Publication date: Monday, August 6, 2018

===Fortieth issue===

Coordinating Editor: Ruth Kitchin Tillman
*Call for proposals: Friday, December 29, 2017
*Second call for proposals: Friday, January 19, 2018 (if necessary)
*Proposals due: Tuesday, January 30, 2018
*Proposals accepted: Tuesday, February 6, 2018
*First draft due: Tuesday, March 6, 2018
*Second draft due: Tuesday, April 3, 2018
*Publication date: Friday, May 4, 2018

===Thirty-ninth issue===
Coordinating Editor: Terry Reese
*Call for proposals: Monday, September 25, 2017
*Second call for proposals: Monday, October 16, 2017 (if necessary)
*Proposals due: Friday, November 3, 2017
*Proposals accepted: Friday, November 17, 2017
*First draft due: Friday, December 8, 2017
*Second draft due: Friday, January 5, 2017
*Publication date: Monday, January 29, 2018

===Thirty-eighth issue===
Coordinating Editor: Carol Bean
*Call for proposals: Monday, June 12, 2017
*Second call for proposals: Monday, July 3, 2017 (if necessary)
*Proposals due: Friday, July 14, 2017
*Proposals accepted: Friday, July 21, 2017
*First draft due: Friday, August 18, 2017
*Second draft due: Friday, September 15, 2017
*Publication date: Monday, October 16, 2017

===Thirty-seventh issue===
Coordinating Editor: Sara Amato
*Call for proposals: Monday, March 13, 2017
*Second call for proposals: Monday, April 3, 2017 (if necessary)
*Proposals due: Friday, April 14, 2017
*Proposals accepted: Friday, April 21, 2017
*First draft due: Friday, May 19, 2017
*Second draft due: Friday, June 16, 2017
*Publication date: Monday, July 17, 2017

===Thirty-sixth issue===
Coordinating Editor: Peter Murray
*Call for proposals: Thursday, December 15, 2016
*Second call for proposals: Thursday, January 5, 2017 (if necessary)
*Proposals due: Tuesday, January 17, 2017
*Proposals accepted: Monday, January 23, 2017
*First draft due: Monday, February 20, 2017
*Second draft due: Monday, March 20, 2017
*Publication date: Monday, April 17, 2017

===Thirty-fifth issue===

Coordinating Editor: Ruth Kitchin Tillman

* Call for proposals: Monday, September 26, 2016
* Second call for proposals: Monday, October 17, 2016 (if necessary)
* Proposals due: Friday, October 28, 2016
* Proposals accepted: Friday, November 4, 2016
* First draft due: Friday, December 2, 2016
* Second draft due: Friday, December 30, 2016
* Publication date: Monday, January 30, 2017

===Thirty-fourth issue===
Coordinating Editor: Andrew Darby

* Call for proposals: Monday, June 20, 2016
* Second call for proposals: Monday, July 11, 2016 (if necessary)
* Proposals due: Friday, July 22, 2016
* Proposals accepted: Friday, July 29, 2016
* First draft due: Friday, August 26, 2016
* Second draft due: Friday, September 23, 2016
* Publication date: Monday, October 24, 2016

===Thirty-third issue===
Coordinating Editor: Ron Peterson

* Call for proposals: Monday, March 14, 2016
* Second call for proposals: Monday, April 4, 2016 (if necessary)
* Proposals due: Friday, April 15, 2016
* Proposals accepted: Friday, April 29, 2016
* First draft due: Friday, May 20, 2016
* Second draft due: Friday, June 17, 2016
* Publication date: Monday, July 18, 2016

===Thirty-second issue===
Coordinating Editor: Meghan Finch
* Call for proposals: Monday, December 14, 2015
* Second call for proposals: Monday, January 4, 2016 (if necessary)
* Proposals due: Friday, January 15, 2016
* Proposals accepted: Friday, January 22, 2016
* First draft due: Friday, February 19, 2016
* Second draft due: Friday, March 18, 2016
* Publication date: Monday, April 25, 2016

===Thirty-first issue===
Coordinating Editor: Terry Reese
* Call for proposals: Monday, September 21, 2015
* Second call for proposals: Thursday, October 8, 2015 (if necessary)
* Proposals due: Friday, October 23, 2015
* Proposals accepted: Friday, October 30, 2015
* First draft due: Monday, November 23, 2015
* Second draft due: Monday, December 21, 2015
* Publication date: Monday, January 25, 2016

===Thirtieth issue===
Coordinating editor for issue #30: Carol Bean

* Call for proposals: Thursday, June 11, 2015
* Second call for proposals: Thursday, July 2, 2015 (if necessary)
* Proposals due: Monday, July 13, 2015
* Proposals accepted: Monday, July 20, 2015
* First draft due: Monday, August 17, 2015
* Second draft due: Monday, September 14, 2015
* Publication date: Monday, October 19, 2015

===Twenty-ninth issue===
Coordinating editor for issue #29: Sara Amato

* Call for proposals: Wednesday, March 11, 2015
* Second call for proposals: Wednesday, April 1, 2015 (if necessary)
* Proposals due: Friday, April 10, 2015
* Proposals accepted: Monday, April 20, 2015
* First draft due: Monday, May 18, 2015
* Second draft due: Monday, June 15, 2015
* Publication date: Monday, July 13, 2015

===Twenty-eighth issue===
Coordinating editor for issue #28: Heidi Dowding

Special issue on diversity in library technology.

* Call for proposals: Wednesday, December 10, 2014
* Second call for proposals: Monday, January 5, 2015 (if necessary, adjusted from 31-Dec-2014)
* Proposals due: Monday, January 12, 2015
* Proposals accepted: Monday, January 19, 2015
* First draft due: Monday, February 16, 2015
* Second draft due: Monday, March 16, 2015
* Publication date: Wednesday, April 15, 2015

===Twenty-seventh issue===
Coordinating editor for issue #27: Terry Reese

*Call for proposals: Monday, September 27, 2014
*Second call for proposals: Monday, October 6, 2014 (if necessary)
*Proposals due: Friday, October 24, 2014
*Proposals accepted: Friday, October 31, 2014
*First draft due: Friday, November 21, 2014
*Second draft due: Friday, December 19, 2014
*Publication date: Monday, January 19, 2015

===Twenty-sixth issue===
Coordinating editor for issue #26: Kelley McGrath

*Call for proposals: Monday, June 9, 2014
*Second call for proposals: Monday, June 30, 2014 (if necessary)
*Proposals due: Friday, July 11, 2014
*Proposals accepted: Friday, July 18, 2014
*First draft due: Friday, August 15, 2014
*Second draft due: Friday, September 12, 2014
*Publication date: Monday, October 20, 2014

===Twenty-fifth issue===
Coordinating editor for issue #25: Dan Scott

*Call for proposals: Monday, March 10, 2014
*Second call for proposals: Monday, March 31, 2014 (if necessary)
*Proposals due: Friday, April 11, 2014
*Proposals accepted: Friday, April 18, 2014
*First draft due: Friday, May 16, 2014
*Second draft due: Friday, June 13, 2014
*Publication date: Monday, July 14, 2014

===Twenty-fourth issue===
Coordinating editor for issue #24: Ron Peterson

*Call for proposals: Monday, December 9, 2013
*Call for proposals #2: Monday, December 30, 2013 (if necessary)
*Proposals due: Friday, January 10, 2014
*Proposals accepted: Friday, January 17, 2014
*First draft due: Friday, February 14, 2014
*Second draft due: Friday, March 14, 2014
*Publication date: Monday, April 14, 2014

===Twenty-third issue===
Coordinating editor for issue #23: Shawn Averkamp
* Call for proposals: Monday, September 9, 2013
* Call for proposals #2: Monday September 30, 2013 (if necessary)
* Proposals due: Friday, October 11, 2013
* Proposals accepted: Friday, October 18, 2013
* First draft due: Friday, November 15, 2013
* Second draft due: Friday, December 13, 2013
* Publication date: Monday, January 13, 2014

===Twenty-second issue===
Coordinating editor for issue #22: Sara Amato
* Call for proposals: Monday, June 10, 2013
* Call for proposals #2: July 5, 2013 (if necessary)
* Proposals due: Friday, July 12, 2013
* Proposals accepted: Friday, July 19, 2013
* First draft due: Friday, August 16, 2013
* Second draft due: Friday, September 13, 2013
* Publication date: Monday, October 14, 2013

===Twenty-first issue===
Coordinating editor for issue #21: Terry Reese
* Call for proposals: Monday, March 11, 2013
* Call for proposals #2: Monday, April 1, 2013
* Proposals due: Friday, April 12, 2013
* Proposals accepted: Friday, April 19, 2013
* First draft due: Friday, May 17, 2013
* Second draft due: Friday, June 14, 2013
* Publication date: Monday, July 15, 2013

===Twentieth issue===
Coordinating editor for issue #20: [[User:DataGazetteer|Peter Murray]]
* Call for proposals:     Monday, December 10, 2012
* Call for proposals #2: Monday, January 7, 2013 (if necessary)
* Proposals due:          Friday, January 18, 2013
* Proposals accepted:     Friday, January 25, 2013
* First draft due:        Friday, February 22, 2013
* Second draft due:       Friday, March 22, 2013
* Publication date:       Monday, April 15, 2013

===Nineteenth issue===
Coordinating editor for issue #19: Andrew Darby
* Call for proposals: Monday, September 10, 2012
* Proposals due: Friday, October 12, 2012
* Proposals accepted: Friday, October 19, 2012
* First draft due: Friday, November 16, 2012
* Second draft due: Friday, December 14, 2012
* Publication date: Monday, January 14, 2013

===Eighteenth issue===
Coordinating editor for issue #18: Ron Peterson
* Call for proposals: Monday, May 28, 2012
* Proposals due: Friday, June 29, 2012
* Proposals accepted: Friday, July 6, 2012
* First draft due: Friday, August 3, 2012
* Second draft due: Friday, August 31, 2012
* Publication date: Monday, October 1, 2012

===Seventeenth issue===
Coordinating editor for issue #17: Tim Lepczyk
* Call for proposals: Wednesday, February 8, 2012
* Proposals due: Tuesday, February 28, 2012
* Proposals accepted: Tuesday, March 6, 2012
* First draft due: Tuesday, April 3, 2012
* Second draft due: Tuesday, May 1, 2012
* Publication date: Friday, June 1, 2012

===Sixteenth issue===
Coordinating editor for issue #16: Carol Bean
* Call for proposals: Monday, September 26, 2011
* Proposals due: Friday, October 28, 2011
* Proposals accepted: Friday, November 4, 2011
* First draft due: Friday, December 2, 2011
* Second draft due: Friday, December 30, 2011
* Publication date: Monday, January 30, 2012

===Fifteenth issue===
Coordinating editor for issue #15: Tod Olson
* Call for proposals: Monday, June 27, 2011
* Proposals due: Friday, July 29, 2011
* Proposals accepted: Friday, August 5, 2011
* First draft due: Friday, September 2, 2011
* Second draft due: Friday, September 30, 2011
* Publication date: Monday, October 31, 2011

===Fourteenth issue===

* Call for proposals: Monday, March 21, 2011
* Proposals due: Friday, April 22, 2011
* Proposals accepted: Friday, April 29, 2011
* First draft due: Friday, May 27, 2011
* Second draft due: Friday, June 24, 2011
* Publication date: Monday, July 25, 2011

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

2013-02-06T02:59:39Z

Agdarby: /* Newcomer Dinner, Tuesday 2/12 */

2013 social activities

2013-02-05T23:34:04Z

Agdarby: /* Newcomer Dinner, Tuesday 2/12 */

Code4Lib Journal Life of an Article

2013-02-05T18:33:30Z

Agdarby: moved Code4Lib Journal Email Life of an Article to Code4Lib Journal Life of an Article

[[File:C4LJ_life_of_an_article_3.jpg]]

Code4Lib Journal Email Life of an Article

2013-02-05T18:33:30Z

Agdarby: moved Code4Lib Journal Email Life of an Article to Code4Lib Journal Life of an Article

#REDIRECT [[Code4Lib Journal Life of an Article]]

File:C4LJ life of an article 3.jpg

2013-02-05T18:29:57Z

Agdarby: uploaded a new version of "File:C4LJ life of an article 3.jpg"

File:C4LJ life of an article 3.jpg

2013-02-05T18:25:46Z

Agdarby:

Code4Lib Journal Life of an Article

2013-02-05T16:57:09Z

Agdarby: Created page with "File:C4LJ_life_of_an_article_3.jpg"

[[File:C4LJ_life_of_an_article_3.jpg]]

Code4Lib Journal

2013-02-05T16:52:49Z

Agdarby:

* [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]]
* [[Code4lib Journal Republication Guidelines]]
** [[COinS (layman's description)]]
* [[Code4Lib Journal WordPress Customizations]]
* [[Code4Lib Journal Email Life of an Article]]

<br/>

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

[[Code4Lib Journal PDFs]]

[[Category: Code4Lib Journal]]

2013-01-09T15:18:33Z

Agdarby: /* Intro to NoSQL Databases */

Proposals '''now closed'''.

Spaces available: 4+ Rooms

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

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

Description.
</pre>

==Full Day==

===Drupal4lib Sub-con Barcamp===

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

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

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

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

====I plan on attending:====

=====All Day=====
*Margaret Heller
*Mahria Lebow
*Paula Gray-Overtoom, pgrayove at gmail.com

=====Morning=====
* [[User:Kevenj|Keven Jeffery]]
* Sean Chen

=====Afternoon=====
* Kevin Reiss, Princeton University Library, kr2 at princeton.edu (afternoon only)
* Christina Salazar (afternoon only)
* Sarah Dooley (afternoon)
* Josh Wilson, joshwilsonnc at gmail (likely afternoon only)
* Ken Varnum, varnum at umich e-d-u
* Cody Hennesy, chennesy at library berkeley edu

==Half Day Morning==
=== Open space session ===

* Dan Chudnov, dchud at gwu edu

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

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

'''I plan on attending:'''
* Devon Smith
* Esmé Cowles, escowles@ucsd.edu
* Jason Casden
* Ryan Eby
* mark matienzo
* Donald Mennerich
* Patrick Berry, pberry@csuchico.edu

=== Delivery services ===
* Ted Lawless, Brown University Library, tlawless at brown edu.
* Kevin Reiss, Princeton University Library, kr2 at princeton edu.

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

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

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

'''I plan on attending:'''
* Ken Varnum, varnum at umich e-d-u
* Ayla Stein
* Curtis Thacker
* Rosalyn Metz rosalynmetz at gmail com
* James Van Mil
* Andrew Nagy
* Ranti Junus

=== Intro to Blacklight CANCELLED ===

PLEASE NOTE: This pre-conference has been cancelled in favor of joining forces with the RailsBridge workshop. The afternoon Blacklight session will still be offered.

=== RailsBridge Intro to Ruby on Rails ===
* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)
* Shaun Ellis (helper), Princeton University Library, shaune@princeton.edu
* Ross Singer, Talis, rossfsinger@gmail.com
* Adam Wead (helper), Rock and Roll Hall of Fame, awead@rockhall.org
* Bess Sadler, Stanford University, bess@stanford.edu
* Anyone else want to come and help folks? Contact Jason.

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

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

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

Please add your name below and fill out the [https://docs.google.com/spreadsheet/viewform?formkey=dEpxd0tzU1ZscnU5QUUtd0JGUk9qQkE6MA#gid=0 experience survey].

'''I plan on attending:'''
# First and last name and email address
# John MacGillivray
# Jon Stroop - jstroop at princeton
# Christina Salazar - christina{dot}salazar{at}csuci{dot}edu
# Karen Coombs - coombsk{at}oclc{dot}org
# Becky Yoose - b dot yoose at google overlord
# Jeremy Morse - jgmorse at umich
# Julia Bauder - julia{dot}bauder{at}gmail{dot}com
# Chung Kang
# Karen Miller - k-miller3{at}northwestern{dot}edu
# Betsy Coles - bcoles{at}caltech{dot}edu
# Jay Luker - jay{dot}luker{at}gmail{dot}com
# Santi Thompson
# Sarah Dooley - sarah{at}nclive{dot}org
# Brandon Dudley
# Ken Irwin
# Dennis Ogg - ogg{at}ucar{dot}edu
# Ian Walls - iwalls{at}library{dot}umass{dot}edu
# Steven Villereal – villereal{at}gmail{dot}com
# Hillel Arnold - hillel{dot}arnold{at}gmail{dot}com
# Josh Wilson - joshwilsonnc at gmail
# Cynthia Ng - cynthia [dot] s [dot] ng [at] gmail
# Ian Chan
# Heidi Frank - hf36{at}nyu{dot}edu
# Mark Mounts
# Bill McMillin - wmcmilli{at}pratt {dot}edu
# David Lacy - david dot lacy at villanova dot edu
# Courtney Greene - crgreene at indiana dot edu
# Laney McGlohon - lmcglohon@getty.edu
# Nancy Enneking - nenneking@getty.edu
# Jason Raitz - jcraitz at ncsu dot edu
# Nick Cappadona
# Steven Marsden
# Linda Ballinger - ballingerl at newberry dot org
# Brendan Quinn - brendan-quinn at northwestern dot edu
# Michael Levy - mlevy {at}ushmm {dot}org
# Michael North (m-north at northwestern dot edu)
# Shawn Averkamp - shawnaverkamp{at}gmail{dot}com
# Tim Thompson - t.thompson5{at}miami{dot}edu
# Allan Berry - allan{dot}berry{at}gmail{dot}com

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

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

'''I plan on attending:'''
* Esha Datta
* Trevor Thornton
* Michael Doran
* Ray Schwartz - schwartzr2@wpunj.edu
* Kevin Clarke
* Andreas Orphanides
* Tommy Ingulfsen - tommying{at}caltech{dot}edu
* Harrison Dekker
* Eric James eric dot james at yale dot edu
* Sean Crowe - sean.crowe@uc.edu
* Scott Hanrath
* Erin Fahy - erin.fahy at mtholyoke edu
* Karen Coyle - kcoyle at kcoyle.net
* Charles Draper
* David Uspal
* Shawn Kiewel - smkiewel at uga dot edu
* Stephanie Collett - stephanie dot collett at ucop dot edu
* Declan Fleming - declan at declan dot net
* David Gonzalez - d.gonzalez26 at umiami dot edu

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

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

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

'''I plan on attending:'''
* Devon Smith
* Esha Datta
* Ray Schwartz - schwartzr2@wpunj.edu
* Karen Coombs - coombsk{at}oclc{dot}org
* Julia Bauder - julia{dot}bauder{at}gmail{dot}com
* Jason Stirnaman (jstirnaman at kumc.edu)
* Joshua Gomez
* Ayla Stein
* Harrison Dekker
* Ian Walls - iwalls{at}library{dot}umass{dot}edu
* Scott Hanrath
* [[User:Kevenj|Keven Jeffery]]
* James Van Mil
* Sean Crowe - sean.crowe@uc.edu
* Karen coyle - kcoyle at kcoyle.net
* David Lacy - david dot lacy at villanova dot edu
* mark matienzo
* David Uspal
* Emily Lynema - ejlynema at ncsu dot edu
* Sean Chen
* Donald Mennerich
* Allan Berry - allan{dot}berry{at}gmail{dot}com
* Declan Fleming - declan at declan dot net
* Chick Markley -- chick at qrhino dot com

=== Intro to Hydra ===
* Adam Wead, Rock and Roll Hall of Fame (awead at rockhall.org)
* Justin Coyne, Data Curation Experts (justin.coyne at curationexperts.com)
* Mark Bussey, Data Curation Experts (mark at curationexperts.com)

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

'''I plan on attending:'''
* Jeremy Prevost
* Dennis Ogg - ogg{at}ucar{dot}edu
* Terry Brady
* Betsy Coles - bcoles{at}caltech{dot}edu
* Brendan Quinn - brendan-quinn at northwestern dot edu
* Shawn Kiewel - smkiewel at uga dot edu
* Steven Villereal – villereal{at}gmail{dot}com
* Ryan Eby
* Dean Farrell
* Ian Chan
* Mark Mounts
* Carl Jones
* Laney McGlohon - lmcglohon@getty.edu
* Nancy Enneking - nenneking@getty.edu
* First and last name
* Allan Berry - allan{dot}berry{at}gmail{dot}com

=== Intro to Blacklight ===
* Bess Sadler, Stanford University Library (bess at stanford.edu)
* Jason Ronallo, NC State (jronallo at gmail.com)
* Shaun Ellis (helper), Princeton University Library, (shaune@princeton.edu)

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

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

'''I plan on attending:'''
* John MacGillivray
* Jon Stroop
* Jeremy Morse - jgmorse at umich
* Karen Miller - k-miller3{at}northwestern{dot}edu
* Tommy Ingulfsen - tommying{at}caltech{dot}edu
* Chung Kang
* Santi Thompson
* Brandon Dudley
* Ken Irwin
* Hillel Arnold
* Heidi Frank - hf36{at}nyu{dot}com
* Chris Sharp - csharp{at}georgialibraries{dot}org
* Bill McMillin - wmcmilli{at} pratt{dot} edu
* Jason Raitz - jcraitz at ncsu dot edu
* Linda Ballinger - ballingerl at newberry dot org
* Tim Thompson - t.thompson5{at}miami{dot}edu

=== DPLA Intro/Hacking ===

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

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

'''I plan on attending:'''
* First and last name

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

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

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

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

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

'''I plan on attending:'''
* Becky Yoose
* Lisa Rabey
* Cynthia Ng (maybe) - cynthia [dot] s [dot] ng [at] gmail
* Patrick Berry, pberry@csuchico.edu

=== Solr 4 In Depth ===
* Contact: Erik Hatcher (erik.hatcher at lucidworks.com)

The long awaited and much anticipated Solr 4 has been released! It's a really big deal. There are so many improvements, it makes the head spin. This session will cover the major feature improvements from Lucene's flexible indexing and scoring API up through SolrCloud in a digestable half-day format. Sounds like this is an evening thing that might happen at a bar somewhere?

'''I plan on attending:'''
* First and last name
* Erin Fahy - erin.fahy at mtholyoke edu
* Esmé Cowles, escowles@ucsd.edu
* Jon Stroop
* Adam Constabars
* Kevin Clarke
* Jacob Andresen
* Ted Lawless (tlawless at brown dot edu)
* Jay Luker
* Tom Burton-West
* Curtis Thacker
* Eric James eric dot james at yale dot edu
* Bess Sadler (bess at stanford dot edu)
* Michael North
* Charles Draper
* Nick Cappadona
* Stephanie Collett - stephanie dot collett at ucop dot edu
[[Category:Code4Lib2013]]

2012-01-17T21:45:07Z

Agdarby: /* 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
* Kåre Fiedler Christiansen (morning only)
* Jørn Thøgersen
* Michael Poltorak Nielsen
* Dre
* Andrew Darby

==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
* Shaun Ellis (shaune@princeton.edu)
* Wendy Robertson
* Joel Richard (richardjm AT si DOT edu)
* Devon Smith

=== 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)
* Sepehr Mavedati (sepehr DOT mavedati AT utoronto DOT ca)
* Anna Headley aheadle1 swarthmore edu
* Mads Villadsen
* Jonathan Rochkind
* Shahin Sahebi (shahin.ezzatsahebi at utoronto dot ca)
* Naomi Dushay (ndushay at stanford dot edu)
* Jeremy Nelson

==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
* Shaun Ellis (shaune@princeton.edu)
* Mads Villadsen
* Kåre Fiedler Christiansen
* Shahin Sahebi (shahin.ezzatsahebi@utoronto.ca)
* Devon Smith
* Jeremy Nelson

=== 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)
* Jonathan Rochkind

=== 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)
* Sarah Johnston (johnsts@stolaf.edu)
* Derek Merleaux (derek@merleaux d0t net)

=== "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)
* Anna Headley aheadle1 swarthmore edu
* Michael Poltorak Nielsen
* Wendy Robertson
* Joel Richard (richardjm AT si DOT edu)
* Jonathan Rochkind
* Naomi Dushay (ndushay at stanford dot edu)

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

5. Microsoft Audio Visual Indexing System - [http://research.microsoft.com/mavis]

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: Behrooz Chitsaz; 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>
* Shaun Ellis (shaune AT princeton DOT edu)
* Derek Merleaux (derek@merleaux d0t net)
* Anna Headley
* Mads Villadsen
* Kåre Fiedler Christiansen
* Jørn Thøgersen
* Michael Poltorak Nielsen
* Dileshni Jayasinghe
* Matt Phillips (mphillips@law.harvard.edu)
* Wendy Robertson
* Shahin Sahebi
* Matt Connolly <mjc12 AT cornell dot edu>
* Jeremy Nelson
* Naomi Dushay (ndushay at stanford dot edu)
* Dre
* Ken Varnum (varnum umich edu)

[[Category: Code4Lib2012]]

Code4Lib Journal Tech Wishlist

2011-02-01T20:29:10Z

Agdarby:

Things on this page aren't neccesarily consensus, just things people listed as tech wishlist.

* Seperate author names in individual fields in db, for better metadata generation. (Then make export of DOAJ metadata use it, to make it a fully automated process!)

* epub and/or PDF export of a complete issue

* PDF of individual article

* Include "cite as" text on each page, with several major citation formats filled in with our data. Especially important because we use an "article number", rather than a page number -- which is supported by most citation formats, but it's not obvious from looking at an article what it's "article number" _is_, you have to know to get it from the URL. Makes it hard to cite correctly.

* Automated list of "most viewed articles", from WP statistics or Google Analytics?

[[Category: Code4Lib Journal]]

Code4Lib Journal Email Templates

2009-08-13T19:06:16Z

Agdarby: /* 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 c4lj-articles@googlegroups.com 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 c4lj-articles@googlegroups.com 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 c4lj-articles@googlegroups.com 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 c4lj-articles@googlegroups.com with the additional information requested.

You may also contact the editors at c4lj-articles@googlegroups.com 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 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.

== 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 c4lj-articles@googlegroups.com in the future with a new or revised proposal.

[[Category: Code4Lib Journal]]