Code4Lib - User contributions [en]

Code4Lib Journal

2023-01-03T16:06:43Z

Jtidal:

* [http://journal.code4lib.org/ Code4Lib Journal] (homepage)
* [[Code4Lib Editorial Committee Introduction]]
* [[Code4Lib Journal Deadlines]]
* [[Code4Lib Journal Voting]]
* [[Code4Lib Journal Guest Editor Policy]]
* [[Code4Lib Journal Publicity Venues]]
* [[Code4Lib Style Guide]]
* [[Code4Lib Corrections]]
* [[Code4Lib Contact and Mailing List Setup]]
* [[Code4Lib Journal Email Templates]]
* [[Code4Lib Journal WordPress Input Guidelines]]
* [[Code4lib Journal Republication Guidelines]]
** [[COinS (layman's description)]]
* [[Code4Lib Journal Retraction Policy]]
* [[Code4Lib Journal WordPress Customizations]]
* [[Code4Lib Journal Email Life of an Article]]

 

[[Code4Lib Journal Entries in Directory of Open Access Journals]]

[[Code4Lib Journal PDFs]]

[[Category: Code4Lib Journal]]

Code4Lib Journal Retraction Policy

2023-01-03T16:05:50Z

Jtidal: Created page with "The editorial committee of the Cod4Lib Journal may consider retracting an article due to plagiarism, copyright infringement, data misuse, ethical misconduct, or other consider..."

The editorial committee of the Cod4Lib Journal may consider retracting an article due to plagiarism, copyright infringement, data misuse, ethical misconduct, or other considerations.

Article authors may request to retract an article. When requesting a retraction, authors should contact the coordinating editor of that issue and/or the main editorial member (1st and/or 2nd reader) and include:
* which article should be retracted with title, publication date, journal issue, and URL
* reason for retraction.

Articles that have been retracted will be listed in the issue’s contents with the author’s name, but the abstract, text, images, figures, code, and other content will be removed from public view.

A notice of retraction will replace the article including who, when, and why the article was retracted.

Comments posted in the retracted article will be preserved or retracted at the discretion of the editorial board.

The editorial committee will work with the author(s) for appropriate language to be displayed.

Retractions will happen in a timely manner.

The editorial committee may post an Expression of Concern as an alternative to retraction if the committee finds that a formal retraction is not warranted.

2023 Scholarship Documents/Call for appliations

2022-12-08T21:03:32Z

Jtidal: /* Code4Lib 2023 Diversity Scholarships */

[[2023_Scholarship_Documents|2023 Scholarship Committee Documents]]

== Code4Lib 2023 Diversity Scholarships ==
We would like to thank our sponsors for supporting the Code4Lib 2023 Diversity Scholarships. Currently, 10 scholarships are fully funded.

* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)

As part of Code4Lib's ongoing commitment to reducing economic barriers that prevent participation for underrepresented groups, and to achieving a balanced representation of the human experience, we are pleased to announce that we are now seeking applicants for our [https://2023.code4lib.org/general-info/scholarships 2023 Diversity Scholarship program!] The Code4Lib Scholarship Committee hopes to award a number of Diversity Scholarships, based on merit and need. Each scholarship will cover up to $1,500 for domestic (normally US and Canada) and for international applicants, up to $3,000, for travel costs, lodging, and conference fees for selected applicants to attend the 2023 Code4Lib Conference in Princeton, NJ. The deadline for applications is '''Friday, January 13, 2023''' at 11:59 PM ET.

The scholarship will cover conference registration and hotel accommodations up front to scholarship awardees. Other incidentals like travel and meals may be reimbursed based on the amount awarded. Reimbursement will be managed independently at the conference. Pairing up housing with other scholarship awardees or conference attendees may also be accommodated. Please contact code4libaward@gmail.com with any questions about this arrangement. We want to ensure that financial issues do not discourage anyone from applying to this award.

We do not expect scholarship recipients to be responsible for being an ambassador for their group or an educator of others during the conference. While learning and exchange may happen as a result of interactions between participants, scholarship recipients are encouraged to focus on getting the most out of their experience and have no special duties or obligations apart from conference attendance, engaged participation to their comfort level, and giving us feedback on their experience.

Code4Lib conference 2023: [https://2023.code4lib.org https://2023.code4lib.org]

=== About Code4Lib ===
Code4Lib ([https://code4lib.org https://code4lib.org]) seeks to maintain a vibrant and diverse community of technology minded folks. We are developers and technologists for libraries, museums, and archives who have a strong commitment to open technologies. Code4Lib began as a simple mailing list in 2003 and held its first face-to-face meeting in 2005 in Chicago. The first official annual conference was held in 2006 in Corvallis, Oregon. Code4Lib is dedicated to providing a harassment-free community experience for everyone regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. For more information, please see our emerging '''[https://github.com/code4lib/code-of-conduct/blob/master/code_of_conduct.md CodeofConduct4Lib]'''. Code4Lib is dedicated to being a diverse and inclusive community of technologists seeking to share ideas and build collaboration.

=== Diversity Scholarship Eligibility, Criteria, And Requirements ===
* An applicant must be a member of a group not well-represented within the code4lib community, including but not limited to: women, people of color, LGBTQ+, ability/disability, non-binary gender identities, etc. We also invite applications from members of underrepresented and/or marginalized groups that don't fit into the categories listed above.
* An applicant must be interested in actively engaging with the Code4Lib community. For more information about Code4Lib, see the [https://2023.code4lib.org/general-info/about-c4l About Code4Lib Page].
* Applications will be evaluated based upon merit and financial needs.

=== Registration Details ===
Registration spots and hotel rooms are being held for scholarship recipients. If you can attend only if you receive a scholarship, there is no need to register for the conference or book a hotel room when registration opens. Code4Lib will assist you with both registration and hotel arrangements. If you register for the conference or book a hotel room, you will be reimbursed along with other expenses. Reimbursement for expenses will be provided to recipients during the conference.

=== How to Apply ===
Submit your application materials via the Code4Lib online form: https://docs.google.com/forms/d/e/1FAIpQLSeJnCxmj3_P-N3c9pqYdBA5WIvMpnjik7wB-tlFCwS9Wn8BXg/viewform

'''Questions can be directed to code4libaward@gmail.com.'''

The application deadline is '''Friday, January 13th, 2023 at 11:59 PM ET'''.

The scholarship committee will notify all applicants by '''Monday, January 22nd''', regardless of award results.

2023 Scholarship Documents/Call for appliations

2022-12-08T19:30:24Z

Jtidal: /* Code4Lib 2023 Diversity Scholarships */

[[2023_Scholarship_Documents|2023 Scholarship Committee Documents]]

== Code4Lib 2023 Diversity Scholarships ==
We would like to thank our sponsors for supporting the Code4Lib 2023 Diversity Scholarships. Currently, 10 scholarships are fully funded.

* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)

As part of Code4Lib's ongoing commitment to reducing economic barriers that prevent participation for underrepresented groups, and to achieving a balanced representation of the human experience, we are pleased to announce that we are now seeking applicants for our [https://2023.code4lib.org/general-info/scholarships 2023 Diversity Scholarship program!] The Code4Lib Scholarship Committee hopes to award a number of Diversity Scholarships, based on merit and need. Each scholarship will cover up to $1,500 for domestic (normally US and Canada) and for international applicants, up to $3,000. for travel costs, lodging, and conference fees for selected applicants to attend the 2023 Code4Lib Conference in Princeton, NJ. The deadline for applications is '''Friday, January 13, 2023''' at 11:59 PM ET.

The scholarship will cover conference registration and hotel accommodations up front to scholarship awardees. Other incidentals like travel and meals may be reimbursed based on the amount awarded. Reimbursement will be managed independently at the conference. Pairing up housing with other scholarship awardees or conference attendees may also be accommodated. Please contact code4libaward@gmail.com with any questions about this arrangement. We want to ensure that financial issues do not discourage anyone from applying to this award.

We do not expect scholarship recipients to be responsible for being an ambassador for their group or an educator of others during the conference. While learning and exchange may happen as a result of interactions between participants, scholarship recipients are encouraged to focus on getting the most out of their experience and have no special duties or obligations apart from conference attendance, engaged participation to their comfort level, and giving us feedback on their experience.

Code4Lib conference 2023: [https://2023.code4lib.org https://2023.code4lib.org]

=== About Code4Lib ===
Code4Lib ([https://code4lib.org https://code4lib.org]) seeks to maintain a vibrant and diverse community of technology minded folks. We are developers and technologists for libraries, museums, and archives who have a strong commitment to open technologies. Code4Lib began as a simple mailing list in 2003 and held its first face-to-face meeting in 2005 in Chicago. The first official annual conference was held in 2006 in Corvallis, Oregon. Code4Lib is dedicated to providing a harassment-free community experience for everyone regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. For more information, please see our emerging '''[https://github.com/code4lib/code-of-conduct/blob/master/code_of_conduct.md CodeofConduct4Lib]'''. Code4Lib is dedicated to being a diverse and inclusive community of technologists seeking to share ideas and build collaboration.

=== Diversity Scholarship Eligibility, Criteria, And Requirements ===
* An applicant must be a member of a group not well-represented within the code4lib community, including but not limited to: women, people of color, LGBTQ+, ability/disability, non-binary gender identities, etc. We also invite applications from members of underrepresented and/or marginalized groups that don't fit into the categories listed above.
* An applicant must be interested in actively engaging with the Code4Lib community. For more information about Code4Lib, see the [https://2023.code4lib.org/general-info/about-c4l About Code4Lib Page].
* Applications will be evaluated based upon merit and financial needs.

=== Registration Details ===
Registration spots and hotel rooms are being held for scholarship recipients. If you can attend only if you receive a scholarship, there is no need to register for the conference or book a hotel room when registration opens. Code4Lib will assist you with both registration and hotel arrangements. If you register for the conference or book a hotel room, you will be reimbursed along with other expenses. Reimbursement for expenses will be provided to recipients during the conference.

=== How to Apply ===
Submit your application materials via the Code4Lib online form: https://docs.google.com/forms/d/e/1FAIpQLSeJnCxmj3_P-N3c9pqYdBA5WIvMpnjik7wB-tlFCwS9Wn8BXg/viewform

'''Questions can be directed to code4libaward@gmail.com.'''

The application deadline is '''Friday, January 13th, 2023 at 11:59 PM ET'''.

The scholarship committee will notify all applicants by '''Monday, January 22nd''', regardless of award results.

2023 Scholarship Documents/Call for appliations

2022-12-08T19:28:18Z

Jtidal: /* Code4Lib 2023 Diversity Scholarships */

[[2023_Scholarship_Documents|2023 Scholarship Committee Documents]]

== Code4Lib 2023 Diversity Scholarships ==
We would like to thank our sponsors for supporting the Code4Lib 2023 Diversity Scholarships. Currently, 10 scholarships are fully funded.

* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)

As part of Code4Lib's ongoing commitment to reducing economic barriers that prevent participation for underrepresented groups, and to achieving a balanced representation of the human experience, we are pleased to announce that we are now seeking applicants for our [https://2023.code4lib.org/general-info/scholarships 2023 Diversity Scholarship program!] The Code4Lib Scholarship Committee hopes to award (number) Diversity Scholarships, based on merit and need. Each scholarship will cover up to $1,500 for domestic (normally US and Canada) and for international applicants, up to $3,000. for travel costs, lodging, and conference fees for selected applicants to attend the 2023 Code4Lib Conference in Princeton, NJ. The deadline for applications is '''Friday, January 13, 2023''' at 11:59 PM ET.

The scholarship will cover conference registration and hotel accommodations up front to scholarship awardees. Other incidentals like travel and meals may be reimbursed based on the amount awarded. Reimbursement will be managed independently at the conference. Pairing up housing with other scholarship awardees or conference attendees may also be accommodated. Please contact code4libaward@gmail.com with any questions about this arrangement. We want to ensure that financial issues do not discourage anyone from applying to this award.

We do not expect scholarship recipients to be responsible for being an ambassador for their group or an educator of others during the conference. While learning and exchange may happen as a result of interactions between participants, scholarship recipients are encouraged to focus on getting the most out of their experience and have no special duties or obligations apart from conference attendance, engaged participation to their comfort level, and giving us feedback on their experience.

Code4Lib conference 2023: [https://2023.code4lib.org https://2023.code4lib.org]

=== About Code4Lib ===
Code4Lib ([https://code4lib.org https://code4lib.org]) seeks to maintain a vibrant and diverse community of technology minded folks. We are developers and technologists for libraries, museums, and archives who have a strong commitment to open technologies. Code4Lib began as a simple mailing list in 2003 and held its first face-to-face meeting in 2005 in Chicago. The first official annual conference was held in 2006 in Corvallis, Oregon. Code4Lib is dedicated to providing a harassment-free community experience for everyone regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. For more information, please see our emerging '''[https://github.com/code4lib/code-of-conduct/blob/master/code_of_conduct.md CodeofConduct4Lib]'''. Code4Lib is dedicated to being a diverse and inclusive community of technologists seeking to share ideas and build collaboration.

=== Diversity Scholarship Eligibility, Criteria, And Requirements ===
* An applicant must be a member of a group not well-represented within the code4lib community, including but not limited to: women, people of color, LGBTQ+, ability/disability, non-binary gender identities, etc. We also invite applications from members of underrepresented and/or marginalized groups that don't fit into the categories listed above.
* An applicant must be interested in actively engaging with the Code4Lib community. For more information about Code4Lib, see the [https://2023.code4lib.org/general-info/about-c4l About Code4Lib Page].
* Applications will be evaluated based upon merit and financial needs.

=== Registration Details ===
Registration spots and hotel rooms are being held for scholarship recipients. If you can attend only if you receive a scholarship, there is no need to register for the conference or book a hotel room when registration opens. Code4Lib will assist you with both registration and hotel arrangements. If you register for the conference or book a hotel room, you will be reimbursed along with other expenses. Reimbursement for expenses will be provided to recipients during the conference.

=== How to Apply ===
Submit your application materials via the Code4Lib online form: https://docs.google.com/forms/d/e/1FAIpQLSeJnCxmj3_P-N3c9pqYdBA5WIvMpnjik7wB-tlFCwS9Wn8BXg/viewform

'''Questions can be directed to code4libaward@gmail.com.'''

The application deadline is '''Friday, January 13th, 2023 at 11:59 PM ET'''.

The scholarship committee will notify all applicants by '''Monday, January 22nd''', regardless of award results.

2023 Scholarship Documents/Call for appliations

2022-12-08T19:26:16Z

Jtidal: /* How to Apply */

[[2023_Scholarship_Documents|2023 Scholarship Committee Documents]]

== Code4Lib 2023 Diversity Scholarships ==
We would like to thank our sponsors for supporting the Code4Lib 2023 Diversity Scholarships. Currently, 10 scholarships are fully funded.

* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)

As part of Code4Lib's ongoing commitment to reducing economic barriers that prevent participation for underrepresented groups, and to achieving a balanced representation of the human experience, we are pleased to announce that we are now seeking applicants for our [https://2023.code4lib.org/general-info/scholarships 2023 Diversity Scholarship program!] The Code4Lib Scholarship Committee hopes to award (number) Diversity Scholarships, based on merit and need. Each scholarship will cover up to $1,500 for travel costs, lodging, and conference fees for selected applicants to attend the 2023 Code4Lib Conference in Princeton, NJ. The deadline for applications is '''Friday, January 13, 2023''' at 11:59 PM ET.

The scholarship will cover conference registration and hotel accommodations up front to scholarship awardees. Other incidentals like travel and meals may be reimbursed based on the amount awarded. Reimbursement will be managed independently at the conference. Pairing up housing with other scholarship awardees or conference attendees may also be accommodated. Please contact code4libaward@gmail.com with any questions about this arrangement. We want to ensure that financial issues do not discourage anyone from applying to this award.

We do not expect scholarship recipients to be responsible for being an ambassador for their group or an educator of others during the conference. While learning and exchange may happen as a result of interactions between participants, scholarship recipients are encouraged to focus on getting the most out of their experience and have no special duties or obligations apart from conference attendance, engaged participation to their comfort level, and giving us feedback on their experience.

Code4Lib conference 2023: [https://2023.code4lib.org https://2023.code4lib.org]

=== About Code4Lib ===
Code4Lib ([https://code4lib.org https://code4lib.org]) seeks to maintain a vibrant and diverse community of technology minded folks. We are developers and technologists for libraries, museums, and archives who have a strong commitment to open technologies. Code4Lib began as a simple mailing list in 2003 and held its first face-to-face meeting in 2005 in Chicago. The first official annual conference was held in 2006 in Corvallis, Oregon. Code4Lib is dedicated to providing a harassment-free community experience for everyone regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. For more information, please see our emerging '''[https://github.com/code4lib/code-of-conduct/blob/master/code_of_conduct.md CodeofConduct4Lib]'''. Code4Lib is dedicated to being a diverse and inclusive community of technologists seeking to share ideas and build collaboration.

=== Diversity Scholarship Eligibility, Criteria, And Requirements ===
* An applicant must be a member of a group not well-represented within the code4lib community, including but not limited to: women, people of color, LGBTQ+, ability/disability, non-binary gender identities, etc. We also invite applications from members of underrepresented and/or marginalized groups that don't fit into the categories listed above.
* An applicant must be interested in actively engaging with the Code4Lib community. For more information about Code4Lib, see the [https://2023.code4lib.org/general-info/about-c4l About Code4Lib Page].
* Applications will be evaluated based upon merit and financial needs.

=== Registration Details ===
Registration spots and hotel rooms are being held for scholarship recipients. If you can attend only if you receive a scholarship, there is no need to register for the conference or book a hotel room when registration opens. Code4Lib will assist you with both registration and hotel arrangements. If you register for the conference or book a hotel room, you will be reimbursed along with other expenses. Reimbursement for expenses will be provided to recipients during the conference.

=== How to Apply ===
Submit your application materials via the Code4Lib online form: https://docs.google.com/forms/d/e/1FAIpQLSeJnCxmj3_P-N3c9pqYdBA5WIvMpnjik7wB-tlFCwS9Wn8BXg/viewform

'''Questions can be directed to code4libaward@gmail.com.'''

The application deadline is '''Friday, January 13th, 2023 at 11:59 PM ET'''.

The scholarship committee will notify all applicants by '''Monday, January 22nd''', regardless of award results.

2023 Scholarship Documents/Call for appliations

2022-12-08T19:10:50Z

Jtidal: /* How to Apply */

[[2023_Scholarship_Documents|2023 Scholarship Committee Documents]]

== Code4Lib 2023 Diversity Scholarships ==
We would like to thank our sponsors for supporting the Code4Lib 2023 Diversity Scholarships. Currently, 10 scholarships are fully funded.

* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)

As part of Code4Lib's ongoing commitment to reducing economic barriers that prevent participation for underrepresented groups, and to achieving a balanced representation of the human experience, we are pleased to announce that we are now seeking applicants for our [https://2023.code4lib.org/general-info/scholarships 2023 Diversity Scholarship program!] The Code4Lib Scholarship Committee hopes to award (number) Diversity Scholarships, based on merit and need. Each scholarship will cover up to $1,500 for travel costs, lodging, and conference fees for selected applicants to attend the 2023 Code4Lib Conference in Princeton, NJ. The deadline for applications is '''Friday, January 13, 2023''' at 11:59 PM ET.

The scholarship will cover conference registration and hotel accommodations up front to scholarship awardees. Other incidentals like travel and meals may be reimbursed based on the amount awarded. Reimbursement will be managed independently at the conference. Pairing up housing with other scholarship awardees or conference attendees may also be accommodated. Please contact code4libaward@gmail.com with any questions about this arrangement. We want to ensure that financial issues do not discourage anyone from applying to this award.

We do not expect scholarship recipients to be responsible for being an ambassador for their group or an educator of others during the conference. While learning and exchange may happen as a result of interactions between participants, scholarship recipients are encouraged to focus on getting the most out of their experience and have no special duties or obligations apart from conference attendance, engaged participation to their comfort level, and giving us feedback on their experience.

Code4Lib conference 2023: [https://2023.code4lib.org https://2023.code4lib.org]

=== About Code4Lib ===
Code4Lib ([https://code4lib.org https://code4lib.org]) seeks to maintain a vibrant and diverse community of technology minded folks. We are developers and technologists for libraries, museums, and archives who have a strong commitment to open technologies. Code4Lib began as a simple mailing list in 2003 and held its first face-to-face meeting in 2005 in Chicago. The first official annual conference was held in 2006 in Corvallis, Oregon. Code4Lib is dedicated to providing a harassment-free community experience for everyone regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. For more information, please see our emerging '''[https://github.com/code4lib/code-of-conduct/blob/master/code_of_conduct.md CodeofConduct4Lib]'''. Code4Lib is dedicated to being a diverse and inclusive community of technologists seeking to share ideas and build collaboration.

=== Diversity Scholarship Eligibility, Criteria, And Requirements ===
* An applicant must be a member of a group not well-represented within the code4lib community, including but not limited to: women, people of color, LGBTQ+, ability/disability, non-binary gender identities, etc. We also invite applications from members of underrepresented and/or marginalized groups that don't fit into the categories listed above.
* An applicant must be interested in actively engaging with the Code4Lib community. For more information about Code4Lib, see the [https://2023.code4lib.org/general-info/about-c4l About Code4Lib Page].
* Applications will be evaluated based upon merit and financial needs.

=== Registration Details ===
Registration spots and hotel rooms are being held for scholarship recipients. If you can attend only if you receive a scholarship, there is no need to register for the conference or book a hotel room when registration opens. Code4Lib will assist you with both registration and hotel arrangements. If you register for the conference or book a hotel room, you will be reimbursed along with other expenses. Reimbursement for expenses will be provided to recipients during the conference.

=== How to Apply ===
Submit your application materials via the Code4Lib online form: https://docs.google.com/forms/d/e/1FAIpQLSeJnCxmj3_P-N3c9pqYdBA5WIvMpnjik7wB-tlFCwS9Wn8BXg/viewform

You will need to prepare:
# Your brief letter of interest, which:
## Identifies your eligibility for a diversity scholarship (200 max)
## Describes your financial needs to attend the conference (200 - 300 words)
## Describes how you see yourself benefiting from and participating in the Code4Lib 2018 conference and the general Code4Lib community (200 - 300 words)
# Your current resume or CV

'''Questions can be directed to code4libaward@gmail.com.'''

The application deadline is '''Friday, January 13th, 2023 at 11:59 PM ET'''.

The scholarship committee will notify all applicants by '''Monday, January 22nd''', regardless of award results.

2023 Scholarship Documents/Call for appliations

2022-12-08T19:09:42Z

Jtidal: /* How to Apply */

[[2023_Scholarship_Documents|2023 Scholarship Committee Documents]]

== Code4Lib 2023 Diversity Scholarships ==
We would like to thank our sponsors for supporting the Code4Lib 2023 Diversity Scholarships. Currently, 10 scholarships are fully funded.

* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)

As part of Code4Lib's ongoing commitment to reducing economic barriers that prevent participation for underrepresented groups, and to achieving a balanced representation of the human experience, we are pleased to announce that we are now seeking applicants for our [https://2023.code4lib.org/general-info/scholarships 2023 Diversity Scholarship program!] The Code4Lib Scholarship Committee hopes to award (number) Diversity Scholarships, based on merit and need. Each scholarship will cover up to $1,500 for travel costs, lodging, and conference fees for selected applicants to attend the 2023 Code4Lib Conference in Princeton, NJ. The deadline for applications is '''Friday, January 13, 2023''' at 11:59 PM ET.

The scholarship will cover conference registration and hotel accommodations up front to scholarship awardees. Other incidentals like travel and meals may be reimbursed based on the amount awarded. Reimbursement will be managed independently at the conference. Pairing up housing with other scholarship awardees or conference attendees may also be accommodated. Please contact code4libaward@gmail.com with any questions about this arrangement. We want to ensure that financial issues do not discourage anyone from applying to this award.

We do not expect scholarship recipients to be responsible for being an ambassador for their group or an educator of others during the conference. While learning and exchange may happen as a result of interactions between participants, scholarship recipients are encouraged to focus on getting the most out of their experience and have no special duties or obligations apart from conference attendance, engaged participation to their comfort level, and giving us feedback on their experience.

Code4Lib conference 2023: [https://2023.code4lib.org https://2023.code4lib.org]

=== About Code4Lib ===
Code4Lib ([https://code4lib.org https://code4lib.org]) seeks to maintain a vibrant and diverse community of technology minded folks. We are developers and technologists for libraries, museums, and archives who have a strong commitment to open technologies. Code4Lib began as a simple mailing list in 2003 and held its first face-to-face meeting in 2005 in Chicago. The first official annual conference was held in 2006 in Corvallis, Oregon. Code4Lib is dedicated to providing a harassment-free community experience for everyone regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. For more information, please see our emerging '''[https://github.com/code4lib/code-of-conduct/blob/master/code_of_conduct.md CodeofConduct4Lib]'''. Code4Lib is dedicated to being a diverse and inclusive community of technologists seeking to share ideas and build collaboration.

=== Diversity Scholarship Eligibility, Criteria, And Requirements ===
* An applicant must be a member of a group not well-represented within the code4lib community, including but not limited to: women, people of color, LGBTQ+, ability/disability, non-binary gender identities, etc. We also invite applications from members of underrepresented and/or marginalized groups that don't fit into the categories listed above.
* An applicant must be interested in actively engaging with the Code4Lib community. For more information about Code4Lib, see the [https://2023.code4lib.org/general-info/about-c4l About Code4Lib Page].
* Applications will be evaluated based upon merit and financial needs.

=== Registration Details ===
Registration spots and hotel rooms are being held for scholarship recipients. If you can attend only if you receive a scholarship, there is no need to register for the conference or book a hotel room when registration opens. Code4Lib will assist you with both registration and hotel arrangements. If you register for the conference or book a hotel room, you will be reimbursed along with other expenses. Reimbursement for expenses will be provided to recipients during the conference.

=== How to Apply ===
Submit your application materials via the Code4Lib online form: https://docs.google.com/forms/d/e/1FAIpQLSeJnCxmj3_P-N3c9pqYdBA5WIvMpnjik7wB-tlFCwS9Wn8BXg/viewform

You will need to prepare:
# Your brief letter of interest, which:
## Identifies your eligibility for a diversity scholarship (200 max)
## Describes your financial needs to attend the conference (200 - 300 words)
## Describes how you see yourself benefiting from and participating in the Code4Lib 2018 conference and the general Code4Lib community (200 - 300 words)
# Your current resume or CV

'''Questions can be directed to code4libaward@gmail.com.'''

The application deadline is '''Friday, January 13th, 2023 at 11:59 PM ET'''.

The scholarship committee will notify all applicants by '''Monday, January 17th''', regardless of award results.

2023 Scholarship Documents/Call for appliations

2022-12-08T19:08:45Z

Jtidal: /* How to Apply */

[[2023_Scholarship_Documents|2023 Scholarship Committee Documents]]

== Code4Lib 2023 Diversity Scholarships ==
We would like to thank our sponsors for supporting the Code4Lib 2023 Diversity Scholarships. Currently, 10 scholarships are fully funded.

* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)

As part of Code4Lib's ongoing commitment to reducing economic barriers that prevent participation for underrepresented groups, and to achieving a balanced representation of the human experience, we are pleased to announce that we are now seeking applicants for our [https://2023.code4lib.org/general-info/scholarships 2023 Diversity Scholarship program!] The Code4Lib Scholarship Committee hopes to award (number) Diversity Scholarships, based on merit and need. Each scholarship will cover up to $1,500 for travel costs, lodging, and conference fees for selected applicants to attend the 2023 Code4Lib Conference in Princeton, NJ. The deadline for applications is '''Friday, January 13, 2023''' at 11:59 PM ET.

The scholarship will cover conference registration and hotel accommodations up front to scholarship awardees. Other incidentals like travel and meals may be reimbursed based on the amount awarded. Reimbursement will be managed independently at the conference. Pairing up housing with other scholarship awardees or conference attendees may also be accommodated. Please contact code4libaward@gmail.com with any questions about this arrangement. We want to ensure that financial issues do not discourage anyone from applying to this award.

We do not expect scholarship recipients to be responsible for being an ambassador for their group or an educator of others during the conference. While learning and exchange may happen as a result of interactions between participants, scholarship recipients are encouraged to focus on getting the most out of their experience and have no special duties or obligations apart from conference attendance, engaged participation to their comfort level, and giving us feedback on their experience.

Code4Lib conference 2023: [https://2023.code4lib.org https://2023.code4lib.org]

=== About Code4Lib ===
Code4Lib ([https://code4lib.org https://code4lib.org]) seeks to maintain a vibrant and diverse community of technology minded folks. We are developers and technologists for libraries, museums, and archives who have a strong commitment to open technologies. Code4Lib began as a simple mailing list in 2003 and held its first face-to-face meeting in 2005 in Chicago. The first official annual conference was held in 2006 in Corvallis, Oregon. Code4Lib is dedicated to providing a harassment-free community experience for everyone regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. For more information, please see our emerging '''[https://github.com/code4lib/code-of-conduct/blob/master/code_of_conduct.md CodeofConduct4Lib]'''. Code4Lib is dedicated to being a diverse and inclusive community of technologists seeking to share ideas and build collaboration.

=== Diversity Scholarship Eligibility, Criteria, And Requirements ===
* An applicant must be a member of a group not well-represented within the code4lib community, including but not limited to: women, people of color, LGBTQ+, ability/disability, non-binary gender identities, etc. We also invite applications from members of underrepresented and/or marginalized groups that don't fit into the categories listed above.
* An applicant must be interested in actively engaging with the Code4Lib community. For more information about Code4Lib, see the [https://2023.code4lib.org/general-info/about-c4l About Code4Lib Page].
* Applications will be evaluated based upon merit and financial needs.

=== Registration Details ===
Registration spots and hotel rooms are being held for scholarship recipients. If you can attend only if you receive a scholarship, there is no need to register for the conference or book a hotel room when registration opens. Code4Lib will assist you with both registration and hotel arrangements. If you register for the conference or book a hotel room, you will be reimbursed along with other expenses. Reimbursement for expenses will be provided to recipients during the conference.

=== How to Apply ===
Submit your application materials via the Code4Lib online form: https://docs.google.com/forms/d/e/1FAIpQLSeJnCxmj3_P-N3c9pqYdBA5WIvMpnjik7wB-tlFCwS9Wn8BXg/viewform

You will need to prepare:
# Your brief letter of interest, which:
## Identifies your eligibility for a diversity scholarship (200 max)
## Describes your financial needs to attend the conference (200 - 300 words)
## Describes how you see yourself benefiting from and participating in the Code4Lib 2018 conference and the general Code4Lib community (200 - 300 words)
# Your current resume or CV

'''Questions can be directed to code4libaward@gmail.com.'''

The application deadline is '''Monday, January 22nd, 2023 at 11:59 PM ET'''.

The scholarship committee will notify all applicants by '''Monday, January 17th''', regardless of award results.

2023 Scholarship Documents/Call for appliations

2022-12-05T16:36:10Z

Jtidal: /* How to Apply */

[[2023_Scholarship_Documents|2023 Scholarship Committee Documents]]

== Code4Lib 2023 Diversity Scholarships ==
We would like to thank our sponsors for supporting the Code4Lib 2018 Diversity Scholarships. Currently, 10 scholarships are fully funded.

* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)

As part of Code4Lib's ongoing commitment to reducing economic barriers that prevent participation for underrepresented groups, and to achieving a balanced representation of the human experience, we are pleased to announce that we are now seeking applicants for our [https://2023.code4lib.org/general-info/scholarships 2023 Diversity Scholarship program!] The Code4Lib Scholarship Committee hopes to award (number) Diversity Scholarships, based on merit and need. Each scholarship will cover up to $1,500 for travel costs, lodging, and conference fees for selected applicants to attend the 2023 Code4Lib Conference in Princeton, NJ. The deadline for applications is '''Friday, January 13, 2023''' at 11:59 PM ET.

The scholarship will cover conference registration and hotel accommodations up front to scholarship awardees. Other incidentals like travel and meals may be reimbursed based on the amount awarded. Reimbursement will be managed independently at the conference. Pairing up housing with other scholarship awardees or conference attendees may also be accommodated. Please contact code4libaward@gmail.com with any questions about this arrangement. We want to ensure that financial issues do not discourage anyone from applying to this award.

We do not expect scholarship recipients to be responsible for being an ambassador for their group or an educator of others during the conference. While learning and exchange may happen as a result of interactions between participants, scholarship recipients are encouraged to focus on getting the most out of their experience and have no special duties or obligations apart from conference attendance, engaged participation to their comfort level, and giving us feedback on their experience.

Code4Lib conference 2023: [https://2023.code4lib.org https://2023.code4lib.org]

=== About Code4Lib ===
Code4Lib ([https://code4lib.org https://code4lib.org]) seeks to maintain a vibrant and diverse community of technology minded folks. We are developers and technologists for libraries, museums, and archives who have a strong commitment to open technologies. Code4Lib began as a simple mailing list in 2003 and held its first face-to-face meeting in 2005 in Chicago. The first official annual conference was held in 2006 in Corvallis, Oregon. Code4Lib is dedicated to providing a harassment-free community experience for everyone regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. For more information, please see our emerging '''[https://github.com/code4lib/code-of-conduct/blob/master/code_of_conduct.md CodeofConduct4Lib]'''. Code4Lib is dedicated to being a diverse and inclusive community of technologists seeking to share ideas and build collaboration.

=== Diversity Scholarship Eligibility, Criteria, And Requirements ===
* An applicant must be a member of a group not well-represented within the code4lib community, including but not limited to: women, people of color, LGBTQ+, ability/disability, non-binary gender identities, etc. We also invite applications from members of underrepresented and/or marginalized groups that don't fit into the categories listed above.
* An applicant must be interested in actively engaging with the Code4Lib community. For more information about Code4Lib, see the [https://2023.code4lib.org/general-info/about-c4l About Code4Lib Page].
* Applications will be evaluated based upon merit and financial needs.

=== Registration Details ===
Registration spots and hotel rooms are being held for scholarship recipients. If you can attend only if you receive a scholarship, there is no need to register for the conference or book a hotel room when registration opens. Code4Lib will assist you with both registration and hotel arrangements. If you register for the conference or book a hotel room, you will be reimbursed along with other expenses. Reimbursement for expenses will be provided to recipients during the conference.

=== How to Apply ===
Submit your application materials via the Code4Lib online form: https://goo.gl/forms/(url)

You will need to prepare:
# Your brief letter of interest, which:
## Identifies your eligibility for a diversity scholarship (200 max)
## Describes your financial needs to attend the conference (200 - 300 words)
## Describes how you see yourself benefiting from and participating in the Code4Lib 2018 conference and the general Code4Lib community (200 - 300 words)
# Your current resume or CV

'''Questions can be directed to code4libaward@gmail.com.'''

The application deadline is '''Friday, January 13th, 2023 at 11:59 PM ET'''.

The scholarship committee will notify all applicants by '''Monday, January 22nd''', regardless of award results.

2023 Scholarship Documents/Call for appliations

2022-12-05T16:35:24Z

Jtidal: /* How to Apply */

[[2023_Scholarship_Documents|2023 Scholarship Committee Documents]]

== Code4Lib 2023 Diversity Scholarships ==
We would like to thank our sponsors for supporting the Code4Lib 2018 Diversity Scholarships. Currently, 10 scholarships are fully funded.

* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)

As part of Code4Lib's ongoing commitment to reducing economic barriers that prevent participation for underrepresented groups, and to achieving a balanced representation of the human experience, we are pleased to announce that we are now seeking applicants for our [https://2023.code4lib.org/general-info/scholarships 2023 Diversity Scholarship program!] The Code4Lib Scholarship Committee hopes to award (number) Diversity Scholarships, based on merit and need. Each scholarship will cover up to $1,500 for travel costs, lodging, and conference fees for selected applicants to attend the 2023 Code4Lib Conference in Princeton, NJ. The deadline for applications is '''Friday, January 13, 2023''' at 11:59 PM ET.

The scholarship will cover conference registration and hotel accommodations up front to scholarship awardees. Other incidentals like travel and meals may be reimbursed based on the amount awarded. Reimbursement will be managed independently at the conference. Pairing up housing with other scholarship awardees or conference attendees may also be accommodated. Please contact code4libaward@gmail.com with any questions about this arrangement. We want to ensure that financial issues do not discourage anyone from applying to this award.

We do not expect scholarship recipients to be responsible for being an ambassador for their group or an educator of others during the conference. While learning and exchange may happen as a result of interactions between participants, scholarship recipients are encouraged to focus on getting the most out of their experience and have no special duties or obligations apart from conference attendance, engaged participation to their comfort level, and giving us feedback on their experience.

Code4Lib conference 2023: [https://2023.code4lib.org https://2023.code4lib.org]

=== About Code4Lib ===
Code4Lib ([https://code4lib.org https://code4lib.org]) seeks to maintain a vibrant and diverse community of technology minded folks. We are developers and technologists for libraries, museums, and archives who have a strong commitment to open technologies. Code4Lib began as a simple mailing list in 2003 and held its first face-to-face meeting in 2005 in Chicago. The first official annual conference was held in 2006 in Corvallis, Oregon. Code4Lib is dedicated to providing a harassment-free community experience for everyone regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. For more information, please see our emerging '''[https://github.com/code4lib/code-of-conduct/blob/master/code_of_conduct.md CodeofConduct4Lib]'''. Code4Lib is dedicated to being a diverse and inclusive community of technologists seeking to share ideas and build collaboration.

=== Diversity Scholarship Eligibility, Criteria, And Requirements ===
* An applicant must be a member of a group not well-represented within the code4lib community, including but not limited to: women, people of color, LGBTQ+, ability/disability, non-binary gender identities, etc. We also invite applications from members of underrepresented and/or marginalized groups that don't fit into the categories listed above.
* An applicant must be interested in actively engaging with the Code4Lib community. For more information about Code4Lib, see the [https://2023.code4lib.org/general-info/about-c4l About Code4Lib Page].
* Applications will be evaluated based upon merit and financial needs.

=== Registration Details ===
Registration spots and hotel rooms are being held for scholarship recipients. If you can attend only if you receive a scholarship, there is no need to register for the conference or book a hotel room when registration opens. Code4Lib will assist you with both registration and hotel arrangements. If you register for the conference or book a hotel room, you will be reimbursed along with other expenses. Reimbursement for expenses will be provided to recipients during the conference.

=== How to Apply ===
Submit your application materials via the Code4Lib online form: https://goo.gl/forms/(url)

You will need to prepare:
# Your brief letter of interest, which:
## Identifies your eligibility for a diversity scholarship (200 max)
## Describes your financial needs to attend the conference (200 - 300 words)
## Describes how you see yourself benefiting from and participating in the Code4Lib 2018 conference and the general Code4Lib community (200 - 300 words)
# Your current resume or CV

'''Please note: Your brief letter of interest and current CV/resume should be '''combined into a single pdf'''. Your file should follow a “Lastname-Firstname.pdf” naming convention. Questions can be directed to code4libaward@gmail.com.'''

The application deadline is '''Friday, January 13th, 2023 at 11:59 PM ET'''.

The scholarship committee will notify all applicants by '''Monday, January 22nd''', regardless of award results.

2023 Scholarship Documents/Call for appliations

2022-12-05T16:35:01Z

Jtidal: /* How to Apply */

[[2023_Scholarship_Documents|2023 Scholarship Committee Documents]]

== Code4Lib 2023 Diversity Scholarships ==
We would like to thank our sponsors for supporting the Code4Lib 2018 Diversity Scholarships. Currently, 10 scholarships are fully funded.

* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)

As part of Code4Lib's ongoing commitment to reducing economic barriers that prevent participation for underrepresented groups, and to achieving a balanced representation of the human experience, we are pleased to announce that we are now seeking applicants for our [https://2023.code4lib.org/general-info/scholarships 2023 Diversity Scholarship program!] The Code4Lib Scholarship Committee hopes to award (number) Diversity Scholarships, based on merit and need. Each scholarship will cover up to $1,500 for travel costs, lodging, and conference fees for selected applicants to attend the 2023 Code4Lib Conference in Princeton, NJ. The deadline for applications is '''Friday, January 13, 2023''' at 11:59 PM ET.

The scholarship will cover conference registration and hotel accommodations up front to scholarship awardees. Other incidentals like travel and meals may be reimbursed based on the amount awarded. Reimbursement will be managed independently at the conference. Pairing up housing with other scholarship awardees or conference attendees may also be accommodated. Please contact code4libaward@gmail.com with any questions about this arrangement. We want to ensure that financial issues do not discourage anyone from applying to this award.

We do not expect scholarship recipients to be responsible for being an ambassador for their group or an educator of others during the conference. While learning and exchange may happen as a result of interactions between participants, scholarship recipients are encouraged to focus on getting the most out of their experience and have no special duties or obligations apart from conference attendance, engaged participation to their comfort level, and giving us feedback on their experience.

Code4Lib conference 2023: [https://2023.code4lib.org https://2023.code4lib.org]

=== About Code4Lib ===
Code4Lib ([https://code4lib.org https://code4lib.org]) seeks to maintain a vibrant and diverse community of technology minded folks. We are developers and technologists for libraries, museums, and archives who have a strong commitment to open technologies. Code4Lib began as a simple mailing list in 2003 and held its first face-to-face meeting in 2005 in Chicago. The first official annual conference was held in 2006 in Corvallis, Oregon. Code4Lib is dedicated to providing a harassment-free community experience for everyone regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. For more information, please see our emerging '''[https://github.com/code4lib/code-of-conduct/blob/master/code_of_conduct.md CodeofConduct4Lib]'''. Code4Lib is dedicated to being a diverse and inclusive community of technologists seeking to share ideas and build collaboration.

=== Diversity Scholarship Eligibility, Criteria, And Requirements ===
* An applicant must be a member of a group not well-represented within the code4lib community, including but not limited to: women, people of color, LGBTQ+, ability/disability, non-binary gender identities, etc. We also invite applications from members of underrepresented and/or marginalized groups that don't fit into the categories listed above.
* An applicant must be interested in actively engaging with the Code4Lib community. For more information about Code4Lib, see the [https://2023.code4lib.org/general-info/about-c4l About Code4Lib Page].
* Applications will be evaluated based upon merit and financial needs.

=== Registration Details ===
Registration spots and hotel rooms are being held for scholarship recipients. If you can attend only if you receive a scholarship, there is no need to register for the conference or book a hotel room when registration opens. Code4Lib will assist you with both registration and hotel arrangements. If you register for the conference or book a hotel room, you will be reimbursed along with other expenses. Reimbursement for expenses will be provided to recipients during the conference.

=== How to Apply ===
Submit your application materials via the Code4Lib online form: https://goo.gl/forms/(url)

You will need to prepare:
# Your brief letter of interest, which:
## Identifies your eligibility for a diversity scholarship (200 max)
## '''Describes your financial needs to attend the conference (200 - 300 words)'''
## Describes how you see yourself benefiting from and participating in the Code4Lib 2018 conference and the general Code4Lib community '''(200 - 300 words)'''
# Your current resume or CV

'''Please note: Your brief letter of interest and current CV/resume should be '''combined into a single pdf'''. Your file should follow a “Lastname-Firstname.pdf” naming convention. Questions can be directed to code4libaward@gmail.com.'''

The application deadline is '''Friday, January 13th, 2023 at 11:59 PM ET'''.

The scholarship committee will notify all applicants by '''Monday, January 22nd''', regardless of award results.

2023 Scholarship Documents/Call for appliations

2022-12-05T16:34:30Z

Jtidal: /* How to Apply */

[[2023_Scholarship_Documents|2023 Scholarship Committee Documents]]

== Code4Lib 2023 Diversity Scholarships ==
We would like to thank our sponsors for supporting the Code4Lib 2018 Diversity Scholarships. Currently, 10 scholarships are fully funded.

* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)

As part of Code4Lib's ongoing commitment to reducing economic barriers that prevent participation for underrepresented groups, and to achieving a balanced representation of the human experience, we are pleased to announce that we are now seeking applicants for our [https://2023.code4lib.org/general-info/scholarships 2023 Diversity Scholarship program!] The Code4Lib Scholarship Committee hopes to award (number) Diversity Scholarships, based on merit and need. Each scholarship will cover up to $1,500 for travel costs, lodging, and conference fees for selected applicants to attend the 2023 Code4Lib Conference in Princeton, NJ. The deadline for applications is '''Friday, January 13, 2023''' at 11:59 PM ET.

The scholarship will cover conference registration and hotel accommodations up front to scholarship awardees. Other incidentals like travel and meals may be reimbursed based on the amount awarded. Reimbursement will be managed independently at the conference. Pairing up housing with other scholarship awardees or conference attendees may also be accommodated. Please contact code4libaward@gmail.com with any questions about this arrangement. We want to ensure that financial issues do not discourage anyone from applying to this award.

We do not expect scholarship recipients to be responsible for being an ambassador for their group or an educator of others during the conference. While learning and exchange may happen as a result of interactions between participants, scholarship recipients are encouraged to focus on getting the most out of their experience and have no special duties or obligations apart from conference attendance, engaged participation to their comfort level, and giving us feedback on their experience.

Code4Lib conference 2023: [https://2023.code4lib.org https://2023.code4lib.org]

=== About Code4Lib ===
Code4Lib ([https://code4lib.org https://code4lib.org]) seeks to maintain a vibrant and diverse community of technology minded folks. We are developers and technologists for libraries, museums, and archives who have a strong commitment to open technologies. Code4Lib began as a simple mailing list in 2003 and held its first face-to-face meeting in 2005 in Chicago. The first official annual conference was held in 2006 in Corvallis, Oregon. Code4Lib is dedicated to providing a harassment-free community experience for everyone regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. For more information, please see our emerging '''[https://github.com/code4lib/code-of-conduct/blob/master/code_of_conduct.md CodeofConduct4Lib]'''. Code4Lib is dedicated to being a diverse and inclusive community of technologists seeking to share ideas and build collaboration.

=== Diversity Scholarship Eligibility, Criteria, And Requirements ===
* An applicant must be a member of a group not well-represented within the code4lib community, including but not limited to: women, people of color, LGBTQ+, ability/disability, non-binary gender identities, etc. We also invite applications from members of underrepresented and/or marginalized groups that don't fit into the categories listed above.
* An applicant must be interested in actively engaging with the Code4Lib community. For more information about Code4Lib, see the [https://2023.code4lib.org/general-info/about-c4l About Code4Lib Page].
* Applications will be evaluated based upon merit and financial needs.

=== Registration Details ===
Registration spots and hotel rooms are being held for scholarship recipients. If you can attend only if you receive a scholarship, there is no need to register for the conference or book a hotel room when registration opens. Code4Lib will assist you with both registration and hotel arrangements. If you register for the conference or book a hotel room, you will be reimbursed along with other expenses. Reimbursement for expenses will be provided to recipients during the conference.

=== How to Apply ===
Submit your application materials via the Code4Lib online form: https://goo.gl/forms/(url)

You will need to prepare:
# Your brief letter of interest, no more than '''( 200 words max ) words''', which:
## Identifies your eligibility for a diversity scholarship (200 max)
## '''Describes your financial needs to attend the conference (200 - 300 words)'''
## Describes how you see yourself benefiting from and participating in the Code4Lib 2018 conference and the general Code4Lib community '''(200 - 300 words)'''
# Your current resume or CV

'''Please note: Your brief letter of interest and current CV/resume should be '''combined into a single pdf'''. Your file should follow a “Lastname-Firstname.pdf” naming convention. Questions can be directed to code4libaward@gmail.com.'''

The application deadline is '''Friday, January 13th, 2023 at 11:59 PM ET'''.

The scholarship committee will notify all applicants by '''Monday, January 22nd''', regardless of award results.

2023 Scholarship Documents/Call for appliations

2022-12-05T16:34:05Z

Jtidal: /* How to Apply */

[[2023_Scholarship_Documents|2023 Scholarship Committee Documents]]

== Code4Lib 2023 Diversity Scholarships ==
We would like to thank our sponsors for supporting the Code4Lib 2018 Diversity Scholarships. Currently, 10 scholarships are fully funded.

* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)

As part of Code4Lib's ongoing commitment to reducing economic barriers that prevent participation for underrepresented groups, and to achieving a balanced representation of the human experience, we are pleased to announce that we are now seeking applicants for our [https://2023.code4lib.org/general-info/scholarships 2023 Diversity Scholarship program!] The Code4Lib Scholarship Committee hopes to award (number) Diversity Scholarships, based on merit and need. Each scholarship will cover up to $1,500 for travel costs, lodging, and conference fees for selected applicants to attend the 2023 Code4Lib Conference in Princeton, NJ. The deadline for applications is '''Friday, January 13, 2023''' at 11:59 PM ET.

The scholarship will cover conference registration and hotel accommodations up front to scholarship awardees. Other incidentals like travel and meals may be reimbursed based on the amount awarded. Reimbursement will be managed independently at the conference. Pairing up housing with other scholarship awardees or conference attendees may also be accommodated. Please contact code4libaward@gmail.com with any questions about this arrangement. We want to ensure that financial issues do not discourage anyone from applying to this award.

We do not expect scholarship recipients to be responsible for being an ambassador for their group or an educator of others during the conference. While learning and exchange may happen as a result of interactions between participants, scholarship recipients are encouraged to focus on getting the most out of their experience and have no special duties or obligations apart from conference attendance, engaged participation to their comfort level, and giving us feedback on their experience.

Code4Lib conference 2023: [https://2023.code4lib.org https://2023.code4lib.org]

=== About Code4Lib ===
Code4Lib ([https://code4lib.org https://code4lib.org]) seeks to maintain a vibrant and diverse community of technology minded folks. We are developers and technologists for libraries, museums, and archives who have a strong commitment to open technologies. Code4Lib began as a simple mailing list in 2003 and held its first face-to-face meeting in 2005 in Chicago. The first official annual conference was held in 2006 in Corvallis, Oregon. Code4Lib is dedicated to providing a harassment-free community experience for everyone regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. For more information, please see our emerging '''[https://github.com/code4lib/code-of-conduct/blob/master/code_of_conduct.md CodeofConduct4Lib]'''. Code4Lib is dedicated to being a diverse and inclusive community of technologists seeking to share ideas and build collaboration.

=== Diversity Scholarship Eligibility, Criteria, And Requirements ===
* An applicant must be a member of a group not well-represented within the code4lib community, including but not limited to: women, people of color, LGBTQ+, ability/disability, non-binary gender identities, etc. We also invite applications from members of underrepresented and/or marginalized groups that don't fit into the categories listed above.
* An applicant must be interested in actively engaging with the Code4Lib community. For more information about Code4Lib, see the [https://2023.code4lib.org/general-info/about-c4l About Code4Lib Page].
* Applications will be evaluated based upon merit and financial needs.

=== Registration Details ===
Registration spots and hotel rooms are being held for scholarship recipients. If you can attend only if you receive a scholarship, there is no need to register for the conference or book a hotel room when registration opens. Code4Lib will assist you with both registration and hotel arrangements. If you register for the conference or book a hotel room, you will be reimbursed along with other expenses. Reimbursement for expenses will be provided to recipients during the conference.

=== How to Apply ===
Submit your application materials via the Code4Lib online form: https://goo.gl/forms/(url)

You will need to prepare:
# Your brief letter of interest, no more than '''( 200 words max ) words''', which:
## Identifies your eligibility for a diversity scholarship (200 max)
## '''Describes your financial needs to attend the conference (200 - 300 words)'''
## Describes how you see yourself benefiting from and participating in the Code4Lib 2018 conference and the general Code4Lib community '''(200 - 300 words)'''
# Your current resume or CV

'''Please note: Your brief letter of interest and current CV/resume should be '''combined into a single pdf'''. Your file should follow a “Lastname-Firstname.pdf” naming convention. Questions can be directed to code4libaward@gmail.com.'''

The application deadline is '''(Friday, January 13th, 2023) at 11:59 PM ET'''.

The scholarship committee will notify all applicants by '''(Monday, January 22nd)''', regardless of award results.

2023 Scholarship Documents/Disseminating the call

2022-12-05T15:48:39Z

Jtidal:

[[2023_Scholarship_Documents|2023 Scholarship Committee Documents]]

[[List_of_Listservs|List of Listservs]]

The 2023 Scholarship Committee disseminated the call for applications to at least the following outlets/groups:
* CODE4LIB list
* Asian Pacific American Librarians Association (APALA)
* We Here
* Black Caucus of the American Library Association
* REFORMA
* Bibliotecas para la Gente
* Joint Council of Librarians of Color
* American Indian Library Association
* Gay, Lesbian, Bisexual, Transgender Round Table of ALA
* ALA New Members Round Table
* Library Information Technology Association
* ALA Think Tank
* University of Illinois iSchool Alumni Connections
* St. John's University Division of Library & Information Science alumni group
* Library Leadership & Management Association (LLAMA) New Professional Section
* I Need A Library Job
* Association of College & Research Libraries (ACRL) College Libraries Section
* ALA Learning Roundtable
* California Libraries
* DIAL-CARL (Diversity In Academic Libraries - California Academic & Research Libraries)
* Library Employee Support Network
* Ethnic and Multicultural Information Exchange Round Table (EMIERT)
* University of Illinois iSchool Students of Color
* ACRL Residency Interest Group
* LLAMA Diversity Officers Discussion Group
* APALA mentoring channels
* LLAMA mentoring channels
* ALCTS mentoring program
* New York's Libraries Information Network (NYLINE)
* Digital Cultural Heritage DC Meetup
* DLF-ANNOUNCE (Digital Library Federation)
* DPLA Hubs (Digital Public Library of America)
* Roy Rosenzweig Center for History and New Media
* University of Maryland iSchool
* Society of American Archivists (SAA) Students and New Archivists Roundtable
* National Digital Stewardship Alliance
* SAA Archivists and Archives of Color Section
* Hear Me Code
* dh+lib
* ACRL Digital Humanities SIG
* Women Who Code DC
* Black Girls Code
* Maryland Institute for Technology in the Humanities
* Hack Library School
* University of Maryland Division of Student Affairs
* California Library Information eXchange
* California Academic Reference Librarians Discussion Interest Group - South

2023 Scholarship Documents/Disseminating the call

2022-12-05T15:48:15Z

Jtidal:

[[2023_Scholarship_Documents|2023 Scholarship Committee Documents]]

[[https://wiki.code4lib.org/List_of_Listservs|List of Listservs]]

The 2023 Scholarship Committee disseminated the call for applications to at least the following outlets/groups:
* CODE4LIB list
* Asian Pacific American Librarians Association (APALA)
* We Here
* Black Caucus of the American Library Association
* REFORMA
* Bibliotecas para la Gente
* Joint Council of Librarians of Color
* American Indian Library Association
* Gay, Lesbian, Bisexual, Transgender Round Table of ALA
* ALA New Members Round Table
* Library Information Technology Association
* ALA Think Tank
* University of Illinois iSchool Alumni Connections
* St. John's University Division of Library & Information Science alumni group
* Library Leadership & Management Association (LLAMA) New Professional Section
* I Need A Library Job
* Association of College & Research Libraries (ACRL) College Libraries Section
* ALA Learning Roundtable
* California Libraries
* DIAL-CARL (Diversity In Academic Libraries - California Academic & Research Libraries)
* Library Employee Support Network
* Ethnic and Multicultural Information Exchange Round Table (EMIERT)
* University of Illinois iSchool Students of Color
* ACRL Residency Interest Group
* LLAMA Diversity Officers Discussion Group
* APALA mentoring channels
* LLAMA mentoring channels
* ALCTS mentoring program
* New York's Libraries Information Network (NYLINE)
* Digital Cultural Heritage DC Meetup
* DLF-ANNOUNCE (Digital Library Federation)
* DPLA Hubs (Digital Public Library of America)
* Roy Rosenzweig Center for History and New Media
* University of Maryland iSchool
* Society of American Archivists (SAA) Students and New Archivists Roundtable
* National Digital Stewardship Alliance
* SAA Archivists and Archives of Color Section
* Hear Me Code
* dh+lib
* ACRL Digital Humanities SIG
* Women Who Code DC
* Black Girls Code
* Maryland Institute for Technology in the Humanities
* Hack Library School
* University of Maryland Division of Student Affairs
* California Library Information eXchange
* California Academic Reference Librarians Discussion Interest Group - South

2023 Scholarship Documents/Disseminating the call

2022-12-05T15:47:36Z

Jtidal:

[[2023_Scholarship_Documents|2023 Scholarship Committee Documents]]

[[https://wiki.code4lib.org/List_of_Listservs]]

The 2023 Scholarship Committee disseminated the call for applications to at least the following outlets/groups:
* CODE4LIB list
* Asian Pacific American Librarians Association (APALA)
* We Here
* Black Caucus of the American Library Association
* REFORMA
* Bibliotecas para la Gente
* Joint Council of Librarians of Color
* American Indian Library Association
* Gay, Lesbian, Bisexual, Transgender Round Table of ALA
* ALA New Members Round Table
* Library Information Technology Association
* ALA Think Tank
* University of Illinois iSchool Alumni Connections
* St. John's University Division of Library & Information Science alumni group
* Library Leadership & Management Association (LLAMA) New Professional Section
* I Need A Library Job
* Association of College & Research Libraries (ACRL) College Libraries Section
* ALA Learning Roundtable
* California Libraries
* DIAL-CARL (Diversity In Academic Libraries - California Academic & Research Libraries)
* Library Employee Support Network
* Ethnic and Multicultural Information Exchange Round Table (EMIERT)
* University of Illinois iSchool Students of Color
* ACRL Residency Interest Group
* LLAMA Diversity Officers Discussion Group
* APALA mentoring channels
* LLAMA mentoring channels
* ALCTS mentoring program
* New York's Libraries Information Network (NYLINE)
* Digital Cultural Heritage DC Meetup
* DLF-ANNOUNCE (Digital Library Federation)
* DPLA Hubs (Digital Public Library of America)
* Roy Rosenzweig Center for History and New Media
* University of Maryland iSchool
* Society of American Archivists (SAA) Students and New Archivists Roundtable
* National Digital Stewardship Alliance
* SAA Archivists and Archives of Color Section
* Hear Me Code
* dh+lib
* ACRL Digital Humanities SIG
* Women Who Code DC
* Black Girls Code
* Maryland Institute for Technology in the Humanities
* Hack Library School
* University of Maryland Division of Student Affairs
* California Library Information eXchange
* California Academic Reference Librarians Discussion Interest Group - South

2023 Scholarship Documents/Call for appliations

2022-12-05T15:44:12Z

Jtidal: /* Code4Lib 2023 Diversity Scholarships */

[[2023_Scholarship_Documents|2023 Scholarship Committee Documents]]

== Code4Lib 2023 Diversity Scholarships ==
We would like to thank our sponsors for supporting the Code4Lib 2018 Diversity Scholarships. Currently, 10 scholarships are fully funded.

* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)

As part of Code4Lib's ongoing commitment to reducing economic barriers that prevent participation for underrepresented groups, and to achieving a balanced representation of the human experience, we are pleased to announce that we are now seeking applicants for our [https://2023.code4lib.org/general-info/scholarships 2023 Diversity Scholarship program!] The Code4Lib Scholarship Committee hopes to award (number) Diversity Scholarships, based on merit and need. Each scholarship will cover up to $1,500 for travel costs, lodging, and conference fees for selected applicants to attend the 2023 Code4Lib Conference in Princeton, NJ. The deadline for applications is '''Friday, January 13, 2023''' at 11:59 PM ET.

The scholarship will cover conference registration and hotel accommodations up front to scholarship awardees. Other incidentals like travel and meals may be reimbursed based on the amount awarded. Reimbursement will be managed independently at the conference. Pairing up housing with other scholarship awardees or conference attendees may also be accommodated. Please contact code4libaward@gmail.com with any questions about this arrangement. We want to ensure that financial issues do not discourage anyone from applying to this award.

We do not expect scholarship recipients to be responsible for being an ambassador for their group or an educator of others during the conference. While learning and exchange may happen as a result of interactions between participants, scholarship recipients are encouraged to focus on getting the most out of their experience and have no special duties or obligations apart from conference attendance, engaged participation to their comfort level, and giving us feedback on their experience.

Code4Lib conference 2023: [https://2023.code4lib.org https://2023.code4lib.org]

=== About Code4Lib ===
Code4Lib ([https://code4lib.org https://code4lib.org]) seeks to maintain a vibrant and diverse community of technology minded folks. We are developers and technologists for libraries, museums, and archives who have a strong commitment to open technologies. Code4Lib began as a simple mailing list in 2003 and held its first face-to-face meeting in 2005 in Chicago. The first official annual conference was held in 2006 in Corvallis, Oregon. Code4Lib is dedicated to providing a harassment-free community experience for everyone regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. For more information, please see our emerging '''[https://github.com/code4lib/code-of-conduct/blob/master/code_of_conduct.md CodeofConduct4Lib]'''. Code4Lib is dedicated to being a diverse and inclusive community of technologists seeking to share ideas and build collaboration.

=== Diversity Scholarship Eligibility, Criteria, And Requirements ===
* An applicant must be a member of a group not well-represented within the code4lib community, including but not limited to: women, people of color, LGBTQ+, ability/disability, non-binary gender identities, etc. We also invite applications from members of underrepresented and/or marginalized groups that don't fit into the categories listed above.
* An applicant must be interested in actively engaging with the Code4Lib community. For more information about Code4Lib, see the [https://2023.code4lib.org/general-info/about-c4l About Code4Lib Page].
* Applications will be evaluated based upon merit and financial needs.

=== Registration Details ===
Registration spots and hotel rooms are being held for scholarship recipients. If you can attend only if you receive a scholarship, there is no need to register for the conference or book a hotel room when registration opens. Code4Lib will assist you with both registration and hotel arrangements. If you register for the conference or book a hotel room, you will be reimbursed along with other expenses. Reimbursement for expenses will be provided to recipients during the conference.

=== How to Apply ===
Submit your application materials via the Code4Lib online form: https://goo.gl/forms/(url)

You will need to prepare:
# Your brief letter of interest, no more than '''( ) words''', which:
## Identifies your eligibility for a diversity scholarship (100 words)
## '''Describes your financial needs to attend the conference (100 words)'''
## Describes how you see yourself benefiting from and participating in the Code4Lib 2018 conference and the general Code4Lib community '''(200 words)'''
# Your current resume or CV
# '''Contact information for one reference who can speak to your professional goals and/or achievements'''

'''Please note: Your brief letter of interest and current CV/resume should be '''combined into a single pdf'''. Your file should follow a “Lastname-Firstname.pdf” naming convention. Questions can be directed to code4libaward@gmail.com.'''

The application deadline is '''(deadline date) at 11:59 PM ET'''.

The scholarship committee will notify all applicants by '''(date)''', regardless of award results.

2023 Scholarship Documents/Call for appliations

2022-12-05T15:43:44Z

Jtidal: /* Code4Lib 2023 Diversity Scholarships */

[[2023_Scholarship_Documents|2023 Scholarship Committee Documents]]

== Code4Lib 2023 Diversity Scholarships ==
We would like to thank our sponsors for supporting the Code4Lib 2018 Diversity Scholarships. Currently, 10 scholarships are fully funded.

* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)
* sponsor ( scholarship)

As part of Code4Lib's ongoing commitment to reducing economic barriers that prevent participation for underrepresented groups, and to achieving a balanced representation of the human experience, we are pleased to announce that we are now seeking applicants for our [https://2023.code4lib.org/general-info/scholarships 2023 Diversity Scholarship program!] The Code4Lib Scholarship Committee hopes to award (number) Diversity Scholarships, based on merit and need. Each scholarship will cover up to $1,500 for travel costs, lodging, and conference fees for selected applicants to attend the 2023 Code4Lib Conference in Princeton, NJ. The deadline for applications is '''January 13, 2023''' at 11:59 PM ET.

The scholarship will cover conference registration and hotel accommodations up front to scholarship awardees. Other incidentals like travel and meals may be reimbursed based on the amount awarded. Reimbursement will be managed independently at the conference. Pairing up housing with other scholarship awardees or conference attendees may also be accommodated. Please contact code4libaward@gmail.com with any questions about this arrangement. We want to ensure that financial issues do not discourage anyone from applying to this award.

We do not expect scholarship recipients to be responsible for being an ambassador for their group or an educator of others during the conference. While learning and exchange may happen as a result of interactions between participants, scholarship recipients are encouraged to focus on getting the most out of their experience and have no special duties or obligations apart from conference attendance, engaged participation to their comfort level, and giving us feedback on their experience.

Code4Lib conference 2023: [https://2023.code4lib.org https://2023.code4lib.org]

=== About Code4Lib ===
Code4Lib ([https://code4lib.org https://code4lib.org]) seeks to maintain a vibrant and diverse community of technology minded folks. We are developers and technologists for libraries, museums, and archives who have a strong commitment to open technologies. Code4Lib began as a simple mailing list in 2003 and held its first face-to-face meeting in 2005 in Chicago. The first official annual conference was held in 2006 in Corvallis, Oregon. Code4Lib is dedicated to providing a harassment-free community experience for everyone regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. For more information, please see our emerging '''[https://github.com/code4lib/code-of-conduct/blob/master/code_of_conduct.md CodeofConduct4Lib]'''. Code4Lib is dedicated to being a diverse and inclusive community of technologists seeking to share ideas and build collaboration.

=== Diversity Scholarship Eligibility, Criteria, And Requirements ===
* An applicant must be a member of a group not well-represented within the code4lib community, including but not limited to: women, people of color, LGBTQ+, ability/disability, non-binary gender identities, etc. We also invite applications from members of underrepresented and/or marginalized groups that don't fit into the categories listed above.
* An applicant must be interested in actively engaging with the Code4Lib community. For more information about Code4Lib, see the [https://2023.code4lib.org/general-info/about-c4l About Code4Lib Page].
* Applications will be evaluated based upon merit and financial needs.

=== Registration Details ===
Registration spots and hotel rooms are being held for scholarship recipients. If you can attend only if you receive a scholarship, there is no need to register for the conference or book a hotel room when registration opens. Code4Lib will assist you with both registration and hotel arrangements. If you register for the conference or book a hotel room, you will be reimbursed along with other expenses. Reimbursement for expenses will be provided to recipients during the conference.

=== How to Apply ===
Submit your application materials via the Code4Lib online form: https://goo.gl/forms/(url)

You will need to prepare:
# Your brief letter of interest, no more than '''( ) words''', which:
## Identifies your eligibility for a diversity scholarship (100 words)
## '''Describes your financial needs to attend the conference (100 words)'''
## Describes how you see yourself benefiting from and participating in the Code4Lib 2018 conference and the general Code4Lib community '''(200 words)'''
# Your current resume or CV
# '''Contact information for one reference who can speak to your professional goals and/or achievements'''

'''Please note: Your brief letter of interest and current CV/resume should be '''combined into a single pdf'''. Your file should follow a “Lastname-Firstname.pdf” naming convention. Questions can be directed to code4libaward@gmail.com.'''

The application deadline is '''(deadline date) at 11:59 PM ET'''.

The scholarship committee will notify all applicants by '''(date)''', regardless of award results.

Code4Lib 2023 Conference Committees

2022-10-24T16:01:11Z

Jtidal:

= Code4Lib 2023 Conference Committees =

Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2023 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. 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 (LPC) to each committee.

== Location and Dates ==

* Location: Princeton University
* Dates: March 14-17, 2023

== Local Planning Committee ==
The LPC is charged with running the show such as overall timeline, budgeting, coordinating of locations and logistics, wrangler of committees, and communicating with the community.

* Kate Lynch - (katelynch@princeton.edu) - Chair, Primary Contact
* Esmé Cowles - (escowles@princeton.edu) - Documentarian & Secondary Contact
* Greg Murray - (gregory.murray@ptsem.edu) - Tertiary Contact
* Hillel Arnold - (harnold@rockarch.org) - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Website Working Group ==
This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users).

[[2023 Website Working Group Documents|2023 Website Working Group Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Kate Deibel (kndeibel@metageekery.org) - Accessibility Committee Contact
* Craig Rosenbeck (rosenbeck_craig@roberts.edu) - Volunteer
* Robert-Anthony Lee-Faison (rl3667-at-princeton-dot-edu) - Volunteer
* Your Name Here - Volunteer

== Budget and Sponsorship Committee ==
This group involves working with the Planning Committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.

[[2023 Budget and Sponsorship Documents|2023 Budget and Sponsorship Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Linda Salvesen - (salvesenl@wpunj.edu) - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Keynote Committee ==
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.

[[2023 Keynote Documents|2023 Keynote Documents]]

[[2023 Keynote Speakers Nominations|2023 Keynote Speakers Nominations]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Ranti Junus - Volunteer
* Tyler N Wade-(tw8766@princeton.edu) - Volunteer
* Your Name Here - Volunteer

== Pre-conference Committee ==
This committee plans the pre or post-conference day (TBD). It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.

[[2023 Pre-conference Documents|2023 Pre-conference Documents]]

* Ann Marie Mesco - (mesco@andrew.cmu.edu) - Primary Contact, Chair
* Andrea Schurr - (Andrea-Schurr@utc.edu) - Secondary Contact, CoChair
* Hardy Pottinger - (hardy.pottinger@ucop.edu) - Documentarian
* Eric Morgan <emorgan@nd.edu> - Volunteer, grip, and all-around lackey
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== 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. Committee membership will be capped at 10 members.

[[2023 Program Documents|2023 Program Documents]]

* Matt Sherman - (matt.r.sherman-at-gmail-com) - Primary Contact, Chair
* Dre (akorphan) - Secondary Contact, CoChair
* Andrew Battelini - (abattel@emory.edu)- Documentarian
* Ranti Junus (junus-at-msu-edu) - Volunteer
* Emily Boss (eboss-at-unr-edu) - Volunteer
* [[User:highermath|Cary Gordon]] - Volunteer

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

[[2023 Scholarship Documents|2023 Scholarship Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* Bess Sadler - (bess-dot-sadler-at-princeton-dot-edu) - Secondary Contact, CoChair
* Soojeong Herring - (soojeong-dot-herring-at-colostate-dot-edu) - Documentarian
* Yongming Wang - Volunteer
* Junior Tidal - (jtidal-at-citytech-dot-cuny-dot-edu)- Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
This group responds to violations and concerns regarding [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees. More details here: https://2022.code4lib.org/conduct/#volunteers

* Coordinator: Bess Sadler - bess-dot-sadler-at-princeton-dot-edu
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2023 T-Shirt Documents|2023 T-Shirt Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

'''Looking for opportunities to help out at the conference? See [[2023 Conference Volunteers]]'''

[[2023 Online Volunteer Documents|2023 Online Volunteer Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==

This committee organizes social activities for the conference, including the Newcomer Dinner (for in-person conferences) and other after/before conference hours activities (for in-person and virtual conferences). This committee also facilitates the process for attendee-planned social activities for virtual and in-person conferences.

2023 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Streaming Video Committee ==
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks (?), and possibly running the camera during the conference.

[[2023 Streaming Video Documents|2023 Streaming Video Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* [[User:ksclarke|Kevin S. Clarke]] - Volunteer
* [[User:highermath|Cary Gordon]] - Volunteer

== Code4Lib 2023 Host Voting Committee ==
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process.

[[2023 Host Voting Documents|2023 Host Voting Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Book Giveaway Committee ==
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies (for example, free private repo from Github or license for oXygen). They also handle the raffle at the conference (with a randomizer to do the drawing of names).

[[2023 Book Giveaway Documents|2023 Book Giveaway Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== IRC and Slack Committee ==
This committee will assist attendees with IRC and Slack.

[[2023 IRC and Slack Documents|2023 IRC and Slack Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Accessibility Committee ==
Document and address major points of the conference that are not accessible for conference attendees.

[[2023 Accessibility Documents|2023 Accessibility Documents]]

* Kate Deibel - (kndeibel@metageekery.org) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Whatever Committee ==
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.

[[2023 Whatever Documents|2023 Whatever Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

[[Category:Code4Lib2023]]

Code4Lib 2023 Conference Committees

2022-10-24T16:00:45Z

Jtidal:

= Code4Lib 2023 Conference Committees =

Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2023 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. 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 (LPC) to each committee.

== Location and Dates ==

* Location: Princeton University
* Dates: March 14-17, 2023

== Local Planning Committee ==
The LPC is charged with running the show such as overall timeline, budgeting, coordinating of locations and logistics, wrangler of committees, and communicating with the community.

* Kate Lynch - (katelynch@princeton.edu) - Chair, Primary Contact
* Esmé Cowles - (escowles@princeton.edu) - Documentarian & Secondary Contact
* Greg Murray - (gregory.murray@ptsem.edu) - Tertiary Contact
* Hillel Arnold - (harnold@rockarch.org) - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Website Working Group ==
This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users).

[[2023 Website Working Group Documents|2023 Website Working Group Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Kate Deibel (kndeibel@metageekery.org) - Accessibility Committee Contact
* Craig Rosenbeck (rosenbeck_craig@roberts.edu) - Volunteer
* Robert-Anthony Lee-Faison (rl3667-at-princeton-dot-edu) - Volunteer
* Your Name Here - Volunteer

== Budget and Sponsorship Committee ==
This group involves working with the Planning Committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.

[[2023 Budget and Sponsorship Documents|2023 Budget and Sponsorship Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Linda Salvesen - (salvesenl@wpunj.edu) - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Keynote Committee ==
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.

[[2023 Keynote Documents|2023 Keynote Documents]]

[[2023 Keynote Speakers Nominations|2023 Keynote Speakers Nominations]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Ranti Junus - Volunteer
* Tyler N Wade-(tw8766@princeton.edu) - Volunteer
* Your Name Here - Volunteer

== Pre-conference Committee ==
This committee plans the pre or post-conference day (TBD). It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.

[[2023 Pre-conference Documents|2023 Pre-conference Documents]]

* Ann Marie Mesco - (mesco@andrew.cmu.edu) - Primary Contact, Chair
* Andrea Schurr - (Andrea-Schurr@utc.edu) - Secondary Contact, CoChair
* Hardy Pottinger - (hardy.pottinger@ucop.edu) - Documentarian
* Eric Morgan <emorgan@nd.edu> - Volunteer, grip, and all-around lackey
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== 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. Committee membership will be capped at 10 members.

[[2023 Program Documents|2023 Program Documents]]

* Matt Sherman - (matt.r.sherman-at-gmail-com) - Primary Contact, Chair
* Dre (akorphan) - Secondary Contact, CoChair
* Andrew Battelini - (abattel@emory.edu)- Documentarian
* Ranti Junus (junus-at-msu-edu) - Volunteer
* Emily Boss (eboss-at-unr-edu) - Volunteer
* [[User:highermath|Cary Gordon]] - Volunteer

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

[[2023 Scholarship Documents|2023 Scholarship Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* Bess Sadler - (bess-dot-sadler-at-princeton-dot-edu) - Secondary Contact, CoChair
* Soojeong Herring - (soojeong-dot-herring-at-colostate-dot-edu) - Documentarian
* Yongming Wang - Volunteer
* Junior Tidal(jtidal-at-citytech-dot-cuny-dot-edu)- Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
This group responds to violations and concerns regarding [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees. More details here: https://2022.code4lib.org/conduct/#volunteers

* Coordinator: Bess Sadler - bess-dot-sadler-at-princeton-dot-edu
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2023 T-Shirt Documents|2023 T-Shirt Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

'''Looking for opportunities to help out at the conference? See [[2023 Conference Volunteers]]'''

[[2023 Online Volunteer Documents|2023 Online Volunteer Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==

This committee organizes social activities for the conference, including the Newcomer Dinner (for in-person conferences) and other after/before conference hours activities (for in-person and virtual conferences). This committee also facilitates the process for attendee-planned social activities for virtual and in-person conferences.

2023 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Streaming Video Committee ==
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks (?), and possibly running the camera during the conference.

[[2023 Streaming Video Documents|2023 Streaming Video Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* [[User:ksclarke|Kevin S. Clarke]] - Volunteer
* [[User:highermath|Cary Gordon]] - Volunteer

== Code4Lib 2023 Host Voting Committee ==
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process.

[[2023 Host Voting Documents|2023 Host Voting Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Book Giveaway Committee ==
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies (for example, free private repo from Github or license for oXygen). They also handle the raffle at the conference (with a randomizer to do the drawing of names).

[[2023 Book Giveaway Documents|2023 Book Giveaway Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== IRC and Slack Committee ==
This committee will assist attendees with IRC and Slack.

[[2023 IRC and Slack Documents|2023 IRC and Slack Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Accessibility Committee ==
Document and address major points of the conference that are not accessible for conference attendees.

[[2023 Accessibility Documents|2023 Accessibility Documents]]

* Kate Deibel - (kndeibel@metageekery.org) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Whatever Committee ==
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.

[[2023 Whatever Documents|2023 Whatever Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

[[Category:Code4Lib2023]]

Code4Lib Journal Deadlines

2022-08-30T17:44:45Z

Jtidal: /* Fifty-fifth issue */

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

== Formula for calculating deadlines ==

A rough guideline based on recent issues:

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

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

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

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

===Fifty-fifth issue===
Coordinating Editor: Junior Tidal

* Call for proposals: Tuesday, September 6, 2022
* Second call for proposals: Tuesday, September 27, 2022 (if necessary)
* Proposals due: Saturday, October 8, 2022
* Proposals accepted: Saturday, October 15, 2022
* First draft due: Saturday, November 12, 2022
* Second draft due: Saturday, December 10, 2022
* Publication date: Tuesday, January 10, 2023

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

* Call for proposals: Monday, April 18, 2022
* 2nd call for proposals: Monday, May 9, 2022 (if necessary)
* Proposals due: Friday, May 20, 2022
* Proposals accepted: Friday, May 27, 2022
* First draft due: Friday, June 24, 2022
* Second draft due: Friday, July 22, 2022
* Publication date: Monday, August 22, 2022

===Fifty-third issue===
Coordinating Editor: Ron Peterson
* Call for proposals: Monday, December 20, 2021
* Second call for proposals: Monday, January 10, 2022 (if necessary)
* Proposals due: Friday, January 21, 2022
* Proposals accepted: Friday, January 28, 2022
* First draft due: Friday, February 25, 2022
* Second draft due: Friday, March 25, 2022
* Publication date: Monday, April 25, 2022

===Fifty-second issue===
Coordinating Editor: Mark Swenson
* Call for proposals: Monday, May 10, 2021
* Second call for proposals: Tuesday, June 1, 2021 (if necessary)
* Proposals due: Friday, June 11, 2021
* Proposals accepted: Friday, June 18, 2021
* First draft due: Friday, July 16, 2021
* Second draft due: Friday, August 13, 2021
* Publication date: Monday, September 13, 2021

===Fifty-first issue===
Coordinating Editor: Edward Corrado

Note date changes from originally published schedule

* Call for proposals: Thursday, February 4, 2021
* Second call for proposals: Thursday, February 25, 2021 (if necessary)
* Proposals due: Monday, March 15, 2021
* Proposals accepted: Monday, March 22, 2021
* First draft due: Monday, April 19, 2021
* Second draft due: Monday, May 10, 2021
* Publication date: Thursday, June 10, 2021

===Fiftieth issue===

Coordinating Editor: Eric Hanson

''Note: Issue dates adjusted to skip one quarter's publication.''
* Call for proposals: Monday, October 5, 2020 <del>July 6, 2020</del>
* Second call for proposals: Monday, October 26, 2020 <del>July 27, 2020</del> (if necessary)
* Proposals due: Friday, November 6, 2020 <del>August 7, 2020</del>
* Proposals accepted: Friday, November 13, 2020 <del>August 14, 2020</del>
* First draft due: Friday, December 11, 2020 <del>September 11, 2020</del>
* Second draft due: Friday, January 8, 2021 <del>October 9, 2020</del>
* Publication date: Monday, February 8, 2021 <del>November 9, 2020</del>

===Forty-ninth issue===

Coordinating Editor: Peter Murray

* Call for proposals: Monday, March 30, 2020
* Second call for proposals: Monday, April 20, 2020 (if necessary)
* Proposals due: Friday, May 1, 2020
* Proposals accepted: Friday, May 8, 2020
* First draft due: Friday, June 5, 2020
* Second draft due: Friday, July 3, 2020
* Publication date: Monday, August 3, 2020

===Forty-eighth issue===

Coordinating Editor: Brighid M. Gonzales

* Call for proposals: Monday, January 6, 2020
* Second call for proposals: Monday, January 27, 2020 (if necessary)
* Proposals due: Friday, February 7, 2020
* Proposals accepted: Friday, February 14, 2020
* First draft due: Friday, March 13, 2020
* Second draft due: Friday, April 10, 2020
* Publication date: Monday, May 11, 2020

===Forty-seventh issue===

Coordinating Editor: Péter Király

* Call for proposals: Monday, September 30, 2019
* Second call for proposals: Monday, October 21, 2019 (if necessary)
* Proposals due: Friday, November 1, 2019
* Proposals accepted: Friday, November 15, 2019
* First draft due: Friday, December 13, 2019
* Second draft due: Friday, January 10, 2020
* Publication date: Monday, February 10, 2020

===Forty-sixth issue===

Coordinating Editor: Sara Amato
* Call for proposals: Monday, July 1, 2019
* Second call for proposals: Monday, July 22, 2019 (if necessary)
* Proposals due: Friday, August 2, 2019
* Proposals accepted: Friday, August 9, 2019
* First draft due: Friday, September 6, 2019
* Second draft due: Friday, October 4, 2019
* Publication date: Monday, November 4, 2019

===Forty-fifth issue===

Coordinating Editor: Eric Hanson
* Call for proposals: Monday, April 1, 2019
* Second call for proposals: Monday, April 22, 2019 (if necessary)
* Proposals due: Friday, May 3, 2019
* Proposals accepted: Friday, May 10, 2019
* First draft due: Friday, June 7, 2019
* Second draft due: Friday, July 5, 2019
* Publication date: Monday, August 5, 2019

===Forty-fourth issue===

Coordinating Editor: Junior Tidal
* Call for proposals: Monday, December 31, 2018
* Second call for proposals: Monday, January 21, 2019 (if necessary)
* Proposals due: Friday, February 1, 2019
* Proposals accepted: Friday, February 8, 2019
* First draft due: Friday, March 8, 2019
* Second draft due: Friday, April 5, 2019
* Publication date: Monday, May 6, 2019

===Forty-third issue===

Coordinating Editor: Peter Murray
* Call for proposals: Monday, October 1, 2018
* Second call for proposals: Monday, October 22, 2018 (if necessary)
* Proposals due: Friday, November 2, 2018
* Proposals accepted: Friday, November 9, 2018
* First draft due: Friday, December 7, 2018
* Second draft due: Friday, January 11, 2019
* Publication date: Monday, February 11, 2019

===Forty-second issue===

Coordinating Editor: Andrew Darby
* Call for proposals: Monday, July 2, 2018
* Second call for proposals: Monday, July 23, 2018 (if necessary)
* Proposals due: Friday, August 3, 2018
* Proposals accepted: Friday, August 10, 2018
* First draft due: Friday, September 7, 2018
* Second draft due: Friday, October 5, 2018
* Publication date: Monday, November 5, 2018

===Forty-first issue===

Coordinating Editor: Ron Peterson
*Call for proposals: Monday, April 17, 2017
*Second call for proposals: Monday, April 30, 2017 (if necessary)
*Proposals due: Friday, May 11, 2017
*Proposals accepted: Friday, May 18, 2017
*First draft due: Friday, June 8, 2017
*Second draft due: Friday, July 6, 2017
*Publication date: Monday, August 6, 2018

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

2022-06-02T14:38:13Z

Jtidal: updated dates

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

===Fifty-fifth issue===
Coordinating Editor: Junior Tidal

* Call for proposals: Tuesday, August 16, 2022
* Second call for proposals: Tuesday, September 6, 2022 (if necessary)
* Proposals due: Saturday, September 17, 2022
* Proposals accepted: Saturday, September 24, 2022
* First draft due: Saturday, October 22, 2022
* Second draft due: Saturday, November 19, 2022
* Publication date: Tuesday, December 20, 2022

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

* Call for proposals: Monday, April 18, 2022
* 2nd call for proposals: Monday, May 9, 2022 (if necessary)
* Proposals due: Friday, May 20, 2022
* Proposals accepted: Friday, May 27, 2022
* First draft due: Friday, June 24, 2022
* Second draft due: Friday, July 22, 2022
* Publication date: Monday, August 22, 2022

===Fifty-third issue===
Coordinating Editor: Ron Peterson
* Call for proposals: Monday, December 20, 2021
* Second call for proposals: Monday, January 10, 2022 (if necessary)
* Proposals due: Friday, January 21, 2022
* Proposals accepted: Friday, January 28, 2022
* First draft due: Friday, February 25, 2022
* Second draft due: Friday, March 25, 2022
* Publication date: Monday, April 25, 2022

===Fifty-second issue===
Coordinating Editor: Mark Swenson
* Call for proposals: Monday, May 10, 2021
* Second call for proposals: Tuesday, June 1, 2021 (if necessary)
* Proposals due: Friday, June 11, 2021
* Proposals accepted: Friday, June 18, 2021
* First draft due: Friday, July 16, 2021
* Second draft due: Friday, August 13, 2021
* Publication date: Monday, September 13, 2021

===Fifty-first issue===
Coordinating Editor: Edward Corrado

Note date changes from originally published schedule

* Call for proposals: Thursday, February 4, 2021
* Second call for proposals: Thursday, February 25, 2021 (if necessary)
* Proposals due: Monday, March 15, 2021
* Proposals accepted: Monday, March 22, 2021
* First draft due: Monday, April 19, 2021
* Second draft due: Monday, May 10, 2021
* Publication date: Thursday, June 10, 2021

===Fiftieth issue===

Coordinating Editor: Eric Hanson

''Note: Issue dates adjusted to skip one quarter's publication.''
* Call for proposals: Monday, October 5, 2020 <del>July 6, 2020</del>
* Second call for proposals: Monday, October 26, 2020 <del>July 27, 2020</del> (if necessary)
* Proposals due: Friday, November 6, 2020 <del>August 7, 2020</del>
* Proposals accepted: Friday, November 13, 2020 <del>August 14, 2020</del>
* First draft due: Friday, December 11, 2020 <del>September 11, 2020</del>
* Second draft due: Friday, January 8, 2021 <del>October 9, 2020</del>
* Publication date: Monday, February 8, 2021 <del>November 9, 2020</del>

===Forty-ninth issue===

Coordinating Editor: Peter Murray

* Call for proposals: Monday, March 30, 2020
* Second call for proposals: Monday, April 20, 2020 (if necessary)
* Proposals due: Friday, May 1, 2020
* Proposals accepted: Friday, May 8, 2020
* First draft due: Friday, June 5, 2020
* Second draft due: Friday, July 3, 2020
* Publication date: Monday, August 3, 2020

===Forty-eighth issue===

Coordinating Editor: Brighid M. Gonzales

* Call for proposals: Monday, January 6, 2020
* Second call for proposals: Monday, January 27, 2020 (if necessary)
* Proposals due: Friday, February 7, 2020
* Proposals accepted: Friday, February 14, 2020
* First draft due: Friday, March 13, 2020
* Second draft due: Friday, April 10, 2020
* Publication date: Monday, May 11, 2020

===Forty-seventh issue===

Coordinating Editor: Péter Király

* Call for proposals: Monday, September 30, 2019
* Second call for proposals: Monday, October 21, 2019 (if necessary)
* Proposals due: Friday, November 1, 2019
* Proposals accepted: Friday, November 15, 2019
* First draft due: Friday, December 13, 2019
* Second draft due: Friday, January 10, 2020
* Publication date: Monday, February 10, 2020

===Forty-sixth issue===

Coordinating Editor: Sara Amato
* Call for proposals: Monday, July 1, 2019
* Second call for proposals: Monday, July 22, 2019 (if necessary)
* Proposals due: Friday, August 2, 2019
* Proposals accepted: Friday, August 9, 2019
* First draft due: Friday, September 6, 2019
* Second draft due: Friday, October 4, 2019
* Publication date: Monday, November 4, 2019

===Forty-fifth issue===

Coordinating Editor: Eric Hanson
* Call for proposals: Monday, April 1, 2019
* Second call for proposals: Monday, April 22, 2019 (if necessary)
* Proposals due: Friday, May 3, 2019
* Proposals accepted: Friday, May 10, 2019
* First draft due: Friday, June 7, 2019
* Second draft due: Friday, July 5, 2019
* Publication date: Monday, August 5, 2019

===Forty-fourth issue===

Coordinating Editor: Junior Tidal
* Call for proposals: Monday, December 31, 2018
* Second call for proposals: Monday, January 21, 2019 (if necessary)
* Proposals due: Friday, February 1, 2019
* Proposals accepted: Friday, February 8, 2019
* First draft due: Friday, March 8, 2019
* Second draft due: Friday, April 5, 2019
* Publication date: Monday, May 6, 2019

===Forty-third issue===

Coordinating Editor: Peter Murray
* Call for proposals: Monday, October 1, 2018
* Second call for proposals: Monday, October 22, 2018 (if necessary)
* Proposals due: Friday, November 2, 2018
* Proposals accepted: Friday, November 9, 2018
* First draft due: Friday, December 7, 2018
* Second draft due: Friday, January 11, 2019
* Publication date: Monday, February 11, 2019

===Forty-second issue===

Coordinating Editor: Andrew Darby
* Call for proposals: Monday, July 2, 2018
* Second call for proposals: Monday, July 23, 2018 (if necessary)
* Proposals due: Friday, August 3, 2018
* Proposals accepted: Friday, August 10, 2018
* First draft due: Friday, September 7, 2018
* Second draft due: Friday, October 5, 2018
* Publication date: Monday, November 5, 2018

===Forty-first issue===

Coordinating Editor: Ron Peterson
*Call for proposals: Monday, April 17, 2017
*Second call for proposals: Monday, April 30, 2017 (if necessary)
*Proposals due: Friday, May 11, 2017
*Proposals accepted: Friday, May 18, 2017
*First draft due: Friday, June 8, 2017
*Second draft due: Friday, July 6, 2017
*Publication date: Monday, August 6, 2018

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

2022-06-02T14:20:13Z

Jtidal: /* Fifty-fifth issue */

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

== Formula for calculating deadlines ==

A rough guideline based on recent issues:

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

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

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

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

===Fifty-fifth issue===
Coordinating Editor: Junior Tidal

* Call for proposals:
* Second call for proposals:
* Proposals due:
* Proposals accepted:
* First draft due:
* Second draft due:
* Publication date:

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

* Call for proposals: Monday, April 18, 2022
* 2nd call for proposals: Monday, May 9, 2022 (if necessary)
* Proposals due: Friday, May 20, 2022
* Proposals accepted: Friday, May 27, 2022
* First draft due: Friday, June 24, 2022
* Second draft due: Friday, July 22, 2022
* Publication date: Monday, August 22, 2022

===Fifty-third issue===
Coordinating Editor: Ron Peterson
* Call for proposals: Monday, December 20, 2021
* Second call for proposals: Monday, January 10, 2022 (if necessary)
* Proposals due: Friday, January 21, 2022
* Proposals accepted: Friday, January 28, 2022
* First draft due: Friday, February 25, 2022
* Second draft due: Friday, March 25, 2022
* Publication date: Monday, April 25, 2022

===Fifty-second issue===
Coordinating Editor: Mark Swenson
* Call for proposals: Monday, May 10, 2021
* Second call for proposals: Tuesday, June 1, 2021 (if necessary)
* Proposals due: Friday, June 11, 2021
* Proposals accepted: Friday, June 18, 2021
* First draft due: Friday, July 16, 2021
* Second draft due: Friday, August 13, 2021
* Publication date: Monday, September 13, 2021

===Fifty-first issue===
Coordinating Editor: Edward Corrado

Note date changes from originally published schedule

* Call for proposals: Thursday, February 4, 2021
* Second call for proposals: Thursday, February 25, 2021 (if necessary)
* Proposals due: Monday, March 15, 2021
* Proposals accepted: Monday, March 22, 2021
* First draft due: Monday, April 19, 2021
* Second draft due: Monday, May 10, 2021
* Publication date: Thursday, June 10, 2021

===Fiftieth issue===

Coordinating Editor: Eric Hanson

''Note: Issue dates adjusted to skip one quarter's publication.''
* Call for proposals: Monday, October 5, 2020 <del>July 6, 2020</del>
* Second call for proposals: Monday, October 26, 2020 <del>July 27, 2020</del> (if necessary)
* Proposals due: Friday, November 6, 2020 <del>August 7, 2020</del>
* Proposals accepted: Friday, November 13, 2020 <del>August 14, 2020</del>
* First draft due: Friday, December 11, 2020 <del>September 11, 2020</del>
* Second draft due: Friday, January 8, 2021 <del>October 9, 2020</del>
* Publication date: Monday, February 8, 2021 <del>November 9, 2020</del>

===Forty-ninth issue===

Coordinating Editor: Peter Murray

* Call for proposals: Monday, March 30, 2020
* Second call for proposals: Monday, April 20, 2020 (if necessary)
* Proposals due: Friday, May 1, 2020
* Proposals accepted: Friday, May 8, 2020
* First draft due: Friday, June 5, 2020
* Second draft due: Friday, July 3, 2020
* Publication date: Monday, August 3, 2020

===Forty-eighth issue===

Coordinating Editor: Brighid M. Gonzales

* Call for proposals: Monday, January 6, 2020
* Second call for proposals: Monday, January 27, 2020 (if necessary)
* Proposals due: Friday, February 7, 2020
* Proposals accepted: Friday, February 14, 2020
* First draft due: Friday, March 13, 2020
* Second draft due: Friday, April 10, 2020
* Publication date: Monday, May 11, 2020

===Forty-seventh issue===

Coordinating Editor: Péter Király

* Call for proposals: Monday, September 30, 2019
* Second call for proposals: Monday, October 21, 2019 (if necessary)
* Proposals due: Friday, November 1, 2019
* Proposals accepted: Friday, November 15, 2019
* First draft due: Friday, December 13, 2019
* Second draft due: Friday, January 10, 2020
* Publication date: Monday, February 10, 2020

===Forty-sixth issue===

Coordinating Editor: Sara Amato
* Call for proposals: Monday, July 1, 2019
* Second call for proposals: Monday, July 22, 2019 (if necessary)
* Proposals due: Friday, August 2, 2019
* Proposals accepted: Friday, August 9, 2019
* First draft due: Friday, September 6, 2019
* Second draft due: Friday, October 4, 2019
* Publication date: Monday, November 4, 2019

===Forty-fifth issue===

Coordinating Editor: Eric Hanson
* Call for proposals: Monday, April 1, 2019
* Second call for proposals: Monday, April 22, 2019 (if necessary)
* Proposals due: Friday, May 3, 2019
* Proposals accepted: Friday, May 10, 2019
* First draft due: Friday, June 7, 2019
* Second draft due: Friday, July 5, 2019
* Publication date: Monday, August 5, 2019

===Forty-fourth issue===

Coordinating Editor: Junior Tidal
* Call for proposals: Monday, December 31, 2018
* Second call for proposals: Monday, January 21, 2019 (if necessary)
* Proposals due: Friday, February 1, 2019
* Proposals accepted: Friday, February 8, 2019
* First draft due: Friday, March 8, 2019
* Second draft due: Friday, April 5, 2019
* Publication date: Monday, May 6, 2019

===Forty-third issue===

Coordinating Editor: Peter Murray
* Call for proposals: Monday, October 1, 2018
* Second call for proposals: Monday, October 22, 2018 (if necessary)
* Proposals due: Friday, November 2, 2018
* Proposals accepted: Friday, November 9, 2018
* First draft due: Friday, December 7, 2018
* Second draft due: Friday, January 11, 2019
* Publication date: Monday, February 11, 2019

===Forty-second issue===

Coordinating Editor: Andrew Darby
* Call for proposals: Monday, July 2, 2018
* Second call for proposals: Monday, July 23, 2018 (if necessary)
* Proposals due: Friday, August 3, 2018
* Proposals accepted: Friday, August 10, 2018
* First draft due: Friday, September 7, 2018
* Second draft due: Friday, October 5, 2018
* Publication date: Monday, November 5, 2018

===Forty-first issue===

Coordinating Editor: Ron Peterson
*Call for proposals: Monday, April 17, 2017
*Second call for proposals: Monday, April 30, 2017 (if necessary)
*Proposals due: Friday, May 11, 2017
*Proposals accepted: Friday, May 18, 2017
*First draft due: Friday, June 8, 2017
*Second draft due: Friday, July 6, 2017
*Publication date: Monday, August 6, 2018

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

2022-06-02T13:34:48Z

Jtidal: added issue 55 information

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

===Fifty-fifth issue===
Coordinating Editor: Junior Tidal

* Call for proposals: Monday, June 6, 2022
* Second call for proposals: Monday, June 27, 2022 (if necessary)
* Proposals due: Friday, July 8, 2022
* Proposals accepted: Friday, July 15, 2022
* First draft due: Friday, August 12, 2022
* Second draft due: Friday, September 9, 2022
* Publication date: Monday, October 10, 2022

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

* Call for proposals: Monday, April 18, 2022
* 2nd call for proposals: Monday, May 9, 2022 (if necessary)
* Proposals due: Friday, May 20, 2022
* Proposals accepted: Friday, May 27, 2022
* First draft due: Friday, June 24, 2022
* Second draft due: Friday, July 22, 2022
* Publication date: Monday, August 22, 2022

===Fifty-third issue===
Coordinating Editor: Ron Peterson
* Call for proposals: Monday, December 20, 2021
* Second call for proposals: Monday, January 10, 2022 (if necessary)
* Proposals due: Friday, January 21, 2022
* Proposals accepted: Friday, January 28, 2022
* First draft due: Friday, February 25, 2022
* Second draft due: Friday, March 25, 2022
* Publication date: Monday, April 25, 2022

===Fifty-second issue===
Coordinating Editor: Mark Swenson
* Call for proposals: Monday, May 10, 2021
* Second call for proposals: Tuesday, June 1, 2021 (if necessary)
* Proposals due: Friday, June 11, 2021
* Proposals accepted: Friday, June 18, 2021
* First draft due: Friday, July 16, 2021
* Second draft due: Friday, August 13, 2021
* Publication date: Monday, September 13, 2021

===Fifty-first issue===
Coordinating Editor: Edward Corrado

Note date changes from originally published schedule

* Call for proposals: Thursday, February 4, 2021
* Second call for proposals: Thursday, February 25, 2021 (if necessary)
* Proposals due: Monday, March 15, 2021
* Proposals accepted: Monday, March 22, 2021
* First draft due: Monday, April 19, 2021
* Second draft due: Monday, May 10, 2021
* Publication date: Thursday, June 10, 2021

===Fiftieth issue===

Coordinating Editor: Eric Hanson

''Note: Issue dates adjusted to skip one quarter's publication.''
* Call for proposals: Monday, October 5, 2020 <del>July 6, 2020</del>
* Second call for proposals: Monday, October 26, 2020 <del>July 27, 2020</del> (if necessary)
* Proposals due: Friday, November 6, 2020 <del>August 7, 2020</del>
* Proposals accepted: Friday, November 13, 2020 <del>August 14, 2020</del>
* First draft due: Friday, December 11, 2020 <del>September 11, 2020</del>
* Second draft due: Friday, January 8, 2021 <del>October 9, 2020</del>
* Publication date: Monday, February 8, 2021 <del>November 9, 2020</del>

===Forty-ninth issue===

Coordinating Editor: Peter Murray

* Call for proposals: Monday, March 30, 2020
* Second call for proposals: Monday, April 20, 2020 (if necessary)
* Proposals due: Friday, May 1, 2020
* Proposals accepted: Friday, May 8, 2020
* First draft due: Friday, June 5, 2020
* Second draft due: Friday, July 3, 2020
* Publication date: Monday, August 3, 2020

===Forty-eighth issue===

Coordinating Editor: Brighid M. Gonzales

* Call for proposals: Monday, January 6, 2020
* Second call for proposals: Monday, January 27, 2020 (if necessary)
* Proposals due: Friday, February 7, 2020
* Proposals accepted: Friday, February 14, 2020
* First draft due: Friday, March 13, 2020
* Second draft due: Friday, April 10, 2020
* Publication date: Monday, May 11, 2020

===Forty-seventh issue===

Coordinating Editor: Péter Király

* Call for proposals: Monday, September 30, 2019
* Second call for proposals: Monday, October 21, 2019 (if necessary)
* Proposals due: Friday, November 1, 2019
* Proposals accepted: Friday, November 15, 2019
* First draft due: Friday, December 13, 2019
* Second draft due: Friday, January 10, 2020
* Publication date: Monday, February 10, 2020

===Forty-sixth issue===

Coordinating Editor: Sara Amato
* Call for proposals: Monday, July 1, 2019
* Second call for proposals: Monday, July 22, 2019 (if necessary)
* Proposals due: Friday, August 2, 2019
* Proposals accepted: Friday, August 9, 2019
* First draft due: Friday, September 6, 2019
* Second draft due: Friday, October 4, 2019
* Publication date: Monday, November 4, 2019

===Forty-fifth issue===

Coordinating Editor: Eric Hanson
* Call for proposals: Monday, April 1, 2019
* Second call for proposals: Monday, April 22, 2019 (if necessary)
* Proposals due: Friday, May 3, 2019
* Proposals accepted: Friday, May 10, 2019
* First draft due: Friday, June 7, 2019
* Second draft due: Friday, July 5, 2019
* Publication date: Monday, August 5, 2019

===Forty-fourth issue===

Coordinating Editor: Junior Tidal
* Call for proposals: Monday, December 31, 2018
* Second call for proposals: Monday, January 21, 2019 (if necessary)
* Proposals due: Friday, February 1, 2019
* Proposals accepted: Friday, February 8, 2019
* First draft due: Friday, March 8, 2019
* Second draft due: Friday, April 5, 2019
* Publication date: Monday, May 6, 2019

===Forty-third issue===

Coordinating Editor: Peter Murray
* Call for proposals: Monday, October 1, 2018
* Second call for proposals: Monday, October 22, 2018 (if necessary)
* Proposals due: Friday, November 2, 2018
* Proposals accepted: Friday, November 9, 2018
* First draft due: Friday, December 7, 2018
* Second draft due: Friday, January 11, 2019
* Publication date: Monday, February 11, 2019

===Forty-second issue===

Coordinating Editor: Andrew Darby
* Call for proposals: Monday, July 2, 2018
* Second call for proposals: Monday, July 23, 2018 (if necessary)
* Proposals due: Friday, August 3, 2018
* Proposals accepted: Friday, August 10, 2018
* First draft due: Friday, September 7, 2018
* Second draft due: Friday, October 5, 2018
* Publication date: Monday, November 5, 2018

===Forty-first issue===

Coordinating Editor: Ron Peterson
*Call for proposals: Monday, April 17, 2017
*Second call for proposals: Monday, April 30, 2017 (if necessary)
*Proposals due: Friday, May 11, 2017
*Proposals accepted: Friday, May 18, 2017
*First draft due: Friday, June 8, 2017
*Second draft due: Friday, July 6, 2017
*Publication date: Monday, August 6, 2018

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

2018-11-27T18:32:13Z

Jtidal: Added deadlines for issue 44

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

===Forty-fourth issue===

Coordinating Editor: Junior Tidal
* Call for proposals: Monday, December 31, 2018
* Second call for proposals: Monday, January 21, 2019 (if necessary)
* Proposals due: Friday, February 1, 2019
* Proposals accepted: Friday, February 8, 2019
* First draft due: Friday, March 8, 2019
* Second draft due: Friday, April 5, 2019
* Publication date: Monday, May 6, 2019

===Forty-third issue===

Coordinating Editor: Peter Murray
* Call for proposals: Monday, October 1, 2018
* Second call for proposals: Monday, October 22, 2018 (if necessary)
* Proposals due: Friday, November 2, 2018
* Proposals accepted: Friday, November 9, 2018
* First draft due: Friday, December 7, 2018
* Second draft due: Friday, January 11, 2019
* Publication date: Monday, February 11, 2019

===Forty-second issue===

Coordinating Editor: Andrew Darby
* Call for proposals: Monday, July 2, 2018
* Second call for proposals: Monday, July 23, 2018 (if necessary)
* Proposals due: Friday, August 3, 2018
* Proposals accepted: Friday, August 10, 2018
* First draft due: Friday, September 7, 2018
* Second draft due: Friday, October 5, 2018
* Publication date: Monday, November 5, 2018

===Forty-first issue===

Coordinating Editor: Ron Peterson
*Call for proposals: Monday, April 17, 2017
*Second call for proposals: Monday, April 30, 2017 (if necessary)
*Proposals due: Friday, May 11, 2017
*Proposals accepted: Friday, May 18, 2017
*First draft due: Friday, June 8, 2017
*Second draft due: Friday, July 6, 2017
*Publication date: Monday, August 6, 2018

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

2016 Conference Committees

2015-09-02T11:49:43Z

Jtidal: /* Scholarship Committee */

= Code4Lib 2016 Committees =

''Many hands make for light work.''

Hosting a conference is incredibly complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2016 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. 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 (LPC) to each committee.

== Location and Dates ==

* Location: Old City District of Philadelphia, PA
* Dates: March 7-10, 2016
** Pre-conferences -
** Main meeting -
** Post conference activities?

== Local Planning Committee ==
This committee is charged with running the show such as overall timeline, budgeting, coordinating of locations and logistics, wrangler of committees, and communicating with the community.

* David Lacy (Villanova) - Primary Contact (v)
* Chad Nelson - Secondary Contact (v)
* Anna Headley (Chemical Heritage Foundation) - Documentarian (v)
* [[User:Sdellis|Shaun Ellis]] (Princeton) (v)
* Katherine Lynch (Temple) (v)
* Stephen Ng (Temple)
* Brett Bonfield (Collingswood Public)
* Lauren Gala (UPenn)
* David Uspal (Villanova) (v)
* Chris Clement (Drexel)

== Website Working Group ==
This group will focus on content strategy (in collaboration with the Documentation Committee) and feature implementations to improve the overall user experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users).

[[Website Working Group Documents|Website Working Group Documents]]

* [[User:Cdmo|Charlie Morris]] (Penn State) - Primary Contact
* [[User:jtidal|Junior Tidal]] (New York City College of Technology) - Secondary Contact
* [[User:BillMcMillin|Bill McMillin]] (Pratt Institute) - Documentarian
* [[User:Sdellis|Shaun Ellis]] (Princeton) - LPC Contact (v)
* [[User:Phette23|Eric Phetteplace]] (Cal College of the Arts)
* [[User:Sarahshealy| Sarah Shealy]] (Greenville (SC) County Public Library)
* [[User:JennC| Jennifer Colt]] (Cornell University Library)
* [[User:LaurenAjamie| Lauren Ajamie]] (University of Notre Dame Library)
* [[User:MichaelSchofield| Michael Schofield]] ( @schoeyfield )
* [[User:LukeAeschleman| Luke Aeschleman]] (UNC - Chapel Hill | Health Sciences Library)
* [[User:Wickr|Ryan Wick]]
* [[User:cbeer|Chris Beer]]

== Sponsorship Committee ==
This group will focus on making sure all who want to support the conference have the opportunity to do so. Sponsorship Committee work involves working with the LPC to close budget gaps and talking to potential sponsors to find the level that is right for them.

The Sponsorship committee meets every Monday at 3pm EST (12pm PST) via [https://plus.google.com/hangouts/_/gwibrfqhzxe23uto4me3tktbnia Google hangout].

* [[User:Sdellis|Shaun Ellis]] (Princeton) (v)
* David Uspal (Villanova) - LPC Contact (v)
* Chad Nelson
* Morgan McKeehan
* Ray Schwartz
* Sharon Whitfield (Rowan University)
* Brett Bonfield (Collingswood Public) (v)
* Katherine Lynch (Temple University)

== Keynote Committee ==
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.

* Brett Bonfield (Collingswood Public)
* John Mignault (ESDN/METRO)
* Emily Morton-Owens
* [[User:Phette23|Eric Phetteplace]]
* Whitni Watkins (St. Lawrence University)
* Beatrice Pulliam (Providence Public)

== 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.
* Anna Headley - Chemical Heritage Foundation (Local Contact)
* [[User:ChristinaHarlow|Christina Harlow]]

== 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.
* David Lacy - Villanova (Local Contact)

== Scholarship 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.
* Chad Nelson (Local Contact)
* [[User:jtidal|Junior Tidal]] (New York City College of Technology)

== Childcare Committee ==
This group assess the need for childcare at the conference, organizes childcare options, determines cost, and liaises with parents and chilcare providers
* Chad Nelson (Local Contact)

== Additional Committees... Coming Soon! ==
* Book Give-Away
* Onsite Volunteer
* Social Activities
* Streaming Video
* T-Shirt
* Voting
* Whatever
* Wifi/Electrical
* IRC
* Reception?
* Accessibility

2016 Conference Committees

2015-04-16T17:56:48Z

Jtidal: Added self to website working group

User:Jtidal

2015-04-16T17:18:36Z

Jtidal: added linebreaks

Junior Tidal 

Assistant Professor 

Web Services & Multimedia Librarian 

New York City College of Technology, CUNY 

[http://mailto:jtidal@citytech.cuny.edu jtidal@citytech.cuny.edu]

[http://twitter.com/JuniorTidal @JuniorTidal]

User:Jtidal

2015-04-16T17:17:16Z

Jtidal: added line breaks

Junior Tidal

Assistant Professor

Web Services & Multimedia Librarian

New York City College of Technology, CUNY

Brooklyn, NY

11222

[http://mailto:jtidal@citytech.cuny.edu jtidal@citytech.cuny.edu]

[http://twitter.com/JuniorTidal @JuniorTidal]

User:Jtidal

2015-04-16T17:16:54Z

Jtidal: Added contact info

Junior Tidal
Assistant Professor
Web Services & Multimedia Librarian
New York City College of Technology, CUNY
Brooklyn, NY
11222

[http://mailto:jtidal@citytech.cuny.edu jtidal@citytech.cuny.edu]
[http://twitter.com/JuniorTidal @JuniorTidal]

2014 AVGeeks Signup

2014-03-10T19:40:06Z

Jtidal:

[http://www.avgeeks.com/wp2/ A/V Geeks] maintains a collection of over 23,000 old 16mm educational films from various decades of the 20th century, including such classics as [http://www.avgeeks.com/wp2/library-story-the-1952/ The Library Story (1952)], many obtained from school and government auctions. Media archaeologist [http://www.indyweek.com/indyweek/skip-elsheimer/Content?oid=1183990 Skip Elsheimer] holds themed showings of selected films at events around the Triangle and in other states.

This event, [http://kingsbarcade.com/2014/03/26/av-geeks-present-when-computers-where-young/ When Computers Were Young], will include "Actual 16mm school films that introduce us to the wonderful world of computers and their potential future -- all before Google!" Films will include Disney's Ethics in the Computer Age and more. This showing is an all ages, public event that is part of a series of monthly shows held at [http://kingsbarcade.com/ Kings Barcade], but the event has been scheduled and themed with the Code4Lib crowd in mind.

'''When:''' Doors open at 7:30 PM.

'''Where:''' Located two blocks from the Sheraton, Kings is a 250-capacity live music venue with a full bar and several local beers on tap. Kings is directly connected with the [http://neptunesparlour.com/ Neptunes Parlour], a cocktail lounge with classic arcade games, pinball, and nightly DJ's. The new [http://garlandraleigh.com/ Garland] Indian restaurant, operated by the same owners, is also downstairs.

'''Cost:''' The event is free with a suggested $5 donation.

'''Please add your name to the list below if you would like to attend so that we can inform the organizers about the level of interest:'''

* Steve Morris
*Laurie Lee Moses - this looks really fun!
* Heather Rayl - old education films AND Indian food??! What more could a girl want?
* Anna Headley
* Ian Walls
* Kevin Clarke
* Paula Gray-Overtoom
* Julia Bauder
* Junior Tidal
[[Category:Code4Lib2014]]

2014 Social Activities

2014-03-04T17:10:04Z

Jtidal: /* Newcomer Dinner, Monday 3/24 */

The Social Activities Group is working on several events and social opportunities for after conference hours. We will be adding more events as they come along. Watch this page!

Also, if you find a cool event to go to, and want to share the wealth with others, feel free to add the event to the page. :)

== Planned Events ==

=== Newcomer Dinner, Monday 3/24 ===

First time at code4lib? Join fellow c4l newbies and veterans for an evening of food, socializing, and stimulating <strike>discussions about</strike> demonstrations of the many uses of <strike>bacon</strike> <strike>dongles</strike> <strike>XML</strike> EZProxy alternatives.

Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!

'''Plans'''
* When: Monday 3/24
* Time: 6 PM (ish) or whenever you can get your group together
* Mastermind (if you have any questions): [mailto:yoosebec@grinnell.edu Becky Yoose]

''Guidelines:''
*Max of '''6''' per group
**Please, no waitlisting
**Some restaurants can hold multiple groups of six. It is up to you to investigate the venue to see if this is possible.
*ID yourselves so we can get a good mix of new people and veterans in each group
**New folks - n
**c4l vets - v
*One leader needed for each location (declare yourself! - '''Vets are highly encouraged to lead the group''')
**Leader duties
***Make reservations if required; otherwise make sure that the restaurant can handle a group of 6 rowdy library tech type folks
***Herd folks from hotel to restaurant (know where you're going!)
*See a restaurant that's not listed? Feel free to add one, '''but please make sure that it is open that Monday evening.'''

'''Restaurants'''

'''Under .5 mile from hotel'''

[http://bukuraleigh.com/buku/ bu ku] (Global street food)
# Bohyun Kim - v (leader)
# Junior Tidal - n

[http://www.oxfordraleigh.com/ The Oxford] (Gastropub)

[http://www.sonoraleigh.com/index.php Sono] (Japanese)

[http://www.lavoltarestaurant.com/ La Volta] (Italian)

[http://ac-restaurants.com/pooles/ Poole's] (Local food)
# Jean Rainwater - v (leader)

[http://calaveraraleigh.com/ Calavera Empanada & Tequila Bar] (Empanada)

[http://bigeasync.com/ The Big Easy] (New Orleans/Creole)

[http://postatuscangrille.com/ Posta Tuscan Grille] (Italian)

# Julia Bauder - v

[http://www.mecca-restaurant.com/ The Mecca] (Diner/Southern)

[http://busybeeraleigh.com/ Busy Bee Cafe] (American)

[http://ac-restaurants.com/beasleys/ Beasley's Chicken + Honey] (Southern)
# Rosalyn Metz - v (leader)
# Chad Nelson - v (insubordinator)
# Andrew Pasterfield

[http://ac-restaurants.com/chucks/ Chuck's] (Burgers)

[http://ororaleigh.com/ Oro] (Tapas vegan options)

[http://www.jimmyvsraleigh.com/ Jimmy V's Osteria and Bar] (Italian)

[http://bidamanda.com/ Bida Manda] (Laotian)
# Dre - v (leader)

[http://www.tnnirishpub.com/ Tir Na Nog] (Pub)

[http://sitti-raleigh.com/index1.php Sitte] (Lebanese)
# Becky Yoose - v (benevolent dictator/leader)

[http://www.thepit-raleigh.com/ The Pit Authentic Barbecue] (BBQ)
# Joshua Gomez - v (leader) (I have reservations for 6 people at 6pm. Send me your contact info: gomezjn_AT_usc_DOT_edu)
# Cary Gordon - v

[http://www.gravyraleigh.com/ Gravy] (Italian)

[http://theboroughraleigh.com/ The Borough] (Pub)

[http://www.theremedydiner.com/ The Remedy Diner] (Diner (lots of Veg*n options))

[http://www.centroraleigh.com/ Centro] (Mexican)

[http://www.beerknurd.com/stores/raleigh/ Flying Saucer] (Pub)

[http://brewmastersbarandgrill.com/ Brewmasters Bar and Grill] (Brewpub)

'''5 to 1 mile from hotel'''

[http://www.518west.com/ 518 West Italian Cafe] (Italian)

[http://boylanbridge.com/ Boylan Bridge Brewpub] (Brewpub)

[http://www.mantraindiancuisinebar.com/ Mantra] (Indian)

[http://mtfujinc.com/SushiO/ Sushi O] (Asian)

[http://zakyrestaurant.com/ Zaky Restaurant] (Mediterranean)

[http://sullivanssteakhouse.com/raleigh/ Sullivan's Steakhouse] (Steak)

[http://bia-restaurant.com/ Bia ] (New American)

[http://www.18seaboard.com/index.html 18 Seaboard] (Contemporary American)

[http://sushibluescafe.com Sushi Blues Cafe] (Japanese)

[http://www.therockfordrestaurant.com/About.aspx Rockford] (American)

[http://www.tylerstaproom.com/ Tyler's Restaurant and Taproom] (Pub)

[http://bluemangoraleigh.com/ Blue Mango] (Indian)

[http://mellowmushroom.com/store/raleigh Mellow Mushroom] (Pizza)

[http://tascabrava.com/index2.html Tasca Brava] (Spanish)

[http://clockworkraleigh.com/index.html Clockwork] (Pub)

[http://dostaquitosnc.com/ Dos Taquitos] (Mexican)

[http://nappertandysraleighnc.com/ Napper Tandy's Irish Pub] (Pub)

[http://www.thaiphoonbistro.com/ Thaiphoon bistro] (Thai)

'''More than 1 mile from hotel'''

[http://www.peacechinanc.com/ Peace China] (Chinese)

[http://www.ddandnb.com/ Davids Dumpling and Noodle Bar] (Asian)

[http://www.abyssiniarestaurant.net/5.html Abyssinia Ethiopian Restaurant] (Ethiopian)

=== James B. Hunt Library Reception and Tour, Tuesday 3/25 ===

A reception and tour of the James B. Hunt Library on NCSU's Centennial Campus will take place on Tuesday, March 26, 5:00-7:30 PM. See the library, which opened in January 2013, through the eyes of the students in the over 3,000 Instagram photos in the [http://d.lib.ncsu.edu/myhuntlibrary My #HuntLibrary] project. The furniture alone has generated interest, as shown on the [http://chairsofhuntlibrary.tumblr.com/ Chairs of Hunt Library] Tumbler site.

'''Travel to Hunt'''

Buses will begin loading at the Sheraton at 5:00 PM after the day's sessions have concluded. The Hunt Library is 4 miles from the Sheraton.

'''Reception'''

Pizza and light snacks will be made available in the Multipurpose Room, along with soft drinks and beer from the [http://www.ncsu.edu/foodscience/Sheppard/NCSU-12004%20Brewery%20Brochure1.pdf NC State Brewery].

'''Tour'''

Attendees will be welcome to embark on a self-guided tour of the library. Library staff will be on hand at selected locations, including hi-tech spaces such as the [http://www.lib.ncsu.edu/huntlibrary/bookBot bookBot] robotic book delivery system, the [http://www.lib.ncsu.edu/spaces/teaching-and-visualization-lab Teaching & Visualization Lab], the [http://www.lib.ncsu.edu/spaces/creativity-studio Creativity Studio], the [http://www.lib.ncsu.edu/spaces/game-lab Game Lab], and the [http://www.lib.ncsu.edu/spaces/makerspace Makerspace].

'''Travel back to the Sheraton'''

Buses will begin to load for the return trip at 6:45 PM. The last bus will leave the Hunt Library at approximately 7:45 PM.

=== #libtechwomen meetup, Tuesday 3/25 ===

An informal meetup for women and their friends in library technology for networking and fun. Come join us! Learn more about #libtechwomen at [http://libtechwomen.org/about.html].

Where: TBA

Time: Evening after the tour :c)

=== A/V Geeks Present: When Computers Were Young, Wednesday 3/26 ===

[http://www.avgeeks.com/wp2/ A/V Geeks] maintains a collection of over 23,000 old 16mm educational films from various decades of the 20th century, including such classics as [http://www.avgeeks.com/wp2/library-story-the-1952/ The Library Story (1952)], many obtained from school and government auctions. Media archaeologist [http://www.indyweek.com/indyweek/skip-elsheimer/Content?oid=1183990 Skip Elsheimer] holds themed showings of selected films at events around the Triangle and in other states.

This event, [http://kingsbarcade.com/2014/03/26/av-geeks-present-when-computers-where-young/ When Computers Were Young], will include "Actual 16mm school films that introduce us to the wonderful world of computers and their potential future -- all before Google!" Films will include Disney's Ethics in the Computer Age and more. This showing is an all ages, public event that is part of a series of monthly shows held at [http://kingsbarcade.com/ Kings Barcade], but the event has been scheduled and themed with the Code4Lib crowd in mind.

'''When:''' Doors open at 7:30 PM.

'''Where:''' Located two blocks from the Sheraton, Kings is a 250-capacity live music venue with a full bar and several local beers on tap. Kings is directly connected with the [http://neptunesparlour.com/ Neptunes Parlour], a cocktail lounge with classic arcade games, pinball, and nightly DJ's. The new [http://garlandraleigh.com/ Garland] Indian restaurant, operated by the same owners, is also downstairs.

'''Cost:''' The event is free with a suggested $5 donation.

'''Signup:''' Please add your name to the [http://wiki.code4lib.org/index.php/2014_AVGeeks_Signup sign up list] if you would like to attend so that we can inform the organizers about the level of interest

== Social Map - Places of Interest==

[https://maps.google.com/maps/ms?msid=211601269129937460559.0004d8d5902e5e3d04b05&msa=0&ll=35.782519,-78.640223&spn=0.01464,0.01929 Code4Lib 2014 Amenities Map, Downtown Raleigh, NC] - Amenities that are within walking distance of the Sheraton or the R Line circulator

== Local Events ==

[http://www.godowntownraleigh.com/explore/arts Map of downtown arts and cultural entertainment]

[http://www.godowntownraleigh.com/event-calendar/2014/3 Calendar of downtown events]

[http://www.godowntownraleigh.com/explore/shopping Map of downtown shopping]

=== Exhibits, Showings, Museums ===

*[http://naturalsciences.org/ North Carolina Museum of Natural Sciences]
**[http://naturalsciences.org/nature-research-center Nature Research Center]
**Exhibit - [http://naturalsciences.org/exhibits/special-exhibits Birds of Paradise: Amazing Avian Evolution] (final day March 23)

*[http://www.ncdcr.gov/ncmoh/Home.aspx North Carolina Museum of History] Exhibits:
**[http://www.godowntownraleigh.com/event/exhibit-opening-cedars-in-the-pines Cedars in the Pines]
**[http://www.ncdcr.gov/ncmoh/SeeOurExhibits/CurrentExhibits/NorthCarolinaandtheCivilWar/The_Bitter_End.aspx North Carolina and the Civil War: The Bitter End, 1864-1865]
**[http://www.ncdcr.gov/ncmoh/SeeourExhibits/CurrentExhibits/Watergate.aspx Watergate: Political Scandal & the Presidency]

*[http://www.nchistoricsites.org/capitol/ North Carolina State Capitol]

*[http://camraleigh.org/2014nc-arts-council-artist-fellowship/ NC Arts Council Artist Fellowship Award Exhibition] at the [http://camraleigh.org/ Contemporary Arts Museum]

*[http://ncartmuseum.org/calendar/ NC Museum of Art Calendar]

*[http://artspacenc.org/about-us/visit/ ArtSpace]

*[http://www.raleighcitymuseum.org/index.shtml City of Raleigh Museum]

*[http://calendar.activedatax.com/ncstate/EventList.aspx?fromdate=3/1/2014&todate=3/31/2014&display=Month&type=public&eventidn=9669&view=EventDetails&information_id=27372 Remnants of the Floating World: Japanese Art from the Permanent Collection] at the [http://www.ncsu.edu/gregg/index.html NCSU Gregg Museum of Art & Design]

*[http://www.joellane.org/ Joel Lane Museum House]

*[http://www.raleighnc.gov/parks/content/PRecRecreation/Articles/MordecaiHistoricPark2.html Mordecai Historic Park]

=== Outside Activities ===

* [http://www.triangleglides.com/ Triangle Glides] Segway tours, standup paddleboard rentals

* [http://www.raleighnc.gov/parks/content/PRecDesignDevelop/Articles/CapitalAreaGreenwayTrailSystem.html Capital Area Greenway Trail System]

* [http://www.ncartmuseum.org/museum_park/visit_park/ NC Museum of Art: Museum Park] Scenic trails and outdoor art

* [http://www.nps.gov/nr/travel/raleigh/index.htm National Register of Historic Places]

* [http://www.ncsu.edu/jcraulstonarboretum/index.php JC Raulston Arboretum]

=== Run Clubs ===

'''Monday Night'''
* [http://www.nogrunclub.com/ Nog Run Club] - 6:00 PM at Tir Na Nog Irish Pub: 3-5 mile routes, followed by team trivia, $1 pasta, and beer specials

'''Tuesday Night'''
* [https://www.facebook.com/events/553725497983418/ Natty Greene's Run Club] - 6:00 PM at Natty Greene's Brewery: 1, 3, 5 mile routes
* Big Boss Run Club - 7:00 PM at [http://bigbossbrewing.com/age-verification.aspx?returnTo=%2f Big Boss Brewery]: 3-6 mile routes followed by beer specials

'''Wednesday Night'''
* Margarita Run Club - 6:00 PM at [http://www.centroraleigh.com/ Centro] restaurant: 3-5 mile routes followed by taco bar and margarita specials
* [http://www.ymcatriangle.org/programs-services/fitness-wellness/walking-running-clubs/alexander-family-ymca-0 Trophy Brewery Runs] - 6:00 PM at Trophy Brewing: 1, 3, 5 mile routes

== Local Food ==

[http://www.godowntownraleigh.com/explore/dining Map of Downtown Restaurants & Dining]

=== Restaurants ===

[http://www.newsobserver.com/2014/01/30/3577164/2014-best-restaurants-in-the-triangle.html News & Observer 2014 Best Restaurants of the Triangle]

[http://www.indyweek.com/indyweek/LocationSearch?locationSection=1218750 Indy Weekly Triangle Dining Guide]

'''Fayetteville St. District''' (0-0.4 miles north)

* [http://clydecoopersbbq.com/ Clyde Cooper's BBQ]
* [http://garlandraleigh.com/ Garland] Indian
* [http://ac-restaurants.com/beasleys/ Beasley's Chicken & Honey] Fried Chicken, Chicken and Waffles (''Ashley Christiansen'')
* [http://www.sonoraleigh.com/ Sono] Sushi
* [http://www.capitalclub16.com/Capital_Club_16/Home.html Capital Club 16] Eclectic pub grub
* [http://sitti-raleigh.com/ Sitti] Lebanese
* [http://ororaleigh.com/ Oro] Tapas (vegan options)
* [http://www.centroraleigh.com/ Centro] Mexican
* [http://www.centroraleigh.com/ Chuck's Burgers] (''Ashley Christiansen'')
* [http://www.oakcitymeatball.com/ Oak City Meatball Shoppe]
* [http://www.gravyraleigh.com/ Gravy] Italian-American
* [http://www.gravyraleigh.com/ Buku] Global street food
* [http://www.boltbistro.com/ Bolt] Bistro, Steakhouse, Seafood

'''Moore Square''' (0.3-0.5 miles east)

* [http://bidamanda.com/ Bida Manda] Laotian
* [http://www.theremedydiner.com/ Remedy Diner] Veg*n and non-veg*n
* [http://www.cafeluna.com/ Cafe Luna] Italian (Tuscan)
* [http://calaveraraleigh.com/ Calavera] Empanadas and tequila
* [http://www.bigedscitymarket.com/ Big Ed's] Diner
* [http://www.mosdiner.net/ Mo's Diner] American (New)

'''Warehouse District''' (0.2-0.7 miles west)

* [http://www.thepit-raleigh.com/ The Pit] Whole-hog, pit-coooked BBQ
* [http://thefictionkitchen.com/ Fiction Kitchen] Veg*n
* [http://ac-restaurants.com/pooles/ Poole's Diner] American/Diner (''Ashley Christiansen'')
* [http://joseandsons.com/ Jose and Sons] Mexican/Southern fusion
* [http://humblepierestaurant.com/ Humble Pie] Tapas (Live jazz on Wed.)
* [http://www.heatseekershrimp.com/ Five Star] Asian (Traditional and creative)
* [http://roastgrill.com/ Roast Grill] Just hot dogs (''as seen on Man v. Food'')

'''Glenwood South''' (0.6-1.3 miles northwest)

* [http://www.42ndstoysterbar.com/ 42nd St. Oyster Bar] Seafood
* [http://therockfordrestaurant.com/ Rockford] American (New)/Pub grub
* [http://www.518west.com/ 518 West] Italian
* [http://www.second-empire.com/ Second Empire] American (New)

'''Seaboard Station/Person St.''' (1.0-1.2 miles north)

* [http://www.18seaboard.com/ Seaboard Station] Southern, American (New)
* [http://jbetskis.com/ J. Betskis] Central & Eastern European
* [https://www.facebook.com/pages/Stanbury/359649790802483 Stanbury] Contemporary
* [http://piebirdraleigh.com/ Piebird] Sweet and savory pies
* [http://stationraleigh.com/ The Station] American (Traditional)

'''West towards NC State''' (1.2-2.2 miles west)

* [http://www.irregardless.com/ Irregardless Cafe] veg*n options
* [http://www.abyssiniarestaurant.net/5.html Abysinnia] Ethiopian
* [http://www.ddandnb.com/ Davids Dumpling & Noodle Bar] Asian

'''Five Points''' (2.5 miles north)

* [http://bloomsburybistro.com/bistro.restaurant.raleigh/ Bloomsbury Bistro] American (New)
* [https://nofo.com/ NOFO @ The Pig] American (New), Brunch
* [http://lillyspizza.com/ Lilly's Pizza] Pizza and beer

'''Other Inside-the-Beltline Raleigh'''

* [http://guasaca.com/ Guasaca] Venezuelan (6 miles)
* [http://glenwoodgrill.com/ Glenwood Grill] American (Traditional), Southern (4 miles)

=== Desserts ===

* [https://viderichocolatefactory.com/ Videri Chocolate Factory]
* [http://www.escazuchocolates.com/ Escazu Artisan Chocolates]
* [https://plus.google.com/113675251912407366356/about?gl=us&hl=en Crema] Ice cream

=== Coffee ===

* [http://morningtimes-raleigh.com/ Morning Times] (wifi) -- 3 blocks
* [http://ac-restaurants.com/joule/ Joule Coffee] (''Ashley Christiansen'', wifi, breakfast/lunch -- CNN eatocracy [http://eatocracy.cnn.com/2014/02/21/5-hottest-new-coffee-spots-in-the-u-s/ 5 hottest new coffee spots in the US]) -- 3 blocks
* [http://beneluxcoffee.com/ Benelux Coffee] (wifi) -- 4 blocks
* [http://www.sostacafe.com/ Sosta Cafe] (wifi, lunch) -- 2 blocks
* [http://www.cafemuertos.com/ Cafe de los Muertos] (wifi) -- 5 blocks
* [http://www.cafehelios.com/ Cafe Helios] (wifi, breakfast/lunch) -- 1.1 miles

There is a Starbucks in the lobby of the Marriott, next to the Sheraton.

== Local Drinks ==

[http://www.godowntownraleigh.com/explore/nightlife Map of Bars, Clubs & Live Entertainment]

=== Bars ===

'''Fayetteville St. District'''

* [http://www.raleightimesbar.com/ Raleigh Times] Draft Magazine Top 100 beer bar
* [http://www.busybeeraleigh.com/ Busy Bee] Draft Magazine Top 100 beer bar (The Hive is upstairs)
* [http://foundationnc.com/ Foundation] Cocktails, bourbon, local beer
* [http://neptunesparlour.com/ Neptunes Parlour] Cocktails, local beer
* [http://ac-restaurants.com/fox/ Fox Liquor Bar] Cocktails, local beer (''Ashley Christiansen'')
* [http://www.slimsraleigh.com/ Slim's] Dive bar (live music)

'''Moore Square'''

* [http://www.yelp.com/biz/landmark-tavern-raleigh Landmark Tavern] beer, back patio
* [http://www.tnnirishpub.com/ Tir Na Nog] Irish pub
* [http://calaveraraleigh.com/ Calavera] Empanadas and 40 tequila varieties
* [http://woodyscitymarket.com/ Woody's] Beer and wings

'''Warehouse District'''

* [http://brewmastersbarandgrill.com/ Brewmasters] Grill, 2012 Draft Magazine Top 100 beer bar
* [http://www.crankarmbrewing.com/ Crank Arm Brewing] Brewpub
* [http://www.beerknurd.com/stores/raleigh/ Flying Saucer] Beer
* [http://boylanbridge.com/ Boylan Bridge Brewpub] Brewpub

'''Glenwood South'''

* [http://www.cgracebar.com/ C Grace] Cocktails and live jazz
* [http://clockworkraleigh.com/ Clockwork] Retro cocktail lounge

'''Seaboard Station/Person St.'''

* [http://www.tylerstaproom.com/ Tyler's Tap Room] Beer

=== Breweries ===

[http://www.ncbeer.org/brewery-map/ Map of NC Breweries]

'''Walking Distance'''

* [http://www.crankarmbrewing.com/ Crank Arm Brewing] (0.3 miles)
* [http://boylanbridge.com/ Boylan Bridge Brewpub] (0.9 miles)
* [http://trophybrewing.com/ Trophy Brewing & Pizza Company] (1.2 miles)

[http://goo.gl/maps/haOiD Theoretical brewpub walking tour] [NOTE: Trophy has great pizza but limited seating. To finish with dinner consider going the opposite direction and eating in the Warehouse District or downtown]

'''Greater Raleigh'''

* [http://bigbossbrewing.com/‎ Big Boss Brewing] (3.5 miles, Raleigh)
* [http://raleighbrewingcompany.com/ Raleigh Brewing Company] (4 miles, Raleigh)
* [http://www.lynnwoodgrill.com/node/10 Lynnwood Brewing Concern] (9 miles, Raleigh)
* [http://www.loneriderbeer.com/ Lone Rider] (13 miles, Raleigh)
* [http://gizmobrewworks.com/ Gizmo Brewworks] (12 miles, Raleigh)
* [http://www.aviatorbrew.com/ Aviator Brewing Company] (17 miles, Fuquay Varina)
* [http://hosannabrewing.com/ Hosanna Brewery] (14 miles, Fuquay Varina)
* [http://deepriverbrewing.com/ Deep River Brewing] (16 miles, Clayton)
* [http://www.carolinabrew.com/ Carolina Brewing] (19 miles, Holly Springs)
* [http://www.bombshellbeer.com/ Bombshell Beer] (18 miles, Holly Springs)
* [http://www.whitestreetbrewing.com/ White Street Brewing] (18 miles, Wake Forest)

'''Greater Triangle'''

* [http://trianglebrewery.com/ Triangle Brewing] (Durham)
* [http://www.fullsteam.ag/beer/ Fullsteam] (Durham)
* [http://bullcityburgerandbrewery.com/Bull_City_Burger_and_Brewery/Home.html Bull City Burger & Brewing] (Durham)
* [http://thetopofthehill.com/ Top of the Hill] (Chapel Hill)
* [http://steelstringbrewery.com/ Steel String Craft Brewery] (Carrboro)
* [http://www.mysterybrewing.com/ Mystery Brewing] (Hillsborough)
* [http://whiterabbitbrewery.com/ White Rabbit Brewing] (Angiers)
* [http://doublebarleybrewing.com/ Double Barley Brewing] (Wilson Mills)

Other nanobrews: [http://subnoir.net/ Sub Noir Brewing] (Raleigh), [http://starpointbrewing.com/ StarPoint Brewing] (Carrboro), [https://www.facebook.com/sourwoodbrewingco Sourwood Brewing Company - Cider] (Durham)

=== Bottle Shops ===

* [http://tastybeverageco.com/ Tasty Beverage Company] About 1200 packaged beers and 6 draft beers (0.3 mile)
* [http://paddyobeers.com/ Paddy O'Beers] Bottle shop and tasting room (0.4 mile)
* [https://plus.google.com/116185965486400371099/about?gl=us&hl=en The Bottle Shop at Tyler's Taproom] (1.0 mile)
* [http://www.wineauthorities.com/ Wine Authorities] (1.3 miles)

==Raleigh Events March 23-27==

[https://www.mergerecords.com/25k Merge Records 25k] (March 22) Chapel Hill to Durham run, with post race party and bands at Motorco music hall (celebrating 25th year of Merge Records label)

===Sunday March 23===

* Apparently there's going to be [http://www.thepncarena.com/events/detail/2014-ncaa-division-i-mens-basketball-tournament some basketball game] at PNC Arena...
** If anyone else is crazy enough to pay the money for tickets email rosalynmetz [at] the gmail
* Another basketball game - [http://www.visitraleigh.com/includes/calendar-of-events/Cary-Invasion-vs-East-Carolina-Stealth/26414/ Cary Invasion vs. East Carolina Stealth], 6 pm
* [http://www.visitraleigh.com/includes/calendar-of-events/Civil-Rights-Through-Song/25383/ Civil Rights Through Song], Burning Coal Theater Company, at Murphrey School Auditorium, 2 pm
* Romeo and Juliet - Carolina Ballet at [http://www.dukeenergycenterraleigh.com/event/carolina-ballet-private-event-3340 Fletcher Opera Theater]
* [http://calendar.activedatax.com/ncstate/EventList.aspx?fromdate=3/1/2014&todate=3/31/2014&display=Month&type=public&eventidn=9568&view=EventDetails&information_id=27101 LEO (the anti-gravity show)], NCSU Center Stage, 3 pm
* [http://triangleyarncrawl.com/ Triangle Yarn Crawl]
* [http://nuvyug.net/ India Fest] at Dorton Arena
* [http://www.godowntownraleigh.com/event/at-the-movies-frost-and-nixon At the Movies: Frost/Nixon] at NC Museum of History (free movie and lecture)

===Monday March 24===

===Tuesday, March 25===
* [http://www.visitraleigh.com/includes/calendar-of-events/NHL-Carolina-Hurricanes-vs-New-York-Islanders/24787/ NHL Carolina Hurricanes vs. New York Islanders], 7pm (for free bus see [http://www.godowntownraleigh.com/get-around/pepsi-caniac-coach Pepsi Caniac Coach])

===Wednesday, March 26===

===Thursday, March 27===

* [http://www.ncsu.edu/dance/events/PDP_SPR2014.html Panoramic Dance Project] at NCSU's Titmus Theater
* [http://www.dukeenergycenterraleigh.com/event/north-carolina-artists-exhibition-3994 2014 Artists Exhibition - Raleigh Fine Arts Society] at Betty Ray McCain Art Gallery
* [http://www.ncdcr.gov/ncmoh/Home.aspx Watergate: Politics, Scandal, and the Media] Panel discussion at the NC Museum of History (reservation required)

== Music ==

'''Sunday March 23'''

* [http://www.thepourhousemusichall.com/event/447527-matt-schofield-raleigh/ Matt Schofield] at Pour House
* Action Bronson at [http://www.catscradle.com/events/ Cat's Cradle] (in Carrboro)

'''Monday March 24'''

* [http://www.dpacnc.com/events/detail/csn Crosby, Stills & Nash] at Durham Performing Arts Center (in Durham)
* [http://southlandballroom.com/events/asleep-wheel/ Asleep at the Wheel] at Southland Ballroom
* [http://kingsbarcade.com/2014/03/24/moullinex-live-with-marbeya-sound/ Moulinex with Marbeya Sound] at Kings Barcade
* Devils Wears Prada with Ghost Inside, others at [http://www.lincolntheatre.com/schedule.htm Lincoln Theater]
* [http://www.thepourhousemusichall.com/event/497289-daley-raleigh/ Daley] at Pour House

'''Tuesday March 25'''

* Three 6 Mafia at [http://www.lincolntheatre.com/schedule.htm Lincoln Theater]
* [http://kingsbarcade.com/2014/03/25/kings-presents-axxaabraxas-captured-tracks-at-slims/ Axxa/Abraxas] at Slim's
* [http://www.thepourhousemusichall.com/event/497341-coast-2-coast-live-raleigh/ Coast 2 Coast Live Interactive Showcase] at Pour House
* Open Mic Night at [http://www.deepsouththebar.com/ Deep South]

'''Wednesday March 26'''

* [http://www.thepourhousemusichall.com/event/479771-pigeons-playing-ping-pong-raleigh/ Pigeons Playing Ping Pong] and Imperial Blend at [http://www.thepourhousemusichall.com/ Pour House]
* Mang (Ween tribute) at [http://www.slimsraleigh.com/ Slim's]
* Free Jazz Night at [http://humblepierestaurant.com/ Humble Pie]
* Open Mic Night at [http://www.deepsouththebar.com/ Deep South]

'''Thursday March 27'''

* Local Beer/Local Band night at [http://www.tnnirishpub.com/ Tir Na Nog]
* [http://www.thepourhousemusichall.com/event/497347-blue-sky-black-death-raleigh/ Blue Sky Black Death] at Pour House
* [http://www.deepsouththebar.com/event/492779-unifier-jessica-long-new-raleigh/ Unifier, Jessica Long & The New Kind] at Deep South
* [http://kingsbarcade.com/2014/03/27/good-graeff/ Good Graeff] at Kings Barcade
* Triathalon with Giant Giants at [http://www.slimsraleigh.com/ Slim's]
* Sarah Colonna (Comedy) at [https://center-stage.seatengine.com/venues/goodnights Goodnight's Comedy]

'''More Music Venues in the Greater Triangle'''

* Chapel Hill/Carrboro: [http://www.catscradle.com/ Cat's Cradle], [http://www.local506.com/calendar/ Local 506], [http://caverntavern.com/ The Cave], [http://www.chapelhillunderground.com/ Underground], [https://www.carolinaperformingarts.org/ Memorial Hall]
* Durham: [http://motorcomusic.com/ Motorco], [http://www.thepinhook.com/ Pinhook]
* Saxapahaw: [http://www.hawriverballroom.com/ Haw River Ballroom]
[[Category:Code4Lib2014]]

2014 preconference proposals

2014-01-17T19:22:07Z

Jtidal: /* Fail4Lib 2014 */

= PROPOSALS ARE CLOSED : PLEASE DO NOT ADD NEW PRECONFERENCES TO THIS PAGE =

Proposals were accepted through December 6th, 2013.

It would be really, super duper helpful if folks who think they might want to attend a pre-conference could indicate interest by adding your name to a session below.

===Note===
Attendance at a pre-conference will require a small fee ''due at the time of conference registration".

Although this was specified in the email announcements relating to pre-conferences, it was not added to this page until December 2nd. I (Adam C.) apologize for the omission and I hope this will not cause any "sticker shock." Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.

Please put your pre-conference on the list in the following format:

=Code4Lib 2014 Pre-Conference Proposals=

===Drupal4lib Sub-con Barcamp===
=====Full Day=====

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com

This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.

This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).

[[resources to help you learn drupal]]

====Interested in Attending:====

=====All Day=====

* Renna Tuten

=====Morning=====

* Kevin Reiss
* Charlie Morris (NCSU) - glad to see this again this year!
* Paula Gray-Overtoom
* Laurie Lee Moses

=====Afternoon=====

 

----

===Open Refine Hackfest===
'''"Half-Day"'''
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com

[http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control

The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
<ol>
<li>Adam Constabaris
<li>Ray Schwartz
<li>Jason Stirnaman
<li>Joshua Gomez
<li>Sam Kome
<li>Mike Beccaria
<li>Angela Zoss
<li>A. Soroka
<li> Matt Zumwalt
</ol>
----

===Responsive Design Hackfest===
'''"Half-Day [Afternoon]"'''
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com
* Contact David Ward, University of Illinois, dh-ward@illinois.edu

This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php].

Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.

''Interested in Attending''

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

=== Intro to Blacklight ===
'''"Half-Day [Morning]"'''
* Contact: Chris Beer, Stanford University, cabeer@stanford.edu
* TA: Bess Sadler, Stanford University, bess@stanford.edu

This session will be walk-through of the architecture of Blacklight, the community, and an introduction to building a Blacklight-based application. Each participant will have the opportunity to build a simple Blacklight application, and make basic customizations, while using a test-driven approach.

For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ). We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.

''Interested in Attending''

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

# Megan Kudzia
# Bret Davidson
# Coral Sheldon-Hess
# Cory Lown
# Emily Daly
# Angela Zoss
# Sean Aery
# Francis Kayiwa
# Heidi Frank
# Junior Tidal
----

===Blacklight Hackfest===
'''"Half-Day [Afternoon]"'''
* Contact Chris Beer, Stanford University, cabeer@stanford.edu

This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.

For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ).

''Interested in Attending''

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

# Shaun Ellis
# Kevin Reiss
# Megan Kudzia
# Erik Hatcher
# Emily Daly
# Laurie Lee Moses
# Francis Kayiwa

----

===RailsBridge: Intro to programming in Ruby on Rails===
'''"Half-Day" [morning]'''
* Contact Justin Coyne, Data Curation Experts, justin@curationexperts.com

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! 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 Blacklight and Hydra.

''Interested in Attending''

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

1. Ayla Stein

2. Heidi Dowding

3. Caitlin Christian-Lamb

4. Scott Bacon

5. [[User:RileyChilds | Riley Childs]]

6. Carolina Garcia

----

===Managing Projects: Or I'm in charge, now what? (aka PM4Lib)===
'''Full-Day'''

Contact:
* [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com
* [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu

This will be a full day session on project management. We'll cover
* '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment
* '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets
* '''Executing the Project''' -- status meeting, status reports, issue management
* '''Finishing the Project''' -- achieving the goal, post mortems, project v. product
This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good) and adapted to c4lib types.

''Interested in Attending''

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

# Robin Dean
# Erin White
# Andrew Darby
# Sam Kome
# Ryan Scherle
# Will Shaw
# Liz Milewicz
# Cynthia "Arty" Ng
# Laurie Lee Moses (if I don't do the Hackfest for Blacklight)
# Ranti Junus
# Bohyun Kim (Afternoon)

----

===Fail4Lib 2014===
'''Half Day [TBD, probably afternoon]'''

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

The task of design (and the work that we do as library coders) is intimately tied to failure. Failures, both big and small, motivate us to create and improve. Failures are also occasionally the result of our work. Understanding and embracing failure, encouraging enlightened risk-taking, and seeking out opportunities to fail and learn are essential to success in our field. 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 feared.

The schedule may include the following:

* Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?
* Confessionals, for those willing to share. Talk about your own experiences with rough starts, labor pains, and doomed projects in your own work: What can we learn from our own (and each others') failures?
* Group therapy. Let's talk about how to deal with risk management, failed projects, experimental endeavors, and more: How can we make ourselves, our colleagues, and our organizations more fault tolerant? How do we make sure we fail as productively as possible?

''Interested in attending''

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

#Bret Davidson
#Mike Graves
#Ray Schwartz
#Jason Stirnaman
#Julia Bauder
#Linda Ballinger
#Scott Hanrath
#Caitlin Christian-Lamb
#Ian Walls
#Scott Bacon
#mx matienzo
#Chris Sharp
#Junior Tidal
----

===CLLAM @ code4lib===
'''(Computational Linguistics for Libraries, Archives and Museums)'''

'''Full Day'''

Contacts:
* Douglas W. Oard (primary), oard (at) umd.edu
* Corey Harper, corey (dot) harper (at) nyu.edu
* Robert Sanderson, azaroth42 (at) gmail.com
* Robert Warren, rwarren (at) math.carleton.ca

We will hack at the intersection of diverse content from Libraries, Archives and Museums and bleeding edge tools from computational linguistics for slicing and dicing that content. Did you just acquire the email archives of a startup company? Maybe you can automatically build an org chart. Have you got metadata in a slew of languages? Perhaps you can search it all using one query. Is name authority control for e-resources getting too costly? Let’s see if entity linking techniques can help. These are just a few teasers.

There’ll be plenty of content and tools supplied, but please bring your own [data] too -- you’ll hack with it in new ways throughout the day. We’ll get started with some lightning talks on what we’ve brought,then we’ll break up into groups to experiment and work on the ideas that appeal. Three guaranteed outcomes: you’ll walk away with new ideas, new tools, and new people you’ll have met.

''Interested in attending''

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

# Devon Smith
# Kevin S. Clarke
# Jason Stirnaman
# Joshua Gomez
# Carolina Garcia
# Tom Burton-West
# Dan Scott
# Devin Higgins
----

=== GeoHydra: Managing geospatial content ===

'''Half-day [Afternoon]'''

* Contact: Darren Hardy, Stanford University, drh@stanford.edu
* Moderator: Bess Sadler, Stanford University, bess@stanford.edu

Do you have digitized maps, GIS datasets like Shapefiles, aerial photography,
etc., all of which you want to integrate into your digital repository? In this
workshop, we will discuss how Hydra can provide discovery, delivery, and
management services for geospatial assets, as well as solicit questions about
your own GIS projects. We aim to help answer the following questions you might have about putting geospatial data into your Hydra-based digital library:

* What are the types of geospatial data?
* How to dive into Hydra?
* How to model geospatial holdings with Hydra?
* How to discover and view geospatial data?
* How to build a geospatial data infrastructure?
* What are common approaches and problems?

''Interested in Attending''

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

# Esmé Cowles
----

===Technology, Librarianship, and Gender: Moving the conversation forward===
'''Full Day'''

Contact: Lisa Rabey lisa @ biblyotheke dot net | [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]

'''Description'''

Librarianship is largely made up of women, yet women are significantly underrepresented in tech positions, on any level, within libraries themselves. Why? What are we doing to encourage women to become more involved in STEM within librarianship? What kind of message are we sending when library technology keynotes remain almost resolutely male? How are we changing the face of technology, not only within libraries, but with the field itself? How are we training our staff and colleagues in the areas of fairness and removal of bias? Our vendors?

Lots of tough questions.

While the conversation has been going on via various blogs and articles within the last few years, it was given a public face at [http://infotoday.com/il2013/day.asp?day=Monday#session_D105 Internet Librarian 2013] where a panel of 7 (four women, three men) gave personal experiences on the above and then opened up the conversation to the audience. As eye opening and enriching the conversation was, a 45 minute panel was not enough. One thing remains clear: We need to keep the conversation moving forward and start making some radical changes in the way we think, act, and how we need to harness this to start making real changes within librarianship itself.

Topics to include: Fairness, bias, impostor syndrome, code of conducts, sexual harassment, training opportunities, support systems, mentoring, ally support, and more

Those attending should expect: Begin with opening up the conversation of experiences and talking about what is most needed, spending remaining time putting together live, usable solutions to start implementing as well as pushing the conversation forward at local levels

''Interested in Attending''

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

=====All Day=====
1. Kate Kosturski

2. Valerie Aurora

3. Declan Fleming (I'd be good with a half day too)

4. mx matienzo (likewise ok w/ half day)

=====Morning=====
1. Shaun Ellis

2. Jason Casden

3. Bohyun Kim

=====Afternoon=====
1. Ayla Stein

2. Heidi Dowding

3. Coral Sheldon-Hess

4. Cory Lown
----

===FileAnalyzer: Rapid Development of File Manipulation Tasks===
'''"Half-Day" [morning]'''
* Contact Terry Brady, twb27@georgetown.edu

The FileAnalyzer (http://georgetown-university-libraries.github.io/File-Analyzer/) is an application designed to solve a number of library automation challenges:

* validating digitized and reformatted files
* validating vendor statistics for counter compliance
* preparing collections of digital files for archiving and ingest
* manipulating ILS import and export files

The File Analyzer application was used by the US National Archives to validate 3.5 million digitized images from the 1940 Census. After implementing a customized ingest workflow within the File Analyzer, the Georgetown University Libraries was able to process an ingest backlog of over a thousand files of digital resources into DigitalGeorgetown, the Libraries’ Digital Collections and Institutional Repository platform. Georgetown is currently developing customized workflows that integrate Apache Tika, BagIt, and Marc conversion utilities.

The File Analyzer is a desktop application with a powerful framework for implementing customized file validation and transformation rules. As new rules are deployed, they are presented to users within a user interface that is easy (and powerful) to use.

The first half of this session will be targeted to potential users and developers. The second half of the session will be targeted towards developers who are interested in developing custom rules for the application.

''Session Overview''
* Overview of the application
* Running sample file tests/transformations through the application
* Compiling and building the application
* Coding a custom file processing task

''Interested in Attending''

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

#Ray Schwartz
# Michael Doran
----

===Collecting social media data with Social Feed Manager===
'''Half-Day [Morning]'''

Contacts:
* Dan Chudnov, GW Libraries, dchud (at) gwu.edu
* Dan Kerchner, GW Libraries, kerchner (at) gwu.edu
* Laura Wrubel, GW Libraries, lwrubel (at) gwu.edu

Social media data is a popular material for research and a new format for building collections. What does it take to collect meaningfully from Twitter, Tumblr, YouTube, Weibo, Facebook, and other sites? We will:
* Introduce options for collections, including both high- and low-end commercial offerings. Discuss what it means to collect these resources, covering boundaries, policies, and workflows required to develop a social media collection program in your institution.
* Explore the Twitter API in depth, with hands-on opportunities for those w/laptops and others who want to team up w/them
* Help you get started using the free [http://gwu-libraries.github.io/social-feed-manager Social Feed Manager] (SFM) app we're developing at GW to create your first collections. We’ll demo its use and demo a clean install (those w/environments can follow along)

''Interested in Attending''

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

# Declan Fleming
# Esmé Cowles
# Jason Stirnaman
# Ray Schwartz
# Liz Milewicz
# Ranti Junus

----

=== Intro to Git ===
'''"Half-Day [tbd - probably afternoon]"'''
* Contact: Erin Fahy, Stanford University, efahy at stanford.edu
* TA: Michael Klein, Northwestern University, michael.klein at northwestern.edu

This session will cover the fundamentals of git by discussing/going through (time allowing):
* what is a distributed version control system
* what is git and github
* initializing a repo on a remote server/github
* cloning an existing repo
* creating a branch
* contributing code to a repo
* how to handle merge conflicts

''Interested in Attending''

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

# Ray Schwartz
# Sam Kome
# Paula Gray-Overtoom
# Liz Milewicz
# Michael Doran
# Caitlin Christian-Lamb
# [[User:RileyChilds|Riley Childs]]
----

=== Archival discovery and use ===
'''Full Day'''

Contacts:
* Tim Shearer, UNC Chapel Hill, tshearer at email.unc.edu,
* Will Sexton, Duke, will.sexton at duke.edu

This is a full day pre-conference about archival collections and will cover the intersections of archives, workflows, technologies, discovery, and use.

Morning agenda: focused talks around (but not limited to) issues such as:
* Crowd-sourcing description to enhance collecitons
* Linked data and authority
* Mass digitization and sustainable workflows
* Digitized objects in context (images and other objects in finding aids)
* Too many cooks in the kitchen: versioning
* Global-, intra-, and inter- discovery of archival materials via finding aids
* and more...

Afternoon agenda: Focused talks around specific tools followed by general discussion, connections, opportunities, aspirations, and planning.

Tool examples:
* Archivespace
* STEADy
* "RAMP" (Remixing Archival Metadata Project)
* OpenRefine
* Aeon

''Interested in Attending''

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

Morning:
* Julia Bauder

Afternoon:
* your name

All day:

# Josh Wilson
# Sam Kome
# Linda Ballinger
# Caitlin Christian-Lamb
# Laurie Lee Moses (seriously hard to decide here!)
# David Bass
# John Rees
----

===AV Content Slam===
'''Half-Day [morning]'''
Contacts:
* Kara Van Malssen, kara (at) avpreserve.com
* Lauren Sorenson, laurens (at) bavc.org
* Steven Villereal , villereal (at) gmail.com
A morning BarCamp/unconference for practitioners and coders who work with audiovisual content. The agenda will be attendee-driven, with a focus on sharing, synthesizing, and improving workflow strategies and documentation for software-based approaches to wrangling and providing access to audio and video content.
Possible topics of discussion might include:
* Use of format id and characterization/metadata extraction tools for AV
* Creating and using time-based metadata
* Managing (moving, fixity checking, etc) massive files (like uncompressed video)
For a better idea of the topics and concerns that have informed some past AV-themed events, check out the event wikis for [http://wiki.curatecamp.org/index.php/CURATEcamp_AVpres_2013 CURATEcamp AVpres 2013] as well as the [http://wiki.curatecamp.org/index.php/Association_of_Moving_Image_Archivists_%26_Digital_Library_Federation_Hack_Day_2013 AMIA/DLF 2013 Hack Day] .

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

# A. Soroka

----

===OCLC Web Services Hackfest===

"Half-Day" [afternoon]

Contact: Shelley Hostetler, Community Manager, Developer Network hostetls[at]oclc.org

This half-day hackfest will explore some of the OCLC Developer Network web services. We will provide an overview of some of the common topics such as the general REST-based architecture for most services and how to use some new authentication clients. The group can then decide to take a deep dive into a particular API and/or write a client library for the community.

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

----

===Obey the Testing Goat!: Test Driven Web Development From The Ground Up===
'''Half-Day [tbd - probably afternoon]'''
* Contact [[User:Mredar|Mark Redar]], mredar[at]gmail.com

Test driven development is a proven method for producing better quality code. But I've found it hard to follow a strict TDD methodology when starting new web projects. How do you write that first test when there is no code or web pages created yet.

In this session, we will follow the excellent book [http://shop.oreilly.com/product/0636920029533.do "Test-Driven Web Development with Python"] to create a simple web site in Django following TDD from the first character typed. Come ready to code and test. No prior knowledge of python or Django required.

By the end of this session, you should be able to [http://www.obeythetestinggoat.com/ "Obey the Testing Goat"] from the start to finish for your next project.

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

# Charlie Morris (NCSU)
# Jason Stirnaman
# Joshua Gomez
# Liz Milewicz
# Scott Hanrath
# Mike Beccaria
# Sean Aery
# Carolina Garcia
# Heidi Frank
----

===Summon Hackfest and ProQuest Discovery & Management Technologies Users Group ===

Presenter: Eddie Newwirth and presenters from Summon libraries
Contact: Scott Schuetze (first DOT last @ serialssolutions. com)

The morning hackfest (10:30am-12pm) will be a great opportunity for libraries using the Summon service to share their creative customizations and code and exchange ideas about ways they can leverage the Summon API to better meet the needs of their users.

The ProQuest Discovery & Management Technologies User Group (1pm-4pm) will feature updates from product managers, presentations by several libraries sharing different aspects of their experiences with ProQuest discovery and management services, and an interactive session designed to let you share your stories and discuss ideas.

The Summon Hackfest and User Group are open to all libraries currently using ProQuest discovery and management services (Intota, Summon, Ulrich’s or the 360 suite of services), whether they are attending Code4Lib or are just in the area.

----

[[:Category:Code4Lib2014]]

2014 preconference proposals

2014-01-17T19:21:04Z

Jtidal: /* Intro to Blacklight */

= PROPOSALS ARE CLOSED : PLEASE DO NOT ADD NEW PRECONFERENCES TO THIS PAGE =

Proposals were accepted through December 6th, 2013.

It would be really, super duper helpful if folks who think they might want to attend a pre-conference could indicate interest by adding your name to a session below.

===Note===
Attendance at a pre-conference will require a small fee ''due at the time of conference registration".

Although this was specified in the email announcements relating to pre-conferences, it was not added to this page until December 2nd. I (Adam C.) apologize for the omission and I hope this will not cause any "sticker shock." Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.

Please put your pre-conference on the list in the following format:

=Code4Lib 2014 Pre-Conference Proposals=

===Drupal4lib Sub-con Barcamp===
=====Full Day=====

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com

This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.

This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).

[[resources to help you learn drupal]]

====Interested in Attending:====

=====All Day=====

* Renna Tuten

=====Morning=====

* Kevin Reiss
* Charlie Morris (NCSU) - glad to see this again this year!
* Paula Gray-Overtoom
* Laurie Lee Moses

=====Afternoon=====

 

----

===Open Refine Hackfest===
'''"Half-Day"'''
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com

[http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control

The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
<ol>
<li>Adam Constabaris
<li>Ray Schwartz
<li>Jason Stirnaman
<li>Joshua Gomez
<li>Sam Kome
<li>Mike Beccaria
<li>Angela Zoss
<li>A. Soroka
<li> Matt Zumwalt
</ol>
----

===Responsive Design Hackfest===
'''"Half-Day [Afternoon]"'''
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com
* Contact David Ward, University of Illinois, dh-ward@illinois.edu

This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php].

Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.

''Interested in Attending''

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

=== Intro to Blacklight ===
'''"Half-Day [Morning]"'''
* Contact: Chris Beer, Stanford University, cabeer@stanford.edu
* TA: Bess Sadler, Stanford University, bess@stanford.edu

This session will be walk-through of the architecture of Blacklight, the community, and an introduction to building a Blacklight-based application. Each participant will have the opportunity to build a simple Blacklight application, and make basic customizations, while using a test-driven approach.

For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ). We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.

''Interested in Attending''

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

# Megan Kudzia
# Bret Davidson
# Coral Sheldon-Hess
# Cory Lown
# Emily Daly
# Angela Zoss
# Sean Aery
# Francis Kayiwa
# Heidi Frank
# Junior Tidal
----

===Blacklight Hackfest===
'''"Half-Day [Afternoon]"'''
* Contact Chris Beer, Stanford University, cabeer@stanford.edu

This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.

For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ).

''Interested in Attending''

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

# Shaun Ellis
# Kevin Reiss
# Megan Kudzia
# Erik Hatcher
# Emily Daly
# Laurie Lee Moses
# Francis Kayiwa

----

===RailsBridge: Intro to programming in Ruby on Rails===
'''"Half-Day" [morning]'''
* Contact Justin Coyne, Data Curation Experts, justin@curationexperts.com

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! 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 Blacklight and Hydra.

''Interested in Attending''

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

1. Ayla Stein

2. Heidi Dowding

3. Caitlin Christian-Lamb

4. Scott Bacon

5. [[User:RileyChilds | Riley Childs]]

6. Carolina Garcia

----

===Managing Projects: Or I'm in charge, now what? (aka PM4Lib)===
'''Full-Day'''

Contact:
* [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com
* [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu

This will be a full day session on project management. We'll cover
* '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment
* '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets
* '''Executing the Project''' -- status meeting, status reports, issue management
* '''Finishing the Project''' -- achieving the goal, post mortems, project v. product
This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good) and adapted to c4lib types.

''Interested in Attending''

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

# Robin Dean
# Erin White
# Andrew Darby
# Sam Kome
# Ryan Scherle
# Will Shaw
# Liz Milewicz
# Cynthia "Arty" Ng
# Laurie Lee Moses (if I don't do the Hackfest for Blacklight)
# Ranti Junus
# Bohyun Kim (Afternoon)

----

===Fail4Lib 2014===
'''Half Day [TBD, probably afternoon]'''

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

The task of design (and the work that we do as library coders) is intimately tied to failure. Failures, both big and small, motivate us to create and improve. Failures are also occasionally the result of our work. Understanding and embracing failure, encouraging enlightened risk-taking, and seeking out opportunities to fail and learn are essential to success in our field. 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 feared.

The schedule may include the following:

* Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?
* Confessionals, for those willing to share. Talk about your own experiences with rough starts, labor pains, and doomed projects in your own work: What can we learn from our own (and each others') failures?
* Group therapy. Let's talk about how to deal with risk management, failed projects, experimental endeavors, and more: How can we make ourselves, our colleagues, and our organizations more fault tolerant? How do we make sure we fail as productively as possible?

''Interested in attending''

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

#Bret Davidson
#Mike Graves
#Ray Schwartz
#Jason Stirnaman
#Julia Bauder
#Linda Ballinger
#Scott Hanrath
#Caitlin Christian-Lamb
#Ian Walls
#Scott Bacon
#mx matienzo
#Chris Sharp

----

===CLLAM @ code4lib===
'''(Computational Linguistics for Libraries, Archives and Museums)'''

'''Full Day'''

Contacts:
* Douglas W. Oard (primary), oard (at) umd.edu
* Corey Harper, corey (dot) harper (at) nyu.edu
* Robert Sanderson, azaroth42 (at) gmail.com
* Robert Warren, rwarren (at) math.carleton.ca

We will hack at the intersection of diverse content from Libraries, Archives and Museums and bleeding edge tools from computational linguistics for slicing and dicing that content. Did you just acquire the email archives of a startup company? Maybe you can automatically build an org chart. Have you got metadata in a slew of languages? Perhaps you can search it all using one query. Is name authority control for e-resources getting too costly? Let’s see if entity linking techniques can help. These are just a few teasers.

There’ll be plenty of content and tools supplied, but please bring your own [data] too -- you’ll hack with it in new ways throughout the day. We’ll get started with some lightning talks on what we’ve brought,then we’ll break up into groups to experiment and work on the ideas that appeal. Three guaranteed outcomes: you’ll walk away with new ideas, new tools, and new people you’ll have met.

''Interested in attending''

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

# Devon Smith
# Kevin S. Clarke
# Jason Stirnaman
# Joshua Gomez
# Carolina Garcia
# Tom Burton-West
# Dan Scott
# Devin Higgins
----

=== GeoHydra: Managing geospatial content ===

'''Half-day [Afternoon]'''

* Contact: Darren Hardy, Stanford University, drh@stanford.edu
* Moderator: Bess Sadler, Stanford University, bess@stanford.edu

Do you have digitized maps, GIS datasets like Shapefiles, aerial photography,
etc., all of which you want to integrate into your digital repository? In this
workshop, we will discuss how Hydra can provide discovery, delivery, and
management services for geospatial assets, as well as solicit questions about
your own GIS projects. We aim to help answer the following questions you might have about putting geospatial data into your Hydra-based digital library:

* What are the types of geospatial data?
* How to dive into Hydra?
* How to model geospatial holdings with Hydra?
* How to discover and view geospatial data?
* How to build a geospatial data infrastructure?
* What are common approaches and problems?

''Interested in Attending''

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

# Esmé Cowles
----

===Technology, Librarianship, and Gender: Moving the conversation forward===
'''Full Day'''

Contact: Lisa Rabey lisa @ biblyotheke dot net | [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]

'''Description'''

Librarianship is largely made up of women, yet women are significantly underrepresented in tech positions, on any level, within libraries themselves. Why? What are we doing to encourage women to become more involved in STEM within librarianship? What kind of message are we sending when library technology keynotes remain almost resolutely male? How are we changing the face of technology, not only within libraries, but with the field itself? How are we training our staff and colleagues in the areas of fairness and removal of bias? Our vendors?

Lots of tough questions.

While the conversation has been going on via various blogs and articles within the last few years, it was given a public face at [http://infotoday.com/il2013/day.asp?day=Monday#session_D105 Internet Librarian 2013] where a panel of 7 (four women, three men) gave personal experiences on the above and then opened up the conversation to the audience. As eye opening and enriching the conversation was, a 45 minute panel was not enough. One thing remains clear: We need to keep the conversation moving forward and start making some radical changes in the way we think, act, and how we need to harness this to start making real changes within librarianship itself.

Topics to include: Fairness, bias, impostor syndrome, code of conducts, sexual harassment, training opportunities, support systems, mentoring, ally support, and more

Those attending should expect: Begin with opening up the conversation of experiences and talking about what is most needed, spending remaining time putting together live, usable solutions to start implementing as well as pushing the conversation forward at local levels

''Interested in Attending''

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

=====All Day=====
1. Kate Kosturski

2. Valerie Aurora

3. Declan Fleming (I'd be good with a half day too)

4. mx matienzo (likewise ok w/ half day)

=====Morning=====
1. Shaun Ellis

2. Jason Casden

3. Bohyun Kim

=====Afternoon=====
1. Ayla Stein

2. Heidi Dowding

3. Coral Sheldon-Hess

4. Cory Lown
----

===FileAnalyzer: Rapid Development of File Manipulation Tasks===
'''"Half-Day" [morning]'''
* Contact Terry Brady, twb27@georgetown.edu

The FileAnalyzer (http://georgetown-university-libraries.github.io/File-Analyzer/) is an application designed to solve a number of library automation challenges:

* validating digitized and reformatted files
* validating vendor statistics for counter compliance
* preparing collections of digital files for archiving and ingest
* manipulating ILS import and export files

The File Analyzer application was used by the US National Archives to validate 3.5 million digitized images from the 1940 Census. After implementing a customized ingest workflow within the File Analyzer, the Georgetown University Libraries was able to process an ingest backlog of over a thousand files of digital resources into DigitalGeorgetown, the Libraries’ Digital Collections and Institutional Repository platform. Georgetown is currently developing customized workflows that integrate Apache Tika, BagIt, and Marc conversion utilities.

The File Analyzer is a desktop application with a powerful framework for implementing customized file validation and transformation rules. As new rules are deployed, they are presented to users within a user interface that is easy (and powerful) to use.

The first half of this session will be targeted to potential users and developers. The second half of the session will be targeted towards developers who are interested in developing custom rules for the application.

''Session Overview''
* Overview of the application
* Running sample file tests/transformations through the application
* Compiling and building the application
* Coding a custom file processing task

''Interested in Attending''

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

#Ray Schwartz
# Michael Doran
----

===Collecting social media data with Social Feed Manager===
'''Half-Day [Morning]'''

Contacts:
* Dan Chudnov, GW Libraries, dchud (at) gwu.edu
* Dan Kerchner, GW Libraries, kerchner (at) gwu.edu
* Laura Wrubel, GW Libraries, lwrubel (at) gwu.edu

Social media data is a popular material for research and a new format for building collections. What does it take to collect meaningfully from Twitter, Tumblr, YouTube, Weibo, Facebook, and other sites? We will:
* Introduce options for collections, including both high- and low-end commercial offerings. Discuss what it means to collect these resources, covering boundaries, policies, and workflows required to develop a social media collection program in your institution.
* Explore the Twitter API in depth, with hands-on opportunities for those w/laptops and others who want to team up w/them
* Help you get started using the free [http://gwu-libraries.github.io/social-feed-manager Social Feed Manager] (SFM) app we're developing at GW to create your first collections. We’ll demo its use and demo a clean install (those w/environments can follow along)

''Interested in Attending''

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

# Declan Fleming
# Esmé Cowles
# Jason Stirnaman
# Ray Schwartz
# Liz Milewicz
# Ranti Junus

----

=== Intro to Git ===
'''"Half-Day [tbd - probably afternoon]"'''
* Contact: Erin Fahy, Stanford University, efahy at stanford.edu
* TA: Michael Klein, Northwestern University, michael.klein at northwestern.edu

This session will cover the fundamentals of git by discussing/going through (time allowing):
* what is a distributed version control system
* what is git and github
* initializing a repo on a remote server/github
* cloning an existing repo
* creating a branch
* contributing code to a repo
* how to handle merge conflicts

''Interested in Attending''

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

# Ray Schwartz
# Sam Kome
# Paula Gray-Overtoom
# Liz Milewicz
# Michael Doran
# Caitlin Christian-Lamb
# [[User:RileyChilds|Riley Childs]]
----

=== Archival discovery and use ===
'''Full Day'''

Contacts:
* Tim Shearer, UNC Chapel Hill, tshearer at email.unc.edu,
* Will Sexton, Duke, will.sexton at duke.edu

This is a full day pre-conference about archival collections and will cover the intersections of archives, workflows, technologies, discovery, and use.

Morning agenda: focused talks around (but not limited to) issues such as:
* Crowd-sourcing description to enhance collecitons
* Linked data and authority
* Mass digitization and sustainable workflows
* Digitized objects in context (images and other objects in finding aids)
* Too many cooks in the kitchen: versioning
* Global-, intra-, and inter- discovery of archival materials via finding aids
* and more...

Afternoon agenda: Focused talks around specific tools followed by general discussion, connections, opportunities, aspirations, and planning.

Tool examples:
* Archivespace
* STEADy
* "RAMP" (Remixing Archival Metadata Project)
* OpenRefine
* Aeon

''Interested in Attending''

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

Morning:
* Julia Bauder

Afternoon:
* your name

All day:

# Josh Wilson
# Sam Kome
# Linda Ballinger
# Caitlin Christian-Lamb
# Laurie Lee Moses (seriously hard to decide here!)
# David Bass
# John Rees
----

===AV Content Slam===
'''Half-Day [morning]'''
Contacts:
* Kara Van Malssen, kara (at) avpreserve.com
* Lauren Sorenson, laurens (at) bavc.org
* Steven Villereal , villereal (at) gmail.com
A morning BarCamp/unconference for practitioners and coders who work with audiovisual content. The agenda will be attendee-driven, with a focus on sharing, synthesizing, and improving workflow strategies and documentation for software-based approaches to wrangling and providing access to audio and video content.
Possible topics of discussion might include:
* Use of format id and characterization/metadata extraction tools for AV
* Creating and using time-based metadata
* Managing (moving, fixity checking, etc) massive files (like uncompressed video)
For a better idea of the topics and concerns that have informed some past AV-themed events, check out the event wikis for [http://wiki.curatecamp.org/index.php/CURATEcamp_AVpres_2013 CURATEcamp AVpres 2013] as well as the [http://wiki.curatecamp.org/index.php/Association_of_Moving_Image_Archivists_%26_Digital_Library_Federation_Hack_Day_2013 AMIA/DLF 2013 Hack Day] .

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

# A. Soroka

----

===OCLC Web Services Hackfest===

"Half-Day" [afternoon]

Contact: Shelley Hostetler, Community Manager, Developer Network hostetls[at]oclc.org

This half-day hackfest will explore some of the OCLC Developer Network web services. We will provide an overview of some of the common topics such as the general REST-based architecture for most services and how to use some new authentication clients. The group can then decide to take a deep dive into a particular API and/or write a client library for the community.

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

----

===Obey the Testing Goat!: Test Driven Web Development From The Ground Up===
'''Half-Day [tbd - probably afternoon]'''
* Contact [[User:Mredar|Mark Redar]], mredar[at]gmail.com

Test driven development is a proven method for producing better quality code. But I've found it hard to follow a strict TDD methodology when starting new web projects. How do you write that first test when there is no code or web pages created yet.

In this session, we will follow the excellent book [http://shop.oreilly.com/product/0636920029533.do "Test-Driven Web Development with Python"] to create a simple web site in Django following TDD from the first character typed. Come ready to code and test. No prior knowledge of python or Django required.

By the end of this session, you should be able to [http://www.obeythetestinggoat.com/ "Obey the Testing Goat"] from the start to finish for your next project.

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

# Charlie Morris (NCSU)
# Jason Stirnaman
# Joshua Gomez
# Liz Milewicz
# Scott Hanrath
# Mike Beccaria
# Sean Aery
# Carolina Garcia
# Heidi Frank
----

===Summon Hackfest and ProQuest Discovery & Management Technologies Users Group ===

Presenter: Eddie Newwirth and presenters from Summon libraries
Contact: Scott Schuetze (first DOT last @ serialssolutions. com)

The morning hackfest (10:30am-12pm) will be a great opportunity for libraries using the Summon service to share their creative customizations and code and exchange ideas about ways they can leverage the Summon API to better meet the needs of their users.

The ProQuest Discovery & Management Technologies User Group (1pm-4pm) will feature updates from product managers, presentations by several libraries sharing different aspects of their experiences with ProQuest discovery and management services, and an interactive session designed to let you share your stories and discuss ideas.

The Summon Hackfest and User Group are open to all libraries currently using ProQuest discovery and management services (Intota, Summon, Ulrich’s or the 360 suite of services), whether they are attending Code4Lib or are just in the area.

----

[[:Category:Code4Lib2014]]

NYC

2013-10-08T18:38:06Z