Code4Lib - User contributions [en]

C4L2010 manning discount

2010-01-27T14:16:59Z

128.230.13.231: /* Manning Publications Discount Code */

= Manning Publications Discount Code =

Manning Publications was kind enough to donate 12 books for drawings at the conference this year. All they wanted in return was to send out this discount code for you to use:

<blockquote>Code4Lib conference attendees can get 40% off any purchase from [http://manning.com manning.com] with the promotional code '''code4lib''' until Feb 28, 2010. Get great new titles like ''jQuery in Action, 2nd Edition'', ''The Art of Unit Testing'' and ''Becoming Agile''!</blockquote>

[[Category: Code4Lib2010]]

C4L2010 social activities

2010-01-27T14:16:37Z

128.230.13.231: /* BBQ Excursion Signup */

==Code4Lib 2010 social activities ==

==Ideas==
[http://www.citizen-times.com/apps/pbcs.dll/article?AID=2009912010314 New breweries opening]

[http://digital.library.appstate.edu/code4lib2010.html Original Proposal (suggests some nearby events)]

[http://ashevilletwitterhashtags.blogspot.com/2009/09/asheville-beer-avlbeer.html Asheville Beer Hashtag]

==Planned events==

Plan one if you like! Either on your own or you can [[Committees_sign-up_page|join the social activities committee]].

== Asheville Brews Cruise ==

"Experience a taste of Asheville’s thriving local beer scene with an exclusive tour of three of our award-winning microbreweries." - http://www.brewscruise.com/asheville/

This activity would be either Tuesday or Wednesday night starting at 6pm and leaving from the hotel. First stop would be the Asheville Pizza & Brewing Co. to sample 16-20 different beers and eat some pizza (food billed separately). Then two more stops at the French Broad Brewery and the Highland Brewing Company for more beer sampling and learning about their brewery process.

The cost will be $40/person (not including pizza). The minimum number of folks we need is 16. There is no maximum.

==== Beer Cruise Signup ====

Please indicate interest in the Beer Cruise by adding your name to the list below. We'll figure out a way to coordinate and communicate the details somewhere down the line.

* Jay Luker (organizer)
* Mike Giarlo (inebriator)
* Rob Casson (drunk)
* Declan Fleming (beer receptacle)
* Jim Safley (recovering teetotaler)
* Ian Walls (epicurean of ale)
* Bill Erickson (burp)

== 12 Bones BBQ Lunch Excursion ==

[http://www.12bones.com/ 12 Bones BBQ] is widely considered the best BBQ in Asheville [[http://www.yelp.com/biz/12-bones-smokehouse-asheville *]]. However it is only open from 11-4, M-F. I would like to organize a lunchtime excursion via taxi or maybe hotel shuttle. According to google maps it is only a five minute drive from the hotel, so should be doable within our lunch window.

This excursion is tentatively scheduled for lunchtime on Wednesday, February 24th.

==== BBQ Excursion Signup ====

For the time being please indicate interest in the BBQ excursion by adding your name to the list below. We'll figure out a way to coordinate and communicate the details somewhere down the line.

* Jay Luker (organizer)
* Mike Giarlo (consumer)
* Rob Casson (glutton)
* Declan Fleming (condor)
* Erik Hatcher (carnivore)

[[Category: Code4Lib2010]]

Code4Lib Journal Deadlines

2010-01-25T15:16:53Z

128.230.13.231: /* Tenth 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

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

C4L2010rideshare

2009-12-17T18:07:38Z

128.230.13.231: /* Asheville/Arden Regional Airport */

== Rideshare Info ==

Several people have made vague but curious noises about trying to share transportation to and from Asheville. This page will attempt to organize the details relevant to help attendees make appropriate travel/transportation plans.

Each table below represents a group of attendees with relatively common transportation needs. Feel free to combine/split/add tables to suit different needs. The columns should be self-explanatory, with '''Driving?''' indicating that you're willing/able to share the driving (even if it's someone else's car/rental), and '''Van?''' indicating whether you would be interested in taking one of the App. State vans (if it were to make a couple runs to the airport).

=== Charlotte Douglas International Airport ===
{| border="1" cellpadding="5" class="sortable"
|- style="text-align: left;"
! Name !! Arriving !! Departing !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van?
|-
| Michael Klein || 2010-02-21 (Sunday; late afternoon/evening) || 2010-02-26 (Friday) || No || Yes || Yes || Yes || Yes
|-
| Julia Bauder || 2010-02-21 (Sunday; mid-afternoon) || 2010-02-25 (Thursday; late afternoon) || No || Yes || Yes || Yes || Yes
|}

=== Asheville/Arden Regional Airport ===
{| border="1" cellpadding="5" class="sortable"
|- style="text-align: left;"
! Name !! Arriving !! Departing !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van?
|-
| Mike Giarlo || 2010-02-21 (Sunday) 11:38am || 2010-02-26 (Friday) 12:03pm || No || Yes || Yes || No || Yes
|-
| Daniel Lovins || 2010-02-21 (Sunday) 11:57am || 2010-02-25 (Thursday) 2:21pm || No || Yes || Yes || Yes || Yes
|-
| Jean Rainwater || 2010-02-21 (Sunday) 12:15pm || 2010-02-26 (Friday) 4:00pm || No || Yes || Yes || No || Yes
|-
| Michael Doran || 2010-02-21 (Sunday) 6:14pm || 2010-02-26 (Friday) 11:25am || No || No || No || No || Yes
|-
| Andrew Darby || 2010-02-21 (Sunday) 6:15pm || 2010-02-26 (Friday) 11:25am || No || Yes || Yes || No || Yes
|-
| Cody Hennesy || 2010-02-21 (Sunday) 9:55pm || 2010-02-25 (Thursday) 4:17pm || No || Yes || Yes || No || Yes
|-
| Tim McGeary || 2010-02-22 (Monday) 9:35pm || 2010-02-25 (Thursday) 4:30pm || No || Yes || Yes || No || Yes
|-
| Tom Keays || 2010-02-21 (Sunday) 12:09pm || 2010-02-25 (Thursday) 12:55pm || No || Yes || Yes || No || Yes
|}

=== Northeast (VA/DC/MD/DE/PA/NJ/NY/New England) ===
{| border="1" cellpadding="5" class="sortable"
|- style="text-align: left;"
! Name !! Traveling From !! Plan to Arrive !! Plan to Depart !! Car? !! Share rental cost? !! Gas? !! Driving?
|-
| Ray Schwartz || New York City Metro || Before Preconferences || To get to prefconfs in time || N/A || Yes || Yes || Yes
|-
| Yitzchak Schaffer || New York City Metro || Monday (not for precon) || Thurs aftn || no, willing to rent || yes || yes || yes
|-
| Jodi Schneider || NJ Turnpike/Philly Metro || Before Preconferences || Thurs aftn || no || Yes || Yes || No
|}

=== Michigan/Ohio/West Virginia ===
{| border="1" cellpadding="5" class="sortable"
|- style="text-align: left;"
! Name !! Traveling From !! Plan to Arrive !! Plan to Depart !! Car? !! Share rental cost? !! Gas? !! Driving?
|-
| Peter Murray || Columbus, OH || Monday afternoon || Thursday after conference close || Yes || Yes || Yes || Yes
|-

[[Category: Code4Lib2010]]

Code4Lib Journal Entries in Directory of Open Access Journals

2009-07-01T17:35:42Z

128.230.13.231: /* Semi-Automated */

There are two ways to get metadata into the Directory of Open Access Journals: 1) by hand, or 2) through the use of an XML file. Before you do either method, please keep in mind the following things:

# We chose not to have volume numbers, just issue numbers. Issue numbers will just keep incrementing.
# We decided that the "record number" for an article is the article-id that shows up in the WordPress URI. That is, they are not sequential, numbers are skipped. That's fine. So there is no 'start page', but there is a 'record number'; there is no 'end page'.
# Enter the abstract and authors affiliation exactly as found in our published articles.
# Enter keywords if there are any. If not, leave this blank

==By Hand==

To edit by hand go to http://www.doaj.org/restricted, enter our secret username/password combination, and do the necessary data entry.

See this [http://groups.google.com/group/c4lj-articles/browse_thread/thread/ba2efed674d66d7a post] for username and password information.

==Semi-Automated==

To use the XML file to do data entry:
# make sure the WordPress databases is up-to-date,
# go to http://journal.code4lib.org/issues/issue#/feed/doaj to get the necessary XML. (eg http://journal.code4lib.org/issues/issue5/feed/doaj.)
# edit the XML [http://journal.code4lib.org/doaj/|so each author is in a element by themselves],
# validate the XML against the Directory's schema,
#* Download a copy of the DOAJ schema, http://www.doaj.org/schemas/doajArticles.xsd , to your computer along with the XML file you've just edited.
#* Upload both files to a schema validator service such as http://tools.decisionsoft.com/schemaValidate/
# go to http://www.doaj.org/restricted and upload the fruits of your labors. See this [http://groups.google.com/group/c4lj-articles/browse_thread/thread/ba2efed674d66d7a post] for username and password information.

More info about the feed and how to customize the XML for import into DOAJ:
* http://journal.code4lib.org/doaj/ and
* http://www.doaj.org/doaj?func=loadTempl&templ=uploadInfo

--[[User:Ericleasemorgan|Eric Lease Morgan]] 10:42, 28 May 2008 (PDT)

[[Category: Code4Lib Journal]]

Code4Lib Journal Entries in Directory of Open Access Journals

2009-07-01T17:35:12Z

128.230.13.231: /* Semi-Automated */

There are two ways to get metadata into the Directory of Open Access Journals: 1) by hand, or 2) through the use of an XML file. Before you do either method, please keep in mind the following things:

# We chose not to have volume numbers, just issue numbers. Issue numbers will just keep incrementing.
# We decided that the "record number" for an article is the article-id that shows up in the WordPress URI. That is, they are not sequential, numbers are skipped. That's fine. So there is no 'start page', but there is a 'record number'; there is no 'end page'.
# Enter the abstract and authors affiliation exactly as found in our published articles.
# Enter keywords if there are any. If not, leave this blank

==By Hand==

To edit by hand go to http://www.doaj.org/restricted, enter our secret username/password combination, and do the necessary data entry.

See this [http://groups.google.com/group/c4lj-articles/browse_thread/thread/ba2efed674d66d7a post] for username and password information.

==Semi-Automated==

To use the XML file to do data entry:
# make sure the WordPress databases is up-to-date,
# go to http://journal.code4lib.org/issues/issue#/feed/doaj to get the necessary XML. (eg http://journal.code4lib.org/issues/issue5/feed/doaj.)
# edit the XML [http://journal.code4lib.org/doaj/|so each author is in a element by themselves],
# validate the XML against the Directory's schema,
#* Download a copy of the DOAJ schema, http://www.doaj.org/schemas/doajArticles.xsd , to your computer along with the XML file you've just edited.
#* Upload both files to a schema validator service such as http://tools.decisionsoft.com/schemaValidate/
# go to http://www.doaj.org/restricted and upload the fruits of your labors. See this [http://groups.google.com/group/c4lj-articles/browse_thread/thread/ba2efed674d66d7a post] for username and password information.

More info about the feed and how to customize the XML for import into DOAJ: http://journal.code4lib.org/doaj/ and http://www.doaj.org/doaj?func=loadTempl&templ=uploadInfo

--[[User:Ericleasemorgan|Eric Lease Morgan]] 10:42, 28 May 2008 (PDT)

[[Category: Code4Lib Journal]]

Code4Lib Journal Entries in Directory of Open Access Journals

2009-07-01T17:32:45Z

128.230.13.231: /* Semi-Automated */

There are two ways to get metadata into the Directory of Open Access Journals: 1) by hand, or 2) through the use of an XML file. Before you do either method, please keep in mind the following things:

# We chose not to have volume numbers, just issue numbers. Issue numbers will just keep incrementing.
# We decided that the "record number" for an article is the article-id that shows up in the WordPress URI. That is, they are not sequential, numbers are skipped. That's fine. So there is no 'start page', but there is a 'record number'; there is no 'end page'.
# Enter the abstract and authors affiliation exactly as found in our published articles.
# Enter keywords if there are any. If not, leave this blank

==By Hand==

To edit by hand go to http://www.doaj.org/restricted, enter our secret username/password combination, and do the necessary data entry.

See this [http://groups.google.com/group/c4lj-articles/browse_thread/thread/ba2efed674d66d7a post] for username and password information.

==Semi-Automated==

To use the XML file to do data entry:
# make sure the WordPress databases is up-to-date,
# go to http://journal.code4lib.org/issues/issue#/feed/doaj to get the necessary XML. (eg http://journal.code4lib.org/issues/issue5/feed/doaj.)
# edit the XML [http://journal.code4lib.org/doaj/|so each author is in a element by themselves],
# validate the XML against the Directory's schema,
#* Download a copy of the DOAJ schema, http://www.doaj.org/schemas/doajArticles.xsd , to your computer along with the XML file you've just edited.
#* Upload both files to a schema validator service such as http://tools.decisionsoft.com/schemaValidate/
# go to http://www.doaj.org/restricted and upload the fruits of your labors. See this [http://groups.google.com/group/c4lj-articles/browse_thread/thread/ba2efed674d66d7a post] for username and password information.

More info about the feed and how to customize the XML for import into DOAJ: http://journal.code4lib.org/doaj/

--[[User:Ericleasemorgan|Eric Lease Morgan]] 10:42, 28 May 2008 (PDT)

[[Category: Code4Lib Journal]]

Code4Lib Style Guide

2008-12-10T19:59:51Z

128.230.13.231: /* Code */

== 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 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, pascal, java, js, jscript, javascript, 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.

=== 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-10T19:56:54Z

128.230.13.231: /* Code */

== 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 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 cpp, c, c++, c#, c-sharp, csharp, css, delphi, pascal, java, js, jscript, javascript, php, py, python, rb, ruby, rails, ror, sql, vb, vb.net, xml, html, xhtml, and xslt. Pretty much everything except perl.

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

2008-09-22T21:08:01Z

128.230.13.231: /* 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:

#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-22T21:03:53Z

128.230.13.231: /* 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:

#code4lib (Ken)
#drupal4lib (Ken)
#LISWire (Ken)
#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:58:01Z

128.230.13.231: /* 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)
#ol-lib (Tom)
#oss4lib (Tom)
#public-lod (Tom)
#usability4lib (Tom)
#xml4lib (Tom)

[[Category: Code4Lib Journal]]

Code4Lib Journal WordPress Input Guidelines

2007-12-06T19:53:44Z

128.230.13.231: /* Images and Attached Content */

Please follow the guidelines below when creating or editing Code4Lib Journal articles in WordPress. Enter all articles as "Posts".

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

Change directory to:
/public/vhost/c/c4lj/html/media

in there you'll find an "issue1" subdir. Inside THERE (or other issue dir), 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/lastname/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. 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>

====External Content====

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

==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.
* I have been inserting the string "(COinS)" inside the span tag, so the user without a browser extension will see that something is there she might be interested in. This might be better replaced with a link to a brief page we provide on what COinS can do for you and where to find a browser extension.

==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)", then give a short paragraph about 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.

[[Category:Code4Lib Journal]]