Code4Lib - User contributions [en]

Code4Lib Journal and EBSCO

2018-03-31T14:06:25Z

Bean:

Code4Lib Journal has signed an agreement with EBSCO whereby they will index the content of our issues in the [http://www.libraryresearch.com/ LISTA] database.

In March 2018, the Code4Lib Community voted to engage CLIR as its fiscal agent. The signed MOU includes provisions for the Journal to be included in their sponsorship and receive royalty funds accrued at EBSCO on behalf of the Journal. Carol Bean initiated negotiations on renewing the contract with EBSCO, with input from the Journal's Editorial Committee. Relevant discussions can be found in these c4lj-articles threads:
*https://groups.google.com/forum/?hl=en#!topic/c4lj-articles/K0HvLkS_K3k
*https://groups.google.com/forum/?hl=en#!topic/c4lj-articles/hcg0V48E0gI
*https://groups.google.com/forum/?hl=en#!topic/c4lj-articles/X6AkljgsDxE

CLIR agreed to sign the agreement on the Journal's behalf at the Editorial Committee's direction, and to be the contact point with EBSCO for the agreement. The final discussion thread and signed agreement can be found in this thread in the c4lj-articles group list:
https://groups.google.com/forum/?hl=en#!topic/c4lj-articles/886b1Qtca2A

Funds due the Journal from EBSCO will be deposited with CLIR, who will administer them at the direction of the Editorial Committee. The primary contact for the Editorial Committee will be whoever is the Coordinating Editor, although communication can and may be through other members of the E.C. (as listed on the [http://journal.code4lib.org/editorial-committee Journal Editorial Committee Page])

Decisions on using accumulated funds will be made by the Editorial Committee and communicated to CLIR through either the Coordinating Editor or another designated contact within the E.C.

The initial agreement can be found as an attached PDF in this posting on c4lj-articles.
* http://groups.google.com/group/c4lj-articles/browse_frm/thread/a43aa80541116bc8

They agreed to get the HTML from us directly:
* http://groups.google.com/group/c4lj-articles/browse_frm/thread/1b84482ff089aee5/

(3/12/2010) There's a problem with indexing; only Issue 7 has actually been indexed. Jodi sent a follow up to EBSCO about this problem, based on this email from their data group.
* http://groups.google.com/group/c4lj-articles/browse_frm/thread/e79ab9442abe6555/

Follow-up from EBSCO
* http://groups.google.com/group/c4lj-articles/browse_frm/thread/9a3c670463aab78

[[Category: Code4Lib Journal]]

Code4Lib Journal and EBSCO

2018-03-27T20:24:18Z

Bean:

Code4Lib Journal has signed an agreement with EBSCO whereby they will index the content of our issues in the [http://www.libraryresearch.com/ LISTA] database.

In March 2018, the Code4Lib Community voted to engage CLIR as its fiscal agent. The signed MOU includes provisions for the Journal to be included in their sponsorship and receive royalty funds accrued at EBSCO on behalf of the Journal. Carol Bean initiated negotiations on renewing the contract with EBSCO, with input from the Journal's Editorial Committee. Relevant discussions can be found in these c4lj-articles threads:
*https://groups.google.com/forum/?hl=en#!topic/c4lj-articles/K0HvLkS_K3k
*https://groups.google.com/forum/?hl=en#!topic/c4lj-articles/hcg0V48E0gI
*https://groups.google.com/forum/?hl=en#!topic/c4lj-articles/X6AkljgsDxE

CLIR agreed to sign the agreement on the Journal's behalf at the Editorial Committee's direction, and to be the contact point with EBSCO for the agreement. The final discussion thread and signed agreement can be found in this thread in the c4lj-articles group list:
https://groups.google.com/forum/?hl=en#!topic/c4lj-articles/886b1Qtca2A

Funds due the Journal from EBSCO will be deposited with CLIR, who will administer them at the direction of the Editorial Committee. The primary contact for the Editorial Committee will be whoever is the Coordinating Editor, although communication can and may be through other members of the E.C. (as listed on the [http://journal.code4lib.org/editorial-committee Journal Editorial Committee Page])

Decisions on using accumulated funds will be made by the Editorial Committee and communicated to CLIR through either the Coordinating Editor or another designated contact within the E.C.

The initial agreement can be found as an attached PDF in this posting on c4lj-articles.
* http://groups.google.com/group/c4lj-articles/browse_frm/thread/a43aa80541116bc8

They agreed to get the HTML from us directly:
* http://groups.google.com/group/c4lj-articles/browse_frm/thread/1b84482ff089aee5/

Currently (3/12/2010) there's a problem with indexing; only Issue 7 has actually been indexed. Jodi sent a follow up to EBSCO about this problem, based on this email from their data group.
* http://groups.google.com/group/c4lj-articles/browse_frm/thread/e79ab9442abe6555/

Follow-up from EBSCO
* http://groups.google.com/group/c4lj-articles/browse_frm/thread/9a3c670463aab78

[[Category: Code4Lib Journal]]

Code4Lib Journal and EBSCO

2018-03-27T20:23:45Z

Bean: Documenting changes in status and process for the updated EBSCO agreement

Code4Lib Journal has signed an agreement with EBSCO whereby they will index the content of our issues in the [http://www.libraryresearch.com/ LISTA] database.

In March 2018, the Code4Lib Community voted to engage CLIR as its fiscal agent. The signed MOU includes provisions for the Journal to be included in their sponsorship and receive royalty funds accrued at EBSCO on behalf of the Journal. Carol Bean initiated negotiations on renewing the contract with EBSCO, with input from the Journal's Editorial Committee. Relevant discussions can be found in these c4lj-articles threads:
*https://groups.google.com/forum/?hl=en#!topic/c4lj-articles/K0HvLkS_K3k
*https://groups.google.com/forum/?hl=en#!topic/c4lj-articles/hcg0V48E0gI
https://groups.google.com/forum/?hl=en#!topic/c4lj-articles/X6AkljgsDxE

CLIR agreed to sign the agreement on the Journal's behalf at the Editorial Committee's direction, and to be the contact point with EBSCO for the agreement. The final discussion thread and signed agreement can be found in this thread in the c4lj-articles group list:
https://groups.google.com/forum/?hl=en#!topic/c4lj-articles/886b1Qtca2A

Funds due the Journal from EBSCO will be deposited with CLIR, who will administer them at the direction of the Editorial Committee. The primary contact for the Editorial Committee will be whoever is the Coordinating Editor, although communication can and may be through other members of the E.C. (as listed on the [http://journal.code4lib.org/editorial-committee Journal Editorial Committee Page])

Decisions on using accumulated funds will be made by the Editorial Committee and communicated to CLIR through either the Coordinating Editor or another designated contact within the E.C.

The initial agreement can be found as an attached PDF in this posting on c4lj-articles.
* http://groups.google.com/group/c4lj-articles/browse_frm/thread/a43aa80541116bc8

They agreed to get the HTML from us directly:
* http://groups.google.com/group/c4lj-articles/browse_frm/thread/1b84482ff089aee5/

Currently (3/12/2010) there's a problem with indexing; only Issue 7 has actually been indexed. Jodi sent a follow up to EBSCO about this problem, based on this email from their data group.
* http://groups.google.com/group/c4lj-articles/browse_frm/thread/e79ab9442abe6555/

Follow-up from EBSCO
* http://groups.google.com/group/c4lj-articles/browse_frm/thread/9a3c670463aab78

[[Category: Code4Lib Journal]]

Code4Lib Journal WordPress Input Guidelines

2018-01-23T17:29:46Z

Bean: minor edit to fix the url to be used in WP posts for images

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-admin/). If you don't have a WordPress editor login and need one, talk to our web admin (Tom Keays).

==Proofs for Authors==
A read-only login that is shared with authors can be found in the 'Administrivia' tab/worksheet of our Google Docs article tracking spreadsheet.

==Title==
Title, including the subtitle, goes in the "Title" field.

Article titles are in Title Case -- all major words capitalized. The title is followed by an abstract, which will be pulled from the excerpt section lower on the post page, and byline of the form "by Author" or "by Author 1, Author 2, and Author 3".

==Article Content==
The body of the article goes in the "Post" field. Use HTML markup appropriately and semantically, ''e.g.'', <code></code> for emphasized text, <code></code> for strongly emphasized text, <code><blockquote></code> when quoting blocks of text. Avoid such monstrosities as <code></code> and <code><blink></code>.

===Headings===
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,
<code><h3></code> for sub-sections, <code><h4></code> if you need a lower level. <code><h2></code> are in "Title Case" -- all words capitalized, short words (the, a, in, up, over, about) should not be. <code><h3></code> and <code><h4></code> are in "Sentence case" -- only the first word is capitalized. Any header from second- to sixth-level may be used as appropriate.

===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.
Alternatively, use the [http://www.textfixer.com/html/convert-word-to-html.php Word DOC to HTML converter].

===Figures & Tables===
Figures and tables are centered, placed inside a P or DIV with class of "caption". In general, we bold the figure / table label using the strong tag.

For example:
<pre>

<img src = "....">
Figure X. How to Caption an Image.


<div class = "caption">
Table X. How to Caption a Table.
<table>
<tr>...</tr>
</table>
</div>
</pre>
Captions for figures appear beneath the figure, centered, with "Figure X:" in bold, the descriptive text in sentence case, plain text.

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

===Images and Attached Content===
In-line images should be no wider than 500px. See above section for captioning and image

'''Uploading files manually'''

To upload images or other attached media / files, you will need to upload the content to our ibiblio host site manually.

To do that, sftp to login.ibiblio.org. See the Administrivia tab in the shared "C4LJ Article Tracking" doc for the username and password.

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. This sort of url will be used in the "<img src>" tag:
/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. (see below)

'''Uploading media via WordPress'''

Before uploading files to WordPress, you will need to change permissions on the directory where you are putting the files.
# Login to c4ljeditor@login.ibiblio.org. Ask Tom Keays for the password for the c4ljeditor account (or see this [http://groups.google.com/group/c4lj-articles/msg/fad004416f12ac25 post] on c4lj-articles).
# Change the directory to /public/vhost/c/c4lj/html/wp-content/uploads/
# WordPress tries to write the files to /public/vhost/c/c4lj/html/wp-content/uploads/[current year]/[current month]. If the current year or month directory does not yet exist, create them, "mkdir [current year]" or mkdir "[current month]" in the appropriate directory. Creating the directory while logged in makes the owner and group of the directory c4ljeditor and c4lj respectively. Wordpress will create the directories as nobody/nobody.
# Change the permissions on the [current month] directory from 755 to 777, "chmod 777 [current month]".
# In the WordPress editor, click the "Add an Image" button.
# Browse to and select your image/file.
# Click the Upload button.
# File in the Alternate text and Caption fields.
# Select the size of the image you want to display in the article.
# Click "Insert into Post".
# On the ibiblio.org server, change the permissions on the current month's directory back to 775, "chmod 775 [current month]"

==== Video ====

We haven't had too much video, but we just had one (a screencast). The option we used was hosting on archive.org. Upload the video, click on the IA 'pillars' icon on the resulting video on the archive.org page to get an 'iframe' embed code, which works fine in our wordpress html source, and I believe the archive.org infrastructure will take care of translating the video to multiple formats and delivering in the proper format for a given browser. Very convenient.

Include a visible link to the archive.org URL for the individual video page as a caption, so printed or otherwise captured versions of the article will always have that link.

You don't need to use archive.org if you or we figure out a better way, it's just one option that worked very conveniently so far.

===Code===

If code is attached as a file, follow the directions above for attached images, except:

* If there is not a folder for the author, create it, according to the guidelines above for images)
* Create a subfolder under the author's folder for "code". Insert code files here
* In the article link to the files using the path format http://path-to-the-server/media/issueNumber/authorname/code/filename (e.g., http://journal.code4lib.org/media/issue1/smith/code/something.pl)

Put all inline 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 extension, so if you an "s" on the end of .php files, it does syntax highlighting for you, e.g.:
<filename>.phps

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

If the language parameter is not set, it will default to "text" (no syntax highlighting). Supported languages include <tt>cpp, c, c++, c#, c-sharp, csharp, css, delphi, java, js, jscript, javascript, pascal, php, py, python, rb, ruby, rails, ror, sql, vb, vb.net, xml, html, xhtml, and xslt</tt>. Pretty much everything except <tt>perl</tt>. For a full list consult: http://en.support.wordpress.com/code/posting-source-code/

Note: do not surround code with <tt><pre></tt> tags, as the <tt>[sourcecode]</tt> tag itself will generate the necessary HTML.

For more subtleties of code formatting, see this gist from editor Péter Király https://gist.github.com/pkiraly/c48193925ad3806c31ef010b58e8600f

====Ampersand Issues====
We've had some problems with ampersand handling in the sourcecode sections. If you notice extra amp;s in your article, such as "&amp;amp;" and "&amp;amp;amp;", and you're comfortable using only the HTML editor for article entry, try checking the "Disable the visual editor when writing" box on your profile page in the admin.

==Abstract==

Abstracts should be placed in the Excerpt box, displayed a little ways below the "Post" field. If you do not see the Excerpt box, look under "Screen Options" in the top right of the page. Selecting the down arrow will display fields to show on the screen. Make sure that 'Excerpt' is selected. This will display the Excerpt (abstract) input box on the page.

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.

It appears the COinS generator at http://generator.ocoins.info/ is no longer in service. An alternative is [https://www.zotero.org/download/ Zotero's stand alone citation software].
After creating a citation, simply right click the citation and choose export / format: coins.
* Paste the output provided at the end of the reference in HTML. You will need to delete the line breaks inserted into the output created by the generator for it to work properly.
* 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. For an example see the [http://journal.code4lib.org/articles/7922 References section of a published article including coins].

===Endnotes style and HTML coding===
* Endnote number in text: The number is the link which appears in square brackets. Square brackets themselves are not part of the link. HTML coding for the text: '''[<a id="ref1" href="#note1">1</a>]'''

* The link should work both ways. So, the endnote will link back to the text. HTML coding for the endnote: '''[<a id="note1" href="#ref1">1</a>]'''

==Author Information==

Start off each article with a paragraph stating the name(s) of the author(s). Something simple like "By Jonathan Rochkind". If desired, the author's name can be a link to something appropriate.

End each article with a second-level header that says "About the Author(s)", with class="abouttheauthor" set. Then give a short paragraph about each author. Italicize the author's name when it is first used (for example, "''Foo Bar'' is a librarian at..."). 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==
Posts will have "Uncagetorized" checked by default. Uncheck that box, and check the box next to the current issue, which will be a subcategory of "Issues." Do not check the "Issues" category. We generally do not add tags, except for Conference reviews

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

# Let everyone on the c4lj-articles list know you are getting ready to publish (so they can save and close any open articles).
# Log in to WordPress
# Make sure that all articles for the issue have the correct issue category selected and have been set to 'Pending Review'. Make sure that the "Uncategorized" and "Issues" categories are unchecked (only the specific issue should be selected).
# Sanity check: count the number of posts which should appear in the publish list
# Click on Posts -> Issues (on the left side)
# Click on "Publish" for the issue you'd like to publish.
## You'll get a list of every "Pending Review" article in that issue. Make sure the number of articles in the list matches your previous count. Don't see all the articles you think you should see? They could be still in Draft status, or not in the correct Issue category, or still have "Uncategorized" selected, or someone may still have it in edit mode. Go back to the posts list and make any necessary changes, and start from #5 again.
# 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).
## 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.
# Click on Posts -> Categories (on the left side)
# Make sure all three fields for the current issue are filled in and correct:
## The human-readable name of the issue goes into the Name field -- e.g., "Issue 15".
## The date of publication goes into the Description field -- e.g., "2011-10-31".
## The URL name goes into the Slug field -- e.g., "issue15" would give the URL of the issue, http://journal.code4lib.org/issues/issue15
# 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.
# Go to the Journal front page; check the number of articles is correct (again) and that they are in the right order. If there is a problem, go back to the admin interface, click on Posts -> Issues and click Unpublish for the issue. Make whatever corrections are needed and proceed from #5 again.
# Once the issue is finally published, go to [[Code4Lib_Journal_Entries_in_Directory_of_Open_Access_Journals]] and follow the directions to upload the issue metadata to DOAJ.
# Submit URLS to Internet Archives for harvest ([https://gist.github.com/ruthtillman/fa7562989f299e4904c7fb0448d1fc83#file-waybacksubmit-py Wayback Submission Script] )
# Send out announcements (see [[Code4Lib_Journal_Publicity_Venues]])
# Update [http://journal.code4lib.org/editorial-committee#coordinating Coordinating Editor] on the Editorial Committee page to state the name of the editor for the next issue.

==Corrections==
See [http://groups.google.com/group/c4lj-articles/browse_thread/thread/8eaabcff2d9c000d/a0aeeb9367fcea5f?lnk=gst&q=errata#a0aeeb9367fcea5f|the editors' list] for how to make corrections. Generally, use an Errata or Correction section at the end with information about the change that was made and have the actual text link down to that section. See also [[Code4Lib_Corrections]]

[[Category:Code4Lib Journal]]

Code4Lib Journal Deadlines

2017-07-25T16:44:50Z

Bean: /* Deadlines for Issues */

''See also [[Code4Lib Journal Voting]]''

== Formula for calculating deadlines ==

A rough guideline based on recent issues:

{| border="1" cellpadding="2" cellspacing="0"
|-
! Weeks before
! Task
! Day offset
! On
|-
| style="text-align:right" | '''-18'''
| Call for proposals
| style="text-align:right" | -126
| Monday
|-
| style="text-align:right" | '''-14'''
| Proposals due
| style="text-align:right" | -94
| Friday
|-
| style="text-align:right" | '''-13'''
| Publication of previous issue
| style="text-align:right" | -91
| Monday
|-
| style="text-align:right" | '''-13'''
| Finish voting on proposals; notify authors
| style="text-align:right" | -87
| Friday
|-
| style="text-align:right" | '''-9'''
| First draft due
| style="text-align:right" | -59
| Friday
|-
| style="text-align:right" | '''-5'''
| Second draft due
| style="text-align:right" | -31
| Friday
|-
| style="text-align:right" | '''0'''
| Publication
| style="text-align:right" | 0
| Monday
|}

'''Note:''' Week numbers assume week begins on Monday.

'''See also:''' [[Code4Lib_Journal_Email_Templates]] (formerly at [http://groups.google.com/group/c4lj-articles/web/templates-for-email-responses Templates for Email Responses])

== Deadlines for Issues ==
Editors: see also http://tomkeays.com/library/c4ljpubdate/ for Tom's calculator

===Thirty-ninth issue===
(tentative)
*Call for proposals: Monday, September 25, 2017
*Second call for proposals: Monday, October 16, 2017 (if necessary)
*Proposals due: Friday, October 27, 2017
*Proposals accepted: Friday, November 3, 2017
*First draft due: Friday, December 1, 2017
*Second draft due: Friday, December 29, 2017
*Publication date: Monday, January 29, 2018

===Thirty-eighth issue===
Coordinating Editor: Carol Bean
*Call for proposals: Monday, June 12, 2017
*Second call for proposals: Monday, July 3, 2017 (if necessary)
*Proposals due: Friday, July 14, 2017
*Proposals accepted: Friday, July 21, 2017
*First draft due: Friday, August 18, 2017
*Second draft due: Friday, September 15, 2017
*Publication date: Monday, October 16, 2017

===Thirty-seventh issue===
Coordinating Editor: Sara Amato
*Call for proposals: Monday, March 13, 2017
*Second call for proposals: Monday, April 3, 2017 (if necessary)
*Proposals due: Friday, April 14, 2017
*Proposals accepted: Friday, April 21, 2017
*First draft due: Friday, May 19, 2017
*Second draft due: Friday, June 16, 2017
*Publication date: Monday, July 17, 2017

===Thirty-sixth issue===
Coordinating Editor: Peter Murray
*Call for proposals: Thursday, December 15, 2016
*Second call for proposals: Thursday, January 5, 2017 (if necessary)
*Proposals due: Tuesday, January 17, 2017
*Proposals accepted: Monday, January 23, 2017
*First draft due: Monday, February 20, 2017
*Second draft due: Monday, March 20, 2017
*Publication date: Monday, April 17, 2017

===Thirty-fifth issue===

Coordinating Editor: Ruth Kitchin Tillman

* Call for proposals: Monday, September 26, 2016
* Second call for proposals: Monday, October 17, 2016 (if necessary)
* Proposals due: Friday, October 28, 2016
* Proposals accepted: Friday, November 4, 2016
* First draft due: Friday, December 2, 2016
* Second draft due: Friday, December 30, 2016
* Publication date: Monday, January 30, 2017

===Thirty-fourth issue===
Coordinating Editor: Andrew Darby

* Call for proposals: Monday, June 20, 2016
* Second call for proposals: Monday, July 11, 2016 (if necessary)
* Proposals due: Friday, July 22, 2016
* Proposals accepted: Friday, July 29, 2016
* First draft due: Friday, August 26, 2016
* Second draft due: Friday, September 23, 2016
* Publication date: Monday, October 24, 2016

===Thirty-third issue===
Coordinating Editor: Ron Peterson

* Call for proposals: Monday, March 14, 2016
* Second call for proposals: Monday, April 4, 2016 (if necessary)
* Proposals due: Friday, April 15, 2016
* Proposals accepted: Friday, April 29, 2016
* First draft due: Friday, May 20, 2016
* Second draft due: Friday, June 17, 2016
* Publication date: Monday, July 18, 2016

===Thirty-second issue===
Coordinating Editor: Meghan Finch
* Call for proposals: Monday, December 14, 2015
* Second call for proposals: Monday, January 4, 2016 (if necessary)
* Proposals due: Friday, January 15, 2016
* Proposals accepted: Friday, January 22, 2016
* First draft due: Friday, February 19, 2016
* Second draft due: Friday, March 18, 2016
* Publication date: Monday, April 25, 2016

===Thirty-first issue===
Coordinating Editor: Terry Reese
* Call for proposals: Monday, September 21, 2015
* Second call for proposals: Thursday, October 8, 2015 (if necessary)
* Proposals due: Friday, October 23, 2015
* Proposals accepted: Friday, October 30, 2015
* First draft due: Monday, November 23, 2015
* Second draft due: Monday, December 21, 2015
* Publication date: Monday, January 25, 2016

===Thirtieth issue===
Coordinating editor for issue #30: Carol Bean

* Call for proposals: Thursday, June 11, 2015
* Second call for proposals: Thursday, July 2, 2015 (if necessary)
* Proposals due: Monday, July 13, 2015
* Proposals accepted: Monday, July 20, 2015
* First draft due: Monday, August 17, 2015
* Second draft due: Monday, September 14, 2015
* Publication date: Monday, October 19, 2015

===Twenty-ninth issue===
Coordinating editor for issue #29: Sara Amato

* Call for proposals: Wednesday, March 11, 2015
* Second call for proposals: Wednesday, April 1, 2015 (if necessary)
* Proposals due: Friday, April 10, 2015
* Proposals accepted: Monday, April 20, 2015
* First draft due: Monday, May 18, 2015
* Second draft due: Monday, June 15, 2015
* Publication date: Monday, July 13, 2015

===Twenty-eighth issue===
Coordinating editor for issue #28: Heidi Dowding

Special issue on diversity in library technology.

* Call for proposals: Wednesday, December 10, 2014
* Second call for proposals: Monday, January 5, 2015 (if necessary, adjusted from 31-Dec-2014)
* Proposals due: Monday, January 12, 2015
* Proposals accepted: Monday, January 19, 2015
* First draft due: Monday, February 16, 2015
* Second draft due: Monday, March 16, 2015
* Publication date: Wednesday, April 15, 2015

===Twenty-seventh issue===
Coordinating editor for issue #27: Terry Reese

*Call for proposals: Monday, September 27, 2014
*Second call for proposals: Monday, October 6, 2014 (if necessary)
*Proposals due: Friday, October 24, 2014
*Proposals accepted: Friday, October 31, 2014
*First draft due: Friday, November 21, 2014
*Second draft due: Friday, December 19, 2014
*Publication date: Monday, January 19, 2015

===Twenty-sixth issue===
Coordinating editor for issue #26: Kelley McGrath

*Call for proposals: Monday, June 9, 2014
*Second call for proposals: Monday, June 30, 2014 (if necessary)
*Proposals due: Friday, July 11, 2014
*Proposals accepted: Friday, July 18, 2014
*First draft due: Friday, August 15, 2014
*Second draft due: Friday, September 12, 2014
*Publication date: Monday, October 20, 2014

===Twenty-fifth issue===
Coordinating editor for issue #25: Dan Scott

*Call for proposals: Monday, March 10, 2014
*Second call for proposals: Monday, March 31, 2014 (if necessary)
*Proposals due: Friday, April 11, 2014
*Proposals accepted: Friday, April 18, 2014
*First draft due: Friday, May 16, 2014
*Second draft due: Friday, June 13, 2014
*Publication date: Monday, July 14, 2014

===Twenty-fourth issue===
Coordinating editor for issue #24: Ron Peterson

*Call for proposals: Monday, December 9, 2013
*Call for proposals #2: Monday, December 30, 2013 (if necessary)
*Proposals due: Friday, January 10, 2014
*Proposals accepted: Friday, January 17, 2014
*First draft due: Friday, February 14, 2014
*Second draft due: Friday, March 14, 2014
*Publication date: Monday, April 14, 2014

===Twenty-third issue===
Coordinating editor for issue #23: Shawn Averkamp
* Call for proposals: Monday, September 9, 2013
* Call for proposals #2: Monday September 30, 2013 (if necessary)
* Proposals due: Friday, October 11, 2013
* Proposals accepted: Friday, October 18, 2013
* First draft due: Friday, November 15, 2013
* Second draft due: Friday, December 13, 2013
* Publication date: Monday, January 13, 2014

===Twenty-second issue===
Coordinating editor for issue #22: Sara Amato
* Call for proposals: Monday, June 10, 2013
* Call for proposals #2: July 5, 2013 (if necessary)
* Proposals due: Friday, July 12, 2013
* Proposals accepted: Friday, July 19, 2013
* First draft due: Friday, August 16, 2013
* Second draft due: Friday, September 13, 2013
* Publication date: Monday, October 14, 2013

===Twenty-first issue===
Coordinating editor for issue #21: Terry Reese
* Call for proposals: Monday, March 11, 2013
* Call for proposals #2: Monday, April 1, 2013
* Proposals due: Friday, April 12, 2013
* Proposals accepted: Friday, April 19, 2013
* First draft due: Friday, May 17, 2013
* Second draft due: Friday, June 14, 2013
* Publication date: Monday, July 15, 2013

===Twentieth issue===
Coordinating editor for issue #20: [[User:DataGazetteer|Peter Murray]]
* Call for proposals:     Monday, December 10, 2012
* Call for proposals #2: Monday, January 7, 2013 (if necessary)
* Proposals due:          Friday, January 18, 2013
* Proposals accepted:     Friday, January 25, 2013
* First draft due:        Friday, February 22, 2013
* Second draft due:       Friday, March 22, 2013
* Publication date:       Monday, April 15, 2013

===Nineteenth issue===
Coordinating editor for issue #19: Andrew Darby
* Call for proposals: Monday, September 10, 2012
* Proposals due: Friday, October 12, 2012
* Proposals accepted: Friday, October 19, 2012
* First draft due: Friday, November 16, 2012
* Second draft due: Friday, December 14, 2012
* Publication date: Monday, January 14, 2013

===Eighteenth issue===
Coordinating editor for issue #18: Ron Peterson
* Call for proposals: Monday, May 28, 2012
* Proposals due: Friday, June 29, 2012
* Proposals accepted: Friday, July 6, 2012
* First draft due: Friday, August 3, 2012
* Second draft due: Friday, August 31, 2012
* Publication date: Monday, October 1, 2012

===Seventeenth issue===
Coordinating editor for issue #17: Tim Lepczyk
* Call for proposals: Wednesday, February 8, 2012
* Proposals due: Tuesday, February 28, 2012
* Proposals accepted: Tuesday, March 6, 2012
* First draft due: Tuesday, April 3, 2012
* Second draft due: Tuesday, May 1, 2012
* Publication date: Friday, June 1, 2012

===Sixteenth issue===
Coordinating editor for issue #16: Carol Bean
* Call for proposals: Monday, September 26, 2011
* Proposals due: Friday, October 28, 2011
* Proposals accepted: Friday, November 4, 2011
* First draft due: Friday, December 2, 2011
* Second draft due: Friday, December 30, 2011
* Publication date: Monday, January 30, 2012

===Fifteenth issue===
Coordinating editor for issue #15: Tod Olson
* Call for proposals: Monday, June 27, 2011
* Proposals due: Friday, July 29, 2011
* Proposals accepted: Friday, August 5, 2011
* First draft due: Friday, September 2, 2011
* Second draft due: Friday, September 30, 2011
* Publication date: Monday, October 31, 2011

===Fourteenth issue===

* Call for proposals: Monday, March 21, 2011
* Proposals due: Friday, April 22, 2011
* Proposals accepted: Friday, April 29, 2011
* First draft due: Friday, May 27, 2011
* Second draft due: Friday, June 24, 2011
* Publication date: Monday, July 25, 2011

===Thirteenth issue===

* Call for proposals: Monday, December 6, 2010
* Proposals due: Friday, January 7, 2011
* Proposals accepted: Friday, January 14, 2011
* First draft due: Friday, February 11, 2011
* Second draft due: Friday, March 11, 2011
* Publication date: Monday, April 11, 2011

===Twelfth issue===

* Call for proposals: Monday, August 16, 2010
* Proposals due: Friday, September 17, 2010
* Proposals accepted: Friday, September 24, 2010
* First draft due: Friday, October 22, 2010
* Second draft due: Friday, November 19, 2010
* Publication date: Monday, December 20, 2010

===Eleventh issue===

* Call for proposals: Monday, May 17, 2010
* Proposals due: Friday, June 18, 2010
* Proposals accepted: Friday, June 25, 2010
* First draft due: Friday, July 23, 2010
* Second draft due: Friday, August 20, 2010
* Publication date: Monday, September 20, 2010

=== Tenth issue ===

* Call for proposals: Monday, February 15, 2010
* Proposals due: Friday, March 19, 2010
* Proposals accepted: Friday, March 26, 2010
* First draft due: Friday, April 23, 2010
* Second draft due: Friday, May 21, 2010
* Publication date: Monday, June 21, 2010

=== Ninth issue ===

* Monday, November 9, 2009 -- Call for proposals
* Friday, December 11, 2009 -- Proposals due
* Friday, December 18, 2009 -- Finish voting on proposals, notify authors
* Friday, January 15, 2010 -- First draft due
* Friday, February 12, 2010 -- Second draft due
* Monday, March 15, 2010 -- Publication date

=== Eighth issue ===

* Monday, July 27 -- call for proposals
* Friday, August 14 -- proposals due
* Friday, August 21 -- finish voting on proposals; notify authors
* Friday, September 25 -- first draft due
* Friday, October 23 -- second draft due
* Monday, November 23 -- publication

=== Seventh issue ===

* Monday, February 16 -- call for proposals
* Friday, March 20 -- proposals due
* Monday, March 30 -- publication of issue 6
* Friday, March 27 -- finish voting on proposals; notify authors
* Friday, April 24 -- first draft due
* Friday, May 22 -- second draft due
* Monday, June 22 -- publication

=== Sixth issue ===

* Monday, November 10 -- call for proposals
* Friday, December 12 -- proposals due
* Monday, December 15 -- publication of issue 5
* Friday, December 19 -- finish voting on proposals; notify authors
* Friday, January 23 -- first draft due
* Friday, February 20 -- second draft due
* Monday, March 30 -- publication (originally scheduled for March 23)

=== Fifth issue ===

* Monday, August 18 -- call for proposals
* Friday, September 12 -- proposals due
* Friday, September 19 -- finish voting on proposals; notify authors
* Monday, September 22 -- issue 4 published
* Friday, October 17 -- first draft due
* Friday, November 14 -- second draft due
* Monday, December 15 -- publication

=== Fourth issue ===

* Friday, May 16 -- call for proposals
* Friday, June 20 -- extended proposal deadline (originally 6/13, before issue 3 is published)
* Friday, July 18 -- first draft due
* Friday, August 15 -- second draft due
* Monday, September 22 -- publication

=== Third issue ===

* Wednesday February 13th -- call for proposals
* Friday March 14th -- proposals due (after con, before issue 2)
* Friday April 25 -- first draft due
* Saturday June 21 -- publication (tentative)

=== Second issue ===

* Friday November 9th -- call for proposals
* Friday January 11 -- article draft deadline (or Thurs Jan 21, from EM)
* Thursday February 21 -- revisions/second draft deadline
* Friday March 21 -- publication (tentative)

=== First issue ===

* Friday August 31st -- call for proposals
* Friday October 12th -- article draft deadline
* Monday December 17th -- publication

[[Category: Code4Lib Journal]]

Code4Lib Journal Publicity Venues

2017-07-07T20:46:37Z

Bean: /* Distributing Call for Submissions */

== Distributing Call for Submissions ==

* [https://code4lib.org/ Code4Lib website]
* [http://journal.code4lib.org/call-for-submissions c4lj Journal website]
* [https://groups.google.com/forum/?hl=en#!forum/c4lj-discuss c4lj-discuss group]
* [http://listserv.syr.edu/archives/autocat.html AUTOCAT] autocat@listserv.syr.edu
* [https://lists.clir.org/cgi-bin/wa?A0=CODE4LIB Code4Lib] code4lib@lists.clir.org
* [http://listserv.uic.edu/htbin/wa?A0=drupal4lib Drupal4Lib] drupal4lib@listserv.uic.edu
* [http://lists.ala.org/wws/arc/lita-l LITA-L] lita-l@lists.ala.org
* [http://metadatalibrarians.monarchos.com/ Metadatalibrarians] metadatalibrarians@lists.monarchos.com
* [https://listserv.uc.edu/scripts/wa.exe?A0=WEB4LIB Web4Lib] web4lib@listserv.uc.edu
* [http://home.olemiss.edu/~noe/llfaq.html Law-Lib] law-lib@ucdavis.edu
* [http://www.mlanet.org/discussion/medlibl.html MedLib] medlib-l@list.uvm.edu
* [http://infoserv.inist.fr/wwsympa.fcgi/info/diglib IFLA DigLib] diglib@infoserv.inist.fr
* [http://mail.asis.org/mailman/listinfo/asis-l ASIS] asis-l@asis.org
* [http://www.inetbib.de/listenarchiv/ InetBib] inetbib@ub.uni-dortmund.de
* [https://listserv.niif.hu/mailman/listinfo/katalist Katalist] katalist@listserv.niif.hu

* <s> [https://listserv.nd.edu/cgi-bin/wa?A0=NGC4LIB NGC4Lib] ngc4lib@listserv.nd.edu</s>
* <s>[http://mail.archive.org/pipermail/ol-lib/ Open Library] ol-lib@archive.org</s>
* <s>[http://lists.sourceforge.net/lists/listinfo/oss4lib-discuss OSS4Lib] oss4lib-discuss@lists.sourceforge.net</s> (no longer active)
* <s>[https://listserv.nd.edu/cgi-bin/wa?A0=Usability4Lib Usability4Lib] usability4lib@listserv.nd.edu</s> (listerv shut down)
* <s>[https://listserv.nd.edu/cgi-bin/wa?A0=XML4LIB XML4Lib] xml4lib@listserv.nd.edu</s> (listserv shut down)
Web Sites

* <s>[http://liswire.com/ LISWire]. Go to the "[http://liswire.com/node/5 Submit a Release]" page and log in on the right side of the page. See [http://groups.google.com/group/c4lj-articles/t/e0b406daa4599c47 c4lj-articles] group for login information.</s>

== Announcing Publication ==

Announce at above mailing lists and the code4lib website.

== Twitter Hashtag ==

Use #c4lj - its use is tracked in https://docs.google.com/spreadsheets/d/1n7K3JhtBDMqUB1TaBBIEIPgAlNRANRlJhUDr5dgKJGs/edit?usp=sharing

[[Category: Code4Lib Journal]]

Code4Lib Journal Life of an Article

2017-06-08T15:17:35Z

Bean: adding code4lib category

[[File:C4LJ_life_of_an_article_3.jpg]]

[[Category:Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2017-06-08T15:07:00Z

Bean: /* Current Editors */

This supplements the [http://journal.code4lib.org/editorial-committee Editorial Committee] page on the ''Journal'' website.

=== Current Editors ===

* Sara Amato (17-current; CE 22, 29, 37)
* Carol Bean (1-current; CE 9, 16, 30, 38)
* Ed Corrado (1-current; CE 10)
* Andrew Darby (3-current; CE 8, 19, 34)
* Meghan Finch (23-current; CE 32)
* Eric Hanson (37-current)
* Rebecca Hirsch (37-current)
* Péter Király (23-current)
* Peter Murray (17-current; CE 20, 36)
* Norma Palomino (37-current)
* Ron Peterson (1-current; CE 3, 12, 18, 24, 33)
* Terry Reese (17-current; CE 21, 27, 31)
* Mark Swenson (37-current)
* Junior Tidal ( 23-current)
* Ruth K Tillman (29-current; CE 35)

=== Former Editors ===

* Christine Schwartz (3-7; CE 6)
* Ed Summers (16-17)
* Eric Lease Morgan (1-2; CE 2)
* Gabriel Farrell (9-19; CE 13)
* Jodi Schneider (1-8)
* Jon Brinley (TA 1-14)
* Ken Varnum (1-10; CE 4)
* MJ Suhonos (10-14)
* Ryan Wick (TA 3-14)
* Emily Lynema (1-16, CE 5)
* Tim McGeary (10-16; CE 14)
* Tim Lepczyk (10-17, CE 17)
* Tod Olson (10-17; CE 15)
* Jonathan Rochkind (1-20; CE 1)
* Kelley McGrath (8-28; CE 11,26)
* Shawn Averkamp (17- 29; CE 23, 28)
* Heidi Elaine Dowdling (23-29; CE 28)
* Dan Scott (23-29; CE 25)
* Jason Thomale (23-32)
* Tom Keays (1-29; CE 7; TA 15-29)

'''Note''': "CE" = Coordinating Editor and "TA" = Technical Administrator

[[Category: Code4Lib Journal]]

Code4lib Journal Republication Guidelines

2017-06-01T22:43:57Z

Bean:

Periodically editors may run across published web content (blog posts, etc) that they feel would work well as a code4lib journal article. The following is a process for allowing that to happen.

# Someone from the editorial board nominates an article by adding it to the Proposals tab in the Article Tracking spreadsheet and then emailing c4lj-articles
# Editors vote on it as if it came from outside the editorial board
# An editor volunteers (not necessarily the same person as #1)
# The editor contacts the author to see if they are interested in re-publishing the article in c4lj
# If yes, it follows the normal process

Note, it is important not to contact the author to see if they are interested in re-publishing their article prior to the proposal being accepted by the editorial board. This will prevent unnecessary disappointment or potential insult if the proposal is ultimately voted down.

[[Category: Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2017-06-01T22:41:50Z

Bean: /* Current Editors */

This supplements the [http://journal.code4lib.org/editorial-committee Editorial Committee] page on the ''Journal'' website.

=== Current Editors ===

* Sara Amato (17-current; CE 22, 29, 37)
* Carol Bean (1-current; CE 9, 16, 30, 38)
* Ed Corrado (1-current; CE 10)
* Andrew Darby (3-current; CE 8, 19, 34)
* Meghan Finch (23-current; CE 32)
* Péter Király (23-current)
* Peter Murray (17-current; CE 20, 36)
* Ron Peterson (1-current; CE 3, 12, 18, 24, 33)
* Terry Reese (17-current; CE 21, 27, 31)
* Junior Tidal ( 23-current)
* Ruth K Tillman (29-current; CE 35)

=== Former Editors ===

* Christine Schwartz (3-7; CE 6)
* Ed Summers (16-17)
* Eric Lease Morgan (1-2; CE 2)
* Gabriel Farrell (9-19; CE 13)
* Jodi Schneider (1-8)
* Jon Brinley (TA 1-14)
* Ken Varnum (1-10; CE 4)
* MJ Suhonos (10-14)
* Ryan Wick (TA 3-14)
* Emily Lynema (1-16, CE 5)
* Tim McGeary (10-16; CE 14)
* Tim Lepczyk (10-17, CE 17)
* Tod Olson (10-17; CE 15)
* Jonathan Rochkind (1-20; CE 1)
* Kelley McGrath (8-28; CE 11,26)
* Shawn Averkamp (17- 29; CE 23, 28)
* Heidi Elaine Dowdling (23-29; CE 28)
* Dan Scott (23-29; CE 25)
* Jason Thomale (23-32)
* Tom Keays (1-29; CE 7; TA 15-29)

'''Note''': "CE" = Coordinating Editor and "TA" = Technical Administrator

[[Category: Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2017-06-01T22:40:54Z

Bean: /* Former Editors */

This supplements the [http://journal.code4lib.org/editorial-committee Editorial Committee] page on the ''Journal'' website.

=== Current Editors ===

* Sara Amato (17-current; CE 22, 29, 37)
* Carol Bean (1-current; CE 9, 16, 30)
* Ed Corrado (1-current; CE 10)
* Andrew Darby (3-current; CE 8, 19, 34)
* Meghan Finch (23-current; CE 32)
* Péter Király (23-current)
* Peter Murray (17-current; CE 20, 36)
* Ron Peterson (1-current; CE 3, 12, 18, 24, 33)
* Terry Reese (17-current; CE 21, 27, 31)
* Junior Tidal ( 23-current)
* Ruth K Tillman (29-current; CE 35)

=== Former Editors ===

* Christine Schwartz (3-7; CE 6)
* Ed Summers (16-17)
* Eric Lease Morgan (1-2; CE 2)
* Gabriel Farrell (9-19; CE 13)
* Jodi Schneider (1-8)
* Jon Brinley (TA 1-14)
* Ken Varnum (1-10; CE 4)
* MJ Suhonos (10-14)
* Ryan Wick (TA 3-14)
* Emily Lynema (1-16, CE 5)
* Tim McGeary (10-16; CE 14)
* Tim Lepczyk (10-17, CE 17)
* Tod Olson (10-17; CE 15)
* Jonathan Rochkind (1-20; CE 1)
* Kelley McGrath (8-28; CE 11,26)
* Shawn Averkamp (17- 29; CE 23, 28)
* Heidi Elaine Dowdling (23-29; CE 28)
* Dan Scott (23-29; CE 25)
* Jason Thomale (23-32)
* Tom Keays (1-29; CE 7; TA 15-29)

'''Note''': "CE" = Coordinating Editor and "TA" = Technical Administrator

[[Category: Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2017-06-01T22:39:44Z

Bean: /* Former Editors */

This supplements the [http://journal.code4lib.org/editorial-committee Editorial Committee] page on the ''Journal'' website.

=== Current Editors ===

* Sara Amato (17-current; CE 22, 29, 37)
* Carol Bean (1-current; CE 9, 16, 30)
* Ed Corrado (1-current; CE 10)
* Andrew Darby (3-current; CE 8, 19, 34)
* Meghan Finch (23-current; CE 32)
* Péter Király (23-current)
* Peter Murray (17-current; CE 20, 36)
* Ron Peterson (1-current; CE 3, 12, 18, 24, 33)
* Terry Reese (17-current; CE 21, 27, 31)
* Junior Tidal ( 23-current)
* Ruth K Tillman (29-current; CE 35)

=== Former Editors ===

* Christine Schwartz (3-7; CE 6)
* Ed Summers (16-17)
* Eric Lease Morgan (1-2; CE 2)
* Gabriel Farrell (Issues 9-19; CE 13)
* Jodi Schneider (1-8)
* Jon Brinley (TA 1-14)
* Ken Varnum (1-10; CE 4)
* MJ Suhonos (10-14)
* Ryan Wick (TA 3-14)
* Emily Lynema (1-16, CE 5)
* Tim McGeary (10-16; CE 14)
* Tim Lepczyk (10-17, CE 17)
* Tod Olson (10-17; CE 15)
* Jonathan Rochkind (1-20; CE 1)
* Kelley McGrath (8-28; CE 11,26)
* Shawn Averkamp (17- 29, CE 23, 28)
* Heidi Elaine Dowdling (23-29, CE 28)
* Dan Scott (23-29, CE 25)
* Jason Thomale (23-32)
* Tom Keays (1-29; CE 7; TA 15-29)

'''Note''': "CE" = Coordinating Editor and "TA" = Technical Administrator

[[Category: Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2017-06-01T22:38:38Z

Bean: /* Current Editors */

This supplements the [http://journal.code4lib.org/editorial-committee Editorial Committee] page on the ''Journal'' website.

=== Current Editors ===

* Sara Amato (17-current; CE 22, 29, 37)
* Carol Bean (1-current; CE 9, 16, 30)
* Ed Corrado (1-current; CE 10)
* Andrew Darby (3-current; CE 8, 19, 34)
* Meghan Finch (23-current; CE 32)
* Péter Király (23-current)
* Peter Murray (17-current; CE 20, 36)
* Ron Peterson (1-current; CE 3, 12, 18, 24, 33)
* Terry Reese (17-current; CE 21, 27, 31)
* Junior Tidal ( 23-current)
* Ruth K Tillman (29-current; CE 35)

=== Former Editors ===

* Christine Schwartz (3-7; CE 6)
* Ed Summers (16-17)
* Eric Lease Morgan (1-2; CE 2)
* Gabriel Farrell (Issues 9-19; CE 13)
* Jodi Schneider (1-8)
* Jon Brinley (TA 1-14)
* Ken Varnum (1-10; CE 4)
* MJ Suhonos (10-14)
* Ryan Wick (TA 3-14)
* Emily Lynema (1-16, CE 5)
* Tim McGeary (10-16; CE 14)
* Tim Lepczyk (10-17, CE 17)
* Tod Olson (10-17; CE 15)
* Kelley McGrath (8-28; CE 11,26)
* Shawn Averkamp (17- 29, CE 23, 28)
* Heidi Elaine Dowdling (23-29, CE 28)
* Dan Scott (23-29, CE 25)
* Jason Thomale (23-32)
* Tom Keays (1-29; CE 7; TA 15-29)

'''Note''': "CE" = Coordinating Editor and "TA" = Technical Administrator

[[Category: Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2017-06-01T22:37:41Z

Bean: /* Former Editors */

This supplements the [http://journal.code4lib.org/editorial-committee Editorial Committee] page on the ''Journal'' website.

=== Current Editors ===

* Sara Amato (17-current; CE 22, 29, 37)
* Carol Bean (1-current; CE 9, 16, 30)
* Ed Corrado (1-current; CE 10)
* Andrew Darby (3-current; CE 8, 19, 34)
* Meghan Finch (23-current; CE 32)
* Péter Király (23-current)
* Peter Murray (17-current; CE 20, 36)
* Ron Peterson (1-current; CE 3, 12, 18, 24, 33)
* Terry Reese (17-current; CE 21, 27, 31)
* Jonathan Rochkind (1-current; CE 1)
* Junior Tidal ( 23-current)
* Ruth K Tillman (29-current; CE 35)

=== Former Editors ===

* Christine Schwartz (3-7; CE 6)
* Ed Summers (16-17)
* Eric Lease Morgan (1-2; CE 2)
* Gabriel Farrell (Issues 9-19; CE 13)
* Jodi Schneider (1-8)
* Jon Brinley (TA 1-14)
* Ken Varnum (1-10; CE 4)
* MJ Suhonos (10-14)
* Ryan Wick (TA 3-14)
* Emily Lynema (1-16, CE 5)
* Tim McGeary (10-16; CE 14)
* Tim Lepczyk (10-17, CE 17)
* Tod Olson (10-17; CE 15)
* Kelley McGrath (8-28; CE 11,26)
* Shawn Averkamp (17- 29, CE 23, 28)
* Heidi Elaine Dowdling (23-29, CE 28)
* Dan Scott (23-29, CE 25)
* Jason Thomale (23-32)
* Tom Keays (1-29; CE 7; TA 15-29)

'''Note''': "CE" = Coordinating Editor and "TA" = Technical Administrator

[[Category: Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2017-06-01T22:37:19Z

Bean: /* Current Editors */

This supplements the [http://journal.code4lib.org/editorial-committee Editorial Committee] page on the ''Journal'' website.

=== Current Editors ===

* Sara Amato (17-current; CE 22, 29, 37)
* Carol Bean (1-current; CE 9, 16, 30)
* Ed Corrado (1-current; CE 10)
* Andrew Darby (3-current; CE 8, 19, 34)
* Meghan Finch (23-current; CE 32)
* Péter Király (23-current)
* Peter Murray (17-current; CE 20, 36)
* Ron Peterson (1-current; CE 3, 12, 18, 24, 33)
* Terry Reese (17-current; CE 21, 27, 31)
* Jonathan Rochkind (1-current; CE 1)
* Junior Tidal ( 23-current)
* Ruth K Tillman (29-current; CE 35)

=== Former Editors ===

* Christine Schwartz (3-7; CE 6)
* Ed Summers (16-17)
* Eric Lease Morgan (1-2; CE 2)
* Gabriel Farrell (Issues 9-19; CE 13)
* Jodi Schneider (1-8)
* Jon Brinley (TA 1-14)
* Ken Varnum (1-10; CE 4)
* MJ Suhonos (10-14)
* Ryan Wick (TA 3-14)
* Emily Lynema (1-16, CE 5)
* Tim McGeary (10-16; CE 14)
* Tim Lepczyk (10-17, CE 17)
* Tod Olson (10-17; CE 15)
* Kelley McGrath (8-28; CE 11,26)
* Shawn Averkamp (17- 29, CE 23, 28)
* Heidi Elaine Dowdling (23-29, CE 28)
* Dan Scott (23-29, CE 25)
* Jason Thomale (23-32)

'''Note''': "CE" = Coordinating Editor and "TA" = Technical Administrator

[[Category: Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2017-06-01T22:32:27Z

Bean: /* Former Editors */

This supplements the [http://journal.code4lib.org/editorial-committee Editorial Committee] page on the ''Journal'' website.

=== Current Editors ===

* Sara Amato (17-current; CE 22, 29, 37)
* Carol Bean (1-current; CE 9, 16, 30)
* Ed Corrado (1-current; CE 10)
* Andrew Darby (3-current; CE 8, 19, 34)
* Tom Keays (1-current; CE 7; TA 15-current)
* Peter Murray (17-current; CE 20, 36)
* Ron Peterson (1-current; CE 3, 12, 18, 24, 33)
* Terry Reese (17-current; CE 21, 27, 31)
* Jonathan Rochkind (1-current; CE 1)
* Junior Tidal ( 23-current)
* Ruth K Tillman (29-current; CE 35)

=== Former Editors ===

* Christine Schwartz (3-7; CE 6)
* Ed Summers (16-17)
* Eric Lease Morgan (1-2; CE 2)
* Gabriel Farrell (Issues 9-19; CE 13)
* Jodi Schneider (1-8)
* Jon Brinley (TA 1-14)
* Ken Varnum (1-10; CE 4)
* MJ Suhonos (10-14)
* Ryan Wick (TA 3-14)
* Emily Lynema (1-16, CE 5)
* Tim McGeary (10-16; CE 14)
* Tim Lepczyk (10-17, CE 17)
* Tod Olson (10-17; CE 15)
* Kelley McGrath (8-28; CE 11,26)
* Shawn Averkamp (17- 29, CE 23, 28)
* Heidi Elaine Dowdling (23-29, CE 28)
* Dan Scott (23-29, CE 25)
* Jason Thomale (23-32)

'''Note''': "CE" = Coordinating Editor and "TA" = Technical Administrator

[[Category: Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2017-06-01T22:31:20Z

Bean: /* Current Editors */

This supplements the [http://journal.code4lib.org/editorial-committee Editorial Committee] page on the ''Journal'' website.

=== Current Editors ===

* Sara Amato (17-current; CE 22, 29, 37)
* Carol Bean (1-current; CE 9, 16, 30)
* Ed Corrado (1-current; CE 10)
* Andrew Darby (3-current; CE 8, 19, 34)
* Tom Keays (1-current; CE 7; TA 15-current)
* Peter Murray (17-current; CE 20, 36)
* Ron Peterson (1-current; CE 3, 12, 18, 24, 33)
* Terry Reese (17-current; CE 21, 27, 31)
* Jonathan Rochkind (1-current; CE 1)
* Junior Tidal ( 23-current)
* Ruth K Tillman (29-current; CE 35)

=== Former Editors ===

* Christine Schwartz (3-7; CE 6)
* Ed Summers (16-17)
* Eric Lease Morgan (1-2; CE 2)
* Gabriel Farrell (Issues 9-19; CE 13)
* Jodi Schneider (1-8)
* Jon Brinley (TA 1-14)
* Ken Varnum (1-10; CE 4)
* MJ Suhonos (10-14)
* Ryan Wick (TA 3-14)
* Emily Lynema (1-16, CE 5)
* Tim McGeary (10-16; CE 14)
* Tim Lepczyk (10-17, CE 17)
* Tod Olson (10-17; CE 15)
* Kelley McGrath (8-28; CE 11,26)
* Shawn Averkamp (17- 29, CE 23, 28)
* Heidi Elaine Dowdling (23-29, CE 28)
* Dan Scott (23-current, CE 25)

'''Note''': "CE" = Coordinating Editor and "TA" = Technical Administrator

[[Category: Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2017-06-01T22:26:12Z

Bean: /* Former Editors */

This supplements the [http://journal.code4lib.org/editorial-committee Editorial Committee] page on the ''Journal'' website.

=== Current Editors ===

* Sara Amato (17-current; CE 22, 29, 37)
* Carol Bean (1-current; CE 9, 16, 30)
* Ed Corrado (1-current; CE 10)
* Andrew Darby (3-current; CE 8, 19, 34)
* Tom Keays (1-current; CE 7; TA 15-current)
* Peter Murray (17-current; CE 20, 36)
* Ron Peterson (1-current; CE 3, 12, 18, 24, 33)
* Terry Reese (17-current; CE 21, 27, 31)
* Jonathan Rochkind (1-current; CE 1)
* Jason Thomale (23-current)

=== Former Editors ===

* Christine Schwartz (3-7; CE 6)
* Ed Summers (16-17)
* Eric Lease Morgan (1-2; CE 2)
* Gabriel Farrell (Issues 9-19; CE 13)
* Jodi Schneider (1-8)
* Jon Brinley (TA 1-14)
* Ken Varnum (1-10; CE 4)
* MJ Suhonos (10-14)
* Ryan Wick (TA 3-14)
* Emily Lynema (1-16, CE 5)
* Tim McGeary (10-16; CE 14)
* Tim Lepczyk (10-17, CE 17)
* Tod Olson (10-17; CE 15)
* Kelley McGrath (8-28; CE 11,26)
* Shawn Averkamp (17- 29, CE 23, 28)
* Heidi Elaine Dowdling (23-29, CE 28)
* Dan Scott (23-current, CE 25)

'''Note''': "CE" = Coordinating Editor and "TA" = Technical Administrator

[[Category: Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2017-06-01T22:25:48Z

Bean: /* Current Editors */

This supplements the [http://journal.code4lib.org/editorial-committee Editorial Committee] page on the ''Journal'' website.

=== Current Editors ===

* Sara Amato (17-current; CE 22, 29, 37)
* Carol Bean (1-current; CE 9, 16, 30)
* Ed Corrado (1-current; CE 10)
* Andrew Darby (3-current; CE 8, 19, 34)
* Tom Keays (1-current; CE 7; TA 15-current)
* Peter Murray (17-current; CE 20, 36)
* Ron Peterson (1-current; CE 3, 12, 18, 24, 33)
* Terry Reese (17-current; CE 21, 27, 31)
* Jonathan Rochkind (1-current; CE 1)
* Jason Thomale (23-current)

=== Former Editors ===

* Christine Schwartz (3-7; CE 6)
* Ed Summers (16-17)
* Eric Lease Morgan (1-2; CE 2)
* Gabriel Farrell (Issues 9-19; CE 13)
* Jodi Schneider (1-8)
* Jon Brinley (TA 1-14)
* Ken Varnum (1-10; CE 4)
* MJ Suhonos (10-14)
* Ryan Wick (TA 3-14)
* Emily Lynema (1-16, CE 5)
* Tim McGeary (10-16; CE 14)
* Tim Lepczyk (10-17, CE 17)
* Tod Olson (10-17; CE 15)
* Kelley McGrath (8-28; CE 11,26)
* Shawn Averkamp (17- 29, CE 23, 28)
* Heidi Elaine Dowdling (23-29, CE 28)

'''Note''': "CE" = Coordinating Editor and "TA" = Technical Administrator

[[Category: Code4Lib Journal]]

Code4Lib Editorial Committee Introduction

2017-06-01T22:13:54Z

Bean: /* How the Editorial Committee Functions */

[[Category: Code4Lib Journal]]

== How the Editorial Committee Functions ==

The Code4Lib Journal Editorial Committee works much as Code4Lib does: informally and collaboratively. For each issue, one member of the Editorial Committee (EC) volunteers to be Coordinating Editor (i.e., managing editor) of a journal issue. For the duration of their tenure, the Coordinating Editor is generally responsible for tying any loose ends, and making sure everything proceeds smoothly, coordinating all of the rest of us. This includes distributing the call for papers, communicating with potential authors, opening and closing editorial committee voting on submissions, notifying authors of rejected articles, and making sure that accepted articles have volunteer editors (and that those editors notify authors of accepted articles). The Coordinating Editor is also responsible for writing an introductory editorial and publishing the journal issue.

Everyone on the EC is expected to vote on article proposals as they come in. The Coordinating Editor generally sets a deadline of 1-2 weeks for voting. Voting is straightforward and recorded in the Article Tracking spreadsheet. An article must have at least two 'yes' votes and two more 'yes' votes than 'no' votes to be accepted. EC members may volunteer to be the primary editor or second reader for an article during the voting process or once voting is completed. The primary editor takes on the responsibility of shepherding the article from proposal to publication, acting as the journal's single point of contact with the author. The second editor/reader for an article serves as another pair of eyes early in the process by reading and providing feedback on drafts. Committee members are generally expected to take primary responsibility for one article per issue and serve as second reader on another one, though the committee is large enough that there is usually some flexibility with editorial responsibility.

Editing an article includes making sure the article draft is submitted on time, distributing drafts to the full committee for comment, making editorial suggestions or recommendations to the author(s), tracking and enforcing submission deadlines, requesting full Editorial Committee approval of the final draft, and inputting the finished article into our [http://wiki.code4lib.org/index.php/Code4Lib_Editorial_Committee_Introduction#Wordpress_.28Required.29 WordPress site]. Once the assigned editor recommends the final draft for publication, the EC again votes on whether to include that article in the current issue. Again, this requires at least two 'yes' votes and more 'yes' votes than 'no' votes for publication. We do not expect every EC member to vote on every article, but we do ask that you read an article thoroughly before voting on it for inclusion in the issue.

More detailed information describing the entire process from sending out the call for proposals to publishing a new issue is available on the Journal site:
* [http://journal.code4lib.org/process-and-structure General outline of process and structure]
* [http://journal.code4lib.org/process-and-structure/editors More detailed information for editors] (requires Wordpress login)

Templates for notifying authors about the status of their proposals are available as on the [http://wiki.code4lib.org/index.php/Code4Lib_Journal_Email_Templates wiki].

All of the Code4Lib Journal information on the wiki can be seen in the [http://wiki.code4lib.org/index.php/Category:Code4Lib_Journal Code4Lib category].

Above all, the Editorial Committee is informal and egalitarian. Jump in with your opinion and ideas!

== Editorial Committee Discussion Lists (Required) ==

Much of the Editorial Committee's business is conducted via email on the [http://groups.google.com/group/c4lj-articles C4LJ-Articles] Google Group. This list is where we debate article submissions, volunteer to be editor or managing editor, discuss acceptance of articles, and take care of any other tasks in front of us that might be of a sensitive nature. Anyone may post to this list, but only editors can read the list activity. To join this list, please visit the URL and request membership, using your preferred email associated with a Google account. If that doesn't work for some reason, you can join the c4lj-discuss group (see below) and send an email requesting membership to c4lj-articles.

All other Journal business is discussed on the [http://groups.google.com/group/c4lj-discuss C4LJ-Discuss] Google Group. If the conversation is unrelated to specific authors, proposals, or articles, it should probably happen on this list. We prefer to discuss other decisions about how the Journal is handled in public where anyone can participate. This list is open for anyone to join and is publicly viewable. Only list members can post. Use the URL above to join this discussion list. Due to spam, authors are moderated the first time they post.

== Article Tracking Spreadsheet (Required) ==

Articles, from proposal submission through to publication, are tracked using the C4LJ Article Tracking spreadsheet in Google Docs. This Google document is private; only Editorial Committee members may view or edit it. Proposal votes and tentative issue assignments for accepted articles are tracked in this spreadsheet. The [http://groups.google.com/group/c4lj-articles/browse_thread/thread/ec4c9701401ce94c/70079ef809a6a9da invitation] to become a collaborator is available on the c4lj-articles list. Please use this invitation to add yourself as a collaborator for this document (you must already be a member of c4lj-articles).

== Wordpress (Required) ==

Code4Lib Journal articles are published in a Wordpress installation hosted by ibiblio (http://journal.code4lib.org). The assigned editor for an article is responsible for entering the content into Wordpress, formatting it, and adding images and code snippets. Guidelines on entering articles are available on the [[Code4Lib_Journal_WordPress_Input_Guidelines|wiki]]. We also maintain basic information about the Journal using pages in Wordpress (Mission, Editorial Committee, Process and Structure, Call for Submissions, Article Guidelines).

New editors need to request a Wordpress account:

# Go to http://journal.code4lib.org/wp/wp-login.php?action=register - if this link does not work, please contact either Carol Bean <beanworks@gmail.com> or Tom Keays <tomkeays@gmail.com> to request access.
# Register
# Send your username to c4lj-articles@googlegroups.com so the technical editor can grant you Wordpress privileges.

Once you have an active WordPress account, please add your name to the list of Editorial Committee members at [http://journal.code4lib.org/editorial-committee http://journal.code4lib.org/editorial-committee].

== Google Analytics (Optional) ==

Google Analytics is used to gather statistics for the Code4Lib Journal. If you are interested in being able to view these statistics, just send your preferred Google Account information to the c4lj-articles@googlegroups.com discussion list, and the technical editor will enable your access.

== Other Shared Documents (Optional) ==

The C4LJ Article/Author Ideas spreadsheet is used to track ideas for have for specific articles we'd like to recruit or specific authors we want to recruit for the Journal. The [http://groups.google.com/group/c4lj-articles/browse_thread/thread/425165428b88e2ee invitation] to become a collaborative editor is available on the c4lj-articles list.

Code4Lib Editorial Committee Introduction

2017-06-01T21:56:07Z

Bean: /* How the Editorial Committee Functions */

[[Category: Code4Lib Journal]]

== How the Editorial Committee Functions ==

The Code4Lib Journal Editorial Committee works much as Code4Lib does: informally and collaboratively. For each issue, one member of the Editorial Committee (EC) volunteers to be Coordinating Editor (i.e., managing editor) of a journal issue. For the duration of their tenure, the Coordinating Editor is generally responsible for any loose ends tying, and making sure everything proceeds smoothly, coordinating all of the rest of us. This includes distributing the call for papers, communicating with potential authors, opening and closing editorial committee voting on submissions, notifying authors of rejected articles, and making sure that accepted articles have volunteer editors (and that those editors notify authors of accepted articles).

Everyone on the EC may vote on article proposals as they come in. The Coordinating Editor generally sets a deadline of 1-2 weeks for voting. Voting is straightforward and recorded in the Article Tracking spreadsheet. An article must have at least two 'yes' votes and two more 'yes' votes than 'no' votes to be accepted. Once an article is accepted for publication, an EC member volunteers to take on editorial responsibility for that article as the first editor. The first editor shepherds the from proposal to publication, acting as the journal's single point of contact with the author. Each article also has a second editor/reader, who serves as another pair of eyes early in the process by reading and providing feedback on drafts. Most Committee members take primary responsibility for about one article per issue and serve as second reader on another one, though the committee is large enough that there is some flexibility with editorial responsibility.

Editing an article includes making sure the article draft is submitted on time, distributing drafts to the full committee for comment, making editorial suggestions or recommendations to the author(s), tracking and enforcing submission deadlines, requesting full Editorial Committee approval of the final draft, and inputting the finished article into our [http://wiki.code4lib.org/index.php/Code4Lib_Editorial_Committee_Introduction#Wordpress_.28Required.29 WordPress site]. Once the assigned editor recommends the final draft for publication, the EC again votes on whether to include that article in the current issue. Again, this requires at least two 'yes' votes and more 'yes' votes than 'no' votes for publication. We do not expect every EC member to vote on every article, but we do ask that you read an article thoroughly before voting on it for inclusion in the issue.

More detailed information describing the entire process from sending out the call for proposals to publishing a new issue is available on the Journal site:
* [http://journal.code4lib.org/process-and-structure General outline of process and structure]
* [http://journal.code4lib.org/process-and-structure/editors More detailed information for editors] (requires Wordpress login)

Templates for notifying authors about the status of their proposals are available as on the [http://wiki.code4lib.org/index.php/Code4Lib_Journal_Email_Templates wiki].

All of the Code4Lib Journal information on the wiki can be seen in the [http://wiki.code4lib.org/index.php/Category:Code4Lib_Journal Code4Lib category].

Above all, the Editorial Committee is informal and egalitarian. Jump in with your opinion and ideas!

== Editorial Committee Discussion Lists (Required) ==

Much of the Editorial Committee's business is conducted via email on the [http://groups.google.com/group/c4lj-articles C4LJ-Articles] Google Group. This list is where we debate article submissions, volunteer to be editor or managing editor, discuss acceptance of articles, and take care of any other tasks in front of us that might be of a sensitive nature. Anyone may post to this list, but only editors can read the list activity. To join this list, please visit the URL and request membership, using your preferred email associated with a Google account. If that doesn't work for some reason, you can join the c4lj-discuss group (see below) and send an email requesting membership to c4lj-articles.

All other Journal business is discussed on the [http://groups.google.com/group/c4lj-discuss C4LJ-Discuss] Google Group. If the conversation is unrelated to specific authors, proposals, or articles, it should probably happen on this list. We prefer to discuss other decisions about how the Journal is handled in public where anyone can participate. This list is open for anyone to join and is publicly viewable. Only list members can post. Use the URL above to join this discussion list. Due to spam, authors are moderated the first time they post.

== Article Tracking Spreadsheet (Required) ==

Articles, from proposal submission through to publication, are tracked using the C4LJ Article Tracking spreadsheet in Google Docs. This Google document is private; only Editorial Committee members may view or edit it. Proposal votes and tentative issue assignments for accepted articles are tracked in this spreadsheet. The [http://groups.google.com/group/c4lj-articles/browse_thread/thread/ec4c9701401ce94c/70079ef809a6a9da invitation] to become a collaborator is available on the c4lj-articles list. Please use this invitation to add yourself as a collaborator for this document (you must already be a member of c4lj-articles).

== Wordpress (Required) ==

Code4Lib Journal articles are published in a Wordpress installation hosted by ibiblio (http://journal.code4lib.org). The assigned editor for an article is responsible for entering the content into Wordpress, formatting it, and adding images and code snippets. Guidelines on entering articles are available on the [[Code4Lib_Journal_WordPress_Input_Guidelines|wiki]]. We also maintain basic information about the Journal using pages in Wordpress (Mission, Editorial Committee, Process and Structure, Call for Submissions, Article Guidelines).

New editors need to request a Wordpress account:

# Go to http://journal.code4lib.org/wp/wp-login.php?action=register - if this link does not work, please contact either Carol Bean <beanworks@gmail.com> or Tom Keays <tomkeays@gmail.com> to request access.
# Register
# Send your username to c4lj-articles@googlegroups.com so the technical editor can grant you Wordpress privileges.

Once you have an active WordPress account, please add your name to the list of Editorial Committee members at [http://journal.code4lib.org/editorial-committee http://journal.code4lib.org/editorial-committee].

== Google Analytics (Optional) ==

Google Analytics is used to gather statistics for the Code4Lib Journal. If you are interested in being able to view these statistics, just send your preferred Google Account information to the c4lj-articles@googlegroups.com discussion list, and the technical editor will enable your access.

== Other Shared Documents (Optional) ==

The C4LJ Article/Author Ideas spreadsheet is used to track ideas for have for specific articles we'd like to recruit or specific authors we want to recruit for the Journal. The [http://groups.google.com/group/c4lj-articles/browse_thread/thread/425165428b88e2ee invitation] to become a collaborative editor is available on the c4lj-articles list.

Code4Lib Journal Deadlines

2017-05-27T13:08:07Z

Bean: adding editor name

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

===Thirty-eighth issue===
Coordinating Editor: Carol Bean
*Call for proposals: Monday, June 12, 2017
*Second call for proposals: Monday, July 3, 2017 (if necessary)
*Proposals due: Friday, July 14, 2017
*Proposals accepted: Friday, July 21, 2017
*First draft due: Friday, August 18, 2017
*Second draft due: Friday, September 15, 2017
*Publication date: Monday, October 16, 2017

===Thirty-seventh issue===
Coordinating Editor: Sara Amato
*Call for proposals: Monday, March 13, 2017
*Second call for proposals: Monday, April 3, 2017 (if necessary)
*Proposals due: Friday, April 14, 2017
*Proposals accepted: Friday, April 21, 2017
*First draft due: Friday, May 19, 2017
*Second draft due: Friday, June 16, 2017
*Publication date: Monday, July 17, 2017

===Thirty-sixth issue===
Coordinating Editor: Peter Murray
*Call for proposals: Thursday, December 15, 2016
*Second call for proposals: Thursday, January 5, 2017 (if necessary)
*Proposals due: Tuesday, January 17, 2017
*Proposals accepted: Monday, January 23, 2017
*First draft due: Monday, February 20, 2017
*Second draft due: Monday, March 20, 2017
*Publication date: Monday, April 17, 2017

===Thirty-fifth issue===

Coordinating Editor: Ruth Kitchin Tillman

* Call for proposals: Monday, September 26, 2016
* Second call for proposals: Monday, October 17, 2016 (if necessary)
* Proposals due: Friday, October 28, 2016
* Proposals accepted: Friday, November 4, 2016
* First draft due: Friday, December 2, 2016
* Second draft due: Friday, December 30, 2016
* Publication date: Monday, January 30, 2017

===Thirty-fourth issue===
Coordinating Editor: Andrew Darby

* Call for proposals: Monday, June 20, 2016
* Second call for proposals: Monday, July 11, 2016 (if necessary)
* Proposals due: Friday, July 22, 2016
* Proposals accepted: Friday, July 29, 2016
* First draft due: Friday, August 26, 2016
* Second draft due: Friday, September 23, 2016
* Publication date: Monday, October 24, 2016

===Thirty-third issue===
Coordinating Editor: Ron Peterson

* Call for proposals: Monday, March 14, 2016
* Second call for proposals: Monday, April 4, 2016 (if necessary)
* Proposals due: Friday, April 15, 2016
* Proposals accepted: Friday, April 29, 2016
* First draft due: Friday, May 20, 2016
* Second draft due: Friday, June 17, 2016
* Publication date: Monday, July 18, 2016

===Thirty-second issue===
Coordinating Editor: Meghan Finch
* Call for proposals: Monday, December 14, 2015
* Second call for proposals: Monday, January 4, 2016 (if necessary)
* Proposals due: Friday, January 15, 2016
* Proposals accepted: Friday, January 22, 2016
* First draft due: Friday, February 19, 2016
* Second draft due: Friday, March 18, 2016
* Publication date: Monday, April 25, 2016

===Thirty-first issue===
Coordinating Editor: Terry Reese
* Call for proposals: Monday, September 21, 2015
* Second call for proposals: Thursday, October 8, 2015 (if necessary)
* Proposals due: Friday, October 23, 2015
* Proposals accepted: Friday, October 30, 2015
* First draft due: Monday, November 23, 2015
* Second draft due: Monday, December 21, 2015
* Publication date: Monday, January 25, 2016

===Thirtieth issue===
Coordinating editor for issue #30: Carol Bean

* Call for proposals: Thursday, June 11, 2015
* Second call for proposals: Thursday, July 2, 2015 (if necessary)
* Proposals due: Monday, July 13, 2015
* Proposals accepted: Monday, July 20, 2015
* First draft due: Monday, August 17, 2015
* Second draft due: Monday, September 14, 2015
* Publication date: Monday, October 19, 2015

===Twenty-ninth issue===
Coordinating editor for issue #29: Sara Amato

* Call for proposals: Wednesday, March 11, 2015
* Second call for proposals: Wednesday, April 1, 2015 (if necessary)
* Proposals due: Friday, April 10, 2015
* Proposals accepted: Monday, April 20, 2015
* First draft due: Monday, May 18, 2015
* Second draft due: Monday, June 15, 2015
* Publication date: Monday, July 13, 2015

===Twenty-eighth issue===
Coordinating editor for issue #28: Heidi Dowding

Special issue on diversity in library technology.

* Call for proposals: Wednesday, December 10, 2014
* Second call for proposals: Monday, January 5, 2015 (if necessary, adjusted from 31-Dec-2014)
* Proposals due: Monday, January 12, 2015
* Proposals accepted: Monday, January 19, 2015
* First draft due: Monday, February 16, 2015
* Second draft due: Monday, March 16, 2015
* Publication date: Wednesday, April 15, 2015

===Twenty-seventh issue===
Coordinating editor for issue #27: Terry Reese

*Call for proposals: Monday, September 27, 2014
*Second call for proposals: Monday, October 6, 2014 (if necessary)
*Proposals due: Friday, October 24, 2014
*Proposals accepted: Friday, October 31, 2014
*First draft due: Friday, November 21, 2014
*Second draft due: Friday, December 19, 2014
*Publication date: Monday, January 19, 2015

===Twenty-sixth issue===
Coordinating editor for issue #26: Kelley McGrath

*Call for proposals: Monday, June 9, 2014
*Second call for proposals: Monday, June 30, 2014 (if necessary)
*Proposals due: Friday, July 11, 2014
*Proposals accepted: Friday, July 18, 2014
*First draft due: Friday, August 15, 2014
*Second draft due: Friday, September 12, 2014
*Publication date: Monday, October 20, 2014

===Twenty-fifth issue===
Coordinating editor for issue #25: Dan Scott

*Call for proposals: Monday, March 10, 2014
*Second call for proposals: Monday, March 31, 2014 (if necessary)
*Proposals due: Friday, April 11, 2014
*Proposals accepted: Friday, April 18, 2014
*First draft due: Friday, May 16, 2014
*Second draft due: Friday, June 13, 2014
*Publication date: Monday, July 14, 2014

===Twenty-fourth issue===
Coordinating editor for issue #24: Ron Peterson

*Call for proposals: Monday, December 9, 2013
*Call for proposals #2: Monday, December 30, 2013 (if necessary)
*Proposals due: Friday, January 10, 2014
*Proposals accepted: Friday, January 17, 2014
*First draft due: Friday, February 14, 2014
*Second draft due: Friday, March 14, 2014
*Publication date: Monday, April 14, 2014

===Twenty-third issue===
Coordinating editor for issue #23: Shawn Averkamp
* Call for proposals: Monday, September 9, 2013
* Call for proposals #2: Monday September 30, 2013 (if necessary)
* Proposals due: Friday, October 11, 2013
* Proposals accepted: Friday, October 18, 2013
* First draft due: Friday, November 15, 2013
* Second draft due: Friday, December 13, 2013
* Publication date: Monday, January 13, 2014

===Twenty-second issue===
Coordinating editor for issue #22: Sara Amato
* Call for proposals: Monday, June 10, 2013
* Call for proposals #2: July 5, 2013 (if necessary)
* Proposals due: Friday, July 12, 2013
* Proposals accepted: Friday, July 19, 2013
* First draft due: Friday, August 16, 2013
* Second draft due: Friday, September 13, 2013
* Publication date: Monday, October 14, 2013

===Twenty-first issue===
Coordinating editor for issue #21: Terry Reese
* Call for proposals: Monday, March 11, 2013
* Call for proposals #2: Monday, April 1, 2013
* Proposals due: Friday, April 12, 2013
* Proposals accepted: Friday, April 19, 2013
* First draft due: Friday, May 17, 2013
* Second draft due: Friday, June 14, 2013
* Publication date: Monday, July 15, 2013

===Twentieth issue===
Coordinating editor for issue #20: [[User:DataGazetteer|Peter Murray]]
* Call for proposals:     Monday, December 10, 2012
* Call for proposals #2: Monday, January 7, 2013 (if necessary)
* Proposals due:          Friday, January 18, 2013
* Proposals accepted:     Friday, January 25, 2013
* First draft due:        Friday, February 22, 2013
* Second draft due:       Friday, March 22, 2013
* Publication date:       Monday, April 15, 2013

===Nineteenth issue===
Coordinating editor for issue #19: Andrew Darby
* Call for proposals: Monday, September 10, 2012
* Proposals due: Friday, October 12, 2012
* Proposals accepted: Friday, October 19, 2012
* First draft due: Friday, November 16, 2012
* Second draft due: Friday, December 14, 2012
* Publication date: Monday, January 14, 2013

===Eighteenth issue===
Coordinating editor for issue #18: Ron Peterson
* Call for proposals: Monday, May 28, 2012
* Proposals due: Friday, June 29, 2012
* Proposals accepted: Friday, July 6, 2012
* First draft due: Friday, August 3, 2012
* Second draft due: Friday, August 31, 2012
* Publication date: Monday, October 1, 2012

===Seventeenth issue===
Coordinating editor for issue #17: Tim Lepczyk
* Call for proposals: Wednesday, February 8, 2012
* Proposals due: Tuesday, February 28, 2012
* Proposals accepted: Tuesday, March 6, 2012
* First draft due: Tuesday, April 3, 2012
* Second draft due: Tuesday, May 1, 2012
* Publication date: Friday, June 1, 2012

===Sixteenth issue===
Coordinating editor for issue #16: Carol Bean
* Call for proposals: Monday, September 26, 2011
* Proposals due: Friday, October 28, 2011
* Proposals accepted: Friday, November 4, 2011
* First draft due: Friday, December 2, 2011
* Second draft due: Friday, December 30, 2011
* Publication date: Monday, January 30, 2012

===Fifteenth issue===
Coordinating editor for issue #15: Tod Olson
* Call for proposals: Monday, June 27, 2011
* Proposals due: Friday, July 29, 2011
* Proposals accepted: Friday, August 5, 2011
* First draft due: Friday, September 2, 2011
* Second draft due: Friday, September 30, 2011
* Publication date: Monday, October 31, 2011

===Fourteenth issue===

* Call for proposals: Monday, March 21, 2011
* Proposals due: Friday, April 22, 2011
* Proposals accepted: Friday, April 29, 2011
* First draft due: Friday, May 27, 2011
* Second draft due: Friday, June 24, 2011
* Publication date: Monday, July 25, 2011

===Thirteenth issue===

* Call for proposals: Monday, December 6, 2010
* Proposals due: Friday, January 7, 2011
* Proposals accepted: Friday, January 14, 2011
* First draft due: Friday, February 11, 2011
* Second draft due: Friday, March 11, 2011
* Publication date: Monday, April 11, 2011

===Twelfth issue===

* Call for proposals: Monday, August 16, 2010
* Proposals due: Friday, September 17, 2010
* Proposals accepted: Friday, September 24, 2010
* First draft due: Friday, October 22, 2010
* Second draft due: Friday, November 19, 2010
* Publication date: Monday, December 20, 2010

===Eleventh issue===

* Call for proposals: Monday, May 17, 2010
* Proposals due: Friday, June 18, 2010
* Proposals accepted: Friday, June 25, 2010
* First draft due: Friday, July 23, 2010
* Second draft due: Friday, August 20, 2010
* Publication date: Monday, September 20, 2010

=== Tenth issue ===

* Call for proposals: Monday, February 15, 2010
* Proposals due: Friday, March 19, 2010
* Proposals accepted: Friday, March 26, 2010
* First draft due: Friday, April 23, 2010
* Second draft due: Friday, May 21, 2010
* Publication date: Monday, June 21, 2010

=== Ninth issue ===

* Monday, November 9, 2009 -- Call for proposals
* Friday, December 11, 2009 -- Proposals due
* Friday, December 18, 2009 -- Finish voting on proposals, notify authors
* Friday, January 15, 2010 -- First draft due
* Friday, February 12, 2010 -- Second draft due
* Monday, March 15, 2010 -- Publication date

=== Eighth issue ===

* Monday, July 27 -- call for proposals
* Friday, August 14 -- proposals due
* Friday, August 21 -- finish voting on proposals; notify authors
* Friday, September 25 -- first draft due
* Friday, October 23 -- second draft due
* Monday, November 23 -- publication

=== Seventh issue ===

* Monday, February 16 -- call for proposals
* Friday, March 20 -- proposals due
* Monday, March 30 -- publication of issue 6
* Friday, March 27 -- finish voting on proposals; notify authors
* Friday, April 24 -- first draft due
* Friday, May 22 -- second draft due
* Monday, June 22 -- publication

=== Sixth issue ===

* Monday, November 10 -- call for proposals
* Friday, December 12 -- proposals due
* Monday, December 15 -- publication of issue 5
* Friday, December 19 -- finish voting on proposals; notify authors
* Friday, January 23 -- first draft due
* Friday, February 20 -- second draft due
* Monday, March 30 -- publication (originally scheduled for March 23)

=== Fifth issue ===

* Monday, August 18 -- call for proposals
* Friday, September 12 -- proposals due
* Friday, September 19 -- finish voting on proposals; notify authors
* Monday, September 22 -- issue 4 published
* Friday, October 17 -- first draft due
* Friday, November 14 -- second draft due
* Monday, December 15 -- publication

=== Fourth issue ===

* Friday, May 16 -- call for proposals
* Friday, June 20 -- extended proposal deadline (originally 6/13, before issue 3 is published)
* Friday, July 18 -- first draft due
* Friday, August 15 -- second draft due
* Monday, September 22 -- publication

=== Third issue ===

* Wednesday February 13th -- call for proposals
* Friday March 14th -- proposals due (after con, before issue 2)
* Friday April 25 -- first draft due
* Saturday June 21 -- publication (tentative)

=== Second issue ===

* Friday November 9th -- call for proposals
* Friday January 11 -- article draft deadline (or Thurs Jan 21, from EM)
* Thursday February 21 -- revisions/second draft deadline
* Friday March 21 -- publication (tentative)

=== First issue ===

* Friday August 31st -- call for proposals
* Friday October 12th -- article draft deadline
* Monday December 17th -- publication

[[Category: Code4Lib Journal]]

2017 Code4Lib Midwest Meeting

2017-04-27T02:00:39Z

Bean: /* Lightning Talks */

===Location===
[http://luc.edu/ic/ Klarchek Information Commons], 4th floor

Loyola University Chicago

[https://www.google.com/maps?f=q&source=s_q&hl=en&geocode&q=42.000202,-87.656182 Google Maps]

==Registration==
Registration available at http://libcal.luc.edu/event/3200163. There is no cost to register.

==Logistics==
====Travel====
Chicago is served by Midway Airport and O'Hare International Airport, Amtrak, and bus lines. O'Hare is closer to campus. If using public transportation, from O'Hare take the Blue Line downtown and transfer to the northbound Red Line; for Midway take the Orange Line downtown and transfer to the northbound Red Line.

[http://www.luc.edu/visit.shtml More information on travel to campus]

====Accommodations====
[http://hamptoninn3.hilton.com/en/hotels/illinois/hampton-inn-chicago-north-loyola-station-CHIYOHX/index.html Hampton Inn Chicago North-Loyola Station]
This newly constructed hotel is on campus, and within a block of the Red Line. We do not have a room block.

====Wireless internet====
Loyola is a member of Eduroam, and public wireless is available on campus.

====Meals====
Breakfast will be included on April 26. Lunch and dinner will be local dinearounds.

====Getting There/Parking====
You are highly encouraged to take public transportation if possible; the Red Line Loyola stop is on campus. Parking is available for $7. [http://luc.edu/campustransportation/generalinformation/visitorsandguests/ Parking and transit information]

====Eat, Drink, Do Fun Things====
[https://drive.google.com/open?id=1r_lsJPKoz6Awr7LkTCOX63IvV0w&usp=sharing Google Map with a few dining suggestions near campus]

====Other Questions?====
Contact Margaret Heller at mheller1@luc.edu

== Schedule ==
April 26, 9-5
April 27, 9-12

Note that the BitCurator Users Forum 2017 takes place on April 27 and 28, so those attending that may choose to attend only on April 26

==== Detailed schedule, April 26 & 27 ====

[https://docs.google.com/spreadsheets/d/1_ahiQjKel0hi9bFUUsk73eMXeO2iPxJkvqVs_2lfyck/edit?usp=sharing Detailed Schedule (subject to change during the day)]

===== Outline of April 26 =====

8:30-9:00: Check-in and breakfast

9:00-9:15: Welcome and introductory remarks

9:15-10:15: Introductions / Successes / Struggles 
One of the strengths of Code4Lib is our willingness to share experience and learn from each other. As an experiment, we will go around the room. Introduce yourself and give an example of (1) something you are proud of and (2) something you are struggling with. We hope that this will stimulate ideas for breakout topics and informal conversations.

10:15-10:30: Break

10:00-11:30 Lightning Talks/presentations

11:30-1:00 Lunch ([https://docs.google.com/document/d/1V0_nANm4OIABHuOEnVjChXAKS2TCnjNuHwkOxnG49LQ/edit?usp=sharing Sign up])

1:00-2:30 Presentations/ Breakouts (4) (post-breakout lightning talks to report back)

3:00-3:15 Break

3:15-4:30 Presentations

Time TBD (~5PM-~8PM): Meetup at [http://caryslounge.com/ Cary's Lounge]
This bar is an easy bus ride from campus, and near many great dining options.

===== Outline of April 27 =====
8:30-9:00: Check-in

9:00-10:30 Presentations and/or lightning talks

10:30-10:45 Break

11:00-12:00 Wrap-up

==Programming Sign-up==

Code4Lib Midwest programming depends on the folks attending the conference. Please consider giving a presentation or lightning talk, or submitting your ideas for a hackfest/breakout session.

Share what you are working on! Add your name and a description below. Please also let us know how long you'll need (10 or 20 minutes), and whether you prefer Wednesday or Thursday (or if it doesn't matter). Contact Ryan Wick (ryanwick@gmail.com) with your preferred username to set up a Code4Lib wiki account. If you don't have a wiki account and don't want to sign up for one, please email [mailto:mheller1@luc.edu mheller1@luc.edu].

===Presentations ===

'''Digitizing World War One Music with the Illinois State Library and Pritzker Military Museum''' - Andrew Bullen, Illinois State Library

I can talk about this program and how we use optical musical recognition to make “playable” MP3 files for the tunes.

'''Digital Preservation at Loyola University Chicago''' - Margaret Heller (and possibly others), Loyola University Chicago

We made the vended choice for digital preservation, but what does that actually mean in practice?
W or Th
10 minutes

'''Library Website Redesign Panel Discussion''' - Various

In 2016, several Chicago-area libraries redesigned their websites. This panel will discuss the different processes they went through and results.

'''Towards a Linked Data workflow''' - Tod A. Olson, University of Chicago

The U. Chicago Library is experimenting with acting as a producer and consumer of linked data. I will discuss a pilot project involving centered around an existing collection of photographs.

'''Search Experience at the University of Michigan Library''' - Jon Earley, University of Michigan

Our newest search tool aims to greatly improve the discoverability and accessibility of our enormous volume of resources by bringing our complex siloed resources together and make them easily searchable in one interface. This presentation will focus on front-end technology decisions and architecture, why we decided to build this discovery interface, the overall strategic direction, and a demo of the beta application. W, 20 minutes

'''Omeka to Scalar Transition''' - Matt Krc, Newberry Library

'''Computational Archival Science: Highlights from the 2016 CAS Workshop''' - Robert J. Sandusky, University of Illinois at Chicago

The workshop [http://dcicblog.umd.edu/cas/ieee_big_data_2016_cas-workshop/ Computational Archival Science: Digital Records in the Age of Big Data] was held at the IEEE Big Data conference in Washington, D.C. in December 2016. This presentation will highlight some of the themes that emerged from the presentations, papers, posters, and discussions at the workshop. A related breakout session will allow code4lib Midwest attendees share what they're doing computationaly and what they need to scale up and improve accessibility, discoverability, and processing of archives and records. W, 20 minutes

===Lightning Talks===

Have something cool to share but you don't want to be in front of the room for more than 5 minutes? Lightning talks are for you. 5 minute max. Sign up now or at the conference:

*'''UIC Mini-DAMS part 1: Where we started - Tracy Seneca
*'''UIC Mini-DAMS part 2: Where we’re at - Esther Verreau
*'''Chicago Building Permits - Tracy Seneca
*'''[[presentation::https://docs.google.com/presentation/d/1e-aMqZKtolRdSpgKmTUrt4Xlaqn8tbt6dcWOV4vZzRY/edit?usp=sharing|C4L Journal Call for Editors]] - Carol Bean

===Breakout Sessions===

Actual breakout sessions presented and locations will be determined on April 26. Please propose an idea here if you are willing to facilitate a discussion on a topic.

'''Moving Toward the Computational Archive'''
Facilitated discussion around questions like:
# How are you using automation or computational approaches to improve archival practice?
# What opportunities have you considered / identified regarding computational approaches to archiving?
# What is needed to develop and move toward implementation of computational approaches to archival practice?
# What is computational provenance and do archives need it? (See [https://en.wikipedia.org/wiki/Blockchain Blockchain] and [https://www.w3.org/TR/prov-overview/ PROV])
Margaret Heller and Bob Sandusky.

'''[http://jekyllrb.com/ Building a site with Jekyll]'''
Kate Flynn and Allan Berry.

'''Hackathon Pedagogies for In-Class Use'''
Bethany McGowan

==Code of Conduct==
Code4Lib seeks to provide a welcoming, fun, and safe community and conference experience and ongoing community for everyone. We do not tolerate harassment in any form. Discriminatory language and imagery (including sexual) is not appropriate for any event venue, including talks, or any community channel such as the chatroom or mailing list.
Harassment is understood as any behavior that threatens another person or group, or produces an unsafe environment. It includes offensive verbal comments or non-verbal expressions related to gender, gender identity, gender expression, sexual orientation, disability, physical appearance, body size, race, age, religious beliefs, sexual or discriminatory images in public spaces (including online), deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention.
===CodeOfConduct4Lib===
[https://github.com/code4lib/antiharassment-policy/blob/master/code_of_conduct.md Read and contribute to our full Code of Conduct document on GitHub]

2016 Code4Lib Midwest Meeting

2016-07-21T15:16:42Z

Bean: Adding link to pptx file used for lightning talk

== Code4Lib Midwest 2016 Meeting ==

Mark your calendars -- The University of Chicago Library will host the Code4Lib Midwest 2016 meeting in Chicago, IL.

===Location===
Code4Lib MidWest meeting will be hosted by [http://www.lib.uchicago.edu The University of Chicago Library].
* '''When''' - July 14 & 15, 2016 ''(NOTE: date change)''
* '''Where''' - [http://www.lib.uchicago.edu Regenstein Library], room 122, 1100 East 57th Street, Chicago. ([https://www.google.com/maps/place/Regenstein+Library,+1100+E+57th+St,+Chicago,+IL+60637/@41.7922338,-87.6024283,17z/data=!3m1!4b1!4m5!3m4!1s0x880e293e39d17fbd:0xc21663d6b4558f0a!8m2!3d41.7923654!4d-87.5999823 Map])
* '''Who''' - contact person: Tod Olson ( tod at uchicago.edu )

===Logistics===
====Travel====
Chicago is served by Midway Airport (closest to UChicago) and O'Hare International Airport (much further), Amtrak, and bus lines.

Directions to campus:
* [https://maps.uchicago.edu/directions/masstransit.shtml Mass Transit]
* [https://maps.uchicago.edu/directions/car.shtml Directions by Car]
* [https://maps.uchicago.edu/directions/airports.shtml From Chicago Airports]
* [https://maps.uchicago.edu/directions/taxi.shtml By Taxi or Shuttle]

====Accommodations====

There are a few hotel options in Hyde Park, including:

* [http://chicagosouthuniversity.place.hyatt.com/en/hotel/home.html Hyatt Place Chicago-South/University Medical Center] (5225 S Harper Ave, Chicago, IL 60615, (773) 752-5300) About 1.2 miles from the meeting location and near a number of restaurants on 53rd St.

====Parking====

The [https://maps.uchicago.edu/?location=Campus+North+Parking parking garage at 55th St. & Ellis Ave.] is an option for visitor parking, at a rate of $25 per day.

====Eat, Drink, Do Fun Things (in Hyde Park)====
[https://drive.google.com/open?id=1_RxnUnLAEmlNpbHML_-jGRf7OXE&usp=sharing We made you a map of good eats and fun things to do in the area!]

=== Schedule ===

==== Detailed schedule, July 14 & 15 ====

Check the detailed '''''[https://docs.google.com/spreadsheets/d/1fbYC_eef4KY7baLNIxK7Sy_bH9ZsKfpNTikHE2DBzGA/edit#gid=0 2016 Code4Lib Midwest Schedule]'''''.

Daily start times are fixed, but individual talks may still shift around.

==== Outline of Thursday, July 14th ====

8:30-9:00: Check-in

9:00-9:15: Welcome and introductory remarks

9:15-10:45: Introductions / Successes / Struggles 
One of the strengths of Code4Lib is our willingness to share experience and learn from each other. As an experiment, we will go around the room. You will have 1-2 minutes to introduce yourself and give an example of (1) something you are proud of and (2) something you are struggling with. We hope that this will stimulate ideas for breakout topics and informal conversations.

10:45-11:00: Break

11:00-4:30: Presentations and breakouts, check the [https://docs.google.com/spreadsheets/d/1fbYC_eef4KY7baLNIxK7Sy_bH9ZsKfpNTikHE2DBzGA/edit#gid=0 detailed schedule]

==== Outline of Friday, July 15th ====

8:30-9:00: Check-in

9:00-11:30: Presentations and breakouts, check the [https://docs.google.com/spreadsheets/d/1fbYC_eef4KY7baLNIxK7Sy_bH9ZsKfpNTikHE2DBzGA/edit#gid=0 detailed schedule]

11:30-12:00: Tour of [https://www.lib.uchicago.edu/mansueto/ Mansueto Library] - with an emphasis on the underground automated storage and retrieval system.

===Technical Details===
* WiFi: Wireless access will be provided, and UChicago is an Eduroam participant

===Social Media Hashtag===
Please use #c4lmw when tagging things!

===Slack channel===
Join #code4libmidwest at [https://code4lib.slack.com code4lib.slack.com]

If you need invitation, [https://docs.google.com/forms/d/120Dw1JjLxPJB9VTGl0mUY7Ot6yg6YNY1RZUISJFzdwk/viewform?c=0&w=1&usp=mail_form_link fill out this form for instant invitation].

==Programming Sign-up==

Code4Lib Midwest programming depends on the folks attending the conference. Please consider giving a presentation or lightning talk, or submitting your ideas for a hackfest/workshop.

Share what you are working on! Add your name and a description below. Please also let us know how long you'll need, and whether you prefer Thursday or Friday (or if it doesn't matter)

===Presentations ===
(If you'd like to propose a workshop, talk to us.)

'''Talk Title''' - [Speaker Name]: [Description]

'''VIAF and Elasticsearch''' - Ralph LeVan, OCLC Research:
I'll give an overview of the technology supporting VIAF and our exercise to switch from our home-grown Pears database loading XML records and move to JSON-based Elasticsearch.

'''How not to work during a sabbatical''' - Eric Lease Morgan, University of Notre Dame:
I will outline the set of applications/systems I wrote during my (not a) sabbatical. They include text mining tools, image processing & analysis hacks, MARC data enrichment activities, collection management decision-making scripts, etc. [[http://blogs.nd.edu/emorgan/2016/07/adjunct-status/ blog posting & one-page handout]]

'''Policies for Data Management''' -Abigail Goben, UIC:
I'll review what might be included in institutional policies and what to think about beyond data security for library data and library research data.

'''Exploring Born-Digital Data and Format Conversion Strategies with DROID and Plotly''' - Max Eckard, Bentley Historical Library:
I recently dug through about 5 years' worth of born-digital archives processed here at the Bentley. This gave me the opportunity to explore not only our born-digital data--and what it *really* looks like--but also the format conversion strategies we employ as part of our Ingest process. [[https://docs.google.com/presentation/d/13xvrQioT_jvqkTUWcnxb896c9EtpuqojqmsLvytdtiw/edit?usp=sharing slides]]

'''Wrapping an Image Server in Proxy and Cache Blankets''' - Graham Hukill, Wayne State University:
Serving images can be a digital object repository's bread and butter, but can touch on logistical and policy complexities. By wrapping the Python based "Loris" image server in a homegrown proxy, and caching with Varnish, we've been able to improve our image delivery, while keeping stakeholders happy as well. [[https://docs.google.com/presentation/d/1uE8l9Ly0M9d6WZvgs1VOULYnkeQrNf5QMef66tWIku8/edit?usp=sharing slides]]

'''Library Gamification in Theory and Practice''' - Ken Irwin, Wittenberg University:
People have been talking for years about bringing gamification ideas into library projects. I will talk about some gamification basics, how I've implemented some of them on one project, and we can discuss other areas in which gamification could be employed.
[[http://www6.wittenberg.edu/lib/ken/presentations/gamification.pptx Slides (PowerPoint)]]

'''Architecting Change in Repository Code''' - Debs Cane, Northwestern University & Avalon Media System:
Presentation on how NU & Indiana plans to “breakup” Avalon’s code (streaming A/V repository solution) over the next few months for easier use from outside coders. I'll also discuss why we’ve made the decisions we’ve made; and the choices we need to make in deciding future pathways for Avalon’s technical and community development.

'''Audio Preservation and Automating Transcription''' - Megan Kudzia, Michigan State University:
I have been working on a project to automate transcription for a digitized audio oral history collection. This talk will cover: how I automated transcription; how I got the finished audio files and transcripts into our Islandora digital repository; problems that I'm still trying to figure out solutions for; and what I learned along the way. Slides here: http://bit.ly/29RLZkS

'''Batch-loading Electronic Serials Records while Maintaining High Quality Bibliographic Control''' - Jamie Carlstone, University of Illinois at Urbana-Champaign: I will go over the workflow challenges of batch loading electronic serials MARC records while trying to maintain a high standard of quality. The process requires a circular workflow between OCLC Connexion, MarcEdit, Excel, and Microsoft Access that is far from ideal. I will also discuss a program I am working on that aims to improve upon this process.

'''Evergreen, From the Bottom Up''' - Dan Wells, Calvin College:
We'll explore how Evergreen works from the server side, with particular focus on its unique and powerful underlying framework, OpenSRF.

'''Evergreen, From the Top Down''' - Remington Steed, Calvin College:
We'll start with a brief overview of Evergreen's features, then dig beneath the surface at the software's various client architectures, including the evolution from XUL, to Dojo, to Angular.

'''Building for Browsing and Discovery with Wagtail, an open-source Django CMS''' -
David Bietila & Brad Busenius, University of Chicago Library:
As part our recent website redesign, we sought to build in paths by which users could move laterally between related pages, discovering relevant resources and services without returning to the home page or to the global navigation. We'll present on the data model that we specified to allow these new types of relationships, and on the Wagtail CMS, which enabled us to realize the site that we wanted.

'''Your Rights Statements Are a Disaster''' - amy buckland, University of Chicago
Chances are good the rights statements on your digital projects are some degree of special-snowflakeness that makes them impossible to decipher with an institutional decoder ring. Fix that. RightsStatements.org offers some great licenses that everyone should get on board with to ensure our digital collections are actually usable!

'''Change''' - Ranti Junus and Megan Kudzia, Michigan State University
How do we make our organization|unit|team more accepting of change? How do we overcome preference vs. best practice? How do we know when a change is not the right answer? These are probably questions that we asked when a change is needed. Let's discuss the approach we employed on making change happens, or when we see that our vision of change is not what we think it should be. What works or doesn't for you?

===Lightning Talks===
Have something cool to share but you don't want to be in front of the room for more than 5 minutes? Lightning talks are for you. Sign up now or at the conference:

''' VIAF AutoSuggest''' - Ralph LeVan

''' Getting Close to Accessible Slideshows''' - Margaret Heller

''' A Very Quick & Dirty & Potentially Embarrassing Look at Docker''' - Michael Klein

''' Code4Lib Journal: No you can't see our data''' - Carol Bean. [http://beanworks.clbean.com/2016/07/code4lib-midwest-lightning-talk-july-2016/ Blog post], and [http://beanworks.clbean.com/wp-content/uploads/2016/07/C4LJournal.pptx downloadable pptx file]

==Registration==
Registration is free, though we will cap at 40. List your name, affiliation, and email address here to register for the meeting. If you signed up and are unable to attend please remove your name or contact us, so that we can make room for others.

Contact Ryan Wick (ryanwick@gmail.com) with your preferred username to set up a Code4Lib wiki account, or ask Tod Olson (tod@uchicago.edu) to add your name to this list if you prefer not to set up an account.:

#Margaret Heller - Loyola University Chicago (mheller1@luc.edu)
#Eric Lease Morgan - University of Notre Dame (emorgan@nd.edu)
#Jamie Carlstone - University of Illinois at Urbana-Champaign (Jdc6@illinois.edu)
#Remington Steed - Hekman Library, Calvin College (rjs7@calvin.edu)
#Dan Wells - Hekman Library, Calvin College (dbw2@calvin.edu)
#Christy Karpinski - Newberry Library - karpinskic@newberry.org
#Carol Bean - beanworks@gmail.com
#Ranti Junus - Michigan State University (junus@mail.lib.msu.edu)
#Ken Irwin - Wittenberg University (kirwin -AT- wittenberg.edu)
#Matt Schultz - Grand Valley State University (schultzm -AT- gvsu.edu)
#Graham Hukill - Wayne State University (graham.hukill@wayne.edu)
#Ralph LeVan - OCLC Research (levan@oclc.org)
#Allan Berry - University of Illinois at Chicago (aberry3@uic.edu)
#Vaishnavi Gowrisankar - University of Illinois at Chicago (vgowri2@uic.edu)
#Max Eckard - Bentley Historical Library, University of Michigan (eckardm@umich.edu)
#Abigail Goben - University of Illinois at Chicago (agoben@uic.edu)
#Megan Kudzia - Michigan State University (kudzia AT msu.edu)
#Kristen Reid - Loyola University of Chicago (kreid8 AT luc.edu)
#Adam Strohm - Illinois Institute of Technology (astrohm@iit.edu)
#Max King - Illinois Institute of Technology (mking9@iit.edu)
#Alice Tippit - Northwestern Unversity (a-tippit@northwestern.edu)
#Michael North - Northwestern University (m-north@northwestern.edu)
#David Schober - Northwestern University (david.schober@northwestern.edu)
#Karen Didrickson - Northwestern University (karen.didrickson@northwestern.edu)
#Lisa Gonzalez - Private Academic Library Network of Indiana (lgonzalez@palni.edu)
#Christie Thomas - University of Chicago (clthomas@uchicago.edu)
#Brendan Quinn - Northwestern University (brendan-quinn at northwestern dot edu)
#Shelley Hostetler - Ex Libris (shelleyh@exlibrisgroup.com)
#Debs Cane - Northwestern University (deborah.cane@northwestern.edu)
#Maura Byrne - University of Chicago (byrne@uchicago.edu)
#David Farley - University of Chicago ( dfarley at uchicago dot edu )
#Keith Waclena - University of Chicago ( keith at lib dot uchicago dot edu )
#David Bietila - University of Chicago ( dbietila at uchicago dot edu )
#Brad Busenius - University of Chicago ( bbusenius at uchicago dot edu )
#Amy Buckland - University of Chicago (amybuckland@uchicago.edu)
#Kristin Martin - University of Chicago (kmarti@uchicago.edu)
#Jerry Kuang - Purdue University (jerrykuang.iit@gmail.com)
#Brittany Adams - Wheaton College (brittany.adams@wheaton.edu)
#Fred Seaton - University of Chicago (fseaton@uchicago.edu)
#Michael Klein - Northwestern University (michael.klein@northwestern.edu)

Friday-only:
#Chris Day - School of the Art Institute - cday2@saic.edu

==Code of Conduct==
Code4Lib seeks to provide a welcoming, fun, and safe community and conference experience and ongoing community for everyone. We do not tolerate harassment in any form. Discriminatory language and imagery (including sexual) is not appropriate for any event venue, including talks, or any community channel such as the chatroom or mailing list.
Harassment is understood as any behavior that threatens another person or group, or produces an unsafe environment. It includes offensive verbal comments or non-verbal expressions related to gender, gender identity, gender expression, sexual orientation, disability, physical appearance, body size, race, age, religious beliefs, sexual or discriminatory images in public spaces (including online), deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention.
===CodeOfConduct4Lib===
[https://github.com/code4lib/antiharassment-policy/blob/master/code_of_conduct.md Read and contribute to our full Code of Conduct document on GitHub]
===Duty Officers===
If you need any support during the conference, please call/email/find:
* Tod Olson (tod@uchicago.edu)
* Maura Byrne (byrne@uchicago.edu)
* Amy Buckland (amybuckland@uchicago.edu)

2016 Code4Lib Midwest Meeting

2016-05-26T10:32:43Z

Bean:

Code4Lib Chicago

2015-11-20T19:34:17Z

Bean:

A "hyperlocal" Code4Lib chapter, which has been in existence since around 2010.

=Resources=
* '''[https://groups.google.com/forum/#!forum/chicode4lib Google Group]'''
** Use this to chat about local issues, propose meetings, and let us know about local events.

 

=Fall 2015 Meeting=
* November 23, 2015
* Daley Library, UIC, Room 1-470
* Watch this space for details.
* '''[https://www.eventbrite.com/e/code4lib-chicago-fall-2015-meeting-tickets-18917137668 Register via EventBrite]'''
*: '''At this point, all tickets are taken'''; you are welcome to sign up for the waitlist. Allan will let you know as soon as anyone cancels.

==Schedule==

* 8:30
*: assemble / coffee
* 9:00
*: start / welcome
* 9:15
*: lightning talks (''see below'')

* 10:30
*: break

* 10:45
*: lightning talks (''continued'')
*: if lightning talks run short, we can commence with the Group Activity before lunch (''see below'')

* 12:00
*: group photo / lunch

* 1:00
*: library tour (''Meet in 1-470'')
* 1:30
*: Group activity; begin Breakout/Hackathon Sessions when complete (''see below'')

* 2:30
*: break

* 2:45
*: Breakout/Hackathon Sessions (''continued'')
* 4:15
*: wrap-up in 1-470 (sustaining energy & engagement?)
* 4:30
*: end
* 5:00
*: social at Jak's Tap http://jakstap.com/bar_and_grill_location_chicago_il.html

==Lightning Talks==
* If you have an idea, please sign up for a slot! These are quick, low-pressure talks, and you'll get good karma.
* [http://wiki.code4lib.org/2015_Lightning_Talks Examples of lightning talks] given at the last national Code4Lib.
* These are set as five minute slots, but at least a few will go over. So there's some flex time at the end.

===Slots===
* 9:15-9:20
*: Using LibCal for Library Hours--the easy way and the hard way
*: Margaret Heller, Loyola University Chicago

* 9:20-9:25
*: Using the OCLC API to Address the Challenge of Special Collections Backlog
*: Brittany Adams, Wheaton College

* 9:25-9:30
*: -

* 9:35-9:40
*: -

* 9:40-9:45
*: -

* 9:45-9:50
*: -

* 9:50-9:55
*: -

* 9:55-10:00
*: -

* 10:00-10:05
*: -

* 10:05-10:10
*: -

* 10:10-10:15
*: -

'''Break'''

* 10:45-10:50
*: Distant reading of texts from the HathiTrust, JSTOR, and/or EEBO
*: Eric Lease Morgan (Librarian-At-Large)

* 10:50-10:55
*: Explore Chicago Collections
*: Tracy Seneca and Kate Flynn, University of Illinois at Chicago

* 10:55-11:00
*: Creating Simple Event Displays from an RSS Feed using JavaScript
*: Paul Keith, Chicago Public Library

* 11:00-11:05
*: On EAD
*: Esther Verreau, University of Illinois at Chicago

* 11:05-11:10
*: TopicHub: identify content of interest in one repository and deposit it in another
*: Jeremy Prevost, Massachusetts Institute of Technology

* 11:10-11:15
*: Building History: exploring campus history with Neatline and Omeka
*: Adam Strohm, Illinois Institute of Technology

* 11:15-11:20
*: Garage Sessions: Automating deployment of CUNY's DH Box at the UWM Libraries' DH Lab
*: Ann Hanlon, University of Wisconsin-Milwaukee

* 11:20-11:25
*: -

* 11:25-11:30
*: -

* 11:30-11:35
*: -

* 11:35-11:40
*: -

* 11:40-11:45
*: -

==Group Activity==
* We're planning to try something a little different: a group mind-map, to warm up for the Breakout sessions.
* Write down on the specified Post-It color (provided): Your name, and one of the following topics:
** '''Green''': the thing which made me most proud this week
** '''Yellow''': the library technology I'm most excited about right now
** '''Pink''': the most annoying thing about my library's website
** '''Blue''': something I'd like to see at the next Chicago Code4Lib meetup
* Stick your post-it on the whiteboard in 1-470, ''close to another topic which you consider related''. Please feel free to move other peoples' post-it notes around!
* Now do another one! Do several!
* Talk amongst yourselves.

==Breakout/Hackathon Sessions==
* Up for debate: these are just some possible topics. We need four total.
* If you have an idea, add it to the list! If we end up with more than four, we will conduct a straw poll to determine the most relevant/popular.
* For inspiration, [http://wiki.code4lib.org/2015_Preconference_Proposals here is the list of pre-conference workshops] at the last national Code4Lib
 
===Meteor.js tutorial===
* In web dev circles, Meteor is the new hotness. It lets you make single-page apps which synchronize automatically between clients/users and the cloud/server. It also lets you kick out iOS and Android apps easily. It's pretty slick.
* Let's get a Meteor.js installation up and running. [https://www.meteor.com/tutorials/blaze/creating-an-app We'll do this tutorial], at least as much as we can. Be prepared for things not to work; let's figure them out together!
* No prior experience necessary, although familiarity with JavaScript will be useful.
* Macintosh/Linux only, unless you have experience using Cygwin on Windows.
* Allan Berry will lead (for better or worse)

===Metadata/data hackathon===
*A discussion around tools and workflows for cleaning up messy data; bring your own data sets to work on if you like.
* We will bring some metadata to share, but please bring your own if you have some! Messier the better!
* Kate Flynn will lead.

===???===
* -

===???===
* -

==UIC Environs: Lunch and Parking==
* '''[https://www.google.com/maps/d/edit?mid=z2JOTakXueSk.kSv_bxAdo3Xc&usp=sharing Lunch and parking map]'''
* Food options are mostly clustered in three places: Greektown (N of the freeway along Halsted), Taylor street (SW of campus), and University Village (S along Halsted).

==Evening social==
* Join us at [http://jakstap.com/bar_and_grill_location_chicago_il.html Jak's Tap] at 5:00pm, for beer and further discussion!
*: Jak's is within walking distance of UIC, a block or two north, across the freeway. Parking can be challenging up there, although meters are usually available on Jackson Blvd.

==Getting to UIC==
* Public Transit: Take the Blue Line west from the Loop; get off at the UIC-Halsted stop. Exit via Morgan Street (to your right as you exit the train). Walk south. The library will be on the left after you cross Harrison Street (address: 801 S Morgan St).
* '''[https://www.uic.edu/about/visit-directions More information on visiting UIC]''', including (better) mass-transit directions
* We have some 25 parking passes available: first come, first served. Otherwise parking will cost $13 for a full day.
* If you're driving, there are several parking lots available (marked on the above map); I recommend [https://goo.gl/QFHDNx the one south of campus (1135 Morgan)].
*: Note that no streets connect Harrison with Taylor, including Morgan, between Racine and Halsted; to reach the south lot, come up Morgan from Roosevelt.

== Circle Interchange difficulties==
* Circle Interchange (the confluence of I-90 and I-290 just NE of campus) construction is ongoing.
* Construction is causing traffic havoc nearby, especially near the corner of Harrison and Halsted. The Harrison bridge over I-90 doesn't currently exist. Best to avoid this area if possible.
* The Morgan street exit from I-290 has been closed for some time. [http://www.circleinterchange.org/under_construction/morgan_street.aspx According to IDOT]:
** Exiting access is prohibited from Westbound I-290/Congress Parkway
** From Southbound I-90/94 - exit Adams Street
** From Northbound I-90/94 - exit Ashland Avenue, backtrack east via Jackson Boulevard or Harrison Street

Code4Lib Journal Deadlines

2015-07-23T14:06:36Z

Bean: /* Deadlines for Issues */

''See also [[Code4Lib Journal Voting]]''

== Formula for calculating deadlines ==

A rough guideline based on recent issues:

{| border="1" cellpadding="2" cellspacing="0"
|-
! Weeks before
! Task
! Day offset
! On
|-
| style="text-align:right" | '''-18'''
| Call for proposals
| style="text-align:right" | -126
| Monday
|-
| style="text-align:right" | '''-14'''
| Proposals due
| style="text-align:right" | -94
| Friday
|-
| style="text-align:right" | '''-13'''
| Publication of previous issue
| style="text-align:right" | -91
| Monday
|-
| style="text-align:right" | '''-13'''
| Finish voting on proposals; notify authors
| style="text-align:right" | -87
| Friday
|-
| style="text-align:right" | '''-9'''
| First draft due
| style="text-align:right" | -59
| Friday
|-
| style="text-align:right" | '''-5'''
| Second draft due
| style="text-align:right" | -31
| Friday
|-
| style="text-align:right" | '''0'''
| Publication
| style="text-align:right" | 0
| Monday
|}

'''Note:''' Week numbers assume week begins on Monday.

'''See also:''' [[Code4Lib_Journal_Email_Templates]] (formerly at [http://groups.google.com/group/c4lj-articles/web/templates-for-email-responses Templates for Email Responses])

== Deadlines for Issues ==
Editors: see also http://tomkeays.com/library/c4ljpubdate/ for Tom's calculator

===Thirty-first issue===

* Call for proposals: Monday, September 21, 2015
* Second call for proposals: Thursday, October 8, 2015 (if necessary)
* Proposals due: Friday, October 23, 2015
* Proposals accepted: Friday, October 30, 2015
* First draft due: Monday, November 23, 2015
* Second draft due: Monday, December 21, 2015
* Publication date: Monday, January 25, 2016

===Thirtieth issue===
Coordinating editor for issue #30: Carol Bean

* Call for proposals: Thursday, June 11, 2015
* Second call for proposals: Thursday, July 2, 2015 (if necessary)
* Proposals due: Monday, July 13, 2015
* Proposals accepted: Monday, July 20, 2015
* First draft due: Monday, August 17, 2015
* Second draft due: Monday, September 14, 2015
* Publication date: Monday, October 19, 2015

===Twenty-ninth issue===
Coordinating editor for issue #29: Sara Amato

* Call for proposals: Wednesday, March 11, 2015
* Second call for proposals: Wednesday, April 1, 2015 (if necessary)
* Proposals due: Friday, April 10, 2015
* Proposals accepted: Monday, April 20, 2015
* First draft due: Monday, May 18, 2015
* Second draft due: Monday, June 15, 2015
* Publication date: Monday, July 13, 2015

===Twenty-eighth issue===
Coordinating editor for issue #28: Heidi Dowding

Special issue on diversity in library technology.

* Call for proposals: Wednesday, December 10, 2014
* Second call for proposals: Monday, January 5, 2015 (if necessary, adjusted from 31-Dec-2014)
* Proposals due: Monday, January 12, 2015
* Proposals accepted: Monday, January 19, 2015
* First draft due: Monday, February 16, 2015
* Second draft due: Monday, March 16, 2015
* Publication date: Wednesday, April 15, 2015

===Twenty-seventh issue===
Coordinating editor for issue #27: Terry Reese

*Call for proposals: Monday, September 27, 2014
*Second call for proposals: Monday, October 6, 2014 (if necessary)
*Proposals due: Friday, October 24, 2014
*Proposals accepted: Friday, October 31, 2014
*First draft due: Friday, November 21, 2014
*Second draft due: Friday, December 19, 2014
*Publication date: Monday, January 19, 2015

===Twenty-sixth issue===
Coordinating editor for issue #26: Kelley McGrath

*Call for proposals: Monday, June 9, 2014
*Second call for proposals: Monday, June 30, 2014 (if necessary)
*Proposals due: Friday, July 11, 2014
*Proposals accepted: Friday, July 18, 2014
*First draft due: Friday, August 15, 2014
*Second draft due: Friday, September 12, 2014
*Publication date: Monday, October 20, 2014

===Twenty-fifth issue===
Coordinating editor for issue #25: Dan Scott

*Call for proposals: Monday, March 10, 2014
*Second call for proposals: Monday, March 31, 2014 (if necessary)
*Proposals due: Friday, April 11, 2014
*Proposals accepted: Friday, April 18, 2014
*First draft due: Friday, May 16, 2014
*Second draft due: Friday, June 13, 2014
*Publication date: Monday, July 14, 2014

===Twenty-fourth issue===
Coordinating editor for issue #24: Ron Peterson

*Call for proposals: Monday, December 9, 2013
*Call for proposals #2: Monday, December 30, 2013 (if necessary)
*Proposals due: Friday, January 10, 2014
*Proposals accepted: Friday, January 17, 2014
*First draft due: Friday, February 14, 2014
*Second draft due: Friday, March 14, 2014
*Publication date: Monday, April 14, 2014

===Twenty-third issue===
Coordinating editor for issue #23: Shawn Averkamp
* Call for proposals: Monday, September 9, 2013
* Call for proposals #2: Monday September 30, 2013 (if necessary)
* Proposals due: Friday, October 11, 2013
* Proposals accepted: Friday, October 18, 2013
* First draft due: Friday, November 15, 2013
* Second draft due: Friday, December 13, 2013
* Publication date: Monday, January 13, 2014

===Twenty-second issue===
Coordinating editor for issue #22: Sara Amato
* Call for proposals: Monday, June 10, 2013
* Call for proposals #2: July 5, 2013 (if necessary)
* Proposals due: Friday, July 12, 2013
* Proposals accepted: Friday, July 19, 2013
* First draft due: Friday, August 16, 2013
* Second draft due: Friday, September 13, 2013
* Publication date: Monday, October 14, 2013

===Twenty-first issue===
Coordinating editor for issue #21: Terry Reese
* Call for proposals: Monday, March 11, 2013
* Call for proposals #2: Monday, April 1, 2013
* Proposals due: Friday, April 12, 2013
* Proposals accepted: Friday, April 19, 2013
* First draft due: Friday, May 17, 2013
* Second draft due: Friday, June 14, 2013
* Publication date: Monday, July 15, 2013

===Twentieth issue===
Coordinating editor for issue #20: [[User:DataGazetteer|Peter Murray]]
* Call for proposals:     Monday, December 10, 2012
* Call for proposals #2: Monday, January 7, 2013 (if necessary)
* Proposals due:          Friday, January 18, 2013
* Proposals accepted:     Friday, January 25, 2013
* First draft due:        Friday, February 22, 2013
* Second draft due:       Friday, March 22, 2013
* Publication date:       Monday, April 15, 2013

===Nineteenth issue===
Coordinating editor for issue #19: Andrew Darby
* Call for proposals: Monday, September 10, 2012
* Proposals due: Friday, October 12, 2012
* Proposals accepted: Friday, October 19, 2012
* First draft due: Friday, November 16, 2012
* Second draft due: Friday, December 14, 2012
* Publication date: Monday, January 14, 2013

===Eighteenth issue===
Coordinating editor for issue #18: Ron Peterson
* Call for proposals: Monday, May 28, 2012
* Proposals due: Friday, June 29, 2012
* Proposals accepted: Friday, July 6, 2012
* First draft due: Friday, August 3, 2012
* Second draft due: Friday, August 31, 2012
* Publication date: Monday, October 1, 2012

===Seventeenth issue===
Coordinating editor for issue #17: Tim Lepczyk
* Call for proposals: Wednesday, February 8, 2012
* Proposals due: Tuesday, February 28, 2012
* Proposals accepted: Tuesday, March 6, 2012
* First draft due: Tuesday, April 3, 2012
* Second draft due: Tuesday, May 1, 2012
* Publication date: Friday, June 1, 2012

===Sixteenth issue===
Coordinating editor for issue #16: Carol Bean
* Call for proposals: Monday, September 26, 2011
* Proposals due: Friday, October 28, 2011
* Proposals accepted: Friday, November 4, 2011
* First draft due: Friday, December 2, 2011
* Second draft due: Friday, December 30, 2011
* Publication date: Monday, January 30, 2012

===Fifteenth issue===
Coordinating editor for issue #15: Tod Olson
* Call for proposals: Monday, June 27, 2011
* Proposals due: Friday, July 29, 2011
* Proposals accepted: Friday, August 5, 2011
* First draft due: Friday, September 2, 2011
* Second draft due: Friday, September 30, 2011
* Publication date: Monday, October 31, 2011

===Fourteenth issue===

* Call for proposals: Monday, March 21, 2011
* Proposals due: Friday, April 22, 2011
* Proposals accepted: Friday, April 29, 2011
* First draft due: Friday, May 27, 2011
* Second draft due: Friday, June 24, 2011
* Publication date: Monday, July 25, 2011

===Thirteenth issue===

* Call for proposals: Monday, December 6, 2010
* Proposals due: Friday, January 7, 2011
* Proposals accepted: Friday, January 14, 2011
* First draft due: Friday, February 11, 2011
* Second draft due: Friday, March 11, 2011
* Publication date: Monday, April 11, 2011

===Twelfth issue===

* Call for proposals: Monday, August 16, 2010
* Proposals due: Friday, September 17, 2010
* Proposals accepted: Friday, September 24, 2010
* First draft due: Friday, October 22, 2010
* Second draft due: Friday, November 19, 2010
* Publication date: Monday, December 20, 2010

===Eleventh issue===

* Call for proposals: Monday, May 17, 2010
* Proposals due: Friday, June 18, 2010
* Proposals accepted: Friday, June 25, 2010
* First draft due: Friday, July 23, 2010
* Second draft due: Friday, August 20, 2010
* Publication date: Monday, September 20, 2010

=== Tenth issue ===

* Call for proposals: Monday, February 15, 2010
* Proposals due: Friday, March 19, 2010
* Proposals accepted: Friday, March 26, 2010
* First draft due: Friday, April 23, 2010
* Second draft due: Friday, May 21, 2010
* Publication date: Monday, June 21, 2010

=== Ninth issue ===

* Monday, November 9, 2009 -- Call for proposals
* Friday, December 11, 2009 -- Proposals due
* Friday, December 18, 2009 -- Finish voting on proposals, notify authors
* Friday, January 15, 2010 -- First draft due
* Friday, February 12, 2010 -- Second draft due
* Monday, March 15, 2010 -- Publication date

=== Eighth issue ===

* Monday, July 27 -- call for proposals
* Friday, August 14 -- proposals due
* Friday, August 21 -- finish voting on proposals; notify authors
* Friday, September 25 -- first draft due
* Friday, October 23 -- second draft due
* Monday, November 23 -- publication

=== Seventh issue ===

* Monday, February 16 -- call for proposals
* Friday, March 20 -- proposals due
* Monday, March 30 -- publication of issue 6
* Friday, March 27 -- finish voting on proposals; notify authors
* Friday, April 24 -- first draft due
* Friday, May 22 -- second draft due
* Monday, June 22 -- publication

=== Sixth issue ===

* Monday, November 10 -- call for proposals
* Friday, December 12 -- proposals due
* Monday, December 15 -- publication of issue 5
* Friday, December 19 -- finish voting on proposals; notify authors
* Friday, January 23 -- first draft due
* Friday, February 20 -- second draft due
* Monday, March 30 -- publication (originally scheduled for March 23)

=== Fifth issue ===

* Monday, August 18 -- call for proposals
* Friday, September 12 -- proposals due
* Friday, September 19 -- finish voting on proposals; notify authors
* Monday, September 22 -- issue 4 published
* Friday, October 17 -- first draft due
* Friday, November 14 -- second draft due
* Monday, December 15 -- publication

=== Fourth issue ===

* Friday, May 16 -- call for proposals
* Friday, June 20 -- extended proposal deadline (originally 6/13, before issue 3 is published)
* Friday, July 18 -- first draft due
* Friday, August 15 -- second draft due
* Monday, September 22 -- publication

=== Third issue ===

* Wednesday February 13th -- call for proposals
* Friday March 14th -- proposals due (after con, before issue 2)
* Friday April 25 -- first draft due
* Saturday June 21 -- publication (tentative)

=== Second issue ===

* Friday November 9th -- call for proposals
* Friday January 11 -- article draft deadline (or Thurs Jan 21, from EM)
* Thursday February 21 -- revisions/second draft deadline
* Friday March 21 -- publication (tentative)

=== First issue ===

* Friday August 31st -- call for proposals
* Friday October 12th -- article draft deadline
* Monday December 17th -- publication

[[Category: Code4Lib Journal]]

2015 Code4Lib Midwest Meeting

2015-07-11T01:46:48Z

Bean: removed my name from attendees --can't make it this time

== Code4Lib Midwest 2015 Meeting ==

Mark your calendars -- The Ohio State University Libraries will be hosting the Code4Lib Midwest 2015 meeting in Columbus, OH.

===Location===
Code4Lib MidWest meeting will be hosted by [http://library.osu.edu The Ohio State University Libraries].
* '''When''' - July 23 and July 24, 2015
* '''Where''' - [http://library.osu.edu Thompson Library], room 165 at OSU
* '''Who''' - contact person: Terry Reese (reese.2179@osu.edu )

===Logistics===

'''Suggested Hotels'''

* [http://www.theblackwell.com/ '''The Blackwell Inn'''] (2110 Tuttle Park Place, Columbus, OH 43210 :: +1 (614) 247-4000)

-The Blackwell Inn is located on campus, roughly 0.2 miles from the Thompson Library.

* [http://www.varsityinn.com/ '''The Varsity Inn South'''] (1445 Olentangy River Road, Columbus, OH 43212 :: +1 (614) 291-2983)

-The Varsity Inn South is roughly 1.7 miles from the Thompson Library.

* [http://www.uhdcolumbus.com/ '''Columbus Hospitality District''']

-Given the size of the University and University community, the University has it's own hospitality district, with lists to hotels and vendors that work closely with the University.

'''Directions, restaurants, and more'''

=== Schedule ===

==== Tentative Thursday, July 23rd ====

8:30 - 9:00: Check-in 

9:00 - 9:20: Welcome and House Keeping 

9:20 - 9:40: 
Jeffrey Mudge and David Malone (Wheaton College) 
The print/analog library transition to thousands upon thousands of digital resources has brought with it the need to manage associated URLs. Part of the management is to address issues of resource transience and attempts to create persistence. The Handle System is a specification for assigning, managing, and resolving persistent identifiers for digital objects. This presentation will provide background on Handle as well as some user tools that Wheaton College has created to simplify the creation, management, and deletion of Handles. 

9:40 - 10:00: ActiveSierra 
Sean Crowe and James Van Mil 
While waiting for a useful API from III, we've modeled useful bits of the Sierra database for use in Rails apps and in vanilla ruby. We'd be able to present the SierraDNA and ActiveRecord/ActiveModel frameworks with some of the tools we're building
 

10:00 - 10:20: "Automagic" Text Mining 
Eric Lease Morgan (University of Notre Dame) 
This presentation will describe and demonstrate how to "automagically" provide text mining services against content from the HathiTrust, EEBO, and JSTOR. Given specific metadata reports from these services, collections can be automatically created, indexed, analyzed, reported upon, and visualized. The result is the ability to "read distantly" against given reader-defined topics. Eric advocates this sort of service can help refine the definition of curation in a digital library context. 

10:20 - 10:40: Break/Networking 

10:40 - 11:00: 
Brittany Adams (Wheaton College) 
Code4LIb has many full-fledged coders, but there are others who are new to the library coding environment and may have limited access to common tools and operating systems often found in the coder's toolbox. As someone new to coding, Brittany Adams will show how PowerShell, which is part of the Windows OS, can be applied to various metadata projects. PowerShell can serve as the entry point for those unwilling or unable to dive in the deep-end of the Linux pool. 

11:00 - 12:00: Lightning Talks 

12:00 - 1:00: Lunch 

1:00 - 1:20 : 
Victor Replogle 
Title: Ball State Libraries Data Warehouse and Dashboard
Description: Gathering and presenting upon library statistics – a success story. User-selectable widgets share highlights from various system uses; custom reporting pages allow in-depth exploration of services consumed.
Most recently our inter-library loan application (ILLiad) is having its data extracted and transformed to facilitate quick and accurate calculations such as fill rate (able to be segmented by user category, request type, etc).
The presentation will highlight the steps that brought together various disparate data sources into one location, challenges overcome, and open-ended sharing based on audience interest.
 
1:30 - 5:00: Hands on Workshop...tentative topic; supporting digital humanities. 

look at topics related to text mining, topic models, n-grams, visualization 

6:30 - ? Social 

==== Tentative Friday, July 24th ====

8:00 - 8:30: Checkin 
8:30 - 8:45: Housekeeping 
8:45 - 9:45: Lightning Talks #2 (or 3 presentations depending on presentations submitted) 
9:45 - 10:00: Break 
10:00 - 10:20: 
Paul Butler, Ball State University 
EZProxy – The Canary in the Coal Mine for Compromised User Credentials 
EZProxy is one of the most used, and exposed, applications that library IT supports. Libraries use EZProxy to restrict access to some of our most coveted resources. As such, EZProxy can be used as one of the frontlines in identifying compromised user credentials. In this presentation Paul Butler (Library Technologies Support Analyst at Ball State University) will discuss the techniques, EZProxy customizations, and custom code Ball State University Libraries uses to identify compromised user credentials.
 
10:20 - 10:40: 
Mike Shallcross (Bentley Historical Library) 
ArchivesSpace-Archivematica-DSpace Workflow Integration - : Funded by the Andrew W. Mellon Foundation, this project seeks to expedite the ingest, description, and overall curation of digital archives by facilitating the creation and reuse of descriptive and administrative metadata among emerging platforms and streamlining the deposit of fully processed content into a digital preservation repository. This presentation will provide an overview of project goals and objectives and an update on current development work. 
10:40 - 11:00: Presentation #7 
11:00 - 12:00: Lightning Talks #3 / Tech petting zoo? 
12:00 - 12:30: Closing 

===Social Media Goodness===

Twitter hash tag: [https://twitter.com/search?q=c4lmw&src=typd #c4lmw]

===Technical Details===

* We'll have a Projector station with hookups, as well as a community PC Laptop with Powerpoint.
* Both a wired and wireless mic
* Wifi

==Programming Sign-up==

Code4Lib Midwest programming depends on the folks attending the conference. Please consider giving a presentation or lightning talk, or submitting your ideas for the hackfest/workshop.

Share what you are working on! Add your name and a description below. Please also let us know how long you'll need, and whether you prefer Wednesday or Thursday (or if it doesn't matter)

===Presentations or Workshops===

'''ActiveSierra''' - Sean Crowe and James Van Mil: while waiting for a useful API from III, we've modeled useful bits of the Sierra database for use in Rails apps and in vanilla ruby. We'd be able to present the SierraDNA and ActiveRecord/ActiveModel frameworks with some of the tools we're building (~1 hour?). If folks have access to their home III database systems, we could also host a workshop/hackfest around these tools.

'''Hands-on With Automagic Text Mining''' - This workshop provides a venue for participants to create their own "automagically" created text mining reports from the HathiTrust, EEBO, and JSTOR. Participants will create a set of content from the HathiTrust and "feed" it to system which will harvest, index, analyze, visualize, and report on the content. The process will then be repeated with content from EEBO and JSTOR. Participants are expected to have their own laptops, complete with an SSH terminal application and SFTP client. Access to a remote Linux machine will be provided. Familiarity with the Bash Shell is a plus but not necessary . --Eric Lease Morgan (University of Notre Dame)

'''PowerShell''' - Brittany Adams (Wheaton College): Code4LIb has many full-fledged coders, but there are others who are new to the library coding environment and may have limited access to common tools and operating systems often found in the coder's toolbox. As someone new to coding, Brittany Adams will show how PowerShell, which is part of the Windows OS, can be applied to various metadata projects. PowerShell can serve as the entry point for those unwilling or unable to dive in the deep-end of the Linux pool.

'''Handle: getting a grasp on URL management''' - Jeffrey Mudge and David Malone (Wheaton College): The print/analog library transition to thousands upon thousands of digital resources has brought with it the need to manage associated URLs. Part of the management is to address issues of resource transience and attempts to create persistence. The Handle System is a specification for assigning, managing, and resolving persistent identifiers for digital objects. This presentation will provide background on Handle as well as some user tools that Wheaton College has created to simplify the creation, management, and deletion of Handles.

'''ArchivesSpace-Archivematica-DSpace Workflow Integration''' - Mike Shallcross (Bentley Historical Library): Funded by the Andrew W. Mellon Foundation, this project seeks to expedite the ingest, description, and overall curation of digital archives by facilitating the creation and reuse of descriptive and administrative metadata among emerging platforms and streamlining the deposit of fully processed content into a digital preservation repository. This presentation will provide an overview of project goals and objectives and an update on current development work. (20 min. should suffice; Friday works fine.)

===Lightning Talks===
Have something cool to share but you don't want to be in front of the room for more than 5 minutes? Lightning talks are for you. Sign up now or at the conference:

'''Linked Data Fragments''' - James Van Mil - a small group in the Hydra world has started some work to address the issue of low availability of SPARQL endpoints. I can talk about the Linked Data Fragments concept and the work we're doing to apply it

'''Custom Reports in Google Analytics''' - Amelia Mowry

'''ILLiad at Ohio State''' - Angela Galvan - In 2014, the OSU Health Sciences Library migrated its Borrowing operation to University Libraries. This effectively ended the practice of using DOCLINE, the National Library of Medicine's interlibrary services platform, to obtain materials for health sciences patrons. I'll talk about why we made this decision and the wider impact to our users.

==Registration==
Registration is free. List your name, affiliation, and email address here to register for the meeting. If you signed up and are unable to attend please remove your name or contact us, so that we can make room for others.

Contact Ryan Wick (ryanwick@gmail.com) with your preferred username to set up a Code4Lib wiki account, or ask Terry Reese (reese.2179@osu.edu) to add your name to this list if you prefer not to set up an account.:

# David Malone - Wheaton College (david.malone%wheaton.edu)
# Ralph LeVan - OCLC (levan@oclc.org)
# Britain Woodman - University of Michigan (britainwumichedu)
# Angela Galvan - Ohio State University (galvan.as@gmail.com)
# Carrie Preston - Ohio University (prestonc@ohio.edu)
# Laurie Lee Moses - Center for Black Music Research at Columbia College Chicago (lmoses@colum.edu)
# Sasha Griffin - Denison University (griffins@denison.edu)
# Daniel Weddington - Berea College (Daniel_Weddington@berea.edu)
# Ken Irwin - Wittenberg University (kirwin@wittenberg.edu)
# Jane Wu - Otterbein University (jwu@otterbein.edu)
# James Van Mil - University of Cincinnati (vanmiljf@ucmail.uc.edu)
# Nathan Tallman - University of Cincinnati (tallmann@ucmail.uc.edu)
# Sean Crowe - University of Cincinnati (crowesn@ucmail.uc.edu)
# Jeffrey Mudge - Wheaton College (jeffrey.mudge@wheaton.edu)
# Karen Coombs - OCLC (coombsk@oclc.org)
# Ann Schoenenberger - Kenton County Public Library (Ann.Schoenenberger@kentonlibrary.org)
# Megan Kudzia - Albion College (moneill@albion.edu)
# Eric Lease Morgan - University of Notre Dame (emorgan@nd.edu)
# Peter Murray (jester@dltj.org)
# Jon Shank - Northwestern University (j-shank@northwestern.edu)
# Amelia Lauren Mowry - Wayne State University (amelia.mowry@wayne.edu)
# Mark Baggett - University of Tennessee (mbagget1@utk.edu)
# Rebecca Karlis - Marygrove College (rkarlis6534@marygrove.edu)
# Heidi Dowding (dowdingh@gmail.com)
# Ranti Junus (ranti.junus@gmail.com)
# Victor Replogle - Ball State University (vreplogle@bsu.edu)
# Paul Butler - Ball State University (prbutler@bsu.edu)
# Brittany Adams - Wheaton College (brittany.adams@wheaton.edu)
# Tod Olson - University of Chicago (tod@uchicago.edu)
# Kara Reuter - Worthington Libraries (kreuter@worthingtonlibraries.org)
# Stefan Langer - Worthington Libraries (slanger@worthingtonlibraries.org)
# Remington Steed - Hekman Library, Calvin College (rjs7@calvin.edu)
# Dan Wells - Hekman Library, Calvin College (dbw2@calvin.edu)
# Bill McMillin - University of Cincinnati (mcmillwh@ucmail.uc.edu)
# Carolyn Hansen - University of Cincinnati (hansencn@ucmail.uc.edu)
# Beth Snapp - Ohio State (snapp.6@osu.edu)
# Sarah Reid - Ohio State (reid.419@osu.edu)
# Ousmane Kebe - Ohio State (kebe.4@osu.edu)
# Dwight Scott - Ohio State (scott.1379@osu.edu)
# Russell Schelby - Ohio State (schelby.1@osu.edu)
# Chris Bartos - Ohio State (bartos.25@osu.edu)
# Friday only Michelle Gerry - Ohio State (gerry.8@osu.edu)
# Sue Rahnema - Ohio State (rahnema.3@osu.edu)
# Mike Shallcross - Bentley Historical Library, University of Michigan (shallcro@umich.edu)
The capacity of our venue requires us to cap participation at 50. Beyond that, please put your name, affiliation and email address on the wait list and we'll email you if a spot opens up for you.

===Waitlist===

#

2015 Code4Lib Midwest Meeting

2015-06-17T14:38:13Z

Bean: /* Registration */

Code4Lib Style Guide

2015-03-27T12:25:06Z

Bean: /* End of Document */

== A Note About This Guide ==

This is a brief style guide for authors. For information about styles and conventions used in marking up articles for WordPress, see: [http://wiki.code4lib.org/Code4Lib_Journal_WordPress_Input_Guidelines Code4Lib Journal WordPress Input Guidelines].
== Start of Article ==

Article titles are in Title Case -- all major words capitalized. The title is followed by an abstract, which will be pulled from the excerpt section lower on the post page, and byline of the form "by Author" or "by Author 1, Author 2, and Author 3".

== Headings ==

Major section headings are in "Title Case" -- all words capitalized, short words (the, a, in, up, over, about) should not be.
Subheadings are in "Sentence case" -- only the first word is capitalized.

== End of Document ==

=== Recommended Reference Style Discussion: ===

CSE has been voted in as the official recommended style (see: [[Citation_discussion]])

=== Endnote & Endnote References ===

A Bibliography and Notes section (if needed) immediately follows the last of the article's narrative text. References are indicated by author and year (Smith, 2007). Notes are indicated in the text by note number in square brackets [1]. More details can be found in the [[Code4Lib_Journal_WordPress_Input_Guidelines#Endnotes_style_and_HTML_coding|Input Guidelines for Endnotes]].

CSE reference style is the Journal's recommended style for bibliographies. An author may choose to use a different bibliographic reference style, but should follow that style accurately and consistently.

Authors can refer to this guide for using the [[CSE Reference Style]]

Where notes refer to articles, books, etc., that are not available by direct link, insert a [[COinS (layman's description) | COINS]] element after the note.

=== About the Author ===

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

=== Appendices ===

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

[[Category: Code4Lib Journal]]

2015 Preconference Proposals

2014-12-05T21:25:08Z

Bean: /* Linked Data Workshop */

== Preconference Schedule (draft) ==

Session titles in Italics means they have not been confirmed yet by presenters/workshop leaders.

This is a draft, and there may be some room switching when registration opens. Rooms will be confirmed the week before Code4Lib.

{| class="wikitable sortable"
|-
! Room (capacity) !! Morning (9 AM - Noon) !! Afternoon (1:30 PM - 4:30 PM)
|-
| '''Parlor A (30''') || Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable (Needs: projector, internet connection, and power strips) || Intro to Git & possibly beyond (Needs: projector/screen)
|-
| '''Parlor B (30)''' || Code Retreat (Needs whiteboard, dry-erase markers, projector) || Code Retreat (Needs whiteboard, dry-erase markers, projector)
|-
| '''Parlor C (30)''' || code4lib/Write The Docs barcamp (Needs: projector/screen, flipboard/whiteboard, power sources for laptops) || code4lib/Write The Docs barcamp
|-
| '''Grand Ballroom''' I (320) || CANCELLED: [UXtravaganza] || Presentations workshop (Needs: projector/screen)
|-
| '''Grand Ballroom''' II (200) || Visualizing Library Data (Needs: projector) || DPLA API Workshop (Bringing their own projector)
|-
| '''Galleria I (35)''' || Coding Custom Solutions for Every Department in the Library with File Analyzer (Needs PC laptop projection, monitor, internet access/wifi, attendees bring laptops) || Fail4Lib 2015 (Needs: projector/screen; Requested: Conference table seating, limit 20 attendants)
|-
| '''Galleria II (60)''' || RailsBridge: Intro to programming in Ruby on Rails (Needs: internet/wifi, overhead projection) || CollectionSpace: Getting it up and running at your museum (Needs: Projector)
|-
| '''Galleria III (35)''' || ''Replace yourself with a painfully complex bash script...or try Ansible'' || Intro to Docker
|-
| '''Studio (35)''' || Linked Data Workshop (Bringing their own projector) || Dive into Hydra (Needs: projector/screen; Requests: classroom style seating)
|-
| '''Directors (35)''' || Code4Arc (Needs: projector) || Code4Arc (Needs: projector)
|-
| '''Council (45)''' || Delivering and Preserving GIS Data (Projector, Video connector for MacBook Pro, wifi, power outlets) || A hands-on introduction to GeoBlacklight (Needs: projector, outlets; Requests: list of attendees)
|}

== Instructions ==
Thank you for considering proposing a pre-conference! Here are a few details:

* We will be taking pre-conference proposals until '''November 7, 2014'''
* If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu
* Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]
* If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)
* If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu
* '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions
* Please use the template for proposals provided in the pre-formatted block below

== Pre-conferences ==

===MORNING:===

=== Delivering and Preserving GIS Data ===

'''Half Day [Morning]'''

* Darren Hardy, Stanford University, drh@stanford.edu
* Jack Reed, Stanford University, pjreed@stanford.edu

We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# [[User:Ssimpkin|Sarah Simpkin]]
# Vicky Steeves
# Andrew Battista
# Peggy Griesinger
#
#
#
#
#
#

=== A hands-on introduction to GeoBlacklight ===

'''Half Day [Afternoon]'''

* Darren Hardy, Stanford University, drh@stanford.edu
* Jack Reed, Stanford University, pjreed@stanford.edu

GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop "Delivering and Preserving GIS Data".

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# [[User:Ssimpkin|Sarah Simpkin]]
# Vicky Steeves
# Andrew Battista
# Peggy Griesinger
#
#
#
#
#
#

===RailsBridge: Intro to programming in Ruby on Rails===

'''"Half-Day" [morning]'''

* Contact Carolyn Cole, Penn State University, carolyn@psu.edu
* Laney McGlohon, Stanford University, laneymcg@stanford.edu
* Additional instructors welcome

Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.

RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Maura Carbone
#Vicky Steeves
# Peggy Griesinger
# Mike Price
# Jean Rainwater
# Coral Sheldon-Hess
# Margaret Heller
# Bohyun Kim
# Mark Jarrell
#

=== Replace yourself with a painfully complex bash script...or try Ansible ===

'''Half Day [Morning]'''

* Chad Nelson, chad dot nelson @ lyrasis dot org
* Blake Carver, Blake dot carver @lyrasis dot org

Abstract:

[http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
# Ray Schwartz
# Coral Sheldon-Hess
# Kevin S. Clarke
# Joshua Gomez
# Charlie Morris
# Andy Mardesich
# Anna Headley
# Chelsea Lobdell
# Shaun Ellis
# Mark Mounts
# Chris Sharp

=== Intro to Docker ===

'''Half Day [Whenever]'''

* John Fink, McMaster University, john dot fink at gmail dot com
* Francis Kayiwa, University of Maryland Libraries , francis dot kayiwa at gmail dot com

Abstract:

[http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.

''Interested in Attending''

# Jim Hahn
# Joshua Gomez
# Bobbi Fox
# Ray Schwartz
# Megan Kudzia
# Coral Sheldon-Hess (pleeeeaaase put this in a different slot from Ansible!)
# Cary Gordon (uses Docker in production on AWS)
# Eric Phetteplace
# Esther Verreau
# Charlie Morris
# Anna Headley (voting for afternoon, compliments ansible)
# Shaun Ellis
# Mark Mounts

=== Code Retreat ===

'''Full Day'''

* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu
* Additional facilitators welcome; Especially if you have CodeRetreat experience.

Abstract:

"Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.
By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.
Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time." [http://coderetreat.org/about About Code Retreat]

''Interested in Attending''

# Mike Giarlo
# Charlie Morris
# Devon Smith
# Barbara Hui
# Carol Bean
#
#
#
#
#

=== Presentations workshop ===

'''"Half Day [Afternoon]"''' (but could be expanded based on interest)

* Chris Beer, Stanford University, cabeer@stanford.edu
* Additional facilitators welcome.

This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#Vicky Steeves
#
#
#
#
#
#
#
#
#

=== Dive into Hydra ===

'''"Half Day [Afternoon]"'''

* Justin Coyne, Data Curation Experts, justin@curationexperts.com
* Bess Sadler, Stanford University, bess@stanford.edu

Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend "RailsBridge" prior to this workshop.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Maura Carbone
# Peggy Griesinger
# Mike Price
# Jean Rainwater
# Sara Amato
#
#
#
#
#

=== code4lib/Write The Docs barcamp ===

'''"Full Day"''', with options for jumping in for half a day

* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu
* Write the Docs contacts: TBA

Abstract

Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization.

Remember, like metadata, documentation is a love note to the future.

More information about Write the Docs at http://conf.writethedocs.org/

There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

'''Full day'''
# Emily Lynema
#
#
#
#
#
#
#
#
#

'''Morning'''
# Ranti Junus
# Mita Williams
# Whitni Watkins
#
#
#
#
#
#
#

'''Afternoon'''
# Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon.
# Kevin S. Clarke
# Chris Sharp
#
#
#
#
#
#
#

=== Linked Data Workshop ===

'''"Half Day [morning]"'''

* Karen Estlund, University of Oregon, kestlund@uoregon.edu
* Tom Johnson, DPLA, tom@dp.la

Abstract:

Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Logan Cox
# Ray Schwartz
# Chris Hallberg
# Derek Merleaux
# Steven Anderson
# Eben English
# Mark Mounts
# Heather Pitts
# Andrew Woods
# Carol Bean

=== Code4Arc ===

'''"Full Day"''' (with options for half day participation)

* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com
* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org
* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com

Abstract:

What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how?

Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.

The schedule may include the following:

* Panel type conversations about the State of Art in Archives
* Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed
* Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)

Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with.

When signing up, please indicate if you are an end-user or a developer.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Laney McGlohon - developer
# Shaun Ellis
#
#
#
#
#
#
#
#

=== Fail4Lib 2015 ===

'''Half Day [TBD, probably afternoon]'''

* Andreas Orphanides, akorphan (at) ncsu.edu
* Jason Casden, jmcasden (at) ncsu.edu

Abstract:

Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.

This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)

The schedule may include the following:

* Case studies. Avoid our own mistakes by bearing witness to the failures of others.
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.
* Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.

''Interested in attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Ray Schwartz
# Charlie Morris
# Emily Lynema
#
#
#
#
#
#
#

=== Coding Custom Solutions for Every Department in the Library with File Analyzer ===

'''"Half Day [Morning]"'''

* Terry Brady, Georgetown University Library, twb27@georgetown.edu

Abstract

The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.

* Analyzing Marc Records for the Cataloging department
* Transferring ILS invoices for the University Account System for the Acquisitions department
* Delivering patron fines to the Bursar’s office for the Access Service department
* Summarizing student worker timesheet data for the Finance department
* Validating counter compliant reports for the Electronic Resources department
* Preparing ingest packages for the Digital Services department
* Validating checksums for the Preservation department

This hands on workshop will step through the components of the application framework. Workshop participants will install and develop custom File Analyzer tasks in this session.

The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Megan Kudzia
#
#
#
#
#
#
#
#
#

=== Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===

'''Half Day [Whenever]'''

* Karen A. Coombs, OCLC, coombsk@oclc.org

Abstract
Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.

We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Peggy Griesinger
# Ray Schwartz
#
#
#
#
#
#
#
#

=== CANCELLED: ''UXtravaganza'' ===
'''"Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]"'''

* William Hicks, University of North Texas, William.hicks@unt.edu
* Volunteers?

Abstract

I’m envisioning a 1/2 of full day for front-end developers, content strategy people, and other misfits with an interest in user experience, where we can talk about our shared problems, use cases, the state of current research, and play with each other’s sites. A half day seems doable, but if there’s significant enough interest we could push for a full? Here are a few of the things I think might be interesting to see happen:

* '''Analytics Share-fest:''' A few volunteers demonstrate data about their websites, catalogs, archival/digital collections. Most of us know our own sites but it would be interesting/validating to share this data with others so we can start to see commonalities between institutions, in certain kinds of systems, etc. For anyone using event tracking, or using click- or heat-maps, this would be a great opportunity to show off what people are seeing.

* '''UX Best Practices Catch Up:''' This spring I had the opportunity to attend a few days worth of usability workshops from the Nielsen-Norman Group, most of which was focused on mobile. I could distill down a lot of the information into an short presentation. Since this is a constantly moving area of research it would be nice to see a few people do other similar short presentations on some current trends/findings relevant to libraries, search, etc.

* '''Mobile Dev Lab:''' The UNT Libraries has been collecting a small set of smartphones and tablets for testing and development. Basically an [http://labup.org Open Device Lab]. We have about a dozen devices now of varying sizes, OS, OS Versions, + Google Glass. I’ll bring the devices, you can bring yours, and assuming we can get the wifi up and running we can test our sites/services with our big sausage fingers rather than pretending to do so through emulators and the one or two devices we each usually have on hand. If anyone is game they can do a tutorial on Browser-based Inspector Tools, Browser-Cams, or other testing services.

* '''The Eye’s Have It.''' The UNT Libraries is also in the process of acquiring an eye tracker and software for usability and other gaze-based research studies. We’ll take possession of it shortly after this pre-conference proposal is due and will have a couple of months to play with them before the conference. Assuming we can get our act together learning the device and can get past the technical hurdles of setting it up at the pre-conference, we could try to do some live demos on each other’s sites; i.e. You nominate a site/service, someone in the audience volunteers to wear the device, and we all watch them struggle do the tasks you request on a projector. Rinse. Lather. Repeat. It would hardly be scientific, but it sure would be fun. As a backup, if we have some sites nominated beforehand, I can run a few students at my library through some tasks here and we can show off the results to the crowd.

For those of you wanting to attend and help out, I’d really like to see some discussion on typography, writing for the web, “dealing with business/administrative requirements from on-high", maybe do some prototyping exercises, etc. Similarly if anyone is interested in doing some tutorials on bootstrap or how-to’s on running a usability test, that would be rad. But we need you to step up and steer part of the time for most of this to work, so if you are interested in some aspect, and especially if you want to volunteer to lead a bit of the time, contact me.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your
name (but not email address, etc.) here

# Ray Schwartz
# Andy Mardesich
# Chelsea Lobdell
# Eben English (1/2 day)
# Shaun Ellis (as attendee or volunteer)
# Whitni Watkins (as attendee or volunteer)
#
#
#
#

=== Intro to Git & possibly beyond ===

'''Half Day [Whenever]'''

* Erin Fahy, Stanford University, efahy@stanford.edu
* Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu

We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:

* What is a Distributed Version Control System?
* What's the difference between Git and Github.com?
* How to initialize new Git projects locally and on a remote server/Github
* Cloning/Forking existing projects and keeping up to date
* The wonderful world of Git branches
* Interactive rebasing
* Contributing code to existing projects & what pull requests are
* How to handle merge conflicts
* Overview of workflows and branch best practices
* (time allowing) Advanced git: pre/post hooks, submodules, anything else?

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Jeannie Graham
# Derek Merleaux
#
#
#
#
#
#
#
#

=== Visualizing Library Data ===

'''"Half Day [Morning||Afternoon]"'''

* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs

Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Ashley Blewer!
# Bobbi Fox
# Ray Schwartz
# Ranti Junus
# Eric Phetteplace
# Joshua Gomez
# Charlie Morris
# Andy Mardesich
# Tao Zhao
# Chris Hallberg
# Derek Merleaux
# Bohyun Kim
# Mark Jarrell
# Eben English
# Shaun Ellis
# Sarah Simpkin
# Mark Mounts
# Kathryn Stine

=== CollectionSpace: Getting it up and running at your museum ===

'''Half Day [Afternoon]'''

* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org
* TBD

This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org

Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.

''Interested in Attending''
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#
#
#
#
#
#
#
#
#
#

=== DPLA API Workshop: ===

'''Half Day [Afternoon]'''

* Audrey Altman, DPLA
* Mark Breedlove, DPLA
* Mark Matienzo, DPLA
* Tom Johnson, DPLA

The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Ranti Junus
# Jean Rainwater
# Mita Williams
# Margaret Heller
# Bohyun Kim
# Steven Anderson
# Shaun Ellis
# Sarah Simpkin
# Mark Jarrell
# Heather Pitts
# Kathryn Stine
# Andrew Woods

[[Category:Code4Lib2015]]

2015 Preconference Proposals

2014-12-05T21:22:16Z

Bean: /* Code Retreat */

== Preconference Schedule (draft) ==

Session titles in Italics means they have not been confirmed yet by presenters/workshop leaders.

This is a draft, and there may be some room switching when registration opens. Rooms will be confirmed the week before Code4Lib.

{| class="wikitable sortable"
|-
! Room (capacity) !! Morning (9 AM - Noon) !! Afternoon (1:30 PM - 4:30 PM)
|-
| '''Parlor A (30''') || Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable (Needs: projector, internet connection, and power strips) || Intro to Git & possibly beyond (Needs: projector/screen)
|-
| '''Parlor B (30)''' || Code Retreat (Needs whiteboard, dry-erase markers, projector) || Code Retreat (Needs whiteboard, dry-erase markers, projector)
|-
| '''Parlor C (30)''' || code4lib/Write The Docs barcamp (Needs: projector/screen, flipboard/whiteboard, power sources for laptops) || code4lib/Write The Docs barcamp
|-
| '''Grand Ballroom''' I (320) || CANCELLED: [UXtravaganza] || Presentations workshop (Needs: projector/screen)
|-
| '''Grand Ballroom''' II (200) || Visualizing Library Data (Needs: projector) || DPLA API Workshop (Bringing their own projector)
|-
| '''Galleria I (35)''' || Coding Custom Solutions for Every Department in the Library with File Analyzer (Needs PC laptop projection, monitor, internet access/wifi, attendees bring laptops) || Fail4Lib 2015 (Needs: projector/screen; Requested: Conference table seating, limit 20 attendants)
|-
| '''Galleria II (60)''' || RailsBridge: Intro to programming in Ruby on Rails (Needs: internet/wifi, overhead projection) || CollectionSpace: Getting it up and running at your museum (Needs: Projector)
|-
| '''Galleria III (35)''' || ''Replace yourself with a painfully complex bash script...or try Ansible'' || Intro to Docker
|-
| '''Studio (35)''' || Linked Data Workshop (Bringing their own projector) || Dive into Hydra (Needs: projector/screen; Requests: classroom style seating)
|-
| '''Directors (35)''' || Code4Arc (Needs: projector) || Code4Arc (Needs: projector)
|-
| '''Council (45)''' || Delivering and Preserving GIS Data (Projector, Video connector for MacBook Pro, wifi, power outlets) || A hands-on introduction to GeoBlacklight (Needs: projector, outlets; Requests: list of attendees)
|}

== Instructions ==
Thank you for considering proposing a pre-conference! Here are a few details:

* We will be taking pre-conference proposals until '''November 7, 2014'''
* If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu
* Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]
* If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)
* If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu
* '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions
* Please use the template for proposals provided in the pre-formatted block below

== Pre-conferences ==

===MORNING:===

=== Delivering and Preserving GIS Data ===

'''Half Day [Morning]'''

* Darren Hardy, Stanford University, drh@stanford.edu
* Jack Reed, Stanford University, pjreed@stanford.edu

We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# [[User:Ssimpkin|Sarah Simpkin]]
# Vicky Steeves
# Andrew Battista
# Peggy Griesinger
#
#
#
#
#
#

=== A hands-on introduction to GeoBlacklight ===

'''Half Day [Afternoon]'''

* Darren Hardy, Stanford University, drh@stanford.edu
* Jack Reed, Stanford University, pjreed@stanford.edu

GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop "Delivering and Preserving GIS Data".

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# [[User:Ssimpkin|Sarah Simpkin]]
# Vicky Steeves
# Andrew Battista
# Peggy Griesinger
#
#
#
#
#
#

===RailsBridge: Intro to programming in Ruby on Rails===

'''"Half-Day" [morning]'''

* Contact Carolyn Cole, Penn State University, carolyn@psu.edu
* Laney McGlohon, Stanford University, laneymcg@stanford.edu
* Additional instructors welcome

Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.

RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Maura Carbone
#Vicky Steeves
# Peggy Griesinger
# Mike Price
# Jean Rainwater
# Coral Sheldon-Hess
# Margaret Heller
# Bohyun Kim
# Mark Jarrell
#

=== Replace yourself with a painfully complex bash script...or try Ansible ===

'''Half Day [Morning]'''

* Chad Nelson, chad dot nelson @ lyrasis dot org
* Blake Carver, Blake dot carver @lyrasis dot org

Abstract:

[http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
# Ray Schwartz
# Coral Sheldon-Hess
# Kevin S. Clarke
# Joshua Gomez
# Charlie Morris
# Andy Mardesich
# Anna Headley
# Chelsea Lobdell
# Shaun Ellis
# Mark Mounts
# Chris Sharp

=== Intro to Docker ===

'''Half Day [Whenever]'''

* John Fink, McMaster University, john dot fink at gmail dot com
* Francis Kayiwa, University of Maryland Libraries , francis dot kayiwa at gmail dot com

Abstract:

[http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.

''Interested in Attending''

# Jim Hahn
# Joshua Gomez
# Bobbi Fox
# Ray Schwartz
# Megan Kudzia
# Coral Sheldon-Hess (pleeeeaaase put this in a different slot from Ansible!)
# Cary Gordon (uses Docker in production on AWS)
# Eric Phetteplace
# Esther Verreau
# Charlie Morris
# Anna Headley (voting for afternoon, compliments ansible)
# Shaun Ellis
# Mark Mounts

=== Code Retreat ===

'''Full Day'''

* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu
* Additional facilitators welcome; Especially if you have CodeRetreat experience.

Abstract:

"Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.
By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.
Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time." [http://coderetreat.org/about About Code Retreat]

''Interested in Attending''

# Mike Giarlo
# Charlie Morris
# Devon Smith
# Barbara Hui
# Carol Bean
#
#
#
#
#

=== Presentations workshop ===

'''"Half Day [Afternoon]"''' (but could be expanded based on interest)

* Chris Beer, Stanford University, cabeer@stanford.edu
* Additional facilitators welcome.

This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#Vicky Steeves
#
#
#
#
#
#
#
#
#

=== Dive into Hydra ===

'''"Half Day [Afternoon]"'''

* Justin Coyne, Data Curation Experts, justin@curationexperts.com
* Bess Sadler, Stanford University, bess@stanford.edu

Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend "RailsBridge" prior to this workshop.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Maura Carbone
# Peggy Griesinger
# Mike Price
# Jean Rainwater
# Sara Amato
#
#
#
#
#

=== code4lib/Write The Docs barcamp ===

'''"Full Day"''', with options for jumping in for half a day

* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu
* Write the Docs contacts: TBA

Abstract

Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization.

Remember, like metadata, documentation is a love note to the future.

More information about Write the Docs at http://conf.writethedocs.org/

There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

'''Full day'''
# Emily Lynema
#
#
#
#
#
#
#
#
#

'''Morning'''
# Ranti Junus
# Mita Williams
# Whitni Watkins
#
#
#
#
#
#
#

'''Afternoon'''
# Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon.
# Kevin S. Clarke
# Chris Sharp
#
#
#
#
#
#
#

=== Linked Data Workshop ===

'''"Half Day [morning]"'''

* Karen Estlund, University of Oregon, kestlund@uoregon.edu
* Tom Johnson, DPLA, tom@dp.la

Abstract:

Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Logan Cox
# Ray Schwartz
# Chris Hallberg
# Derek Merleaux
# Steven Anderson
# Eben English
# Mark Mounts
# Heather Pitts
# Andrew Woods
#

=== Code4Arc ===

'''"Full Day"''' (with options for half day participation)

* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com
* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org
* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com

Abstract:

What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how?

Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.

The schedule may include the following:

* Panel type conversations about the State of Art in Archives
* Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed
* Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)

Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with.

When signing up, please indicate if you are an end-user or a developer.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Laney McGlohon - developer
# Shaun Ellis
#
#
#
#
#
#
#
#

=== Fail4Lib 2015 ===

'''Half Day [TBD, probably afternoon]'''

* Andreas Orphanides, akorphan (at) ncsu.edu
* Jason Casden, jmcasden (at) ncsu.edu

Abstract:

Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.

This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)

The schedule may include the following:

* Case studies. Avoid our own mistakes by bearing witness to the failures of others.
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.
* Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.

''Interested in attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Ray Schwartz
# Charlie Morris
# Emily Lynema
#
#
#
#
#
#
#

=== Coding Custom Solutions for Every Department in the Library with File Analyzer ===

'''"Half Day [Morning]"'''

* Terry Brady, Georgetown University Library, twb27@georgetown.edu

Abstract

The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.

* Analyzing Marc Records for the Cataloging department
* Transferring ILS invoices for the University Account System for the Acquisitions department
* Delivering patron fines to the Bursar’s office for the Access Service department
* Summarizing student worker timesheet data for the Finance department
* Validating counter compliant reports for the Electronic Resources department
* Preparing ingest packages for the Digital Services department
* Validating checksums for the Preservation department

This hands on workshop will step through the components of the application framework. Workshop participants will install and develop custom File Analyzer tasks in this session.

The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Megan Kudzia
#
#
#
#
#
#
#
#
#

=== Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===

'''Half Day [Whenever]'''

* Karen A. Coombs, OCLC, coombsk@oclc.org

Abstract
Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.

We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Peggy Griesinger
# Ray Schwartz
#
#
#
#
#
#
#
#

=== CANCELLED: ''UXtravaganza'' ===
'''"Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]"'''

* William Hicks, University of North Texas, William.hicks@unt.edu
* Volunteers?

Abstract

I’m envisioning a 1/2 of full day for front-end developers, content strategy people, and other misfits with an interest in user experience, where we can talk about our shared problems, use cases, the state of current research, and play with each other’s sites. A half day seems doable, but if there’s significant enough interest we could push for a full? Here are a few of the things I think might be interesting to see happen:

* '''Analytics Share-fest:''' A few volunteers demonstrate data about their websites, catalogs, archival/digital collections. Most of us know our own sites but it would be interesting/validating to share this data with others so we can start to see commonalities between institutions, in certain kinds of systems, etc. For anyone using event tracking, or using click- or heat-maps, this would be a great opportunity to show off what people are seeing.

* '''UX Best Practices Catch Up:''' This spring I had the opportunity to attend a few days worth of usability workshops from the Nielsen-Norman Group, most of which was focused on mobile. I could distill down a lot of the information into an short presentation. Since this is a constantly moving area of research it would be nice to see a few people do other similar short presentations on some current trends/findings relevant to libraries, search, etc.

* '''Mobile Dev Lab:''' The UNT Libraries has been collecting a small set of smartphones and tablets for testing and development. Basically an [http://labup.org Open Device Lab]. We have about a dozen devices now of varying sizes, OS, OS Versions, + Google Glass. I’ll bring the devices, you can bring yours, and assuming we can get the wifi up and running we can test our sites/services with our big sausage fingers rather than pretending to do so through emulators and the one or two devices we each usually have on hand. If anyone is game they can do a tutorial on Browser-based Inspector Tools, Browser-Cams, or other testing services.

* '''The Eye’s Have It.''' The UNT Libraries is also in the process of acquiring an eye tracker and software for usability and other gaze-based research studies. We’ll take possession of it shortly after this pre-conference proposal is due and will have a couple of months to play with them before the conference. Assuming we can get our act together learning the device and can get past the technical hurdles of setting it up at the pre-conference, we could try to do some live demos on each other’s sites; i.e. You nominate a site/service, someone in the audience volunteers to wear the device, and we all watch them struggle do the tasks you request on a projector. Rinse. Lather. Repeat. It would hardly be scientific, but it sure would be fun. As a backup, if we have some sites nominated beforehand, I can run a few students at my library through some tasks here and we can show off the results to the crowd.

For those of you wanting to attend and help out, I’d really like to see some discussion on typography, writing for the web, “dealing with business/administrative requirements from on-high", maybe do some prototyping exercises, etc. Similarly if anyone is interested in doing some tutorials on bootstrap or how-to’s on running a usability test, that would be rad. But we need you to step up and steer part of the time for most of this to work, so if you are interested in some aspect, and especially if you want to volunteer to lead a bit of the time, contact me.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your
name (but not email address, etc.) here

# Ray Schwartz
# Andy Mardesich
# Chelsea Lobdell
# Eben English (1/2 day)
# Shaun Ellis (as attendee or volunteer)
# Whitni Watkins (as attendee or volunteer)
#
#
#
#

=== Intro to Git & possibly beyond ===

'''Half Day [Whenever]'''

* Erin Fahy, Stanford University, efahy@stanford.edu
* Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu

We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:

* What is a Distributed Version Control System?
* What's the difference between Git and Github.com?
* How to initialize new Git projects locally and on a remote server/Github
* Cloning/Forking existing projects and keeping up to date
* The wonderful world of Git branches
* Interactive rebasing
* Contributing code to existing projects & what pull requests are
* How to handle merge conflicts
* Overview of workflows and branch best practices
* (time allowing) Advanced git: pre/post hooks, submodules, anything else?

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Jeannie Graham
# Derek Merleaux
#
#
#
#
#
#
#
#

=== Visualizing Library Data ===

'''"Half Day [Morning||Afternoon]"'''

* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs

Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Ashley Blewer!
# Bobbi Fox
# Ray Schwartz
# Ranti Junus
# Eric Phetteplace
# Joshua Gomez
# Charlie Morris
# Andy Mardesich
# Tao Zhao
# Chris Hallberg
# Derek Merleaux
# Bohyun Kim
# Mark Jarrell
# Eben English
# Shaun Ellis
# Sarah Simpkin
# Mark Mounts
# Kathryn Stine

=== CollectionSpace: Getting it up and running at your museum ===

'''Half Day [Afternoon]'''

* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org
* TBD

This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org

Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.

''Interested in Attending''
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#
#
#
#
#
#
#
#
#
#

=== DPLA API Workshop: ===

'''Half Day [Afternoon]'''

* Audrey Altman, DPLA
* Mark Breedlove, DPLA
* Mark Matienzo, DPLA
* Tom Johnson, DPLA

The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Ranti Junus
# Jean Rainwater
# Mita Williams
# Margaret Heller
# Bohyun Kim
# Steven Anderson
# Shaun Ellis
# Sarah Simpkin
# Mark Jarrell
# Heather Pitts
# Kathryn Stine
# Andrew Woods

[[Category:Code4Lib2015]]

MDC

2012-09-11T10:24:41Z

Bean: /* Tentative Agenda */

= Maryland, Virginia, Washington D.C, etc. =

We want to bring the code{4}lib experience to the library community in the Maryland, Washington, D.C., and the great Commonwealth of Virginia area. Our hope is that meeting at the regional level will strengthen our local connections and develop more real world collaborative efforts.

== Next Meeting ==

'''When:''' Thursday, September 13th 4:30-5:30p meet, 5:30p-? Tasty beverages 
'''Where:'''Smithsonian Institution, National Museum of Natural History, 10th and Constitution Ave. NW, Washington DC 20004 Room CEG 15, Library Conference Room. [https://maps.google.com/maps?q=National+Museum+of+Natural+History,+Washington,+DC&hl=en&ll=38.891233,-77.026091&spn=0.003073,0.004554&sll=37.0625,-95.677068&sspn=50.777825,74.619141&oq=national+museum+o&t=h&hq=National+Museum+of+Natural+History,+Washington,+DC&radius=15000&z=18 Google Map] 
'''How:''' Nearest METRO stops are Federal Triangle on Blue/Orange, Archives/Navy Memorial on Yellow/Green or Metro Center (everything else.)

==Tentative Agenda==

Main Meeting 4:30

* Introductions (5 minutes)

* Show n' Tell (15 min each)

* Linked Data projects and schema.org +1

* Business matters

5:30ish - Iron Horse for a beer. or Asia Nine if beer is not your thing.

==Attending/Apologies==

Attending: Eric P., Brooke, Keri, Joel, Carol

== Previous Meetings ==
''''Wednesday, 27 June, 2012 4:30-6 Smithsonian National Museum of Natural History'''
Main Meeting
* Introductions (5 minutes)
* Anyone went to ALA? Did we miss anything? (10 min)
* Anyone going to wikimania? (Brooke is :D)
* Brooke is going to thatcamp, too. (http://thatcamp.org/)
* Lightning talks, demos & Discussion (25 min.)
* Katie Filbert: Wikidata Project
* (tentative) Michael Levy: Blacklight at USHMM
* backplane, dchud
* Requests, ideas, topics for future gatherings (10 min.)
* Selection of next venue and schedule (2 min. 30 sec.) "can't grab a beer until we get a volunteer(tm)"

5:30ish - Iron Horse for a beer.

''Attending/Regrets''
RSVP for 6/27: Rosy, Brooke, Joe, Dan, Josh, Keri, Joel, Katie, Terry, Michael, Carol, Nicholas, Ed

Paul @ UMW needs a ride from Fredericksburg in order to attend. Can anyone help him out??
Hmmm. Would he be cool with being picked up in the late morning and then taking the Metro from Alexandriaish? -Brooke
Eric P is workin' the late shift

'''Tuesday, 10 April, 2012 4-5 at [http://www.gwu.edu/ The George Washington University Gelman Library] in Foggy Bottom, DC 2130 H Street NW Washington DC 20052'''
 
4ish Main Meeting

* Introductions

* Selection of next venue and a thanks to this round's host

* Shameless plug for (http://wikimania2012.wikimedia.org/wiki/Main_Page Wikimania)

* Update on the wider code{4}lib community

* You know you want to talk about summat. Joe did it.

* Requests, ideas, and volunteers for topics for future gatherings

5ish Booze!

This meeting will be an ad hoc meeting for code{4}libMDC. If you have any bril ideas on how to fill the time, feel free to post them here. If no one posts anything, we'll enjoy an open exchange of ideas and updates on each other's work. All are welcome to attend. We hope to see you there!
'''Tuesday, 10 January, 2012 10:00AM to Noon at The George Washington University Gelman Library in Foggy Bottom, DC 2130 H Street NW Washington DC 20052'''

10 - Noon Main Meeting

* Introductions

* Selection of next venue and a thanks to this round's host

* Shameless plug for (http://www.dcla.org DCLA)

* Update on the wider code{4}lib community

* There will be a quick summary of FRBR, and a possible solution for aggregates which opens up a whole 'nother can of worms, but allows for some complex relationships to be described.

* Requests, ideas, and volunteers for topics for future gatherings
12:15–1:30 Lunch

There are a whole bunch of lunch spots near the Library. We didn't do lunch last time, but maybe we will this go.

'''Tuesday, 13 September, 2011 10-11.20ish at [http://library.arlingtonva.us/Departments/Libraries/LibrariesMain.aspx Arlington Public Library Central Branch] in Arlington, VA'''

With representatives present from Public, Academic, and Special Libraries, this looked to be a great start to rejuvenating the Chapter. (School Librarians, come out and play!) We had a great discussion about Linked Data. We reaffirmed that we'll hold quarterly meetings, and that doing so regularly will help keep things rolling. We hope to have diverse subjects to explore to keep everyone's interest. We'll hold off on formal governance until a larger group necessitates formality.

The Martin Luther King Library in the District would like help with [http://wikidc.org/wiki/Library_Lab Library Lab DC] if anyone would like to participate in that endeavour. This is also a wonderful place to go if you're looking for spot to house open collaboration.

There were a couple of interesting meetings and events to attend that we shared with one another.

Agenda

*10 - Noon Main Meeting
*Introductions
*Discussion of current venue.
*Shameless plug for (http://www.fallforthebook.org/ Fall for the Book)
*Hash out possibilities of other venues.
*Is the frequency right? Will quarterly meetings still work?
*Is the Chapter's problem indicative of fragmented general regional Library collaboration?
*Update on the wider code{4}lib community
*Discuss and invite folks to get involved with Library Lab DC at the DCPL
*Requests, ideas, and volunteers for topics for future gatherings
*Governance (do we want any?)
*12:15–1:30 Lunch

There are a whole bunch of lunch spots near the Library.

'''Wednesday, August 5, 2009 9:00am to 4:30pm at [http://nal.usda.gov/ National Agricultural Library] in Beltsville, MD'''

This meeting will be a joint meeting between code{4}libMDC and the DC Fedora Users Group.
This meeting is a joint meeting between the two groups, the first part of the day is code{4}libMDC meeting, centered on our stated goal to focus our second meeting on Fedora. This part of the meeting will follow the same time line as our initial meeting. After lunch, the meeting will be the initial meeting of the DC Fedora Users Group, however all are welcome and encouraged to attend. This part of the meeting will deal with the more technical aspects of Fedora.

'''Agenda'''

8:30–9:00 Coffee and sign-in

9:00–9:10 Welcome and Introductions

9:10–9:30 MarcEdit (Chuck Schoppet, NAL)

9:30-10:15 Fedora/DuraSpace/ Update (Thornton Staples) and DuraCloud project and LC pilot (Andrew Woods)

10:15–10:30 Break

10:30-12:00 Fedora Projects (NASA Goddard, University of Maryland, NLM)

12:00-12:15 code{4}libMDC business discussion

12:15–1:30 Lunch

1:30–4:30 Fedora Users Group technical discussions (with break)

Code4LibMDC had it's first meeting on Friday April 3, at the [http://nal.usda.gov/ National Agricultural Library] in Beltsville MD a.m. A total of 30 people attended including people from:
USDA,
NASA,
National Agricultural Library,
Library of Congress,
The Supreme Court Library,
The United States Senate Library,
National Oceanic Atmospheric Administration.

'''Contents'''

1. Welcome by Maria Pisa, NAL's Associate Director for Public Services
2. Individual introductions
3. Presentations
· John Doyle from the National Library of Medicine (NLM) gave a presentation on the use of [http://www.fedora-commons.org/ Fedora Commons] at NLM.
· Vernon Chapman from the Agriculture Network Information Center (AgNIC) gave a presentation on Searching [http://www.openarchives.org/OAI/openarchivesprotocol.html OAI-PMH] metadata with [http://lucene.apache.org/solr/ SOLR].
4. Discussion of Next steps for Code4LibMDC
· What will this group to be?
· Open to all in the library community.
· Showcase of library technology.
· Formula for sharing of code and ideas.
· A place for the development of collaborate projects.
· How to get involved?
· Prepare presentation on what you are currently working on:
· Preparing for a new ILS.
· Metadata translation
· Digital repositories
· Share ideas.
· Join smaller ad hoc meetings.
· Set up a local Listserv for this group.
5. Scheduling
· Meet quarterly for face to face meetings
· Hosted at sites in the area.
· Vote on location of meeting on local Listserv.

MDC

2012-09-11T10:19:52Z

Bean: /* Attending/Apologies */

= Maryland, Virginia, Washington D.C, etc. =

We want to bring the code{4}lib experience to the library community in the Maryland, Washington, D.C., and the great Commonwealth of Virginia area. Our hope is that meeting at the regional level will strengthen our local connections and develop more real world collaborative efforts.

== Next Meeting ==

'''When:''' Thursday, September 13th 4:30-5:30p meet, 5:30p-? Tasty beverages 
'''Where:'''Smithsonian Institution, National Museum of Natural History, 10th and Constitution Ave. NW, Washington DC 20004 Room CEG 15, Library Conference Room. [https://maps.google.com/maps?q=National+Museum+of+Natural+History,+Washington,+DC&hl=en&ll=38.891233,-77.026091&spn=0.003073,0.004554&sll=37.0625,-95.677068&sspn=50.777825,74.619141&oq=national+museum+o&t=h&hq=National+Museum+of+Natural+History,+Washington,+DC&radius=15000&z=18 Google Map] 
'''How:''' Nearest METRO stops are Federal Triangle on Blue/Orange, Archives/Navy Memorial on Yellow/Green or Metro Center (everything else.)

==Tentative Agenda==

Main Meeting 4:30

* Introductions (5 minutes)

* Show n' Tell (15 min each)

* Business matters

5:30ish - Iron Horse for a beer. or Asia Nine if beer is not your thing.

==Attending/Apologies==

Attending: Eric P., Brooke, Keri, Joel, Carol

== Previous Meetings ==
''''Wednesday, 27 June, 2012 4:30-6 Smithsonian National Museum of Natural History'''
Main Meeting
* Introductions (5 minutes)
* Anyone went to ALA? Did we miss anything? (10 min)
* Anyone going to wikimania? (Brooke is :D)
* Brooke is going to thatcamp, too. (http://thatcamp.org/)
* Lightning talks, demos & Discussion (25 min.)
* Katie Filbert: Wikidata Project
* (tentative) Michael Levy: Blacklight at USHMM
* backplane, dchud
* Requests, ideas, topics for future gatherings (10 min.)
* Selection of next venue and schedule (2 min. 30 sec.) "can't grab a beer until we get a volunteer(tm)"

5:30ish - Iron Horse for a beer.

''Attending/Regrets''
RSVP for 6/27: Rosy, Brooke, Joe, Dan, Josh, Keri, Joel, Katie, Terry, Michael, Carol, Nicholas, Ed

Paul @ UMW needs a ride from Fredericksburg in order to attend. Can anyone help him out??
Hmmm. Would he be cool with being picked up in the late morning and then taking the Metro from Alexandriaish? -Brooke
Eric P is workin' the late shift

'''Tuesday, 10 April, 2012 4-5 at [http://www.gwu.edu/ The George Washington University Gelman Library] in Foggy Bottom, DC 2130 H Street NW Washington DC 20052'''
 
4ish Main Meeting

* Introductions

* Selection of next venue and a thanks to this round's host

* Shameless plug for (http://wikimania2012.wikimedia.org/wiki/Main_Page Wikimania)

* Update on the wider code{4}lib community

* You know you want to talk about summat. Joe did it.

* Requests, ideas, and volunteers for topics for future gatherings

5ish Booze!

This meeting will be an ad hoc meeting for code{4}libMDC. If you have any bril ideas on how to fill the time, feel free to post them here. If no one posts anything, we'll enjoy an open exchange of ideas and updates on each other's work. All are welcome to attend. We hope to see you there!
'''Tuesday, 10 January, 2012 10:00AM to Noon at The George Washington University Gelman Library in Foggy Bottom, DC 2130 H Street NW Washington DC 20052'''

10 - Noon Main Meeting

* Introductions

* Selection of next venue and a thanks to this round's host

* Shameless plug for (http://www.dcla.org DCLA)

* Update on the wider code{4}lib community

* There will be a quick summary of FRBR, and a possible solution for aggregates which opens up a whole 'nother can of worms, but allows for some complex relationships to be described.

* Requests, ideas, and volunteers for topics for future gatherings
12:15–1:30 Lunch

There are a whole bunch of lunch spots near the Library. We didn't do lunch last time, but maybe we will this go.

'''Tuesday, 13 September, 2011 10-11.20ish at [http://library.arlingtonva.us/Departments/Libraries/LibrariesMain.aspx Arlington Public Library Central Branch] in Arlington, VA'''

With representatives present from Public, Academic, and Special Libraries, this looked to be a great start to rejuvenating the Chapter. (School Librarians, come out and play!) We had a great discussion about Linked Data. We reaffirmed that we'll hold quarterly meetings, and that doing so regularly will help keep things rolling. We hope to have diverse subjects to explore to keep everyone's interest. We'll hold off on formal governance until a larger group necessitates formality.

The Martin Luther King Library in the District would like help with [http://wikidc.org/wiki/Library_Lab Library Lab DC] if anyone would like to participate in that endeavour. This is also a wonderful place to go if you're looking for spot to house open collaboration.

There were a couple of interesting meetings and events to attend that we shared with one another.

Agenda

*10 - Noon Main Meeting
*Introductions
*Discussion of current venue.
*Shameless plug for (http://www.fallforthebook.org/ Fall for the Book)
*Hash out possibilities of other venues.
*Is the frequency right? Will quarterly meetings still work?
*Is the Chapter's problem indicative of fragmented general regional Library collaboration?
*Update on the wider code{4}lib community
*Discuss and invite folks to get involved with Library Lab DC at the DCPL
*Requests, ideas, and volunteers for topics for future gatherings
*Governance (do we want any?)
*12:15–1:30 Lunch

There are a whole bunch of lunch spots near the Library.

'''Wednesday, August 5, 2009 9:00am to 4:30pm at [http://nal.usda.gov/ National Agricultural Library] in Beltsville, MD'''

This meeting will be a joint meeting between code{4}libMDC and the DC Fedora Users Group.
This meeting is a joint meeting between the two groups, the first part of the day is code{4}libMDC meeting, centered on our stated goal to focus our second meeting on Fedora. This part of the meeting will follow the same time line as our initial meeting. After lunch, the meeting will be the initial meeting of the DC Fedora Users Group, however all are welcome and encouraged to attend. This part of the meeting will deal with the more technical aspects of Fedora.

'''Agenda'''

8:30–9:00 Coffee and sign-in

9:00–9:10 Welcome and Introductions

9:10–9:30 MarcEdit (Chuck Schoppet, NAL)

9:30-10:15 Fedora/DuraSpace/ Update (Thornton Staples) and DuraCloud project and LC pilot (Andrew Woods)

10:15–10:30 Break

10:30-12:00 Fedora Projects (NASA Goddard, University of Maryland, NLM)

12:00-12:15 code{4}libMDC business discussion

12:15–1:30 Lunch

1:30–4:30 Fedora Users Group technical discussions (with break)

Code4LibMDC had it's first meeting on Friday April 3, at the [http://nal.usda.gov/ National Agricultural Library] in Beltsville MD a.m. A total of 30 people attended including people from:
USDA,
NASA,
National Agricultural Library,
Library of Congress,
The Supreme Court Library,
The United States Senate Library,
National Oceanic Atmospheric Administration.

'''Contents'''

1. Welcome by Maria Pisa, NAL's Associate Director for Public Services
2. Individual introductions
3. Presentations
· John Doyle from the National Library of Medicine (NLM) gave a presentation on the use of [http://www.fedora-commons.org/ Fedora Commons] at NLM.
· Vernon Chapman from the Agriculture Network Information Center (AgNIC) gave a presentation on Searching [http://www.openarchives.org/OAI/openarchivesprotocol.html OAI-PMH] metadata with [http://lucene.apache.org/solr/ SOLR].
4. Discussion of Next steps for Code4LibMDC
· What will this group to be?
· Open to all in the library community.
· Showcase of library technology.
· Formula for sharing of code and ideas.
· A place for the development of collaborate projects.
· How to get involved?
· Prepare presentation on what you are currently working on:
· Preparing for a new ILS.
· Metadata translation
· Digital repositories
· Share ideas.
· Join smaller ad hoc meetings.
· Set up a local Listserv for this group.
5. Scheduling
· Meet quarterly for face to face meetings
· Hosted at sites in the area.
· Vote on location of meeting on local Listserv.

Code4Lib Journal Editorial Committee

2012-06-27T00:52:38Z

Bean: /* Current Editors */

This supplements the [http://journal.code4lib.org/editorial-committee Editorial Committee] page on the ''Journal'' website.

=== Current Editors ===

* Sara Amato (17-current)
* Shawn Averkamp (17-current)
* Carol Bean (1-current; CE 9, 16)
* Ed Corrado (1-current; CE 10)
* Andrew Darby (3-current; CE 8)
* Gabriel Farrell (10-current; CE 13)
* Elisa Graydon (17-current)
* Tom Keays (1-current; CE 7; TA 15-current)
* Kelley McGrath (8-current; CE 11)
* Peter Murray (17-current)
* Tod Olson (10-current; CE 15)
* Ron Peterson (1-current; CE 3, 12)
* Terry Reese (17-current)
* Jonathan Rochkind (1-current; CE 1)
* Ed Summers (14-current)

=== Former Editors ===

* Christine Schwartz (3-7; CE 6)
* Eric Lease Morgan (1-2; CE 2)
* Jodi Schneider (1-8)
* Jon Brinley (TA 1-14)
* Ken Varnum (1-10; CE 4)
* MJ Suhonos (10-14)
* Ryan Wick (TA 3-14)
* Emily Lynema (1-16, CE 5)
* Tim McGeary (10-16; CE 14)
* Tim Lepczyk (10-17, CE 17)

'''Note''': "CE" = Coordinating Editor and "TA" = Technical Administrator

[[Category: Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2012-06-27T00:52:16Z

Bean: /* Current Editors */

This supplements the [http://journal.code4lib.org/editorial-committee Editorial Committee] page on the ''Journal'' website.

=== Current Editors ===

* Sara Amato (17-current)
* Shawn Averkamp (17-current)
* Carol Bean (1-current; CE 9, 16)
* Ed Corrado (1-current; CE 10)
* Andrew Darby (3-current; CE 8)
* Gabriel Farrell (10-current; CE 13)
* Elisa Graydon (17-current)
* Tom Keays (1-current; CE 7; TA 15-current)
* Kelley McGrath (8-current; CE 11)
* Peter Murray (17-current)
* Tod Olson (10-current; CE 15)
* Ron Peterson (1-current; CE 3, 12)
* Terry Reese (17-current(
* Jonathan Rochkind (1-current; CE 1)
* Ed Summers (14-current)

=== Former Editors ===

* Christine Schwartz (3-7; CE 6)
* Eric Lease Morgan (1-2; CE 2)
* Jodi Schneider (1-8)
* Jon Brinley (TA 1-14)
* Ken Varnum (1-10; CE 4)
* MJ Suhonos (10-14)
* Ryan Wick (TA 3-14)
* Emily Lynema (1-16, CE 5)
* Tim McGeary (10-16; CE 14)
* Tim Lepczyk (10-17, CE 17)

'''Note''': "CE" = Coordinating Editor and "TA" = Technical Administrator

[[Category: Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2012-06-27T00:46:10Z

Bean: /* Former Editors */

This supplements the [http://journal.code4lib.org/editorial-committee Editorial Committee] page on the ''Journal'' website.

=== Current Editors ===

* Andrew Darby (3-current; CE 8)
* Carol Bean (1-current; CE 9, 16)
* Ed Corrado (1-current; CE 10)
* Gabriel Farrell (10-current; CE 13)
* Jonathan Rochkind (1-current; CE 1)
* Kelley McGrath (8-current; CE 11)
* Ron Peterson (1-current; CE 3, 12)
* Tod Olson (10-current; CE 15)
* Tom Keays (1-current; CE 7; TA 15-current)
* Ed Summers (14-current)

=== Former Editors ===

* Christine Schwartz (3-7; CE 6)
* Eric Lease Morgan (1-2; CE 2)
* Jodi Schneider (1-8)
* Jon Brinley (TA 1-14)
* Ken Varnum (1-10; CE 4)
* MJ Suhonos (10-14)
* Ryan Wick (TA 3-14)
* Emily Lynema (1-16, CE 5)
* Tim McGeary (10-16; CE 14)
* Tim Lepczyk (10-17, CE 17)

'''Note''': "CE" = Coordinating Editor and "TA" = Technical Administrator

[[Category: Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2012-06-27T00:45:48Z

Bean: /* Current Editors */

This supplements the [http://journal.code4lib.org/editorial-committee Editorial Committee] page on the ''Journal'' website.

=== Current Editors ===

* Andrew Darby (3-current; CE 8)
* Carol Bean (1-current; CE 9, 16)
* Ed Corrado (1-current; CE 10)
* Gabriel Farrell (10-current; CE 13)
* Jonathan Rochkind (1-current; CE 1)
* Kelley McGrath (8-current; CE 11)
* Ron Peterson (1-current; CE 3, 12)
* Tod Olson (10-current; CE 15)
* Tom Keays (1-current; CE 7; TA 15-current)
* Ed Summers (14-current)

=== Former Editors ===

* Christine Schwartz (3-7; CE 6)
* Eric Lease Morgan (1-2; CE 2)
* Jodi Schneider (1-8)
* Jon Brinley (TA 1-14)
* Ken Varnum (1-10; CE 4)
* MJ Suhonos (10-14)
* Ryan Wick (TA 3-14)
* Emily Lynema (1-16, CE 5)
* Tim Lepczyk (10-17, CE 17)

'''Note''': "CE" = Coordinating Editor and "TA" = Technical Administrator

[[Category: Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2012-06-27T00:45:08Z

Bean: /* Former Editors */

This supplements the [http://journal.code4lib.org/editorial-committee Editorial Committee] page on the ''Journal'' website.

=== Current Editors ===

* Andrew Darby (3-current; CE 8)
* Carol Bean (1-current; CE 9, 16)
* Ed Corrado (1-current; CE 10)
* Gabriel Farrell (10-current; CE 13)
* Jonathan Rochkind (1-current; CE 1)
* Kelley McGrath (8-current; CE 11)
* Ron Peterson (1-current; CE 3, 12)
* Tim McGeary (10-current; CE 14)
* Tod Olson (10-current; CE 15)
* Tom Keays (1-current; CE 7; TA 15-current)
* Ed Summers (14-current)

=== Former Editors ===

* Christine Schwartz (3-7; CE 6)
* Eric Lease Morgan (1-2; CE 2)
* Jodi Schneider (1-8)
* Jon Brinley (TA 1-14)
* Ken Varnum (1-10; CE 4)
* MJ Suhonos (10-14)
* Ryan Wick (TA 3-14)
* Emily Lynema (1-16, CE 5)
* Tim Lepczyk (10-17, CE 17)

'''Note''': "CE" = Coordinating Editor and "TA" = Technical Administrator

[[Category: Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2012-06-27T00:44:41Z

Bean: /* Current Editors */

This supplements the [http://journal.code4lib.org/editorial-committee Editorial Committee] page on the ''Journal'' website.

=== Current Editors ===

* Andrew Darby (3-current; CE 8)
* Carol Bean (1-current; CE 9, 16)
* Ed Corrado (1-current; CE 10)
* Gabriel Farrell (10-current; CE 13)
* Jonathan Rochkind (1-current; CE 1)
* Kelley McGrath (8-current; CE 11)
* Ron Peterson (1-current; CE 3, 12)
* Tim McGeary (10-current; CE 14)
* Tod Olson (10-current; CE 15)
* Tom Keays (1-current; CE 7; TA 15-current)
* Ed Summers (14-current)

=== Former Editors ===

* Christine Schwartz (3-7; CE 6)
* Eric Lease Morgan (1-2; CE 2)
* Jodi Schneider (1-8)
* Jon Brinley (TA 1-14)
* Ken Varnum (1-10; CE 4)
* MJ Suhonos (10-14)
* Ryan Wick (TA 3-14)
* Emily Lynema (1-16, CE 5)

'''Note''': "CE" = Coordinating Editor and "TA" = Technical Administrator

[[Category: Code4Lib Journal]]

Code4Lib Journal Publicity Venues

2012-06-27T00:42:25Z

Bean: /* Distributing Call for Submissions */

== Distributing Call for Submissions ==

* [http://listserv.syr.edu/archives/autocat.html AUTOCAT] autocat@listserv.syr.edu
* [https://listserv.nd.edu/cgi-bin/wa?A0=CODE4LIB Code4Lib] code4lib@listserv.nd.edu
* [http://listserv.uic.edu/htbin/wa?A0=drupal4lib Drupal4Lib] drupal4lib@listserv.uic.edu
* [http://lists.ala.org/wws/arc/lita-l LITA-L] lita-l@ala.org
* [http://metadatalibrarians.monarchos.com/ Metadatalibrarians] metadatalibrarians@lists.monarchos.com
* [https://listserv.nd.edu/cgi-bin/wa?A0=NGC4LIB NGC4Lib] ngc4lib@listserv.nd.edu
* <s>[http://mail.archive.org/pipermail/ol-lib/ Open Library] ol-lib@archive.org</s>
* [http://lists.sourceforge.net/lists/listinfo/oss4lib-discuss OSS4Lib] oss4lib-discuss@lists.sourceforge.net
* [https://listserv.nd.edu/cgi-bin/wa?A0=Usability4Lib Usability4Lib] usability4lib@listserv.nd.edu,
* [http://lists.webjunction.org/web4lib/ Web4Lib] web4lib@webjunction.org
* <s>[http://lists.webjunction.org/xml4lib/ XML4Lib] xml4lib@webjunction.org</s>
* [http://home.olemiss.edu/~noe/llfaq.html Law-Lib] law-lib@ucdavis.edu
* [http://www.mlanet.org/discussion/medlibl.html MedLib] medlib-l@list.uvm.edu
*[http://infoserv.inist.fr/wwsympa.fcgi/info/diglib IFLA DigLib] diglib@infoserv.inist.fr
*[http://mail.asis.org/mailman/listinfo/asis-l ASIS] asis-l@asis.org

Web Sites

* [http://liswire.com/ LISWire]. Go to the "[http://liswire.com/node/5 Submit a Release]" page and log in on the right side of the page. See [http://groups.google.com/group/c4lj-articles/t/e0b406daa4599c47 c4lj-articles] group for login information.

== Announcing Publication ==

Announce at above mailing lists and the code4lib website.

== Twitter Hashtag ==

Use #c4lj - its use is tracked in Twapper Keeper: http://twapperkeeper.com/hashtag/c4lj

[[Category: Code4Lib Journal]]

Code4Lib Journal WordPress Input Guidelines

2012-05-18T02:06:42Z

Bean: /* Code */

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

==Proofs for Authors==
A read-only login that is shared with authors can be found in the Administrivia tab.

==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></code> for emphasized text, <code></code> for strongly emphasized text, <code><blockquote></code> when quoting blocks of text. Avoid such monstrosities as <code></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>Figure 1. How to Caption an Image.
</nowiki>
In general, we bold the figure / table label using the strong tag:
<nowiki>Figure 1. How to Caption an Image.
</nowiki>

'''Uploading files manually'''

To upload images or other attached media / files, you will need to upload the content to our ibiblio host site manually.

To do that, sftp to ibiblio.org. See the Administrivia tab in the shared "C4LJ Article Tracking" doc for the username and password.

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. (see below)

'''Uploading media via WordPress'''

Before uploading files to WordPress, you will need to change permissions on the directory where you are putting the files.
# Login to c4ljeditor@login.ibiblio.org. Ask jrochkind for the password for the c4ljeditor account (or see this [http://groups.google.com/group/c4lj-articles/msg/fad004416f12ac25 post] on c4lj-articles).
# Change the directory to /public/vhost/c/c4lj/html/wp-content/uploads/
# WordPress tries to write the files to /public/vhost/c/c4lj/html/wp-content/uploads/[current year]/[current month]. If the current year or month directory does not yet exist, create them, "mkdir [current year]" or mkdir "[current month]" in the appropriate directory. Creating the directory while logged in makes the owner and group of the directory c4ljeditor and c4lj respectively. Wordpress will create the directories as nobody/nobody.
# Change the permissions on the [current month] directory from 755 to 777, "chmod 777 [current month]".
# In the WordPress editor, click the "Add an Image" button.
# Browse to and select your image/file.
# Click the Upload button.
# File in the Alternate text and Caption fields.
# Select the size of the image you want to display in the article.
# Click "Insert into Post".
# On the ibiblio.org server, change the permissions on the current month's directory back to 775, "chmod 775 [current month]"

===Code===

If code is attached as a file, follow the directions above for attached images, except:

* If there is not a folder for the author, create it, according to the guidelines above for images)
* Create a subfolder under the author's folder for "code". Insert code files here
* In the article link to the files using the path format http://path-to-the-server/media/issueNumber/authorname/code/filename (e.g., http://journal.code4lib.org/media/issue1/smith/code/something.pl)

Put all inline 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>

====Ampersand Issues====
We've had some problems with ampersand handling in the sourcecode sections. If you notice extra amp;s in your article, such as "&amp;amp;" and "&amp;amp;amp;", and you're comfortable using only the HTML editor for article entry, try checking the "Disable the visual editor when writing" box on your profile page in the admin.

==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/ .
** If using this generator, enter '(COinS)' in the box for COinS Default Text and 'http://journal.code4lib.org/coins' in the box for COinS Default Link at the bottom.
** Paste the output provided at the end of the reference in HTML. You will need to delete the line breaks inserted into the output created by the generator for it to work properly.
* Another option is to use the WP COinS plugin. Open the Code tab, put the cursor before the citation, and click COinS. Enter the appropriate information. This works so-so for journals, and not at all for books.
* COinS should really always have an ISSN or ISBN.
* Inside the span tag, put the string "(COinS)" with a link to our coins explanation page. Ie:

<pre><a href="http://journal.code4lib.org/coins">(COinS)</a></pre>

This is so the user without a browser extension will see that something is there she might be interested in, and get an explanation of COinS and how to make use of it.

===Endnotes style and HTML coding===
* Endnote number in text: The number is the link which appears in square brackets. Square brackets themselves are not part of the link. HTML coding for the text: '''[<a id="ref1" href="#note1">1</a>]'''

* The link should work both ways. So, the endnote will link back to the text. HTML coding for the endnote: '''[<a id="note1" href="#ref1">1</a>]'''

==Author Information==

Start off each article with a paragraph stating the name(s) of the author(s). Something simple like "By Jonathan Rochkind". If desired, the author's name can be a link to something appropriate.

End each article with a second-level header that says "About the Author(s)", with class="abouttheauthor" set. Then give a short paragraph about each author. We do want to have some kind of contact information published (personal web page, email address (obscured if desired), etc.) for each author.

There is a box beneath the article-editing box with the label "Author(s)". Anything you put in this field will be treated as the author of the article. This will show up in the ToC and in the syndication feeds. If you don't populate this field, WordPress will use the username of the editor, instead.

==Categories/Tags==
Posts will have "Uncagetorized" checked by default. Uncheck that box, and check the box next to the current issue, which will be a subcategory of "Issues." Do not check the "Issues" category. We generally do not add tags, except for Conference reviews

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

# Let everyone on the c4lj-articles list know you are getting ready to publish (so they can save and close any open articles).
# Log in to WordPress
# Make sure that all articles for the issue have the correct issue category selected and have been set to 'Pending Review'. Make sure that the "Uncategorized" and "Issues" categories are unchecked (only the specific issue should be selected).
# Sanity check: count the number of posts which should appear in the publish list
# Click on Posts -> Issues (on the left side)
# Click on "Publish" for the issue you'd like to publish.
## You'll get a list of every "Pending Review" article in that issue. Make sure the number of articles in the list matches your previous count. Don't see all the articles you think you should see? They could be still in Draft status, or not in the correct Issue category, or still have "Uncategorized" selected, or someone may still have it in edit mode. Go back to the posts list and make any necessary changes, and start from #5 again.
# 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).
## 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.
# Click on Posts -> Categories (on the left side)
# Make sure all three fields for the current issue are filled in and correct:
## The human-readable name of the issue goes into the Name field -- e.g., "Issue 15".
## The date of publication goes into the Description field -- e.g., "2011-10-31".
## The URL name goes into the Slug field -- e.g., "issue15" would give the URL of the issue, http://journal.code4lib.org/issues/issue15
# 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.
# Go to the Journal front page; check the number of articles is correct (again) and that they are in the right order. If there is a problem, go back to the admin interface, click on Posts -> Issues and click Unpublish for the issue. Make whatever corrections are needed and proceed from #5 again.
# Once the issue is finally published, go to [[Code4Lib_Journal_Entries_in_Directory_of_Open_Access_Journals]] and follow the directions to upload the issue metadata to DOAJ.
# Send out announcements (see [[Code4Lib_Journal_Publicity_Venues]])

==Corrections==
See [http://groups.google.com/group/c4lj-articles/browse_thread/thread/8eaabcff2d9c000d/a0aeeb9367fcea5f?lnk=gst&q=errata#a0aeeb9367fcea5f|the editors' list] for how to make corrections. Generally, use an Errata or Correction section at the end with information about the change that was made and have the actual text link down to that section. See also [[Code4Lib_Corrections]]

[[Category:Code4Lib Journal]]

Code4Lib Journal WordPress Input Guidelines

2012-05-18T02:06:17Z

Bean: /* Images and Attached Content */

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

==Proofs for Authors==
A read-only login that is shared with authors can be found in the Administrivia tab.

==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></code> for emphasized text, <code></code> for strongly emphasized text, <code><blockquote></code> when quoting blocks of text. Avoid such monstrosities as <code></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>Figure 1. How to Caption an Image.
</nowiki>
In general, we bold the figure / table label using the strong tag:
<nowiki>Figure 1. How to Caption an Image.
</nowiki>

'''Uploading files manually'''

To upload images or other attached media / files, you will need to upload the content to our ibiblio host site manually.

To do that, sftp to ibiblio.org. See the Administrivia tab in the shared "C4LJ Article Tracking" doc for the username and password.

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. (see below)

'''Uploading media via WordPress'''

Before uploading files to WordPress, you will need to change permissions on the directory where you are putting the files.
# Login to c4ljeditor@login.ibiblio.org. Ask jrochkind for the password for the c4ljeditor account (or see this [http://groups.google.com/group/c4lj-articles/msg/fad004416f12ac25 post] on c4lj-articles).
# Change the directory to /public/vhost/c/c4lj/html/wp-content/uploads/
# WordPress tries to write the files to /public/vhost/c/c4lj/html/wp-content/uploads/[current year]/[current month]. If the current year or month directory does not yet exist, create them, "mkdir [current year]" or mkdir "[current month]" in the appropriate directory. Creating the directory while logged in makes the owner and group of the directory c4ljeditor and c4lj respectively. Wordpress will create the directories as nobody/nobody.
# Change the permissions on the [current month] directory from 755 to 777, "chmod 777 [current month]".
# In the WordPress editor, click the "Add an Image" button.
# Browse to and select your image/file.
# Click the Upload button.
# File in the Alternate text and Caption fields.
# Select the size of the image you want to display in the article.
# Click "Insert into Post".
# On the ibiblio.org server, change the permissions on the current month's directory back to 775, "chmod 775 [current month]"

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

====Ampersand Issues====
We've had some problems with ampersand handling in the sourcecode sections. If you notice extra amp;s in your article, such as "&amp;amp;" and "&amp;amp;amp;", and you're comfortable using only the HTML editor for article entry, try checking the "Disable the visual editor when writing" box on your profile page in the admin.

==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/ .
** If using this generator, enter '(COinS)' in the box for COinS Default Text and 'http://journal.code4lib.org/coins' in the box for COinS Default Link at the bottom.
** Paste the output provided at the end of the reference in HTML. You will need to delete the line breaks inserted into the output created by the generator for it to work properly.
* Another option is to use the WP COinS plugin. Open the Code tab, put the cursor before the citation, and click COinS. Enter the appropriate information. This works so-so for journals, and not at all for books.
* COinS should really always have an ISSN or ISBN.
* Inside the span tag, put the string "(COinS)" with a link to our coins explanation page. Ie:

<pre><a href="http://journal.code4lib.org/coins">(COinS)</a></pre>

This is so the user without a browser extension will see that something is there she might be interested in, and get an explanation of COinS and how to make use of it.

===Endnotes style and HTML coding===
* Endnote number in text: The number is the link which appears in square brackets. Square brackets themselves are not part of the link. HTML coding for the text: '''[<a id="ref1" href="#note1">1</a>]'''

* The link should work both ways. So, the endnote will link back to the text. HTML coding for the endnote: '''[<a id="note1" href="#ref1">1</a>]'''

==Author Information==

Start off each article with a paragraph stating the name(s) of the author(s). Something simple like "By Jonathan Rochkind". If desired, the author's name can be a link to something appropriate.

End each article with a second-level header that says "About the Author(s)", with class="abouttheauthor" set. Then give a short paragraph about each author. We do want to have some kind of contact information published (personal web page, email address (obscured if desired), etc.) for each author.

There is a box beneath the article-editing box with the label "Author(s)". Anything you put in this field will be treated as the author of the article. This will show up in the ToC and in the syndication feeds. If you don't populate this field, WordPress will use the username of the editor, instead.

==Categories/Tags==
Posts will have "Uncagetorized" checked by default. Uncheck that box, and check the box next to the current issue, which will be a subcategory of "Issues." Do not check the "Issues" category. We generally do not add tags, except for Conference reviews

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

# Let everyone on the c4lj-articles list know you are getting ready to publish (so they can save and close any open articles).
# Log in to WordPress
# Make sure that all articles for the issue have the correct issue category selected and have been set to 'Pending Review'. Make sure that the "Uncategorized" and "Issues" categories are unchecked (only the specific issue should be selected).
# Sanity check: count the number of posts which should appear in the publish list
# Click on Posts -> Issues (on the left side)
# Click on "Publish" for the issue you'd like to publish.
## You'll get a list of every "Pending Review" article in that issue. Make sure the number of articles in the list matches your previous count. Don't see all the articles you think you should see? They could be still in Draft status, or not in the correct Issue category, or still have "Uncategorized" selected, or someone may still have it in edit mode. Go back to the posts list and make any necessary changes, and start from #5 again.
# 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).
## 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.
# Click on Posts -> Categories (on the left side)
# Make sure all three fields for the current issue are filled in and correct:
## The human-readable name of the issue goes into the Name field -- e.g., "Issue 15".
## The date of publication goes into the Description field -- e.g., "2011-10-31".
## The URL name goes into the Slug field -- e.g., "issue15" would give the URL of the issue, http://journal.code4lib.org/issues/issue15
# 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.
# Go to the Journal front page; check the number of articles is correct (again) and that they are in the right order. If there is a problem, go back to the admin interface, click on Posts -> Issues and click Unpublish for the issue. Make whatever corrections are needed and proceed from #5 again.
# Once the issue is finally published, go to [[Code4Lib_Journal_Entries_in_Directory_of_Open_Access_Journals]] and follow the directions to upload the issue metadata to DOAJ.
# Send out announcements (see [[Code4Lib_Journal_Publicity_Venues]])

==Corrections==
See [http://groups.google.com/group/c4lj-articles/browse_thread/thread/8eaabcff2d9c000d/a0aeeb9367fcea5f?lnk=gst&q=errata#a0aeeb9367fcea5f|the editors' list] for how to make corrections. Generally, use an Errata or Correction section at the end with information about the change that was made and have the actual text link down to that section. See also [[Code4Lib_Corrections]]

[[Category:Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2012-02-05T14:14:49Z

Bean: /* Current Editors */

This supplements the [http://journal.code4lib.org/editorial-committee Editorial Committee] page on the ''Journal'' website.

=== Current Editors ===

* Andrew Darby (3-current; CE 8)
* Carol Bean (1-current; CE 9, 16)
* Ed Corrado (1-current; CE 10)
* Gabriel Farrell (10-current; CE 13)
* Jonathan Rochkind (1-current; CE 1)
* Kelley McGrath (8-current; CE 11)
* Ron Peterson (1-current; CE 3, 12)
* Tim Lepczyk (10-current, CE 17)
* Tim McGeary (10-current; CE 14)
* Tod Olson (10-current; CE 15)
* Tom Keays (1-current; CE 7; TA 15-current)
* Ed Summers (14-current)

=== Former Editors ===

* Christine Schwartz (3-7; CE 6)
* Eric Lease Morgan (1-2; CE 2)
* Jodi Schneider (1-8)
* Jon Brinley (TA 1-14)
* Ken Varnum (1-10; CE 4)
* MJ Suhonos (10-14)
* Ryan Wick (TA 3-14)
* Emily Lynema (1-16, CE 5)

'''Note''': "CE" = Coordinating Editor and "TA" = Technical Administrator

[[Category: Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2012-02-05T14:13:39Z

Bean: /* Current Editors */

This supplements the [http://journal.code4lib.org/editorial-committee Editorial Committee] page on the ''Journal'' website.

=== Current Editors ===

* Andrew Darby (3-current; CE 8)
* Carol Bean (1-current; CE 9, 16)
* Ed Corrado (1-current; CE 10)
* Gabriel Farrell (10-current; CE 13)
* Jonathan Rochkind (1-current; CE 1)
* Kelley McGrath (8-current; CE 11)
* Ron Peterson (1-current; CE 3, 12)
* Tim Lepczyk (10-current, CE 17)
* Tim McGeary (10-current; CE 14)
* Tod Olson (10-current; CE 15)
* Tom Keays (1-current; CE 7; TA 15-current)

=== Former Editors ===

* Christine Schwartz (3-7; CE 6)
* Eric Lease Morgan (1-2; CE 2)
* Jodi Schneider (1-8)
* Jon Brinley (TA 1-14)
* Ken Varnum (1-10; CE 4)
* MJ Suhonos (10-14)
* Ryan Wick (TA 3-14)
* Emily Lynema (1-16, CE 5)

'''Note''': "CE" = Coordinating Editor and "TA" = Technical Administrator

[[Category: Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2012-02-05T14:12:04Z

Bean: /* Current Editors */

This supplements the [http://journal.code4lib.org/editorial-committee Editorial Committee] page on the ''Journal'' website.

=== Current Editors ===

* Andrew Darby (3-current; CE 8)
* Carol Bean (1-current; CE 9, 16)
* Ed Corrado (1-current; CE 10)
* Gabriel Farrell (10-current; CE 13)
* Jonathan Rochkind (1-current; CE 1)
* Kelley McGrath (8-current; CE 11)
* Ron Peterson (1-current; CE 3, 12)
* Tim Lepczyk (10-current)
* Tim McGeary (10-current; CE 14)
* Tod Olson (10-current; CE 15)
* Tom Keays (1-current; CE 7; TA 15-current)

=== Former Editors ===

* Christine Schwartz (3-7; CE 6)
* Eric Lease Morgan (1-2; CE 2)
* Jodi Schneider (1-8)
* Jon Brinley (TA 1-14)
* Ken Varnum (1-10; CE 4)
* MJ Suhonos (10-14)
* Ryan Wick (TA 3-14)
* Emily Lynema (1-16, CE 5)

'''Note''': "CE" = Coordinating Editor and "TA" = Technical Administrator

[[Category: Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2012-02-05T14:10:51Z

Bean: /* Former Editors */

This supplements the [http://journal.code4lib.org/editorial-committee Editorial Committee] page on the ''Journal'' website.

=== Current Editors ===

* Andrew Darby (3-current; CE 8)
* Carol Bean (1-current; CE 9, 16)
* Ed Corrado (1-current; CE 10)
* Gabriel Farrell (10-current; CE 13)
* Jonathan Rochkind (1-current; CE 1)
* Kelley McGrath (8-current; CE 11)
* Ron Peterson (1-current; CE 12)
* Tim Lepczyk (10-current)
* Tim McGeary (10-current; CE 14)
* Tod Olson (10-current; CE 15)
* Tom Keays (1-current; CE 7; TA 15-current)

=== Former Editors ===

* Christine Schwartz (3-7; CE 6)
* Eric Lease Morgan (1-2; CE 2)
* Jodi Schneider (1-8)
* Jon Brinley (TA 1-14)
* Ken Varnum (1-10; CE 4)
* MJ Suhonos (10-14)
* Ryan Wick (TA 3-14)
* Emily Lynema (1-16, CE 5)

'''Note''': "CE" = Coordinating Editor and "TA" = Technical Administrator

[[Category: Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2012-02-05T14:10:25Z

Bean: /* Former Editors */

This supplements the [http://journal.code4lib.org/editorial-committee Editorial Committee] page on the ''Journal'' website.

=== Current Editors ===

* Andrew Darby (3-current; CE 8)
* Carol Bean (1-current; CE 9, 16)
* Ed Corrado (1-current; CE 10)
* Gabriel Farrell (10-current; CE 13)
* Jonathan Rochkind (1-current; CE 1)
* Kelley McGrath (8-current; CE 11)
* Ron Peterson (1-current; CE 12)
* Tim Lepczyk (10-current)
* Tim McGeary (10-current; CE 14)
* Tod Olson (10-current; CE 15)
* Tom Keays (1-current; CE 7; TA 15-current)

=== Former Editors ===

* Christine Schwartz (3-7; CE 6)
* Eric Lease Morgan (1-2; CE 2)
* Jodi Schneider (1-8)
* Jon Brinley (TA 1-14)
* Ken Varnum (1-10; CE 4)
* MJ Suhonos (10-14)
* Ryan Wick (TA 3-14)
* Emily. Lynema (1-16, CE 5)

'''Note''': "CE" = Coordinating Editor and "TA" = Technical Administrator

[[Category: Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2012-02-05T14:07:44Z

Bean: /* Current Editors */

This supplements the [http://journal.code4lib.org/editorial-committee Editorial Committee] page on the ''Journal'' website.

=== Current Editors ===

* Andrew Darby (3-current; CE 8)
* Carol Bean (1-current; CE 9, 16)
* Ed Corrado (1-current; CE 10)
* Gabriel Farrell (10-current; CE 13)
* Jonathan Rochkind (1-current; CE 1)
* Kelley McGrath (8-current; CE 11)
* Ron Peterson (1-current; CE 12)
* Tim Lepczyk (10-current)
* Tim McGeary (10-current; CE 14)
* Tod Olson (10-current; CE 15)
* Tom Keays (1-current; CE 7; TA 15-current)

=== Former Editors ===

* Christine Schwartz (3-7; CE 6)
* Eric Lease Morgan (1-2; CE 2)
* Jodi Schneider (1-8)
* Jon Brinley (TA 1-14)
* Ken Varnum (1-10; CE 4)
* MJ Suhonos (10-14)
* Ryan Wick (TA 3-14)

'''Note''': "CE" = Coordinating Editor and "TA" = Technical Administrator

[[Category: Code4Lib Journal]]

Code4Lib Journal Entries in Directory of Open Access Journals

2012-02-05T14:04:25Z

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

SGzt3u Excellent article, I will take note. Many thanks for the story!

==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 (replace # with the current issue number) 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.

Note: if there are any sub-elements in the XML fields (e.g., HTML tags), the document will not validate. Also of note, Windows often creates character encoding that breaks with UTF-8, throwing an error on validation.

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