Code4Lib - User contributions [en]

Code4Lib Journal Deadlines

2010-06-29T15:59:05Z

128.230.13.149: /* Twelfth issue */

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

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

Citation Format Recommendations

2010-06-07T14:59:09Z

128.230.13.149: /* Voting on Recommended Style: */

[[Category: Code4Lib Journal]]

==== Recommended Reference Style Information: ====

Tim McGeary proposes that the Editorial Committee chose a recommended style for all authors. Authors that do not choose recommended style need to follow another documented style and communicate that to their assigned editor. Using a documented style will provide a clear editorial guidelines for consistency, and ensure proper citations and references of literature and resources.

[http://owl.english.purdue.edu/owl/resource/560/10/ APA Style Example (Purdue)]

[http://www.library.cornell.edu/resrch/citmanage/mla MLA Style Example (Cornell)]

[http://library.osu.edu/help/research-strategies/how-do-i-cite-references/cse-citation-guide CSE Style Example (Ohio State)]

jrochkind's proposal: Citations should be clear and unambiguous, and reasonably consistent within an article. Authors are welcome but not required to use a formal style. Editors will ensure readability, clarity, and reasonable consistency of citations, but will not check citations for compliance with stylebooks.

==== Voting on Recommended Style: ====
{| border="1" cellpadding="5" class="sortable"
|- style="text-align: left;"

!Name !! Recommend Style? (Y/N) !! Which Style? (Vote even if N)
|-
| Tim McGeary || Y || CSE
|-
| J Rochkind || N ||
|-
| Carol Bean || Y || CSE
|-
| Staurt Yeates || N || RFC
|-
| MJ Suhonos || N ||
|-
| Ron Peterson || N ||
|-
| Andrew Darby || Y || APA
|-
| Edward Corrado || Y || CSE
|-
| Kelley McGrath || Y || CSE
|-
| Tim Lepczyk || Y || APA
|-
| Tod Olson || Y || CSE
|-
| Tom Keays || Y || CSE
|}

Code4Lib Journal WordPress Customizations

2010-05-19T14:50:10Z

128.230.13.149:

==Plugins==
===Anti-Spam===
;[http://akismet.com/ Akimset]
:Filters out spam-link comments based on their content
;[http://recaptcha.net/plugins/wordpress reCAPTCHA]
:Requires users to copy a distorted word before they can comment

===Metadata===
;[http://www.wallandbinkley.com/quaedam/ COinS Quicktags Button]
:In the non-WYSIWYG editor, can be used to build a basic COinS tag. This has been abandoned in favor of the generator at http://generator.ocoins.info/.
;[http://www.lackoftalent.org/michael/blog/unapi-wordpress-plug-in/ unAPI Server]
:Provides information about articles. Useful for Zotero users.

===Presentation===
;[http://wordpress.org/extend/plugins/syntaxhighlighter/ SyntaxHighlighter]
:Makes code pretty.
;C4LJ Custom the_author()
:Replaces the text returned by the_author() with the value of the "author" custom field. Necessary since articles are entered by their editors, but we want author information to appear on the articles and in the syndication feeds.

===URLs===
;C4LJ Remove Parents
:A customization of http://wordpress.org/extend/plugins/remove-parents/. Prettifies category URLs so that issues appear at <code>http://journal.code4lib.org/issues/issue1</code> instead of <code>http://journal.code4lib.org/issues/issues/issue1</code>.
;[http://www.feedburner.com/fb/a/help/wordpress_quickstart FeedBurner FeedSmith]
:Redirects the main feed and the general comments feed to FeedBurner

===Workflow===
;Issue Manager
:Enables one-click publishing of new issues, and prevents articles from being published until their associated issue is published.
;[http://www.im-web-gefunden.de/wordpress-plugins/role-manager/ Role Manager]
:Allows creation of custom roles and editing of roles' permissions. Used to create the Reviewer role, which can read Private articles, so that authors can see their articles before publication, and to prevent editors from publishing articles on accident.

==Upgrading==

These fixes were necessary for WP < 2.5, but should not be needed any longer.

===Save the <div>s===
Edit wp-includes/js/tinymce/tiny_mce_config.php, around line 25.
$valid_elements = '-strong/-b[*],-em/-i[*],-font[*],-ul[*],-ol[*],-li[*],*[*]';

==="Submit for Review"===
Edit wp-admin/includes/post.php. After line 71 (in version 2.3.3) add:
// START FIX
if ('publish' == $_POST['post_status'] && !current_user_can( 'publish_posts' )) {
$post =& get_post( $post_ID );
if ('publish' != $post->post_status)
$_POST['post_status'] = 'pending';
}
// END FIX

==Issue Manager Plugin==
===To Publish an Issue===
#Assign timestamps to the articles in the order you want them to appear on the page (newest timestamps go at the top of the page)
#Go to the Issue Manager page in the "Manage" tab.
#Click "Publish" next to the category for the issue you want to publish.
#All "Pending Review" articles with the given category (that don't also have an "unpublished" category) will be published, with the timestamps updated to about now, retaining the order established earlier.
===To Prevent Early Publication of Articles===
#Go to the Issue Manager page in the "Manage" tab.
#Click "Unpublish" next to the category for the issue you want to keep unpublished.
#Any published articles with that category will revert to "Pending Review" status. Any new articles you attempt to publish will instead be set to "Pending Review".

==Google Code Repository==
The theme and plugins used by the Journal are available via [http://code.google.com/p/c4lj/ Google Code]. Some of the plugins are described on [http://xplus3.net/tag/plugins/ Jonathan Brinley's blog].

[[Category:Code4Lib Journal]]