Code4Lib - User contributions [en]

2016 Conference Volunteers

2016-02-19T17:19:05Z

Christineschwartz: Added name to Welcome Wagon/Concierge section

Code4Lib 2016 Volunteers sign-up page. As conference plans evolve, the page will be periodically updated with new opportunities to volunteer. When you sign up please either include some way to contact you or send your contact information to Kathleen Haley (Chair for Volunteers) at KHaley AT mwa DOT org.

For general questions, or if you identify a volunteer need not covered in the list below, feel free to contact Kathleen or David Uspal (LPC Committee Contact for Volunteers) at david DOT uspal AT villanova DOT edu.

== Welcome Wagon/Concierge ==

Helps with greeting newcomers, directing people to evening activities and local points of interest, etc. and being generally awesome to the community.
* Megan Kudzia
* Becky Yoose
* Bohyun Kim
* Christine Schwartz

== Conference Logistics ==

Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.

Sunday:
* Katherine Lynch
* Lauren Gala
* Chad Nelson

Monday:
* Lauren Gala
* Ian Walls
* Drew Gordon

== Preconference Setup ==

Help manage preconference sessions, setting up projectors, etc.

Sheraton Society Hill (Conference Hotel):
* Lauren Gala

Chemical Heritage Foundation:
* Anna Headley (CHF contact)
* Michelle DiMeo (CHF contact)

Franklin Hall:
* Scott Ziegler (venue contact at APS)

== Social Networking ==

Answering general questions on Twitter and IRC:
* Christina Harlow
* Mx A. Matienzo

Ask questions on mic on behalf of community (because of distance, mic aversion, etc)

Tuesday:
* [[User:Todrobbins|Tod Robbins]]

Wednesday:
* Christina Harlow

Thursday:
* Elise Warshavsky

== Livestream ==
Volunteers for the livestream will assist the livestream technician with conferencee streaming. Their main duty will be to serve as a backup minder of the equipment in case the technician needs to step aside for a break.

Technician/on-call:
* [[User:AshleyBlewer|Ashley Blewer!]] (@ablwr)

Tuesday AM:
* [[User:Phette23|Eric Phetteplace]] (@phette23)

Tuesday PM:
* Francis Kayiwa

Wednesday AM:
* [[User:Todrobbins|Tod Robbins]]

Wednesday PM:
* Drew Gordon

Thursday AM:
* Jason Stirnaman (@jastirn)

== IRC (Technical) ==

Access:
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people.
* Mx Matienzo (anarchivist)

Helper:
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.
*

==Registration Desk ==
Assists with handing out registration materials to attendees.

Monday AM (8:00-9:30):
* Shaun Ellis
* Katherine Lynch

Monday PM (12:00-1:30):
* Megan Kudzia
* Katherine Lynch

Tuesday AM (7:00-9:30):
* Lauren Gala
* Cody Hanson

==MCs==

Tuesday AM:
* David Lacy

Tuesday PM:
* Shaun Ellis

Wednesday AM:
* Anna Headley

Wednesday PM:
* Dre

Thursday AM:
* Becky, Destroyer of Last Names

== Session Timers ==

People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop or tablet with a stopwatch program). It's good to have two people in each slot to back each other up in case of machinery failure.

Tuesday AM:
* Francis Kayiwa
* Christina Harlow

Tuesday PM:
* Lauren Gala
* Katherine Lynch

Wednesday AM:
* Lauren Gala
* Chris Clement

Wednesday PM:
* Lauren Gala
* Chris Clement

Thursday AM:
* Lauren Gala
* Chris Clement

== The Whatever Crew ==
Volunteers who are willing to help with various tasks as needed during the conference.
* Dre
* Katherine Lynch
* [[User:Todrobbins|Tod Robbins]]
* Whitni Watkins
* Cody Hanson
* Bohyun Kim
* Alison Hitchens
* [[User:Phette23|Eric Phetteplace]]
* Christine Schwartz

[[Category: Code4Lib2016]]

2016 Conference Volunteers

2016-02-19T15:54:56Z

Christineschwartz: Added name to The Whatever Crew section

Code4Lib 2016 Volunteers sign-up page. As conference plans evolve, the page will be periodically updated with new opportunities to volunteer. When you sign up please either include some way to contact you or send your contact information to Kathleen Haley (Chair for Volunteers) at KHaley AT mwa DOT org.

For general questions, or if you identify a volunteer need not covered in the list below, feel free to contact Kathleen or David Uspal (LPC Committee Contact for Volunteers) at david DOT uspal AT villanova DOT edu.

== Welcome Wagon/Concierge ==

Helps with greeting newcomers, directing people to evening activities and local points of interest, etc. and being generally awesome to the community.
* Megan Kudzia
* Becky Yoose
* Bohyun Kim

== Conference Logistics ==

Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.

Sunday:
* Katherine Lynch
* Lauren Gala
* Chad Nelson

Monday:
* Lauren Gala
* Ian Walls
* Drew Gordon

== Preconference Setup ==

Help manage preconference sessions, setting up projectors, etc.

Sheraton Society Hill (Conference Hotel):
* Lauren Gala

Chemical Heritage Foundation:
* Anna Headley (CHF contact)
* Michelle DiMeo (CHF contact)

Franklin Hall:
* Scott Ziegler (venue contact at APS)

== Social Networking ==

Answering general questions on Twitter and IRC:
* Christina Harlow
* Mx A. Matienzo

Ask questions on mic on behalf of community (because of distance, mic aversion, etc)

Tuesday:
* [[User:Todrobbins|Tod Robbins]]

Wednesday:
* Christina Harlow

Thursday:
* Elise Warshavsky

== Livestream ==
Volunteers for the livestream will assist the livestream technician with conferencee streaming. Their main duty will be to serve as a backup minder of the equipment in case the technician needs to step aside for a break.

Technician/on-call:
* [[User:AshleyBlewer|Ashley Blewer!]] (@ablwr)

Tuesday AM:
* [[User:Phette23|Eric Phetteplace]] (@phette23)

Tuesday PM:
* Francis Kayiwa

Wednesday AM:
* [[User:Todrobbins|Tod Robbins]]

Wednesday PM:
* Drew Gordon

Thursday AM:
* Jason Stirnaman (@jastirn)

== IRC (Technical) ==

Access:
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people.
* Mx Matienzo (anarchivist)

Helper:
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.
*

==Registration Desk ==
Assists with handing out registration materials to attendees.

Monday AM (8:00-9:30):
* Shaun Ellis
* Katherine Lynch

Monday PM (12:00-1:30):
* Megan Kudzia
* Katherine Lynch

Tuesday AM (7:00-9:30):
* Lauren Gala
* Cody Hanson

==MCs==

Tuesday AM:
* David Lacy

Tuesday PM:
* Shaun Ellis

Wednesday AM:
* Anna Headley

Wednesday PM:
* Dre

Thursday AM:
* Becky, Destroyer of Last Names

== Session Timers ==

People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop or tablet with a stopwatch program). It's good to have two people in each slot to back each other up in case of machinery failure.

Tuesday AM:
* Francis Kayiwa
* Christina Harlow

Tuesday PM:
* Lauren Gala
* Katherine Lynch

Wednesday AM:
* Lauren Gala
* Chris Clement

Wednesday PM:
* Lauren Gala
* Chris Clement

Thursday AM:
* Lauren Gala
* Chris Clement

== The Whatever Crew ==
Volunteers who are willing to help with various tasks as needed during the conference.
* Dre
* Katherine Lynch
* [[User:Todrobbins|Tod Robbins]]
* Whitni Watkins
* Cody Hanson
* Bohyun Kim
* Alison Hitchens
* [[User:Phette23|Eric Phetteplace]]
* Christine Schwartz

[[Category: Code4Lib2016]]

Code4Lib Journal WordPress Input Guidelines

2009-06-21T14:06:28Z

Christineschwartz: /* Endnotes style and HTML coding */

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

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

Two options for images and other attached content/media:
# use WordPress uploaded content managing feature, or
# upload the content to our host manually.

jrochkind found the WordPress content managing feature to be more of a pain than it was worth, so is uploading content 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/browse_thread/thread/7d66327ef69c507a/6dceb7d578676334?lnk=gst&q=account+upload#6dceb7d578676334 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/
* 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==
Every article in issue 1 should be put in a category "Issue 1". Etc. This should make it easier to generate issue specific RSS feeds and do other stuff at a later date.

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

# Make sure that all articles for the issue have the correct issue category selected and have been set to 'Pending Review'.
# Click on Posts -> Issues after logging into WordPress
# Click on "Publish" for the issue you'd like to publish.
## You'll get a list of every "Pending Review" article in that issue. Don't see all the articles you think you should see? Either they are still in Draft status or they're not in the Issue 5 category.
# 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).
# 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.

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.

[[Category:Code4Lib Journal]]

Code4Lib Journal Deadlines

2009-06-20T12:39:09Z

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

=== Eighth issue ===

* Monday, May 8 -- call for proposals
* Friday, June 5 -- proposals due
* Monday, June 22 -- publication of issue 7
* 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 Journal WordPress Input Guidelines

2009-06-20T12:18:23Z

Christineschwartz: /* Endnotes style and HTML coding */

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

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

Two options for images and other attached content/media:
# use WordPress uploaded content managing feature, or
# upload the content to our host manually.

jrochkind found the WordPress content managing feature to be more of a pain than it was worth, so is uploading content 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/browse_thread/thread/7d66327ef69c507a/6dceb7d578676334?lnk=gst&q=account+upload#6dceb7d578676334 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/
* 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 name="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 href="#ref1" name="note1">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==
Every article in issue 1 should be put in a category "Issue 1". Etc. This should make it easier to generate issue specific RSS feeds and do other stuff at a later date.

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

# Make sure that all articles for the issue have the correct issue category selected and have been set to 'Pending Review'.
# Click on Posts -> Issues after logging into WordPress
# Click on "Publish" for the issue you'd like to publish.
## You'll get a list of every "Pending Review" article in that issue. Don't see all the articles you think you should see? Either they are still in Draft status or they're not in the Issue 5 category.
# 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).
# 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.

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.

[[Category:Code4Lib Journal]]

Code4Lib Journal Publicity Venues

2009-02-17T20:39:41Z

Christineschwartz: /* Announcing Publication */

== Distributing Call for Submissions ==

* [http://listserv.syr.edu/archives/autocat.html AUTOCAT] autocat@listserv.syr.edu
* [https://listserv.nd.edu/cgi-bin/wa?A0=CODE4LIB Code4Lib] code4lib@listserv.nd.edu
* [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] web4lib@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 (?)

[[Category: Code4Lib Journal]]

Code4Lib Journal Publicity Venues

2009-02-17T18:06:48Z

Christineschwartz: /* Announcing Publication */

== Distributing Call for Submissions ==

* [http://listserv.syr.edu/archives/autocat.html AUTOCAT] autocat@listserv.syr.edu
* [https://listserv.nd.edu/cgi-bin/wa?A0=CODE4LIB Code4Lib] code4lib@listserv.nd.edu
* [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] web4lib@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:

#code4lib (Tom)
#drupal4lib (Tom)
#ngc4lib (Tom)
#ol-lib (Tom)
#oss4lib (Tom)
#usability4lib (Tom)
#web4lib (Tom)
#xml4lib (Tom)

Still to do:

#Autocat (Chris)
#code4lib website (?)
#LISWire (?)
#lita-l (Chris)
#Metadatalibrarians (Chris)

[[Category: Code4Lib Journal]]

Code4Lib Corrections

2009-01-07T18:20:14Z

Christineschwartz:

There are three approaches to correcting a published article, depending on the impact of the correction:

# Corrections to spelling or simple grammar (a change in punctuation, etc.) should simply be made.
# Corrections that change the actual wording of the article should be made inline, with a "Corrections" section added at the end of the article outlining the date and the change made. This should be done only if absolutely necessary.
# A clarification or explanation of the text should be made in the "Corrections" section, with a note added to the original text to "See Correction", linked to the explanation/clarification. See, for example, [http://journal.code4lib.org/articles/527 We Love Open Source Software. No, You Can’t Have Our Code] (Issue 5).

[[Category: Code4Lib Journal]]

Code4Lib Journal Publicity Venues

2008-11-10T14:46:20Z

Christineschwartz:

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

Added for Issue 6:
*AUTOCAT

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 Deadlines

2008-10-30T14:15:46Z

Christineschwartz: /* Sixth issue */

== Formula for calculating deadlines ==

A rough guideline based on first two issues:

* '''week -14:''' Proposals due
* '''week -8:''' First draft due
* '''week 0:''' Publication

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

Dates pulled from [http://groups.google.com/group/c4lj-discuss/browse_thread/thread/52f178f1a1d133a5/8df8c50af2773cd4?#8df8c50af2773cd4 c4lj-discuss thread]

Note: these aren't consistent -- i.e., when does the call for proposals go out for issue 3?

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

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

2008-10-30T14:14:18Z

Christineschwartz: /* Deadlines for Issues */

== Formula for calculating deadlines ==

A rough guideline based on first two issues:

* '''week -14:''' Proposals due
* '''week -8:''' First draft due
* '''week 0:''' Publication

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

Dates pulled from [http://groups.google.com/group/c4lj-discuss/browse_thread/thread/52f178f1a1d133a5/8df8c50af2773cd4?#8df8c50af2773cd4 c4lj-discuss thread]

Note: these aren't consistent -- i.e., when does the call for proposals go out for issue 3?

=== 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 23: publication

=== 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 WordPress Input Guidelines

2008-09-20T13:45:06Z

Christineschwartz: /* Bibliographies/Endnotes */

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

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

Two options for images and other attached content/media:
# use WordPress uploaded content managing feature, or
# upload the content to our host manually.

jrochkind found the WordPress content managing feature to be more of a pain than it was worth, so is uploading content 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/browse_thread/thread/7d66327ef69c507a/6dceb7d578676334?lnk=gst&q=account+upload#6dceb7d578676334 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/
* 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 that are not part of the link. HTML coding example: [<a href="#note1">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.

Add a custom field to the article called "author" (see the bottom of the "write post" page). 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, then there will be no author information attached to the article.

==Categories/Tags==
Every article in issue 1 should be put in a category "Issue 1". Etc. This should make it easier to generate issue specific RSS feeds and do other stuff at a later date.

==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/d31f58a145ef877b/1ed35fa6bcd01e86?lnk=gst&q=author+preview#1ed35fa6bcd01e86 post] on c4lj-articles for the login information for the author account.
;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.

[[Category:Code4Lib Journal]]

==Dates of Posts--order on ToC==
The dates of the posts in Word Press control what order they will show up in on the issue table of contents.

I think it's the coordinating editor's responsibility to decide what order he or she would like them to show up in, and set the dates appropriately. For issue 1, I did this by setting them all to the same date, and mucking with the actual hour/minute/second time to control order. The most 'recent' (ie, the latest) time will show up first.

<del>I also made a mistake with issue 1 though, thinking the date didn't really matter except for this. In fact, the date/time should be set as close to the actual publication (that is, making public) time as reasonably possible to keep feed readers from getting confused. When I had the date of the post set to a few days before the actual make-public time, this caused the code4lib planet feedreader to put the posts down at the bottom of it's screen the first time they showed up in the feed, since it was ordering by date (reversed).

So coordinating editor should probably set the date/hour to be close to date of actual publication, and then mess with minutes to determine order on ToC?</del>

Don't worry about exactly which date and time you use, just make sure they're in order. The Issue Manager plugin will take care of setting it to the right date.

Code4Lib Journal WordPress Input Guidelines

2008-09-20T12:16:31Z

Christineschwartz: /* Bibliographies/Endnotes */

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

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

Two options for images and other attached content/media:
# use WordPress uploaded content managing feature, or
# upload the content to our host manually.

jrochkind found the WordPress content managing feature to be more of a pain than it was worth, so is uploading content 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/browse_thread/thread/7d66327ef69c507a/6dceb7d578676334?lnk=gst&q=account+upload#6dceb7d578676334 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/
* 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.

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

Add a custom field to the article called "author" (see the bottom of the "write post" page). 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, then there will be no author information attached to the article.

==Categories/Tags==
Every article in issue 1 should be put in a category "Issue 1". Etc. This should make it easier to generate issue specific RSS feeds and do other stuff at a later date.

==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/d31f58a145ef877b/1ed35fa6bcd01e86?lnk=gst&q=author+preview#1ed35fa6bcd01e86 post] on c4lj-articles for the login information for the author account.
;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.

[[Category:Code4Lib Journal]]

==Dates of Posts--order on ToC==
The dates of the posts in Word Press control what order they will show up in on the issue table of contents.

I think it's the coordinating editor's responsibility to decide what order he or she would like them to show up in, and set the dates appropriately. For issue 1, I did this by setting them all to the same date, and mucking with the actual hour/minute/second time to control order. The most 'recent' (ie, the latest) time will show up first.

<del>I also made a mistake with issue 1 though, thinking the date didn't really matter except for this. In fact, the date/time should be set as close to the actual publication (that is, making public) time as reasonably possible to keep feed readers from getting confused. When I had the date of the post set to a few days before the actual make-public time, this caused the code4lib planet feedreader to put the posts down at the bottom of it's screen the first time they showed up in the feed, since it was ordering by date (reversed).

So coordinating editor should probably set the date/hour to be close to date of actual publication, and then mess with minutes to determine order on ToC?</del>

Don't worry about exactly which date and time you use, just make sure they're in order. The Issue Manager plugin will take care of setting it to the right date.