Code4Lib - User contributions [en]

Code4Lib Journal Deadlines

2009-06-05T12:57:04Z

141.211.43.152: /* 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 ==

=== Eighth issue ===

* Monday, May 8 -- call for proposals
* Friday, June 5 -- proposals due
* Monday, June 22 -- publication of issue 6
* Friday, June 19 -- finish voting on proposals; notify authors
* Friday, July 17 -- first draft due
* Friday, August 14 -- second draft due
* Monday, September 21 -- 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 Style Guide

2009-03-10T12:36:58Z

141.211.43.152: /* Figures & Tables */

== Start of Article ==

Article titles are in Title Case -- all major words capitalized. The title is followed by an abstract and byline of the form "by Author" or "by Author 1, Author 2, and Author 3".

== Headings ==

Use H2 for main section headings, H3 for sub-sections, H4 if you need a lower level. H2 are in "Title Case" -- all words capitalized, short words (the, a, in, up, over, about) should not be. H3 and H4 are in "Sentence case" -- only the first word is capitalized.

== Figures & Tables ==

Figures and tables are centered, placed inside a P or DIV with class of "caption". For example:

<pre>
<p class = "caption">
<img src = "....">
<strong>Caption for Figure</strong>
<p>

<div class = "caption">
<table>
<tr>...</tr>
</table>
</div>
</pre>

Captions for figures appear beneath the figure, centered, with "Figure X:" in bold, the descriptive text in sentence case, plain text.

Captions for tables and code appear above the table, centered, with "Table X:" in bold, the descriptive text in sentence case, plain text.

== Code ==

Code samples entered as preformatted text, as in the following example, are automagically color highlighted in Wordpress by the [http://wordpress.org/extend/plugins/syntaxhighlighter/ SyntaxHighlighter] plugin:

<pre>
<pre>
[sourcecode language='php']
RAW HTML/PHP/XML/Etc. code goes here; change language (in above line) as needed
[/sourcecode]
</pre>
</pre>

Supported formats include <tt>cpp, c, c++, c#, c-sharp, csharp, css, delphi, java, js, jscript, javascript, pascal, php, py, python, rb, ruby, rails, ror, sql, vb, vb.net, xml, html, xhtml, and xslt</tt>. Pretty much everything except <tt>perl</tt>.

== End of Document ==

=== Footnotes & Footnote References ===

A Notes section (if needed) immediately follows the last of the article's narrative text. Notes are indicated in the text either by note number in square brackets [1] or by author and year [Smith, 2007]. Where notes refer to articles, books, etc., that are not available by direct link, insert a [[COinS (layman's description) | COINS]] element after the note.

=== About the Author ===

A sentence or two of brief biography, provided by the author(s), appears listed after the Notes.

=== Appendices ===

If there are appendices, they appear after the author biography.

[[Category: Code4Lib Journal]]

Code4Lib Style Guide

2009-03-10T12:36:38Z

141.211.43.152: /* Figures & Tables */

== Start of Article ==

Article titles are in Title Case -- all major words capitalized. The title is followed by an abstract and byline of the form "by Author" or "by Author 1, Author 2, and Author 3".

== Headings ==

Use H2 for main section headings, H3 for sub-sections, H4 if you need a lower level. H2 are in "Title Case" -- all words capitalized, short words (the, a, in, up, over, about) should not be. H3 and H4 are in "Sentence case" -- only the first word is capitalized.

== Figures & Tables ==

Figures and tables are centered, placed inside a P or DIV with class of "caption". For example:

<pre>
<p class = "caption">
<img src = "....">
<strong>Caption for Figure</strong>
<p>

<div class = "caption">
<table>
<tr>...</tr>
</table>
<div>
</pre>

Captions for figures appear beneath the figure, centered, with "Figure X:" in bold, the descriptive text in sentence case, plain text.

Captions for tables and code appear above the table, centered, with "Table X:" in bold, the descriptive text in sentence case, plain text.

== Code ==

Code samples entered as preformatted text, as in the following example, are automagically color highlighted in Wordpress by the [http://wordpress.org/extend/plugins/syntaxhighlighter/ SyntaxHighlighter] plugin:

<pre>
<pre>
[sourcecode language='php']
RAW HTML/PHP/XML/Etc. code goes here; change language (in above line) as needed
[/sourcecode]
</pre>
</pre>

Supported formats include <tt>cpp, c, c++, c#, c-sharp, csharp, css, delphi, java, js, jscript, javascript, pascal, php, py, python, rb, ruby, rails, ror, sql, vb, vb.net, xml, html, xhtml, and xslt</tt>. Pretty much everything except <tt>perl</tt>.

== End of Document ==

=== Footnotes & Footnote References ===

A Notes section (if needed) immediately follows the last of the article's narrative text. Notes are indicated in the text either by note number in square brackets [1] or by author and year [Smith, 2007]. Where notes refer to articles, books, etc., that are not available by direct link, insert a [[COinS (layman's description) | COINS]] element after the note.

=== About the Author ===

A sentence or two of brief biography, provided by the author(s), appears listed after the Notes.

=== Appendices ===

If there are appendices, they appear after the author biography.

[[Category: Code4Lib Journal]]

Code4Lib Style Guide

2009-03-05T18:01:56Z

141.211.43.152: /* Figures & Tables */

== Start of Article ==

Article titles are in Title Case -- all major words capitalized. The title is followed by an abstract and byline of the form "by Author" or "by Author 1, Author 2, and Author 3".

== Headings ==

Use H2 for main section headings, H3 for sub-sections, H4 if you need a lower level. H2 are in "Title Case" -- all words capitalized, short words (the, a, in, up, over, about) should not be. H3 and H4 are in "Sentence case" -- only the first word is capitalized.

== Figures & Tables ==

Figures and tables are centered.

Captions for figures appear beneath the figure, centered, with "Figure X:" in bold, the descriptive text in sentence case, plain text.

Captions for tables and code appear above the table, centered, with "Table X:" in bold, the descriptive text in sentence case, plain text.

== Code ==

Code samples entered as preformatted text, as in the following example, are automagically color highlighted in Wordpress by the [http://wordpress.org/extend/plugins/syntaxhighlighter/ SyntaxHighlighter] plugin:

<pre>
<pre>
[sourcecode language='php']
RAW HTML/PHP/XML/Etc. code goes here; change language (in above line) as needed
[/sourcecode]
</pre>
</pre>

Supported formats include <tt>cpp, c, c++, c#, c-sharp, csharp, css, delphi, java, js, jscript, javascript, pascal, php, py, python, rb, ruby, rails, ror, sql, vb, vb.net, xml, html, xhtml, and xslt</tt>. Pretty much everything except <tt>perl</tt>.

== End of Document ==

=== Footnotes & Footnote References ===

A Notes section (if needed) immediately follows the last of the article's narrative text. Notes are indicated in the text either by note number in square brackets [1] or by author and year [Smith, 2007]. Where notes refer to articles, books, etc., that are not available by direct link, insert a [[COinS (layman's description) | COINS]] element after the note.

=== About the Author ===

A sentence or two of brief biography, provided by the author(s), appears listed after the Notes.

=== Appendices ===

If there are appendices, they appear after the author biography.

[[Category: Code4Lib Journal]]

Code4Lib Style Guide

2008-12-10T15:01:26Z

141.211.43.152: Added code instructions

== Start of Article ==

Article titles are in Title Case -- all major words capitalized. The title is followed by an abstract and byline of the form "by Author" or "by Author 1, Author 2, and Author 3".

== Headings ==

Use H2 for main section headings, H3 for sub-sections, H4 if you need a lower level. H2 are in "Title Case" -- all words capitalized, short words (the, a, in, up, over, about) should not be. H3 and H4 are in "Sentence case" -- only the first word is capitalized.

== Figures & Tables ==

Figures and tables are centered.

Captions for figures appear beneath the figure, centered, with "Figure X:" in bold, the descriptive text in sentence case, plain text.

Captions for tables appear above the table, centered, with "Table X:" in bold, the descriptive text in sentence case, plain text.

== Code ==

Code samples are entered as preformatted text, as in the following example:

<pre>
<pre>
[sourcecode language='php']
RAW HTML/Perl/PHP/XML/Etc. code goes here; change language (in above line) as needed
[/sourcecode]
</pre>
</pre>

== End of Document ==

=== Footnotes & Footnote References ===

A Notes section (if needed) immediately follows the last of the article's narrative text. Notes are indicated in the text either by note number in square brackets [1] or by author and year [Smith, 2007]. Where notes refer to articles, books, etc., that are not available by direct link, insert a [[COinS (layman's description) | COINS]] element after the note.

=== Author Biography ===

Text provided by each author is listed after the Notes.

=== Appendices ===

If there are appendices, they appear after the author biography.

[[Category: Code4Lib Journal]]

Code4Lib Style Guide

2008-12-10T14:01:02Z

141.211.43.152: Started a style guide

Code4Lib Journal Publicity Venues

2008-09-23T13:33:53Z

141.211.43.152: /* Distributing Call for Submissions */

== Distributing Call for Submissions ==

Sent to following lists to announce Call for Submissions for Issue 4:

*Web4Lib: web4lib@webjunction.org
*Code4Lib: code4lib@listserv.nd.edu
*NGC4Lib: ngc4lib@listserv.nd.edu
*Drupal4Lib: drupal4lib@listserv.uic.edu

Added for Issue 5:
* LITA-L: lita-l@ala.org
* Metadatalibrarians
* OSS4LIB
* Usability4Lib
* XML4LIB

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 4 was publicized:

#code4lib (Ken)
#drupal4lib (Ken)
#LISWire (Ken)
#lita-l (Jodi)
#ngc4lib (Ken)
#ol-lib (Tom)
#oss4lib (Tom)
#public-lod (Tom)
#usability4lib (Tom)
#web4lib (Ken)
#xml4lib (Tom)

[[Category: Code4Lib Journal]]

Code4Lib Journal Publicity Venues

2008-09-22T20:54:06Z

141.211.43.152: /* Announcing Publication */

== Distributing Call for Submissions ==

Sent to following lists to announce Call for Submissions for Issue 4:

*Web4Lib: web4lib@webjunction.org
*Code4Lib: code4lib@listserv.nd.edu
*NGC4Lib: ngc4lib@listserv.nd.edu
*Drupal4Lib: drupal4lib@listserv.uic.edu

Added for Issue 5:
* LITA-L: lita-l@ala.org
* Metadatalibrarians
* OSS4LIB
* Usability4Lib
* XML4LIB

Web Sites

* [http://liswire.com/ LISWire] See [http://groups.google.com/group/c4lj-articles/t/e0b406daa4599c47 c4lj-articles] group for login information.

== Announcing Publication ==

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

#web4lib (Ken)
#ngc4lib (Ken)
#code4lib (Ken)
#drupal4lib (Ken)
#LISWire (Ken)

[[Category: Code4Lib Journal]]

Code4Lib Journal Publicity Venues

2008-09-22T17:49:57Z

141.211.43.152: /* Distributing Call for Submissions */

Code4Lib Journal Publicity Venues

2008-09-22T17:32:30Z

141.211.43.152: /* Distributing Call for Submissions */

Code4Lib Journal Publicity Venues

2008-09-22T17:32:07Z

141.211.43.152: /* Distributing Call for Submissions */