Code4Lib - User contributions [en]

Code4Lib Journal Publicity Venues

2022-05-10T23:01:38Z

Ronpeterson: IFLA server not found

== Distributing Call for Submissions ==

* [https://code4lib.org/ Code4Lib website]
* [http://journal.code4lib.org/call-for-submissions c4lj Journal website]
* [https://groups.google.com/forum/?hl=en#!forum/c4lj-discuss c4lj-discuss group]
* [http://listserv.syr.edu/archives/autocat.html AUTOCAT] autocat@listserv.syr.edu
* [https://lists.clir.org/cgi-bin/wa?A0=CODE4LIB Code4Lib] code4lib@lists.clir.org
* <s>[http://lists.ala.org/wws/arc/lita-l LITA-L] lita-l@lists.ala.org</s>
* [http://metadatalibrarians.monarchos.com/ Metadatalibrarians] metadatalibrarians@lists.monarchos.com
* [https://listserv.uc.edu/scripts/wa.exe?A0=WEB4LIB Web4Lib] web4lib@listserv.uc.edu
* [http://home.olemiss.edu/~noe/llfaq.html Law-Lib] law-lib@ucdavis.edu
* [http://www.mlanet.org/discussion/medlibl.html MedLib] medlib-l@list.uvm.edu
* <s>[http://infoserv.inist.fr/wwsympa.fcgi/info/diglib IFLA DigLib] diglib@infoserv.inist.fr</s>
* [http://www.inetbib.de/listenarchiv/ InetBib] inetbib@ub.uni-dortmund.de
* [https://listserv.niif.hu/mailman/listinfo/katalist Katalist] katalist@listserv.niif.hu

* <s>[http://listserv.uic.edu/htbin/wa?A0=drupal4lib Drupal4Lib] drupal4lib@listserv.uic.edu</s>
* <s>[http://mail.asis.org/mailman/listinfo/asis-l ASIS] asis-l@mail.asist.org</s> (no longer active)
* <s>[https://listserv.nd.edu/cgi-bin/wa?A0=NGC4LIB NGC4Lib] ngc4lib@listserv.nd.edu</s>
* <s>[http://mail.archive.org/pipermail/ol-lib/ Open Library] ol-lib@archive.org</s>
* <s>[http://lists.sourceforge.net/lists/listinfo/oss4lib-discuss OSS4Lib] oss4lib-discuss@lists.sourceforge.net</s> (no longer active)
* <s>[https://listserv.nd.edu/cgi-bin/wa?A0=Usability4Lib Usability4Lib] usability4lib@listserv.nd.edu</s> (listerv shut down)
* <s>[https://listserv.nd.edu/cgi-bin/wa?A0=XML4LIB XML4Lib] xml4lib@listserv.nd.edu</s> (listserv shut down)
Web Sites

* <s>[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.</s>

== Announcing Publication ==

Announce at above mailing lists and the code4lib website.

== Twitter Hashtag ==

Use #c4lj - its use is tracked in https://docs.google.com/spreadsheets/d/1n7K3JhtBDMqUB1TaBBIEIPgAlNRANRlJhUDr5dgKJGs/edit?usp=sharing

[[Category: Code4Lib Journal]]

Code4Lib Journal Publicity Venues

2022-05-10T01:30:00Z

Ronpeterson: LITA list no longer active

== Distributing Call for Submissions ==

* [https://code4lib.org/ Code4Lib website]
* [http://journal.code4lib.org/call-for-submissions c4lj Journal website]
* [https://groups.google.com/forum/?hl=en#!forum/c4lj-discuss c4lj-discuss group]
* [http://listserv.syr.edu/archives/autocat.html AUTOCAT] autocat@listserv.syr.edu
* [https://lists.clir.org/cgi-bin/wa?A0=CODE4LIB Code4Lib] code4lib@lists.clir.org
* <s>[http://lists.ala.org/wws/arc/lita-l LITA-L] lita-l@lists.ala.org</s>
* [http://metadatalibrarians.monarchos.com/ Metadatalibrarians] metadatalibrarians@lists.monarchos.com
* [https://listserv.uc.edu/scripts/wa.exe?A0=WEB4LIB Web4Lib] web4lib@listserv.uc.edu
* [http://home.olemiss.edu/~noe/llfaq.html Law-Lib] law-lib@ucdavis.edu
* [http://www.mlanet.org/discussion/medlibl.html MedLib] medlib-l@list.uvm.edu
* [http://infoserv.inist.fr/wwsympa.fcgi/info/diglib IFLA DigLib] diglib@infoserv.inist.fr
* [http://www.inetbib.de/listenarchiv/ InetBib] inetbib@ub.uni-dortmund.de
* [https://listserv.niif.hu/mailman/listinfo/katalist Katalist] katalist@listserv.niif.hu

* <s>[http://listserv.uic.edu/htbin/wa?A0=drupal4lib Drupal4Lib] drupal4lib@listserv.uic.edu</s>
* <s>[http://mail.asis.org/mailman/listinfo/asis-l ASIS] asis-l@mail.asist.org</s> (no longer active)
* <s>[https://listserv.nd.edu/cgi-bin/wa?A0=NGC4LIB NGC4Lib] ngc4lib@listserv.nd.edu</s>
* <s>[http://mail.archive.org/pipermail/ol-lib/ Open Library] ol-lib@archive.org</s>
* <s>[http://lists.sourceforge.net/lists/listinfo/oss4lib-discuss OSS4Lib] oss4lib-discuss@lists.sourceforge.net</s> (no longer active)
* <s>[https://listserv.nd.edu/cgi-bin/wa?A0=Usability4Lib Usability4Lib] usability4lib@listserv.nd.edu</s> (listerv shut down)
* <s>[https://listserv.nd.edu/cgi-bin/wa?A0=XML4LIB XML4Lib] xml4lib@listserv.nd.edu</s> (listserv shut down)
Web Sites

* <s>[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.</s>

== Announcing Publication ==

Announce at above mailing lists and the code4lib website.

== Twitter Hashtag ==

Use #c4lj - its use is tracked in https://docs.google.com/spreadsheets/d/1n7K3JhtBDMqUB1TaBBIEIPgAlNRANRlJhUDr5dgKJGs/edit?usp=sharing

[[Category: Code4Lib Journal]]

Code4Lib Journal Name Change Policy

2022-05-09T23:03:01Z

Ronpeterson: Added category

The policy can be viewed at https://journal.code4lib.org/?page_id=16545

[[Category: Code4Lib Journal]]

Code4Lib Journal Name Change Policy

2022-05-09T23:00:53Z

Ronpeterson: Redirected to journal website

The policy can be viewed at https://journal.code4lib.org/?page_id=16545

Code4Lib Journal Name Change Policy

2022-05-09T22:47:31Z

Ronpeterson: Original version

May 9, 2022

As part of our commitment to addressing the needs of all research communities to improve inclusivity, diversity, and equity and inclusion, the Code4Lib Journal Editorial Committee (referred to hereafter as the “Editorial Committee”) has implemented a policy to enable name and pronoun changes for our authors<sup>1</sup>. Going forward, all requests to make a name or pronoun change will be honored. This includes, but is not limited to, name changes because of marriage, divorce, gender affirmation, and religious conversion. The Code4Lib Journal will not publish a correction notice nor require any form of proof or supporting documentation.

All references to the author within the Code4Lib Journal will be fully replaced online, and their indexing metadata (which affects how the author list appears in other outlets (Director of Open Access Journals, Google Scholar, etc.) will be updated accordingly. This replaces the author's name fully while ensuring that citation information such as the DOI for the paper remains the same. All previous citations to the paper remain valid.

In order to enable co-authors to update the way they cite the paper in the future, we recommend informing them of the name change to the article. The Editorial Committee will ask authors who are updating their name to select one of three options: (1) the Editorial Committee will contact the co-authors on the author’s behalf; (2) the author may prefer to contact the co-authors themselves;or (3) authors may opt not to inform them at all.

To request a name and/or pronoun change, please email journal@Code4Lib.org with your request, links to the articles in question, and confirmation as to whether or not you permit the Editorial Committee to contact the co-authors to inform them of the change. The author will be sent a draft with the changes and asked to review and approve it before publication. We are committed to implementing the updates promptly and confidentially in recognition of the potentially sensitive nature of these requests.

Please note that misspellings or other errors in an author’s name in published papers will be managed following Code4Lib’s usual post-publication corrections policy. Outdated affiliations or changes to email addresses that are not due to changes to the author’s name will not be updated.

Important: Over time, the Editorial Committee will be working to refine and improve this policy, and in particular to get closer to the guiding principles outlined in ‘A vision for a more trans-inclusive publishing world: guest article’, published on the COPE website. While our current process for handling name change requests does not guarantee the removal of the author’s previous name from all public-facing records, as recommended in the COPE article, we are currently exploring what systems and infrastructure improvements can be made to allow for more of these changes in the future.

== Notes: ==
<sup>1</sup> We have drawn on SAGE’s [https://us.sagepub.com/en-us/nam/name-change-policy Name Change Policy] as the basis for our policy.

Code4Lib Journal Deadlines

2018-04-17T13:52:24Z

Ronpeterson: /* Deadlines for Issues */

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

Code4Lib Journal Publicity Venues

2016-07-20T01:31:42Z

Ronpeterson:

== Distributing Call for Submissions ==

* [http://journal.code4lib.org/call-for-submissions c4lj website]
* [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@lists.ala.org
* [http://metadatalibrarians.monarchos.com/ Metadatalibrarians] metadatalibrarians@lists.monarchos.com
*<s> [https://listserv.nd.edu/cgi-bin/wa?A0=NGC4LIB NGC4Lib] ngc4lib@listserv.nd.edu</s>
* <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
* <s>[https://listserv.nd.edu/cgi-bin/wa?A0=Usability4Lib Usability4Lib] usability4lib@listserv.nd.edu</s> (listerv shut down)
* [https://listserv.nd.edu/cgi-bin/wa?A0=WEB4LIB Web4Lib] web4lib@listserv.nd.edu
* <s>[https://listserv.nd.edu/cgi-bin/wa?A0=XML4LIB XML4Lib] xml4lib@listserv.nd.edu</s> (listserv shut down)
* [http://home.olemiss.edu/~noe/llfaq.html Law-Lib] law-lib@ucdavis.edu
* [http://www.mlanet.org/discussion/medlibl.html MedLib] medlib-l@list.uvm.edu
* [http://infoserv.inist.fr/wwsympa.fcgi/info/diglib IFLA DigLib] diglib@infoserv.inist.fr
* [http://mail.asis.org/mailman/listinfo/asis-l ASIS] asis-l@asis.org
* [http://www.inetbib.de/listenarchiv/ InetBib] inetbib@ub.uni-dortmund.de

Web Sites

* <s>[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.</s>

== Announcing Publication ==

Announce at above mailing lists and the code4lib website.

== Twitter Hashtag ==

Use #c4lj - its use is tracked in https://docs.google.com/spreadsheets/d/1n7K3JhtBDMqUB1TaBBIEIPgAlNRANRlJhUDr5dgKJGs/edit?usp=sharing

[[Category: Code4Lib Journal]]

Code4Lib Journal Deadlines

2016-02-24T21:09:44Z

Ronpeterson:

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

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

Code4Lib Journal Deadlines

2016-02-24T21:07:34Z

Ronpeterson:

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

===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 22, 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 18, 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]]

Code4Lib Journal Deadlines

2016-02-24T21:04:31Z

Ronpeterson: Added issue 33 deadlines

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

===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 22, 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 18, 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]]

Code4Lib Journal Email Templates

2014-02-06T01:14:12Z

Ronpeterson: /* Submission Acknowledgement with Request for CC-BY Affirmation */

''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 will be in touch with you 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>

== Submission Acknowledgement with Request for CC-BY Affirmation ==

<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 will be in touch with you regarding its appropriateness for publication in C4LJ.

Articles in the Code4Lib Journal are published with a Creative Commons 'By' license, and we require that all authors acknowledge that licensing (see http://journal.code4lib.org/article-guidelines#Copyright - "Copyright/Licensing" section). Please send a reply and let us know if that is acceptable.

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 Email Templates

2014-02-06T01:13:02Z

Ronpeterson: /* Submission Acknowledgement */

''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 will be in touch with you 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>

== Submission Acknowledgement with Request for CC-BY Affirmation ==

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

Articles in the Code4Lib Journal are published with a Creative Commons 'By' license, and we require that all authors acknowledge that licensing (see http://journal.code4lib.org/article-guidelines#Copyright - "Copyright/Licensing" section). Please send a reply and let us know if that is acceptable.

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 Deadlines

2012-05-26T16:37:52Z

Ronpeterson: /* Deadlines for Issues */

2012 preconference proposals

2012-02-02T19:12:59Z

Ronpeterson: /* Proposals for 2012 Code4LibCon Preconferences */

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

=== 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 (schwartzr2@wpunj.edu)
*Jim Robinson
*David Bucknum
*Jean Rainwater
*Joshua Gomez
*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
* Timothy Clarke (tclarke@muhlenberg.edu)
* Keith Folsom
* Rebecca Jones
* Michael Doran (doran@uta.edu)
* Ray Henry (ray dot henry at pcc dot edu)
* Stephanie Collett
* Bohyun Kim
* Matt Connolly
* Cynthia Ng
* Justin Littman
* Sibyl Schaefer
* Ron Peterson (ronp@udel.edu)

==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
* Scott Hanrath (shanrath AT ku DOT edu)
* Jason Stirnaman (jstirnaman AT kumc DOT edu)
* Sean Chen
* Laura Smart
* Tommy Ingulfsen

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

UPDATE: Erik won't be making it to Seattle, but will tune in and call in as desired to that time slot. Discuss Solr!!! I'll be lurking and helping out however I can.

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 (remotely calling in and/or via IRC)

==== Interest in Attending ====
* "Gabriel Farrell" <gsf24@drexel.edu>
* "Erik Hetzner" <erik.hetzner AT ucop BORK edu>
* "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)
* Mads Villadsen
* Jonathan Rochkind
* Shahin Sahebi (shahin.ezzatsahebi at utoronto dot ca)
* Naomi Dushay (ndushay at stanford dot edu)
* Jeremy Nelson
* Kirk Hess <kirkhess@illinois.edu>
* Gary Thompson
* Larry Baerveldt <lrbaerveldt@gmail.com>
* Dennis Schafroth <dennis @ indexdata.com>
* Bobbi Fox <bobbi_fox at harvard dot edu>
* Ed Fugikawa <ed at coalliance dot org>
* Eric James <eric dot james at yale dot edu>

=== Knocking Down Silos: Tools and Approaches for Simplifying Discovery ===

What strategies have you used to merge silos to give users a more streamlined search experience? How are libraries using tools like Drupal, Islandora, Dublin Core, Solr and Blacklight to make article, catalog and/or repository content discoverable via a single interface? If you’re interested in these issues, challenges and conundrums join us for a morning of thinking, dreaming and scheming.

Speakers/Facilitators will be:
- Thom Cox - Manager of Library Information Technology Services - Tufts University
- Ken Varnum – Web Systems Manager - University of Michigan Libraries
- Stephen Westman – Analyst Programmer, 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
* Wayne Schneider
* Laney McGlohon
* Andrea Schurr (Andrea-Schurr AT utc DOT edu)
* "Kevin S. Clarke" <ksclarke@gmail>

==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: <del>Ian Walls, ByWater Solutions, @sekjal or ian.walls at bywatersolutions com</del>

Coordinator Stand-In: Michael B. Klein, Stanford University Libraries, @mbklein or mbklein at stanford.edu

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 at rockarch dot 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
* Stephanie Collett
* Gary Thompson
* Brian McBride (brian.mcbride at utah.edu)
* Jacob Reed (jacob.reed at utah.edu)
* Bohyun Kim (bohyun.kim at fiu.edu)
* Larry Baerveldt <lrbaerveldt@gmail.com>
* Wayne Schneider
* Matt Connolly
* ernesto valencia
* Ed Fugikawa <ed at coalliance dot org>
* Andrea Schurr (Andrea-Schurr at utc dot edu)
* David Uspal (david DOT uspal AT villanova DOT 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.

Installation screencast: https://www.youtube.com/watch?v=VLuHuoB8Z6w

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
* Keith Folsom
* Kirk Hess <kirkhess@illinois.edu>
* Jason Stirnaman (jstirnaman AT kumc DOT edu)
* David Drexler <ddrexler@eou.edu>
* Mike Giarlo (michael at psu.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 ====
* 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)
* Adam Wead (awead {at} rockhall d.t 0 R G)
* Tania Fersenheim (tania dot fersenheim at gmail) (I'm only a maybe because I may have a conflict in this time slot)
* Robin Dean (robin at coalliance dot org)

=== "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)
* Michael Poltorak Nielsen
* Wendy Robertson
* Joel Richard (richardjm AT si DOT edu)
* Jonathan Rochkind
* Naomi Dushay (ndushay at stanford dot edu)
* Scott Hanrath (shanrath AT ku DOT edu)
* Aaron Collier (acollier AT csufresno DOT edu)
* David Lacy (david DOT lacy AT villanova DOT edu)
* Jen Weintraub (jweintraub AT library dot ucla dot edu)
* Sean Chen
* Bobbi Fox (bobbi_fox AT harvard dot edu)
* Eric James (eric dot james at yale 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, the Envisioning Lab, and/or the MS Library. 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 (Registration closed! We are now at capacity.) ====
* Declan Fleming
* Matt Critchlow
* Tom Keays (keaysht at lemoyne dot edu)
* 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)
* 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)
* Andrew Darby (agdarby at miami dot edu)
* David Uspal (david DOT uspal AT villanova DOT edu)
* REGISTRATION IS NOW CLOSED

[[Category: Code4Lib2012]]

2012 c4l2012 social activities

2012-02-01T16:22:59Z

Ronpeterson: /* Newcomer dinner Tuesday */

==Ideas==
* Woodinville distillery tour
* Seattle distillery tour
* Favorite local breweries
* Favorite local tea houses
* Favorite local used bookstores
* Visit hackerspace
** +1
* Evergreen/Koha - Open Source ILS brewery/tea house meetup

==Planned events==

===[[2012 Craft Brew Drinkup|Craft Brew Drinkup]]===

'''Date/Time TBA; to be held in the Hospitality Suite.'''

Like good beer? Bring some in your luggage! Some of us are planning to bring some of our favorite local, special, or homebrewed beers to share. Interested? Sign up on the [[2012 Craft Brew Drinkup]] page!

==="Get Lamp" showing===

Some attendees are organizing a showing of [http://www.getlamp.com/ Get Lamp: The Text Adventure Documentary] in the hospitality suite.

To indicate your preference of time and date for the showing, please fill out [http://www.doodle.com/p4c32i3b2ybsrkbh this Doodle poll].

===Pre-Newcomer + Veterans dinner /drink-up Monday===
Early in town for pre-conference?
First time at code4lib?
Don't know anyone at code4lib?
Join fellow c4l newbies + 2nd + 3rd timers + veterans.
You will gain a bunch of new/veteran code4libbers in one night!
Sign up below (NO CAPS). You can show up only for dinner or drinks or both!

But put your name so that we have a rough idea about the number of ppl who will show up =)

'''Plans'''
* When: Monday evening (2/6)
* For Dinner: Meet at 6PM (ish)at the hotel lobby
* For Drinks: show up at Hideout between 8 -10 PM for local art, fancy cocktails, or Belgian beer
* For Hangout: show up at 10 PM - midnight? at hospitality suite

Dinner: [http://www.yelp.com/biz/kastoori-grill-seattle Kastoori Grill -Indian & Himalayan/Nepalese/Tibetan (vegetarian-friendly)]
0.4 miles 9 min. walk
* Bohyun Kim - n/v (2nd-timer) (leader)
* Jason Clark - leader
* Margaret Heller
* Sarah Johnston - n
* Andrea Schurr - n/v (2nd-timer)

Drinks: [http://www.yelp.com/biz/the-hideout-seattle Hideout Lounge] for local art, fancy cocktails, and Belgian beer
* Bohyun Kim - n/v (2nd-timer) (leader)
* Jason Clark - leader
* Lisa Kurt
* Margaret Heller
* Andrea Schurr - n/v (2nd-timer)

Hangout: just show up at the hospitality suite - no sign up required.

===Newcomer dinner Tuesday===
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/7) '''Note that this year's dinner is on Tuesday'''
* 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 coders
***Herd folks from hotel to restaurant (know where you're going!)

'''Happenings'''

Crashing the [http://www.seattlerb.org/ Seattle Ruby] meetup, which meets on Capital Hill at 7:00 on Tuesdays. Eat at [http://www.yelp.com/biz/poppy-seattle Poppy] before. Leaving from the hotel lobby at 6:00.
* Matt Zumwalt (leader) - v
''If you dig Ruby, come to this. Seattle ruby produced Nokogiri, Vlad, Rubygems.org ....''

'''Restaurants'''

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

[http://www.sazeracrestaurant.com/index.php Sazerac] (AWESOME happy hour menu that runs until 8)
* Martin Haye - n
* William Gunn - n
* Rebecca Jones - n
* Chick Markley - v
* Al Cornish - v
* Keri Thompson - n
*'''capped at 6''' ''(So, who's the fearless leader of this group? ~yo_bj)''

[http://oasiankitchen.com/ O'Asian Kitchen and Lounge] (Asian)

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

[http://www.pikebrewing.com/index_html.shtml Pike Brewing] (local brewery, pub food)
* Ken Varnum - n
* Chad Nelson - n
* Ed Summers - v
* Tommy Ingulfsen - n
* Adam Wead - v or .5n
* Dan Coughlin - n
*'''capped at 6''' ''(So, who's the fearless leader of this group? ~yo_bj)''

[http://www.rockbottom.com/ The Rock Bottom Restaurant & Brewery] (American)

[http://www.wildginger.net/ Wild Ginger] (Asian, a bit overpriced)

[http://www.thepurplecafe.com/index.html Purple Cafe] (American, Wine Bar)
* Calvin Mah - (leader) - v
* David Isaak - n
* Aaron Collier - n
* Sean Hannan - v
* Joshua Gomez - v
* Charlie Morris - n
* '''capped at 6'''

[http://www.cafepaloma.com/ Cafe Paloma] (Mediterranean)
* Jean Rainwater (leader) - v
* Kelley McGrath - n
* Lori Robare - n
* Emily Lynema - v
* Sarah Johnston - n

[http://www.thecollinspub.com/ Collins Pub] (Pub Food, great beer selection)
* Francis Kayiwa - (leader) "(get hold of me at first dot last name at goog as the date gets closer with your mobile)" v
* Michael Lindsey - v
* Dan Suchy - v
* David Drexler - n
* Laura Smart - n
* Heather Pitts - n
*'''capped at 6'''

[http://www.mcmenamins.com/311-six-arms-home Six Arms - McMenamins] (Pub Food & they brew their own beer) ''Meeting place TBA. Leave email and I'll coordinate late next week. --Joel''
* Joel Richard (richardjm AT si.edu) (leader) - v
* Margaret Heller - v
* Sibyl Schaefer (sschaefer AT rockarch . org) - v
* Tim Lepczyk (timlepczyk AT gmail.com) - n
* Ray Schwartz (schwartzr2@wpunj.edu) - v
* Andrea Schurr (andrea-schurr AT utc DOT edu) - v(2nd-timer)
* '''capped at 6'''

[http://www.611supreme.com/ 611 Supreme] (Crepes and Full Bar) ''Meet in the conference hotel lobby at 6pm. Look for the short woman in a trench coat and wide brim hat ~Becky''

*Becky Yoose (leader) - v
*Cynthia Ng - n
*Zoe Chao - v
*Justin Coyne - n
*Stephanie Collett - n
*Bethany Nowviskie - n
*'''capped at 6'''

[http://www.panafricamarket.com/wp/ Pan Africa Restaurant & Bar] (Pan African)
CLOSED TUESDAYS!!!!!!!!!!!!!!!!!!
Sorry for the confusion. I have moved everyone to Long Provincial, so that you'll have a place held in case you want it. If Long Provincial doesn't suit you, please remove your name in case someone else wants the spot. Again, I'm sorry. --Jason

[http://longprovincial.com/ Long Provincial] Vietnamese (.7 miles from hotel; 15 minute walk)

Reservation for 6 for 6:30 (and I have a confirmation number!)

Has a jellyfish tank.

*Jason Ronallo (leader?) - v?
*Nettie Lagace - n
*Bohyun Kim - n/v (2nd-timer)
*Wendy Robertson - n
*Jennifer Bowen - n/v (3rd timer)
*James Stuart - n
*'''capped at six'''

'''Restaurants between .5 and 1 mile from hotel'''

[http://tomdouglas.com/index.php?page=palace-kitchen-dinner Palace Kitchen] (another Tom Douglas restaurant, w/ a focus on meat). ''I have made a reservation for 6 at 8pm. Let's meet in the conference lobby at 6:30pm and make our way slowly over; we will find things to do in the interim. Look for Mike Giarlo, a man who may be holding a sign that says "HI I'M MIKE GIARLO" or otherwise shouting his name or looking confused.''

* Mike Giarlo (leader) - v
* Carmen Mitchell - n
* Daniel Lovins - v
* Cary Gordon - v
* Declan Fleming - v
* Amy Unger - n
* (CAPPED AT SIX!)

[http://sitkaandspruce.com/ Sitka and Spruce] (Eclectic, super-local and super-seasonal.) ''We have a reservation for 6 at 8:15pm. We'll meet in the conference lobby at 6:30 pm and head over - the owners also run [http://www.ferdinandthebar.com/home/ Bar Ferd'nand], a wine shop/bar in the same building, and we can kill time there before we eat. Look for Mark Matienzo or Hillel Arnold.''

* Mark Matienzo (leader) - v
* Hillel Arnold - sophomore
* Devon Smith - v
* bernardo gomez - n
* Derek Merleaux - sophmore
* Jennifer Weintraub - n
* (CAPPED AT SIX!)

[http://www.yelp.com/biz/japonessa-seattle Japonessa Restaurant] (Japanese + full bar)
* Kate Zwaard - n

[http://tomdouglas.com/index.php?page=serious-pie Serious Pie] (Tom Douglas restaurant, inventive pizzas, good local beer list).

* Christopher Spalding (leader) - v
* Dan Paskett - n
* Ray Jankoski - n
* Robin Schaaf - n
* Jason Stirnaman - v
* Christina Morris - n
* (CAPPED AT SIX!)

[http://www.allmenus.com/wa/seattle/204592-ballet-restaurant/menu/ Ballet] (Vietnamese)

[http://www.kokebrestaurant.com/ Kokeb Ethiopian Restaurant] (Ethiopian) ''Let's say meet at the lobby at 6pm like everyone else. Woohoo!''

''We have reservations for 6 at 6:45.''

* Andreas Orphanides (leader) - v
* Mark Mounts - v
* Joe Montibello - n
* Andrew Darby - v
* Justin Littman - n
* Ron Peterson
* (CAPPED AT SIX!)

[http://tomdouglas.com/index.php?page=dahlia-lounge Dahlia Lounge] (Pacific Northwest cuisine, $$$)

[http://www.mattsinthemarket.com/ Matt's in the Market] (Northwest Cuisine, $$$)

[http://www.placepigalle-seattle.com/ Place Pigalle] (French)

[http://www.chezshea.com/ Chez Shea] (French)

[http://www.elysianbrewing.com/elysian.html Elysian Breweries and Pubs] (Pub Food)

[http://www.mezaseattle.com/index.html Meza] (Latin Fare)
* Tara Robertson - n
* Shawn Averkamp - sophomore
* Corey Harper - v
* Shaun Ellis - sophomore

[http://inthebowlbistro.com/index.php In the Bowl] (Veg*n, Asian)

[http://www.plumbistro.com/ Plumb Bistro] (Veg*n)

[http://highlineseattle.com/ Highline] (Veg*n, bar)

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

[http://bravehorsetavern.com/ Brave Horse Tavern] (another Tom Douglas, good regional beer list, yummy food. Near South Lake Union. Would require a ride on the South Lake Union Trolley (SLUT), but it's easy to get to/use from downtown.

[http://flyingfishrestaurant.com/ Flying Fish] (Seafood)

[http://www.allmenus.com/wa/seattle/3437-cafe-flora/menu/dinner/ Cafe Flora] (FANTASTIC Veg*n restaurant. Use Metro bus #11 to get there)

[http://www.teapotvegetarianhouse.com/index.htm Teapot Vegetarian House] (Veg*n, Asian)

[http://spaceneedle.com/restaurant/ Space Needle] (American, Pricy; but what the heck, listed it anyway for those who want the experience)

===Veg*n Dinner Wednesday===

We'll pick a place with lots of veg*n options to go eat Wednesday for dinner. Vegetarians and non-vegetarians welcome.

(I probably won't make it but DO YOURSELVES A FAVOR AND '''GO TO CAFÉ FLORA''', SRSLY. -mjgiarlo)

options:
*[http://www.cafeflora.com/index.php Cafe Flora] A bit pricey and a #12 bus away. Could see about a large reservation with a prix fixe menu?
*[http://lovinghut.us/seattle/index.html Loving Hut] Modest price. 1 mile from hotel.

Other options?

*Jason Ronallo (jronallo AT gmail.com)
*Sean Hannan
*Ed Summers
*Becky Yoose (carnivore ambassador)
*James Stuart
*Bohyun Kim
*Bethany Nowviskie
*Margaret Heller
*Laura Smart
*Sibyl Schaefer
*WOAH! Didn't expect such a big response! Let's cap this one until we decide on a place that can accomodate us.
*Cynthia Ng - if you can accommodate another veggie

===Meat-Up Dinner Wednesday===

I am thinking burgers. More info soon... (if you do not find a suitable burger joint, there are also some top-notch steakhouses in Seattle. Both the Metropolitan Grill and El Gaucho are delightful if folks are OK with $50 steaks. Just FYI, not trying to hijack your meat-up, Cary!. -mjgiarlo)

* Cary Gordon

===Dim Sum Lunch Thursday===

For those of you staying in town after the last session on Thursday, [http://oasiankitchen.com/ O'Asian Kitchen] has dim sum service during the weekdays. Meet up around 12:35, meeting location tba. Bring cash for easier bill splitting.

*Becky Yoose
* Declan Fleming - love me some Dim Sum!
* Adam Wead
* Heather Pitts
* Sibyl Schaefer
* Anoop Atre
* Dan Suchy
* Carmen Mitchell
* Tara Robertson
* Ray Schwartz
* Cynthia Ng
* Corey Harper
* Joshua Gomez
* Cary Gordon
* Mike Giarlo

==Social Map - places of interest==
[http://g.co/maps/4m5pk Code4lib 2012 - Seattle - social events, hangouts, and places to see]

==Seattle Events Feb 5-9==
===Saturday, February 4, 2012===
In case you are showing up really early.
* Belgianfest: http://www.washingtonbeer.com/belgianfest/
===Sunday, February 5, 2012===
* Clinton Fearon & The Boogie Brown Band/Live Wyya/Adrian Xavier/Selecta Raiford/DJ Courtland, Neumos: http://neumos.com/neumos.php
* Michael The Blind/The Els, Skylark: http://www.skylarkcafe.com/
* Addaura/Alda/Hallow, Comet
* "I Am My Own Wife" 7:30pm at Seattle Repertory Theatre (Seattle Center) http://www.seattlerep.org/Plays/1112/IM/

===Monday, February 6, 2012===
* Silent Movie Mondays: Last Command 1928, http://stgpresents.org/artists/?artist=1829#, Show at 7:00pm, The Paramount Theatre $10
This all-classic film series, First Oscars, is accompanied by live music from the historic Mighty Wurlitzer organ, one of the last three remaining organs of its kind to reside in its original environment, played by critically acclaimed organist Jim Riggs.

===Tuesday, February 7, 2012===
* Lionize/Maylene & The Sons Of Disaster, El Corazon: http://elcorazonseattle.com/
* The Pulltab Playboys/Rachel Lyn Harrington & The Knock Outs/The James Low Western Front, Sunset: http://sunsettavern.com/
* Twin Sister, Vera: http://theveraproject.org/shows/
* The Features, Chop Suey: http://www.chopsuey.com/
* Wilco/White Denim, Paramount Theatre: http://stgpresents.org/
* "I Am My Own Wife" 7:30pm at Seattle Repertory Theatre (Seattle Center) http://www.seattlerep.org/Plays/1112/IM/
* Intro to Arduino Workshop, 7pm at Metrix Create Space http://metrixcreatespace.com/

===Wednesday, February 8, 2012===
* The Golden Blondes/The Jet Age/Mr. Drinx & The Pot Heads, Sunset: http://sunsettavern.com/
* Pipsisewah/The Chasers/The Magic Mirrors, Tractor: http://www.tractortavern.com/
* Dengue Fever vs Secret Chiefs 3, Moe Bar :http://bit.ly/yJtfXv (how could you pass the opportunity to see someone play this thing :http://bit.ly/wB5AgZ

===Thursday, February 9, 2012===
* SAM Opening - Gauguin and Polynesia: An Elusive Paradise: http://www.seattleartmuseum.org/gauguin
* The Jayhawks, Neptune Theater: http://stgpresents.org/
* Digital Leather, Comet
* Savani World Quintet/Super Sones, Columbia City Theater: http://www.columbiacitytheater.com/
* Blvd Park {album release}/Nettle Honey/Creeping Time, Tractor: http://www.tractortavern.com/
* Eleanor Friedberger, Crocodile: http://thecrocodile.com/index.html

===Ongoing Events===
* Seattle Art Museum: Tours are every Saturday & Sunday at noon, and the First Thursday of every month at 10:30, 11:30 am, 12:30 & 1:30 pm.
* EMP: Exhibits on display include: Battlestar Galactica, Nirvana, Avatar, and Can’t Look Away: The Lure of Horror Film
* Teatro ZinZanni: ¡Caliente! http://dreams.zinzanni.org/
* Pacific NW Ballet: performing Don Quixote at McCaw Hall http://www.pnb.org/
* Oklahoma!, Sunday matinee and nightly: 5th Avenue Theatre, 1308 Fifth Avenue http://www.5thavenue.org/show/oklahoma

==Local events/places==
* Metrix Create Space
* Ada's Technical Books
* Northwest Outdoor Center
* Center for Wooden Boats
* Empty Sea Studios acoustic music

==Local Beer Places==
* Map of [http://beermapping.com/maps/citymaps.php?m=seattle#lat=47.66723703450515&lng=-122.28263854980469&z=5 beer venues] maintained at Beermapping.com.
* List of [http://www.washingtonbeer.com/breweries/seattle-king-co/ local breweries] ([http://maps.google.com/maps/ms?hl=en&ie=UTF8&msa=0&msid=201783184139227541123.0004813e64758434cb054&source=embed&ll=47.558921,-122.106171&spn=0.442982,1.234589&z=10&source=embed map]) maintained by the Washington Beer Commission
* Map of [http://www.ratebeer.com/Places/RegionMap.asp?rid=7600 beer venues] maintained by Ratebeer.com.

==See also==
[http://orbiscascade.org/index/c4l-things-to-do-in-seattle Things to do in Seattle, from the hosts]

2012 preconference proposals

2012-01-18T20:01:46Z

Ronpeterson: /* 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
* Timothy Clarke (tclarke@muhlenberg.edu)
* Keith Folsom

==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
* Ron Peterson (ronp@udel.edu0

=== 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
* Ron Peterson (ronp@udel.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 ( 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
* Keith Folsom

=== 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)
* Adam Wead (awead {at} rockhall d.t 0 R G)
* Tania Fersenheim (tania dot fersenheim at gmail) (I'm only a maybe because I may have a conflict in this time slot)

=== "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 (Registration closed! We are now at capacity.) ====
* 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)
* Andrew Darby (agdarby at miami dot edu)
* REGISTRATION IS NOW CLOSED

[[Category: Code4Lib2012]]

2012 preconference proposals

2012-01-18T20:01:02Z

Ronpeterson: /* 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
* Timothy Clarke (tclarke@muhlenberg.edu)
* Keith Folsom

==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
* Ron Peterson (ronp@udel.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 ( 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
* Keith Folsom

=== 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)
* Adam Wead (awead {at} rockhall d.t 0 R G)
* Tania Fersenheim (tania dot fersenheim at gmail) (I'm only a maybe because I may have a conflict in this time slot)

=== "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 (Registration closed! We are now at capacity.) ====
* 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)
* Andrew Darby (agdarby at miami dot edu)
* REGISTRATION IS NOW CLOSED

[[Category: Code4Lib2012]]

Code4Lib Journal WordPress Input Guidelines

2010-12-09T01:46:06Z

Ronpeterson: /* Uploading files manually */

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><em></code> for emphasized text, <code><strong></code> for strongly emphasized text, <code><blockquote></code> when quoting blocks of text. Avoid such monstrosities as <code><font></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><p class="caption">Figure 1. How to Caption an Image.</p>
</nowiki>
In general, we bold the figure / table label using the strong tag:
<nowiki><p class="caption"><strong>Figure 1.</strong> How to Caption an Image.</p>
</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>

==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-09T01:45:32Z

Ronpeterson: /* Uploading media via WordPress */

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><em></code> for emphasized text, <code><strong></code> for strongly emphasized text, <code><blockquote></code> when quoting blocks of text. Avoid such monstrosities as <code><font></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><p class="caption">Figure 1. How to Caption an Image.</p>
</nowiki>
In general, we bold the figure / table label using the strong tag:
<nowiki><p class="caption"><strong>Figure 1.</strong> How to Caption an Image.</p>
</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>

==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-09T01:44:49Z

Ronpeterson: /* Uploading files manually */

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><em></code> for emphasized text, <code><strong></code> for strongly emphasized text, <code><blockquote></code> when quoting blocks of text. Avoid such monstrosities as <code><font></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><p class="caption">Figure 1. How to Caption an Image.</p>
</nowiki>
In general, we bold the figure / table label using the strong tag:
<nowiki><p class="caption"><strong>Figure 1.</strong> How to Caption an Image.</p>
</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>

==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-09T01:44:04Z

Ronpeterson: /* 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><em></code> for emphasized text, <code><strong></code> for strongly emphasized text, <code><blockquote></code> when quoting blocks of text. Avoid such monstrosities as <code><font></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><p class="caption">Figure 1. How to Caption an Image.</p>
</nowiki>
In general, we bold the figure / table label using the strong tag:
<nowiki><p class="caption"><strong>Figure 1.</strong> How to Caption an Image.</p>
</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>

==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-08T22:21:53Z

Ronpeterson: /* 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><em></code> for emphasized text, <code><strong></code> for strongly emphasized text, <code><blockquote></code> when quoting blocks of text. Avoid such monstrosities as <code><font></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><p class="caption">Figure 1. How to Caption an Image.</p>
</nowiki>
In general, we bold the figure / table label using the strong tag:
<nowiki><p class="caption"><strong>Figure 1.</strong> How to Caption an Image.</p>
</nowiki>

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.

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

==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 Publicity Venues

2010-08-16T15:03:18Z

Ronpeterson: /* 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
* [http://mail.archive.org/pipermail/ol-lib/ Open Library] ol-lib@archive.org
* [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
* [http://lists.webjunction.org/xml4lib/ XML4Lib] xml4lib@webjunction.org

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)
#ol-lib (Tom)
#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]]