Code4Lib - User contributions [en]

2013 Code4Lib Midwest Conference

2010-03-03T19:46:05Z

Jbrinley:

==Possible meeting venues==
* jbrinley's fire pit

==Who's interested in Code4Lib Midwest? Put your name/location here...==
* Jonathan Brinley, Adelie Design - Pendleton, IN

2013 Code4Lib Midwest Conference

2010-03-03T19:43:30Z

Jbrinley: /* Who's interested in Code4Lib North? Put your name/location here... */

==Who's interested in Code4Lib Midwest? Put your name/location here...==
*Jonathan Brinley, Adelie Design - Pendleton, IN

2013 Code4Lib Midwest Conference

2010-03-03T19:43:12Z

Jbrinley: New page: ==Who's interested in Code4Lib North? Put your name/location here...== *Jonathan Brinley, Adelie Design - Pendleton, IN

==Who's interested in Code4Lib North? Put your name/location here...==
*Jonathan Brinley, Adelie Design - Pendleton, IN

Main Page

2010-03-03T19:40:29Z

Jbrinley: /* Local / Regional Groups */

__NOTOC__
= Code4Lib Wiki =

== About Code4Lib ==

* [[About Code4Lib]] - Background and history of the community

== Code4libcon 2010 ==
''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2010 Code4lib2010 category]''
* [http://code4lib.org/conference/2010/schedule Finalized schedule]
* [[2010 Lightning Talks Signup]] - sign up to give a lightning talk
* [[2010 Breakout Sessions]] - suggest a breakout here
* '''[[2010 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff'''
* [[C4L2010_social_activities|Social Activities]] - ideas & sign-up
* [[Committees sign-up page]] - '''Volunteer to help'''
* [[C4L2011_planning_wishlist|'''Put your ideas for 2011 here!''']]

=== Transportation ===
* [[Asheville Airport to Hotel Van Manifest]]
* [[C4L2010rideshare|General shared travel/transportation planning]]
* [[C4L2010planning:RoommatesRidesEtc|Roommates, Rides, Etc]]

=== Deals ===
* [[C4L2010_manning_discount|Manning Publications Discount]] - discount code (40% off) for use by attendees through Feb. 28, 2010
* Thanks also to our other sponsors!

=== Asheville planning ===
* [[C4L2010planning|2010 Planning]]
* [[C4L2010planning:_wishlist | 2010 Planning Wishlist]] - planning page for issues, expectations, etc. for the 2010 conference

== Local / Regional Groups ==

* [[NYC|Code4LibNYC]] - NYC and surrounding areas
* [[NEC4L|New England Code4lib]] - New England
* [http://se.code4lib.org Southeastern Code4lib] - North Carolina, Virginia, Tennessee, etc.
* [[NL|Code4Bib]] - Dutch Code4Bib
* [[MDC|Code4libMDC]] - Maryland, Washington D.C and surrounding areas
* [http://groups.google.com/group/pnwcode4lib?hl=en PNWCode4Lib] - Pacific Northwest
* [[North|code4lib North]] - Ontario and surrounding areas ''(new for Jan 2010!)''
* [[Midwest|Code4Lib Midwest]] - Wherever that is...

== Interest Groups ==

* [[ILS_Interop|ILS Interoperability]] - A group working to develop an infrastructure for interoperating between discovery layers and integrated library systems.
* [[Open_Source_Book_Widgets|Open Source Book Widgets]] - A list of open source book widgets
* [[Discovery|Open Source Discovery]] - Open Source application to enhance and support "discovery" in libraries
* [[Mobile_Apps|Mobile Applications]] - A group interested in mobile web and native application development for libraries

== Software Usage and Documentation ==

* [[Umlaut]] - OpenURL link resolving middleware
* [[:Category:Patterns|Patterns for Collaborative Code]] - Patterns to make your open source 'more open', more amenable to distributed development and use at multiple institutions without forking.
* [[ILS Documentation]]
* [[OSS Directory]]
* [[Getting Started with Zebra]] - indexing and searching MARC records
* [[ruby-marc]] - some notes and recipes for processing MARC files in ruby
* [[Rogue]] - principles for standards creation

== Earlier Conferences and events ==
=== Code4libcon 2009 ===
* [[BookRaffle]] - coordinate begging publishers for books to raffle off at the conference
* [http://inkdroid.org/c4l2009/attendees Get FOAFed] - add your FOAF profile to the network of c4l2009 attendees
* PreConferences:
** [[GIS_preconf_code4libcon2009]] - Open source GIS just like mom used to make
** [[LinkedData]] - A proposal for a linked-data code4lib2009 pre-conference
** [[LibX_Preconference]] - Proposal for a half-day pre-conference targeted at developers who wish to use the LibX 2.0 platform
** [http://code4lib.org/2009/oclc-precon OCLC Grid Services Preconference]
* [[RoommatesRidesEtc]] - Find roommates for Code4Lib 2009, share rides, etc.
* [[2009 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff

=== Other workshops ===
* [http://barcamp.org/SearchCampDC SearchCampDC] - barcamp style event in DC with usual suspects from code4lib
* [[code4lib/elag2010]] - 1-day code4lib preconference at elag2010

== Code4lib Journal ==

* [[:Category:Code4Lib Journal|Code4Lib Journal]] - information and working documents

== Current topics ==

* [[Logo Design Process]]
* [[OCLC Policy Change]]
* [[SirsiDynix: Integrated Library System Platforms on Open Source]]

== Other Code4Lib Sites ==

* [http://www.code4lib.org/ code4lib.org]
* [http://planet.code4lib.org planet.code4lib.org]

[[AdminToDo]] - ideas and tasks for maintaining the Code4Lib sites

Code4Lib Journal WordPress Input Guidelines

2009-06-19T18:14:44Z

Jbrinley: /* Publishing an Issue */

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

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

2007-12-14T20:36:25Z

Jbrinley: /* First 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:''' [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?

=== Third issue ===

* 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

2007-12-14T20:36:03Z

Jbrinley: /* Third issue */

JR Draft

2007-12-12T19:35:08Z

Jbrinley: /* DRAFT, please do not circulate */

=DRAFT, please do not circulate=

Code4Lib Journal

Issue 1

Introduction from the Coordinating Editor

In a constantly changing social and technological environment, libraries have a critical need to adapt to fulfill their missions and satisfy their users. This pressure is acutely felt by those working with library technology. igital services, content and tools have become a part of nearly every aspect of library operations. The "digital library" is here, and most of us work in one.

This mission of this journal is to cover "the intersection of libraries, technology, and the future." We plan to provide practical information to help the library community envision and achieve our technological future, to bring libraries' tradition of collaboration to bear on new challenges. We want the digital libraries of today need to be transformed into the digital libraries of tomorrow, providing quality information while meeting new and changing needs. This course might have its risks, but maintaining the status quo brings its own, greater risks. Libraries and their vendors must take a leading role in the technological innovation that effects this transformation.

===The Code4Lib Community===

One locus of pragmatic innovation has been the Code4Lib community [1]. Inspired in part by the social dynamics of distributed open source projects, Code4Lib is an annual conference and, more importantly, an informal online social and professional network embodying values of transparency, cooperation, and pragmatic problem solving. This dynamic community fosters collaboration and encourages the sharing of skills and ideas [2,3,4]. But paradoxically, this amorphous informality can make it hard for someone new to the field—or wanting to take a new look at the field—to find a comfortable entry point to the community and the resources it has to offer.

We hope the Code4Lib Journal can embody the successful values of the Code4Lib community, while providing increased access to the collective knowledge and experience held in our various informal professional networks (Code4Lib and others) and local organizations, increasing cross-pollination among library technology innovators.

===This Journal is an Experiment===

The Code4Lib Journal project aspires to balance a variety of sometimes competing goals. We want to provide quality articles providing useful information and discussion on bringing library technology into the future. We want every article to be a useful intervention into our communities of practice. We value readability over formality, and hope to meet high standards for quality and utility. At the same time we want to ensure an easy process for authors, letting authors share their important work and ideas with as few barriers as we can get away with. The journal is intentionally edited rather than refereed, and we try to contribute editing advice to help authors improve their articles without aggravation. We are committed to the Journal's free online availability, to increase its visibility and impact in addition to its accessibility. We want the immediacy of a blog, the usefulness of a professional conference, the reliable quality of a good scholarly journal, and the participatory nature of our online communities, all in one easy to read and easy to produce package.

And we are trying to accomplish all of that on a shoestring, with an all volunteer editorial committee sharing management and editorial responsibilities in an informal, open, and productive way as per the Code4Lib ethic. Our Coordinating Editor will rotate with every issue; I'll soon be passing the baton to Eric Lease Morgan.

The Code4Lib Journal project is very much like some of the innovative library technology projects many of us work on in our daily lives, balancing competing values and priorities with limited resources. And we've tackled this project the same way we do those, with a 'can do' spirit and an agile development approach—in other words, we're making it up as we go along.

So how is the experiment working out? We think we've got a great first issue. This is due to the great work of our authors, and of the Editorial Committee. I am not alone among the Editorial Committee in discovering that inventing a journal—even one solely online which is intended to be relatively informal and agile—is more work than I personally expected. All of our authors and editorial staff deserve to be proud of what we've produced together through hard work [5]. But ultimately only the judgments and actions of you, our readers, can measure our success. If you think this first issue is evidence of a worthwhile endeavor, you can contribute to its future success.

===How Can You Help?===

You can read our articles, suggest them to others, and continue the discussions in your blogs, listservs, and right in the articles themselves. We want every article here to be part of an ongoing conversation towards cooperative innovation among libraries.

You can submit articles to us, and when you run into a colleague with an interesting project or idea, you can suggest that they submit articles to us. We're happy to accept articles and proposals at any time, although there will of course be cut off dates for particular issues. We welcome anyone interested in participating in the operation of the journal to join our public discussion list for journal business [6]. At some point in the future, we will solicit more official members of the Editorial Committee, too.

We hope that this Journal can be one more contribution to the developing culture of collaboration around library technology, and we welcome you to join in our experiment.

Jonathan Rochkind

Coordinating Editor (for Issue 1),

The Code4Lib Journal

===Code4Lib Issue 1 Editorial Committee===

Carol Bean

Jonathan Brinley

Edward Corrado

Tom Keays

Emily Lynema

Eric Lease Morgan

Ron Peterson

Jonathan Rochkind

Jodi Schneider

Ken Varnum

===Notes===

[1] http://www.code4lib.org

[2] Barrera, Antonio and Chilana, Parmit and Clarke, Kevin and Giarlo, Michael (2007) 2007 Code4Lib Conference Report. Library Hi Tech News 24(6). pp. 4-7. http://eprints.rclis.org/archive/00011670/

[3] Frumkin, Jeremy and Chudnov, Dan. (2006) Code4Lib 2006. Ariadne Issue 47, April 2006. http://www.ariadne.ac.uk/issue47/code4lib-2006-rpt/

[4] Chudnov, Daniel. (2007). code4libcon Shows What a Participatory Conference Looks Like. Computers in Libraries. 27(5), May 2007. pp 37-40

[5] Special thanks to Jonathan Brinley for providing the nuts-and-bolts web management that many of us wanted to leave at our day jobs.

[6] http://groups.google.com/group/c4lj-discuss/ .

JR Draft

2007-12-12T19:28:25Z

Jbrinley: /* DRAFT, please do not circulate */

=DRAFT, please do not circulate=

Code4Lib Journal

Issue 1

Introduction from the Coordinating Editor

In a constantly changing social and technological environment, libraries have a critical need to adapt to fulfill their missions and satisfy their users. This pressure is acutely felt by those working with library technology. igital services, content and tools have become a part of nearly every aspect of library operations. The "digital library" is here, and most of us work in one.

This mission of this journal is to cover "the intersection of libraries, technology, and the future." We plan to provide practical information to help the library community envision and achieve our technological future, to bring libraries' tradition of collaboration to bear on new challenges. We want the digital libraries of today need to be transformed into the digital libraries of tomorrow, providing quality information while meeting new and changing needs.

We are at an exciting juncture, with new opportunities to face these challenges. The same network and information technology that is responsible for foundational shifts in our environment makes possible tools to face this new environment that would have seemed a futuristic fantasy a decade ago, while the internet provides an ability to collaborate with each other over a distance on solutions, accomplishing through cooperation what limited resources make infeasible individually. Libraries are increasingly realizing that while there are risks to undertaking a transformation of our technology and our organizations, there are even greater risks to maintaining the status quo. In order to take full advantage of these possibilities, libraries are increasingly realizing they need to step up to a leading role in technological innovation towards our users’ needs, alongside our vendors.

===The Code4Lib Community===

One locus of pragmatic innovation has been the Code4Lib community [1]. Inspired in part by the social dynamics of distributed open source projects, Code4Lib is an annual conference and, more importantly, an informal online social and professional network embodying values of transparency, cooperation, and pragmatic problem solving. This dynamic community fosters collaboration and encourages the sharing of skills and ideas [2,3,4]. But paradoxically, this amorphous informality can make it hard for someone new to the field—or wanting to take a new look at the field—to find a comfortable entry point to the community and the resources it has to offer.

We hope the Code4Lib Journal can embody the successful values of the Code4Lib community, while providing increased access to the collective knowledge and experience held in our various informal professional networks (Code4Lib and others) and local organizations, increasing cross-pollination among library technology innovators.

===This Journal is an Experiment===

The Code4Lib Journal project aspires to balance a variety of sometimes competing goals. We want to provide quality articles providing useful information and discussion on bringing library technology into the future. We want every article to be a useful intervention into our communities of practice. We value readability over formality, and hope to meet high standards for quality and utility. At the same time we want to ensure an easy process for authors, letting authors share their important work and ideas with as few barriers as we can get away with. The journal is intentionally edited rather than refereed, and we try to contribute editing advice to help authors improve their articles without aggravation. We are committed to the Journal's free online availability, to increase its visibility and impact in addition to its accessibility. We want the immediacy of a blog, the usefulness of a professional conference, the reliable quality of a good scholarly journal, and the participatory nature of our online communities, all in one easy to read and easy to produce package.

And we are trying to accomplish all of that on a shoestring, with an all volunteer editorial committee sharing management and editorial responsibilities in an informal, open, and productive way as per the Code4Lib ethic. Our Coordinating Editor will rotate with every issue; I'll soon be passing the baton to Eric Lease Morgan.

The Code4Lib Journal project is very much like some of the innovative library technology projects many of us work on in our daily lives, balancing competing values and priorities with limited resources. And we've tackled this project the same way we do those, with a 'can do' spirit and an agile development approach—in other words, we're making it up as we go along.

So how is the experiment working out? We think we've got a great first issue. This is due to the great work of our authors, and of the Editorial Committee. I am not alone among the Editorial Committee in discovering that inventing a journal—even one solely online which is intended to be relatively informal and agile—is more work than I personally expected. All of our authors and editorial staff deserve to be proud of what we've produced together through hard work [5]. But ultimately only the judgments and actions of you, our readers, can measure our success. If you think this first issue is evidence of a worthwhile endeavor, you can contribute to its future success.

===How Can You Help?===

You can read our articles, suggest them to others, and continue the discussions in your blogs, listservs, and right in the articles themselves. We want every article here to be part of an ongoing conversation towards cooperative innovation among libraries.

You can submit articles to us, and when you run into a colleague with an interesting project or idea, you can suggest that they submit articles to us. We're happy to accept articles and proposals at any time, although there will of course be cut off dates for particular issues. We welcome anyone interested in participating in the operation of the journal to join our public discussion list for journal business [6]. At some point in the future, we will solicit more official members of the Editorial Committee, too.

We hope that this Journal can be one more contribution to the developing culture of collaboration around library technology, and we welcome you to join in our experiment.

Jonathan Rochkind

Coordinating Editor (for Issue 1),

The Code4Lib Journal

===Code4Lib Issue 1 Editorial Committee===

Carol Bean

Jonathan Brinley

Edward Corrado

Tom Keays

Emily Lynema

Eric Lease Morgan

Ron Peterson

Jonathan Rochkind

Jodi Schneider

Ken Varnum

===Notes===

[1] http://www.code4lib.org

[2] Barrera, Antonio and Chilana, Parmit and Clarke, Kevin and Giarlo, Michael (2007) 2007 Code4Lib Conference Report. Library Hi Tech News 24(6). pp. 4-7. http://eprints.rclis.org/archive/00011670/

[3] Frumkin, Jeremy and Chudnov, Dan. (2006) Code4Lib 2006. Ariadne Issue 47, April 2006. http://www.ariadne.ac.uk/issue47/code4lib-2006-rpt/

[4] Chudnov, Daniel. (2007). code4libcon Shows What a Participatory Conference Looks Like. Computers in Libraries. 27(5), May 2007. pp 37-40

[5] Special thanks to Jonathan Brinley for providing the nuts-and-bolts web management that many of us wanted to leave at our day jobs.

[6] http://groups.google.com/group/c4lj-discuss/ .

JR Draft

2007-12-12T19:02:55Z

Jbrinley:

=DRAFT, please do not circulate=

Code4Lib Journal

Issue 1

Introduction from the Coordinating Editor

This is a critical time for libraries. The social environment around libraries has changed such that libraries need to transform as well. This is specifically a critical time for library technology. Digital services, content and tools have become a part of nearly every aspect of library operations. The “digital library” is already here, and most of us work in one. But these digital libraries of today need to be transformed into the digital libraries of tomorrow to meet radically new needs while carrying forward libraries’ principles of quality provision of information, and bringing libraries’ tradition of collaboration to bear on new challenges. This mission of this journal is to cover "the intersection of libraries, technology, and the future," providing practical information to help the library community envision and achieve our technological future, one step at a time.

We are at an exciting juncture, with new opportunities to face these serious challenges. The same network and information technology that is responsible for foundational shifts in our environment makes possible tools to face this new environment that would have seemed a futuristic fantasy a decade ago, while the internet provides an ability to collaborate with each other over a distance on solutions, accomplishing through cooperation what limited resources make infeasible individually. Libraries are increasingly realizing that while there are risks to undertaking a transformation of our technology and our organizations, there are even greater risks to maintaining the status quo. In order to take full advantage of these possibilities, libraries are increasingly realizing they need to step up to a leading role in technological innovation towards our users’ needs, alongside our vendors.

===The Code4Lib Community===

One locus of pragmatic innovation has been the Code4Lib community [1]. Inspired in part by the social dynamics of distributed open source projects, Code4Lib is an annual conference and, more importantly, an informal online social and professional network embodying values of transparency, cooperation, and pragmatic problem solving. This dynamic community fosters collaboration and encourages the sharing of skills and ideas [2,3,4]. But paradoxically, this amorphous informality can make it hard for someone new to the field—or wanting to take a new look at the field—to find a comfortable entry point to the community and the resources it has to offer.

We hope the Code4Lib Journal can embody the successful values of the Code4Lib community, while providing increased access to the collective knowledge and experience held in our various informal professional networks (Code4Lib and others) and local organizations, increasing cross-pollination among library technology innovators.

===This Journal is an Experiment===

The Code4Lib Journal project aspires to balance a variety of sometimes competing goals. We want to provide quality articles providing useful information and discussion on bringing library technology into the future. We want every article to be a useful intervention into our communities of practice. We value readability over formality, and hope to meet high standards for quality and utility. At the same time we want to ensure an easy process for authors, letting authors share their important work and ideas with as few barriers as we can get away with. The journal is intentionally edited rather than refereed, and we try to contribute editing advice to help authors improve their articles without aggravation. We are committed to the Journal's free online availability, to increase its visibility and impact in addition to its accessibility. We want the immediacy of a blog, the usefulness of a professional conference, the reliable quality of a good scholarly journal, and the participatory nature of our online communities, all in one easy to read and easy to produce package.

And we are trying to accomplish all of that on a shoestring, with an all volunteer editorial committee sharing management and editorial responsibilities in an informal, open, and productive way as per the Code4Lib ethic. Our Coordinating Editor will rotate with every issue; I'll soon be passing the baton to Eric Lease Morgan.

The Code4Lib Journal project is very much like some of the innovative library technology projects many of us work on in our daily lives, balancing competing values and priorities with limited resources. And we've tackled this project the same way we do those, with a 'can do' spirit and an agile development approach—in other words, we're making it up as we go along.

So how is the experiment working out? We think we've got a great first issue. This is due to the great work of our authors, and of the Editorial Committee. I am not alone among the Editorial Committee in discovering that inventing a journal—even one solely online which is intended to be relatively informal and agile—is more work than I personally expected. All of our authors and editorial staff deserve to be proud of what we've produced together through hard work [5]. But ultimately only the judgments and actions of you, our readers, can measure our success. If you think this first issue is evidence of a worthwhile endeavor, you can contribute to its future success.

===How Can You Help?===

You can read our articles, suggest them to others, and continue the discussions in your blogs, listservs, and right in the articles themselves. We want every article here to be part of an ongoing conversation towards cooperative innovation among libraries.

You can submit articles to us, and when you run into a colleague with an interesting project or idea, you can suggest that they submit articles to us. We're happy to accept articles and proposals at any time, although there will of course be cut off dates for particular issues. We welcome anyone interested in participating in the operation of the journal to join our public discussion list for journal business [6]. At some point in the future, we will solicit more official members of the Editorial Committee, too.

We hope that this Journal can be one more contribution to the developing culture of collaboration around library technology, and we welcome you to join in our experiment.

Jonathan Rochkind

Coordinating Editor (for Issue 1),

The Code4Lib Journal

===Code4Lib Issue 1 Editorial Committee===

Carol Bean

Jonathan Brinley

Edward Corrado

Tom Keays

Emily Lynema

Eric Lease Morgan

Ron Peterson

Jonathan Rochkind

Jodi Schneider

Ken Varnum

===Notes===

[1] http://www.code4lib.org

[2] Barrera, Antonio and Chilana, Parmit and Clarke, Kevin and Giarlo, Michael (2007) 2007 Code4Lib Conference Report. Library Hi Tech News 24(6). pp. 4-7. http://eprints.rclis.org/archive/00011670/

[3] Frumkin, Jeremy and Chudnov, Dan. (2006) Code4Lib 2006. Ariadne Issue 47, April 2006. http://www.ariadne.ac.uk/issue47/code4lib-2006-rpt/

[4] Chudnov, Daniel. (2007). code4libcon Shows What a Participatory Conference Looks Like. Computers in Libraries. 27(5), May 2007. pp 37-40

[5] Special thanks to Jonathan Brinley for providing the nuts-and-bolts web management that many of us wanted to leave at our day jobs.

[6] http://groups.google.com/group/c4lj-discuss/ .

JR Draft

2007-12-12T18:51:50Z

Jbrinley:

=DRAFT, please do not circulate=

Code4Lib Journal

Issue 1

Introduction from the Coordinating Editor

This is a critical time for libraries. The social environment around libraries has changed such that libraries need to transform as well. This is specifically a critical time for library technology. Digital services, content and tools have become a part of nearly every aspect of library operations. The “digital library” is already here, and most of us work in one. But these digital libraries of today need to be transformed into the digital libraries of tomorrow to meet radically new needs while carrying forward libraries’ principles of quality provision of information, and bringing libraries’ tradition of collaboration to bear on new challenges. This mission of this journal is to cover “the intersection of libraries, technology, and the future,” providing practical information to help the library community envision and achieve our technological future, one step at a time.

We are at an exciting juncture, with new opportunities to face these serious challenges. The same network and information technology that is responsible for foundational shifts in our environment makes possible tools to face this new environment that would have seemed a futuristic fantasy a decade ago, while the internet provides an ability to collaborate with each other over a distance on solutions, accomplishing through cooperation what limited resources make infeasible individually. Libraries are increasingly realizing that while there are risks to undertaking a transformation of our technology and our organizations, there are even greater risks to maintaining the status quo. In order to take full advantage of these possibilities, libraries are increasingly realizing they need to step up to a leading role in technological innovation towards our users’ needs, alongside our vendors.

===The Code4Lib Community===

One locus of pragmatic innovation has been the Code4Lib community [1]. Inspired in part by the social dynamics of distributed open source projects, Code4Lib is an annual conference and, more importantly, an informal online social and professional network embodying values of transparency, cooperation, and pragmatic problem solving. This dynamic community fosters collaboration and encourages the sharing of skills and ideas [2,3,4]. But paradoxically, this amorphous informality can make it hard for someone new to the field—or wanting to take a new look at the field—to find a comfortable entry point to the community and the resources it has to offer.

We hope the Code4Lib Journal can embody the successful values of the Code4Lib community, while providing increased access to the collective knowledge and experience held in our various informal professional networks (Code4Lib and others) and local organizations, increasing cross-pollination among library technology innovators.

===This Journal is an Experiment===

The Code4Lib journal project aspires to balance a variety of sometimes competing goals. We want to provide quality articles providing useful information and discussion on bringing library technology into the future. We want every article to be a useful intervention into our communities of practice. We value readability over formality, and hope to meet high standards for quality and utility. At the same time we want to ensure an easy process for authors, letting authors share their important work and ideas with as few barriers as we can get away with. The journal is intentionally edited rather than refereed, and we try to contribute editing advice to help authors improve their articles without aggravation. We are committed to the Journal’s free online availability, to increase its visibility and impact in addition to its accessibility. We want the immediacy of a blog, the usefulness of a professional conference, the reliable quality of a good scholarly journal, and the participatory nature of our online communities, all in one easy to read and easy to produce package.

And we are trying to accomplish all of that on a shoestring, with an all volunteer editorial committee sharing management and editorial responsibilities in an informal, open, and productive way as per the Code4Lib ethic. Our Coordinating Editor will rotate with every issue; I’ll be passing the baton to Eric Lease Morgan.

That is, the Code4Lib Journal project is very much like some of the innovative library technology projects many of us work on in our daily lives, balancing competing values and priorities with limited resources. And we’ve tackled this project the same way we do those, with a ‘can do’ spirit and an agile development approach—that is, we’re making it up as we go along.

So how is the experiment working out? We think we’ve got a great first issue. This is due to the great work of our authors, and of the editorial committee. I am not alone among the Editorial Committee in discovering that inventing a journal—even one solely online which is intended to be relatively informal and agile—is more work than I personally expected. All of our authors and editorial staff deserve to be proud of what we’ve produced together through hard work.[5] But ultimately only the judgments and actions of you, our readers, can measure our success. If you think this first issue is evidence of a worthwhile endeavor, you can contribute to its future success.

===How Can You Help?===

You can read our articles, suggest our articles to others, and continue the discussion found in our articles in your blogs and listservs. You can also continue the discussion right here in the journal, as we’ve intentionally enabled comments on all of our articles, taking advantages of the unique affordances for multilateral communication in online publishing and communication. We want every article here to be part of an ongoing conversation towards cooperative innovation among libraries.

You can submit articles to us, and when you run into a colleague with an interesting project or idea, you can suggest that they submit articles to us. We’re happy to accept articles and proposals at any time, although there will of course be cut off dates for particular issues. We welcome anyone interested to participate in the operation of the journal by joining our public discussion list for journal business [6]. At some point in the future, we will solicit more official members of the Editorial Committee too.

We hope that this Journal can be one more contribution to the developing culture of collaboration around library technology, and we welcome you to join in our experiment.

Jonathan Rochkind

Coordinating Editor (for Issue 1),

The Code4Lib Journal

===Code4Lib Issue 1 Editorial Committee===

Carol Bean

Jonathan Brinley

Edward Corrado

Tom Keays

Emily Lynema

Eric Lease Morgan

Ron Peterson

Jonathan Rochkind

Jodi Schneider

Ken Varnum

===Notes===

[1] http://www.code4lib.org

[2] Barrera, Antonio and Chilana, Parmit and Clarke, Kevin and Giarlo, Michael (2007) 2007 Code4Lib Conference Report. Library Hi Tech News 24(6). pp. 4-7. http://eprints.rclis.org/archive/00011670/

[3] Frumkin, Jeremy and Chudnov, Dan. (2006) Code4Lib 2006. Ariadne Issue 47, April 2006. http://www.ariadne.ac.uk/issue47/code4lib-2006-rpt/

[4] Chudnov, Daniel. (2007). code4libcon Shows What a Participatory Conference Looks Like. Computers in Libraries. 27(5), May 2007. pp 37-40

[5] Special thanks to Jonathan Brinley for providing the nuts-and-bolts web management that many of us wanted to leave at our day jobs.

[6] http://groups.google.com/group/c4lj-discuss/ .

JR Draft

2007-12-12T18:15:40Z

Jbrinley:

=DRAFT, please do not circulate=

Code4Lib Journal

Issue 1

Introduction from the Coordinating Editor

This is a critical time for libraries. The social environment around libraries has changed such that libraries need to transform as well. This is specifically a critical time for library technology. Digital services, content and tools have become a part of nearly every aspect of library operations. The “digital library” is already here, and most of us work in one. But these digital libraries of today need to be transformed into the digital libraries of tomorrow to meet radically new needs while carrying forward libraries’ principles of quality provision of information, and bringing libraries’ tradition of collaboration to bear on new challenges. This mission of this journal is to cover “the intersection of libraries, technology, and the future,” providing practical information to help the library community envision and achieve our technological future, one step at a time.

We are at an exciting juncture, with new opportunities to face these serious challenges. The same network and information technology that is responsible for foundational shifts in our environment makes possible tools to face this new environment that would have seemed a futuristic fantasy a decade ago, while the internet provides an ability to collaborate with each other over a distance on solutions, accomplishing through cooperation what limited resources make infeasible individually. Libraries are increasingly realizing that while there are risks to undertaking a transformation of our technology and our organizations, there are even greater risks to maintaining the status quo. In order to take full advantage of these possibilities, libraries are increasingly realizing they need to step up to a leading role in technological innovation towards our users’ needs, alongside our vendors.

===The Code4Lib Community===

One locus of pragmatic innovation has been the Code4Lib community [1]. Inspired in part by the social dynamics of distributed open source projects, Code4Lib is an annual conference and more importantly an informal online social and professional network embodying values of transparency, cooperation, and pragmatic problem solving. This informality and lack of structure is a strength which provides agility and helps make Code4Lib a focal point for collaborative opportunities and sharing of skills and ideas [2,3,4]. But paradoxically, this amorphous informality can make it hard for someone new to the field—or wanting to take a new look at the field—to find a comfortable entry point to the community and the resources it has to offer.

We hope the Code4Lib Journal can embody the successful values of the Code4Lib community, while providing increased access to the collective knowledge and experience held in our various informal professional networks (Code4Lib and others) and local organizations, increasing cross-pollination among library technology innovators.

===This Journal is an Experiment===

The Code4Lib journal project aspires to balance a variety of sometimes competing goals. We want to provide quality articles providing useful information and discussion on bringing library technology into the future. We want every article to be a useful intervention into our communities of practice. We value readability over formality, and hope to meet high standards for quality and utility. At the same time we want to ensure an easy process for authors, letting authors share their important work and ideas with as few barriers as we can get away with. The journal is intentionally edited rather than refereed, and we try to contribute editing advice to help authors improve their articles without aggravation. We are committed to the Journal’s free online availability, to increase its visibility and impact in addition to its accessibility. We want the immediacy of a blog, the usefulness of a professional conference, the reliable quality of a good scholarly journal, and the participatory nature of our online communities, all in one easy to read and easy to produce package.

And we are trying to accomplish all of that on a shoestring, with an all volunteer editorial committee sharing management and editorial responsibilities in an informal, open, and productive way as per the Code4Lib ethic. Our Coordinating Editor will rotate with every issue; I’ll be passing the baton to Eric Lease Morgan.

That is, the Code4Lib Journal project is very much like some of the innovative library technology projects many of us work on in our daily lives, balancing competing values and priorities with limited resources. And we’ve tackled this project the same way we do those, with a ‘can do’ spirit and an agile development approach—that is, we’re making it up as we go along.

So how is the experiment working out? We think we’ve got a great first issue. This is due to the great work of our authors, and of the editorial committee. I am not alone among the Editorial Committee in discovering that inventing a journal—even one solely online which is intended to be relatively informal and agile—is more work than I personally expected. All of our authors and editorial staff deserve to be proud of what we’ve produced together through hard work.[5] But ultimately only the judgments and actions of you, our readers, can measure our success. If you think this first issue is evidence of a worthwhile endeavor, you can contribute to its future success.

===How Can You Help?===

You can read our articles, suggest our articles to others, and continue the discussion found in our articles in your blogs and listservs. You can also continue the discussion right here in the journal, as we’ve intentionally enabled comments on all of our articles, taking advantages of the unique affordances for multilateral communication in online publishing and communication. We want every article here to be part of an ongoing conversation towards cooperative innovation among libraries.

You can submit articles to us, and when you run into a colleague with an interesting project or idea, you can suggest that they submit articles to us. We’re happy to accept articles and proposals at any time, although there will of course be cut off dates for particular issues. We welcome anyone interested to participate in the operation of the journal by joining our public discussion list for journal business [6]. At some point in the future, we will solicit more official members of the Editorial Committee too.

We hope that this Journal can be one more contribution to the developing culture of collaboration around library technology, and we welcome you to join in our experiment.

Jonathan Rochkind

Coordinating Editor (for Issue 1),

The Code4Lib Journal

===Code4Lib Issue 1 Editorial Committee===

Carol Bean

Jonathan Brinley

Edward Corrado

Tom Keays

Emily Lynema

Eric Lease Morgan

Ron Peterson

Jonathan Rochkind

Jodi Schneider

Ken Varnum

===Notes===

[1] http://www.code4lib.org

[2] Barrera, Antonio and Chilana, Parmit and Clarke, Kevin and Giarlo, Michael (2007) 2007 Code4Lib Conference Report. Library Hi Tech News 24(6). pp. 4-7. http://eprints.rclis.org/archive/00011670/

[3] Frumkin, Jeremy and Chudnov, Dan. (2006) Code4Lib 2006. Ariadne Issue 47, April 2006. http://www.ariadne.ac.uk/issue47/code4lib-2006-rpt/

[4] Chudnov, Daniel. (2007). code4libcon Shows What a Participatory Conference Looks Like. Computers in Libraries. 27(5), May 2007. pp 37-40

[5] Special thanks to Jonathan Brinley for providing the nuts-and-bolts web management that many of us wanted to leave at our day jobs.

[6] http://groups.google.com/group/c4lj-discuss/ .

Code4Lib Journal WordPress Customizations

2007-12-04T18:50:23Z

Jbrinley:

==Feeds==
FeedBurner distributes the feed for the Code4Lib Journal. The main feed is at http://feeds.feedburner.com/c4lj. The general comments feed is at http://feeds.feedburner.com/c4lj/comments. Other feeds (e.g., individual articles' comments feeds) are not redirected to FeedBurner.

The "C4LJ Custom the_author()" and "FeedBurner FeedSmith" customize the URLs and the contents of the feeds.

==Theme==

==Permalinks==
Article permalinks use the custom structure <code>/articles/%post_id%</code>.

Category permalinks have the base <code>/issues</code>.

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

[[Category:Code4Lib Journal]]

Code4Lib Journal WordPress Customizations

2007-12-04T18:43:34Z

Jbrinley:

==Feeds==
FeedBurner distributes the feed for the Code4Lib Journal. The main feed is at http://feeds.feedburner.com/c4lj. The general comments feed is at http://feeds.feedburner.com/c4lj/comments. Other feeds (e.g., individual articles' comments feeds) are not redirected to FeedBurner.

The "C4LJ Custom the_author()" and "FeedBurner FeedSmith" customize the URLs and the contents of the feeds.

==Permalinks==
Article permalinks use the custom structure <code>/articles/%post_id%</code>.

Category permalinks have the base <code>/issues</code>.

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

[[Category:Code4Lib Journal]]

Code4Lib Journal WordPress Customizations

2007-12-04T18:37:58Z

Jbrinley:

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

[[Category:Code4Lib Journal]]

Code4Lib Journal WordPress Customizations

2007-12-04T18:37:23Z

Jbrinley: New page: ==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 cop...

Code4Lib Journal

2007-12-04T18:11:54Z

Jbrinley:

http://journal.code4lib.org/

[[COinS (layman's description)]]

==WordPress==
[[Code4Lib Journal WordPress Input Guidelines]]

[[Code4Lib Journal WordPress Customizations]]

[[Category: Code4Lib Journal]]

Code4Lib Journal WordPress Input Guidelines

2007-12-04T18:10:06Z

Jbrinley: /* Code Highlighting */

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.ibilio.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/
* To enter COinS, one 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.
* You can also use jrochkind's umlaut coins generator:
** books: http://findit.library.jhu.edu/search/books?umlaut.display_coins=true
** journals: http://findit.library.jhu.edu:3000/search/journals?umlaut.display_coins=true
* 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". 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]]

Code4Lib Journal WordPress Input Guidelines

2007-12-04T18:07:14Z

Jbrinley: /* Code */

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

====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/
* To enter COinS, one 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.
* You can also use jrochkind's umlaut coins generator:
** books: http://findit.library.jhu.edu/search/books?umlaut.display_coins=true
** journals: http://findit.library.jhu.edu:3000/search/journals?umlaut.display_coins=true
* 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". 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]]

Code4Lib Journal WordPress Input Guidelines

2007-11-30T14:25:08Z

Jbrinley: /* Author Information */

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.ibilio.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 <pre> tags. jbrinley has also installed a neat code syntax highlighting plug-in. The jury is still out on if we like it. If we do like it, then to use it... directions needed.

====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.
* To enter COinS, one 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.
* You can also use jrochkind's umlaut coins generator:
** books: http://findit.library.jhu.edu/search/books?umlaut.display_coins=true
** journals: http://findit.library.jhu.edu:3000/search/journals?umlaut.display_coins=true
* 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". 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]]

Code4Lib Journal WordPress Input Guidelines

2007-11-27T18:31:34Z

Jbrinley: /* Categories/Tags */

Code4Lib Journal WordPress Input Guidelines

2007-11-20T15:41:24Z

Jbrinley: /* Author Information */

Code4Lib Journal WordPress Input Guidelines

2007-11-19T21:20:16Z

Jbrinley: /* Citations */

Code4Lib Journal WordPress Input Guidelines

2007-11-19T17:44:42Z

Jbrinley: /* Article Content */