Code4Lib - User contributions [en]

Code4Lib Editorial Committee Introduction

2020-11-03T19:56:22Z

Tomkeays: /* Wordpress (Required) */

[[Category: Code4Lib Journal]]

== How the Editorial Committee Functions ==

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

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

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

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

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

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

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

== Editorial Committee Discussion Lists (Required) ==

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

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

== Article Tracking Spreadsheet (Required) ==

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

== Wordpress (Required) ==

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

New editors need to request a Wordpress account:

# Go to http://journal.code4lib.org/wp/wp-login.php?action=register - if this link does not work, please contact the Technical Editor to request access.
# Register
# Send your username to c4lj-articles@googlegroups.com so the technical editor can grant you Wordpress privileges.

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

== Google Analytics (Optional) ==

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

== Other Shared Documents (Optional) ==

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

2020 Breakout Sessions

2020-02-12T14:29:15Z

Tomkeays: Set up page to record breakout sessions

'''NOTE: Breakout sessions are usually proposed at the conference or shortly before the conference begins'''

Those interested in the same project/problem can hang out in a space together for 1 hour blocks. Generally the person who suggests the topic will take on the role as moderator to begin and moderate the discussion. Anyone can propose a breakout session - please think about whether you would want a session to be held on Monday or Tuesday, depending on the order of talks and who you hope will attend. There are lots of spaces in the conference center where small groups can congregate. We will route different proposed sessions to the different rooms depending on a quick show-of-hands survey just before each one begins.

This page will list any sessions proposed, but there will also be flip charts outside the meeting room where more sessions can be proposed. '''Please include your name when proposing a session.'''

'''Monday 3:00-3:55'''

'''Tuesday 2:05-3:05'''

[[Category:Code4Lib2020]]

Code4Lib 2020 Conference Committees

2020-02-12T14:13:54Z

Tomkeays: /* Website Working Group */

= Code4Lib 2020 Conference Committees =

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 2020 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: '''[https://www.marriott.com/hotels/travel/pitwi-the-westin-pittsburgh/ The Westin Pittsburgh]''' Downtown, Pittsburgh, PA
* Dates: March 08 (pre-con) - 22, 2020
** Pre-conferences: March 08, 2020
** Main meeting: March 09-11, 2020
** Post conference activities: Coming Soon

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

* [mailto:kr2e@andrew.cmu.edu Ken Rose], Carnegie Mellon University - Chair, Primary Contact
* [mailto:jglenn@andrew.cmu.edu Jason Glenn], Carnegie Mellon University - Tertiary Contact
* [mailto:mesco@andrew.cmu.edu Ann Marie Mesco], Carnegie Mellon University - Tertiary Contact
* [mailto:jcorrin@andrew.cmu.edu Julia Corrin], Carnegie Mellon University - Tertiary Contact
* [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Tertiary Contact
* [mailto:gesina.a.phillips@gmail.com Gesina Phillips], University of Pittsburgh - Tertiary Contact
* [mailto:sriffe@andrew.cmu.edu Shannon Riffe], Carnegie Mellon University - Tertiary Contact
* [mailto:rashid@andrew.cmu.edu Rashid Siddiqui], Carnegie Mellon University - Tertiary Contact
* [mailto:MStrauss@heinzhistorycenter.org Matthew Strauss], Heinz History Center - Tertiary Contact
* [mailto:MTighe1@Chatham.edu Molly Tighe], Chatham University - Tertiary Contact
* [mailto:tyt3@pitt.edu Tyrica Terry Kapral], University of Pittsburgh - Tertiary Contact
* [mailto:rspotts@andrew.cmu.edu Angelina R Spotts], Carnegie Mellon University - Volunteer
* [mailto:hickss1@duq.edu Sarah Hicks], Duquesne University - 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).

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

* [[User:Phette23|Eric Phetteplace]] - Primary Contact aka Chair
* [[User:KaitlinNewson|Kaitlin Newson]] (v) - Secondary Contact aka Co-Chair
* [mailto:mesco@andrew.cmu.edu Ann Marie Mesco], Carnegie Mellon University - Local Planning Contact
* Your Name Here - Documentarian
* Julia Caffrey (newbie) - Volunteer
* [[User:Ranti|Ranti Junus]] (v) - Volunteer
* [[User:KellyHiser|Kelly Hiser]] (newbie) - Volunteer
* [mailto:qum@miamioh.edu Meng Qu] (newbie) - Volunteer
* [[User:Derekz| Derek Zoladz]] (newbie) - Volunteer

== Budget Committee ==
This group will focus on making sure we are appropriately planning for budgetary issues.

[[2020 Budget and Sponsorship Documents|2020 Budget and Sponsorship Documents]]

* [mailto:swayh@oclc.org Hank Sway] - Primary Contact AKA Chair (veteran of 2018)
* [mailto:gmcharlt@gmail.com Galen Charlton] - Secondary Contact and Co-Chair (veteran of 2017 and 2018)
* [mailto:nbharti@andrew.cmu.edu Neelam Bharti] - Local Planning Contact
* [mailto:gmcharlt@gmail.com Galen Charlton] - Documentarian (veteran of 2017 and 2018)
* [mailto:bethany@clir.org Bethany Nowviskie] - ex officio, fiscal host (CLIR/DLF)

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

[[2020 Budget and Sponsorship Documents|2020 Budget and Sponsorship Documents]]

* Mary Jinglewski - Primary Contact aka Chair
* Scott Carlson - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Janna Avon - Documentarian
* [mailto:gmcharlt@gmail.com Galen Charlton] - Volunteer
* [mailto:Andrea-Schurr@utc.edu Andrea Schurr] - 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.

[[2020 Keynote Documents|2020 Keynote Documents]]

* [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Primary Contact aka Chair
* [mailto:wladimir.labeikovsky@ucdenver.edu Wladimir Labeikovsky], University of Colorado Anschutz Medical Campus - Secondary Contact aka Co-Chair (newbie)
* [mailto:hickss1@duq.edu Sarah Hicks], Duquesne University - Local Planning Contact
* [mailto:sxb891@case.edu Stephanie Becker], Case Western Reserve University - Documentarian
* [mailto:subrama@purdue.edu Annapurni Subramaniam],Purdue University - Volunteer
* [mailto:clara.turp@mcgill.ca Clara Turp], McGill University - Volunteer
* [mailto:eslayton@andrew.cmu.edu Emma Slayton], Carnegie Mellon University - Volunteer

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

[[2020 Pre-conference Documents|2020 Pre-conference Documents]]

* [mailto:jglenn@andrew.cmu.edu Jason Glenn] - Primary Contact aka Chair
* [mailto:mesco@andrew.cmu.edu Ann Marie Mesco] - Local Planning Contact
* [mailto:rspotts@andrew.cmu.edu Angelina R Spotts] - Documentarian
* [mailto:tod@uchicago.edu Tod Olson] (v) - Volunteer
* [mailto:mike.taylor@nau.edu Mike Taylor] - Volunteer
* [mailto:KHaley@mwa.org Kathleen Haley] (v) - Volunteer
* [mailto:jamen.mcgranahan@vanderbilt.edu Jamen McGranahan] (new) - 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.

[[2020 Program Documents|2020 Program Documents]]

* Your Name Here - Primary Contact aka Chair
* [mailto:gesina.a.phillips@gmail.com Gesina Phillips] University of Pittsburgh - Local Planning Contact
* [mailto:lillyho@gmail.com Lilly Ho] - Volunteer
* [mailto:akorphan@ncsu.edu Dre] - Volunteer
* [mailto:matt.r.sherman@gmail.com Matt Sherman] - Volunteer
* [mailto:bomanc@oclc.org Craig Boman] - Volunteer
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer
* [[User:RichardHiggins|Richard Higgins]], Indiana University - 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.

[[2020 Scholarship Documents|2020 Scholarship Documents]]

* Your Name Here - Primary Contact aka Co-Chair
* Your Name Here - Primary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:mlemusro@iupui.edu Mairelys Lemus-Rojas] - Volunteer
* [mailto:ylee4@uottawa.ca Yoo Young Lee] - 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.

[[2020 T-Shirt Documents|2020 T-Shirt Documents]]

* Your Name Here - Primary Contact aka Chair
* [mailto:tfluhr@iit.edu Tim Fluhr] Illinois Institute of Technology - Secondary Contact aka Co-Chair
* [mailto:rashid@andrew.edu Rashid Siddiqui] Carnegie Mellon University - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:mnarlock@nd.edu Mikala Narlock] University of Notre Dame - Volunteer

== Onsite Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

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

[[2020 Onsite Volunteer Documents|2020 Onsite Volunteer Documents]]

* [[User:NatashaAllen|Natasha Allen]] - Primary Contact aka (Co-)Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:jenn@concentra-cms.com Jennifer Cummings] & [mailto:kathy@concentra-cms.com Kathy Azevedo] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:kbehrman@andrew.cmu.edu Katie Behrman] - Volunteer
* [mailto:rloomis@sclibnj.org Rich Loomis], Somerset County Library System of New Jersey - Volunteer

== Social Activities Committee ==
This committee works closely with the local programming committee in organizing events outside of conference hours. This committee is in charge of organizing the Newcomer Dinner (traditionally held the night before the first day of the main conference) as well as ensuring that there is a variety of different events to cater to different interests (alcoholic/non-alcoholic, carnivore/vegan, mainstream/niche, and everything in between).

[https://drive.google.com/drive/folders/1NX5H8G7oRW6-xLi47tnQOoOSNy2Ps2Bu?usp=sharing Social Activities Documents (Members Only)]

Conference goers - The page you are looking for is coming soon... [[2020 Social Activities]]

* [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Co-Chair
* [[User:Yoosebj|Becky Yoose]] - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* meredith.c.broadway@vanderbilt.edu Meredith Broadway, Vanderbilt University - Documentarian
* [mailto:eslayton@andrew.cmu.edu Emma Slayton], Carnegie Mellon University - Volunteer
* [mailto:kbehrman@andrew.cmu.edu Katie Behrman], Carnegie Mellon University - 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, of course, actually running the camera during the conference.

[[2020 Streaming Video Documents|2020 Streaming Video Documents]]

* [mailto:jester@dltj.org Peter Murray] - Chair (note: what Cary doesn't have, I have.... ;-) )
* [mailto:roytennant@gmail.com Roy Tennant] - Secondary Contact aka Co-Chair
* [mailto:jenn@concentra-cms.com Jennifer Cummings] - Local Planning Contact
* Your Name Here - Documentarian
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer (note: I have most needed equipment.)
* [mailto:fu@usna.edu Li Fu], U.S. Naval Academy - Volunteer

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

[[2021 Host Voting Documents|2021 Host Voting Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* 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).

[[2020 Book Giveaway Documents|2020 Book Giveaway Documents]]

* [[User:JulieSwierczek|Julie C. Swierczek]] - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [[User:Hardyoyo|Hardy Pottinger]] - Volunteer

== IRC and Slack Committee ==
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.

[[2020 IRC and Slack Documents|2020 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

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

[[2020 Accessibility Documents|2020 Accessibility Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Documentarian
* Your Name Here - Local Planning Contact
* 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.

[[2020 Whatever Documents|2020 Whatever Documents]]

* [mailto:rebecca@califa.org Rebecca Holloway] - Primary Contact aka Chair
* [mailto:ldobin@courthouselibrary.ca Lesley Dobin] (newbie) - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:jane.thaler@pitt.edu Jane Thaler] (newbie) - Volunteer

[[Category:Code4Lib2020]]

Code4Lib 2020 Conference Committees

2019-06-24T15:14:48Z

Tomkeays: added name to committee

= Code4Lib 2020 Conference Committees =

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 2020 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: '''[https://www.marriott.com/hotels/travel/pitwi-the-westin-pittsburgh/ The Westin Pittsburgh]''' Downtown, Pittsburgh, PA
* Dates: March 08 (pre-con) - 22, 2020
** Pre-conferences: March 08, 2020
** Main meeting: March 09-11, 2020
** Post conference activities: Coming Soon

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

* [mailto:kr2e@andrew.cmu.edu Ken Rose], Carnegie Mellon University - Chair, Primary Contact
* [mailto:jglenn@andrew.cmu.edu Jason Glenn], Carnegie Mellon University - Tertiary Contact
* [mailto:mesco@andrew.cmu.edu Ann Marie Mesco], Carnegie Mellon University - Tertiary Contact
* [mailto:jcorrin@andrew.cmu.edu Julia Corrin], Carnegie Mellon University - Tertiary Contact
* [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Tertiary Contact
* [mailto:gesina.a.phillips@gmail.com Gesina Phillips], University of Pittsburgh - Tertiary Contact
* [mailto:sriffe@andrew.cmu.edu Shannon Riffe], Carnegie Mellon University - Tertiary Contact
* [mailto:rashid@andrew.cmu.edu Rashid Siddiqui], Carnegie Mellon University - Tertiary Contact
* [mailto:MStrauss@heinzhistorycenter.org Matthew Strauss], Heinz History Center - Tertiary Contact
* [mailto:MTighe1@Chatham.edu Molly Tighe], Chatham University - Tertiary Contact
* [mailto:tyt3@pitt.edu Tyrica Terry Kapral], University of Pittsburgh - Tertiary Contact
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

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

* [[User:Phette23|Eric Phetteplace]] - Primary Contact aka Chair
* Julia Caffrey (newbie) - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [[User:KaitlinNewson|Kaitlin Newson]] (veteran) - Volunteer/Program committee contact
* [[User:Ranti|Ranti Junus]] (v) - Volunteer
* [[User:Tomkeays|Tom Keays]] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Budget Committee ==
This group will focus on making sure we are appropriately planning for budgetary issues.

[[2020 Budget and Sponsorship Documents|2020 Budget and Sponsorship Documents]]

* [mailto:swayh@oclc.org Hank Sway] - Primary Contact AKA Chair (veteran of 2018)
* [mailto:gmcharlt@gmail.com Galen Charlton] - Secondary Contact and Co-Chair (veteran of 2017 and 2018)
* Your Name Here - Local Planning Contact
* [mailto:gmcharlt@gmail.com Galen Charlton] - Documentarian (veteran of 2017 and 2018)
* [mailto:bethany@clir.org Bethany Nowviskie] - ex officio, fiscal host (CLIR/DLF)
* [mailto:kerchner@gwu.edu Dan Kerchner] - Volunteer

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

[[2020 Budget and Sponsorship Documents|2020 Budget and Sponsorship Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - 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.

[[2020 Keynote Documents|2020 Keynote Documents]]

* Your Name Here - Primary Contact aka Chair
* [mailto:wladimir.labeikovsky@ucdenver.edu Wladimir Labeikovsky], University of Colorado Anschutz Medical Campus - Secondary Contact aka Co-Chair (newbie)
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:subrama@purdue.edu Annapurni Subramaniam],Purdue University - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2020 Pre-conference Documents|2020 Pre-conference Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* 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.

[[2020 Program Documents|2020 Program Documents]]

* Your Name Here - Primary Contact aka Chair
* [mailto:gesina.a.phillips@gmail.com Gesina Phillips] University of Pittsburgh - Local Planning Contact
* [mailto:lillyho@gmail.com Lilly Ho] - Volunteer
* [[User:KaitlinNewson|Kaitlin Newson]] - Volunteer/Web committee contact
* [mailto:mardenj@carnegielibrary.org Julia Marden] Carnegie Library of Pittsburgh - Documentarian? (new!)
* [mailto:matt.r.sherman@gmail.com Matt Sherman] - Volunteer
* Your Name Here - Volunteer
* [[User:highermath|Cary Gordon]], Cherry Hill Company - 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.

[[2020 Scholarship Documents|2020 Scholarship Documents]]

* Your Name Here - Primary Contact aka Co-Chair
* Your Name Here - Primary Contact aka Co-Chair
* [mailto:phette23@gmail.com Eric Phetteplace] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:mlemusro@iupui.edu Mairelys Lemus-Rojas] - Volunteer
* [mailto:ylee4@uottawa.ca Yoo Young Lee] - 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.

[[2020 T-Shirt Documents|2020 T-Shirt Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:rashid@andrew.edu Rashid Siddiqui] Carnegie Mellon University - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

== Onsite Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

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

[[2020 Onsite Volunteer Documents|2020 Onsite Volunteer Documents]]

* Your Name Here - Primary Contact aka (Co-)Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:jenn@concentra-cms.com Jennifer Cummings] & [mailto:kathy@concentra-cms.com Kathy Azevedo] - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==
This committee works closely with the local programming committee in organizing events outside of conference hours. This committee is in charge of organizing the Newcomer Dinner (traditionally held the night before the first day of the main conference) as well as ensuring that there is a variety of different events to cater to different interests (alcoholic/non-alcoholic, carnivore/vegan, mainstream/niche, and everything in between).

[https://drive.google.com/drive/folders/1NX5H8G7oRW6-xLi47tnQOoOSNy2Ps2Bu?usp=sharing Social Activities Documents (Members Only)]

Conference goers - The page you are looking for is coming soon... [[2020 Social Activities]]

* [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Co-Chair
* [[User:Yoosebj|Becky Yoose]] - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* 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, of course, actually running the camera during the conference.

[[2020 Streaming Video Documents|2020 Streaming Video Documents]]

* [mailto:jester@dltj.org Peter Murray] - Chair (note: what Cary doesn't have, I have.... ;-) )
* [mailto:roytennant@gmail.com Roy Tennant] - Secondary Contact aka Co-Chair
* [mailto:jenn@concentra-cms.com Jennifer Cummings] - Local Planning Contact
* Your Name Here - Documentarian
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer (note: I have most needed equipment.)
* [mailto:fu@usna.edu Li Fu], U.S. Naval Academy - Volunteer

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

[[2021 Host Voting Documents|2021 Host Voting Documents]]

* [[User:Phette23|Eric Phetteplace]] - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Roy Tennant - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:lillyho@gmail.com Lilly HS HO] - 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).

[[2020 Book Giveaway Documents|2020 Book Giveaway Documents]]

* [[User:JulieSwierczek|Julie C. Swierczek]] - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

== IRC and Slack Committee ==
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.

[[2020 IRC and Slack Documents|2020 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

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

[[2020 Accessibility Documents|2020 Accessibility Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Documentarian
* Your Name Here - Local Planning Contact
* 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.

[[2020 Whatever Documents|2020 Whatever Documents]]

* [mailto:rebecca@califa.org Rebecca Holloway] - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

[[Category:Code4Lib2020]]

2017 Social Activities

2017-03-09T04:04:41Z

Tomkeays:

= Code4Lib 2017 Social Activities =

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

=== UCLA Library DIIT Open House ===

Stop by the Charles E. Young Research Library to see activity by the conference host's '''Digital Initiatives and Information Technology''' department.

'''Details'''
* Monday, March 6th, 4pm-6pm
** drop in; stay as long as you like
* [https://www.library.ucla.edu/events/code4lib-open-house More information]

=== Newcomer Dinner, Monday, March 6th ===

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>XML</strike> <strike>EZProxy</strike> <strike>LibGuides alternatives</strike> <strike>spreadsheets</strike> documentation.

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

'''Plans'''
* When: Monday, March 6th
* Suggested Time: 6 PM (ish) or whenever you can get your group together
* Mastermind (if you have any questions): [mailto:becky.yoose@spl.org 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.'''

'''NB! This year's Newcomer Dinner options are not close to the convention center and hotel. You will most likely be relying on public transportation, taxis, or ride-sharing services to get to your destination. Please plan accordingly.'''

'''[http://2017.code4lib.org/venue/dinner.html Restaurant list, sign ups, and transportation information now available!]'''

=== Conference Reception, Tuesday, March 7th ===

*When: 3/7/17, 6 pm - 8 pm
*Where: [http://www.fowler.ucla.edu/ Fowler Museum, UCLA]

Enjoy several of the museum's galleries and spaces while getting a chance to meet other attendees outside of the conference room. Light hors d'oeuvres and drinks will be provided. More information about what exhibits will be open can be found on the [http://2017.code4lib.org/venue/reception.html Code4Lib website].

=== #LibTechWomen Meet-Up, Wednesday, March 8th ===

'''NOTE:''' Due to the space limitation, we can host '''only those who signed up for the event.''' Thank you for your understanding.

[Please note '''TIME/LOCATION CHANGE''' below]

* When: Wed. 3/8/17, '''6-8pm'''
* Where: Please see your '''email invitation for the location'''. You should have received it if you signed up for the meet-up.
* Questions: Contact Bohyun Kim - @bohyunkim in Twitter/Slack/IRC
* There will be drinks and light snacks provided. No dining service on-site unfortunately.
* Sign up now CLOSED.

*Afterwards some of us will go to Play and Share!

[http://libtechwomen.org/ LibTechWomen] is a supportive space for women and their friends to network, develop skills, build confidence, and lead positive change. Are you a lurker? Are you a newcomer? All are welcome! Come meet wonderful colleagues in library technology!

=== Play and Share, Wednesday, March 8th ===

*When: 3/8/17, 6:30 pm - 10:30 pm
*Where: [http://maps.ucla.edu/campus/?locid=268 Kerckhoff Hall, UCLA]

Play games? Have some homemade (or “homemade”) treats to share? Want to find folks to play music with? We organized a large open room near the conference center with plenty of space for attendees to gather and socialize, play games and share goodies. We will provide tables and chairs for Board Game Night and some space for jam sessions. You are also welcome to bring stuff to share, from craft sodas and beers to baked goods to local treats - we’ll have a few tables set up for that as well.

More venue information can be found on the [http://2017.code4lib.org/venue/reception.html Code4Lib website]. If you plan to bring something to play or share, please sign up below!

====List of Games====
* game title, who will bring it, any other info about the game

* [http://www.gamewright.com/gamewright/index.php?section=games&page=game&show=260 Gubs], Hardy Pottinger, a friendly easy-to-pick-up game, strategic-ish, not as random as Flux.
* [https://www.fantasyflightgames.com/en/products/android-netrunner-the-card-game/ NetRunner], Hardy Pottinger, I will bring the intro box set, I've never played, Eric Phetteplace has kindly agreed to teach me how to play. Wanna learn, too?
* [https://www.fantasyflightgames.com/en/products/age-of-war/ Age of War], Matt Sherman, a simple dice rolling game of capturing Japanese castles.
* [https://www.fantasyflightgames.com/en/products/arcana-revised-edition/ Arcana], Matt Sherman, a deckbuilding/bidding game of underworld guilds jockeying for power in a fantasy city.
* [https://www.fantasyflightgames.com/en/products/blood-bowl-team-manager/ Blood Bowl: Team Manager], Matt Sherman, a game of fantasy football (i.e. orc and elves) representing managers running their teams trying to get the most fans in a season.
* [https://boardgamegeek.com/boardgame/157413/new-bedford New Bedford] a game of whaling and the building of the town of New Bedford, MA.
* [http://www.explodingkittens.com/how/ Exploding Kittens], Linda Ballinger, can include Imploding Kittens expansion pack.
* [https://www.boardgamegeek.com/boardgame/152567/basari-das-kartenspiel, Basari: The Card Game], Jon Gorman, A fun quick game where you seek to wheel and deal to get majorities in gems
* [https://www.boardgamegeek.com/boardgame/1107/nyet, Nyet!], Jon Gorman, An interesting trick-taking game played over multiple rounds where each round people determine what the rules will be for the hand. (Note, this is the old 1997 version, not the pretty new one.)
* [https://www.boardgamegeek.com/boardgame/56692/parade, Parade], Jon Gorman, a nice game where you are manipulating a line of cards trying to take the least amount of points possible. (Using a rage deck)
* [https://www.boardgamegeek.com/boardgame/354/sticheln, Sticheln], Jon Gorman, Probably my favorite-trick taking game. Dirt simple: everyone chooses a pain color. Cards taken in that suit are face-value negative points, other cards are single points. (rage deck)
* [https://boardgamegeek.com/boardgame/822/carcassonne Carcassonne], Eric Cahanin, Tile-placing strategy game for 2-5 players. Reasonably quick (45m) and easy to learn.
* [http://www.nintendo.com/games/detail/1-2-switch 1-2 Switch], Steven Carl Anderson, Simple party games played on a tablet screen with detached controller. 2 players at a time but allows a mode for teams that works well for ~6 total players.
* [https://boardgamegeek.com/boardgame/178900/codenames, Codenames], Jon Gorman, team-based game where you're trying to give one clue that will relate to multiple words in a grid.
* [https://boardgamegeek.com/boardgame/161417/red7, Red7], Jon Gorman, A simple card game where you manipulate the rule of the games or the cards out to not be eliminated.
* [http://www.perplext.com/packogame/, Pack o' Game], Jon Gorman, Actually 7 very small and portable games. I've played several of them and wouldn't try playing more.
* [https://boardgamegeek.com/boardgame/98778/hanabi, Hanabi], Jon Gorman, A tricky cooperative game where you can see your teammates cards but not your own and must play them in order.
* [https://www.kickstarter.com/projects/kinderperfect/kinderperfect KinderPerfect], Ian Walls, like Cards Against Humanity, but for parents. 3+ players.
* [https://boardgamegeek.com/boardgame/815/chrononauts Chrononauts], Ian Walls, In this game, you are a Time Traveler, with a Secret Mission, a Secret Identity, and a very important job to do: Paradox Repair. 1-6 players.

====List of Goodies====
* brand, flavor, allergen alerts (if any)
* homebrew: wild ale brewed with mixed berries, imperial stout aged on cacao nibs

== Social Map - Places of Interest==
For a visual-ish view of recommended food, drink, and activities in LA, please visit this awesome [https://drive.google.com/open?id=11dBRFfMhYump8B5nCznsx-iVFVs&usp=sharing Google Map].

== Ideas ==
Please add your idea with date/time!
If you want to participate, please add your name.

* More formalized outing to [http://www.getty.edu/visit/center/plan/ The Getty Center] on Sunday and/or Thursday afternoon?
* Jog4Lib - [[User:BenWallberg|Ben Wallberg]]
* Trip to Getty
* Hammer Museum
* [http://queenmary.com/tours-exhibits/tour-packages/queen-mary-passport/ Queen Mary Tour] -Chad Kluck (Thursday afternoon, 2:15 or 4:15 tour, $27)
* [http://mjt.org/ Museum of Jurassic Technology] ~Hardy Pottinger (Date/Time unsure), Kim Pham (Twitter @tolloid, slack:kimpham)
* [http://www.astro.ucla.edu/planetarium/ UCLA Planetarium public show], (Wednesday evening, 7-8 p.m.) -Shaun Akhtar (shaun [dot] akhtar [at] gmail [dot] com)

== Local Food and Drink ==

A more visual list of food and drink places can be found on the [https://drive.google.com/open?id=11dBRFfMhYump8B5nCznsx-iVFVs&usp=sharing Google Map].

[https://www.google.com/maps/d/viewer?mid=1jHOjCIJFMhfxNJy_XGhqZk6AHow&usp=sharing Where To Eat at UCLA] — a guide to food on campus.

[https://www.zomato.com/los-angeles/restaurants/near/ucla Zomato] —The 200 or so restaurants and coffee shops in and around Westwood, sorted by distance.

== LA Events ==

=== Saturday and Sunday, March 4 & 5 ===
*Saturday only - [http://www.printmuseum.org/ International Printing Museum] (You can also make an appointment during the week to see the museum!)
*Saturday only - [http://cap.ucla.edu/calendar/details/jose_gonzalez_2017 José González & The Göteborg String Theory], Royce Hall, UCLA
*Sunday only - [http://la.smorgasburg.com/ Smorgasburg, L.A.]
*[http://www.discoverlosangeles.com/what-to-do/events/white-guy-bus-bruce-graham White Guy on The Bus], The Road on Magnolia
*[http://laphil.org/tickets/adams-70-nixon-china/2017-03-05 Nixon in China, Los Angeles Philharmonic] John Adams conducts, at Walt Disney Concert Hall

=== Monday, March 6 ===

=== Tuesday, March 7 ===
*[http://cap.ucla.edu/calendar/details/trisha_brown_17 Trisha Brown Dance Company - In Plain Site:LA], The Broad

=== Wednesday, March 8 ===
*[https://hammer.ucla.edu/programs-events/2017/03/incident-at-oglala/ Incident at Oglala], Hammer Museum
*[http://www.astro.ucla.edu/planetarium/ UCLA Planetarium public show], UCLA Mathematical Sciences Building, 7-8 p.m.

=== Thursday, March 9 ===
*[https://hammer.ucla.edu/programs-events/2017/03/the-politics-and-problematics-of-representation/ The Politics and Problematics of Representation], Hammer Museum
*[http://downtownartwalk.org/ Downtown LA Art Walk], Gallery Row

=== All days ===
*[http://www.getty.edu/art/exhibitions/breaking_news/index.html Breaking News: Turning the Lends on Mass Media], Getty Center
*[http://www.laweekly.com/event/david-bowie-among-the-mexican-masters-7852901 David Bowie: Among the Mexican Masters], Forest Lawn Memorial Park
*[https://www.centertheatregroup.org/tickets/ahmanson-theatre/2016-17/fun-home/ Fun Home], Ahmanson Theatre
*[https://www.centertheatregroup.org/tickets/mark-taper-forum/2017-18/zoot-suit/ Zoot Suit] Mark Taper Forum

==Getting Around==
All info on getting to the hotel is on the conference website: http://2017.code4lib.org/venue/

[[Category:Code4Lib2017]]

2017 Social Activities

2017-03-08T21:08:06Z

Tomkeays: /* List of Games */

= Code4Lib 2017 Social Activities =

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

=== UCLA Library DIIT Open House ===

Stop by the Charles E. Young Research Library to see activity by the conference host's '''Digital Initiatives and Information Technology''' department.

'''Details'''
* Monday, March 6th, 4pm-6pm
** drop in; stay as long as you like
* [https://www.library.ucla.edu/events/code4lib-open-house More information]

=== Newcomer Dinner, Monday, March 6th ===

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>XML</strike> <strike>EZProxy</strike> <strike>LibGuides alternatives</strike> <strike>spreadsheets</strike> documentation.

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

'''Plans'''
* When: Monday, March 6th
* Suggested Time: 6 PM (ish) or whenever you can get your group together
* Mastermind (if you have any questions): [mailto:becky.yoose@spl.org 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.'''

'''NB! This year's Newcomer Dinner options are not close to the convention center and hotel. You will most likely be relying on public transportation, taxis, or ride-sharing services to get to your destination. Please plan accordingly.'''

'''[http://2017.code4lib.org/venue/dinner.html Restaurant list, sign ups, and transportation information now available!]'''

=== Conference Reception, Tuesday, March 7th ===

*When: 3/7/17, 6 pm - 8 pm
*Where: [http://www.fowler.ucla.edu/ Fowler Museum, UCLA]

Enjoy several of the museum's galleries and spaces while getting a chance to meet other attendees outside of the conference room. Light hors d'oeuvres and drinks will be provided. More information about what exhibits will be open can be found on the [http://2017.code4lib.org/venue/reception.html Code4Lib website].

=== #LibTechWomen Meet-Up, Wednesday, March 8th ===

'''NOTE:''' Due to the space limitation, we can host '''only those who signed up for the event.''' Thank you for your understanding.

[Please note '''TIME/LOCATION CHANGE''' below]

* When: Wed. 3/8/17, '''6-8pm'''
* Where: Please see your '''email invitation for the location'''. You should have received it if you signed up for the meet-up.
* Questions: Contact Bohyun Kim - @bohyunkim in Twitter/Slack/IRC
* There will be drinks and light snacks provided. No dining service on-site unfortunately.
* Sign up now CLOSED.

*Afterwards some of us will go to Play and Share!

[http://libtechwomen.org/ LibTechWomen] is a supportive space for women and their friends to network, develop skills, build confidence, and lead positive change. Are you a lurker? Are you a newcomer? All are welcome! Come meet wonderful colleagues in library technology!

=== Play and Share, Wednesday, March 8th ===

*When: 3/8/17, 6:30 pm - 10:30 pm
*Where: [http://maps.ucla.edu/campus/?locid=268 Kerckhoff Hall, UCLA]

Play games? Have some homemade (or “homemade”) treats to share? Want to find folks to play music with? We organized a large open room near the conference center with plenty of space for attendees to gather and socialize, play games and share goodies. We will provide tables and chairs for Board Game Night and some space for jam sessions. You are also welcome to bring stuff to share, from craft sodas and beers to baked goods to local treats - we’ll have a few tables set up for that as well.

More venue information can be found on the [http://2017.code4lib.org/venue/reception.html Code4Lib website]. If you plan to bring something to play or share, please sign up below!

====List of Games====
* game title, who will bring it, any other info about the game

* [http://www.gamewright.com/gamewright/index.php?section=games&page=game&show=260 Gubs], Hardy Pottinger, a friendly easy-to-pick-up game, strategic-ish, not as random as Flux.
* [https://www.fantasyflightgames.com/en/products/android-netrunner-the-card-game/ NetRunner], Hardy Pottinger, I will bring the intro box set, I've never played, Eric Phetteplace has kindly agreed to teach me how to play. Wanna learn, too?
* [https://www.fantasyflightgames.com/en/products/age-of-war/ Age of War], Matt Sherman, a simple dice rolling game of capturing Japanese castles.
* [https://www.fantasyflightgames.com/en/products/arcana-revised-edition/ Arcana], Matt Sherman, a deckbuilding/bidding game of underworld guilds jockeying for power in a fantasy city.
* [https://www.fantasyflightgames.com/en/products/blood-bowl-team-manager/ Blood Bowl: Team Manager], Matt Sherman, a game of fantasy football (i.e. orc and elves) representing managers running their teams trying to get the most fans in a season.
* [https://boardgamegeek.com/boardgame/157413/new-bedford New Bedford] a game of whaling and the building of the town of New Bedford, MA.
* [http://www.explodingkittens.com/how/ Exploding Kittens], Linda Ballinger, can include Imploding Kittens expansion pack.
* [https://www.boardgamegeek.com/boardgame/152567/basari-das-kartenspiel, Basari: The Card Game], Jon Gorman, A fun quick game where you seek to wheel and deal to get majorities in gems
* [https://www.boardgamegeek.com/boardgame/1107/nyet, Nyet!], Jon Gorman, An interesting trick-taking game played over multiple rounds where each round people determine what the rules will be for the hand. (Note, this is the old 1997 version, not the pretty new one.)
* [https://www.boardgamegeek.com/boardgame/56692/parade, Parade], Jon Gorman, a nice game where you are manipulating a line of cards trying to take the least amount of points possible. (Using a rage deck)
* [https://www.boardgamegeek.com/boardgame/354/sticheln, Sticheln], Jon Gorman, Probably my favorite-trick taking game. Dirt simple: everyone chooses a pain color. Cards taken in that suit are face-value negative points, other cards are single points. (rage deck)
* [https://boardgamegeek.com/boardgame/822/carcassonne Carcassonne], Eric Cahanin, Tile-placing strategy game for 2-5 players. Reasonably quick (45m) and easy to learn.
* [http://www.nintendo.com/games/detail/1-2-switch 1-2 Switch], Steven Carl Anderson, Simple party games played on a tablet screen with detached controller. 2 players at a time but allows a mode for teams that works well for ~6 total players.
* [https://boardgamegeek.com/boardgame/178900/codenames, Codenames], Jon Gorman, team-based game where you're trying to give one clue that will relate to multiple words in a grid.
* [https://boardgamegeek.com/boardgame/161417/red7, Red7], Jon Gorman, A simple card game where you manipulate the rule of the games or the cards out to not be eliminated.
* [http://www.perplext.com/packogame/, Pack o' Game], Jon Gorman, Actually 7 very small and portable games. I've played several of them and wouldn't try playing more.
* [https://boardgamegeek.com/boardgame/98778/hanabi, Hanabi], Jon Gorman, A tricky cooperative game where you can see your teammates cards but not your own and must play them in order.
* [https://boardgamegeek.com/boardgame/8217/san-juan San Juan], Tom Keays, A card version of the Eurogame, Puerto Rico, with simpler rules and faster play. 2-4 players.

====List of Goodies====
* brand, flavor, allergen alerts (if any)
* homebrew: wild ale brewed with mixed berries, imperial stout aged on cacao nibs

== Social Map - Places of Interest==
For a visual-ish view of recommended food, drink, and activities in LA, please visit this awesome [https://drive.google.com/open?id=11dBRFfMhYump8B5nCznsx-iVFVs&usp=sharing Google Map].

== Ideas ==
Please add your idea with date/time!
If you want to participate, please add your name.

* More formalized outing to [http://www.getty.edu/visit/center/plan/ The Getty Center] on Sunday and/or Thursday afternoon?
* Jog4Lib - [[User:BenWallberg|Ben Wallberg]]
* Trip to Getty
* Hammer Museum
* [http://queenmary.com/tours-exhibits/tour-packages/queen-mary-passport/ Queen Mary Tour] -Chad Kluck (Thursday afternoon, 2:15 or 4:15 tour, $27)
* [http://mjt.org/ Museum of Jurassic Technology] ~Hardy Pottinger (Date/Time unsure), Kim Pham (Twitter @tolloid, slack:kimpham)
* [http://www.astro.ucla.edu/planetarium/ UCLA Planetarium public show], (Wednesday evening, 7-8 p.m.) -Shaun Akhtar (shaun [dot] akhtar [at] gmail [dot] com)

== Local Food and Drink ==

A more visual list of food and drink places can be found on the [https://drive.google.com/open?id=11dBRFfMhYump8B5nCznsx-iVFVs&usp=sharing Google Map].

[https://www.google.com/maps/d/viewer?mid=1jHOjCIJFMhfxNJy_XGhqZk6AHow&usp=sharing Where To Eat at UCLA] — a guide to food on campus.

[https://www.zomato.com/los-angeles/restaurants/near/ucla Zomato] —The 200 or so restaurants and coffee shops in and around Westwood, sorted by distance.

== LA Events ==

=== Saturday and Sunday, March 4 & 5 ===
*Saturday only - [http://www.printmuseum.org/ International Printing Museum] (You can also make an appointment during the week to see the museum!)
*Saturday only - [http://cap.ucla.edu/calendar/details/jose_gonzalez_2017 José González & The Göteborg String Theory], Royce Hall, UCLA
*Sunday only - [http://la.smorgasburg.com/ Smorgasburg, L.A.]
*[http://www.discoverlosangeles.com/what-to-do/events/white-guy-bus-bruce-graham White Guy on The Bus], The Road on Magnolia
*[http://laphil.org/tickets/adams-70-nixon-china/2017-03-05 Nixon in China, Los Angeles Philharmonic] John Adams conducts, at Walt Disney Concert Hall

=== Monday, March 6 ===

=== Tuesday, March 7 ===
*[http://cap.ucla.edu/calendar/details/trisha_brown_17 Trisha Brown Dance Company - In Plain Site:LA], The Broad

=== Wednesday, March 8 ===
*[https://hammer.ucla.edu/programs-events/2017/03/incident-at-oglala/ Incident at Oglala], Hammer Museum
*[http://www.astro.ucla.edu/planetarium/ UCLA Planetarium public show], UCLA Mathematical Sciences Building, 7-8 p.m.

=== Thursday, March 9 ===
*[https://hammer.ucla.edu/programs-events/2017/03/the-politics-and-problematics-of-representation/ The Politics and Problematics of Representation], Hammer Museum
*[http://downtownartwalk.org/ Downtown LA Art Walk], Gallery Row

=== All days ===
*[http://www.getty.edu/art/exhibitions/breaking_news/index.html Breaking News: Turning the Lends on Mass Media], Getty Center
*[http://www.laweekly.com/event/david-bowie-among-the-mexican-masters-7852901 David Bowie: Among the Mexican Masters], Forest Lawn Memorial Park
*[https://www.centertheatregroup.org/tickets/ahmanson-theatre/2016-17/fun-home/ Fun Home], Ahmanson Theatre
*[https://www.centertheatregroup.org/tickets/mark-taper-forum/2017-18/zoot-suit/ Zoot Suit] Mark Taper Forum

==Getting Around==
All info on getting to the hotel is on the conference website: http://2017.code4lib.org/venue/

[[Category:Code4Lib2017]]

Code4Lib Journal WordPress Customizations

2014-05-24T23:14:48Z

Tomkeays: /* Anti-Spam */

==Plugins==

===Anti-Spam===
;[http://akismet.com/ Akimset]
:Filters out spam-link comments based on their content
;[http://wordpress.org/plugins/wp-recaptcha/ WP-reCAPTCHA]
:Requires users to copy a distorted word before they can comment. We disabled this plugin at one point due to accessibility issues. However, we suffered a spam storm in May 2014 that required either disabling comments on all posts (not trivial) or reinstalling the CAPTCHA plugin.

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

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

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

===URLs===
;C4LJ Remove Parents
:A customization of http://wordpress.org/extend/plugins/remove-parents/. Prettifies category URLs so that issues appear at <code>http://journal.code4lib.org/issues/issue1</code> instead of <code>http://journal.code4lib.org/issues/issues/issue1</code>. (J. Brinley)
;[http://www.feedburner.com/fb/a/help/wordpress_quickstart FeedBurner FeedSmith]
:Redirects the main feed and the general comments feed to FeedBurner

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

==Upgrading==

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

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

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

[[Category:Code4Lib Journal]]

Code4Lib Journal WordPress Customizations

2014-05-05T14:07:09Z

Tomkeays: /* Metadata */

==Plugins==

===Anti-Spam===
;[http://akismet.com/ Akimset]
:Filters out spam-link comments based on their content
;[https://github.com/blaenk/wp-recaptcha WP-reCAPTCHA] - disabled - there were accessibility issues
:Requires users to copy a distorted word before they can comment

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

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

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

===URLs===
;C4LJ Remove Parents
:A customization of http://wordpress.org/extend/plugins/remove-parents/. Prettifies category URLs so that issues appear at <code>http://journal.code4lib.org/issues/issue1</code> instead of <code>http://journal.code4lib.org/issues/issues/issue1</code>. (J. Brinley)
;[http://www.feedburner.com/fb/a/help/wordpress_quickstart FeedBurner FeedSmith]
:Redirects the main feed and the general comments feed to FeedBurner

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

==Upgrading==

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

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

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

[[Category:Code4Lib Journal]]

Code4Lib Journal WordPress Customizations

2014-05-05T14:05:51Z

Tomkeays: /* Metadata */

==Plugins==

===Anti-Spam===
;[http://akismet.com/ Akimset]
:Filters out spam-link comments based on their content
;[https://github.com/blaenk/wp-recaptcha WP-reCAPTCHA] - disabled - there were accessibility issues
:Requires users to copy a distorted word before they can comment

===Metadata===
;DOAJ Export
:Provides information about your posts formatted according to the DOAJ Article XML Schema. (J. Brinley)
;[http://www.lackoftalent.org/michael/blog/unapi-wordpress-plug-in/ unAPI Server]
:Provides information about articles. Useful for Zotero users. (M. Giarlo)
;[http://www.wallandbinkley.com/quaedam/ COinS Quicktags Button] - no longer installed; buggy
:In the non-WYSIWYG editor, can be used to build a basic COinS tag. This has been abandoned in favor of the generator at http://generator.ocoins.info/. (P. Binkley)

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

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

===URLs===
;C4LJ Remove Parents
:A customization of http://wordpress.org/extend/plugins/remove-parents/. Prettifies category URLs so that issues appear at <code>http://journal.code4lib.org/issues/issue1</code> instead of <code>http://journal.code4lib.org/issues/issues/issue1</code>. (J. Brinley)
;[http://www.feedburner.com/fb/a/help/wordpress_quickstart FeedBurner FeedSmith]
:Redirects the main feed and the general comments feed to FeedBurner

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

==Upgrading==

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

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

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

[[Category:Code4Lib Journal]]

Code4Lib Journal WordPress Customizations

2014-05-05T14:01:01Z

Tomkeays: /* Metadata */

==Plugins==

===Anti-Spam===
;[http://akismet.com/ Akimset]
:Filters out spam-link comments based on their content
;[https://github.com/blaenk/wp-recaptcha WP-reCAPTCHA] - disabled - there were accessibility issues
:Requires users to copy a distorted word before they can comment

===Metadata===
;DOAJ Export
:Provides information about your posts formatted according to the DOAJ Article XML Schema. (J. Brinley)
;[http://www.lackoftalent.org/michael/blog/unapi-wordpress-plug-in/ unAPI Server]
:Provides information about articles. Useful for Zotero users. (M. Giarlo)
;[http://www.wallandbinkley.com/quaedam/ COinS Quicktags Button] - no longer installed; buggy
:In the non-WYSIWYG editor, can be used to build a basic COinS tag. This has been abandoned in favor of the generator at http://generator.ocoins.info/.

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

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

===URLs===
;C4LJ Remove Parents
:A customization of http://wordpress.org/extend/plugins/remove-parents/. Prettifies category URLs so that issues appear at <code>http://journal.code4lib.org/issues/issue1</code> instead of <code>http://journal.code4lib.org/issues/issues/issue1</code>. (J. Brinley)
;[http://www.feedburner.com/fb/a/help/wordpress_quickstart FeedBurner FeedSmith]
:Redirects the main feed and the general comments feed to FeedBurner

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

==Upgrading==

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

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

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

[[Category:Code4Lib Journal]]

Code4Lib Journal WordPress Customizations

2014-05-05T13:43:44Z

Tomkeays:

==Plugins==

===Anti-Spam===
;[http://akismet.com/ Akimset]
:Filters out spam-link comments based on their content
;[https://github.com/blaenk/wp-recaptcha WP-reCAPTCHA] - disabled - there were accessibility issues
:Requires users to copy a distorted word before they can comment

===Metadata===
;DOAJ Export
:Provides information about your posts formatted according to the DOAJ Article XML Schema. (J. Brinley)
;[http://www.lackoftalent.org/michael/blog/unapi-wordpress-plug-in/ unAPI Server]
:Provides information about articles. Useful for Zotero users. (M. Giarlo)
;[http://www.wallandbinkley.com/quaedam/ COinS Quicktags Button] - no longer installed; buggy
:In the non-WYSIWYG editor, can be used to build a basic COinS tag. This has been abandoned in favor of the generator at
http://generator.ocoins.info/.

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

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

===URLs===
;C4LJ Remove Parents
:A customization of http://wordpress.org/extend/plugins/remove-parents/. Prettifies category URLs so that issues appear at <code>http://journal.code4lib.org/issues/issue1</code> instead of <code>http://journal.code4lib.org/issues/issues/issue1</code>. (J. Brinley)
;[http://www.feedburner.com/fb/a/help/wordpress_quickstart FeedBurner FeedSmith]
:Redirects the main feed and the general comments feed to FeedBurner

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

==Upgrading==

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

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

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

[[Category:Code4Lib Journal]]

Code4Lib Journal WordPress Customizations

2014-05-05T13:31:52Z

Tomkeays: /* Presentation */

==Plugins==
===Anti-Spam===
;[http://akismet.com/ Akimset]
:Filters out spam-link comments based on their content
;[http://recaptcha.net/plugins/wordpress reCAPTCHA] - disabled - there were accessibility issues
:Requires users to copy a distorted word before they can comment

===Metadata===
;[http://www.wallandbinkley.com/quaedam/ COinS Quicktags Button]
:In the non-WYSIWYG editor, can be used to build a basic COinS tag. This has been abandoned in favor of the generator at http://generator.ocoins.info/.
;[http://www.lackoftalent.org/michael/blog/unapi-wordpress-plug-in/ unAPI Server]
:Provides information about articles. Useful for Zotero users.

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

===URLs===
;C4LJ Remove Parents
:A customization of http://wordpress.org/extend/plugins/remove-parents/. Prettifies category URLs so that issues appear at <code>http://journal.code4lib.org/issues/issue1</code> instead of <code>http://journal.code4lib.org/issues/issues/issue1</code>.
;[http://www.feedburner.com/fb/a/help/wordpress_quickstart FeedBurner FeedSmith]
:Redirects the main feed and the general comments feed to FeedBurner

===Workflow===
;[https://github.com/code4lib/c4lj-issue-manager Issue Manager]
:Enables one-click publishing of new issues, and prevents articles from being published until their associated issue is published.
;[http://www.im-web-gefunden.de/wordpress-plugins/role-manager/ Role Manager]
:Allows creation of custom roles and editing of roles' permissions. Used to create the Reviewer role, which can read Private articles, so that authors can see their articles before publication, and to prevent editors from publishing articles on accident.

==Upgrading==

These fixes were necessary for WP < 2.5, but should not be needed any longer.

===Save the <div>s===
Edit wp-includes/js/tinymce/tiny_mce_config.php, around line 25.
$valid_elements = '-strong/-b[*],-em/-i[*],-font[*],-ul[*],-ol[*],-li[*],*[*]';

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

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

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

[[Category:Code4Lib Journal]]

Code4Lib Journal WordPress Customizations

2014-05-05T13:28:25Z

Tomkeays: /* Workflow */

==Plugins==
===Anti-Spam===
;[http://akismet.com/ Akimset]
:Filters out spam-link comments based on their content
;[http://recaptcha.net/plugins/wordpress reCAPTCHA] - disabled - there were accessibility issues
:Requires users to copy a distorted word before they can comment

===Metadata===
;[http://www.wallandbinkley.com/quaedam/ COinS Quicktags Button]
:In the non-WYSIWYG editor, can be used to build a basic COinS tag. This has been abandoned in favor of the generator at http://generator.ocoins.info/.
;[http://www.lackoftalent.org/michael/blog/unapi-wordpress-plug-in/ unAPI Server]
:Provides information about articles. Useful for Zotero users.

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

===URLs===
;C4LJ Remove Parents
:A customization of http://wordpress.org/extend/plugins/remove-parents/. Prettifies category URLs so that issues appear at <code>http://journal.code4lib.org/issues/issue1</code> instead of <code>http://journal.code4lib.org/issues/issues/issue1</code>.
;[http://www.feedburner.com/fb/a/help/wordpress_quickstart FeedBurner FeedSmith]
:Redirects the main feed and the general comments feed to FeedBurner

===Workflow===
;[https://github.com/code4lib/c4lj-issue-manager Issue Manager]
:Enables one-click publishing of new issues, and prevents articles from being published until their associated issue is published.
;[http://www.im-web-gefunden.de/wordpress-plugins/role-manager/ Role Manager]
:Allows creation of custom roles and editing of roles' permissions. Used to create the Reviewer role, which can read Private articles, so that authors can see their articles before publication, and to prevent editors from publishing articles on accident.

==Upgrading==

These fixes were necessary for WP < 2.5, but should not be needed any longer.

===Save the <div>s===
Edit wp-includes/js/tinymce/tiny_mce_config.php, around line 25.
$valid_elements = '-strong/-b[*],-em/-i[*],-font[*],-ul[*],-ol[*],-li[*],*[*]';

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

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

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

[[Category:Code4Lib Journal]]

Code4Lib Journal WordPress Customizations

2014-05-05T13:27:41Z

Tomkeays: /* Anti-Spam */

==Plugins==
===Anti-Spam===
;[http://akismet.com/ Akimset]
:Filters out spam-link comments based on their content
;[http://recaptcha.net/plugins/wordpress reCAPTCHA] - disabled - there were accessibility issues
:Requires users to copy a distorted word before they can comment

===Metadata===
;[http://www.wallandbinkley.com/quaedam/ COinS Quicktags Button]
:In the non-WYSIWYG editor, can be used to build a basic COinS tag. This has been abandoned in favor of the generator at http://generator.ocoins.info/.
;[http://www.lackoftalent.org/michael/blog/unapi-wordpress-plug-in/ unAPI Server]
:Provides information about articles. Useful for Zotero users.

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

===URLs===
;C4LJ Remove Parents
:A customization of http://wordpress.org/extend/plugins/remove-parents/. Prettifies category URLs so that issues appear at <code>http://journal.code4lib.org/issues/issue1</code> instead of <code>http://journal.code4lib.org/issues/issues/issue1</code>.
;[http://www.feedburner.com/fb/a/help/wordpress_quickstart FeedBurner FeedSmith]
:Redirects the main feed and the general comments feed to FeedBurner

===Workflow===
;Issue Manager
:Enables one-click publishing of new issues, and prevents articles from being published until their associated issue is published.
;[http://www.im-web-gefunden.de/wordpress-plugins/role-manager/ Role Manager]
:Allows creation of custom roles and editing of roles' permissions. Used to create the Reviewer role, which can read Private articles, so that authors can see their articles before publication, and to prevent editors from publishing articles on accident.

==Upgrading==

These fixes were necessary for WP < 2.5, but should not be needed any longer.

===Save the <div>s===
Edit wp-includes/js/tinymce/tiny_mce_config.php, around line 25.
$valid_elements = '-strong/-b[*],-em/-i[*],-font[*],-ul[*],-ol[*],-li[*],*[*]';

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

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

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

[[Category:Code4Lib Journal]]

Code4Lib Journal Deadlines

2013-04-15T14:30:45Z

Tomkeays: /* Twenty-second 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

===Twenty-second issue===
* Call for proposals: Monday, June 10, 2013
* 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===
* 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===
* 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===

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

* 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

2013-04-15T14:28:00Z

Tomkeays: /* Twenty-second 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

===Twenty-second issue===
* Call for proposals: Monday, May 13, 2013
* Proposals due: Friday, June 14, 2013
* Proposals accepted: Friday, June 21, 2013
* First draft due: Friday, July 19, 2013
* Second draft due: Friday, August 16, 2013
* Publication date: Monday, September 16, 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===
* 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===
* 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===

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

* 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

2013-04-15T14:26:54Z

Tomkeays: /* Twenty-second issue added */

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

===Twenty-second issue===
* Call for proposals: Sunday, May 12, 2013
* Proposals due: Thursday, June 13, 2013
* Proposals accepted: Thursday, June 20, 2013
* First draft due: Thursday, July 18, 2013
* Second draft due: Thursday, August 15, 2013
* Publication date: Sunday, September 15, 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===
* 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===
* 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===

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

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

One recommended tool/resource for n00bs

2013-02-16T01:07:19Z

Tomkeays: /* Software */

===One recommended tool/resource for n00bs===

These resources/tools were recommended by the Code4Lib community in Nov. 2012, specifically for new coding librarians and library coders. The whole thread of discussion is available at [http://www.mail-archive.com/code4lib@listserv.nd.edu/msg15762.html the C4L listserv archive].

Please fill out a [https://docs.google.com/spreadsheet/viewform?formkey=dHNPVWgyX0E2a20xWHBHS1dJV05Pb0E6MQ#gid=0 mini-survey] if this was helpful to you. Thank you!

====Tools/Resources====

=====Books or Things to read=====
* O'Reiley Head first series
*Visual QuickStart Guides http://www.peachpit.com/imprint/series_detail.aspx?ser=335245
*[https://docs.google.com/spreadsheet/ccc?key=0AlVSWa90m8umdGg3U0h4bjdMT0ttVUJBU3RCaUc0WGc#gid=0 QA Collection Purchases for Code4Lib]
* The top 9 in a hacker's bookshelf: http://grokcode.com/11/the-top-9-in-a-hackers-bookshelf/
* "How to Design Programs" http://www.ccs.neu.edu/home/matthias/HtDP2e/. Good for newbie coders.
* Kernighan and Ritchie's [http://www.worldcat.org/title/c-programming-language/oclc/17650642 "The C Programming Language."] A keeper for life, and surprisingly readable and directed to the newbie. Also [http://www.worldcat.org/title/pragmatic-programmer-from-journeyman-to-master/oclc/42038638 "The Pragmatic Programmer"] by Andrew Hunt and David Thomas.
* http://www.w3.org/International
* Guide for the Perplexed on the code4lib wiki: http://wiki.code4lib.org/index.php/A_Guide_for_the_Perplexed
* Video series on command line basics from Lullabot: http://drupalize.me/series/command-line-basics-series

=====Software=====

* Vi- because it keeps me (you?) focused.
* [http://www.activestate.com/komodo-edit Komodo Edit]
*AMP (LAMP, WAMP, MAMP) stacks for an easy install of Apache, mySQL + perl/ python / php.
*A @rdio subscription. :) And a text editor with syntax highlighting.
* Git (Version Control)
* Github, Bitbucket and Other Remote Git Services
* Emmet, http://docs.emmet.io/ (supersedes Zen Coding, http://code.google.com/p/zen-coding/ ) The idea is that it lets you use CSS-like selectors as tags that can be expanded into full HTML snippets.
* [http://sass-lang.com/ SASS Syntactically Awesome Stylesheets]
* LESS http://lesscss.org/
* Compass http://compass-style.org/ - extends SASS with reusable patterns
* BareBones's [http://www.barebones.com/products/bbedit/index.html BBEdit]
* Sublime Text & Zen Coding (recently reborn as [http://docs.emmet.io Emmet]). Saves a lot of keystrokes when writing web content.
* The best one IMHO is [http://www.sublimetext.com Sublime Text 2]. Oh, okay, I can't resist - I'm going to cheat and list a second: everyone needs to stop writing just CSS and complement it with SASS (syntactically awesome stylesheets) & Compass - http://sass-lang.com/. Totally invaluable for any front-end work. It makes CSS fun.
* [http://www.virtualbox.org VirtualBox] to make new VM setup and deployment easier we use [http://vagrantup.com/ Vagrant]
* Version control. My own strong preference is for git (either managed locally or through github.com), but really, just pick a version control solution and use it. If you value your work at all, it should be in version control. Smart use of version control can make finding and fixing problems in code much, much easier - but even fairly naive use of it leaves you with much, much better tools for fixing screw ups than you have without it.

=====Websites=====
*Code4Lib listserv, IRC, [http://journal.code4lib.org journal] (duh)
* Google is more useful than any reference book to find answers to programming problems.
* [http://stackoverflow.com StackOverflow] is a great site for questions.
*[http://lynda.com lynda.com]
*JS Fiddle http://jsfiddle.net/
*CodePen http://codepen.io/
*[http://stackexchange.com/ StackExchange] (by extension, StackOverflow and [http://libraries.stackexchange.com/ the Libraries StackExchange] site).
*[http://css-tricks.com CSS Tricks ]

=====Meetups and User Groups=====

* Perl Mongers http://www.pm.org/groups/
* Python Local User Groups http://wiki.python.org/moin/LocalUserGroups
* R Users Group Meetups http://r-users-group.meetup.com/
* Drupal Groups http://groups.drupal.org/
* Ruby User Groups http://www.ruby-lang.org/en/community/user-groups/
* Haskell User Groups http://www.haskell.org/haskellwiki/User_groups
* ColdFusion Meetups http://coldfusion.meetup.com/

=====Other=====

*Resources for lots of languages: [http://pear.ly/8ohL pear.ly/8ohL]
* [http://catcode.pbworks.com/w/page/49680175/Resources Catcode]
* FOSS4lib http://foss4lib.org/
* I can already feel the collective rolling of eyes for this, but what about Twitter? It's not a guide or manual, but start following and engaging talented developers and library geeks on Twitter and you'll soon have more help than you know what to do with. Plus, no Zoia ;)
*Practice! No matter the learning material, nothing will really sink in unless you apply it in the wild (like a small project).
* It's still useful to learn a little something about configuring a webserver / database / etc.

=====Advice on what to do=====
*Building things that help people matters, and for that you need empathy.
* Reusing people's [http://dotfiles.github.com/ public dotfiles],my favorite being [https://github.com/mathiasbynens/dotfiles Mathias Bynens']. Using a mature dotfiles collection can help bootstrap you to use the command line more and start grabbing vital tools from package managers like Homebrew or npm that you might not think of otherwise. I'm still a newbie coder but reusing dotfiles gives me the confidence to tweak things here and there without building a ton from scratch.
* I'm taking "tool" to mean a piece of hardware. I'd recommend some old laptop with your favorite linux distro less desktop. Why? Well the main thing is that it puts them into a position where they're not learning to be a google copy/paste coder given the lack of the desktop, mouse and distractions like email. They can also learn to setup the server environment on their new dev box and eventually do all sorts of cool stuff.
* A cheapie online webhosting account - like a $10 a month one - and multiple URLs. Multiple URLs will make them point a URL at a nameserver at least once ideally, and to understand that the two are separate and what you can do with domains and subdomains. The cheapie webhosting account will let them play with installing popular content management systems manually and with one-click installs. The most important thing is to break things and then rebuild them. The worst possible thing would be to build a website, leave it up as their public face or personal website, and be nervous to wreck it so notchange or play with different CMSes (another reason multiple URLs might psychologically be better - they encourage experimentation on one and the person can make the other a static goal oriented publishing area).The more the cheapie hosting account experience I have, the more I know what's cheap and easy to do, and the more I see very specific benefits to adedicated server. It makes me more intentional and able to better assess the value of services vendors provide. That's more web4lib ish, but ultimately if someone experiments enough they have to get comfortable with php. Scripting is the gateway drug.
* +1 to web-hosting as it gives the ability install one's own software on one's domain (which feels great) *and* easy access to shell. And when web-hosting feels like too much of a barrier to access, sites like jsfiddle where you can immediately start adding *and* sharing code is key. IMHO the initial appeal of [http://www.codecademy.com/ Codecademy] was that it removed all barriers to getting started. Getting a laptop's localhost set up is too daunting for a first step, I think.

One recommended tool/resource for n00bs

2013-02-16T01:05:23Z

Tomkeays: /* Websites */

===One recommended tool/resource for n00bs===

These resources/tools were recommended by the Code4Lib community in Nov. 2012, specifically for new coding librarians and library coders. The whole thread of discussion is available at [http://www.mail-archive.com/code4lib@listserv.nd.edu/msg15762.html the C4L listserv archive].

Please fill out a [https://docs.google.com/spreadsheet/viewform?formkey=dHNPVWgyX0E2a20xWHBHS1dJV05Pb0E6MQ#gid=0 mini-survey] if this was helpful to you. Thank you!

====Tools/Resources====

=====Books or Things to read=====
* O'Reiley Head first series
*Visual QuickStart Guides http://www.peachpit.com/imprint/series_detail.aspx?ser=335245
*[https://docs.google.com/spreadsheet/ccc?key=0AlVSWa90m8umdGg3U0h4bjdMT0ttVUJBU3RCaUc0WGc#gid=0 QA Collection Purchases for Code4Lib]
* The top 9 in a hacker's bookshelf: http://grokcode.com/11/the-top-9-in-a-hackers-bookshelf/
* "How to Design Programs" http://www.ccs.neu.edu/home/matthias/HtDP2e/. Good for newbie coders.
* Kernighan and Ritchie's [http://www.worldcat.org/title/c-programming-language/oclc/17650642 "The C Programming Language."] A keeper for life, and surprisingly readable and directed to the newbie. Also [http://www.worldcat.org/title/pragmatic-programmer-from-journeyman-to-master/oclc/42038638 "The Pragmatic Programmer"] by Andrew Hunt and David Thomas.
* http://www.w3.org/International
* Guide for the Perplexed on the code4lib wiki: http://wiki.code4lib.org/index.php/A_Guide_for_the_Perplexed
* Video series on command line basics from Lullabot: http://drupalize.me/series/command-line-basics-series

=====Software=====

* Vi- because it keeps me (you?) focused.
* [http://www.activestate.com/komodo-edit Komodo Edit]
*AMP (LAMP, WAMP, MAMP) stacks for an easy install of Apache, mySQL + perl/ python / php.
*A @rdio subscription. :) And a text editor with syntax highlighting.
* Git (Version Control)
* Github, Bitbucket and Other Remote Git Services
* Emmet, http://docs.emmet.io/ (supersedes Zen Coding, http://code.google.com/p/zen-coding/ ) The idea is that it lets you use CSS-like selectors as tags that can be expanded into full HTML snippets.
* [http://sass-lang.com/ SASS Syntactically Awesome Stylesheets]
* LESS http://lesscss.org/
* BareBones's [http://www.barebones.com/products/bbedit/index.html BBEdit]
* Sublime Text & Zen Coding (recently reborn as [http://docs.emmet.io Emmet]). Saves a lot of keystrokes when writing web content.
* The best one IMHO is [http://www.sublimetext.com Sublime Text 2]. Oh, okay, I can't resist - I'm going to cheat and list a second: everyone needs to stop writing just CSS and complement it with SASS (syntactically awesome stylesheets) & Compass - http://sass-lang.com/. Totally invaluable for any front-end work. It makes CSS fun.
* [http://www.virtualbox.org VirtualBox] to make new VM setup and deployment easier we use [http://vagrantup.com/ Vagrant]
* Version control. My own strong preference is for git (either managed locally or through github.com), but really, just pick a version control solution and use it. If you value your work at all, it should be in version control. Smart use of version control can make finding and fixing problems in code much, much easier - but even fairly naive use of it leaves you with much, much better tools for fixing screw ups than you have without it.

=====Websites=====
*Code4Lib listserv, IRC, [http://journal.code4lib.org journal] (duh)
* Google is more useful than any reference book to find answers to programming problems.
* [http://stackoverflow.com StackOverflow] is a great site for questions.
*[http://lynda.com lynda.com]
*JS Fiddle http://jsfiddle.net/
*CodePen http://codepen.io/
*[http://stackexchange.com/ StackExchange] (by extension, StackOverflow and [http://libraries.stackexchange.com/ the Libraries StackExchange] site).
*[http://css-tricks.com CSS Tricks ]

=====Meetups and User Groups=====

* Perl Mongers http://www.pm.org/groups/
* Python Local User Groups http://wiki.python.org/moin/LocalUserGroups
* R Users Group Meetups http://r-users-group.meetup.com/
* Drupal Groups http://groups.drupal.org/
* Ruby User Groups http://www.ruby-lang.org/en/community/user-groups/
* Haskell User Groups http://www.haskell.org/haskellwiki/User_groups
* ColdFusion Meetups http://coldfusion.meetup.com/

=====Other=====

*Resources for lots of languages: [http://pear.ly/8ohL pear.ly/8ohL]
* [http://catcode.pbworks.com/w/page/49680175/Resources Catcode]
* FOSS4lib http://foss4lib.org/
* I can already feel the collective rolling of eyes for this, but what about Twitter? It's not a guide or manual, but start following and engaging talented developers and library geeks on Twitter and you'll soon have more help than you know what to do with. Plus, no Zoia ;)
*Practice! No matter the learning material, nothing will really sink in unless you apply it in the wild (like a small project).
* It's still useful to learn a little something about configuring a webserver / database / etc.

=====Advice on what to do=====
*Building things that help people matters, and for that you need empathy.
* Reusing people's [http://dotfiles.github.com/ public dotfiles],my favorite being [https://github.com/mathiasbynens/dotfiles Mathias Bynens']. Using a mature dotfiles collection can help bootstrap you to use the command line more and start grabbing vital tools from package managers like Homebrew or npm that you might not think of otherwise. I'm still a newbie coder but reusing dotfiles gives me the confidence to tweak things here and there without building a ton from scratch.
* I'm taking "tool" to mean a piece of hardware. I'd recommend some old laptop with your favorite linux distro less desktop. Why? Well the main thing is that it puts them into a position where they're not learning to be a google copy/paste coder given the lack of the desktop, mouse and distractions like email. They can also learn to setup the server environment on their new dev box and eventually do all sorts of cool stuff.
* A cheapie online webhosting account - like a $10 a month one - and multiple URLs. Multiple URLs will make them point a URL at a nameserver at least once ideally, and to understand that the two are separate and what you can do with domains and subdomains. The cheapie webhosting account will let them play with installing popular content management systems manually and with one-click installs. The most important thing is to break things and then rebuild them. The worst possible thing would be to build a website, leave it up as their public face or personal website, and be nervous to wreck it so notchange or play with different CMSes (another reason multiple URLs might psychologically be better - they encourage experimentation on one and the person can make the other a static goal oriented publishing area).The more the cheapie hosting account experience I have, the more I know what's cheap and easy to do, and the more I see very specific benefits to adedicated server. It makes me more intentional and able to better assess the value of services vendors provide. That's more web4lib ish, but ultimately if someone experiments enough they have to get comfortable with php. Scripting is the gateway drug.
* +1 to web-hosting as it gives the ability install one's own software on one's domain (which feels great) *and* easy access to shell. And when web-hosting feels like too much of a barrier to access, sites like jsfiddle where you can immediately start adding *and* sharing code is key. IMHO the initial appeal of [http://www.codecademy.com/ Codecademy] was that it removed all barriers to getting started. Getting a laptop's localhost set up is too daunting for a first step, I think.

One recommended tool/resource for n00bs

2013-02-16T01:01:32Z

Tomkeays: /* Other */

===One recommended tool/resource for n00bs===

These resources/tools were recommended by the Code4Lib community in Nov. 2012, specifically for new coding librarians and library coders. The whole thread of discussion is available at [http://www.mail-archive.com/code4lib@listserv.nd.edu/msg15762.html the C4L listserv archive].

Please fill out a [https://docs.google.com/spreadsheet/viewform?formkey=dHNPVWgyX0E2a20xWHBHS1dJV05Pb0E6MQ#gid=0 mini-survey] if this was helpful to you. Thank you!

====Tools/Resources====

=====Books or Things to read=====
* O'Reiley Head first series
*Visual QuickStart Guides http://www.peachpit.com/imprint/series_detail.aspx?ser=335245
*[https://docs.google.com/spreadsheet/ccc?key=0AlVSWa90m8umdGg3U0h4bjdMT0ttVUJBU3RCaUc0WGc#gid=0 QA Collection Purchases for Code4Lib]
* The top 9 in a hacker's bookshelf: http://grokcode.com/11/the-top-9-in-a-hackers-bookshelf/
* "How to Design Programs" http://www.ccs.neu.edu/home/matthias/HtDP2e/. Good for newbie coders.
* Kernighan and Ritchie's [http://www.worldcat.org/title/c-programming-language/oclc/17650642 "The C Programming Language."] A keeper for life, and surprisingly readable and directed to the newbie. Also [http://www.worldcat.org/title/pragmatic-programmer-from-journeyman-to-master/oclc/42038638 "The Pragmatic Programmer"] by Andrew Hunt and David Thomas.
* http://www.w3.org/International
* Guide for the Perplexed on the code4lib wiki: http://wiki.code4lib.org/index.php/A_Guide_for_the_Perplexed
* Video series on command line basics from Lullabot: http://drupalize.me/series/command-line-basics-series

=====Software=====

* Vi- because it keeps me (you?) focused.
* [http://www.activestate.com/komodo-edit Komodo Edit]
*AMP (LAMP, WAMP, MAMP) stacks for an easy install of Apache, mySQL + perl/ python / php.
*A @rdio subscription. :) And a text editor with syntax highlighting.
* Git (Version Control)
* Github, Bitbucket and Other Remote Git Services
* Emmet, http://docs.emmet.io/ (supersedes Zen Coding, http://code.google.com/p/zen-coding/ ) The idea is that it lets you use CSS-like selectors as tags that can be expanded into full HTML snippets.
* [http://sass-lang.com/ SASS Syntactically Awesome Stylesheets]
* LESS http://lesscss.org/
* BareBones's [http://www.barebones.com/products/bbedit/index.html BBEdit]
* Sublime Text & Zen Coding (recently reborn as [http://docs.emmet.io Emmet]). Saves a lot of keystrokes when writing web content.
* The best one IMHO is [http://www.sublimetext.com Sublime Text 2]. Oh, okay, I can't resist - I'm going to cheat and list a second: everyone needs to stop writing just CSS and complement it with SASS (syntactically awesome stylesheets) & Compass - http://sass-lang.com/. Totally invaluable for any front-end work. It makes CSS fun.
* [http://www.virtualbox.org VirtualBox] to make new VM setup and deployment easier we use [http://vagrantup.com/ Vagrant]
* Version control. My own strong preference is for git (either managed locally or through github.com), but really, just pick a version control solution and use it. If you value your work at all, it should be in version control. Smart use of version control can make finding and fixing problems in code much, much easier - but even fairly naive use of it leaves you with much, much better tools for fixing screw ups than you have without it.

=====Websites=====
*Code4Lib listserv, IRC, [http://journal.code4lib.org journal] (duh)
* Google is more useful than any reference book to find answers to programming problems.
* [http://stackoverflow.com StackOverflow] is a great site for questions.
*[http://lynda.com lynda.com]
*JS Fiddle http://jsfiddle.net/
*[http://stackexchange.com/ StackExchange] (by extension, StackOverflow and [http://libraries.stackexchange.com/ the Libraries StackExchange] site).
*[http://css-tricks.com CSS Tricks ]

=====Meetups and User Groups=====

* Perl Mongers http://www.pm.org/groups/
* Python Local User Groups http://wiki.python.org/moin/LocalUserGroups
* R Users Group Meetups http://r-users-group.meetup.com/
* Drupal Groups http://groups.drupal.org/
* Ruby User Groups http://www.ruby-lang.org/en/community/user-groups/
* Haskell User Groups http://www.haskell.org/haskellwiki/User_groups
* ColdFusion Meetups http://coldfusion.meetup.com/

=====Other=====

*Resources for lots of languages: [http://pear.ly/8ohL pear.ly/8ohL]
* [http://catcode.pbworks.com/w/page/49680175/Resources Catcode]
* FOSS4lib http://foss4lib.org/
* I can already feel the collective rolling of eyes for this, but what about Twitter? It's not a guide or manual, but start following and engaging talented developers and library geeks on Twitter and you'll soon have more help than you know what to do with. Plus, no Zoia ;)
*Practice! No matter the learning material, nothing will really sink in unless you apply it in the wild (like a small project).
* It's still useful to learn a little something about configuring a webserver / database / etc.

=====Advice on what to do=====
*Building things that help people matters, and for that you need empathy.
* Reusing people's [http://dotfiles.github.com/ public dotfiles],my favorite being [https://github.com/mathiasbynens/dotfiles Mathias Bynens']. Using a mature dotfiles collection can help bootstrap you to use the command line more and start grabbing vital tools from package managers like Homebrew or npm that you might not think of otherwise. I'm still a newbie coder but reusing dotfiles gives me the confidence to tweak things here and there without building a ton from scratch.
* I'm taking "tool" to mean a piece of hardware. I'd recommend some old laptop with your favorite linux distro less desktop. Why? Well the main thing is that it puts them into a position where they're not learning to be a google copy/paste coder given the lack of the desktop, mouse and distractions like email. They can also learn to setup the server environment on their new dev box and eventually do all sorts of cool stuff.
* A cheapie online webhosting account - like a $10 a month one - and multiple URLs. Multiple URLs will make them point a URL at a nameserver at least once ideally, and to understand that the two are separate and what you can do with domains and subdomains. The cheapie webhosting account will let them play with installing popular content management systems manually and with one-click installs. The most important thing is to break things and then rebuild them. The worst possible thing would be to build a website, leave it up as their public face or personal website, and be nervous to wreck it so notchange or play with different CMSes (another reason multiple URLs might psychologically be better - they encourage experimentation on one and the person can make the other a static goal oriented publishing area).The more the cheapie hosting account experience I have, the more I know what's cheap and easy to do, and the more I see very specific benefits to adedicated server. It makes me more intentional and able to better assess the value of services vendors provide. That's more web4lib ish, but ultimately if someone experiments enough they have to get comfortable with php. Scripting is the gateway drug.
* +1 to web-hosting as it gives the ability install one's own software on one's domain (which feels great) *and* easy access to shell. And when web-hosting feels like too much of a barrier to access, sites like jsfiddle where you can immediately start adding *and* sharing code is key. IMHO the initial appeal of [http://www.codecademy.com/ Codecademy] was that it removed all barriers to getting started. Getting a laptop's localhost set up is too daunting for a first step, I think.

Code4Lib Journal WordPress Input Guidelines

2012-12-18T15:11:10Z

Tomkeays: /* Code Highlighting */

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

==The WP Admin Interface==
To get to WordPress interface for entering an article, choose 'Site Admin' from the footer of any Journal page, login if necessary, and then choose Write//Write Post from the WP admin menus. (Alternatively, go to http://journal.code4lib.org/wp-admin/). If you don't have a WordPress editor login and need one, talk to our web admin (Jon Brinley).

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

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

==Article Content==
The body of the article goes in the "Post" field. The top-level header (<code><h1></code>) is used for the title of the post, so start with second-level headers (<code><h2></code>) for sections of the article. Any header from second- to sixth-level may be used as appropriate. Use HTML markup appropriately and semantically, ''e.g.'', <code><em></code> for emphasized text, <code><strong></code> for strongly emphasized text, <code><blockquote></code> when quoting blocks of text. Avoid such monstrosities as <code><font></code> and <code><blink></code>.

===Pasting from Word===

If you just paste content from Word into WP, it ends up with REALLY BAD html. Fortunately, WP has a built-in feature to help with this. Open the 'advanced toolbar' in editing GUI (right-most link), then click on the paste-from-word icon. This transforms Word's html into really nice pretty html.

===Images and Attached Content===
In-line images should be no wider than 500px.

The caption for an image should be entered in a p with class="caption":
<nowiki><p class="caption">Figure 1. How to Caption an Image.</p>
</nowiki>
In general, we bold the figure / table label using the strong tag:
<nowiki><p class="caption"><strong>Figure 1.</strong> How to Caption an Image.</p>
</nowiki>

'''Uploading files manually'''

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

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

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

in there you'll find an "issue1" subdir (or issueX subdir--if you don't, create one or ask for help creating one!). Inside THERE, create a subdir with the last name of the first author, and put all your image and other attached content in there. It will now have this sort of url:
http://journal.code4lib.org/media/issue1/smith/imagename.png

Add to your img src or a href's as desired. You can use this not just for images, but for extended code attachments, etc. (see below)

'''Uploading media via WordPress'''

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

==== Video ====

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

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

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

===Code===

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

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

Put all inline code in <code><pre></code> tags.

====Code Highlighting====

If the code is in a supported language, we can do syntax highlighting.

ibiblio has a PHPS extensionm, so if you an "s" on the end of .php files, e.g.,
<filename>.phps
it does syntax highlighting for you.

We're still deciding if we like the syntax highlighting, don't feel compelled to make it work if it's not working for you (but please let other editors know what your experience is). Around your code, include
[sourcecode language='langcode']...[/sourcecode]

Replace <code>langcode</code> with the appropriate code from the following list (if more than one option for a language, any one will work).

{|
!Language!!Code
|-
|C++||cpp, c, c++
|-
|C#||c#, c-sharp, csharp
|-
|CSS||css
|-
|Delphi||delphi, pascal
|-
|Java||java
|-
|JavaScript||js, jscript, javascript
|-
|PHP||php
|-
|Python||py, python
|-
|Ruby||rb, ruby, rails, ror
|-
|SQL||sql
|-
|VB||vb, vb.net
|-
|XML/HTML||xml, html, xhtml, xslt
|}

Example:
[sourcecode language='css']
body {
font-size: 0.625em;
background-color: #0000ff;
color: #ffff00;
}
[/sourcecode]

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

==Abstract==

While you are editing the article, there is a box labeled "Optional Excerpt" a little ways below the "Post" field. Put the abstract here. Use HTML markup as appropriate. What you put in this field is what will be distributed in our syndication feed and what will appear before the article as the abstract.

Assigned editors are ultimately responsible for a good abstract. Authors aren't always the best at writing good abstracts for their articles, you should probably revise or even write a new one from scratch as necessary, even when the author has provided one. Some of the abstracts for my assigned articles haven't even mentioned what I consider the most significant features of the article.

Since indexes (like EBSCO) may end up indexing abstracts and not full text (and even full text indexes may weigh abstracts more highly), the abstract should probably include any important terms that should 'hit' on the article, such as key technologies or concepts.

I've found that extracting sentences or clauses from the article itself is a good way to build an abstract that will represent the article as the authors intended. The conclusion section is often a good place to look for such key sentences/clauses.

Final abstracts should be passed by the authors for approval.

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

<pre><a href="http://journal.code4lib.org/coins">(COinS)</a></pre>

This is so the user without a browser extension will see that something is there she might be interested in, and get an explanation of COinS and how to make use of it.

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

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

==Author Information==

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

End each article with a second-level header that says "About the Author(s)", with class="abouttheauthor" set. Then give a short paragraph about each author. We do want to have some kind of contact information published (personal web page, email address (obscured if desired), etc.) for each author.

There is a box beneath the article-editing box with the label "Author(s)". Anything you put in this field will be treated as the author of the article. This will show up in the ToC and in the syndication feeds. If you don't populate this field, WordPress will use the username of the editor, instead.

==Categories/Tags==
Posts will have "Uncagetorized" checked by default. Uncheck that box, and check the box next to the current issue, which will be a subcategory of "Issues." Do not check the "Issues" category. We generally do not add tags, except for Conference reviews

==WordPress Buttons==

;Save
:Saves the article, sets the post status to whatever option is selected in the Publish Status form.
;Publish
:Saves the article, sets the post status to Pending Review and assigns a timestamp to the article.

If an issue is not yet published, setting the post status to "Published" or clicking the "Publish" button will set the article to "Pending Review" status. If the issue is already published, this would actually publish the article.

==WordPress Post Status==
An article has four possible statuses. However, only the first three statuses are available to editors.
;Draft
:Use for not yet complete articles. Only editors can see these.
;Pending Review
:Use for sharing the article with authors. Editors and anyone logged in with user ID 17 (i.e., the author account) can see these. See this [http://groups.google.com/group/c4lj-articles/browse_thread/thread/1231b06c09f1289f post] on c4lj-articles for the login information for the author account (username: author).
;Private
:We don't use this option anymore.
;Published
:A published post is visible to everyone. It is part of the RSS feed. If you're editing an already published post, don't select anything in the post status form, just hit Save.

==Publishing an Issue==

# Let everyone on the c4lj-articles list know you are getting ready to publish (so they can save and close any open articles).
# Log in to WordPress
# Make sure that all articles for the issue have the correct issue category selected and have been set to 'Pending Review'. Make sure that the "Uncategorized" and "Issues" categories are unchecked (only the specific issue should be selected).
# Sanity check: count the number of posts which should appear in the publish list
# Click on Posts -> Issues (on the left side)
# Click on "Publish" for the issue you'd like to publish.
## You'll get a list of every "Pending Review" article in that issue. Make sure the number of articles in the list matches your previous count. Don't see all the articles you think you should see? They could be still in Draft status, or not in the correct Issue category, or still have "Uncategorized" selected, or someone may still have it in edit mode. Go back to the posts list and make any necessary changes, and start from #5 again.
# Drag and drop the article titles until they're in the order you want. The order you see there is the order you'll see on the home page (and probably the opposite of the order you'll see in your feed reader).
## Note: It's the coordinating editor's responsibility to decide what order he or she would like the articles to show up in, and order them appropriately when publishing the issue. In general, we try to put the articles with the widest appeal first, and special types (columns, special reports, book reviews, etc.) at the end.
# Click on Posts -> Categories (on the left side)
# Make sure all three fields for the current issue are filled in and correct:
## The human-readable name of the issue goes into the Name field -- e.g., "Issue 15".
## The date of publication goes into the Description field -- e.g., "2011-10-31".
## The URL name goes into the Slug field -- e.g., "issue15" would give the URL of the issue, http://journal.code4lib.org/issues/issue15
# Click "Publish Issue" (optionally setting the publication time, first). Setting the time should only have an impact on readers who are not logged into the c4lj site. Editors will be able to see the published articles.
# Go to the Journal front page; check the number of articles is correct (again) and that they are in the right order. If there is a problem, go back to the admin interface, click on Posts -> Issues and click Unpublish for the issue. Make whatever corrections are needed and proceed from #5 again.
# Once the issue is finally published, go to [[Code4Lib_Journal_Entries_in_Directory_of_Open_Access_Journals]] and follow the directions to upload the issue metadata to DOAJ.
# Send out announcements (see [[Code4Lib_Journal_Publicity_Venues]])

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

[[Category:Code4Lib Journal]]

Code4Lib Journal WordPress Input Guidelines

2012-12-18T15:10:39Z

Tomkeays: /* Code Highlighting */

Code4Lib Journal WordPress Input Guidelines

2012-12-18T11:52:06Z

Tomkeays: /* Code Highlighting */

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

==The WP Admin Interface==
To get to WordPress interface for entering an article, choose 'Site Admin' from the footer of any Journal page, login if necessary, and then choose Write//Write Post from the WP admin menus. (Alternatively, go to http://journal.code4lib.org/wp-admin/). If you don't have a WordPress editor login and need one, talk to our web admin (Jon Brinley).

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

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

==Article Content==
The body of the article goes in the "Post" field. The top-level header (<code><h1></code>) is used for the title of the post, so start with second-level headers (<code><h2></code>) for sections of the article. Any header from second- to sixth-level may be used as appropriate. Use HTML markup appropriately and semantically, ''e.g.'', <code><em></code> for emphasized text, <code><strong></code> for strongly emphasized text, <code><blockquote></code> when quoting blocks of text. Avoid such monstrosities as <code><font></code> and <code><blink></code>.

===Pasting from Word===

If you just paste content from Word into WP, it ends up with REALLY BAD html. Fortunately, WP has a built-in feature to help with this. Open the 'advanced toolbar' in editing GUI (right-most link), then click on the paste-from-word icon. This transforms Word's html into really nice pretty html.

===Images and Attached Content===
In-line images should be no wider than 500px.

The caption for an image should be entered in a p with class="caption":
<nowiki><p class="caption">Figure 1. How to Caption an Image.</p>
</nowiki>
In general, we bold the figure / table label using the strong tag:
<nowiki><p class="caption"><strong>Figure 1.</strong> How to Caption an Image.</p>
</nowiki>

'''Uploading files manually'''

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

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

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

in there you'll find an "issue1" subdir (or issueX subdir--if you don't, create one or ask for help creating one!). Inside THERE, create a subdir with the last name of the first author, and put all your image and other attached content in there. It will now have this sort of url:
http://journal.code4lib.org/media/issue1/smith/imagename.png

Add to your img src or a href's as desired. You can use this not just for images, but for extended code attachments, etc. (see below)

'''Uploading media via WordPress'''

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

==== Video ====

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

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

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

===Code===

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

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

Put all inline code in <code><pre></code> tags.

====Code Highlighting====

If the code is in a supported language, we can do syntax highlighting.

ibiblio has a PHPS extensionm, so if you an "s" on the end of .php files, e.g.,
<filename>.phps
it does syntax highlighting for you.

We're still deciding if we like the syntax highlighting, don't feel compelled to make it work if it's not working for you (but please let other editors know what your experience is). Around your code, include
[sourcecode language='langcode']...[/sourcecode]

Replace <code>langcode</code> with the appropriate code from the following list (if more than one option for a language, any one will work).

{|
!Language!!Code
|-
|C++||cpp, c, c++
|-
|C#||c#, c-sharp, csharp
|-
|CSS||css
|-
|Delphi||delphi, pascal
|-
|Java||java
|-
|JavaScript||js, jscript, javascript
|-
|PHP||php
|-
|Python||py, python
|-
|Ruby||rb, ruby, rails, ror
|-
|SQL||sql
|-
|VB||vb, vb.net
|-
|XML/HTML||xml, html, xhtml, xslt
|}

Example:
[sourcecode language='css']body {
font-size: 0.625em;
background-color: #0000ff;
color: #ffff00;
}[/sourcecode]

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

==Abstract==

While you are editing the article, there is a box labeled "Optional Excerpt" a little ways below the "Post" field. Put the abstract here. Use HTML markup as appropriate. What you put in this field is what will be distributed in our syndication feed and what will appear before the article as the abstract.

Assigned editors are ultimately responsible for a good abstract. Authors aren't always the best at writing good abstracts for their articles, you should probably revise or even write a new one from scratch as necessary, even when the author has provided one. Some of the abstracts for my assigned articles haven't even mentioned what I consider the most significant features of the article.

Since indexes (like EBSCO) may end up indexing abstracts and not full text (and even full text indexes may weigh abstracts more highly), the abstract should probably include any important terms that should 'hit' on the article, such as key technologies or concepts.

I've found that extracting sentences or clauses from the article itself is a good way to build an abstract that will represent the article as the authors intended. The conclusion section is often a good place to look for such key sentences/clauses.

Final abstracts should be passed by the authors for approval.

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

<pre><a href="http://journal.code4lib.org/coins">(COinS)</a></pre>

This is so the user without a browser extension will see that something is there she might be interested in, and get an explanation of COinS and how to make use of it.

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

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

==Author Information==

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

End each article with a second-level header that says "About the Author(s)", with class="abouttheauthor" set. Then give a short paragraph about each author. We do want to have some kind of contact information published (personal web page, email address (obscured if desired), etc.) for each author.

There is a box beneath the article-editing box with the label "Author(s)". Anything you put in this field will be treated as the author of the article. This will show up in the ToC and in the syndication feeds. If you don't populate this field, WordPress will use the username of the editor, instead.

==Categories/Tags==
Posts will have "Uncagetorized" checked by default. Uncheck that box, and check the box next to the current issue, which will be a subcategory of "Issues." Do not check the "Issues" category. We generally do not add tags, except for Conference reviews

==WordPress Buttons==

;Save
:Saves the article, sets the post status to whatever option is selected in the Publish Status form.
;Publish
:Saves the article, sets the post status to Pending Review and assigns a timestamp to the article.

If an issue is not yet published, setting the post status to "Published" or clicking the "Publish" button will set the article to "Pending Review" status. If the issue is already published, this would actually publish the article.

==WordPress Post Status==
An article has four possible statuses. However, only the first three statuses are available to editors.
;Draft
:Use for not yet complete articles. Only editors can see these.
;Pending Review
:Use for sharing the article with authors. Editors and anyone logged in with user ID 17 (i.e., the author account) can see these. See this [http://groups.google.com/group/c4lj-articles/browse_thread/thread/1231b06c09f1289f post] on c4lj-articles for the login information for the author account (username: author).
;Private
:We don't use this option anymore.
;Published
:A published post is visible to everyone. It is part of the RSS feed. If you're editing an already published post, don't select anything in the post status form, just hit Save.

==Publishing an Issue==

# Let everyone on the c4lj-articles list know you are getting ready to publish (so they can save and close any open articles).
# Log in to WordPress
# Make sure that all articles for the issue have the correct issue category selected and have been set to 'Pending Review'. Make sure that the "Uncategorized" and "Issues" categories are unchecked (only the specific issue should be selected).
# Sanity check: count the number of posts which should appear in the publish list
# Click on Posts -> Issues (on the left side)
# Click on "Publish" for the issue you'd like to publish.
## You'll get a list of every "Pending Review" article in that issue. Make sure the number of articles in the list matches your previous count. Don't see all the articles you think you should see? They could be still in Draft status, or not in the correct Issue category, or still have "Uncategorized" selected, or someone may still have it in edit mode. Go back to the posts list and make any necessary changes, and start from #5 again.
# Drag and drop the article titles until they're in the order you want. The order you see there is the order you'll see on the home page (and probably the opposite of the order you'll see in your feed reader).
## Note: It's the coordinating editor's responsibility to decide what order he or she would like the articles to show up in, and order them appropriately when publishing the issue. In general, we try to put the articles with the widest appeal first, and special types (columns, special reports, book reviews, etc.) at the end.
# Click on Posts -> Categories (on the left side)
# Make sure all three fields for the current issue are filled in and correct:
## The human-readable name of the issue goes into the Name field -- e.g., "Issue 15".
## The date of publication goes into the Description field -- e.g., "2011-10-31".
## The URL name goes into the Slug field -- e.g., "issue15" would give the URL of the issue, http://journal.code4lib.org/issues/issue15
# Click "Publish Issue" (optionally setting the publication time, first). Setting the time should only have an impact on readers who are not logged into the c4lj site. Editors will be able to see the published articles.
# Go to the Journal front page; check the number of articles is correct (again) and that they are in the right order. If there is a problem, go back to the admin interface, click on Posts -> Issues and click Unpublish for the issue. Make whatever corrections are needed and proceed from #5 again.
# Once the issue is finally published, go to [[Code4Lib_Journal_Entries_in_Directory_of_Open_Access_Journals]] and follow the directions to upload the issue metadata to DOAJ.
# Send out announcements (see [[Code4Lib_Journal_Publicity_Venues]])

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

[[Category:Code4Lib Journal]]

Code4Lib Journal WordPress Input Guidelines

2012-12-18T11:49:57Z

Tomkeays: /* Code Highlighting */

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

==The WP Admin Interface==
To get to WordPress interface for entering an article, choose 'Site Admin' from the footer of any Journal page, login if necessary, and then choose Write//Write Post from the WP admin menus. (Alternatively, go to http://journal.code4lib.org/wp-admin/). If you don't have a WordPress editor login and need one, talk to our web admin (Jon Brinley).

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

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

==Article Content==
The body of the article goes in the "Post" field. The top-level header (<code><h1></code>) is used for the title of the post, so start with second-level headers (<code><h2></code>) for sections of the article. Any header from second- to sixth-level may be used as appropriate. Use HTML markup appropriately and semantically, ''e.g.'', <code><em></code> for emphasized text, <code><strong></code> for strongly emphasized text, <code><blockquote></code> when quoting blocks of text. Avoid such monstrosities as <code><font></code> and <code><blink></code>.

===Pasting from Word===

If you just paste content from Word into WP, it ends up with REALLY BAD html. Fortunately, WP has a built-in feature to help with this. Open the 'advanced toolbar' in editing GUI (right-most link), then click on the paste-from-word icon. This transforms Word's html into really nice pretty html.

===Images and Attached Content===
In-line images should be no wider than 500px.

The caption for an image should be entered in a p with class="caption":
<nowiki><p class="caption">Figure 1. How to Caption an Image.</p>
</nowiki>
In general, we bold the figure / table label using the strong tag:
<nowiki><p class="caption"><strong>Figure 1.</strong> How to Caption an Image.</p>
</nowiki>

'''Uploading files manually'''

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

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

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

in there you'll find an "issue1" subdir (or issueX subdir--if you don't, create one or ask for help creating one!). Inside THERE, create a subdir with the last name of the first author, and put all your image and other attached content in there. It will now have this sort of url:
http://journal.code4lib.org/media/issue1/smith/imagename.png

Add to your img src or a href's as desired. You can use this not just for images, but for extended code attachments, etc. (see below)

'''Uploading media via WordPress'''

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

==== Video ====

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

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

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

===Code===

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

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

Put all inline code in <code><pre></code> tags.

====Code Highlighting====

If the code is in a supported language, we can do syntax highlighting.

ibiblio has a PHPS extensionm, so if you an "s" on the end of .php files, e.g.,
<filename>.phps
it does syntax highlighting for you.

We're still deciding if we like the syntax highlighting, don't feel compelled to make it work if it's not working for you (but please let other editors know what your experience is). Around your code, include
[sourcecode language='langcode']...[/sourcecode]

Replace <code>langcode</code> with the appropriate code from the following list (if more than one option for a language, any one will work).

{|
!Language!!Code
|-
|C++||cpp, c, c++
|-
|C#||c#, c-sharp, csharp
|-
|CSS||css
|-
|Delphi||delphi, pascal
|-
|Java||java
|-
|JavaScript||js, jscript, javascript
|-
|PHP||php
|-
|Python||py, python
|-
|Ruby||rb, ruby, rails, ror
|-
|SQL||sql
|-
|VB||vb, vb.net
|-
|XML/HTML||xml, html, xhtml, xslt
|}

Example:
[sourcecode language='css']body {
font-size: 0.625em;
background-color: #0000ff;
color: #ffff00;
}[/sourcecode]

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

==Abstract==

While you are editing the article, there is a box labeled "Optional Excerpt" a little ways below the "Post" field. Put the abstract here. Use HTML markup as appropriate. What you put in this field is what will be distributed in our syndication feed and what will appear before the article as the abstract.

Assigned editors are ultimately responsible for a good abstract. Authors aren't always the best at writing good abstracts for their articles, you should probably revise or even write a new one from scratch as necessary, even when the author has provided one. Some of the abstracts for my assigned articles haven't even mentioned what I consider the most significant features of the article.

Since indexes (like EBSCO) may end up indexing abstracts and not full text (and even full text indexes may weigh abstracts more highly), the abstract should probably include any important terms that should 'hit' on the article, such as key technologies or concepts.

I've found that extracting sentences or clauses from the article itself is a good way to build an abstract that will represent the article as the authors intended. The conclusion section is often a good place to look for such key sentences/clauses.

Final abstracts should be passed by the authors for approval.

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

<pre><a href="http://journal.code4lib.org/coins">(COinS)</a></pre>

This is so the user without a browser extension will see that something is there she might be interested in, and get an explanation of COinS and how to make use of it.

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

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

==Author Information==

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

End each article with a second-level header that says "About the Author(s)", with class="abouttheauthor" set. Then give a short paragraph about each author. We do want to have some kind of contact information published (personal web page, email address (obscured if desired), etc.) for each author.

There is a box beneath the article-editing box with the label "Author(s)". Anything you put in this field will be treated as the author of the article. This will show up in the ToC and in the syndication feeds. If you don't populate this field, WordPress will use the username of the editor, instead.

==Categories/Tags==
Posts will have "Uncagetorized" checked by default. Uncheck that box, and check the box next to the current issue, which will be a subcategory of "Issues." Do not check the "Issues" category. We generally do not add tags, except for Conference reviews

==WordPress Buttons==

;Save
:Saves the article, sets the post status to whatever option is selected in the Publish Status form.
;Publish
:Saves the article, sets the post status to Pending Review and assigns a timestamp to the article.

If an issue is not yet published, setting the post status to "Published" or clicking the "Publish" button will set the article to "Pending Review" status. If the issue is already published, this would actually publish the article.

==WordPress Post Status==
An article has four possible statuses. However, only the first three statuses are available to editors.
;Draft
:Use for not yet complete articles. Only editors can see these.
;Pending Review
:Use for sharing the article with authors. Editors and anyone logged in with user ID 17 (i.e., the author account) can see these. See this [http://groups.google.com/group/c4lj-articles/browse_thread/thread/1231b06c09f1289f post] on c4lj-articles for the login information for the author account (username: author).
;Private
:We don't use this option anymore.
;Published
:A published post is visible to everyone. It is part of the RSS feed. If you're editing an already published post, don't select anything in the post status form, just hit Save.

==Publishing an Issue==

# Let everyone on the c4lj-articles list know you are getting ready to publish (so they can save and close any open articles).
# Log in to WordPress
# Make sure that all articles for the issue have the correct issue category selected and have been set to 'Pending Review'. Make sure that the "Uncategorized" and "Issues" categories are unchecked (only the specific issue should be selected).
# Sanity check: count the number of posts which should appear in the publish list
# Click on Posts -> Issues (on the left side)
# Click on "Publish" for the issue you'd like to publish.
## You'll get a list of every "Pending Review" article in that issue. Make sure the number of articles in the list matches your previous count. Don't see all the articles you think you should see? They could be still in Draft status, or not in the correct Issue category, or still have "Uncategorized" selected, or someone may still have it in edit mode. Go back to the posts list and make any necessary changes, and start from #5 again.
# Drag and drop the article titles until they're in the order you want. The order you see there is the order you'll see on the home page (and probably the opposite of the order you'll see in your feed reader).
## Note: It's the coordinating editor's responsibility to decide what order he or she would like the articles to show up in, and order them appropriately when publishing the issue. In general, we try to put the articles with the widest appeal first, and special types (columns, special reports, book reviews, etc.) at the end.
# Click on Posts -> Categories (on the left side)
# Make sure all three fields for the current issue are filled in and correct:
## The human-readable name of the issue goes into the Name field -- e.g., "Issue 15".
## The date of publication goes into the Description field -- e.g., "2011-10-31".
## The URL name goes into the Slug field -- e.g., "issue15" would give the URL of the issue, http://journal.code4lib.org/issues/issue15
# Click "Publish Issue" (optionally setting the publication time, first). Setting the time should only have an impact on readers who are not logged into the c4lj site. Editors will be able to see the published articles.
# Go to the Journal front page; check the number of articles is correct (again) and that they are in the right order. If there is a problem, go back to the admin interface, click on Posts -> Issues and click Unpublish for the issue. Make whatever corrections are needed and proceed from #5 again.
# Once the issue is finally published, go to [[Code4Lib_Journal_Entries_in_Directory_of_Open_Access_Journals]] and follow the directions to upload the issue metadata to DOAJ.
# Send out announcements (see [[Code4Lib_Journal_Publicity_Venues]])

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

[[Category:Code4Lib Journal]]

One recommended tool/resource for n00bs

2012-11-15T21:16:02Z

Tomkeays: /* Software */

===One recommended tool/resource for n00bs===

These resources/tools were recommended by the Code4Lib community in Nov. 2012, specifically for new coding librarians and library coders. The whole thread of discussion is available at [http://www.mail-archive.com/code4lib@listserv.nd.edu/msg15762.html the C4L listserv archive].

Please fill out a [https://docs.google.com/spreadsheet/viewform?formkey=dHNPVWgyX0E2a20xWHBHS1dJV05Pb0E6MQ#gid=0 mini-survey] if this was helpful to you. Thank you!

====Tools/Resources====

=====Books or Things to read=====
* O'Reiley Head first series
*Visual QuickStart Guides http://www.peachpit.com/imprint/series_detail.aspx?ser=335245
*[https://docs.google.com/spreadsheet/ccc?key=0AlVSWa90m8umdGg3U0h4bjdMT0ttVUJBU3RCaUc0WGc#gid=0 QA Collection Purchases for Code4Lib]
* The top 9 in a hacker's bookshelf: http://grokcode.com/11/the-top-9-in-a-hackers-bookshelf/
* "How to Design Programs" http://www.ccs.neu.edu/home/matthias/HtDP2e/. Good for newbie coders.
* Kernighan and Ritchie's [http://www.worldcat.org/title/c-programming-language/oclc/17650642 "The C Programming Language."] A keeper for life, and surprisingly readable and directed to the newbie. Also [http://www.worldcat.org/title/pragmatic-programmer-from-journeyman-to-master/oclc/42038638 "The Pragmatic Programmer"] by Andrew Hunt and David Thomas.
* http://www.w3.org/International
* Guide for the Perplexed on the code4lib wiki: http://wiki.code4lib.org/index.php/A_Guide_for_the_Perplexed
* Video series on command line basics from Lullabot: http://drupalize.me/series/command-line-basics-series

=====Software=====

* Vi- because it keeps me (you?) focused.
* [http://www.activestate.com/komodo-edit Komodo Edit]
*AMP (LAMP, WAMP, MAMP) stacks for an easy install of Apache, mySQL + perl/ python / php.
*A @rdio subscription. :) And a text editor with syntax highlighting.
* Git or Github
* Emmet, http://docs.emmet.io/ (supersedes Zen Coding, http://code.google.com/p/zen-coding/ ) The idea is that it lets you use CSS-like selectors as tags that can be expanded into full HTML snippets.
* LESS http://lesscss.org/
* BareBones's [http://www.barebones.com/products/bbedit/index.html BBEdit]
* Sublime Text & Zen Coding (recently reborn as [http://docs.emmet.io Emmet]). Saves a lot of keystrokes when writing web content.
* The best one IMHO is [http://www.sublimetext.com Sublime Text 2]. Oh, okay, I can't resist - I'm going to cheat and list a second: everyone needs to stop writing just CSS and complement it with SASS (syntactically awesome stylesheets) & Compass - http://sass-lang.com/. Totally invaluable for any front-end work. It makes CSS fun.
* [http://www.virtualbox.org VirtualBox] to make new VM setup and deployment easier we use [http://vagrantup.com/ Vagrant]
* Version control. My own strong preference is for git (either managed locally or through github.com), but really, just pick a version control solution and use it. If you value your work at all, it should be in version control. Smart use of version control can make finding and fixing problems in code much, much easier - but even fairly naive use of it leaves you with much, much better tools for fixing screw ups than you have without it.

=====Websites=====
*Code4Lib listserv, IRC, [http://journal.code4lib.org journal] (duh)
* Google is more useful than any reference book to find answers to programming problems.
* [http://stackoverflow.com StackOverflow] is a great site for questions.
*[http://lynda.com lynda.com]
*JS Fiddle http://jsfiddle.net/
*[http://stackexchange.com/ StackExchange] (by extension, StackOverflow and [http://libraries.stackexchange.com/ the Libraries StackExchange] site).

=====Other=====

*Resources for lots of languages: [http://pear.ly/8ohL pear.ly/8ohL]
* [http://catcode.pbworks.com/w/page/49680175/Resources Catcode]
* Local communities of ruby, python users.
* FOSS4lib http://foss4lib.org/
* I can already feel the collective rolling of eyes for this, but what about Twitter? It's not a guide or manual, but start following and engaging talented developers and library geeks on Twitter and you'll soon have more help than you know what to do with. Plus, no Zoia ;)
*Practice! No matter the learning material, nothing will really sink in unless you apply it in the wild (like a small project).
* It's still useful to learn a little something about configuring a webserver / database / etc.

=====Advice on what to do=====
*Building things that help people matters, and for that you need empathy.
* Reusing people's [http://dotfiles.github.com/ public dotfiles],my favorite being [https://github.com/mathiasbynens/dotfiles Mathias Bynens']. Using a mature dotfiles collection can help bootstrap you to use the command line more and start grabbing vital tools from package managers like Homebrew or npm that you might not think of otherwise. I'm still a newbie coder but reusing dotfiles gives me the confidence to tweak things here and there without building a ton from scratch.
* I'm taking "tool" to mean a piece of hardware. I'd recommend some old laptop with your favorite linux distro less desktop. Why? Well the main thing is that it puts them into a position where they're not learning to be a google copy/paste coder given the lack of the desktop, mouse and distractions like email. They can also learn to setup the server environment on their new dev box and eventually do all sorts of cool stuff.
* A cheapie online webhosting account - like a $10 a month one - and multiple URLs. Multiple URLs will make them point a URL at a nameserver at least once ideally, and to understand that the two are separate and what you can do with domains and subdomains. The cheapie webhosting account will let them play with installing popular content management systems manually and with one-click installs. The most important thing is to break things and then rebuild them. The worst possible thing would be to build a website, leave it up as their public face or personal website, and be nervous to wreck it so notchange or play with different CMSes (another reason multiple URLs might psychologically be better - they encourage experimentation on one and the person can make the other a static goal oriented publishing area).The more the cheapie hosting account experience I have, the more I know what's cheap and easy to do, and the more I see very specific benefits to adedicated server. It makes me more intentional and able to better assess the value of services vendors provide. That's more web4lib ish, but ultimately if someone experiments enough they have to get comfortable with php. Scripting is the gateway drug.
* +1 to web-hosting as it gives the ability install one's own software on one's domain (which feels great) *and* easy access to shell. And when web-hosting feels like too much of a barrier to access, sites like jsfiddle where you can immediately start adding *and* sharing code is key. IMHO the initial appeal of [http://www.codecademy.com/ Codecademy] was that it removed all barriers to getting started. Getting a laptop's localhost set up is too daunting for a first step, I think.

One recommended tool/resource for n00bs

2012-11-15T21:14:57Z

Tomkeays: /* Software */

===One recommended tool/resource for n00bs===

These resources/tools were recommended by the Code4Lib community in Nov. 2012, specifically for new coding librarians and library coders. The whole thread of discussion is available at [http://www.mail-archive.com/code4lib@listserv.nd.edu/msg15762.html the C4L listserv archive].

Please fill out a [https://docs.google.com/spreadsheet/viewform?formkey=dHNPVWgyX0E2a20xWHBHS1dJV05Pb0E6MQ#gid=0 mini-survey] if this was helpful to you. Thank you!

====Tools/Resources====

=====Books or Things to read=====
* O'Reiley Head first series
*Visual QuickStart Guides http://www.peachpit.com/imprint/series_detail.aspx?ser=335245
*[https://docs.google.com/spreadsheet/ccc?key=0AlVSWa90m8umdGg3U0h4bjdMT0ttVUJBU3RCaUc0WGc#gid=0 QA Collection Purchases for Code4Lib]
* The top 9 in a hacker's bookshelf: http://grokcode.com/11/the-top-9-in-a-hackers-bookshelf/
* "How to Design Programs" http://www.ccs.neu.edu/home/matthias/HtDP2e/. Good for newbie coders.
* Kernighan and Ritchie's [http://www.worldcat.org/title/c-programming-language/oclc/17650642 "The C Programming Language."] A keeper for life, and surprisingly readable and directed to the newbie. Also [http://www.worldcat.org/title/pragmatic-programmer-from-journeyman-to-master/oclc/42038638 "The Pragmatic Programmer"] by Andrew Hunt and David Thomas.
* http://www.w3.org/International
* Guide for the Perplexed on the code4lib wiki: http://wiki.code4lib.org/index.php/A_Guide_for_the_Perplexed
* Video series on command line basics from Lullabot: http://drupalize.me/series/command-line-basics-series

=====Software=====

* Vi- because it keeps me (you?) focused.
* [http://www.activestate.com/komodo-edit Komodo Edit]
*AMP (LAMP, WAMP, MAMP) stacks for an easy install of Apache, mySQL + perl/ python / php.
*A @rdio subscription. :) And a text editor with syntax highlighting.
* Git or Github
* Emmet, http://docs.emmet.io/ (supersedes Zen Coding, http://code.google.com/p/zen-coding/ ) The idea is that it lets you use CSS-like selectors as tags that can be expanded into full HTML snippets.
* LESS http://lesscss.org/
* BareBones's [http://www.barebones.com/products/bbedit/index.html BBEdit]
* Sublime Text & Zen Coding (recently reborn as [http://docs.emmet.io Emmet]). Saves a lot of keystrokes when writing web content.
* The best one IMHO is [http://www.sublimetext.com Sublime Text 2]. Oh, okay, I can't resist - I'm going to cheat and list a second: everyone needs to stop writing just CSS and complement it with SASS (syntactically awesome stylesheets) & Compass - http://sass-lang.com/. Totally invaluable for any front-end work. It makes CSS fun.
* [www.virtualbox.org VirtualBox] to make new VM setup and deployment easier we use [http://vagrantup.com/ Vagrant]
* Version control. My own strong preference is for git (either managed locally or through github.com), but really, just pick a version control solution and use it. If you value your work at all, it should be in version control. Smart use of version control can make finding and fixing problems in code much, much easier - but even fairly naive use of it leaves you with much, much better tools for fixing screw ups than you have without it.

=====Websites=====
*Code4Lib listserv, IRC, [http://journal.code4lib.org journal] (duh)
* Google is more useful than any reference book to find answers to programming problems.
* [http://stackoverflow.com StackOverflow] is a great site for questions.
*[http://lynda.com lynda.com]
*JS Fiddle http://jsfiddle.net/
*[http://stackexchange.com/ StackExchange] (by extension, StackOverflow and [http://libraries.stackexchange.com/ the Libraries StackExchange] site).

=====Other=====

*Resources for lots of languages: [http://pear.ly/8ohL pear.ly/8ohL]
* [http://catcode.pbworks.com/w/page/49680175/Resources Catcode]
* Local communities of ruby, python users.
* FOSS4lib http://foss4lib.org/
* I can already feel the collective rolling of eyes for this, but what about Twitter? It's not a guide or manual, but start following and engaging talented developers and library geeks on Twitter and you'll soon have more help than you know what to do with. Plus, no Zoia ;)
*Practice! No matter the learning material, nothing will really sink in unless you apply it in the wild (like a small project).
* It's still useful to learn a little something about configuring a webserver / database / etc.

=====Advice on what to do=====
*Building things that help people matters, and for that you need empathy.
* Reusing people's [http://dotfiles.github.com/ public dotfiles],my favorite being [https://github.com/mathiasbynens/dotfiles Mathias Bynens']. Using a mature dotfiles collection can help bootstrap you to use the command line more and start grabbing vital tools from package managers like Homebrew or npm that you might not think of otherwise. I'm still a newbie coder but reusing dotfiles gives me the confidence to tweak things here and there without building a ton from scratch.
* I'm taking "tool" to mean a piece of hardware. I'd recommend some old laptop with your favorite linux distro less desktop. Why? Well the main thing is that it puts them into a position where they're not learning to be a google copy/paste coder given the lack of the desktop, mouse and distractions like email. They can also learn to setup the server environment on their new dev box and eventually do all sorts of cool stuff.
* A cheapie online webhosting account - like a $10 a month one - and multiple URLs. Multiple URLs will make them point a URL at a nameserver at least once ideally, and to understand that the two are separate and what you can do with domains and subdomains. The cheapie webhosting account will let them play with installing popular content management systems manually and with one-click installs. The most important thing is to break things and then rebuild them. The worst possible thing would be to build a website, leave it up as their public face or personal website, and be nervous to wreck it so notchange or play with different CMSes (another reason multiple URLs might psychologically be better - they encourage experimentation on one and the person can make the other a static goal oriented publishing area).The more the cheapie hosting account experience I have, the more I know what's cheap and easy to do, and the more I see very specific benefits to adedicated server. It makes me more intentional and able to better assess the value of services vendors provide. That's more web4lib ish, but ultimately if someone experiments enough they have to get comfortable with php. Scripting is the gateway drug.
* +1 to web-hosting as it gives the ability install one's own software on one's domain (which feels great) *and* easy access to shell. And when web-hosting feels like too much of a barrier to access, sites like jsfiddle where you can immediately start adding *and* sharing code is key. IMHO the initial appeal of [http://www.codecademy.com/ Codecademy] was that it removed all barriers to getting started. Getting a laptop's localhost set up is too daunting for a first step, I think.

Code4Lib Style Guide

2012-10-16T14:32:35Z

Tomkeays: /* Code */

== Start of Article ==

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

== Headings ==

Use H2 for main section headings, H3 for sub-sections, H4 if you need a lower level. H2 are in "Title Case" -- all words capitalized, short words (the, a, in, up, over, about) should not be. H3 and H4 are in "Sentence case" -- only the first word is capitalized.

== Figures & Tables ==

Figures and tables are centered, placed inside a P or DIV with class of "caption". For example:

<pre>
<p class = "caption">
<img src = "....">
<strong>Caption for Figure</strong>
<p>

<div class = "caption">
<table>
<tr>...</tr>
</table>
</div>
</pre>

Captions for figures appear beneath the figure, centered, with "Figure X:" in bold, the descriptive text in sentence case, plain text.

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

== Code ==

Code samples entered as preformatted text, as in the following example, are automagically color highlighted in Wordpress by the [http://wordpress.org/extend/plugins/syntaxhighlighter/ SyntaxHighlighter] plugin:

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

Supported formats include <tt>cpp, c, c++, c#, c-sharp, csharp, css, delphi, java, js, jscript, javascript, pascal, php, py, python, rb, ruby, rails, ror, sql, vb, vb.net, xml, html, xhtml, and xslt</tt>. Pretty much everything except <tt>perl</tt>.

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

== End of Document ==

=== Recommended Reference Style Discussion: ===

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

=== Endnote & Endnote References ===

A Bibliography and Notes section (if needed) immediately follows the last of the article's narrative text. References are indicated by author and year (Smith, 2007). Notes are indicated in the text either by note number in square brackets [1].

Bibliographies are recommended to follow CSE reference style. An author may choose to use a different bibliographic reference style, but should follow that style accurately.

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

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

=== About the Author ===

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

=== Appendices ===

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

[[Category: Code4Lib Journal]]

2012 c4l2012 social activities

2012-02-07T19:45:07Z

Tomkeays:

==Ideas==
* Woodinville distillery tour
** +1
* Seattle distillery tour
* Favorite local breweries
* Favorite local tea houses
* Favorite local used bookstores
* Visit hackerspace
** +1

==Planned events==

===Pre-Newcomer + Veterans dinner /drink-up Monday===
Early in town for pre-conference?
First time at code4lib?
Don't know anyone at code4lib?
Join fellow c4l newbies + 2nd + 3rd timers + veterans.
You will gain a bunch of new/veteran code4libbers in one night!
Sign up below (NO CAP). You can show up only for dinner or drinks or both!

But put your name so that we have a rough idea about the number of ppl who will show up =)

'''Plans'''
* When: Monday evening (2/6)
* For Dinner: Meet at 6PM (ish)at the hotel lobby
* For Drinks: show up at Hideout between 8 -10 PM for local art, fancy cocktails, or Belgian beer
* For Hospitality suite intro chat/hangout: show up at 10 PM - midnight? at hospitality suite

Dinner: [http://www.yelp.com/biz/kastoori-grill-seattle Kastoori Grill -Indian & Himalayan/Nepalese/Tibetan (vegetarian-friendly)]
0.8 miles 15 min. walk
* Bohyun Kim - n/v (2nd-timer) (leader)
* Jason Clark - n/v leader
* Margaret Heller
* Sarah Johnston - n
* Andrea Schurr - n/v (2nd-timer)
* Jason Ronallo
* Karen Coombs - v
* Eric James
* Misty De Meo - n
* Keri Thompson - n
* Andreas Orphanides - v
* Tom Burton-West -v
* Keith Folsom - n
* Sam Meister - n
* Jen Weintraub - n
* Reservation made for 15. Bring cash if you can! =)

Drinks: [http://www.yelp.com/biz/the-hideout-seattle Hideout Lounge] for local art, fancy cocktails, and Belgian beer
0.3 miles 8 min. walk
* Bohyun Kim - n/v (2nd-timer) (leader)
* Jason Clark - n/v leader
* Lisa Kurt - n
* Margaret Heller
* Andrea Schurr - n/v (2nd-timer)
* Anoop Atre (Would love to if back from MS visit)
* Heather Pitts (maybe) - n
* Evviva Weinraub - Hope to join up if back from MS visit)
* Megan Banasek -n
* Misty De Meo (maybe) - n
* Keri Thompson (definitely)
* David Drexler (likely) - n
* Andreas Orphanides - v
* Rebecca Jones - n
* Chick Markley - v
* Ray Henry - n
* Jonathan Green (likely) - n
* Aaron Collier - n
* Tim Lepczyk - n

Hospitality suite intro chat/ hangout: just show up at the hospitality suite - no sign up required.

===Morning Run Tuesday===
I (Ray Schwartz) am organizing a morning run for anyone that would like to join me. It will be around 5 to 6 miles. I usually run a 10 minute per mile pace. And I would like to start around 7am. Select which days Tuesday or Wednesday or both mornings. Choose the date you wish via this Doodle link http://www.doodle.com/3tbigutqvkda5ib8

Link to the course map is at http://www.runningmap.com/?id=351428.

So far 4 have signed up for both Tuesday and Wednesday. Let's meet in the Lobby at 7am on Tuesday, and we will decide how to do Wednesday.

===Newcomer dinner Tuesday===
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> XML.

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

'''Plans'''
* When: Tuesday evening (2/7) '''Note that this year's dinner is on Tuesday'''
* 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 :(
*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 coders
***Herd folks from hotel to restaurant (know where you're going!)

'''Restaurants'''

'''Restaurants within .25 miles of the hotel'''

[http://www.sazeracrestaurant.com/index.php Sazerac] (AWESOME happy hour menu that runs until 8)
* Martin Haye - n (2nd timer but it's been a ''long'' time)
* William Gunn - n
* Rebecca Jones - n
* Chick Markley - v - leader?
* Keri Thompson - n
*'''capped at 6''' ''(So, who's the fearless leader of this group? ~yo_bj)''

[http://oasiankitchen.com/ O'Asian Kitchen and Lounge] (Asian)

'''Restaurants between .25 miles and .5 miles of the hotel'''

[http://www.pikebrewing.com/index_html.shtml Pike Brewing] (local brewery, pub food)
* Ken Varnum - n
* Chad Nelson - n
* Ed Summers - v
* Tommy Ingulfsen - n
* Adam Wead - v or .5n
* Dan Coughlin - n
*'''capped at 6''' ''(So, who's the fearless leader of this group? ~yo_bj)''

[http://www.rockbottom.com/ The Rock Bottom Restaurant & Brewery] (American)
It seemed like all the others were full so I thought it start this in case anyone else is as crazy unprepared as I am.
* Jonathan Green - n
* Ed Fugikawa ( ed AT coalliance DOT org ) - n
* Zinthia Briceno - n (@zbriceno)
* David Talley - n ( dwtalley AT uw DOT edu ) -- Where to meet? Hotel main entrance, 6pm?
* Patrick Berry - v (@pberry) -- Lobby at 6pm sounds perfect. I'm the short blonde guy. I guess I will "lead" our merry band of famished folk.
* Al Cornish - v
* Tom Keays - v
* ''Any veterans want to come along?''

[http://www.wildginger.net/ Wild Ginger] (Asian, a bit overpriced) "Reservations made under Jason Clark at 6pm for 6 people. Meeting in hotel lobby around 5:45pm."
* Jason Clark - n/v leader
* Tamar Sadeh - n
* Kevin Clarke - v
* Gary Thompson - n
* Keith Folsom - n
* Sarah Park - n (my Seattle friend recommended this place!)

[http://www.thepurplecafe.com/index.html Purple Cafe] (American, Wine Bar) ''reservation made under Calvin Mah for 6:30pm for the 6 of us. I'll be meeting in the hotel lobby at 6pm with some sort of sign. See you then!''
* Calvin Mah - (leader) - v
* David Isaak - n
* Aaron Collier - n
* Sean Hannan - v
* Joshua Gomez - v
* Charlie Morris - n
* '''capped at 6'''

[http://www.cafepaloma.com/ Cafe Paloma] (Mediterranean) Reservation for 6:15 -- Meet in hotel lobby at 6 -- I have short white hair and will be wearing a purple jacket.
* Jean Rainwater (leader) - v
* Kelley McGrath - n
* Lori Robare - n
* Emily Lynema - v
* Sarah Johnston - n
* Sam Meister - n
* '''capped at 6'''

[http://www.thecollinspub.com/ Collins Pub] (Pub Food, great beer selection)
* Francis Kayiwa - (leader) "(get hold of me at first dot last name at goog as the date gets closer with your mobile)" v
* Michael Lindsey - v
* Dan Suchy - v
* David Drexler - n
* Laura Smart - n
* Heather Pitts - n
*'''capped at 6'''

[http://www.mcmenamins.com/311-six-arms-home Six Arms - McMenamins] (Pub Food & they brew their own beer) ''Meet in the Lobby at 6pm. I've also emailed you. --Joel''
* Joel Richard (richardjm AT si.edu) (leader) - v
* Margaret Heller - v
* Sibyl Schaefer (sschaefer AT rockarch . org) - v
* Tim Lepczyk (timlepczyk AT gmail.com) - n
* Ray Schwartz (schwartzr2@wpunj.edu) - v
* Andrea Schurr (andrea-schurr AT utc DOT edu) - v(2nd-timer)
* '''capped at 6'''

[http://www.611supreme.com/ 611 Supreme] (Crepes and Full Bar) ''Reservation for 6 at 6:30. Meet in the conference hotel lobby at 6pm. Look for the short woman in a trench coat and wide brim hat ~Becky''

*Becky Yoose (leader) - v
*Cynthia Ng - n
*Zoe Chao - v
*Stephanie Collett - n (2nd-timer)
*Bethany Nowviskie - n
* Ben Shum - n
*'''capped at 6'''

[http://www.panafricamarket.com/wp/ Pan Africa Restaurant & Bar] (Pan African)
CLOSED TUESDAYS!!!!!!!!!!!!!!!!!!
Sorry for the confusion. I have moved everyone to Long Provincial, so that you'll have a place held in case you want it. If Long Provincial doesn't suit you, please remove your name in case someone else wants the spot. Again, I'm sorry. --Jason

[http://longprovincial.com/ Long Provincial] Vietnamese (.7 miles from hotel; 15 minute walk)

Reservation for 6 for 6:30 (and I have a confirmation number!). Meet in the hotel lobby at 6 to allow for a strolling pace to walk over there.

Has a jellyfish tank.

*Jason Ronallo (leader?) - v?
*Nettie Lagace - n
*Bohyun Kim - n/v (2nd-timer)
*Wendy Robertson - n
*Jennifer Bowen - n/v (3rd timer)
*James Stuart - n
*'''capped at six'''

'''Restaurants between .5 and 1 mile from hotel'''

[http://momijiseattle.com/ Momiji] New Japanese restaurant in Seattle - [http://www.concierge.com/tools/blogs/unpacked/2011/10/momiji-seattle.html Reviewed in Concierge.com]

* Andrew Nagy (leader) - v
* Cory Lown - v
* Tod Robbins - n
* Dennis Schafroth - n
* Tammy Allgood Wolf - n*

[http://tomdouglas.com/index.php?page=palace-kitchen-dinner Palace Kitchen] (another Tom Douglas restaurant, w/ a focus on meat). ''I have made a reservation for 6 at 8pm. Let's meet in the conference lobby at 6:30pm and make our way slowly over; we will find things to do in the interim. Look for Mike Giarlo, a man who may be holding a sign that says "HI I'M MIKE GIARLO" or otherwise shouting his name or looking confused.''

* Mike Giarlo (leader) - v
* Carmen Mitchell - n
* Daniel Lovins - v
* Cary Gordon - v
* Declan Fleming - v
* Amy Unger - n
* (CAPPED AT SIX!)

[http://sitkaandspruce.com/ Sitka and Spruce] (Eclectic, super-local and super-seasonal.) ''We have a reservation for 6 at 8:15pm. We'll meet in the conference lobby at 6:30 pm and head over - the owners also run [http://www.ferdinandthebar.com/home/ Bar Ferd'nand], a wine shop/bar in the same building, and we can kill time there before we eat. Look for Mark Matienzo or Hillel Arnold.''

* Mark Matienzo (leader) - v
* Hillel Arnold - sophomore
* Devon Smith - v
* bernardo gomez - n
* Derek Merleaux - sophmore
* Jennifer Weintraub - n
* (CAPPED AT SIX!)

[http://www.yelp.com/biz/japonessa-seattle Japonessa Restaurant] (Japanese + full bar)

''Reservations for 6 at 7:00pm - Meet in lobby at 6:15''

* Ryan Wick (leader) - v
* Kate Zwaard - n
* Joe Atzberger - v
* Scott Fisher - n (2nd-timer)
* Anoop Atre - n
* Lisa Kurt - n
* '''capped at 6'''

[http://tomdouglas.com/index.php?page=serious-pie Serious Pie] (Tom Douglas restaurant, inventive pizzas, good local beer list).

''No reservations for parties at Serious Pie...So, let's meet in the lobby at 6:30. Look for a guy wearing an 'Alma' t-shirt (me). Others out there...come and crash the 'capped at six' crowd heading to Serious Pie.''

* Christopher Spalding (leader) - v
* Robin Schaaf - n
* Jason Stirnaman - v
* Christina Morris - n
* Ray Henry - n
* Sean Purcell - n
* '''capped at 6'''

[http://www.allmenus.com/wa/seattle/204592-ballet-restaurant/menu/ Ballet] (Vietnamese)

[http://www.kokebrestaurant.com/ Kokeb Ethiopian Restaurant] (Ethiopian) ''Let's say meet at the lobby at 6pm like everyone else. Woohoo!''

''We have reservations for 6 at 6:45.''

* Andreas Orphanides (leader) - v
* Mark Mounts - v
* Joe Montibello - n
* Justin Littman - n
* Ron Peterson
* Bobbi Fox - sophmore
* (CAPPED AT SIX!)
Crashing the [http://www.seattlerb.org/ Seattle Ruby] meetup, which meets on Capital Hill at 7:00 on Tuesdays. Eat at [http://www.yelp.com/biz/poppy-seattle Poppy] before. Reservations for 6:15. Leaving from the hotel lobby at 5:45. ''If you dig Ruby, come to this. Seattle ruby produced Nokogiri, Vlad, Rubygems.org ....''
* Matt Zumwalt (leader) - v
* *Justin Coyne - n
* Misty De Meo - n
* Fumihiro Kato - n (2nd timer)
* Dan Brubaker Horst - n (3nd timer)
* Willy Mene - sophomore
* (CAPPED AT SIX)

[http://tomdouglas.com/index.php?page=dahlia-lounge Dahlia Lounge] (Pacific Northwest cuisine, $$$)

[http://www.mattsinthemarket.com/ Matt's in the Market] (Northwest Cuisine, $$$)

[http://www.placepigalle-seattle.com/ Place Pigalle] (French)

[http://www.chezshea.com/ Chez Shea] (French)

[http://www.elysianbrewing.com/elysian.html Elysian Breweries and Pubs] (Pub Food)

[http://www.mezaseattle.com/index.html Meza] (Latin Fare)
Have reservations for 6.45. It's about a mile from hotel. 10min bus, 30 min walk. Meet in lobby @ 6 and we'll work out bus/walk/cab. -corey
* Tara Robertson - n
* Shawn Averkamp - sophomore
* Corey Harper - v (leader)
* Shaun Ellis - sophomore
* Jon Stroop - fifth year senior
* Birkin James Diana - v (hi Jon!; hey newcomers, I'm taking the 6th slot, but, if you're stuck for a signup, plz do feel free to bump/overwrite me - seriously!)
* '''capped at 6'''''(So, who's the fearless leader of this group? ~yo_bj)''

[http://inthebowlbistro.com/index.php In the Bowl] (Veg*n, Asian)

[http://www.plumbistro.com/ Plumb Bistro] (Veg*n)

[http://highlineseattle.com/ Highline] (Veg*n, bar)

'''Restaurants more than 1 miles from the hotel'''

[http://bravehorsetavern.com/ Brave Horse Tavern] (another Tom Douglas, good regional beer list, yummy food. Near South Lake Union. Would require a ride on the South Lake Union Trolley (SLUT), but it's easy to get to/use from downtown.

[http://www.temperodobrasil.net/ Tempero do Brasil] I was excited to see Ipanema Grill 6 blocks from the hotel, unfortunately it seems to be closed for good. So this restaurant which is a 10 minute ($15) cab ride away and which also serves Brazilian cuisine (including the ever-tasty feijoada) will have to do.
* Robert Haschart - leader - v third year
* Molly Pickral - n
* Erik Hetzner - 2nd c4l

[http://flyingfishrestaurant.com/ Flying Fish] (Seafood)

[http://www.allmenus.com/wa/seattle/3437-cafe-flora/menu/dinner/ Cafe Flora] (FANTASTIC Veg*n restaurant. Use Metro bus #11 to get there)

[http://www.teapotvegetarianhouse.com/index.htm Teapot Vegetarian House] (Veg*n, Asian)

[http://spaceneedle.com/restaurant/ Space Needle] (American, Pricy; but what the heck, listed it anyway for those who want the experience)

==="Get Lamp" viewing Tuesday (9 PM) ===

"Tuesday, February 7, 9 PM or shortly after -Courtyard Ballroom"

Adam Wead and Michael Klein are organizing a viewing of [http://www.getlamp.com/ Get Lamp: The Text Adventure Documentary]

It's not about Linux, Apache, MySQL or PHP, but if you don't have a one, you might get eaten by a grue.

If there is additional interest, there may be another viewing this week.

===Morning Run Wednesday===
I (Ray Schwartz) am organizing a morning run for anyone that would like to join me. It will be around 5 to 6 miles. I usually run a 10 minute per mile pace. And I would like to start around 7am. Select which days Tuesday or Wednesday or both mornings. Choose the date you wish via this Doodle link http://www.doodle.com/3tbigutqvkda5ib8

Link to the course map is at http://www.runningmap.com/?id=351428.

So far 4 have signed up for both Tuesday and Wednesday. Let's meet in the Lobby at 7am on Tuesday, and we will decide how to do Wednesday.

===Veg*n Dinner Wednesday===

We'll pick a place with lots of veg*n options to go eat Wednesday for dinner. Vegetarians and non-vegetarians welcome.

*[http://lovinghut.us/seattle/index.html Loving Hut] Modest price. 1 mile from hotel. Will do bill splitting if we let them know up front.

Talked with Loving Hut and made a reservation for 15 for 6:30. Meet in the hotel lobby at 6.

*Jason Ronallo (jronallo AT gmail.com)
*Sean Hannan
*Ed Summers
*James Stuart
*Bohyun Kim
*Bethany Nowviskie
*Margaret Heller
*Laura Smart
*Sibyl Schaefer
*Cynthia Ng
*Andrea Shurr
*Eric James
*Birkin James Diana
*Sheree F
*Misty De Meo
*Reservation is for 15.

===Meat-Up Dinner Wednesday===

RIP Meat-Up. Going to Amazon for hurricanes.

(if you do not find a suitable burger joint, there are also some top-notch steakhouses in Seattle. Both the Metropolitan Grill and El Gaucho are delightful if folks are OK with $50 steaks. Just FYI, not trying to hijack your meat-up, Cary!. -mjgiarlo)

===Evergreen/Koha and friends dinner Wednesday===
Put your name and any food limitations, or suggestions of places to go. We'll figure where we're going later. For now, let's assume we're meeting in the hotel lobby at 6pm.

* Tara Robertson
* Chris Sharp
* Tod Robbins - n
* Ben Shum
* Anoop Atre - n
* Matt Carlson - n
* Luis Baquera

===[[2012 Craft Brew Drinkup|Craft Brew Drinkup]], Wednesday (9 PM)===

'''Wednesday, February 8, 9 PM-ish -Hospitality Suite'''

Like good beer? Bring some in your luggage! Some of us are planning to bring some of our favorite local, special, or homebrewed beers to share. Interested? Sign up on the [[2012 Craft Brew Drinkup]] page!

===Dim Sum Lunch Thursday===

For those of you staying in town after the last session on Thursday, [http://oasiankitchen.com/ O'Asian Kitchen] has dim sum service during the weekdays. Meet up around 12:35, meeting location tba. Bring cash for easier bill splitting.

*Becky Yoose
* Declan Fleming - love me some Dim Sum!
* Adam Wead
* Heather Pitts
* Sibyl Schaefer
* Anoop Atre
* Dan Suchy
* Carmen Mitchell
* Tara Robertson
* Ray Schwartz
* Cynthia Ng
* Corey Harper
* Joshua Gomez
* Cary Gordon
* Mike Giarlo
* Joe Atzberger
* Dileshni Jayasinghe
* Ryan Wick
* Dennis Schafroth
* Mike Durbin
* Ben Shum

==Social Map - places of interest==
[http://g.co/maps/4m5pk Code4lib 2012 - Seattle - social events, hangouts, and places to see]

==Seattle Events Feb 5-9==
===Saturday, February 4, 2012===
In case you are showing up really early.
* Belgianfest: http://www.washingtonbeer.com/belgianfest/
===Sunday, February 5, 2012===
* Clinton Fearon & The Boogie Brown Band/Live Wyya/Adrian Xavier/Selecta Raiford/DJ Courtland, Neumos: http://neumos.com/neumos.php
* Michael The Blind/The Els, Skylark: http://www.skylarkcafe.com/
* Addaura/Alda/Hallow, Comet
* "I Am My Own Wife" 7:30pm at Seattle Repertory Theatre (Seattle Center) http://www.seattlerep.org/Plays/1112/IM/
* Science Fiction + Fantasy short film festival, Encore screening. http://www.empmuseum.org/programs/index.asp?categoryID=216

===Monday, February 6, 2012===
* Silent Movie Mondays: Last Command 1928, http://stgpresents.org/artists/?artist=1829#, Show at 7:00pm, The Paramount Theatre $10
This all-classic film series, First Oscars, is accompanied by live music from the historic Mighty Wurlitzer organ, one of the last three remaining organs of its kind to reside in its original environment, played by critically acclaimed organist Jim Riggs.

===Tuesday, February 7, 2012===
* Lionize/Maylene & The Sons Of Disaster, El Corazon: http://elcorazonseattle.com/
* The Pulltab Playboys/Rachel Lyn Harrington & The Knock Outs/The James Low Western Front, Sunset: http://sunsettavern.com/
* Twin Sister, Vera: http://theveraproject.org/shows/
* The Features, Chop Suey: http://www.chopsuey.com/
* Wilco/White Denim, Paramount Theatre: http://stgpresents.org/
* "I Am My Own Wife" 7:30pm at Seattle Repertory Theatre (Seattle Center) http://www.seattlerep.org/Plays/1112/IM/
* Intro to Arduino Workshop, 7pm at Metrix Create Space http://metrixcreatespace.com/

===Wednesday, February 8, 2012===
* The Golden Blondes/The Jet Age/Mr. Drinx & The Pot Heads, Sunset: http://sunsettavern.com/
* Pipsisewah/The Chasers/The Magic Mirrors, Tractor: http://www.tractortavern.com/
* Dengue Fever vs Secret Chiefs 3, Moe Bar http://bit.ly/yJtfXv (how could you pass the opportunity to see someone play this thing :http://bit.ly/wB5AgZ
* Amazon Tech in Seattle is having an open house next Wednesday at 5:30 PM with Werner Vogels and David Friedberg of the Climate Corporation. https://aws.amazon.com/amazon-open-house-february-2012/ ([http://g.co/maps/adpnt map])

===Thursday, February 9, 2012===
* SAM Opening - Gauguin and Polynesia: An Elusive Paradise: http://www.seattleartmuseum.org/gauguin
* The Jayhawks, Neptune Theater: http://stgpresents.org/
* Digital Leather, Comet
* Savani World Quintet/Super Sones, Columbia City Theater: http://www.columbiacitytheater.com/
* Blvd Park {album release}/Nettle Honey/Creeping Time, Tractor: http://www.tractortavern.com/
* Eleanor Friedberger, Crocodile: http://thecrocodile.com/index.html

===Ongoing Events===
* Seattle Art Museum: Tours are every Saturday & Sunday at noon, and the First Thursday of every month at 10:30, 11:30 am, 12:30 & 1:30 pm.
* EMP: Exhibits on display include: Battlestar Galactica, Nirvana, Avatar, and Can’t Look Away: The Lure of Horror Film
* Teatro ZinZanni: ¡Caliente! http://dreams.zinzanni.org/
* Pacific NW Ballet: performing Don Quixote at McCaw Hall http://www.pnb.org/
* Oklahoma!, Sunday matinee and nightly: 5th Avenue Theatre, 1308 Fifth Avenue http://www.5thavenue.org/show/oklahoma

==Local events/places==
* Metrix Create Space
* Ada's Technical Books
* Northwest Outdoor Center
* Center for Wooden Boats
* Empty Sea Studios acoustic music

==Local Beer Places==
* Map of [http://beermapping.com/maps/citymaps.php?m=seattle#lat=47.66723703450515&lng=-122.28263854980469&z=5 beer venues] maintained at Beermapping.com.
* List of [http://www.washingtonbeer.com/breweries/seattle-king-co/ local breweries] ([http://maps.google.com/maps/ms?hl=en&ie=UTF8&msa=0&msid=201783184139227541123.0004813e64758434cb054&source=embed&ll=47.558921,-122.106171&spn=0.442982,1.234589&z=10&source=embed map]) maintained by the Washington Beer Commission
* Map of [http://www.ratebeer.com/Places/RegionMap.asp?rid=7600 beer venues] maintained by Ratebeer.com.

==See also==
[http://orbiscascade.org/index/c4l-things-to-do-in-seattle Things to do in Seattle, from the hosts]

==Tour of the Seattle Public Library==

Tuesday breakout session 3-4pm - max 20 ppl

Meet by the coffee urns, leaving at 2:55pm (10% off at the gift shop if you mention that you are attending code4lib)

* Tara Robertson
* Bohyun Kim
* Carmen Mitchell
* Margaret Heller
* Ben Shum
* Anoop Atre
* Chris Sharp
* Cynthia Ng
* Megan Banasek
* Chris Beer
* Peter Murray
* Bobbi Fox
* Joe Montibello
* Tim Lepczyk
* Mark Mounts
* Robin Dean
* Jason Stirnaman
* Robert Haschart
* Zoe Chao
* Shawn Averkamp
* Sheree Fu
* CAPPED at 20

More tour may come later. Stay tuned!

Jeff Christensen 206-387-4659

centaltours@spl.org

Possibility for another tour tomorrow - will add signup and announce if this is possible. Jeff is trying to find someone to lead it.

==

[[Category:Code4Lib2012]]

Ideas for Code4Lib 2013

2012-02-07T17:53:27Z

Tomkeays:

Deprecate this... See [[Ideas_for_2013]]

Put you ideas here for review by the meeting hosts and planning volunteers.

*
*
*

[[Category: Code4Lib2013]]

C4l2012 rideshare

2012-02-06T02:35:07Z

Tomkeays: /* Bus distance */

=== Seattle Tacoma International Airport ===

See also [http://orbiscascade.org/index/c4l-transportation travel advice from the hosts]

'''Arrivals'''
{| border="1" cellpadding="5" class="sortable"
|- style="text-align: left;"
! Name !! Flight Arriving !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?
|-
| yourname/email|| date/time || yes/no|| yes/no || yes/no || who's the driver?||yes/no||# of people you can take
|-
|}

'''Departures'''
{| border="1" cellpadding="5" class="sortable"
|- style="text-align: left;"
! Name !! Flight Departing !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van? !! Sign-Up?
|-
| yourname/email|| date/time || yes/no|| yes/no || yes/no || who's the driver?||yes/no||# of people you can take
|-

|}

===Public Transit from the Airport===
Light Rail: The [http://www.soundtransit.org/Schedules/Central-Link-light-rail.xml Central Link Light Rail station] will be located near the northeast corner of the main airport parking garage, directly connecting pedestrians to the airport ticketing concourse and SeaTac's City Center. The light rail offers a 36-minute ride from the airport to Downtown Seattle.

Get off at the Pioneer Square station. The hotel is 7 blocks from the station (0.4 miles) and the walk includes a steep hill, so plan to take a bus, a cab, or be out of breath by the time you get to the hotel. The easiest transit connection is to walk up Third to Marion, and take the #12 up the hill. It's a free ride till 7 p.m. Trolley stops across the street (6th Ave) from the hotel.

Fare: <$3 for light rail

=== Roommates ===
==== Looking ====

==== Offering ====
* <s> [https://twitter.com/#!/skome samk] -- Have 2 double beds at the conference hotel, need only one. Human male, typically easy going.</s>
* <s> [http://therolfeblog.blogspot.com Alex Rolfe] I also have 2 double beds at the conference hotel, for the 5th-8th, and would be happy to have a roommate for all or part of it. Human male, also easygoing. Contact me at arolfe@georgefox.edu.</s>
* <s>[mailto:bobbi_fox@harvard.edu Bobbi Fox] -- Have reservation (Sunday eve. through Thurs .am.) at conference hotel, woman looking for another woman to share</s>
* <s> [mailto:tclarke@muhlenberg.edu Tim Clarke] -- I also have a reservation at the Renaissance Seattle for 2 double beds, only need one. (Sunday 3 p.m. through Friday Noon.) I expect to bring [http://victorybeer.com Victory] and [http://weyerbacher.com/ Weyerbacher] to share, so I'll seem easygoing. Please email [mailto:tclarke@muhlenberg.edu tclarke@muhlenberg.edu].</s>
* [mailto:gsf747@gmail.com Gabriel Farrell] Human male, easy going, extra double bed, conference hotel, tonight (Sunday) through Thursday.

=== Other places to stay ===
[http://www.tripadvisor.com/Hotels-g60878-Seattle_Washington-Hotels.html| TripAdvisor]
Also if anyone has suggestions.

====Nearby====
* [http://www.monaco-seattle.com/ Hotel Monaco] - .2 mi (1101 4th Avenue, Seattle, WA)
* [http://www.greentortoise.net/ Green Tortise Hostel], $28.50 - $32.50/person in shared dorm rooms - .6 mi (105 1/2 Pike St)
* [http://www.executivehotels.net/downtownseattlehotel/s_seattle_accommodation.cgi Executive Hotel Pacific] $99 (Also available a 20% discount with advance purchase - full payment upfront required) - .1 miles (400 Spring St).
** These guys have free wifi if you book the "executive" package, which is $109 (which was the only option available when I looked).
* [http://www.kimptonhotels.com/hotels/factsheets/hotel-vintage-park-seattle/ Hotel Vintage Park], $153 (king) and $143 (queen) with AAA discount. Might have government rates, not sure.

====Bus distance====
* College Inn (bus ride away)

[[Category:Code4Lib2012]]

2012 Craft Brew Drinkup

2012-02-06T02:34:45Z

Tomkeays:

'''Wednesday, February 8, after 9 PM, in hospitality suite'''

The Craft Brew Drinkup at Code4lib 2012 is all about sharing and enjoying good beer with fellow conference attendees. The idea is to bring bottles of your favorite beers.

While you're not obligated to bring ''local beers'' from whereever you're from, participants are definitely encouraged to bring beer that you think is special and might be somewhat hard for others outside your area to find. Homebrew is especially welcome. Sign up below with your name, where you're from, and list a few brews or bottles you're thinking about (but not necessarily committing to) bringing along. You can also request that people bring specific beer if you so desire, but don't necessarily expect that your wishes will be granted.

''If you do not check bags or otherwise cannot arrange to bring beer from where you call home, you may be interested in buying beer from a local beer store. See the "Buying Beer in Seattle" section below for suggestions.''

__TOC__

=== Sign up ===

{| border="1" cellpadding="5" class="sortable"
! Name
! Location
! Brews or Breweries I might bring
! Requests
|-
| anarchivist
| New Haven CT/Brooklyn NY
| '''Purchased''': Element Brewing Dark Element, Element Brewing Extra Special Oak, Olde Burnside Ten Penny Ale Reserve, Cisco Captain Swain's Extra Stout
'''Special bottles''': Who knows? Something special.
| Imperial porters/stouts; really funky-/Brett-tasting beers or wild ales; highly-hopped stuff; interesting session beers
|-
| kayiwa
| Chicago IL
| Bourbon County Stout; New Glarus Barleywine, 3 Floyds Behemoth Barleywine
| Barleywines; Aged Stouts; Anything from Deschutes
(psst, Francis: I've got some homebrewed barleywine aging in the basement; i won't be in Seattle but I'll bring some to C4L-Midwest -[[User:Kenirwin|Kenirwin]] 13:26, 29 January 2012 (PST))
|-
| danwho
| San Diego, CA
| Alpine Brewery Exponential Hoppiness; Iron Fist; maybe Lost Abbey; Bud Light
| hoppy imperials, sours, funky farmhouses. Also, I'd vote Wednesday or Tuesday evening since a lot of folks are doing the Microsoft tour and/or newcomer dinners Monday
|-
| declan
| San Diego, CA
| hmm, looking over the cellar... Parabola, Black Tuesday, Cherry Adam, Angel Share, Captain stout, Silva.... we'll see!
| dark, black stuff. like my heart. Or sours. Or Belgies. Founders, Bells, New Glaris, Goose Island.
|-
| awead
| Cleveland, OH
| Founders Porter, some new IPA I found...
| Stuff that doesn't suck.
|-
|bibliotechy
|Atlanta, Ga
|Some Terrapin beers... Hopsecutioner, Sweetwater Brewery Exodus Porter if it is still around
|Boreale noire, rousse or cuivre from Montreal!
|-
|sdellis
|Lambertville, NJ
|Riverhorse... (possibly Hop Hazard, but I'll see what's fresh). Maybe Lionshead (pilsner) from Doylestown, PA (legend has it you can drink as much as you want and never get a hangover).
|Bitters, pub style, IPAs, brown ales
|-
|jastirn
|Kansas City, KS
|Whatever I can get from Wilderness Brewing (KC), Free State (Lawrence, KS), Schlafly Imperial Stout (St. Louis), and Blvd Smokestack (KC) (for Danwho)
| More blueberry stout, stouts, lagers, spicy
|-
|HLPitts
|Salem, OR
|Hopworks barleywine, Rogue Chocolate Stout and Dead Guy, Seven Brides porter, Wandering Aengus cider, and a small variety (less small than it was yesterday...) from Deschutes (including Obsidian for anarchivist)
|stouts/porters, sours, red ales
|-
|bohyunkim
|Miami, FL
|Scotch ale and Pale ale from Oskar Blues brewery / White Rascal from Avery from in Colorado, Boulder
|cider, Rogue Dead Guy, malty, fruity, blonde/gloden ale
|-
|carmendarlene
|San Diego, CA
|something from SoCal...Maybe more Alpine. Going shopping at the Best Damn Beer Store later this week.
|New Glaris, Goose Island, Three Floyds, Cantillon...stuff that I can't get in San Diego.
|-
|flyingzumwalt & jcoyne
|Minneapolis, MN
|Surly Coffee Bender & Surly Cynic, Bell's Two Hearted, Lift Bridge Farm Girl, Crispin Cider
|Revivalist beers (ie. [http://www.yardsbrewing.com/ales_poor-richards-tavern-spruce.asp Yard's Revolutionary Beers] ), New Glarus, Yuengling
|-
|singlesoliloquy
|St. Louis, MO
|[http://www.schlafly.com/beers/styles/quadrupel/ Schlafly Quadrupel] & [http://www.schlafly.com/beers/styles/biere-de-garde/ Schlafly Biere de Garde]
|Good pilsners.
|-
|pberry
|Chico, CA
|Hope to buy Chico stuff in SEA, Bigfoot was just released.
|Ales
|-
|calvinmah
|Vancouver, Canada
|driving to SEA so I'll bring a crate
|Beer
|-
|tara robertson
|Vancouver, Canada
|two limited release beers from [http://gib.ca/beer/ Granville Island Brewing]: Fresh Hop ESP, Imperial IPA
|
|-
|younga, ward, jeff
|Seattle, WA
|Random assortment of growlers: Georgetown Brewery, Big Time, Schooner Exact, Epic Ales.
|
|-
|lrobare
|Eugene, OR
|Ninkasi, probably Total Domination and something else
|
|-
|scollett
|Seattle, WA
|Live in Berkeley, CA, but will buy local or raid the beer stash of my Seattle relatives.
|
|-
|lisapisa77
|Reno, NV
|Ichthyosaur "Icky" IPA from Great Basin and probably something else
|Alagash or Victory or brown ales
|-
|-
|chrpr
|New York, NY
|Brooklyn Sorachi Ace, Southhampton Saison, Probably some other stuff
|Sours, Farmhouse, Misc. high abv goodness...
|-
|carboy
|Arlington, TX
|Yeti, Mephistopheles
|Imperial stout, IPA, barleywine
|-
|mbaggett
|Knoxville, TN
|I won't be checking a bag, but I'll be raiding all the Seattle beer spots this weekend. I hope to surprise everyone with a bottle of Pliny the Elder or at least the new Oak Aged Espresso Yeti.
|Double IPAs, West Coast IPAs, Saisons and Sours
|-
|dlovins
|New York, NY
| Not sure. Something local
|<del>Maybe a hefeweizen of some sort</del> something good in any case
|-
|saverkamp
|Iowa City, IA
|Something from Good People (AL), Back Forty (AL), maybe also Millstream (IA) or Peacetree (IA)
|
|-
|dileshni
|Toronto, ON
|Muskoka cream ale & Beau's Brewery LugTread Lagered Ale
|Cookies.
|-
|chick
|Berkeley
|Best I can find between now and then
|Chocolate Bacon Candy
|-
|jeg
|Charlottetown, PEI
|Gahan IPA, Brown, Might pickup something else on the way
|Hops. Enough hops to peel paint off walls.
|-
|jkeck
|SF Bay Area
|Won't be checking baggage so will I will pick up something local.
|All kinds of IPAs. Hoppy beers. Bacon.
|-
|mackeral
|SF Bay Area
|High Water "Blind Spot" Dark Specialty Ale (Belmont, CA), Auburn Alehouse Imperial IPA (Auburn, CA), Monk's Cafe Flemish Sour Ale (Belgium)
|sours baby
|-
|-
|jdwyn
|Iowa
|MillStream John's White Ale--Iowa brewer (think Belium white like: Hoegaarden, Blue Moon)
|A beer tasting education.
|-
|-
|skerijayne aka DigiKeri_SIL
|MD
|Clipper City Siren Noire, Brewer's Art something, Victory maybe Golden Monkey?
|New Glarus, Belgians, anything over 8%
|-
|ddrexler
|La Grande, OR
|Eastern Oregon stuff: a few fancy brews from Deschutes and Terminal Gravity IPA
|surprise me
|-
|gugek
|Durham, NC
|[http://twitter.com/#!/chefjoseandres/statuses/160920845353619457 Fullsteam First Frost Persimmon]
|Something creative
|-
|wickr
|Hillsboro, OR
|Deschutes Hop Henge, probably Rogue and/or Hair of the Dog
|
|}

=== Suggestions ===

'''Add using the following format: (person who you are making the request of): (your request) - (your name)'''

* Unnamed persons from the Keystone State: Sly Fox, any special Weyerbacher - anarchivist
* anyone: Boulevard smokestack series - danwho
* whosoever brought blueberry stout last year, more of that please - jastirn
* Oregonians/PNW folks: Deschutes Hop Henge (cuz it's seasonal) and Obsidian (cuz I like it) - anarchivist
* younga/Seattlites: Georgetown Donkey Deux; Georgetown Braggott - anarchivist
* if by chance anyone is coming from Salt Lake City: I would love Big Bad Baptist from Epic. Or the Wit if it's available again (I think it's the wrong season though). - HLPitts

=== Buying Beer in Seattle ===

from an email to the code4lib list:

: I can think of three good bottleshops (all w/ taps in case you want a growler) that are located on bus lines from downtown:
:
: * [http://bottleworksbeerstore.blogspot.com/ Bottleworks]: Probably the shop I frequent the most. Take the 16 to Wallingford.
: * [http://www.lastdropbeershop.com/ Last Drop]: Take the 71,72, or 73 north from downtown and get off at 80th.
: * [http://www.seattlebeerauthority.com/ Beer Authority]: probably the quickest trip from downtown on the 522. get off at the 125th St stop in Lake City and walk north a couple of blocks.
: * [http://www.fullthrottlebottles.com/ Full Throttle Bottles]: Buses 131, 106, 23 --about 30 minute ride.
: * Also, QFC (large grocery store chain) usually has a great selection.
: * Lots of other pub/beer places noted on [http://g.co/maps/4m5pk the map]

=== Disclaimers ===

* This is an unofficial event organized by attendees of Code4lib 2012.
* All guests at the Drinkup must be 21 years of age or over with a [http://www.cherylslastcall.com/pdfs/Acceptable-ID-Forms.pdf valid form of ID].
* Any participation in the Drinkup is at your own risk.
* All guests are expected to drink responsibly and behave appropriately.

=== Packing and Shipping Beer ===

If you're flying to Code4lib, you will have to consider how to bring your beer. Some attendees in past years have packed beer in their checked luggage, and others have purchased a beer shipper that was checked separately as luggage. In any event, '''you will not be able to bring beer in carryon luggage.'''

The following are links to resources that provide info on packing your beer for transit.

* [http://barlowbrewing.com/2010/11/11/how-to-pack-and-ship-beer/ How to pack and ship beer]
* [http://baltimoresnacker.blogspot.com/2009/06/how-to-pack-beer-and-wine-into-your.html How to pack beer and wine into your luggage]
* [http://beeradvocate.com/forum/read/3880083 Flying With Beer (Beer Advocate forums)]
* [http://beeradvocate.com/forum/read/4364472 Shipping beer while on business travel (Beer Advocate forums)]
* [http://www.mrboxonline.com/bottle-styrofoam-beer-shipper-p-7579.html A sample styrofoam beer shipper/box combo]

[[Category:Code4Lib2012]]

2012 c4l2012 social activities

2012-02-06T02:33:41Z

Tomkeays:

==Ideas==
* Woodinville distillery tour
* Seattle distillery tour
* Favorite local breweries
* Favorite local tea houses
* Favorite local used bookstores
* Visit hackerspace
** +1

==Planned events==

===Pre-Newcomer + Veterans dinner /drink-up Monday===
Early in town for pre-conference?
First time at code4lib?
Don't know anyone at code4lib?
Join fellow c4l newbies + 2nd + 3rd timers + veterans.
You will gain a bunch of new/veteran code4libbers in one night!
Sign up below (NO CAP). You can show up only for dinner or drinks or both!

But put your name so that we have a rough idea about the number of ppl who will show up =)

'''Plans'''
* When: Monday evening (2/6)
* For Dinner: Meet at 6PM (ish)at the hotel lobby
* For Drinks: show up at Hideout between 8 -10 PM for local art, fancy cocktails, or Belgian beer
* For Hospitality suite intro chat/hangout: show up at 10 PM - midnight? at hospitality suite

Dinner: [http://www.yelp.com/biz/kastoori-grill-seattle Kastoori Grill -Indian & Himalayan/Nepalese/Tibetan (vegetarian-friendly)]
0.8 miles 15 min. walk
* Bohyun Kim - n/v (2nd-timer) (leader)
* Jason Clark - leader
* Margaret Heller
* Sarah Johnston - n
* Andrea Schurr - n/v (2nd-timer)
* Jason Ronallo
* Karen Coombs - v
* Eric James
* Misty De Meo - n
* Keri Thompson - n
* Andreas Orphanides - v
* Tom Burton-West -v
* Keith Folsom - n

Drinks: [http://www.yelp.com/biz/the-hideout-seattle Hideout Lounge] for local art, fancy cocktails, and Belgian beer
0.3 miles 8 min. walk
* Bohyun Kim - n/v (2nd-timer) (leader)
* Jason Clark - leader
* Lisa Kurt - n
* Margaret Heller
* Andrea Schurr - n/v (2nd-timer)
* Anoop Atre (Would love to if back from MS visit)
* Heather Pitts (maybe) - n
* Evviva Weinraub - Hope to join up if back from MS visit)
* Megan Banasek -n
* Misty De Meo (maybe) - n
* Keri Thompson (definitely)
* David Drexler (likely) - n
* Andreas Orphanides - v
* Rebecca Jones - n
* Chick Markley - v
* Ray Henry - n

Hospitality suite intro chat/ hangout: just show up at the hospitality suite - no sign up required.

===Morning Run Tuesday===
I (Ray Schwartz) am organizing a morning run for anyone that would like to join me. It will be around 5 to 6 miles. I usually run a 10 minute per mile pace. And I would like to start around 7am. Select which days Tuesday or Wednesday or both mornings. Choose the date you wish via this Doodle link http://www.doodle.com/3tbigutqvkda5ib8

Link to the course map is at http://www.runningmap.com/?id=351428.

So far 4 have signed up for both Tuesday and Wednesday. Let's meet in the Lobby at 7am on Tuesday, and we will decide how to do Wednesday.

===Newcomer dinner Tuesday===
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> XML.

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

'''Plans'''
* When: Tuesday evening (2/7) '''Note that this year's dinner is on Tuesday'''
* 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 :(
*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 coders
***Herd folks from hotel to restaurant (know where you're going!)

'''Restaurants'''

'''Restaurants within .25 miles of the hotel'''

[http://www.sazeracrestaurant.com/index.php Sazerac] (AWESOME happy hour menu that runs until 8)
* Martin Haye - n
* William Gunn - n
* Rebecca Jones - n
* Chick Markley - v
* Al Cornish - v
* Keri Thompson - n
*'''capped at 6''' ''(So, who's the fearless leader of this group? ~yo_bj)''

[http://oasiankitchen.com/ O'Asian Kitchen and Lounge] (Asian)

'''Restaurants between .25 miles and .5 miles of the hotel'''

[http://www.pikebrewing.com/index_html.shtml Pike Brewing] (local brewery, pub food)
* Ken Varnum - n
* Chad Nelson - n
* Ed Summers - v
* Tommy Ingulfsen - n
* Adam Wead - v or .5n
* Dan Coughlin - n
*'''capped at 6''' ''(So, who's the fearless leader of this group? ~yo_bj)''

[http://www.rockbottom.com/ The Rock Bottom Restaurant & Brewery] (American)

[http://www.wildginger.net/ Wild Ginger] (Asian, a bit overpriced)
* Tamar Sadeh - n
* Kevin Clarke - v

[http://www.thepurplecafe.com/index.html Purple Cafe] (American, Wine Bar) ''reservation made under Calvin Mah for 6:30pm for the 6 of us. I'll be meeting in the hotel lobby at 6pm with some sort of sign. See you then!''
* Calvin Mah - (leader) - v
* David Isaak - n
* Aaron Collier - n
* Sean Hannan - v
* Joshua Gomez - v
* Charlie Morris - n
* '''capped at 6'''

[http://www.cafepaloma.com/ Cafe Paloma] (Mediterranean)
* Jean Rainwater (leader) - v
* Kelley McGrath - n
* Lori Robare - n
* Emily Lynema - v
* Sarah Johnston - n
* Sam Meister - n
* '''capped at 6'''

[http://www.thecollinspub.com/ Collins Pub] (Pub Food, great beer selection)
* Francis Kayiwa - (leader) "(get hold of me at first dot last name at goog as the date gets closer with your mobile)" v
* Michael Lindsey - v
* Dan Suchy - v
* David Drexler - n
* Laura Smart - n
* Heather Pitts - n
*'''capped at 6'''

[http://www.mcmenamins.com/311-six-arms-home Six Arms - McMenamins] (Pub Food & they brew their own beer) ''Meet in the Lobby at 6pm. I've also emailed you. --Joel''
* Joel Richard (richardjm AT si.edu) (leader) - v
* Margaret Heller - v
* Sibyl Schaefer (sschaefer AT rockarch . org) - v
* Tim Lepczyk (timlepczyk AT gmail.com) - n
* Ray Schwartz (schwartzr2@wpunj.edu) - v
* Andrea Schurr (andrea-schurr AT utc DOT edu) - v(2nd-timer)
* '''capped at 6'''

[http://www.611supreme.com/ 611 Supreme] (Crepes and Full Bar) ''Reservation for 6 at 6:30. Meet in the conference hotel lobby at 6pm. Look for the short woman in a trench coat and wide brim hat ~Becky''

*Becky Yoose (leader) - v
*Cynthia Ng - n
*Zoe Chao - v
*Stephanie Collett - n (2nd-timer)
*Bethany Nowviskie - n
* Ben Shum - n
*'''capped at 6'''

[http://www.panafricamarket.com/wp/ Pan Africa Restaurant & Bar] (Pan African)
CLOSED TUESDAYS!!!!!!!!!!!!!!!!!!
Sorry for the confusion. I have moved everyone to Long Provincial, so that you'll have a place held in case you want it. If Long Provincial doesn't suit you, please remove your name in case someone else wants the spot. Again, I'm sorry. --Jason

[http://longprovincial.com/ Long Provincial] Vietnamese (.7 miles from hotel; 15 minute walk)

Reservation for 6 for 6:30 (and I have a confirmation number!). Meet in the hotel lobby at 6 to allow for a strolling pace to walk over there.

Has a jellyfish tank.

*Jason Ronallo (leader?) - v?
*Nettie Lagace - n
*Bohyun Kim - n/v (2nd-timer)
*Wendy Robertson - n
*Jennifer Bowen - n/v (3rd timer)
*James Stuart - n
*'''capped at six'''

'''Restaurants between .5 and 1 mile from hotel'''

[http://momijiseattle.com/ Momiji] New Japanese restaurant in Seattle - [http://www.concierge.com/tools/blogs/unpacked/2011/10/momiji-seattle.html Reviewed in Concierge.com]

* Andrew Nagy (leader) - v
* Cory Lown - v
* Tod Robbins - n

[http://tomdouglas.com/index.php?page=palace-kitchen-dinner Palace Kitchen] (another Tom Douglas restaurant, w/ a focus on meat). ''I have made a reservation for 6 at 8pm. Let's meet in the conference lobby at 6:30pm and make our way slowly over; we will find things to do in the interim. Look for Mike Giarlo, a man who may be holding a sign that says "HI I'M MIKE GIARLO" or otherwise shouting his name or looking confused.''

* Mike Giarlo (leader) - v
* Carmen Mitchell - n
* Daniel Lovins - v
* Cary Gordon - v
* Declan Fleming - v
* Amy Unger - n
* (CAPPED AT SIX!)

[http://sitkaandspruce.com/ Sitka and Spruce] (Eclectic, super-local and super-seasonal.) ''We have a reservation for 6 at 8:15pm. We'll meet in the conference lobby at 6:30 pm and head over - the owners also run [http://www.ferdinandthebar.com/home/ Bar Ferd'nand], a wine shop/bar in the same building, and we can kill time there before we eat. Look for Mark Matienzo or Hillel Arnold.''

* Mark Matienzo (leader) - v
* Hillel Arnold - sophomore
* Devon Smith - v
* bernardo gomez - n
* Derek Merleaux - sophmore
* Jennifer Weintraub - n
* (CAPPED AT SIX!)

[http://www.yelp.com/biz/japonessa-seattle Japonessa Restaurant] (Japanese + full bar)
* Kate Zwaard - n
* Joe Atzberger - v
* Scott Fisher - n (2nd-timer)
* Anoop Atre - n

[http://tomdouglas.com/index.php?page=serious-pie Serious Pie] (Tom Douglas restaurant, inventive pizzas, good local beer list).

* Christopher Spalding (leader) - v
* Robin Schaaf - n
* Jason Stirnaman - v
* Christina Morris - n
* Lisa Kurt - n
* Ray Henry - n
*'''capped at six'''

[http://www.allmenus.com/wa/seattle/204592-ballet-restaurant/menu/ Ballet] (Vietnamese)

[http://www.kokebrestaurant.com/ Kokeb Ethiopian Restaurant] (Ethiopian) ''Let's say meet at the lobby at 6pm like everyone else. Woohoo!''

''We have reservations for 6 at 6:45.''

* Andreas Orphanides (leader) - v
* Mark Mounts - v
* Joe Montibello - n
* Justin Littman - n
* Ron Peterson
* Bobbi Fox - sophmore
* (CAPPED AT SIX!)
Crashing the [http://www.seattlerb.org/ Seattle Ruby] meetup, which meets on Capital Hill at 7:00 on Tuesdays. Eat at [http://www.yelp.com/biz/poppy-seattle Poppy] before. Leaving from the hotel lobby at 6:00. ''If you dig Ruby, come to this. Seattle ruby produced Nokogiri, Vlad, Rubygems.org ....''
* Matt Zumwalt (leader) - v
* *Justin Coyne - n
* Misty De Meo - n

[http://tomdouglas.com/index.php?page=dahlia-lounge Dahlia Lounge] (Pacific Northwest cuisine, $$$)

[http://www.mattsinthemarket.com/ Matt's in the Market] (Northwest Cuisine, $$$)

[http://www.placepigalle-seattle.com/ Place Pigalle] (French)

[http://www.chezshea.com/ Chez Shea] (French)

[http://www.elysianbrewing.com/elysian.html Elysian Breweries and Pubs] (Pub Food)

[http://www.mezaseattle.com/index.html Meza] (Latin Fare)
* Tara Robertson - n
* Shawn Averkamp - sophomore
* Corey Harper - v
* Shaun Ellis - sophomore
* Jon Stroop - fifth year senior
* Birkin James Diana - v (hi Jon!; hey newcomers, I'm taking the 6th slot, but, if you're stuck for a signup, plz do feel free to bump/overwrite me - seriously!)
* '''capped at 6'''''(So, who's the fearless leader of this group? ~yo_bj)''

[http://inthebowlbistro.com/index.php In the Bowl] (Veg*n, Asian)

[http://www.plumbistro.com/ Plumb Bistro] (Veg*n)

[http://highlineseattle.com/ Highline] (Veg*n, bar)

'''Restaurants more than 1 miles from the hotel'''

[http://bravehorsetavern.com/ Brave Horse Tavern] (another Tom Douglas, good regional beer list, yummy food. Near South Lake Union. Would require a ride on the South Lake Union Trolley (SLUT), but it's easy to get to/use from downtown.

[http://www.temperodobrasil.net/ Tempero do Brasil] I was excited to see Ipanema Grill 6 blocks from the hotel, unfortunately it seems to be closed for good. So this restaurant which is a 10 minute ($15) cab ride away and which also serves Brazilian cuisine (including the ever-tasty feijoada) will have to do.
* Robert Haschart - leader - v third year
* Molly Pickral - n

[http://flyingfishrestaurant.com/ Flying Fish] (Seafood)

[http://www.allmenus.com/wa/seattle/3437-cafe-flora/menu/dinner/ Cafe Flora] (FANTASTIC Veg*n restaurant. Use Metro bus #11 to get there)

[http://www.teapotvegetarianhouse.com/index.htm Teapot Vegetarian House] (Veg*n, Asian)

[http://spaceneedle.com/restaurant/ Space Needle] (American, Pricy; but what the heck, listed it anyway for those who want the experience)

==="Get Lamp" viewing Tuesday (9 PM) ===

"Tuesday, February 7, 9 PM or shortly after -Courtyard Ballroom"

Adam Wead and Michael Klein are organizing a viewing of [http://www.getlamp.com/ Get Lamp: The Text Adventure Documentary]

It's not about Linux, Apache, MySQL or PHP, but if you don't have a one, you might get eaten by a grue.

If there is additional interest, there may be another viewing this week.

===Morning Run Wednesday===
I (Ray Schwartz) am organizing a morning run for anyone that would like to join me. It will be around 5 to 6 miles. I usually run a 10 minute per mile pace. And I would like to start around 7am. Select which days Tuesday or Wednesday or both mornings. Choose the date you wish via this Doodle link http://www.doodle.com/3tbigutqvkda5ib8

Link to the course map is at http://www.runningmap.com/?id=351428.

So far 4 have signed up for both Tuesday and Wednesday. Let's meet in the Lobby at 7am on Tuesday, and we will decide how to do Wednesday.

===Veg*n Dinner Wednesday===

We'll pick a place with lots of veg*n options to go eat Wednesday for dinner. Vegetarians and non-vegetarians welcome.

*[http://lovinghut.us/seattle/index.html Loving Hut] Modest price. 1 mile from hotel. Will do bill splitting if we let them know up front.

Talked with Loving Hut and made a reservation for 15 for 6:30. Meet in the hotel lobby at 6.

*Jason Ronallo (jronallo AT gmail.com)
*Sean Hannan
*Ed Summers
*James Stuart
*Bohyun Kim
*Bethany Nowviskie
*Margaret Heller
*Laura Smart
*Sibyl Schaefer
*Cynthia Ng
*Andrea Shurr
*Eric James
*Birkin James Diana
*Sheree F
*Misty De Meo
*Reservation is for 15.

===Meat-Up Dinner Wednesday===

[http://www.bokaseattle.com/ BOKA Kitchen + Bar], 1010 1st Ave (between Spring St & Madison St) - about 1/3 mile/5 min from hotel. We head over from the Amazon Technology Open House and get there by 8PM.
Very much a eat-local place. Beecher cheddar - yum. Nice, mellow room. We should be back in plenty of time to hit the Drink-Up.

* Cary Gordon
* Anoop Atre
* Ben Shum

Note that they have some excellent non-meat options for any meat groupies that want to hang with us.

(if you do not find a suitable burger joint, there are also some top-notch steakhouses in Seattle. Both the Metropolitan Grill and El Gaucho are delightful if folks are OK with $50 steaks. Just FYI, not trying to hijack your meat-up, Cary!. -mjgiarlo)

===Evergreen/Koha and friends dinner Wednesday===
Put your name and any food limitations, or suggestions of places to go. We'll figure where we're going later. For now, let's assume we're meeting in the hotel lobby at 6pm.

* Tara Robertson
* Chris Sharp
* Tod Robbins - n

===[[2012 Craft Brew Drinkup|Craft Brew Drinkup]], Wednesday (9 PM)===

'''Wednesday, February 8, 9 PM-ish -Hospitality Suite'''

Like good beer? Bring some in your luggage! Some of us are planning to bring some of our favorite local, special, or homebrewed beers to share. Interested? Sign up on the [[2012 Craft Brew Drinkup]] page!

===Dim Sum Lunch Thursday===

For those of you staying in town after the last session on Thursday, [http://oasiankitchen.com/ O'Asian Kitchen] has dim sum service during the weekdays. Meet up around 12:35, meeting location tba. Bring cash for easier bill splitting.

*Becky Yoose
* Declan Fleming - love me some Dim Sum!
* Adam Wead
* Heather Pitts
* Sibyl Schaefer
* Anoop Atre
* Dan Suchy
* Carmen Mitchell
* Tara Robertson
* Ray Schwartz
* Cynthia Ng
* Corey Harper
* Joshua Gomez
* Cary Gordon
* Mike Giarlo
* Joe Atzberger
* Dileshni Jayasinghe
* Ryan Wick

==Social Map - places of interest==
[http://g.co/maps/4m5pk Code4lib 2012 - Seattle - social events, hangouts, and places to see]

==Seattle Events Feb 5-9==
===Saturday, February 4, 2012===
In case you are showing up really early.
* Belgianfest: http://www.washingtonbeer.com/belgianfest/
===Sunday, February 5, 2012===
* Clinton Fearon & The Boogie Brown Band/Live Wyya/Adrian Xavier/Selecta Raiford/DJ Courtland, Neumos: http://neumos.com/neumos.php
* Michael The Blind/The Els, Skylark: http://www.skylarkcafe.com/
* Addaura/Alda/Hallow, Comet
* "I Am My Own Wife" 7:30pm at Seattle Repertory Theatre (Seattle Center) http://www.seattlerep.org/Plays/1112/IM/
* Science Fiction + Fantasy short film festival, Encore screening. http://www.empmuseum.org/programs/index.asp?categoryID=216

===Monday, February 6, 2012===
* Silent Movie Mondays: Last Command 1928, http://stgpresents.org/artists/?artist=1829#, Show at 7:00pm, The Paramount Theatre $10
This all-classic film series, First Oscars, is accompanied by live music from the historic Mighty Wurlitzer organ, one of the last three remaining organs of its kind to reside in its original environment, played by critically acclaimed organist Jim Riggs.

===Tuesday, February 7, 2012===
* Lionize/Maylene & The Sons Of Disaster, El Corazon: http://elcorazonseattle.com/
* The Pulltab Playboys/Rachel Lyn Harrington & The Knock Outs/The James Low Western Front, Sunset: http://sunsettavern.com/
* Twin Sister, Vera: http://theveraproject.org/shows/
* The Features, Chop Suey: http://www.chopsuey.com/
* Wilco/White Denim, Paramount Theatre: http://stgpresents.org/
* "I Am My Own Wife" 7:30pm at Seattle Repertory Theatre (Seattle Center) http://www.seattlerep.org/Plays/1112/IM/
* Intro to Arduino Workshop, 7pm at Metrix Create Space http://metrixcreatespace.com/

===Wednesday, February 8, 2012===
* The Golden Blondes/The Jet Age/Mr. Drinx & The Pot Heads, Sunset: http://sunsettavern.com/
* Pipsisewah/The Chasers/The Magic Mirrors, Tractor: http://www.tractortavern.com/
* Dengue Fever vs Secret Chiefs 3, Moe Bar http://bit.ly/yJtfXv (how could you pass the opportunity to see someone play this thing :http://bit.ly/wB5AgZ
* Amazon Tech in Seattle is having an open house next Wednesday at 5:30 PM with Werner Vogels and David Friedberg of the Climate Corporation. https://aws.amazon.com/amazon-open-house-february-2012/ ([http://g.co/maps/adpnt map])

===Thursday, February 9, 2012===
* SAM Opening - Gauguin and Polynesia: An Elusive Paradise: http://www.seattleartmuseum.org/gauguin
* The Jayhawks, Neptune Theater: http://stgpresents.org/
* Digital Leather, Comet
* Savani World Quintet/Super Sones, Columbia City Theater: http://www.columbiacitytheater.com/
* Blvd Park {album release}/Nettle Honey/Creeping Time, Tractor: http://www.tractortavern.com/
* Eleanor Friedberger, Crocodile: http://thecrocodile.com/index.html

===Ongoing Events===
* Seattle Art Museum: Tours are every Saturday & Sunday at noon, and the First Thursday of every month at 10:30, 11:30 am, 12:30 & 1:30 pm.
* EMP: Exhibits on display include: Battlestar Galactica, Nirvana, Avatar, and Can’t Look Away: The Lure of Horror Film
* Teatro ZinZanni: ¡Caliente! http://dreams.zinzanni.org/
* Pacific NW Ballet: performing Don Quixote at McCaw Hall http://www.pnb.org/
* Oklahoma!, Sunday matinee and nightly: 5th Avenue Theatre, 1308 Fifth Avenue http://www.5thavenue.org/show/oklahoma

==Local events/places==
* Metrix Create Space
* Ada's Technical Books
* Northwest Outdoor Center
* Center for Wooden Boats
* Empty Sea Studios acoustic music

==Local Beer Places==
* Map of [http://beermapping.com/maps/citymaps.php?m=seattle#lat=47.66723703450515&lng=-122.28263854980469&z=5 beer venues] maintained at Beermapping.com.
* List of [http://www.washingtonbeer.com/breweries/seattle-king-co/ local breweries] ([http://maps.google.com/maps/ms?hl=en&ie=UTF8&msa=0&msid=201783184139227541123.0004813e64758434cb054&source=embed&ll=47.558921,-122.106171&spn=0.442982,1.234589&z=10&source=embed map]) maintained by the Washington Beer Commission
* Map of [http://www.ratebeer.com/Places/RegionMap.asp?rid=7600 beer venues] maintained by Ratebeer.com.

==See also==
[http://orbiscascade.org/index/c4l-things-to-do-in-seattle Things to do in Seattle, from the hosts]

[[Category:Code4Lib2012]]

2012 preconference proposals

2012-01-13T13:57:16Z

Tomkeays: /* Interest in Attending */

=Proposals for 2012 Code4LibCon Preconferences=
Proposals closed Sunday, November 20, 2011, so we can finalize the list and add them to registration! (The deadline for preconference proposals has passed.)

Spaces available: main meeting room (max 275) + 5 breakout rooms (max 30-50).

'''Please include a "Contact/Responsible Individual" name and email address so we know who is willing to put on the proposed precon.
'''
==Full Day==

=== Hacking Content ===

What is the future of getting library information and resources into users’ hands at the right time and with appropriate context and relevancy. Learning management systems, library guides, Web-scale discovery systems-plenty of tools to choose from and still we see lots of opportunities for improvement. Let’s pick them apart and brainstorm ideas for projects that could address weaknesses in one or all of these systems. If you’re interested in these issues, challenges and conundrums join us for a day of thinking, dreaming and scheming. All skill sets and backgrounds needed.

Speakers/Facilitators will be:
- Thom Cox - Manager of Library Information Technology Services - Tufts University
- Ken Varnum – Web Systems Manager - University of Michigan Libraries
- Evviva Weinraub – Director, Emerging Technologies and Services - Oregon State University Libraries

Contact: Margaret Mellinger - margaret dot mellinger at oregonstate dot edu

==== Interest in Attending ====

*David Uspal (david DOT uspal AT villanova DOT edu)
*Tammy Allgood Wolf

=== Developing applications using REST web services ===

Been hearing about web services but don’t know where to start to build something? Have you built applications that use read services but are stumped by OAuth, Content Negotiation and HTTP Headers? Come dig in and learn how to build applications that interact with both read and write REST services. We’ll cover the basic principles and practices of REST services and discuss the Atom Publishing Protocol as a REST service and its extensibility. The group will examine and test the CouchDB HTTP API by building a simple list creation tool. You’ll learn how OCLC’s platform web services leverage Atom to expose the data and business processes from OCLC’s library systems. By the end of the session, you’ll know the basic principles of REST services, be able to perform Create, Read, Update and Delete operations via REST and be able to authenticate to REST services via API keys and OAuth.

Come ready to learn and code!

Presenter: Karen Coombs - coombsk at oclc dot org

==== Interest in Attending ====

*Sam Kome
*Ray Schwartz
*Jim Robinson
*David Bucknum
*Jean Rainwater
*Laney McGlohon
*Joshua Gomez
*Wayne Schneider
*Andy Kohler
* Tom Keays (keaysht at lemoyne dot edu)

==Half Day Morning==

=== Linkfest ===

We've had talks and sessions galore about Linked Data at code4lib in past years. Let's focus on linking. Bring data you want to publish and link to or link from and your ideas about new ways we can push data linking into being part of our regular approach to how we put our libraries' content and services on the web. At the start of the session we'll run a quick poll to see who wants to link to what and how, and we'll pair or group up and get to work from there. May a kajillion links bloom!

If you need an "intro to linked data" we can prep a good list of readings/talks to review before you come. But please come ready to link!

Organizer type person: Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu

==== Interest in Attending ====
*Becky Yoose
*Tom Johnson
*Ed Summers
* bernardo gomez ( bgomez at emory dot edu )
* William Gunn
* Jason Ronallo
* Keri Thompson
* David Lacy
* Corey A Harper
* Matt Phillips (mphillips@law.harvard.edu)
* Declan Fleming

=== What's New in Solr ===

This session will bring folks up to speed on the latest developments in Lucene and Solr. There's always a lot of new capabilities as well as tips and tricks on using Solr in clever and powerful ways.

Presenter: Erik Hatcher - erik . hatcher @ lucidimagination dot com

==== Interest in Attending ====
* "Gabriel Farrell" <gsf24@drexel.edu>
* "Erik Hetzner" <erik.hetzner AT ucop BORK edu>
* "Kevin S. Clarke" <ksclarke@gmail>
* "Michael B. Klein" <mbklein@gmail>
* Demian Katz (demian DOT katz AT villanova DOT edu)
* "Mark Mounts" <mark.mounts@dartmouth.edu>
* Anoop Atre ~ anoop.atre AT mnsu . edu
* David Isaak <david.isaak@kpchr.org>
* John Pillans <jpillan@indiana.edu>
* John Wynstra (john.wynstra@uni.edu)

==Half Day Afternoon==

=== Git -r done ===

A session to cover all things Git, everyone's favorite distributed version control system. This session should cover a little bit of the history of Git, how it works, and how it's different than other version controls systems like SVN. Practical application should also be covered, including how to clone existing repos and contribute code back to them, how to host your own repository, and best practices for setting up a distributed network.

Looking for attendees with real-life Git experience to share it, so we can all broaden our understanding of possible use-cases and nifty advanced features.

Coordinator: Ian Walls, ByWater Solutions, @sekjal or ian.walls at bywatersolutions com

Helper: Cary Gordon, Cherry Hill Company, @highermath / cgordon@chillco.com

==== Interest in Attending ====

* Patrick Berry (pberry@csuchico.edu)
* Chris Sharp (csharp@georgialibraries.org)
* Matt Critchlow (mcritchlow@ucsd.edu)
* Peter Murray (Peter.Murray@lyrasis.org)
* Margaret Heller (mheller@dom.edu)
* Kevin S. Clarke (ksclarke@gmail)
* Michael B. Klein (mbklein@gmail)
* Demian Katz (demian DOT katz AT villanova DOT edu)
* Benjamin Shum (bshum@biblio.org)
* Sibyl Schaefer (sschaefer@rockarch.org)
* Tammy Allgood Wolf (tammy.allgood@asu.edu)
* Chad Nelson (cnelson17 AT gsu DOT edu)
* Lisa Kurt (lkurt@unr.edu)
* Matt Phillips (mphillips@law.harvard.edu)
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)
* John Wynstra (john.wynstra@uni.edu)
* Declan Fleming

=== Blacklight ===

This session will be walk-through of the architecture of Blacklight and what we have been improving since the rails 3 upgrade. In addition to the architecture of the software, we will also briefly discuss the architecture of the Blacklight community and what has made it successful so far.

For part of the session we will install Blacklight live and get it up and running. This install demo will include a How-To on basic customizations in Blacklight using a test-driven approach (one of the cornerstones of the Blacklight community).

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.

Presenters: Jessie Keck, Stanford University - jkeck at stanford dot edu | Molly Pickral, University of Virginia - mpc3c at virginia dot edu

==== Interest in Attending ====
* bernardo gomez ( bgomez at emory dot edu )
* Mark Mounts <mark.mounts@dartmouth.edu>
* Sibyl Schaefer (sschaefer@rockarch.org)
* John Pillans (jpillan@indiana.edu)
* Mang Sun (mang.dot sun at rice dot edu)
* Emily Lynema (emily_lynema at ncsu dot edu)

=== DACS and EAD Overview ===

This session will look at what DACS (Describing Archives: a Content Standard) is and describe the ten required elements. Then there will be an overview of what EAD is, how it works, and the required elements. The final part will be a practice session on taking a paper finding aid and coding it using DACS and EAD.

Presenter: Doris Munson, Eastern Washington University, dmunson at ewu dot edu
(please feel free to contact me if you are interested in being a co-presenter)

==== Interest in Attending ====
* Francis Kayiwa ( kayiwa@ YouEyeSee dot edu )
* Carmen Mitchell (carmenmitchell at gmail dot com)

=== [[Digging into metadata: context, code, and collaboration]] ===

Working with library/archival metadata is difficult. This preconference will tackle pressing questions and will show some of the intricacies of metadata (including AACR2/MARC) with exercises to demonstrate why inconsistencies exist in the data. What steps can the cataloging & metadata community take to help improve the quality of this data? What tools & techniques could help? Rules have evolved over time leaving dirty legacy data. Systems have impacted--and will continue to impact--data structure & design. How can this data be aggregated and refined for use in a new emerging data environments? What assumptions can safely be made and when do you need to inquire about local practice? We will end with a hack-fest where you can ask questions of experienced catalogers and get help with your metadata related problems. Bring your laptops and data.

Person Herder: Becky Yoose, Grinnell College, yoosebec at grinnell dot edu

Collaborators/Facilitators: Corey Harper, New York University - corey dot harper at nyu dot edu | Shana L. McDanold, University of Pennsylvania -
mcdanold at pobox dot upenn dot edu | Laura Smart, Caltech - laura at library dot caltech dot edu

==== Interest in Attending ====
* Jen Weintraub (jweintraub@library.ucla.edu)
* Peter Green (pmgreen@princeton.edu)
* David Isaak (david.isaak@kpchr.org)
* Alex Rolfe (arolfe@georgefox.edu)

=== "Geo" ===
This session will explore, we hope collaboratively, the presentation of objects on maps. There will be a section on workflow, a section on discovering objects via "geobrowse," a section discovery of objects via "geosearch," and an exploration of the discovery and presentation of geo-referenced images (e.g. historic maps). There will be open discussion on other approaches to map-based discovery. Emphasis will be placed on simplicity of workflow and implementation. Technologies include: Atom, Django, Solr, and OpenLayers.

Presenters: Mike Graves, UNC Chapel Hill, gravm at email dot unc dot edu; Tim Shearer, UNC Chapel Hill, tshearer at email dot unc dot edu
(please feel free to contact Tim if you are interested in being a co-presenter)

==== Interest in Attending ====
* "Gabriel Farrell" <gsf24@drexel.edu>
* Anoop Atre ~ anoop.atre AT mnsu . edu
* Chad Nelson (cnelson17 AT gsu DOT edu)
* Jason Casden (jmcasden AT ncsu DOT edu
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)

== Half-day Evening ==

=== Microsoft Campus Visit ===
Join us for a trip across Lake Washington to Microsoft Headquarters. Bus will depart from the conference hotel at 4:15pm on Monday. We will visit the Microsoft Home and the Envisioning Lab. The we'll head over to Microsoft Research for drinks and appetizers, and you'll see some great demos of some cool new (and free!) technologies coming out of MSR. Bus will get back to hotel by 9:00pm, plenty of time to hit a pub. You'll learn about:

1. Layerscape -[http://communities.worldwidetelescope.org/]

2. ChronoZoom - [http://research.microsoft.com/chronozoom/]

3. F# - [http://www.tryfsharp.org]

4. Microsoft Academic Search - [http://academic.research.microsoft.com]

Space is limited, so reserve your seat today Email Alex at the address below.

Coordinator: Alex Wade, Microsoft Research, awade at microsoft dot com

Presenters: Rob Fatland; Christophe Poulain; Michael Zyskowski

==== Interest in Attending ====
* Declan Fleming
* Matt Critchlow
* Tom Keays (keaysht at lemoyne dot edu)

[[Category: Code4Lib2012]]

2012 preconference proposals

2012-01-13T13:57:01Z

Tomkeays: /* Interest in Attending */

2012 preconference proposals

2012-01-13T13:56:45Z

Tomkeays: /* Interest in Attending */

=Proposals for 2012 Code4LibCon Preconferences=
Proposals closed Sunday, November 20, 2011, so we can finalize the list and add them to registration! (The deadline for preconference proposals has passed.)

Spaces available: main meeting room (max 275) + 5 breakout rooms (max 30-50).

'''Please include a "Contact/Responsible Individual" name and email address so we know who is willing to put on the proposed precon.
'''
==Full Day==

=== Hacking Content ===

What is the future of getting library information and resources into users’ hands at the right time and with appropriate context and relevancy. Learning management systems, library guides, Web-scale discovery systems-plenty of tools to choose from and still we see lots of opportunities for improvement. Let’s pick them apart and brainstorm ideas for projects that could address weaknesses in one or all of these systems. If you’re interested in these issues, challenges and conundrums join us for a day of thinking, dreaming and scheming. All skill sets and backgrounds needed.

Speakers/Facilitators will be:
- Thom Cox - Manager of Library Information Technology Services - Tufts University
- Ken Varnum – Web Systems Manager - University of Michigan Libraries
- Evviva Weinraub – Director, Emerging Technologies and Services - Oregon State University Libraries

Contact: Margaret Mellinger - margaret dot mellinger at oregonstate dot edu

==== Interest in Attending ====

*David Uspal (david DOT uspal AT villanova DOT edu)
*Tammy Allgood Wolf

=== Developing applications using REST web services ===

Been hearing about web services but don’t know where to start to build something? Have you built applications that use read services but are stumped by OAuth, Content Negotiation and HTTP Headers? Come dig in and learn how to build applications that interact with both read and write REST services. We’ll cover the basic principles and practices of REST services and discuss the Atom Publishing Protocol as a REST service and its extensibility. The group will examine and test the CouchDB HTTP API by building a simple list creation tool. You’ll learn how OCLC’s platform web services leverage Atom to expose the data and business processes from OCLC’s library systems. By the end of the session, you’ll know the basic principles of REST services, be able to perform Create, Read, Update and Delete operations via REST and be able to authenticate to REST services via API keys and OAuth.

Come ready to learn and code!

Presenter: Karen Coombs - coombsk at oclc dot org

==== Interest in Attending ====

*Sam Kome
*Ray Schwartz
*Jim Robinson
*David Bucknum
*Jean Rainwater
*Laney McGlohon
*Joshua Gomez
*Wayne Schneider
*Andy Kohler
* Tom Keays (keaysht at lemoyne dot edu)

==Half Day Morning==

=== Linkfest ===

We've had talks and sessions galore about Linked Data at code4lib in past years. Let's focus on linking. Bring data you want to publish and link to or link from and your ideas about new ways we can push data linking into being part of our regular approach to how we put our libraries' content and services on the web. At the start of the session we'll run a quick poll to see who wants to link to what and how, and we'll pair or group up and get to work from there. May a kajillion links bloom!

If you need an "intro to linked data" we can prep a good list of readings/talks to review before you come. But please come ready to link!

Organizer type person: Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu

==== Interest in Attending ====
*Becky Yoose
*Tom Johnson
*Ed Summers
* bernardo gomez ( bgomez at emory dot edu )
* William Gunn
* Jason Ronallo
* Keri Thompson
* David Lacy
* Corey A Harper
* Matt Phillips (mphillips@law.harvard.edu)
* Declan Fleming

=== What's New in Solr ===

This session will bring folks up to speed on the latest developments in Lucene and Solr. There's always a lot of new capabilities as well as tips and tricks on using Solr in clever and powerful ways.

Presenter: Erik Hatcher - erik . hatcher @ lucidimagination dot com

==== Interest in Attending ====
* "Gabriel Farrell" <gsf24@drexel.edu>
* "Erik Hetzner" <erik.hetzner AT ucop BORK edu>
* "Kevin S. Clarke" <ksclarke@gmail>
* "Michael B. Klein" <mbklein@gmail>
* Demian Katz (demian DOT katz AT villanova DOT edu)
* "Mark Mounts" <mark.mounts@dartmouth.edu>
* Anoop Atre ~ anoop.atre AT mnsu . edu
* David Isaak <david.isaak@kpchr.org>
* John Pillans <jpillan@indiana.edu>
* John Wynstra (john.wynstra@uni.edu)

==Half Day Afternoon==

=== Git -r done ===

A session to cover all things Git, everyone's favorite distributed version control system. This session should cover a little bit of the history of Git, how it works, and how it's different than other version controls systems like SVN. Practical application should also be covered, including how to clone existing repos and contribute code back to them, how to host your own repository, and best practices for setting up a distributed network.

Looking for attendees with real-life Git experience to share it, so we can all broaden our understanding of possible use-cases and nifty advanced features.

Coordinator: Ian Walls, ByWater Solutions, @sekjal or ian.walls at bywatersolutions com

Helper: Cary Gordon, Cherry Hill Company, @highermath / cgordon@chillco.com

==== Interest in Attending ====

* Patrick Berry (pberry@csuchico.edu)
* Chris Sharp (csharp@georgialibraries.org)
* Matt Critchlow (mcritchlow@ucsd.edu)
* Peter Murray (Peter.Murray@lyrasis.org)
* Margaret Heller (mheller@dom.edu)
* Kevin S. Clarke (ksclarke@gmail)
* Michael B. Klein (mbklein@gmail)
* Demian Katz (demian DOT katz AT villanova DOT edu)
* Benjamin Shum (bshum@biblio.org)
* Sibyl Schaefer (sschaefer@rockarch.org)
* Tammy Allgood Wolf (tammy.allgood@asu.edu)
* Chad Nelson (cnelson17 AT gsu DOT edu)
* Lisa Kurt (lkurt@unr.edu)
* Matt Phillips (mphillips@law.harvard.edu)
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)
* John Wynstra (john.wynstra@uni.edu)
* Declan Fleming
* Tom Keays (keaysht at lemoyne dot edu)

=== Blacklight ===

This session will be walk-through of the architecture of Blacklight and what we have been improving since the rails 3 upgrade. In addition to the architecture of the software, we will also briefly discuss the architecture of the Blacklight community and what has made it successful so far.

For part of the session we will install Blacklight live and get it up and running. This install demo will include a How-To on basic customizations in Blacklight using a test-driven approach (one of the cornerstones of the Blacklight community).

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.

Presenters: Jessie Keck, Stanford University - jkeck at stanford dot edu | Molly Pickral, University of Virginia - mpc3c at virginia dot edu

==== Interest in Attending ====
* bernardo gomez ( bgomez at emory dot edu )
* Mark Mounts <mark.mounts@dartmouth.edu>
* Sibyl Schaefer (sschaefer@rockarch.org)
* John Pillans (jpillan@indiana.edu)
* Mang Sun (mang.dot sun at rice dot edu)
* Emily Lynema (emily_lynema at ncsu dot edu)

=== DACS and EAD Overview ===

This session will look at what DACS (Describing Archives: a Content Standard) is and describe the ten required elements. Then there will be an overview of what EAD is, how it works, and the required elements. The final part will be a practice session on taking a paper finding aid and coding it using DACS and EAD.

Presenter: Doris Munson, Eastern Washington University, dmunson at ewu dot edu
(please feel free to contact me if you are interested in being a co-presenter)

==== Interest in Attending ====
* Francis Kayiwa ( kayiwa@ YouEyeSee dot edu )
* Carmen Mitchell (carmenmitchell at gmail dot com)

=== [[Digging into metadata: context, code, and collaboration]] ===

Working with library/archival metadata is difficult. This preconference will tackle pressing questions and will show some of the intricacies of metadata (including AACR2/MARC) with exercises to demonstrate why inconsistencies exist in the data. What steps can the cataloging & metadata community take to help improve the quality of this data? What tools & techniques could help? Rules have evolved over time leaving dirty legacy data. Systems have impacted--and will continue to impact--data structure & design. How can this data be aggregated and refined for use in a new emerging data environments? What assumptions can safely be made and when do you need to inquire about local practice? We will end with a hack-fest where you can ask questions of experienced catalogers and get help with your metadata related problems. Bring your laptops and data.

Person Herder: Becky Yoose, Grinnell College, yoosebec at grinnell dot edu

Collaborators/Facilitators: Corey Harper, New York University - corey dot harper at nyu dot edu | Shana L. McDanold, University of Pennsylvania -
mcdanold at pobox dot upenn dot edu | Laura Smart, Caltech - laura at library dot caltech dot edu

==== Interest in Attending ====
* Jen Weintraub (jweintraub@library.ucla.edu)
* Peter Green (pmgreen@princeton.edu)
* David Isaak (david.isaak@kpchr.org)
* Alex Rolfe (arolfe@georgefox.edu)

=== "Geo" ===
This session will explore, we hope collaboratively, the presentation of objects on maps. There will be a section on workflow, a section on discovering objects via "geobrowse," a section discovery of objects via "geosearch," and an exploration of the discovery and presentation of geo-referenced images (e.g. historic maps). There will be open discussion on other approaches to map-based discovery. Emphasis will be placed on simplicity of workflow and implementation. Technologies include: Atom, Django, Solr, and OpenLayers.

Presenters: Mike Graves, UNC Chapel Hill, gravm at email dot unc dot edu; Tim Shearer, UNC Chapel Hill, tshearer at email dot unc dot edu
(please feel free to contact Tim if you are interested in being a co-presenter)

==== Interest in Attending ====
* "Gabriel Farrell" <gsf24@drexel.edu>
* Anoop Atre ~ anoop.atre AT mnsu . edu
* Chad Nelson (cnelson17 AT gsu DOT edu)
* Jason Casden (jmcasden AT ncsu DOT edu
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)

== Half-day Evening ==

=== Microsoft Campus Visit ===
Join us for a trip across Lake Washington to Microsoft Headquarters. Bus will depart from the conference hotel at 4:15pm on Monday. We will visit the Microsoft Home and the Envisioning Lab. The we'll head over to Microsoft Research for drinks and appetizers, and you'll see some great demos of some cool new (and free!) technologies coming out of MSR. Bus will get back to hotel by 9:00pm, plenty of time to hit a pub. You'll learn about:

1. Layerscape -[http://communities.worldwidetelescope.org/]

2. ChronoZoom - [http://research.microsoft.com/chronozoom/]

3. F# - [http://www.tryfsharp.org]

4. Microsoft Academic Search - [http://academic.research.microsoft.com]

Space is limited, so reserve your seat today Email Alex at the address below.

Coordinator: Alex Wade, Microsoft Research, awade at microsoft dot com

Presenters: Rob Fatland; Christophe Poulain; Michael Zyskowski

==== Interest in Attending ====
* Declan Fleming
* Matt Critchlow

[[Category: Code4Lib2012]]

2012 preconference proposals

2012-01-13T13:55:52Z

Tomkeays: /* Interest in Attending */

=Proposals for 2012 Code4LibCon Preconferences=
Proposals closed Sunday, November 20, 2011, so we can finalize the list and add them to registration! (The deadline for preconference proposals has passed.)

Spaces available: main meeting room (max 275) + 5 breakout rooms (max 30-50).

'''Please include a "Contact/Responsible Individual" name and email address so we know who is willing to put on the proposed precon.
'''
==Full Day==

=== Hacking Content ===

What is the future of getting library information and resources into users’ hands at the right time and with appropriate context and relevancy. Learning management systems, library guides, Web-scale discovery systems-plenty of tools to choose from and still we see lots of opportunities for improvement. Let’s pick them apart and brainstorm ideas for projects that could address weaknesses in one or all of these systems. If you’re interested in these issues, challenges and conundrums join us for a day of thinking, dreaming and scheming. All skill sets and backgrounds needed.

Speakers/Facilitators will be:
- Thom Cox - Manager of Library Information Technology Services - Tufts University
- Ken Varnum – Web Systems Manager - University of Michigan Libraries
- Evviva Weinraub – Director, Emerging Technologies and Services - Oregon State University Libraries

Contact: Margaret Mellinger - margaret dot mellinger at oregonstate dot edu

==== Interest in Attending ====

*David Uspal (david DOT uspal AT villanova DOT edu)
*Tammy Allgood Wolf

=== Developing applications using REST web services ===

Been hearing about web services but don’t know where to start to build something? Have you built applications that use read services but are stumped by OAuth, Content Negotiation and HTTP Headers? Come dig in and learn how to build applications that interact with both read and write REST services. We’ll cover the basic principles and practices of REST services and discuss the Atom Publishing Protocol as a REST service and its extensibility. The group will examine and test the CouchDB HTTP API by building a simple list creation tool. You’ll learn how OCLC’s platform web services leverage Atom to expose the data and business processes from OCLC’s library systems. By the end of the session, you’ll know the basic principles of REST services, be able to perform Create, Read, Update and Delete operations via REST and be able to authenticate to REST services via API keys and OAuth.

Come ready to learn and code!

Presenter: Karen Coombs - coombsk at oclc dot org

==== Interest in Attending ====

*Sam Kome
*Ray Schwartz
*Jim Robinson
*David Bucknum
*Jean Rainwater
*Laney McGlohon
*Joshua Gomez
*Wayne Schneider
*Andy Kohler

==Half Day Morning==

=== Linkfest ===

We've had talks and sessions galore about Linked Data at code4lib in past years. Let's focus on linking. Bring data you want to publish and link to or link from and your ideas about new ways we can push data linking into being part of our regular approach to how we put our libraries' content and services on the web. At the start of the session we'll run a quick poll to see who wants to link to what and how, and we'll pair or group up and get to work from there. May a kajillion links bloom!

If you need an "intro to linked data" we can prep a good list of readings/talks to review before you come. But please come ready to link!

Organizer type person: Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu

==== Interest in Attending ====
*Becky Yoose
*Tom Johnson
*Ed Summers
* bernardo gomez ( bgomez at emory dot edu )
* William Gunn
* Jason Ronallo
* Keri Thompson
* David Lacy
* Corey A Harper
* Matt Phillips (mphillips@law.harvard.edu)
* Declan Fleming

=== What's New in Solr ===

This session will bring folks up to speed on the latest developments in Lucene and Solr. There's always a lot of new capabilities as well as tips and tricks on using Solr in clever and powerful ways.

Presenter: Erik Hatcher - erik . hatcher @ lucidimagination dot com

==== Interest in Attending ====
* "Gabriel Farrell" <gsf24@drexel.edu>
* "Erik Hetzner" <erik.hetzner AT ucop BORK edu>
* "Kevin S. Clarke" <ksclarke@gmail>
* "Michael B. Klein" <mbklein@gmail>
* Demian Katz (demian DOT katz AT villanova DOT edu)
* "Mark Mounts" <mark.mounts@dartmouth.edu>
* Anoop Atre ~ anoop.atre AT mnsu . edu
* David Isaak <david.isaak@kpchr.org>
* John Pillans <jpillan@indiana.edu>
* John Wynstra (john.wynstra@uni.edu)

==Half Day Afternoon==

=== Git -r done ===

A session to cover all things Git, everyone's favorite distributed version control system. This session should cover a little bit of the history of Git, how it works, and how it's different than other version controls systems like SVN. Practical application should also be covered, including how to clone existing repos and contribute code back to them, how to host your own repository, and best practices for setting up a distributed network.

Looking for attendees with real-life Git experience to share it, so we can all broaden our understanding of possible use-cases and nifty advanced features.

Coordinator: Ian Walls, ByWater Solutions, @sekjal or ian.walls at bywatersolutions com

Helper: Cary Gordon, Cherry Hill Company, @highermath / cgordon@chillco.com

==== Interest in Attending ====

* Patrick Berry (pberry@csuchico.edu)
* Chris Sharp (csharp@georgialibraries.org)
* Matt Critchlow (mcritchlow@ucsd.edu)
* Peter Murray (Peter.Murray@lyrasis.org)
* Margaret Heller (mheller@dom.edu)
* Kevin S. Clarke (ksclarke@gmail)
* Michael B. Klein (mbklein@gmail)
* Demian Katz (demian DOT katz AT villanova DOT edu)
* Benjamin Shum (bshum@biblio.org)
* Sibyl Schaefer (sschaefer@rockarch.org)
* Tammy Allgood Wolf (tammy.allgood@asu.edu)
* Chad Nelson (cnelson17 AT gsu DOT edu)
* Lisa Kurt (lkurt@unr.edu)
* Matt Phillips (mphillips@law.harvard.edu)
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)
* John Wynstra (john.wynstra@uni.edu)
* Declan Fleming
* Tom Keays (keaysht at lemoyne dot edu)

=== Blacklight ===

This session will be walk-through of the architecture of Blacklight and what we have been improving since the rails 3 upgrade. In addition to the architecture of the software, we will also briefly discuss the architecture of the Blacklight community and what has made it successful so far.

For part of the session we will install Blacklight live and get it up and running. This install demo will include a How-To on basic customizations in Blacklight using a test-driven approach (one of the cornerstones of the Blacklight community).

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.

Presenters: Jessie Keck, Stanford University - jkeck at stanford dot edu | Molly Pickral, University of Virginia - mpc3c at virginia dot edu

==== Interest in Attending ====
* bernardo gomez ( bgomez at emory dot edu )
* Mark Mounts <mark.mounts@dartmouth.edu>
* Sibyl Schaefer (sschaefer@rockarch.org)
* John Pillans (jpillan@indiana.edu)
* Mang Sun (mang.dot sun at rice dot edu)
* Emily Lynema (emily_lynema at ncsu dot edu)

=== DACS and EAD Overview ===

This session will look at what DACS (Describing Archives: a Content Standard) is and describe the ten required elements. Then there will be an overview of what EAD is, how it works, and the required elements. The final part will be a practice session on taking a paper finding aid and coding it using DACS and EAD.

Presenter: Doris Munson, Eastern Washington University, dmunson at ewu dot edu
(please feel free to contact me if you are interested in being a co-presenter)

==== Interest in Attending ====
* Francis Kayiwa ( kayiwa@ YouEyeSee dot edu )
* Carmen Mitchell (carmenmitchell at gmail dot com)

=== [[Digging into metadata: context, code, and collaboration]] ===

Working with library/archival metadata is difficult. This preconference will tackle pressing questions and will show some of the intricacies of metadata (including AACR2/MARC) with exercises to demonstrate why inconsistencies exist in the data. What steps can the cataloging & metadata community take to help improve the quality of this data? What tools & techniques could help? Rules have evolved over time leaving dirty legacy data. Systems have impacted--and will continue to impact--data structure & design. How can this data be aggregated and refined for use in a new emerging data environments? What assumptions can safely be made and when do you need to inquire about local practice? We will end with a hack-fest where you can ask questions of experienced catalogers and get help with your metadata related problems. Bring your laptops and data.

Person Herder: Becky Yoose, Grinnell College, yoosebec at grinnell dot edu

Collaborators/Facilitators: Corey Harper, New York University - corey dot harper at nyu dot edu | Shana L. McDanold, University of Pennsylvania -
mcdanold at pobox dot upenn dot edu | Laura Smart, Caltech - laura at library dot caltech dot edu

==== Interest in Attending ====
* Jen Weintraub (jweintraub@library.ucla.edu)
* Peter Green (pmgreen@princeton.edu)
* David Isaak (david.isaak@kpchr.org)
* Alex Rolfe (arolfe@georgefox.edu)

=== "Geo" ===
This session will explore, we hope collaboratively, the presentation of objects on maps. There will be a section on workflow, a section on discovering objects via "geobrowse," a section discovery of objects via "geosearch," and an exploration of the discovery and presentation of geo-referenced images (e.g. historic maps). There will be open discussion on other approaches to map-based discovery. Emphasis will be placed on simplicity of workflow and implementation. Technologies include: Atom, Django, Solr, and OpenLayers.

Presenters: Mike Graves, UNC Chapel Hill, gravm at email dot unc dot edu; Tim Shearer, UNC Chapel Hill, tshearer at email dot unc dot edu
(please feel free to contact Tim if you are interested in being a co-presenter)

==== Interest in Attending ====
* "Gabriel Farrell" <gsf24@drexel.edu>
* Anoop Atre ~ anoop.atre AT mnsu . edu
* Chad Nelson (cnelson17 AT gsu DOT edu)
* Jason Casden (jmcasden AT ncsu DOT edu
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)

== Half-day Evening ==

=== Microsoft Campus Visit ===
Join us for a trip across Lake Washington to Microsoft Headquarters. Bus will depart from the conference hotel at 4:15pm on Monday. We will visit the Microsoft Home and the Envisioning Lab. The we'll head over to Microsoft Research for drinks and appetizers, and you'll see some great demos of some cool new (and free!) technologies coming out of MSR. Bus will get back to hotel by 9:00pm, plenty of time to hit a pub. You'll learn about:

1. Layerscape -[http://communities.worldwidetelescope.org/]

2. ChronoZoom - [http://research.microsoft.com/chronozoom/]

3. F# - [http://www.tryfsharp.org]

4. Microsoft Academic Search - [http://academic.research.microsoft.com]

Space is limited, so reserve your seat today Email Alex at the address below.

Coordinator: Alex Wade, Microsoft Research, awade at microsoft dot com

Presenters: Rob Fatland; Christophe Poulain; Michael Zyskowski

==== Interest in Attending ====
* Declan Fleming
* Matt Critchlow

[[Category: Code4Lib2012]]

2012 preconference proposals

2012-01-13T13:53:59Z

Tomkeays: /* Interest in Attending */

=Proposals for 2012 Code4LibCon Preconferences=
Proposals closed Sunday, November 20, 2011, so we can finalize the list and add them to registration! (The deadline for preconference proposals has passed.)

Spaces available: main meeting room (max 275) + 5 breakout rooms (max 30-50).

'''Please include a "Contact/Responsible Individual" name and email address so we know who is willing to put on the proposed precon.
'''
==Full Day==

=== Hacking Content ===

What is the future of getting library information and resources into users’ hands at the right time and with appropriate context and relevancy. Learning management systems, library guides, Web-scale discovery systems-plenty of tools to choose from and still we see lots of opportunities for improvement. Let’s pick them apart and brainstorm ideas for projects that could address weaknesses in one or all of these systems. If you’re interested in these issues, challenges and conundrums join us for a day of thinking, dreaming and scheming. All skill sets and backgrounds needed.

Speakers/Facilitators will be:
- Thom Cox - Manager of Library Information Technology Services - Tufts University
- Ken Varnum – Web Systems Manager - University of Michigan Libraries
- Evviva Weinraub – Director, Emerging Technologies and Services - Oregon State University Libraries

Contact: Margaret Mellinger - margaret dot mellinger at oregonstate dot edu

==== Interest in Attending ====

*David Uspal (david DOT uspal AT villanova DOT edu)
*Tammy Allgood Wolf

=== Developing applications using REST web services ===

Been hearing about web services but don’t know where to start to build something? Have you built applications that use read services but are stumped by OAuth, Content Negotiation and HTTP Headers? Come dig in and learn how to build applications that interact with both read and write REST services. We’ll cover the basic principles and practices of REST services and discuss the Atom Publishing Protocol as a REST service and its extensibility. The group will examine and test the CouchDB HTTP API by building a simple list creation tool. You’ll learn how OCLC’s platform web services leverage Atom to expose the data and business processes from OCLC’s library systems. By the end of the session, you’ll know the basic principles of REST services, be able to perform Create, Read, Update and Delete operations via REST and be able to authenticate to REST services via API keys and OAuth.

Come ready to learn and code!

Presenter: Karen Coombs - coombsk at oclc dot org

==== Interest in Attending ====

*Sam Kome
*Ray Schwartz
*Jim Robinson
*David Bucknum
*Jean Rainwater
*Laney McGlohon
*Joshua Gomez
*Wayne Schneider
*Andy Kohler

==Half Day Morning==

=== Linkfest ===

We've had talks and sessions galore about Linked Data at code4lib in past years. Let's focus on linking. Bring data you want to publish and link to or link from and your ideas about new ways we can push data linking into being part of our regular approach to how we put our libraries' content and services on the web. At the start of the session we'll run a quick poll to see who wants to link to what and how, and we'll pair or group up and get to work from there. May a kajillion links bloom!

If you need an "intro to linked data" we can prep a good list of readings/talks to review before you come. But please come ready to link!

Organizer type person: Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu

==== Interest in Attending ====
*Becky Yoose
*Tom Johnson
*Ed Summers
* bernardo gomez ( bgomez at emory dot edu )
* William Gunn
* Jason Ronallo
* Keri Thompson
* David Lacy
* Corey A Harper
* Matt Phillips (mphillips@law.harvard.edu)
* Declan Fleming

=== What's New in Solr ===

This session will bring folks up to speed on the latest developments in Lucene and Solr. There's always a lot of new capabilities as well as tips and tricks on using Solr in clever and powerful ways.

Presenter: Erik Hatcher - erik . hatcher @ lucidimagination dot com

==== Interest in Attending ====
* "Gabriel Farrell" <gsf24@drexel.edu>
* "Erik Hetzner" <erik.hetzner AT ucop BORK edu>
* "Kevin S. Clarke" <ksclarke@gmail>
* "Michael B. Klein" <mbklein@gmail>
* Demian Katz (demian DOT katz AT villanova DOT edu)
* "Mark Mounts" <mark.mounts@dartmouth.edu>
* Anoop Atre ~ anoop.atre AT mnsu . edu
* David Isaak <david.isaak@kpchr.org>
* John Pillans <jpillan@indiana.edu>
* John Wynstra (john.wynstra@uni.edu)

==Half Day Afternoon==

=== Git -r done ===

A session to cover all things Git, everyone's favorite distributed version control system. This session should cover a little bit of the history of Git, how it works, and how it's different than other version controls systems like SVN. Practical application should also be covered, including how to clone existing repos and contribute code back to them, how to host your own repository, and best practices for setting up a distributed network.

Looking for attendees with real-life Git experience to share it, so we can all broaden our understanding of possible use-cases and nifty advanced features.

Coordinator: Ian Walls, ByWater Solutions, @sekjal or ian.walls at bywatersolutions com

Helper: Cary Gordon, Cherry Hill Company, @highermath / cgordon@chillco.com

==== Interest in Attending ====

* Patrick Berry (pberry@csuchico.edu)
* Chris Sharp (csharp@georgialibraries.org)
* Matt Critchlow (mcritchlow@ucsd.edu)
* Peter Murray (Peter.Murray@lyrasis.org)
* Margaret Heller (mheller@dom.edu)
* Kevin S. Clarke (ksclarke@gmail)
* Michael B. Klein (mbklein@gmail)
* Demian Katz (demian DOT katz AT villanova DOT edu)
* Benjamin Shum (bshum@biblio.org)
* Sibyl Schaefer (sschaefer@rockarch.org)
* Tammy Allgood Wolf (tammy.allgood@asu.edu)
* Chad Nelson (cnelson17 AT gsu DOT edu)
* Lisa Kurt (lkurt@unr.edu)
* Matt Phillips (mphillips@law.harvard.edu)
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)
* John Wynstra (john.wynstra@uni.edu)
* Declan Fleming
* Tom Keays (keaysht@lemoyne.edu)

=== Blacklight ===

This session will be walk-through of the architecture of Blacklight and what we have been improving since the rails 3 upgrade. In addition to the architecture of the software, we will also briefly discuss the architecture of the Blacklight community and what has made it successful so far.

For part of the session we will install Blacklight live and get it up and running. This install demo will include a How-To on basic customizations in Blacklight using a test-driven approach (one of the cornerstones of the Blacklight community).

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.

Presenters: Jessie Keck, Stanford University - jkeck at stanford dot edu | Molly Pickral, University of Virginia - mpc3c at virginia dot edu

==== Interest in Attending ====
* bernardo gomez ( bgomez at emory dot edu )
* Mark Mounts <mark.mounts@dartmouth.edu>
* Sibyl Schaefer (sschaefer@rockarch.org)
* John Pillans (jpillan@indiana.edu)
* Mang Sun (mang.dot sun at rice dot edu)
* Emily Lynema (emily_lynema at ncsu dot edu)

=== DACS and EAD Overview ===

This session will look at what DACS (Describing Archives: a Content Standard) is and describe the ten required elements. Then there will be an overview of what EAD is, how it works, and the required elements. The final part will be a practice session on taking a paper finding aid and coding it using DACS and EAD.

Presenter: Doris Munson, Eastern Washington University, dmunson at ewu dot edu
(please feel free to contact me if you are interested in being a co-presenter)

==== Interest in Attending ====
* Francis Kayiwa ( kayiwa@ YouEyeSee dot edu )
* Carmen Mitchell (carmenmitchell at gmail dot com)

=== [[Digging into metadata: context, code, and collaboration]] ===

Working with library/archival metadata is difficult. This preconference will tackle pressing questions and will show some of the intricacies of metadata (including AACR2/MARC) with exercises to demonstrate why inconsistencies exist in the data. What steps can the cataloging & metadata community take to help improve the quality of this data? What tools & techniques could help? Rules have evolved over time leaving dirty legacy data. Systems have impacted--and will continue to impact--data structure & design. How can this data be aggregated and refined for use in a new emerging data environments? What assumptions can safely be made and when do you need to inquire about local practice? We will end with a hack-fest where you can ask questions of experienced catalogers and get help with your metadata related problems. Bring your laptops and data.

Person Herder: Becky Yoose, Grinnell College, yoosebec at grinnell dot edu

Collaborators/Facilitators: Corey Harper, New York University - corey dot harper at nyu dot edu | Shana L. McDanold, University of Pennsylvania -
mcdanold at pobox dot upenn dot edu | Laura Smart, Caltech - laura at library dot caltech dot edu

==== Interest in Attending ====
* Jen Weintraub (jweintraub@library.ucla.edu)
* Peter Green (pmgreen@princeton.edu)
* David Isaak (david.isaak@kpchr.org)
* Alex Rolfe (arolfe@georgefox.edu)

=== "Geo" ===
This session will explore, we hope collaboratively, the presentation of objects on maps. There will be a section on workflow, a section on discovering objects via "geobrowse," a section discovery of objects via "geosearch," and an exploration of the discovery and presentation of geo-referenced images (e.g. historic maps). There will be open discussion on other approaches to map-based discovery. Emphasis will be placed on simplicity of workflow and implementation. Technologies include: Atom, Django, Solr, and OpenLayers.

Presenters: Mike Graves, UNC Chapel Hill, gravm at email dot unc dot edu; Tim Shearer, UNC Chapel Hill, tshearer at email dot unc dot edu
(please feel free to contact Tim if you are interested in being a co-presenter)

==== Interest in Attending ====
* "Gabriel Farrell" <gsf24@drexel.edu>
* Anoop Atre ~ anoop.atre AT mnsu . edu
* Chad Nelson (cnelson17 AT gsu DOT edu)
* Jason Casden (jmcasden AT ncsu DOT edu
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)

== Half-day Evening ==

=== Microsoft Campus Visit ===
Join us for a trip across Lake Washington to Microsoft Headquarters. Bus will depart from the conference hotel at 4:15pm on Monday. We will visit the Microsoft Home and the Envisioning Lab. The we'll head over to Microsoft Research for drinks and appetizers, and you'll see some great demos of some cool new (and free!) technologies coming out of MSR. Bus will get back to hotel by 9:00pm, plenty of time to hit a pub. You'll learn about:

1. Layerscape -[http://communities.worldwidetelescope.org/]

2. ChronoZoom - [http://research.microsoft.com/chronozoom/]

3. F# - [http://www.tryfsharp.org]

4. Microsoft Academic Search - [http://academic.research.microsoft.com]

Space is limited, so reserve your seat today Email Alex at the address below.

Coordinator: Alex Wade, Microsoft Research, awade at microsoft dot com

Presenters: Rob Fatland; Christophe Poulain; Michael Zyskowski

==== Interest in Attending ====
* Declan Fleming
* Matt Critchlow

[[Category: Code4Lib2012]]

2012 preconference proposals

2012-01-13T13:53:47Z

Tomkeays: /* Interest in Attending */

=Proposals for 2012 Code4LibCon Preconferences=
Proposals closed Sunday, November 20, 2011, so we can finalize the list and add them to registration! (The deadline for preconference proposals has passed.)

Spaces available: main meeting room (max 275) + 5 breakout rooms (max 30-50).

'''Please include a "Contact/Responsible Individual" name and email address so we know who is willing to put on the proposed precon.
'''
==Full Day==

=== Hacking Content ===

What is the future of getting library information and resources into users’ hands at the right time and with appropriate context and relevancy. Learning management systems, library guides, Web-scale discovery systems-plenty of tools to choose from and still we see lots of opportunities for improvement. Let’s pick them apart and brainstorm ideas for projects that could address weaknesses in one or all of these systems. If you’re interested in these issues, challenges and conundrums join us for a day of thinking, dreaming and scheming. All skill sets and backgrounds needed.

Speakers/Facilitators will be:
- Thom Cox - Manager of Library Information Technology Services - Tufts University
- Ken Varnum – Web Systems Manager - University of Michigan Libraries
- Evviva Weinraub – Director, Emerging Technologies and Services - Oregon State University Libraries

Contact: Margaret Mellinger - margaret dot mellinger at oregonstate dot edu

==== Interest in Attending ====

*David Uspal (david DOT uspal AT villanova DOT edu)
*Tammy Allgood Wolf

=== Developing applications using REST web services ===

Been hearing about web services but don’t know where to start to build something? Have you built applications that use read services but are stumped by OAuth, Content Negotiation and HTTP Headers? Come dig in and learn how to build applications that interact with both read and write REST services. We’ll cover the basic principles and practices of REST services and discuss the Atom Publishing Protocol as a REST service and its extensibility. The group will examine and test the CouchDB HTTP API by building a simple list creation tool. You’ll learn how OCLC’s platform web services leverage Atom to expose the data and business processes from OCLC’s library systems. By the end of the session, you’ll know the basic principles of REST services, be able to perform Create, Read, Update and Delete operations via REST and be able to authenticate to REST services via API keys and OAuth.

Come ready to learn and code!

Presenter: Karen Coombs - coombsk at oclc dot org

==== Interest in Attending ====

*Sam Kome
*Ray Schwartz
*Jim Robinson
*David Bucknum
*Jean Rainwater
*Laney McGlohon
*Joshua Gomez
*Wayne Schneider
*Andy Kohler
*Tom Keays

==Half Day Morning==

=== Linkfest ===

We've had talks and sessions galore about Linked Data at code4lib in past years. Let's focus on linking. Bring data you want to publish and link to or link from and your ideas about new ways we can push data linking into being part of our regular approach to how we put our libraries' content and services on the web. At the start of the session we'll run a quick poll to see who wants to link to what and how, and we'll pair or group up and get to work from there. May a kajillion links bloom!

If you need an "intro to linked data" we can prep a good list of readings/talks to review before you come. But please come ready to link!

Organizer type person: Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu

==== Interest in Attending ====
*Becky Yoose
*Tom Johnson
*Ed Summers
* bernardo gomez ( bgomez at emory dot edu )
* William Gunn
* Jason Ronallo
* Keri Thompson
* David Lacy
* Corey A Harper
* Matt Phillips (mphillips@law.harvard.edu)
* Declan Fleming

=== What's New in Solr ===

This session will bring folks up to speed on the latest developments in Lucene and Solr. There's always a lot of new capabilities as well as tips and tricks on using Solr in clever and powerful ways.

Presenter: Erik Hatcher - erik . hatcher @ lucidimagination dot com

==== Interest in Attending ====
* "Gabriel Farrell" <gsf24@drexel.edu>
* "Erik Hetzner" <erik.hetzner AT ucop BORK edu>
* "Kevin S. Clarke" <ksclarke@gmail>
* "Michael B. Klein" <mbklein@gmail>
* Demian Katz (demian DOT katz AT villanova DOT edu)
* "Mark Mounts" <mark.mounts@dartmouth.edu>
* Anoop Atre ~ anoop.atre AT mnsu . edu
* David Isaak <david.isaak@kpchr.org>
* John Pillans <jpillan@indiana.edu>
* John Wynstra (john.wynstra@uni.edu)

==Half Day Afternoon==

=== Git -r done ===

A session to cover all things Git, everyone's favorite distributed version control system. This session should cover a little bit of the history of Git, how it works, and how it's different than other version controls systems like SVN. Practical application should also be covered, including how to clone existing repos and contribute code back to them, how to host your own repository, and best practices for setting up a distributed network.

Looking for attendees with real-life Git experience to share it, so we can all broaden our understanding of possible use-cases and nifty advanced features.

Coordinator: Ian Walls, ByWater Solutions, @sekjal or ian.walls at bywatersolutions com

Helper: Cary Gordon, Cherry Hill Company, @highermath / cgordon@chillco.com

==== Interest in Attending ====

* Patrick Berry (pberry@csuchico.edu)
* Chris Sharp (csharp@georgialibraries.org)
* Matt Critchlow (mcritchlow@ucsd.edu)
* Peter Murray (Peter.Murray@lyrasis.org)
* Margaret Heller (mheller@dom.edu)
* Kevin S. Clarke (ksclarke@gmail)
* Michael B. Klein (mbklein@gmail)
* Demian Katz (demian DOT katz AT villanova DOT edu)
* Benjamin Shum (bshum@biblio.org)
* Sibyl Schaefer (sschaefer@rockarch.org)
* Tammy Allgood Wolf (tammy.allgood@asu.edu)
* Chad Nelson (cnelson17 AT gsu DOT edu)
* Lisa Kurt (lkurt@unr.edu)
* Matt Phillips (mphillips@law.harvard.edu)
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)
* John Wynstra (john.wynstra@uni.edu)
* Declan Fleming
* Tom Keays (keaysht@lemoyne.edu)

=== Blacklight ===

This session will be walk-through of the architecture of Blacklight and what we have been improving since the rails 3 upgrade. In addition to the architecture of the software, we will also briefly discuss the architecture of the Blacklight community and what has made it successful so far.

For part of the session we will install Blacklight live and get it up and running. This install demo will include a How-To on basic customizations in Blacklight using a test-driven approach (one of the cornerstones of the Blacklight community).

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.

Presenters: Jessie Keck, Stanford University - jkeck at stanford dot edu | Molly Pickral, University of Virginia - mpc3c at virginia dot edu

==== Interest in Attending ====
* bernardo gomez ( bgomez at emory dot edu )
* Mark Mounts <mark.mounts@dartmouth.edu>
* Sibyl Schaefer (sschaefer@rockarch.org)
* John Pillans (jpillan@indiana.edu)
* Mang Sun (mang.dot sun at rice dot edu)
* Emily Lynema (emily_lynema at ncsu dot edu)

=== DACS and EAD Overview ===

This session will look at what DACS (Describing Archives: a Content Standard) is and describe the ten required elements. Then there will be an overview of what EAD is, how it works, and the required elements. The final part will be a practice session on taking a paper finding aid and coding it using DACS and EAD.

Presenter: Doris Munson, Eastern Washington University, dmunson at ewu dot edu
(please feel free to contact me if you are interested in being a co-presenter)

==== Interest in Attending ====
* Francis Kayiwa ( kayiwa@ YouEyeSee dot edu )
* Carmen Mitchell (carmenmitchell at gmail dot com)

=== [[Digging into metadata: context, code, and collaboration]] ===

Working with library/archival metadata is difficult. This preconference will tackle pressing questions and will show some of the intricacies of metadata (including AACR2/MARC) with exercises to demonstrate why inconsistencies exist in the data. What steps can the cataloging & metadata community take to help improve the quality of this data? What tools & techniques could help? Rules have evolved over time leaving dirty legacy data. Systems have impacted--and will continue to impact--data structure & design. How can this data be aggregated and refined for use in a new emerging data environments? What assumptions can safely be made and when do you need to inquire about local practice? We will end with a hack-fest where you can ask questions of experienced catalogers and get help with your metadata related problems. Bring your laptops and data.

Person Herder: Becky Yoose, Grinnell College, yoosebec at grinnell dot edu

Collaborators/Facilitators: Corey Harper, New York University - corey dot harper at nyu dot edu | Shana L. McDanold, University of Pennsylvania -
mcdanold at pobox dot upenn dot edu | Laura Smart, Caltech - laura at library dot caltech dot edu

==== Interest in Attending ====
* Jen Weintraub (jweintraub@library.ucla.edu)
* Peter Green (pmgreen@princeton.edu)
* David Isaak (david.isaak@kpchr.org)
* Alex Rolfe (arolfe@georgefox.edu)

=== "Geo" ===
This session will explore, we hope collaboratively, the presentation of objects on maps. There will be a section on workflow, a section on discovering objects via "geobrowse," a section discovery of objects via "geosearch," and an exploration of the discovery and presentation of geo-referenced images (e.g. historic maps). There will be open discussion on other approaches to map-based discovery. Emphasis will be placed on simplicity of workflow and implementation. Technologies include: Atom, Django, Solr, and OpenLayers.

Presenters: Mike Graves, UNC Chapel Hill, gravm at email dot unc dot edu; Tim Shearer, UNC Chapel Hill, tshearer at email dot unc dot edu
(please feel free to contact Tim if you are interested in being a co-presenter)

==== Interest in Attending ====
* "Gabriel Farrell" <gsf24@drexel.edu>
* Anoop Atre ~ anoop.atre AT mnsu . edu
* Chad Nelson (cnelson17 AT gsu DOT edu)
* Jason Casden (jmcasden AT ncsu DOT edu
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)

== Half-day Evening ==

=== Microsoft Campus Visit ===
Join us for a trip across Lake Washington to Microsoft Headquarters. Bus will depart from the conference hotel at 4:15pm on Monday. We will visit the Microsoft Home and the Envisioning Lab. The we'll head over to Microsoft Research for drinks and appetizers, and you'll see some great demos of some cool new (and free!) technologies coming out of MSR. Bus will get back to hotel by 9:00pm, plenty of time to hit a pub. You'll learn about:

1. Layerscape -[http://communities.worldwidetelescope.org/]

2. ChronoZoom - [http://research.microsoft.com/chronozoom/]

3. F# - [http://www.tryfsharp.org]

4. Microsoft Academic Search - [http://academic.research.microsoft.com]

Space is limited, so reserve your seat today Email Alex at the address below.

Coordinator: Alex Wade, Microsoft Research, awade at microsoft dot com

Presenters: Rob Fatland; Christophe Poulain; Michael Zyskowski

==== Interest in Attending ====
* Declan Fleming
* Matt Critchlow

[[Category: Code4Lib2012]]

2012 preconference proposals

2012-01-13T13:50:55Z

Tomkeays: /* Interest in Attending */

=Proposals for 2012 Code4LibCon Preconferences=
Proposals closed Sunday, November 20, 2011, so we can finalize the list and add them to registration! (The deadline for preconference proposals has passed.)

Spaces available: main meeting room (max 275) + 5 breakout rooms (max 30-50).

'''Please include a "Contact/Responsible Individual" name and email address so we know who is willing to put on the proposed precon.
'''
==Full Day==

=== Hacking Content ===

What is the future of getting library information and resources into users’ hands at the right time and with appropriate context and relevancy. Learning management systems, library guides, Web-scale discovery systems-plenty of tools to choose from and still we see lots of opportunities for improvement. Let’s pick them apart and brainstorm ideas for projects that could address weaknesses in one or all of these systems. If you’re interested in these issues, challenges and conundrums join us for a day of thinking, dreaming and scheming. All skill sets and backgrounds needed.

Speakers/Facilitators will be:
- Thom Cox - Manager of Library Information Technology Services - Tufts University
- Ken Varnum – Web Systems Manager - University of Michigan Libraries
- Evviva Weinraub – Director, Emerging Technologies and Services - Oregon State University Libraries

Contact: Margaret Mellinger - margaret dot mellinger at oregonstate dot edu

==== Interest in Attending ====

*David Uspal (david DOT uspal AT villanova DOT edu)
*Tammy Allgood Wolf

=== Developing applications using REST web services ===

Been hearing about web services but don’t know where to start to build something? Have you built applications that use read services but are stumped by OAuth, Content Negotiation and HTTP Headers? Come dig in and learn how to build applications that interact with both read and write REST services. We’ll cover the basic principles and practices of REST services and discuss the Atom Publishing Protocol as a REST service and its extensibility. The group will examine and test the CouchDB HTTP API by building a simple list creation tool. You’ll learn how OCLC’s platform web services leverage Atom to expose the data and business processes from OCLC’s library systems. By the end of the session, you’ll know the basic principles of REST services, be able to perform Create, Read, Update and Delete operations via REST and be able to authenticate to REST services via API keys and OAuth.

Come ready to learn and code!

Presenter: Karen Coombs - coombsk at oclc dot org

==== Interest in Attending ====

*Sam Kome
*Ray Schwartz
*Jim Robinson
*David Bucknum
*Jean Rainwater
*Laney McGlohon
*Joshua Gomez
*Wayne Schneider
*Andy Kohler
*Tom Keays

==Half Day Morning==

=== Linkfest ===

We've had talks and sessions galore about Linked Data at code4lib in past years. Let's focus on linking. Bring data you want to publish and link to or link from and your ideas about new ways we can push data linking into being part of our regular approach to how we put our libraries' content and services on the web. At the start of the session we'll run a quick poll to see who wants to link to what and how, and we'll pair or group up and get to work from there. May a kajillion links bloom!

If you need an "intro to linked data" we can prep a good list of readings/talks to review before you come. But please come ready to link!

Organizer type person: Dan Chudnov, GWU Libraries, @dchud or dchud at gwu edu

==== Interest in Attending ====
*Becky Yoose
*Tom Johnson
*Ed Summers
* bernardo gomez ( bgomez at emory dot edu )
* William Gunn
* Jason Ronallo
* Keri Thompson
* David Lacy
* Corey A Harper
* Matt Phillips (mphillips@law.harvard.edu)
* Declan Fleming

=== What's New in Solr ===

This session will bring folks up to speed on the latest developments in Lucene and Solr. There's always a lot of new capabilities as well as tips and tricks on using Solr in clever and powerful ways.

Presenter: Erik Hatcher - erik . hatcher @ lucidimagination dot com

==== Interest in Attending ====
* "Gabriel Farrell" <gsf24@drexel.edu>
* "Erik Hetzner" <erik.hetzner AT ucop BORK edu>
* "Kevin S. Clarke" <ksclarke@gmail>
* "Michael B. Klein" <mbklein@gmail>
* Demian Katz (demian DOT katz AT villanova DOT edu)
* "Mark Mounts" <mark.mounts@dartmouth.edu>
* Anoop Atre ~ anoop.atre AT mnsu . edu
* David Isaak <david.isaak@kpchr.org>
* John Pillans <jpillan@indiana.edu>
* John Wynstra (john.wynstra@uni.edu)

==Half Day Afternoon==

=== Git -r done ===

A session to cover all things Git, everyone's favorite distributed version control system. This session should cover a little bit of the history of Git, how it works, and how it's different than other version controls systems like SVN. Practical application should also be covered, including how to clone existing repos and contribute code back to them, how to host your own repository, and best practices for setting up a distributed network.

Looking for attendees with real-life Git experience to share it, so we can all broaden our understanding of possible use-cases and nifty advanced features.

Coordinator: Ian Walls, ByWater Solutions, @sekjal or ian.walls at bywatersolutions com

Helper: Cary Gordon, Cherry Hill Company, @highermath / cgordon@chillco.com

==== Interest in Attending ====

* Patrick Berry (pberry@csuchico.edu)
* Chris Sharp (csharp@georgialibraries.org)
* Matt Critchlow (mcritchlow@ucsd.edu)
* Peter Murray (Peter.Murray@lyrasis.org)
* Margaret Heller (mheller@dom.edu)
* Kevin S. Clarke (ksclarke@gmail)
* Michael B. Klein (mbklein@gmail)
* Demian Katz (demian DOT katz AT villanova DOT edu)
* Benjamin Shum (bshum@biblio.org)
* Sibyl Schaefer (sschaefer@rockarch.org)
* Tammy Allgood Wolf (tammy.allgood@asu.edu)
* Chad Nelson (cnelson17 AT gsu DOT edu)
* Lisa Kurt (lkurt@unr.edu)
* Matt Phillips (mphillips@law.harvard.edu)
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)
* John Wynstra (john.wynstra@uni.edu)
* Declan Fleming

=== Blacklight ===

This session will be walk-through of the architecture of Blacklight and what we have been improving since the rails 3 upgrade. In addition to the architecture of the software, we will also briefly discuss the architecture of the Blacklight community and what has made it successful so far.

For part of the session we will install Blacklight live and get it up and running. This install demo will include a How-To on basic customizations in Blacklight using a test-driven approach (one of the cornerstones of the Blacklight community).

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.

Presenters: Jessie Keck, Stanford University - jkeck at stanford dot edu | Molly Pickral, University of Virginia - mpc3c at virginia dot edu

==== Interest in Attending ====
* bernardo gomez ( bgomez at emory dot edu )
* Mark Mounts <mark.mounts@dartmouth.edu>
* Sibyl Schaefer (sschaefer@rockarch.org)
* John Pillans (jpillan@indiana.edu)
* Mang Sun (mang.dot sun at rice dot edu)
* Emily Lynema (emily_lynema at ncsu dot edu)

=== DACS and EAD Overview ===

This session will look at what DACS (Describing Archives: a Content Standard) is and describe the ten required elements. Then there will be an overview of what EAD is, how it works, and the required elements. The final part will be a practice session on taking a paper finding aid and coding it using DACS and EAD.

Presenter: Doris Munson, Eastern Washington University, dmunson at ewu dot edu
(please feel free to contact me if you are interested in being a co-presenter)

==== Interest in Attending ====
* Francis Kayiwa ( kayiwa@ YouEyeSee dot edu )
* Carmen Mitchell (carmenmitchell at gmail dot com)

=== [[Digging into metadata: context, code, and collaboration]] ===

Working with library/archival metadata is difficult. This preconference will tackle pressing questions and will show some of the intricacies of metadata (including AACR2/MARC) with exercises to demonstrate why inconsistencies exist in the data. What steps can the cataloging & metadata community take to help improve the quality of this data? What tools & techniques could help? Rules have evolved over time leaving dirty legacy data. Systems have impacted--and will continue to impact--data structure & design. How can this data be aggregated and refined for use in a new emerging data environments? What assumptions can safely be made and when do you need to inquire about local practice? We will end with a hack-fest where you can ask questions of experienced catalogers and get help with your metadata related problems. Bring your laptops and data.

Person Herder: Becky Yoose, Grinnell College, yoosebec at grinnell dot edu

Collaborators/Facilitators: Corey Harper, New York University - corey dot harper at nyu dot edu | Shana L. McDanold, University of Pennsylvania -
mcdanold at pobox dot upenn dot edu | Laura Smart, Caltech - laura at library dot caltech dot edu

==== Interest in Attending ====
* Jen Weintraub (jweintraub@library.ucla.edu)
* Peter Green (pmgreen@princeton.edu)
* David Isaak (david.isaak@kpchr.org)
* Alex Rolfe (arolfe@georgefox.edu)

=== "Geo" ===
This session will explore, we hope collaboratively, the presentation of objects on maps. There will be a section on workflow, a section on discovering objects via "geobrowse," a section discovery of objects via "geosearch," and an exploration of the discovery and presentation of geo-referenced images (e.g. historic maps). There will be open discussion on other approaches to map-based discovery. Emphasis will be placed on simplicity of workflow and implementation. Technologies include: Atom, Django, Solr, and OpenLayers.

Presenters: Mike Graves, UNC Chapel Hill, gravm at email dot unc dot edu; Tim Shearer, UNC Chapel Hill, tshearer at email dot unc dot edu
(please feel free to contact Tim if you are interested in being a co-presenter)

==== Interest in Attending ====
* "Gabriel Farrell" <gsf24@drexel.edu>
* Anoop Atre ~ anoop.atre AT mnsu . edu
* Chad Nelson (cnelson17 AT gsu DOT edu)
* Jason Casden (jmcasden AT ncsu DOT edu
* Dileshni Jayasinghe (d.jayasinghe@utoronto.ca)

== Half-day Evening ==

=== Microsoft Campus Visit ===
Join us for a trip across Lake Washington to Microsoft Headquarters. Bus will depart from the conference hotel at 4:15pm on Monday. We will visit the Microsoft Home and the Envisioning Lab. The we'll head over to Microsoft Research for drinks and appetizers, and you'll see some great demos of some cool new (and free!) technologies coming out of MSR. Bus will get back to hotel by 9:00pm, plenty of time to hit a pub. You'll learn about:

1. Layerscape -[http://communities.worldwidetelescope.org/]

2. ChronoZoom - [http://research.microsoft.com/chronozoom/]

3. F# - [http://www.tryfsharp.org]

4. Microsoft Academic Search - [http://academic.research.microsoft.com]

Space is limited, so reserve your seat today Email Alex at the address below.

Coordinator: Alex Wade, Microsoft Research, awade at microsoft dot com

Presenters: Rob Fatland; Christophe Poulain; Michael Zyskowski

==== Interest in Attending ====
* Declan Fleming
* Matt Critchlow

[[Category: Code4Lib2012]]

Code4Lib Journal WordPress Input Guidelines

2011-10-31T12:58:02Z

Tomkeays: /* Publishing an Issue */

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

==The WP Admin Interface==
To get to WordPress interface for entering an article, choose 'Site Admin' from the footer of any Journal page, login if necessary, and then choose Write//Write Post from the WP admin menus. (Alternatively, go to http://journal.code4lib.org/wp/wp-admin/). If you don't have a WordPress editor login and need one, talk to our web admin (Jon Brinley).

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

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

==Article Content==
The body of the article goes in the "Post" field. The top-level header (<code><h1></code>) is used for the title of the post, so start with second-level headers (<code><h2></code>) for sections of the article. Any header from second- to sixth-level may be used as appropriate. Use HTML markup appropriately and semantically, ''e.g.'', <code><em></code> for emphasized text, <code><strong></code> for strongly emphasized text, <code><blockquote></code> when quoting blocks of text. Avoid such monstrosities as <code><font></code> and <code><blink></code>.

===Pasting from Word===

If you just paste content from Word into WP, it ends up with REALLY BAD html. Fortunately, WP has a built-in feature to help with this. Open the 'advanced toolbar' in editing GUI (right-most link), then click on the paste-from-word icon. This transforms Word's html into really nice pretty html.

===Images and Attached Content===
In-line images should be no wider than 500px.

The caption for an image should be entered in a p with class="caption":
<nowiki><p class="caption">Figure 1. How to Caption an Image.</p>
</nowiki>
In general, we bold the figure / table label using the strong tag:
<nowiki><p class="caption"><strong>Figure 1.</strong> How to Caption an Image.</p>
</nowiki>

'''Uploading files manually'''

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

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

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

in there you'll find an "issue1" subdir (or issueX subdir--if you don't, create one or ask for help creating one!). Inside THERE, create a subdir with the last name of the first author, and put all your image and other attached content in there. It will now have this sort of url:
http://journal.code4lib.org/media/issue1/smith/imagename.png

Add to your img src or a href's as desired. You can use this not just for images, but for extended code attachments, etc.

'''Uploading media via WordPress'''

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

===Code===

Put all code in <code><pre></code> tags.

====Code Highlighting====

If the code is in a supported language, we can do syntax highlighting.

ibiblio has a PHPS extensionm, so if you an "s" on the end of .php files, e.g.,
<filename>.phps
it does syntax highlighting for you.

We're still deciding if we like the syntax highlighting, don't feel compelled to make it work if it's not working for you (but please let other editors know what your experience is). To make this work, you still wrap your code in <code><pre></code> tags. Inside of the <code><pre></code> tags, but around your code, include
[sourcecode language='langcode']...[/sourcecode]

Replace <code>langcode</code> with the appropriate code from the following list (if more than one option for a language, any one will work).

{|
!Language!!Code
|-
|C++||cpp, c, c++
|-
|C#||c#, c-sharp, csharp
|-
|CSS||css
|-
|Delphi||delphi, pascal
|-
|Java||java
|-
|JavaScript||js, jscript, javascript
|-
|PHP||php
|-
|Python||py, python
|-
|Ruby||rb, ruby, rails, ror
|-
|SQL||sql
|-
|VB||vb, vb.net
|-
|XML/HTML||xml, html, xhtml, xslt
|}

Example:
<pre>[sourcecode language='css']body {
font-size: 0.625em;
background-color: #0000ff;
color: #ffff00;
}[/sourcecode]</pre>

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

==Abstract==

While you are editing the article, there is a box labeled "Optional Excerpt" a little ways below the "Post" field. Put the abstract here. Use HTML markup as appropriate. What you put in this field is what will be distributed in our syndication feed and what will appear before the article as the abstract.

Assigned editors are ultimately responsible for a good abstract. Authors aren't always the best at writing good abstracts for their articles, you should probably revise or even write a new one from scratch as necessary, even when the author has provided one. Some of the abstracts for my assigned articles haven't even mentioned what I consider the most significant features of the article.

Since indexes (like EBSCO) may end up indexing abstracts and not full text (and even full text indexes may weigh abstracts more highly), the abstract should probably include any important terms that should 'hit' on the article, such as key technologies or concepts.

I've found that extracting sentences or clauses from the article itself is a good way to build an abstract that will represent the article as the authors intended. The conclusion section is often a good place to look for such key sentences/clauses.

Final abstracts should be passed by the authors for approval.

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

<pre><a href="http://journal.code4lib.org/coins">(COinS)</a></pre>

This is so the user without a browser extension will see that something is there she might be interested in, and get an explanation of COinS and how to make use of it.

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

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

==Author Information==

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

End each article with a second-level header that says "About the Author(s)", with class="abouttheauthor" set. Then give a short paragraph about each author. We do want to have some kind of contact information published (personal web page, email address (obscured if desired), etc.) for each author.

There is a box beneath the article-editing box with the label "Author(s)". Anything you put in this field will be treated as the author of the article. This will show up in the ToC and in the syndication feeds. If you don't populate this field, WordPress will use the username of the editor, instead.

==Categories/Tags==
Posts will have "Uncagetorized" checked by default. Uncheck that box, and check the box next to the current issue, which will be a subcategory of "Issues." Do not check the "Issues" category. We generally do not add tags, except for Conference reviews

==WordPress Buttons==

;Save
:Saves the article, sets the post status to whatever option is selected in the Publish Status form.
;Publish
:Saves the article, sets the post status to Pending Review and assigns a timestamp to the article.

If an issue is not yet published, setting the post status to "Published" or clicking the "Publish" button will set the article to "Pending Review" status. If the issue is already published, this would actually publish the article.

==WordPress Post Status==
An article has four possible statuses. However, only the first three statuses are available to editors.
;Draft
:Use for not yet complete articles. Only editors can see these.
;Pending Review
:Use for sharing the article with authors. Editors and anyone logged in with user ID 17 (i.e., the author account) can see these. See this [http://groups.google.com/group/c4lj-articles/browse_thread/thread/1231b06c09f1289f post] on c4lj-articles for the login information for the author account (username: author).
;Private
:We don't use this option anymore.
;Published
:A published post is visible to everyone. It is part of the RSS feed. If you're editing an already published post, don't select anything in the post status form, just hit Save.

==Publishing an Issue==

# Let everyone on the c4lj-articles list know you are getting ready to publish (so they can save and close any open articles).
# Log in to WordPress
# Make sure that all articles for the issue have the correct issue category selected and have been set to 'Pending Review'. Make sure that the "Uncategorized" and "Issues" categories are unchecked (only the specific issue should be selected).
# Sanity check: count the number of posts which should appear in the publish list
# Click on Posts -> Issues (on the left side)
# Click on "Publish" for the issue you'd like to publish.
## You'll get a list of every "Pending Review" article in that issue. Make sure the number of articles in the list matches your previous count. Don't see all the articles you think you should see? They could be still in Draft status, or not in the correct Issue category, or still have "Uncategorized" selected, or someone may still have it in edit mode. Go back to the posts list and make any necessary changes, and start from #5 again.
# Drag and drop the article titles until they're in the order you want. The order you see there is the order you'll see on the home page (and probably the opposite of the order you'll see in your feed reader).
## Note: It's the coordinating editor's responsibility to decide what order he or she would like the articles to show up in, and order them appropriately when publishing the issue. In general, we try to put the articles with the widest appeal first, and special types (columns, special reports, book reviews, etc.) at the end.
# Click on Posts -> Categories (on the left side)
# Make sure all three fields for the current issue are filled in and correct:
## The human-readable name of the issue goes into the Name field -- e.g., "Issue 15".
## The date of publication goes into the Description field -- e.g., "2011-10-31".
## The URL name goes into the Slug field -- e.g., "issue15" would give the URL of the issue, http://journal.code4lib.org/issues/issue15
# Click "Publish Issue" (optionally setting the publication time, first). Setting the time should only have an impact on readers who are not logged into the c4lj site. Editors will be able to see the published articles.
# Go to the Journal front page; check the number of articles is correct (again) and that they are in the right order. If there is a problem, go back to the admin interface, click on Posts -> Issues and click Unpublish for the issue. Make whatever corrections are needed and proceed from #5 again.
# Once the issue is finally published, go to [[Code4Lib_Journal_Entries_in_Directory_of_Open_Access_Journals]] and follow the directions to upload the issue metadata to DOAJ.
# Send out announcements (see [[Code4Lib_Journal_Publicity_Venues]])

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

[[Category:Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2011-07-29T16:28:59Z

Tomkeays: /* Current Editors */

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

=== Current Editors ===

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

=== Former Editors ===

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

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

[[Category: Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2011-07-29T16:27:00Z

Tomkeays: /* Roster */

=== Current Editors ===

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

=== Former Editors ===

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

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

[[Category: Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2011-07-29T16:26:49Z

Tomkeays: /* Code4Lib Journal Editorial Committee Members */

== Roster ==

=== Current Editors ===

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

=== Former Editors ===

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

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

[[Category: Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2011-07-29T16:21:34Z

Tomkeays: /* Former Editors */

== Code4Lib Journal Editorial Committee Members ==

=== Current Editors ===

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

=== Former Editors ===

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

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

[[Category: Code4Lib Journal]]

Code4Lib Journal Editorial Committee

2011-07-29T16:20:47Z

Tomkeays: New page: == Code4Lib Journal Editorial Committee Members == === Current Editors === * Andrew Darby (3-current; CE 8) * Carol Bean (1-current; CE 9) * Ed Corrado (1-current; CE 10) * Emily Lynema...

== Code4Lib Journal Editorial Committee Members ==

=== Current Editors ===

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

=== Former Editors ===

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

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

Code4Lib Journal Deadlines

2011-07-02T02:08:33Z

Tomkeays: /* Fifteenth 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

===Fifteenth issue===

* Call for proposals: Monday, June 27, 2011
* Proposals due: Friday, July 29, 2011
* Proposals accepted: Friday, August 5, 2011
* First draft due: Friday, September 2, 2011
* Second draft due: Friday, September 30, 2011
* Publication date: Monday, October 31, 2011

===Fourteenth issue===

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

===Thirteenth issue===

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

===Twelfth issue===

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

===Eleventh issue===

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

=== Tenth issue ===

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

=== Ninth issue ===

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

=== Eighth issue ===

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

=== Seventh issue ===

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

=== Sixth issue ===

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

=== Fifth issue ===

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

=== Fourth issue ===

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

=== Third issue ===

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

=== Second issue ===

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

=== First issue ===

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

[[Category: Code4Lib Journal]]

Code4Lib Journal Publicity Venues

2010-06-22T22:16:23Z

Tomkeays: /* Announcing Publication */

== Distributing Call for Submissions ==

* [http://listserv.syr.edu/archives/autocat.html AUTOCAT] autocat@listserv.syr.edu
* [https://listserv.nd.edu/cgi-bin/wa?A0=CODE4LIB Code4Lib] code4lib@listserv.nd.edu
* [http://listserv.uic.edu/htbin/wa?A0=drupal4lib Drupal4Lib] drupal4lib@listserv.uic.edu
* [http://lists.ala.org/wws/arc/lita-l LITA-L] lita-l@ala.org
* [http://metadatalibrarians.monarchos.com/ Metadatalibrarians] metadatalibrarians@lists.monarchos.com
* [https://listserv.nd.edu/cgi-bin/wa?A0=NGC4LIB NGC4Lib] ngc4lib@listserv.nd.edu
* [http://mail.archive.org/pipermail/ol-lib/ Open Library] ol-lib@archive.org
* [http://lists.sourceforge.net/lists/listinfo/oss4lib-discuss OSS4Lib] oss4lib-discuss@lists.sourceforge.net
* [https://listserv.nd.edu/cgi-bin/wa?A0=Usability4Lib Usability4Lib] usability4lib@listserv.nd.edu,
* [http://lists.webjunction.org/web4lib/ Web4Lib] web4lib@webjunction.org
* [http://lists.webjunction.org/xml4lib/ XML4Lib] web4lib@webjunction.org

Web Sites

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

== Announcing Publication ==

Lists, blogs, etc., where issue 7 was publicized:

#Autocat (Chris)
#code4lib (Tom)
#drupal4lib (Tom)
#LISWire (Chris)
#lita-l (Chris)
#Metadatalibrarians (Chris)
#ngc4lib (Tom)
#ol-lib (Tom)
#oss4lib (Tom)
#usability4lib (Tom)
#web4lib (Tom)
#xml4lib (Tom)

Still to do:

#code4lib website (?)

== Twitter Hashtag ==

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

[[Category: Code4Lib Journal]]

Code4Lib Journal WordPress Input Guidelines

2010-06-04T11:46:05Z

Tomkeays: /* Images and Attached Content */

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

==The WP Admin Interface==
To get to WordPress interface for entering an article, choose 'Site Admin' from the footer of any Journal page, login if necessary, and then choose Write//Write Post from the WP admin menus. (Alternatively, go to http://journal.code4lib.org/wp/wp-admin/). If you don't have a WordPress editor login and need one, talk to our web admin (Jon Brinley).

==Proofs for Authors==
A read-only login that is shared with authors can be found in [http://groups.google.com/group/c4lj-articles/msg/88ffb388fe0419e8?hl=en this message] on the c4lj-articles listserv.

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

==Article Content==
The body of the article goes in the "Post" field. The top-level header (<code><h1></code>) is used for the title of the post, so start with second-level headers (<code><h2></code>) for sections of the article. Any header from second- to sixth-level may be used as appropriate. Use HTML markup appropriately and semantically, ''e.g.'', <code><em></code> for emphasized text, <code><strong></code> for strongly emphasized text, <code><blockquote></code> when quoting blocks of text. Avoid such monstrosities as <code><font></code> and <code><blink></code>.

===Pasting from Word===

If you just paste content from Word into WP, it ends up with REALLY BAD html. Fortunately, WP has a built-in feature to help with this. Open the 'advanced toolbar' in editing GUI (right-most link), then click on the paste-from-word icon. This transforms Word's html into really nice pretty html.

===Images and Attached Content===
In-line images should be no wider than 500px.
The caption for an image should be entered in a p with class="caption":
<nowiki><p class="caption">Figure 1. How to Caption an Image.</p>
</nowiki>
In general, we bold the figure / table label using the strong tag:
<nowiki><p class="caption"><strong>Figure 1.</strong> How to Caption an Image.</p>
</nowiki>

Two options for images and other attached content/media:
# use WordPress uploaded content managing feature, or
# upload the content to our host manually.

jrochkind found the WordPress content managing feature to be more of a pain than it was worth, so is uploading content manually. To do that, sftp to c4ljeditor@login.ibiblio.org. Ask jrochkind for the password for the c4ljeditor account (or see this [http://groups.google.com/group/c4lj-articles/msg/fad004416f12ac25 post] on c4lj-articles).

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

in there you'll find an "issue1" subdir (or issueX subdir--if you don't, create one or ask for help creating one!). Inside THERE, create a subdir with the last name of the first author, and put all your image and other attached content in there. It will now have this sort of url:
http://journal.code4lib.org/media/issue1/smith/imagename.png

Add to your img src or a href's as desired. You can use this not just for images, but for extended code attachments, etc.

===Code===

Put all code in <code><pre></code> tags.

====Code Highlighting====

If the code is in a supported language, we can do syntax highlighting.

ibiblio has a PHPS extensionm, so if you an "s" on the end of .php files, e.g.,
<filename>.phps
it does syntax highlighting for you.

We're still deciding if we like the syntax highlighting, don't feel compelled to make it work if it's not working for you (but please let other editors know what your experience is). To make this work, you still wrap your code in <code><pre></code> tags. Inside of the <code><pre></code> tags, but around your code, include
[sourcecode language='langcode']...[/sourcecode]

Replace <code>langcode</code> with the appropriate code from the following list (if more than one option for a language, any one will work).

{|
!Language!!Code
|-
|C++||cpp, c, c++
|-
|C#||c#, c-sharp, csharp
|-
|CSS||css
|-
|Delphi||delphi, pascal
|-
|Java||java
|-
|JavaScript||js, jscript, javascript
|-
|PHP||php
|-
|Python||py, python
|-
|Ruby||rb, ruby, rails, ror
|-
|SQL||sql
|-
|VB||vb, vb.net
|-
|XML/HTML||xml, html, xhtml, xslt
|}

Example:
<pre>[sourcecode language='css']body {
font-size: 0.625em;
background-color: #0000ff;
color: #ffff00;
}[/sourcecode]</pre>

==Abstract==

While you are editing the article, there is a box labeled "Optional Excerpt" a little ways below the "Post" field. Put the abstract here. Use HTML markup as appropriate. What you put in this field is what will be distributed in our syndication feed and what will appear before the article as the abstract.

Assigned editors are ultimately responsible for a good abstract. Authors aren't always the best at writing good abstracts for their articles, you should probably revise or even write a new one from scratch as necessary, even when the author has provided one. Some of the abstracts for my assigned articles haven't even mentioned what I consider the most significant features of the article.

Since indexes (like EBSCO) may end up indexing abstracts and not full text (and even full text indexes may weigh abstracts more highly), the abstract should probably include any important terms that should 'hit' on the article, such as key technologies or concepts.

I've found that extracting sentences or clauses from the article itself is a good way to build an abstract that will represent the article as the authors intended. The conclusion section is often a good place to look for such key sentences/clauses.

Final abstracts should be passed by the authors for approval.

==Bibliographies/Endnotes==
We would like to provide COinS information with every appropriate citation that does not have a publically accessible url.
* Recommended COinS generator: http://generator.ocoins.info/
* Another option is to use the WP COinS plugin. Open the Code tab, put the cursor before the citation, and click COinS. Enter the appropriate information. This works so-so for journals, and not at all for books.
* COinS should really always have an ISSN or ISBN.
* Inside the span tag, put the string "(COinS)" with a link to our coins explanation page. Ie:

<pre><a href="http://journal.code4lib.org/coins">(COinS)</a></pre>

This is so the user without a browser extension will see that something is there she might be interested in, and get an explanation of COinS and how to make use of it.

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

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

==Author Information==

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

End each article with a second-level header that says "About the Author(s)", with class="abouttheauthor" set. Then give a short paragraph about each author. We do want to have some kind of contact information published (personal web page, email address (obscured if desired), etc.) for each author.

There is a box beneath the article-editing box with the label "Author(s)". Anything you put in this field will be treated as the author of the article. This will show up in the ToC and in the syndication feeds. If you don't populate this field, WordPress will use the username of the editor, instead.

==Categories/Tags==
Posts will have "Uncagetorized" checked by default. Uncheck that box, and check the box next to the current issue, which will be a subcategory of "Issues." Do not check the "Issues" category. We generally do not add tags, except for Conference reviews

==WordPress Buttons==

;Save
:Saves the article, sets the post status to whatever option is selected in the Publish Status form.
;Publish
:Saves the article, sets the post status to Pending Review and assigns a timestamp to the article.

If an issue is not yet published, setting the post status to "Published" or clicking the "Publish" button will set the article to "Pending Review" status. If the issue is already published, this would actually publish the article.

==WordPress Post Status==
An article has four possible statuses. However, only the first three statuses are available to editors.
;Draft
:Use for not yet complete articles. Only editors can see these.
;Pending Review
:Use for sharing the article with authors. Editors and anyone logged in with user ID 17 (i.e., the author account) can see these. See this [http://groups.google.com/group/c4lj-articles/browse_thread/thread/1231b06c09f1289f post] on c4lj-articles for the login information for the author account (username: author).
;Private
:We don't use this option anymore.
;Published
:A published post is visible to everyone. It is part of the RSS feed. If you're editing an already published post, don't select anything in the post status form, just hit Save.

==Publishing an Issue==

# Let everyone on the c4lj-articles list know you are getting ready to publish (so they can save and close any open articles).
# Log in to WordPress
# Make sure that all articles for the issue have the correct issue category selected and have been set to 'Pending Review'. Make sure that the "Uncategorized" and "Issues" categories are unchecked (only the specific issue should be selected).
# Sanity check: count the number of posts which should appear in the publish list
# Click on Posts -> Issues (on the left side)
# Click on "Publish" for the issue you'd like to publish.
## You'll get a list of every "Pending Review" article in that issue. Make sure the number of articles in the list matches your previous count. Don't see all the articles you think you should see? They could be still in Draft status, or not in the correct Issue category, or still have "Uncategorized" selected, or someone may still have it in edit mode. Go back to the posts list and make any necessary changes, and start from #5 again.
# Drag and drop the article titles until they're in the order you want. The order you see there is the order you'll see on the home page (and probably the opposite of the order you'll see in your feed reader).
## Note: It's the coordinating editor's responsibility to decide what order he or she would like the articles to show up in, and order them appropriately when publishing the issue. In general, we try to put the articles with the widest appeal first, and special types (columns, special reports, book reviews, etc.) at the end.
# Click "Publish Issue" (optionally setting the publication time, first). Setting the time should only have an impact on readers who are not logged into the c4lj site. Editors will be able to see the published articles.
# Go to the Journal front page; check the number of articles is correct (again) and that they are in the right order. If there is a problem, go back to the admin interface, click on Posts -> Issues and click Unpublish for the issue. Make whatever corrections are needed and proceed from #5 again.
# Once the issue is finally published, go to [[Code4Lib_Journal_Entries_in_Directory_of_Open_Access_Journals]] and follow the directions to upload the issue metadata to DOAJ.
# Send out announcements (see [[Code4Lib_Journal_Publicity_Venues]])

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

[[Category:Code4Lib Journal]]

Code4Lib Journal and EBSCO

2010-03-24T18:57:00Z

Tomkeays:

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

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

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

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

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

[[Category: Code4Lib Journal]]

Code4Lib Journal WordPress Input Guidelines

2010-03-19T12:34:07Z

Tomkeays: /* The WP Admin Interface */