Code4Lib - User contributions [en]

Code4Lib Journal Editorial Committee

2021-09-17T16:07:21Z

RuthKitchinTillman: moved myself below, added Jon

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)
* Ed Corrado (1-current; CE 10)
* Andrew Darby (3-current; CE 8, 19, 34)
* Brighid M. Gonzales (37-current)
* Eric Hanson (37-current)
* Rebecca Hirsch (37-current)
* 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)
* Mark Swenson (37-current)
* Junior Tidal ( 23-current)

Technical Administrator: Jon Fackrell (52- )

=== Former Editors ===
* Carolin Moritz (44-46)
* Carol Bean (1-44; CE 9, 16, 30, 38)
* 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)
* Meghan Finch (23-43; CE 32)
* MJ Suhonos (10-14)
* Norma Palomino (37)
* 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)
* Ruth K Tillman (29-41; CE 35, 40; TA 30-52)
* 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 WordPress Customizations

2021-08-18T14:26:46Z

RuthKitchinTillman: /* Plugins */ edits to represent a few changes to plugins

==Plugins==

===Anti-Spam / Security===
;[http://akismet.com/ Akismet]
:Baseline anti-spam.
;[https://wordpress.org/plugins/antispam-bee/ Antispam Bee]
:After a number of experiments with anti-spam plugins, using this to augment Akismet seems to do a pretty good job.
;[https://wordpress.org/plugins/sucuri-scanner/ Sucuri Security Plugin]
:Scans for issues and sends updates when changes are made. This may be a bit overkill at times, but it also provides early detection of hacks.
;[https://wordpress.org/plugins/really-simple-ssl/ Really Simple SSL]
:We have an SSL certificate through ibiblio. This plugin makes sure Wordpress uses HTTPS appropriately.

===Metadata===
;DOAJ Export
:Provides information about your posts formatted according to the DOAJ Article XML Schema. (J. Brinley)
;[http://www.lackoftalent.org/michael/blog/unapi-wordpress-plug-in/ unAPI Server]
:Provides information about articles. Useful for Zotero users. (M. Giarlo)
;[http://www.wallandbinkley.com/quaedam/ COinS Quicktags Button] - no longer installed; buggy
:In the non-WYSIWYG editor, can be used to build a basic COinS tag. (P. Binkley)
:This was abandoned in favor of the generator at http://generator.ocoins.info/. However, the generator has now gone south and no longer seems to be supported.
;[Google XML Sitemaps https://wordpress.org/plugins/www-xml-sitemap-generator-org/]
:Generates search-engine friendly sitemaps.

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

===User Feedback===
;[http://contactform7.com/ Contact Form 7]
:Email contact form plugin.
;[http://www.callum-macdonald.com/code/wp-mail-smtp/ WP-Mail-SMTP]
:Reconfigures the wp_mail() function to use SMTP instead of mail() and creates an options page to manage the settings.

===URLs===
;C4LJ Remove Parents
:A customization of http://wordpress.org/extend/plugins/remove-parents/. Prettifies category URLs so that issues appear at <code>http://journal.code4lib.org/issues/issue1</code> instead of <code>http://journal.code4lib.org/issues/issues/issue1</code>. (J. Brinley)

===Workflow===
;[https://wordpress.org/plugins/classic-editor/ Classic Editor]
:Restores option for classic editor functionality for anyone who finds it more usable than the new mobile-focused editor.
;[https://github.com/code4lib/c4lj-issue-manager Issue Manager]
:Enables one-click publishing of new issues, and prevents articles from being published until their associated issue is published. (J. Brinley)
;[http://wordpress.org/extend/plugins/revision-cleaner/ Revision Cleaner]
:Auto clean your revisions that you don't needed any more.
;[http://www.im-web-gefunden.de/wordpress-plugins/role-manager/ Role Manager]
:Allows creation of custom roles and editing of roles' permissions. Used to create the Reviewer role, which can read Private articles, so that authors can see their articles before publication, and to prevent editors from publishing articles on accident.
;C4LJ Permissions
:Lets authors see pending posts. (J. Brinley)
;C4LJ Remove Parents
:Remove parent directories & "category" from category permalinks. (J. Brinley)
;Remove Special Word Characters
:Replaces special characters copied from MS Word with their entity equivalents. (J. Brinley)

==Upgrading==

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

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

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

[[Category:Code4Lib Journal]]

Code4Lib Editorial Committee Introduction

2020-12-18T13:48:06Z

RuthKitchinTillman: /* Wordpress (Required) */

[[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:

# Contact c4lj-articles@googlegroups.com and specify your preferred ''email'' and preferred ''username'' for the account. The technical administrator will create your account and send you information to login and reset the password.

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

2020-12-18T13:47:38Z

RuthKitchinTillman: /* Wordpress (Required) */ Fixing long out of date info.

[[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:

# Contact c4lj-articles@googlegroups.com and specify your preferred email and preferred username for the account. The technical administrator will create your account and send you information to login and reset the password.

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 Editorial Committee

2020-12-18T13:38:35Z

RuthKitchinTillman:

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)
* Ed Corrado (1-current; CE 10)
* Andrew Darby (3-current; CE 8, 19, 34)
* Brighid M. Gonzales (37-current)
* Eric Hanson (37-current)
* Rebecca Hirsch (37-current)
* 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)
* Mark Swenson (37-current)
* Junior Tidal ( 23-current)
* Ruth K Tillman (29-current; CE 35, 40; TA 30-)

=== Former Editors ===
* Carolin Moritz (44-46)
* Carol Bean (1-44; CE 9, 16, 30, 38)
* 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)
* Meghan Finch (23-43; CE 32)
* MJ Suhonos (10-14)
* Norma Palomino (37)
* 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

2020-12-18T13:38:16Z

RuthKitchinTillman:

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)
* Ed Corrado (1-current; CE 10)
* Andrew Darby (3-current; CE 8, 19, 34)
* Brighid M. Gonzales (37-current)
* Eric Hanson (37-current)
* Rebecca Hirsch (37-current)
* 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)
* Mark Swenson (37-current)
* Junior Tidal ( 23-current)
* Ruth K Tillman (29-current; CE 35; 40; TA 30-)

=== Former Editors ===
* Carolin Moritz (44-46)
* Carol Bean (1-44; CE 9, 16, 30, 38)
* 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)
* Meghan Finch (23-43; CE 32)
* MJ Suhonos (10-14)
* Norma Palomino (37)
* 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 Deadlines

2018-01-10T21:21:15Z

RuthKitchinTillman: adding a new issue I'm editing

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

===Fortieth issue===

Coordinating Editor: Ruth Kitchin Tillman
*Call for proposals: Friday, December 29, 2017
*Second call for proposals: Friday, January 19, 2018 (if necessary)
*Proposals due: Tuesday, January 30, 2018
*Proposals accepted: Tuesday, February 6, 2018
*First draft due: Tuesday, March 6, 2018
*Second draft due: Tuesday, April 3, 2018
*Publication date: Friday, May 4, 2018

===Thirty-ninth issue===
Coordinating Editor: Terry Reese
*Call for proposals: Monday, September 25, 2017
*Second call for proposals: Monday, October 16, 2017 (if necessary)
*Proposals due: Friday, November 3, 2017
*Proposals accepted: Friday, November 17, 2017
*First draft due: Friday, December 8, 2017
*Second draft due: Friday, January 5, 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 Deadlines

2016-09-26T19:30:33Z

RuthKitchinTillman: Added issue 35.

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

User:RuthKitchinTillman

2016-09-26T19:26:57Z

RuthKitchinTillman:

Digital Collections Librarian at the University of Notre Dame. C4L Journal Editor. Creator of [http://eadiva.com/ EADiva]. Interested in lowering barriers to technology.

2015 Game Night

2015-02-11T17:10:10Z

RuthKitchinTillman: Too burned out to be able to run a good game, sorry.

Right now we don't have much more than an idea, so interested parties are encouraged to come up with plans and update this page at will!
 

= Schedule =
Wednesday, February 11 at 6pm
 

= Where =
The Hilton has given us the use of the meeting rooms/ballroom for Game Night. We can't bring in outside food or drink but can order from the hotel restaurant.

For people interested in checking out the local gaming scene:
* [http://www.ggportland.com/#eventscal Guardian Games] (across the river from downtown but accessible via the Streetcar)
* [http://www.timevaultgames.com/TimeVaultGames%20retail%20store Time Vault Games] (about 2 blocks from the hotel)
 

= Games =
If you have games that you are planning on bringing, please add them to the table below:

{| class="wikitable"
|-
! Name !! Game !! # Players
|-
| [[User:Phette23|Eric Phetteplace]] || Netrunner || 2
|-
| [[User:dojobo|Dominic Bordelon]] || D&D 5th (i.e. current) edition -- We will play with the [http://dnd.wizards.com/articles/features/basicrules free basic rules] -- email if you want to sign up as a player; I will bring a few prepped chars for drop-ins || 3-7
|-
| [[User:sanderson|Steven Anderson]] || Citadels || 2-7
|-
| [[@starsplatter]] || Gloom || 2-7
|-
| [[User:Holly|Holly Becker]] || [https://boardgamegeek.com/boardgame/2655/hive Hive] || 2
|-
| [[User:Holly|Holly Becker]] || [https://boardgamegeek.com/boardgame/11971/cockroach-poker Cockroach poker] || 4-8
|-
| [[User:Holly|Holly Becker]] || [https://boardgamegeek.com/boardgame/8203/hey-s-my-fish Hey, that's my fish!] || 2-4
|-
| [[User:Holly|Holly Becker]] || [https://boardgamegeek.com/boardgame/148228/splendor Splendor] || 2-4
|-
| [[User:Holly|Holly Becker]] || [http://boardgamegeek.com/boardgame/28143/race-galaxy Race for the Galaxy] or [http://boardgamegeek.com/boardgame/43015/hansa-teutonica Hansa Teutonica] for something heavier || 2-6/3-5
|-
| [[User:rarleyj|Jon Earley]] || [http://www.worldofmunchkin.com/game/ Munchkin] || 3-6
|-
| [[User:efrierson|Eric Frierson]] || [http://magic.wizards.com Magic the Gathering] Decks || 2-4
|-
| [[User:efrierson|Eric Frierson]] || [http://boardgamegeek.com/boardgame/100901/flash-point-fire-rescue Flash Point] || 2-6
|-
| Mike Abrahamson || [http://boardgamegeek.com/boardgame/40692/small-world Small World] || 2-5
|-
| [[User:ThomGoodnow|Thom Goodnow]] || [http://www.alderac.com/doomtown Doomtown Reloaded] || 2-4
|-
|[[User:JonGorman| Jon Gorman]] || Rage deck with rules for stichlen and parade. || 2-5
|}

 

= Contact Info =
Any questions? Contact [mailto:michael.eaton@oregonstate.edu Mike Eaton]

 

= Planned Events =
Want to get a game group going? Add an event here.

== Munchkin ==
Register your name to play Munchkin. [http://www.worldofmunchkin.com/game/ Munchkin] 3 to ~6 players

'''When:''' 6pm

'''Where:''' Meet in the lobby then walk to a nearby coffee shop.

{| class="wikitable"
|-
! Spot !! Name
|-
| 1 || [[User:rarleyj|Jon Earley]] - organizer, @jonathanearley
|-
| 2 || [[User:Jamesvanmil|James Van Mil]] - Munchkin newb, @jamesvanmil
|-
| 3 ||
|-
| 4 ||
|-
| 5 ||
|-
| 6 ||
|-
| 7 ||
|}

User:RuthKitchinTillman

2015-02-04T16:42:31Z

RuthKitchinTillman: Created user page for myself.

Metadata Librarian for Cadence Group at NASA Goddard. Creator of [http://eadiva.com/ EADiva]. Interested in lowering barriers to technology.

2015 Game Night

2015-02-04T14:24:51Z

RuthKitchinTillman: added a game.

Right now we don't have much more than an idea, so interested parties are encouraged to come up with plans and update this page at will!
 

= Schedule =
Wednesday, February 11 at 6pm
 

= Where =
The Hilton has given us the use of the meeting rooms/ballroom for Game Night. We can't bring in outside food or drink but can order from the hotel restaurant.

For people interested in checking out the local gaming scene:
* [http://www.ggportland.com/#eventscal Guardian Games] (across the river from downtown but accessible via the Streetcar)
* [http://www.timevaultgames.com/TimeVaultGames%20retail%20store Time Vault Games] (about 2 blocks from the hotel)
 

= Games =
If you have games that you are planning on bringing, please add them to the table below:

{| class="wikitable"
|-
! Name !! Game !! # Players
|-
| [[User:Phette23|Eric Phetteplace]] || Netrunner || 2
|-
| [[User:dojobo|Dominic Bordelon]] || D&D 5th (i.e. current) edition -- [http://dnd.wizards.com/articles/features/basicrules free basic rules] -- email if you want to DM (I'd rather not) or sign up as a player || 3-7
|-
| [[User:sanderson|Steven Anderson]] || Citadels || 2-7
|-
| [[User:Holly|Holly Becker]] || [https://boardgamegeek.com/boardgame/2655/hive Hive] || 2
|-
| [[User:Holly|Holly Becker]] || [https://boardgamegeek.com/boardgame/11971/cockroach-poker Cockroach poker] || 4-8
|-
| [[User:Holly|Holly Becker]] || [https://boardgamegeek.com/boardgame/8203/hey-s-my-fish Hey, that's my fish!] || 2-4
|-
| [[User:Holly|Holly Becker]] || [https://boardgamegeek.com/boardgame/148228/splendor Splendor] || 2-4
|-
| [[User:Holly|Holly Becker]] || [http://boardgamegeek.com/boardgame/28143/race-galaxy Race for the Galaxy] or [http://boardgamegeek.com/boardgame/43015/hansa-teutonica Hansa Teutonica] for something heavier || 2-6/3-5
|-
| [[User:rarleyj|Jon Earley]] || [http://www.worldofmunchkin.com/game/ Munchkin] || 3-6
|-
| [[User:RuthKitchinTillman|Ruth Tillman]] || GUMSHOE game, either a [http://pelgranepress.com/site/?p=809 Bookhounds of London game] if we want to go professional or a [http://www.pelgranepress.com/?cat=153 Night's Black Agents] super-spy vampire killing thriller game (1d6 required, simple rules, I'll bring dice). Please let me know on Twitter if you're interested: @ruthbrarian. It'd help if I had time to prep. || 3-5
|}

 

= Contact Info =
Any questions? Contact [mailto:michael.eaton@oregonstate.edu Mike Eaton]

 

= Planned Events =
Want to get a game group going? Add an event here.

== Munchkin ==
Register your name to play Munchkin. [http://www.worldofmunchkin.com/game/ Munchkin] 3 to ~6 players

'''When:''' 6pm

'''Where:''' Meet in the lobby then walk to a nearby coffee shop.

{| class="wikitable"
|-
! Spot !! Name
|-
| 1 || [[User:rarleyj|Jon Earley]] - organizer, @jonathanearley
|-
| 2 ||
|-
| 3 ||
|-
| 4 ||
|-
| 5 ||
|-
| 6 ||
|-
| 7 ||
|}

MDC

2014-08-04T15:07:59Z

RuthKitchinTillman: I moved my talk from 5-min lightning talk to 20 min talk.

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

We met quarterly throughout 2012. We've enjoyed a number of in depth technical presentations on a variety of topics. Meetings have been free to attend. Past host institutions have been the Smithsonian, GWU, and the Arlington Public Library. We're looking forward to a 2013 of the same calibre. If you are in the area, please do feel free to drop in. If you are unable to make it in person, check with the hosts to see if distance participation is an option. We did have one distance person with us at one of the Smithsonian meet ups. :)

== Next Meeting ==

===Code4Lib DC 2014 unconference===

August 11-12, 2014 
Gelman Library 
George Washington University 

Connect with fellow code-interested cultural heritage professionals at two side-by-side events: a DC-area code4lib unconference and an introduction to programming workshop. As typical of unconferences, the content and activities of the day are determined by the attendees. Bring your ideas! We encourage everyone to consider giving a 10-20 minute talk, a lightning talk, lead a workshop, or organize another activity.

The two events are intended to provide an inclusive, welcoming environment, supported by the [http://www.diglib.org/about/code-of-conduct/ DLF Code of Conduct]. The schedule includes opportunities for the attendees in each track to meet each other, including a plenary opening session, shared lightning talks, Day 2 afternoon unconference events, and combined coffee/lunch/snack breaks.

These events are sponsored by the Digital Library Federation and the GW Libraries.

'''Details, schedule, and registration''': [http://library.gwu.edu/code4lib-dc-2014 GW Libraries site].

'''20-minute talks - feel free to sign up'''

* Dan Chudnov (GW Libraries), "7±2 things code4libbers should know about data science"
* Mark Matienzo (Digital Public Library of America): "What We Learned From Aggregating Metadata for 7 Million Items"
* Bohyun Kim (Univ. of Maryland, Baltimore): "Where to start when your library wants an online payment option"
* Francis Kayiwa, "Monitoring Sucks"
* David Anderson (National Library of Medicine): "Linked Data at NLM"
* Ben Wallberg (UMD Libraries), "Research Services at UMD Libraries"
* Ruth Kitchin Tillman (EADiva, NASA Goddard), "EAD 2002 to EAD3: the N big changes"

'''5-minute talks - feel free to sign up'''

'''1.5 or 3 hour workshops - feel free to sign up'''

* Jason Griffey, Hacking on Hardware (3 hours): Come and join me for an afternoon filled with circuits and silicon! We'll be learning the basics of breadboards and simple circuits, and building our own input/output systems with Arduino. Learn the basics of programming to the Arduino...hardware will be provided, although you will need your own laptop (or are comfortable team learning with someone else). If you are planning to attend this hardware hacking afternoon, you will need to have the Arduino IDE 1.0.5 installed. The IDE can be downloaded from http://arduino.cc/en/Main/Software.

== Last Meeting ==

'''When:''' Thursday, September 13th 2012 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] '''Please meet near the totem pole in the Constitution Ave Lobby''' 
'''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)
** Terry: File Analyzer https://github.com/usnationalarchives/File-Analyzer and/or DSpace web tools!

** 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 (SIL), Joel (SIL), Carol, Ben Wallberg (UMd), Terry Brady G'town

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

2014-07-08T23:21:58Z

RuthKitchinTillman: Added my lightning talk.

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

We met quarterly throughout 2012. We've enjoyed a number of in depth technical presentations on a variety of topics. Meetings have been free to attend. Past host institutions have been the Smithsonian, GWU, and the Arlington Public Library. We're looking forward to a 2013 of the same calibre. If you are in the area, please do feel free to drop in. If you are unable to make it in person, check with the hosts to see if distance participation is an option. We did have one distance person with us at one of the Smithsonian meet ups. :)

== Next Meeting ==

===Code4Lib DC 2014 unconference===

August 11-12, 2014 
Gelman Library 
George Washington University 

Connect with fellow code-interested cultural heritage professionals at two side-by-side events: a DC-area code4lib unconference and an introduction to programming workshop. As typical of unconferences, the content and activities of the day are determined by the attendees. Bring your ideas! We encourage everyone to consider giving a 10-20 minute talk, a lightning talk, lead a workshop, or organize another activity.

The two events are intended to provide an inclusive, welcoming environment, supported by the [http://www.diglib.org/about/code-of-conduct/ DLF Code of Conduct]. The schedule includes opportunities for the attendees in each track to meet each other, including a plenary opening session, shared lightning talks, Day 2 afternoon unconference events, and combined coffee/lunch/snack breaks.

These events are sponsored by the Digital Library Federation and the GW Libraries.

'''Details, schedule, and registration''': [http://library.gwu.edu/code4lib-dc-2014 GW Libraries site].

'''20-minute talks - feel free to sign up'''

* Dan Chudnov (GW Libraries), "7±2 things code4libbers should know about data science"
* Mark Matienzo (Digital Public Library of America): "What We Learned From Aggregating Metadata for 7 Million Items"

'''5-minute talks - feel free to sign up'''

* Ruth Kitchin Tillman (EADiva, NASA Goddard), "EAD 2002 to EAD3: the N big changes"

'''1.5 or 3 hour workshops - feel free to sign up'''

* Jason Griffey, Hacking on Hardware (3 hours): Come and join me for an afternoon filled with circuits and silicon! We'll be learning the basics of breadboards and simple circuits, and building our own input/output systems with Arduino. Learn the basics of programming to the Arduino...hardware will be provided, although you will need your own laptop (or are comfortable team learning with someone else).

== Last Meeting ==

'''When:''' Thursday, September 13th 2012 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] '''Please meet near the totem pole in the Constitution Ave Lobby''' 
'''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)
** Terry: File Analyzer https://github.com/usnationalarchives/File-Analyzer and/or DSpace web tools!

** 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 (SIL), Joel (SIL), Carol, Ben Wallberg (UMd), Terry Brady G'town

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

2015 Conference Committees

2014-06-26T13:11:22Z

RuthKitchinTillman:

= Code4Lib 2015 Committees =

If you are interested in helping out with a particular part of the Code4Lib 2015 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.

We will assign a local contact to each committee.

== Book Give-Away Committee ==

This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.

Need about 2 months to get books shipped to the conference location.

*

== Keynote Speakers Committee ==

This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.

== Onsite Volunteer Committee ==

This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.

== Pre-conference Committee ==

This committee plans the pre-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.

== Program Committee ==

This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.

* mx matienzo
* cbeer
* Tod Olson
* [[User:Cynthia|Arty]]

== Scholarships Committee ==

This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.

* Sarah Shealy - v
* Ruth Kitchin Tillman

== Social Activities Committee ==

The committee plans, proposes, and organizes the evening activities.

* Becky Yoose (committee member 4 life)

== Sponsorships Committee ==

This committee organizes the sponsorship activities. Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.

== Streaming Video Committee ==

*[[User:highermath|Cary Gordon]] has equipment and domain knowledge to share.
*[[User:RileyChilds|Riley Childs]] has Knowledge and the YouTube Account credentials

== T-Shirt Committee ==

This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.

== Voting Activities Committee ==

This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.

== Whatever Committee ==

This committee does whatever the organizers can't talk anyone else into doing.

== Wifi / Electrical / IRC ==

This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community.

* [[User:highermath|Cary Gordon]], cgordon@chillco.com
* [[User:RileyChilds|Riley Childs]] is able to assist with Wireless planning and IRC stuffs, rchilds@cucawarriors.com

= Documentation =
To help with documention, no need to sign up, just start editing.
* [[How To Plan A Code4LibCon]]

== Documentation Interest Group ==
Promote ongoing documentation efforts.

[[Category: Code4Lib2015]]