https://wiki.code4lib.org/api.php?action=feedcontributions&feedformat=atom&user=Cdmo 2026-04-23T21:57:26Z User contributions MediaWiki 1.26.2 https://wiki.code4lib.org/index.php?title=2016_Conference_Committees&diff=43622 2015-11-09T12:38:33Z

<p>Cdmo: /* Website Working Group */</p> <hr /> <div>= Code4Lib 2016 Committees =<br /> <br /> ''Many hands make for light work.''<br /> <br /> Hosting a conference is incredibly complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2016 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.<br /> <br /> We will assign a local contact (LPC) to each committee.<br /> <br /> == Location and Dates ==<br /> <br /> * Location: Old City District of Philadelphia, PA<br /> * Dates: March 7-10, 2016<br /> ** Pre-conferences - <br /> ** Main meeting - <br /> ** Post conference activities?<br /> <br /> == Local Planning Committee ==<br /> 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.<br /> <br /> * David Lacy (Villanova) - Primary Contact (v)<br /> * Chad Nelson - Secondary Contact (v)<br /> * Anna Headley (Chemical Heritage Foundation) - Documentarian (v)<br /> * [[User:Sdellis|Shaun Ellis]] (Princeton) (v)<br /> * Katherine Lynch (Temple) (v)<br /> * Stephen Ng (Temple)<br /> * Brett Bonfield (Collingswood Public)<br /> * Lauren Gala (UPenn)<br /> * David Uspal (Villanova) (v)<br /> * Chris Clement (Drexel)<br /> <br /> == Website Working Group ==<br /> 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). <br /> <br /> [[Website Working Group Documents|Website Working Group Documents]]<br /> <br /> * Shaun Ellis (Princeton) - Primary Contact<br /> * [[User:LukeAeschleman| Luke Aeschleman]] (UNC - Chapel Hill | Health Sciences Library) - Secondary Contact<br /> * [[User:jtidal|Junior Tidal]] (New York City College of Technology)<br /> * [[User:BillMcMillin|Bill McMillin]] (Pratt Institute) - Documentarian<br /> * [[User:Sdellis|Shaun Ellis]] (Princeton) - LPC Contact (v)<br /> * [[User:Phette23|Eric Phetteplace]] (Cal College of the Arts)<br /> * [[User:Sarahshealy| Sarah Shealy]] (Greenville (SC) County Public Library)<br /> * [[User:JennC| Jennifer Colt]] (Cornell University Library)<br /> * [[User:LaurenAjamie| Lauren Ajamie]] (University of Notre Dame Library)<br /> * [[User:MichaelSchofield| Michael Schofield]] ( @schoeyfield )<br /> * [[User:Wickr|Ryan Wick]]<br /> * [[User:cbeer|Chris Beer]]<br /> * [[User:Cdmo|Charlie Morris]] (Penn State)<br /> <br /> == Sponsorship Committee ==<br /> This group will focus on making sure all who want to support the conference have the opportunity to do so. Sponsorship Committee work involves working with the LPC to close budget gaps and talking to potential sponsors to find the level that is right for them. <br /> <br /> The Sponsorship committee meets every other Tuesday at 2pm EST (11am PST) via [https://plus.google.com/hangouts/_/gwibrfqhzxe23uto4me3tktbnia Google hangout]. <br /> <br /> * [[User:Sdellis|Shaun Ellis]] (Princeton) (v)<br /> * David Uspal (Villanova) - LPC Contact (v)<br /> * Chad Nelson<br /> * Morgan McKeehan<br /> * Ray Schwartz<br /> * Sharon Whitfield (Rowan University)<br /> * Brett Bonfield (Collingswood Public) (v)<br /> * Katherine Lynch (Temple University)<br /> * Rachel Trent (George Washington University)<br /> <br /> == Keynote Committee ==<br /> 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.<br /> <br /> * Brett Bonfield (Collingswood Public)<br /> * John Mignault (ESDN/METRO)<br /> * Emily Morton-Owens<br /> * [[User:Phette23|Eric Phetteplace]]<br /> * Whitni Watkins (St. Lawrence University)<br /> * Beatrice Pulliam (Providence Public)<br /> <br /> == Pre-conference Committee ==<br /> 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.<br /> * Anna Headley - Chemical Heritage Foundation (Local Contact)<br /> * [[User:ChristinaHarlow|Christina Harlow]] - convener<br /> * Eric Lease Morgan - Librarian-At-Large<br /> * Andrea Schurr - Univ. of TN at Chattanooga<br /> * [[User:AndyWeidner|Andy Weidner]] - Univ. of Houston<br /> <br /> [[Preconference2016Workspace]]<br /> <br /> == Program Committee == <br /> 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.<br /> * David Lacy - Villanova (Local Contact)<br /> * Kevin Beswick - NCSU<br /> * Peter Murray - Cherry HIll Company<br /> * Chris Beer - Stanford University Libraries<br /> * Matt Sherman - University of Bridgeport<br /> * Whitni Watkins - St. Lawrence University<br /> * Ben Armintor - Columbia University<br /> * Ranti Junus - Michigan State University<br /> * Katherine Lynch - Temple University<br /> * Tod Olson - University of Chicago<br /> <br /> == Scholarship Committee ==<br /> 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.<br /> * Chad Nelson (Local Contact)<br /> * [[User:jtidal|Junior Tidal]] (New York City College of Technology)<br /> * Linda Ballinger (Penn State)<br /> * Mairelys Lemus-Rojas (University of Miami Libraries)<br /> * Spencer Lamm (Drexel University)<br /> * Lauren Gala (U Penn)<br /> * Bohyun Kim (U Maryland, Baltimore)<br /> * Dan Kerchner (George Washington University)<br /> <br /> == Childcare Committee == <br /> This group assess the need for childcare at the conference, organizes childcare options, determines cost, and liaises with parents and chilcare providers<br /> * Chad Nelson (Local Contact)<br /> <br /> <br /> == Additional Committees... Coming Soon! ==<br /> * Book Give-Away<br /> * Onsite Volunteer<br /> * Social Activities<br /> * Streaming Video<br /> * T-Shirt<br /> * Voting<br /> * Whatever<br /> * Wifi/Electrical<br /> * IRC<br /> * Reception?<br /> * Accessibility<br /> <br /> [[Category:Code4Lib2016]]</div>

Cdmo https://wiki.code4lib.org/index.php?title=Conference_Site_Users:_Goals_and_Interactions&diff=43030 2015-05-11T02:00:01Z

<p>Cdmo: /* Speakers (Keynote, Standard, Lightning Talks) */</p> <hr /> <div>==Conference Organizers &amp; Committees==<br /> *Pre-conference<br /> **Build out the site<br /> **Collect feedback from potential conference-goers<br /> *Peri-conference<br /> **Make crucial information changes quickly and easily<br /> **Collect time-sensitive feedback from conference-goers<br /> *Post-conference<br /> **Post slides, video and any other related content for archive purposes<br /> **Review Feedback and pass on to future hosts<br /> **Review Site Use and Page Views<br /> <br /> ==Speakers (Keynote, Standard, Lightning Talks)==<br /> *Pre-conference<br /> **Submit standard talk proposals<br /> **View status of proposal<br /> **Find info on date, location, conference and room setup (coffee, wifi, food), conference cost, hotel cost (wifi add'l cost?), transportation cost<br /> **Understand exactly how lightning talks will be organized and how submissions will occur<br /> **Keynote speakers will probably view the site for general info about what code4lib and the code4lib conference is exactly<br /> *Peri-conference<br /> **Update event/session information<br /> **Sign Up for Lightning Talk <br /> **Know where lightning talks are being held and what the order is<br /> *Post-conference<br /> **Add links, slides, content<br /> **Not sure speakers need the site much post conference<br /> <br /> ==On-Site Volunteers==<br /> <br /> *Pre-conference<br /> **Understand how they can help and what jobs need to be done<br /> **Sign up<br /> **Schedule shifts<br /> **Find out more about duties/tasks to be completed<br /> *Peri-conference<br /> **Coordinate with organizers<br /> **Find contact info for organizers/other volunteers<br /> *Post-conference<br /> <br /> ==On-Site Attendees==<br /> *Pre-conference<br /> **Learn about speakers and presentation topics<br /> **Vote on speakers/presentations<br /> **View final list of speakers and presentations<br /> **Submit T-Shirt Designs<br /> **Vote on T-Shirt Designs<br /> **Complete all registration procedures<br /> ***Register for conference<br /> ***Register for pre-conference workshops/events<br /> **Prepare travel arrangements<br /> ***How to get from airport/train stations to conference site<br /> ***Find recommended and/or nearby hotels<br /> ***Estimate food costs (conference provided?) and/or nearby restaurants (low-mid-high)<br /> *Peri-conference<br /> **Navigate Conference center<br /> ***Request help via website (optional)<br /> ***Online map<br /> **Comment and Converse <br /> ***Find twitter handle to live tweet<br /> ***View twitter stream<br /> ***Brief instructions for getting on IRC channel<br /> **View schedule (optimize for mobile devices)<br /> ***By track/event type<br /> ***Log in and save to personal itinerary (optional)<br /> **Social/Extra Events<br /> ***Find listings<br /> ***Propose/add an event<br /> ****Add/edit event info<br /> ***Sign up<br /> *Post-conference<br /> **Revisit Presentations<br /> ***Watch recordings of presentations<br /> ***Get presentation slides<br /> ***Contact speakers<br /> ***Tag Presentations<br /> ***Share presentation with others<br /> **Provide Feedback<br /> ***...about individual sessions<br /> ***...about conference (facilities, overall opinion, etc)<br /> <br /> ==Remote Attendees==<br /> *Pre-conference<br /> **Decide which sessions to attend remotely<br /> ***Review all sessions (titles, abstracts, speakers)<br /> ***Instructions to download software/plugins (if needed)<br /> **Notifications<br /> ***Option 1: Add wanted sessions to personal calendar (opt-in notification)<br /> ***Option 2: push notifications via email (requires user to register for specific sessions)<br /> *Peri-conference<br /> **View schedule (optimize for mobile devices)<br /> ***By track/event type<br /> ***Log in and save to personal itinerary (optional)<br /> **View session remotely<br /> ***Instructions to download software/plugins (if needed)<br /> ***Links to remote sessions<br /> **Social media<br /> ***Find twitter handle to live tweet<br /> ***View twitter stream<br /> *Post-conference<br /> **Revisit Presentations (see on-site for details)<br /> **Provide Feedback<br /> ***...about individual sessions<br /> ***...about remote experience<br /> <br /> ==Sponsors==<br /> *Pre-conference<br /> ** Evaluate the ROI for sponsorship:<br /> *** who is the audience and do they need our product/services? <br /> *** who are/have the speakers been?<br /> *** what are the goals, uniqueness, and the overall vibe of the conference?<br /> ** Determine appropriate level of sponsorship for me or my org.<br /> ** Make a pledge or a contribution online<br /> *** Make a general contribution<br /> *** Make a directed contribution<br /> ** Contact someone with further questions or to make a larger contribution<br /> ** Submit my logo/blurb for inclusion on site/materials<br /> <br /> *Peri-conference<br /> ** Appropriate visibility on site <br /> ** Appreciation expressed<br /> <br /> *Post-conference<br /> ** Provide Feedback<br /> *** ... about what we could do better<br /> *** ... about new business generated through conference</div>

Cdmo https://wiki.code4lib.org/index.php?title=Conference_Site_Users:_Goals_and_Interactions&diff=43029 2015-05-11T01:59:36Z

<p>Cdmo: deleting editorializing</p> <hr /> <div>==Conference Organizers &amp; Committees==<br /> *Pre-conference<br /> **Build out the site<br /> **Collect feedback from potential conference-goers<br /> *Peri-conference<br /> **Make crucial information changes quickly and easily<br /> **Collect time-sensitive feedback from conference-goers<br /> *Post-conference<br /> **Post slides, video and any other related content for archive purposes<br /> **Review Feedback and pass on to future hosts<br /> **Review Site Use and Page Views<br /> <br /> ==Speakers (Keynote, Standard, Lightning Talks)==<br /> *Pre-conference<br /> **Submit standard talk proposals<br /> **View status of proposal<br /> **Find info on date, location, conference and room setup (coffee, wifi, food), conference cost, hotel cost (wifi add'l cost?), transportation cost<br /> **Understand exactly how lightning talks will be organized and how submissions will occur<br /> **Keynote speakers will probably view the site for general info about what code4lib and the code4lib conference is exactly<br /> *Peri-conference<br /> **Update event/session information<br /> **Sign Up for Lightning Talk (maybe, right? -Charlie)<br /> **Know where lightning talks are being held and what the order is<br /> *Post-conference<br /> **Add links, slides, content (will speakers be doing that themselves or will they be sending that on to conference organizers? -Charlie)<br /> **Not sure speakers need the site much post conference<br /> <br /> ==On-Site Volunteers==<br /> <br /> *Pre-conference<br /> **Understand how they can help and what jobs need to be done<br /> **Sign up<br /> **Schedule shifts<br /> **Find out more about duties/tasks to be completed<br /> *Peri-conference<br /> **Coordinate with organizers<br /> **Find contact info for organizers/other volunteers<br /> *Post-conference<br /> <br /> ==On-Site Attendees==<br /> *Pre-conference<br /> **Learn about speakers and presentation topics<br /> **Vote on speakers/presentations<br /> **View final list of speakers and presentations<br /> **Submit T-Shirt Designs<br /> **Vote on T-Shirt Designs<br /> **Complete all registration procedures<br /> ***Register for conference<br /> ***Register for pre-conference workshops/events<br /> **Prepare travel arrangements<br /> ***How to get from airport/train stations to conference site<br /> ***Find recommended and/or nearby hotels<br /> ***Estimate food costs (conference provided?) and/or nearby restaurants (low-mid-high)<br /> *Peri-conference<br /> **Navigate Conference center<br /> ***Request help via website (optional)<br /> ***Online map<br /> **Comment and Converse <br /> ***Find twitter handle to live tweet<br /> ***View twitter stream<br /> ***Brief instructions for getting on IRC channel<br /> **View schedule (optimize for mobile devices)<br /> ***By track/event type<br /> ***Log in and save to personal itinerary (optional)<br /> **Social/Extra Events<br /> ***Find listings<br /> ***Propose/add an event<br /> ****Add/edit event info<br /> ***Sign up<br /> *Post-conference<br /> **Revisit Presentations<br /> ***Watch recordings of presentations<br /> ***Get presentation slides<br /> ***Contact speakers<br /> ***Tag Presentations<br /> ***Share presentation with others<br /> **Provide Feedback<br /> ***...about individual sessions<br /> ***...about conference (facilities, overall opinion, etc)<br /> <br /> ==Remote Attendees==<br /> *Pre-conference<br /> **Decide which sessions to attend remotely<br /> ***Review all sessions (titles, abstracts, speakers)<br /> ***Instructions to download software/plugins (if needed)<br /> **Notifications<br /> ***Option 1: Add wanted sessions to personal calendar (opt-in notification)<br /> ***Option 2: push notifications via email (requires user to register for specific sessions)<br /> *Peri-conference<br /> **View schedule (optimize for mobile devices)<br /> ***By track/event type<br /> ***Log in and save to personal itinerary (optional)<br /> **View session remotely<br /> ***Instructions to download software/plugins (if needed)<br /> ***Links to remote sessions<br /> **Social media<br /> ***Find twitter handle to live tweet<br /> ***View twitter stream<br /> *Post-conference<br /> **Revisit Presentations (see on-site for details)<br /> **Provide Feedback<br /> ***...about individual sessions<br /> ***...about remote experience<br /> <br /> ==Sponsors==<br /> *Pre-conference<br /> ** Evaluate the ROI for sponsorship:<br /> *** who is the audience and do they need our product/services? <br /> *** who are/have the speakers been?<br /> *** what are the goals, uniqueness, and the overall vibe of the conference?<br /> ** Determine appropriate level of sponsorship for me or my org.<br /> ** Make a pledge or a contribution online<br /> *** Make a general contribution<br /> *** Make a directed contribution<br /> ** Contact someone with further questions or to make a larger contribution<br /> ** Submit my logo/blurb for inclusion on site/materials<br /> <br /> *Peri-conference<br /> ** Appropriate visibility on site <br /> ** Appreciation expressed<br /> <br /> *Post-conference<br /> ** Provide Feedback<br /> *** ... about what we could do better<br /> *** ... about new business generated through conference</div>

Cdmo https://wiki.code4lib.org/index.php?title=Conference_Site_Users:_Goals_and_Interactions&diff=43028 2015-05-11T01:56:56Z

<p>Cdmo: /* On-Site Volunteers */</p> <hr /> <div>==Conference Organizers &amp; Committees==<br /> *Pre-conference<br /> **Build out the site<br /> **Collect feedback from potential conference-goers<br /> *Peri-conference<br /> **Make crucial information changes quickly and easily<br /> **Collect time-sensitive feedback from conference-goers<br /> *Post-conference<br /> **Post slides, video and any other related content for archive purposes<br /> **Review Feedback and pass on to future hosts<br /> **Review Site Use and Page Views<br /> <br /> ==Speakers (Keynote, Standard, Lightning Talks)==<br /> *Pre-conference<br /> **Submit standard talk proposals<br /> **View status of proposal (are we talking about the voting results or something else? the diebold-o-tron handles all that... - Charlie)<br /> **Find info on date, location, conference and room setup (coffee, wifi, food), conference cost, hotel cost (wifi add'l cost?), transportation cost<br /> **Understand exactly how lightning talks will be organized and how submissions will occur (website, paper, etc. for the conf. organizers to determine)<br /> **Keynote speakers will probably view the site for general info about what code4lib and the code4lib conference is exactly<br /> *Peri-conference<br /> **Update event/session information (speakers would do this via conference organizers, I think -Charlie)<br /> **Sign Up for Lightning Talk (maybe, right? -Charlie)<br /> **Know where lightning talks are being held and what the order is<br /> *Post-conference<br /> **Add links, slides, content (will speakers be doing that themselves or will they be sending that on to conference organizers? -Charlie)<br /> **Not sure speakers need the site much post conference<br /> <br /> ==On-Site Volunteers==<br /> <br /> *Pre-conference<br /> **Understand how they can help and what jobs need to be done<br /> **Sign up<br /> **Schedule shifts<br /> **Find out more about duties/tasks to be completed<br /> *Peri-conference<br /> **Coordinate with organizers<br /> **Find contact info for organizers/other volunteers<br /> *Post-conference<br /> <br /> ==On-Site Attendees==<br /> *Pre-conference<br /> **Learn about speakers and presentation topics<br /> **Vote on speakers/presentations<br /> **View final list of speakers and presentations<br /> **Submit T-Shirt Designs<br /> **Vote on T-Shirt Designs<br /> **Complete all registration procedures<br /> ***Register for conference<br /> ***Register for pre-conference workshops/events<br /> **Prepare travel arrangements<br /> ***How to get from airport/train stations to conference site<br /> ***Find recommended and/or nearby hotels<br /> ***Estimate food costs (conference provided?) and/or nearby restaurants (low-mid-high)<br /> *Peri-conference<br /> **Navigate Conference center<br /> ***Request help via website (optional)<br /> ***Online map<br /> **Comment and Converse <br /> ***Find twitter handle to live tweet<br /> ***View twitter stream<br /> ***Brief instructions for getting on IRC channel<br /> **View schedule (optimize for mobile devices)<br /> ***By track/event type<br /> ***Log in and save to personal itinerary (optional)<br /> **Social/Extra Events<br /> ***Find listings<br /> ***Propose/add an event<br /> ****Add/edit event info<br /> ***Sign up<br /> *Post-conference<br /> **Revisit Presentations<br /> ***Watch recordings of presentations<br /> ***Get presentation slides<br /> ***Contact speakers<br /> ***Tag Presentations<br /> ***Share presentation with others<br /> **Provide Feedback<br /> ***...about individual sessions<br /> ***...about conference (facilities, overall opinion, etc)<br /> <br /> ==Remote Attendees==<br /> *Pre-conference<br /> **Decide which sessions to attend remotely<br /> ***Review all sessions (titles, abstracts, speakers)<br /> ***Instructions to download software/plugins (if needed)<br /> **Notifications<br /> ***Option 1: Add wanted sessions to personal calendar (opt-in notification)<br /> ***Option 2: push notifications via email (requires user to register for specific sessions)<br /> *Peri-conference<br /> **View schedule (optimize for mobile devices)<br /> ***By track/event type<br /> ***Log in and save to personal itinerary (optional)<br /> **View session remotely<br /> ***Instructions to download software/plugins (if needed)<br /> ***Links to remote sessions<br /> **Social media<br /> ***Find twitter handle to live tweet<br /> ***View twitter stream<br /> *Post-conference<br /> **Revisit Presentations (see on-site for details)<br /> **Provide Feedback<br /> ***...about individual sessions<br /> ***...about remote experience<br /> <br /> ==Sponsors==<br /> *Pre-conference<br /> ** Evaluate the ROI for sponsorship:<br /> *** who is the audience and do they need our product/services? <br /> *** who are/have the speakers been?<br /> *** what are the goals, uniqueness, and the overall vibe of the conference?<br /> ** Determine appropriate level of sponsorship for me or my org.<br /> ** Make a pledge or a contribution online<br /> *** Make a general contribution<br /> *** Make a directed contribution<br /> ** Contact someone with further questions or to make a larger contribution<br /> ** Submit my logo/blurb for inclusion on site/materials<br /> <br /> *Peri-conference<br /> ** Appropriate visibility on site <br /> ** Appreciation expressed<br /> <br /> *Post-conference<br /> ** Provide Feedback<br /> *** ... about what we could do better<br /> *** ... about new business generated through conference</div>

Cdmo https://wiki.code4lib.org/index.php?title=Conference_Site_Users:_Goals_and_Interactions&diff=43027 2015-05-11T01:49:25Z

<p>Cdmo: /* On-Site Volunteers */</p> <hr /> <div>==Conference Organizers &amp; Committees==<br /> *Pre-conference<br /> **Build out the site<br /> **Collect feedback from potential conference-goers<br /> *Peri-conference<br /> **Make crucial information changes quickly and easily<br /> **Collect time-sensitive feedback from conference-goers<br /> *Post-conference<br /> **Post slides, video and any other related content for archive purposes<br /> **Review Feedback and pass on to future hosts<br /> **Review Site Use and Page Views<br /> <br /> ==Speakers (Keynote, Standard, Lightning Talks)==<br /> *Pre-conference<br /> **Submit standard talk proposals<br /> **View status of proposal (are we talking about the voting results or something else? the diebold-o-tron handles all that... - Charlie)<br /> **Find info on date, location, conference and room setup (coffee, wifi, food), conference cost, hotel cost (wifi add'l cost?), transportation cost<br /> **Understand exactly how lightning talks will be organized and how submissions will occur (website, paper, etc. for the conf. organizers to determine)<br /> **Keynote speakers will probably view the site for general info about what code4lib and the code4lib conference is exactly<br /> *Peri-conference<br /> **Update event/session information (speakers would do this via conference organizers, I think -Charlie)<br /> **Sign Up for Lightning Talk (maybe, right? -Charlie)<br /> **Know where lightning talks are being held and what the order is<br /> *Post-conference<br /> **Add links, slides, content (will speakers be doing that themselves or will they be sending that on to conference organizers? -Charlie)<br /> **Not sure speakers need the site much post conference<br /> <br /> ==On-Site Volunteers==<br /> <br /> From Charlie: a general question, is the conference site expected to be the volunteer organizing tool too? seems out of scope to me, but I could be wrong!<br /> <br /> *Pre-conference<br /> **Understand how they can help and what jobs need to be done<br /> **Sign up<br /> **Schedule shifts<br /> **Find out more about duties/tasks to be completed<br /> *Peri-conference<br /> **Coordinate with organizers<br /> **Find contact info for organizers/other volunteers<br /> *Post-conference<br /> <br /> ==On-Site Attendees==<br /> *Pre-conference<br /> **Learn about speakers and presentation topics<br /> **Vote on speakers/presentations<br /> **View final list of speakers and presentations<br /> **Submit T-Shirt Designs<br /> **Vote on T-Shirt Designs<br /> **Complete all registration procedures<br /> ***Register for conference<br /> ***Register for pre-conference workshops/events<br /> **Prepare travel arrangements<br /> ***How to get from airport/train stations to conference site<br /> ***Find recommended and/or nearby hotels<br /> ***Estimate food costs (conference provided?) and/or nearby restaurants (low-mid-high)<br /> *Peri-conference<br /> **Navigate Conference center<br /> ***Request help via website (optional)<br /> ***Online map<br /> **Comment and Converse <br /> ***Find twitter handle to live tweet<br /> ***View twitter stream<br /> ***Brief instructions for getting on IRC channel<br /> **View schedule (optimize for mobile devices)<br /> ***By track/event type<br /> ***Log in and save to personal itinerary (optional)<br /> **Social/Extra Events<br /> ***Find listings<br /> ***Propose/add an event<br /> ****Add/edit event info<br /> ***Sign up<br /> *Post-conference<br /> **Revisit Presentations<br /> ***Watch recordings of presentations<br /> ***Get presentation slides<br /> ***Contact speakers<br /> ***Tag Presentations<br /> ***Share presentation with others<br /> **Provide Feedback<br /> ***...about individual sessions<br /> ***...about conference (facilities, overall opinion, etc)<br /> <br /> ==Remote Attendees==<br /> *Pre-conference<br /> **Decide which sessions to attend remotely<br /> ***Review all sessions (titles, abstracts, speakers)<br /> ***Instructions to download software/plugins (if needed)<br /> **Notifications<br /> ***Option 1: Add wanted sessions to personal calendar (opt-in notification)<br /> ***Option 2: push notifications via email (requires user to register for specific sessions)<br /> *Peri-conference<br /> **View schedule (optimize for mobile devices)<br /> ***By track/event type<br /> ***Log in and save to personal itinerary (optional)<br /> **View session remotely<br /> ***Instructions to download software/plugins (if needed)<br /> ***Links to remote sessions<br /> **Social media<br /> ***Find twitter handle to live tweet<br /> ***View twitter stream<br /> *Post-conference<br /> **Revisit Presentations (see on-site for details)<br /> **Provide Feedback<br /> ***...about individual sessions<br /> ***...about remote experience<br /> <br /> ==Sponsors==<br /> *Pre-conference<br /> ** Evaluate the ROI for sponsorship:<br /> *** who is the audience and do they need our product/services? <br /> *** who are/have the speakers been?<br /> *** what are the goals, uniqueness, and the overall vibe of the conference?<br /> ** Determine appropriate level of sponsorship for me or my org.<br /> ** Make a pledge or a contribution online<br /> *** Make a general contribution<br /> *** Make a directed contribution<br /> ** Contact someone with further questions or to make a larger contribution<br /> ** Submit my logo/blurb for inclusion on site/materials<br /> <br /> *Peri-conference<br /> ** Appropriate visibility on site <br /> ** Appreciation expressed<br /> <br /> *Post-conference<br /> ** Provide Feedback<br /> *** ... about what we could do better<br /> *** ... about new business generated through conference</div>

Cdmo https://wiki.code4lib.org/index.php?title=Conference_Site_Users:_Goals_and_Interactions&diff=43026 2015-05-11T01:47:08Z

<p>Cdmo: /* Speakers (Keynote, Standard, Lightning Talks) */</p> <hr /> <div>==Conference Organizers &amp; Committees==<br /> *Pre-conference<br /> **Build out the site<br /> **Collect feedback from potential conference-goers<br /> *Peri-conference<br /> **Make crucial information changes quickly and easily<br /> **Collect time-sensitive feedback from conference-goers<br /> *Post-conference<br /> **Post slides, video and any other related content for archive purposes<br /> **Review Feedback and pass on to future hosts<br /> **Review Site Use and Page Views<br /> <br /> ==Speakers (Keynote, Standard, Lightning Talks)==<br /> *Pre-conference<br /> **Submit standard talk proposals<br /> **View status of proposal (are we talking about the voting results or something else? the diebold-o-tron handles all that... - Charlie)<br /> **Find info on date, location, conference and room setup (coffee, wifi, food), conference cost, hotel cost (wifi add'l cost?), transportation cost<br /> **Understand exactly how lightning talks will be organized and how submissions will occur (website, paper, etc. for the conf. organizers to determine)<br /> **Keynote speakers will probably view the site for general info about what code4lib and the code4lib conference is exactly<br /> *Peri-conference<br /> **Update event/session information (speakers would do this via conference organizers, I think -Charlie)<br /> **Sign Up for Lightning Talk (maybe, right? -Charlie)<br /> **Know where lightning talks are being held and what the order is<br /> *Post-conference<br /> **Add links, slides, content (will speakers be doing that themselves or will they be sending that on to conference organizers? -Charlie)<br /> **Not sure speakers need the site much post conference<br /> <br /> ==On-Site Volunteers==<br /> *Pre-conference<br /> **Sign up<br /> **Schedule shifts<br /> **Find out more about duties/tasks to be completed<br /> *Peri-conference<br /> **Coordinate with organizers<br /> **Find contact info for organizers/other volunteers<br /> *Post-conference<br /> <br /> ==On-Site Attendees==<br /> *Pre-conference<br /> **Learn about speakers and presentation topics<br /> **Vote on speakers/presentations<br /> **View final list of speakers and presentations<br /> **Submit T-Shirt Designs<br /> **Vote on T-Shirt Designs<br /> **Complete all registration procedures<br /> ***Register for conference<br /> ***Register for pre-conference workshops/events<br /> **Prepare travel arrangements<br /> ***How to get from airport/train stations to conference site<br /> ***Find recommended and/or nearby hotels<br /> ***Estimate food costs (conference provided?) and/or nearby restaurants (low-mid-high)<br /> *Peri-conference<br /> **Navigate Conference center<br /> ***Request help via website (optional)<br /> ***Online map<br /> **Comment and Converse <br /> ***Find twitter handle to live tweet<br /> ***View twitter stream<br /> ***Brief instructions for getting on IRC channel<br /> **View schedule (optimize for mobile devices)<br /> ***By track/event type<br /> ***Log in and save to personal itinerary (optional)<br /> **Social/Extra Events<br /> ***Find listings<br /> ***Propose/add an event<br /> ****Add/edit event info<br /> ***Sign up<br /> *Post-conference<br /> **Revisit Presentations<br /> ***Watch recordings of presentations<br /> ***Get presentation slides<br /> ***Contact speakers<br /> ***Tag Presentations<br /> ***Share presentation with others<br /> **Provide Feedback<br /> ***...about individual sessions<br /> ***...about conference (facilities, overall opinion, etc)<br /> <br /> ==Remote Attendees==<br /> *Pre-conference<br /> **Decide which sessions to attend remotely<br /> ***Review all sessions (titles, abstracts, speakers)<br /> ***Instructions to download software/plugins (if needed)<br /> **Notifications<br /> ***Option 1: Add wanted sessions to personal calendar (opt-in notification)<br /> ***Option 2: push notifications via email (requires user to register for specific sessions)<br /> *Peri-conference<br /> **View schedule (optimize for mobile devices)<br /> ***By track/event type<br /> ***Log in and save to personal itinerary (optional)<br /> **View session remotely<br /> ***Instructions to download software/plugins (if needed)<br /> ***Links to remote sessions<br /> **Social media<br /> ***Find twitter handle to live tweet<br /> ***View twitter stream<br /> *Post-conference<br /> **Revisit Presentations (see on-site for details)<br /> **Provide Feedback<br /> ***...about individual sessions<br /> ***...about remote experience<br /> <br /> ==Sponsors==<br /> *Pre-conference<br /> ** Evaluate the ROI for sponsorship:<br /> *** who is the audience and do they need our product/services? <br /> *** who are/have the speakers been?<br /> *** what are the goals, uniqueness, and the overall vibe of the conference?<br /> ** Determine appropriate level of sponsorship for me or my org.<br /> ** Make a pledge or a contribution online<br /> *** Make a general contribution<br /> *** Make a directed contribution<br /> ** Contact someone with further questions or to make a larger contribution<br /> ** Submit my logo/blurb for inclusion on site/materials<br /> <br /> *Peri-conference<br /> ** Appropriate visibility on site <br /> ** Appreciation expressed<br /> <br /> *Post-conference<br /> ** Provide Feedback<br /> *** ... about what we could do better<br /> *** ... about new business generated through conference</div>

Cdmo https://wiki.code4lib.org/index.php?title=Conference_Site_Users:_Goals_and_Interactions&diff=43025 2015-05-11T01:45:39Z

<p>Cdmo: /* Speakers (Keynote, Standard, Lightning Talks) */</p> <hr /> <div>==Conference Organizers &amp; Committees==<br /> *Pre-conference<br /> **Build out the site<br /> **Collect feedback from potential conference-goers<br /> *Peri-conference<br /> **Make crucial information changes quickly and easily<br /> **Collect time-sensitive feedback from conference-goers<br /> *Post-conference<br /> **Post slides, video and any other related content for archive purposes<br /> **Review Feedback and pass on to future hosts<br /> **Review Site Use and Page Views<br /> <br /> ==Speakers (Keynote, Standard, Lightning Talks)==<br /> *Pre-conference<br /> **Submit standard talk proposals<br /> **View status of proposal (are we talking about the voting results or something else? the diebold-o-tron handles all that... - Charlie)<br /> **Find info on date, location, conference and room setup (coffee, wifi, food), conference cost, hotel cost (wifi add'l cost?), transportation cost<br /> **Understand exactly how lightning talks will be organized and how submissions will occur (website, paper, etc. for the conf. organizers to determine)<br /> **Keynote speakers will probably view the site for general info about what code4lib and the code4lib conference is exactly<br /> *Peri-conference<br /> **Update event/session information<br /> **Sign Up for Lightning Talk (maybe, right? -Charlie)<br /> **Know where lightning talks are being held and what the order is<br /> *Post-conference<br /> **Add links, slides, content (will speakers be doing that themselves or will they be sending that on to conference organizers? -Charlie)<br /> **Not sure speakers need the site much post conference<br /> <br /> ==On-Site Volunteers==<br /> *Pre-conference<br /> **Sign up<br /> **Schedule shifts<br /> **Find out more about duties/tasks to be completed<br /> *Peri-conference<br /> **Coordinate with organizers<br /> **Find contact info for organizers/other volunteers<br /> *Post-conference<br /> <br /> ==On-Site Attendees==<br /> *Pre-conference<br /> **Learn about speakers and presentation topics<br /> **Vote on speakers/presentations<br /> **View final list of speakers and presentations<br /> **Submit T-Shirt Designs<br /> **Vote on T-Shirt Designs<br /> **Complete all registration procedures<br /> ***Register for conference<br /> ***Register for pre-conference workshops/events<br /> **Prepare travel arrangements<br /> ***How to get from airport/train stations to conference site<br /> ***Find recommended and/or nearby hotels<br /> ***Estimate food costs (conference provided?) and/or nearby restaurants (low-mid-high)<br /> *Peri-conference<br /> **Navigate Conference center<br /> ***Request help via website (optional)<br /> ***Online map<br /> **Comment and Converse <br /> ***Find twitter handle to live tweet<br /> ***View twitter stream<br /> ***Brief instructions for getting on IRC channel<br /> **View schedule (optimize for mobile devices)<br /> ***By track/event type<br /> ***Log in and save to personal itinerary (optional)<br /> **Social/Extra Events<br /> ***Find listings<br /> ***Propose/add an event<br /> ****Add/edit event info<br /> ***Sign up<br /> *Post-conference<br /> **Revisit Presentations<br /> ***Watch recordings of presentations<br /> ***Get presentation slides<br /> ***Contact speakers<br /> ***Tag Presentations<br /> ***Share presentation with others<br /> **Provide Feedback<br /> ***...about individual sessions<br /> ***...about conference (facilities, overall opinion, etc)<br /> <br /> ==Remote Attendees==<br /> *Pre-conference<br /> **Decide which sessions to attend remotely<br /> ***Review all sessions (titles, abstracts, speakers)<br /> ***Instructions to download software/plugins (if needed)<br /> **Notifications<br /> ***Option 1: Add wanted sessions to personal calendar (opt-in notification)<br /> ***Option 2: push notifications via email (requires user to register for specific sessions)<br /> *Peri-conference<br /> **View schedule (optimize for mobile devices)<br /> ***By track/event type<br /> ***Log in and save to personal itinerary (optional)<br /> **View session remotely<br /> ***Instructions to download software/plugins (if needed)<br /> ***Links to remote sessions<br /> **Social media<br /> ***Find twitter handle to live tweet<br /> ***View twitter stream<br /> *Post-conference<br /> **Revisit Presentations (see on-site for details)<br /> **Provide Feedback<br /> ***...about individual sessions<br /> ***...about remote experience<br /> <br /> ==Sponsors==<br /> *Pre-conference<br /> ** Evaluate the ROI for sponsorship:<br /> *** who is the audience and do they need our product/services? <br /> *** who are/have the speakers been?<br /> *** what are the goals, uniqueness, and the overall vibe of the conference?<br /> ** Determine appropriate level of sponsorship for me or my org.<br /> ** Make a pledge or a contribution online<br /> *** Make a general contribution<br /> *** Make a directed contribution<br /> ** Contact someone with further questions or to make a larger contribution<br /> ** Submit my logo/blurb for inclusion on site/materials<br /> <br /> *Peri-conference<br /> ** Appropriate visibility on site <br /> ** Appreciation expressed<br /> <br /> *Post-conference<br /> ** Provide Feedback<br /> *** ... about what we could do better<br /> *** ... about new business generated through conference</div>

Cdmo https://wiki.code4lib.org/index.php?title=Conference_Site_Users:_Goals_and_Interactions&diff=43024 2015-05-11T01:33:07Z

<p>Cdmo: speaker concerns</p> <hr /> <div>==Conference Organizers &amp; Committees==<br /> *Pre-conference<br /> **Build out the site<br /> **Collect feedback from potential conference-goers<br /> *Peri-conference<br /> **Make crucial information changes quickly and easily<br /> **Collect time-sensitive feedback from conference-goers<br /> *Post-conference<br /> **Post slides, video and any other related content for archive purposes<br /> **Review Feedback and pass on to future hosts<br /> **Review Site Use and Page Views<br /> <br /> ==Speakers (Keynote, Standard, Lightning Talks)==<br /> *Pre-conference<br /> **Submit Conference proposals<br /> **View status of proposal (are we talking about the voting results or something else? - Charlie)<br /> **Find info on date, location, conference and room setup (coffee, wifi, food), conference cost, hotel cost (wifi add'l cost?), transportation cost<br /> *Peri-conference<br /> **Update event/session information<br /> **Sign Up for Lightning Talk<br /> *Post-conference<br /> **Add links, slides, content<br /> <br /> ==On-Site Volunteers==<br /> *Pre-conference<br /> **Sign up<br /> **Schedule shifts<br /> **Find out more about duties/tasks to be completed<br /> *Peri-conference<br /> **Coordinate with organizers<br /> **Find contact info for organizers/other volunteers<br /> *Post-conference<br /> <br /> ==On-Site Attendees==<br /> *Pre-conference<br /> **Learn about speakers and presentation topics<br /> **Vote on speakers/presentations<br /> **View final list of speakers and presentations<br /> **Submit T-Shirt Designs<br /> **Vote on T-Shirt Designs<br /> **Complete all registration procedures<br /> ***Register for conference<br /> ***Register for pre-conference workshops/events<br /> **Prepare travel arrangements<br /> ***How to get from airport/train stations to conference site<br /> ***Find recommended and/or nearby hotels<br /> ***Estimate food costs (conference provided?) and/or nearby restaurants (low-mid-high)<br /> *Peri-conference<br /> **Navigate Conference center<br /> ***Request help via website (optional)<br /> ***Online map<br /> **Comment and Converse <br /> ***Find twitter handle to live tweet<br /> ***View twitter stream<br /> ***Brief instructions for getting on IRC channel<br /> **View schedule (optimize for mobile devices)<br /> ***By track/event type<br /> ***Log in and save to personal itinerary (optional)<br /> **Social/Extra Events<br /> ***Find listings<br /> ***Propose/add an event<br /> ****Add/edit event info<br /> ***Sign up<br /> *Post-conference<br /> **Revisit Presentations<br /> ***Watch recordings of presentations<br /> ***Get presentation slides<br /> ***Contact speakers<br /> ***Tag Presentations<br /> ***Share presentation with others<br /> **Provide Feedback<br /> ***...about individual sessions<br /> ***...about conference (facilities, overall opinion, etc)<br /> <br /> ==Remote Attendees==<br /> *Pre-conference<br /> **Decide which sessions to attend remotely<br /> ***Review all sessions (titles, abstracts, speakers)<br /> ***Instructions to download software/plugins (if needed)<br /> **Notifications<br /> ***Option 1: Add wanted sessions to personal calendar (opt-in notification)<br /> ***Option 2: push notifications via email (requires user to register for specific sessions)<br /> *Peri-conference<br /> **View schedule (optimize for mobile devices)<br /> ***By track/event type<br /> ***Log in and save to personal itinerary (optional)<br /> **View session remotely<br /> ***Instructions to download software/plugins (if needed)<br /> ***Links to remote sessions<br /> **Social media<br /> ***Find twitter handle to live tweet<br /> ***View twitter stream<br /> *Post-conference<br /> **Revisit Presentations (see on-site for details)<br /> **Provide Feedback<br /> ***...about individual sessions<br /> ***...about remote experience<br /> <br /> ==Sponsors==<br /> *Pre-conference<br /> ** Evaluate the ROI for sponsorship:<br /> *** who is the audience and do they need our product/services? <br /> *** who are/have the speakers been?<br /> *** what are the goals, uniqueness, and the overall vibe of the conference?<br /> ** Determine appropriate level of sponsorship for me or my org.<br /> ** Make a pledge or a contribution online<br /> *** Make a general contribution<br /> *** Make a directed contribution<br /> ** Contact someone with further questions or to make a larger contribution<br /> ** Submit my logo/blurb for inclusion on site/materials<br /> <br /> *Peri-conference<br /> ** Appropriate visibility on site <br /> ** Appreciation expressed<br /> <br /> *Post-conference<br /> ** Provide Feedback<br /> *** ... about what we could do better<br /> *** ... about new business generated through conference</div>

Cdmo https://wiki.code4lib.org/index.php?title=Conference_Site_Users:_Goals_and_Interactions&diff=43023 2015-05-11T01:24:04Z

<p>Cdmo: Made it a little more explicit than basic CRUD operations. They'll need that too.</p> <hr /> <div>==Conference Organizers &amp; Committees==<br /> *Pre-conference<br /> **Build out the site<br /> **Collect feedback from potential conference-goers<br /> *Peri-conference<br /> **Make crucial information changes quickly and easily<br /> **Collect time-sensitive feedback from conference-goers<br /> *Post-conference<br /> **Post slides, video and any other related content for archive purposes<br /> **Review Feedback and pass on to future hosts<br /> **Review Site Use and Page Views<br /> <br /> ==Speakers (Keynote, Standard, Lightning Talks)==<br /> *Pre-conference<br /> **Submit Conference proposals<br /> **View status of proposal<br /> **Find info on time/location of event<br /> *Peri-conference<br /> **Update event/session information<br /> **Sign Up for Lightning Talk<br /> *Post-conference<br /> **Add links, slides, content<br /> <br /> ==On-Site Volunteers==<br /> *Pre-conference<br /> **Sign up<br /> **Schedule shifts<br /> **Find out more about duties/tasks to be completed<br /> *Peri-conference<br /> **Coordinate with organizers<br /> **Find contact info for organizers/other volunteers<br /> *Post-conference<br /> <br /> ==On-Site Attendees==<br /> *Pre-conference<br /> **Learn about speakers and presentation topics<br /> **Vote on speakers/presentations<br /> **View final list of speakers and presentations<br /> **Submit T-Shirt Designs<br /> **Vote on T-Shirt Designs<br /> **Complete all registration procedures<br /> ***Register for conference<br /> ***Register for pre-conference workshops/events<br /> **Prepare travel arrangements<br /> ***How to get from airport/train stations to conference site<br /> ***Find recommended and/or nearby hotels<br /> ***Estimate food costs (conference provided?) and/or nearby restaurants (low-mid-high)<br /> *Peri-conference<br /> **Navigate Conference center<br /> ***Request help via website (optional)<br /> ***Online map<br /> **Comment and Converse <br /> ***Find twitter handle to live tweet<br /> ***View twitter stream<br /> ***Brief instructions for getting on IRC channel<br /> **View schedule (optimize for mobile devices)<br /> ***By track/event type<br /> ***Log in and save to personal itinerary (optional)<br /> **Social/Extra Events<br /> ***Find listings<br /> ***Propose/add an event<br /> ****Add/edit event info<br /> ***Sign up<br /> *Post-conference<br /> **Revisit Presentations<br /> ***Watch recordings of presentations<br /> ***Get presentation slides<br /> ***Contact speakers<br /> ***Tag Presentations<br /> ***Share presentation with others<br /> **Provide Feedback<br /> ***...about individual sessions<br /> ***...about conference (facilities, overall opinion, etc)<br /> <br /> ==Remote Attendees==<br /> *Pre-conference<br /> **Decide which sessions to attend remotely<br /> ***Review all sessions (titles, abstracts, speakers)<br /> ***Instructions to download software/plugins (if needed)<br /> **Notifications<br /> ***Option 1: Add wanted sessions to personal calendar (opt-in notification)<br /> ***Option 2: push notifications via email (requires user to register for specific sessions)<br /> *Peri-conference<br /> **View schedule (optimize for mobile devices)<br /> ***By track/event type<br /> ***Log in and save to personal itinerary (optional)<br /> **View session remotely<br /> ***Instructions to download software/plugins (if needed)<br /> ***Links to remote sessions<br /> **Social media<br /> ***Find twitter handle to live tweet<br /> ***View twitter stream<br /> *Post-conference<br /> **Revisit Presentations (see on-site for details)<br /> **Provide Feedback<br /> ***...about individual sessions<br /> ***...about remote experience<br /> <br /> ==Sponsors==<br /> *Pre-conference<br /> ** Evaluate the ROI for sponsorship:<br /> *** who is the audience and do they need our product/services? <br /> *** who are/have the speakers been?<br /> *** what are the goals, uniqueness, and the overall vibe of the conference?<br /> ** Determine appropriate level of sponsorship for me or my org.<br /> ** Make a pledge or a contribution online<br /> *** Make a general contribution<br /> *** Make a directed contribution<br /> ** Contact someone with further questions or to make a larger contribution<br /> ** Submit my logo/blurb for inclusion on site/materials<br /> <br /> *Peri-conference<br /> ** Appropriate visibility on site <br /> ** Appreciation expressed<br /> <br /> *Post-conference<br /> ** Provide Feedback<br /> *** ... about what we could do better<br /> *** ... about new business generated through conference</div>

Cdmo https://wiki.code4lib.org/index.php?title=User:Cdmo&diff=42986 2015-05-01T13:49:10Z

<p>Cdmo: </p> <hr /> <div>Charlie Morris&lt;br&gt;<br /> Lead Web Developer&lt;br&gt;<br /> Penn State Libraries&lt;br&gt;<br /> State College, PA&lt;br&gt;<br /> cdmorris22 at gmail</div>

Cdmo https://wiki.code4lib.org/index.php?title=April_23&diff=42971 2015-04-23T17:37:28Z

<p>Cdmo: /* Introductions */</p> <hr /> <div>[[Website Working Group Documents|→ Website Working Group Home]]<br /> <br /> == Introductions ==<br /> <br /> We did quick intros of who each of us is and why we are interested in being on this working group.<br /> <br /> '''Charlie'''<br /> * Lead developer at Penn State Libraries, leading team in a move from Adobe CQ5 to Drupal. Previously worked at NCSU Libraries. <br /> * Interested in this group to help make the conference site better<br /> <br /> '''Lauren'''<br /> * Electronics Resource Librarian at Notre Dame<br /> * Interested in improving the scheduling aspects of the site<br /> <br /> '''Junior'''<br /> * Web Services Librarian at NYC College of Technology, currently migrating a Drupal site from 6 to 7, using Twitter Bootstrap<br /> * Likes the community and wants to pitch in and help out<br /> <br /> '''Jenn'''<br /> * UX Designer for Cornell Libraries, front end coding <br /> <br /> '''Eric'''<br /> * Systems Librarian at California College of the Arts<br /> * Likes the community and wants to help, sees the site as functional but confusing<br /> <br /> '''Bill'''<br /> * Currently an Emerging Technologies librarian at Pratt<br /> * Wants to help out as the Documentarian and find out ways we can improve sustainability<br /> <br /> ==Brainstorming==<br /> <br /> ===What is wrong with the current site?===<br /> <br /> * Content is in several different places: the conference site, the wiki, external services. Leads to confusion.<br /> * People couldn't find the streaming channel in previous conferences<br /> * Confusing schedule matrices are a problem for all conference sites and we should spend time on getting this right for 2016<br /> * It isn't mobile-friendly, the fact that participants print the schedule is probably a sign of that problem<br /> * There are problems with not knowing what to do, when. <br /> * Design (we should consider an easier upgrade to something like Twitter Bootstrap)<br /> * User account system isn't great. Newcomers feel like they are putting someone out in order to get an account. Account registration happens last minute. Some don't participate because of this barrier. (-&gt; perhaps provisioning accounts when participants register for the conference would be a good idea)<br /> * Another idea, displaying the code4lib hashtag feed somewhere on the site might be valuable for information dissemenation</div>

Cdmo https://wiki.code4lib.org/index.php?title=April_23&diff=42970 2015-04-23T17:25:08Z

<p>Cdmo: </p> <hr /> <div>== Introductions ==<br /> <br /> We did quick intros of who each of us is and why we are interested in being on this working group.<br /> <br /> '''Charlie'''<br /> * Lead developer at Penn State Libraries, leading team in a move from Adobe CQ5 to Drupal. Previously worked at NCSU Libraries. <br /> * Interested in this group to help make the conference site better<br /> <br /> '''Lauren'''<br /> * Electronics Resource Librarian at Notre Dame<br /> * Interested in improving the scheduling aspects of the site<br /> <br /> '''Junior'''<br /> * Web Services Librarian at NYC College of Technology, currently migrating a Drupal site from 6 to 7, using Twitter Bootstrap<br /> * Likes the community and wants to pitch in and help out<br /> <br /> '''Jenn'''<br /> * UX Designer for Cornell Libraries, front end coding <br /> <br /> '''Eric'''<br /> * Systems Librarian at California College of the Arts<br /> * Likes the community and wants to help, sees the site as functional but confusing<br /> <br /> '''Bill'''<br /> * Currently an Emerging Technologies librarian at Pratt<br /> * Wants to help out as the Documentarian and find out ways we can improve sustainability<br /> <br /> ==Brainstorming==<br /> <br /> ===What is wrong with the current site?===<br /> <br /> * Content is in several different places: the conference site, the wiki, external services. Leads to confusion.<br /> * People couldn't find the streaming channel in previous conferences<br /> * Confusing schedule matrices are a problem for all conference sites and we should spend time on getting this right for 2016<br /> * It isn't mobile-friendly, the fact that participants print the schedule is probably a sign of that problem<br /> * There are problems with not knowing what to do, when. <br /> * Design (we should consider an easier upgrade to something like Twitter Bootstrap)<br /> * User account system isn't great. Newcomers feel like they are putting someone out in order to get an account. Account registration happens last minute. Some don't participate because of this barrier. (-&gt; perhaps provisioning accounts when participants register for the conference would be a good idea)<br /> * Another idea, displaying the code4lib hashtag feed somewhere on the site might be valuable for information dissemenation</div>

Cdmo https://wiki.code4lib.org/index.php?title=April_23&diff=42969 2015-04-23T17:24:37Z

<p>Cdmo: Created page with &quot;== Introductions == We did quick intros of who each of us is and why we are interested in being on this working group. '''Charlie''' * Lead developer at Penn State Libraries...&quot;</p> <hr /> <div>== Introductions ==<br /> <br /> We did quick intros of who each of us is and why we are interested in being on this working group.<br /> <br /> '''Charlie'''<br /> * Lead developer at Penn State Libraries, leading team in a move from Adobe CQ5 to Drupal. Previously worked at NCSU Libraries. <br /> * Interested in this group to help make the conference site better<br /> <br /> '''Lauren'''<br /> * Electronics Resource Librarian at Notre Dame<br /> * Interested in improving the scheduling aspects of the site<br /> <br /> '''Junior'''<br /> * Web Services Librarian at NYC College of Technology, currently migrating a Drupal site from 6 to 7, using Twitter Bootstrap<br /> * Likes the community and wants to pitch in and help out<br /> <br /> '''Jenn'''<br /> * UX Designer for Cornell Libraries, front end coding <br /> <br /> '''Eric'''<br /> * Systems Librarian at California College of the Arts<br /> * Likes the community and wants to help, sees the site as functional but confusing<br /> <br /> '''Bill'''<br /> * Currently an Emerging Technologies librarian at Pratt<br /> * Wants to help out as the Documentarian and find out ways we can improve sustainability<br /> <br /> ===Brainstorming===<br /> <br /> What is wrong with the current site?<br /> <br /> * Content is in several different places: the conference site, the wiki, external services. Leads to confusion.<br /> * People couldn't find the streaming channel in previous conferences<br /> * Confusing schedule matrices are a problem for all conference sites and we should spend time on getting this right for 2016<br /> * It isn't mobile-friendly, the fact that participants print the schedule is probably a sign of that problem<br /> * There are problems with not knowing what to do, when. <br /> * Design (we should consider an easier upgrade to something like Twitter Bootstrap)<br /> * User account system isn't great. Newcomers feel like they are putting someone out in order to get an account. Account registration happens last minute. Some don't participate because of this barrier. (-&gt; perhaps provisioning accounts when participants register for the conference would be a good idea)<br /> * Another idea, displaying the code4lib hashtag feed somewhere on the site might be valuable for information dissemenation</div>

Cdmo https://wiki.code4lib.org/index.php?title=Website_Working_Group_Documents&diff=42968 2015-04-23T17:13:10Z

<p>Cdmo: </p> <hr /> <div>== Notes ==<br /> <br /> [[April 23|April 23]]</div>

Cdmo https://wiki.code4lib.org/index.php?title=Website_Working_Group_Documents&diff=42967 2015-04-23T17:08:31Z

<p>Cdmo: Created page with &quot;New page&quot;</p> <hr /> <div>New page</div>

Cdmo https://wiki.code4lib.org/index.php?title=2016_Conference_Committees&diff=42966 2015-04-23T17:04:03Z

<p>Cdmo: /* Website Working Group */</p> <hr /> <div>= Code4Lib 2016 Committees =<br /> <br /> ''Many hands make for light work.''<br /> <br /> Hosting a conference is incredibly complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2016 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.<br /> <br /> We will assign a local contact (LPC) to each committee.<br /> <br /> == Location and Dates ==<br /> <br /> * Location: TBD, Philadelphia, PA<br /> * Dates: TBD<br /> ** Pre-conferences - <br /> ** Main meeting - <br /> ** Post conference activities?<br /> <br /> == Local Planning Committee ==<br /> 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.<br /> <br /> * David Lacy (Villanova) - Primary Contact (v)<br /> * Chad Nelson - Secondary Contact (v)<br /> * Anna Headley (Chemical Heritage Foundation) - Documentarian (v)<br /> * [[User:Sdellis|Shaun Ellis]] (Princeton) (v)<br /> * Katherine Lynch (Temple) (v)<br /> * Stephen Ng (Temple)<br /> * Brett Bonfield (Collingswood Public)<br /> * Lauren Gala (UPenn)<br /> * David Uspal (Villanova) (v)<br /> * Chris Clement (Drexel)<br /> <br /> == Website Working Group ==<br /> 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). <br /> <br /> [[Website Working Group Documents|Website Working Group Documents]]<br /> <br /> * [[User:Cdmo|Charlie Morris]] (Penn State) - Primary Contact<br /> * [[User:jtidal|Junior Tidal]] (New York City College of Technology) - Secondary Contact<br /> * [[User:BillMcMillin|Bill McMillin]] (Pratt Institute) - Documentarian<br /> * [[User:Sdellis|Shaun Ellis]] (Princeton) - LPC Contact (v)<br /> * [[User:Phette23|Eric Phetteplace]] (Cal College of the Arts)<br /> * [[User:Sarahshealy| Sarah Shealy]] (Greenville (SC) County Public Library)<br /> * [[User:JennC| Jennifer Colt]] (Cornell University Library)<br /> * [[User:LaurenAjamie| Lauren Ajamie]] (University of Notre Dame Library)<br /> * [[User:MichaelSchofield| Michael Schofield]] ( @schoeyfield )<br /> * [[User:LukeAeschleman| Luke Aeschleman]] (UNC - Chapel Hill | Health Sciences Library)<br /> * [[User:Wickr|Ryan Wick]]<br /> * [[User:cbeer|Chris Beer]]<br /> <br /> == Additional Committees... Coming Soon! ==<br /> * Book Give-Away<br /> * Childcare<br /> * Keynote<br /> * Onsite Volunteer<br /> * Preconference<br /> * Program<br /> * Scholarship<br /> * Social Activities<br /> * Sponsorship<br /> * Streaming Video<br /> * T-Shirt<br /> * Voting<br /> * Whatever<br /> * Wifi/Electrical<br /> * IRC<br /> * Reception?</div>

Cdmo https://wiki.code4lib.org/index.php?title=2016_Conference_Committees&diff=42938 2015-04-14T20:30:39Z

<p>Cdmo: /* Website Working Group */</p> <hr /> <div>= Code4Lib 2016 Committees =<br /> <br /> ''Many hands make for light work.''<br /> <br /> Hosting a conference is incredibly complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2016 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.<br /> <br /> We will assign a local contact (LPC) to each committee.<br /> <br /> == Location and Dates ==<br /> <br /> * Location: TBD, Philadelphia, PA<br /> * Dates: TBD<br /> ** Pre-conferences - <br /> ** Main meeting - <br /> ** Post conference activities?<br /> <br /> == Local Planning Committee ==<br /> 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.<br /> <br /> * David Lacy (Villanova) - Primary Contact (v)<br /> * Chad Nelson - Secondary Contact (v)<br /> * Anna Headley (Chemical Heritage Foundation) - Documentarian (v)<br /> * [[User:Sdellis|Shaun Ellis]] (Princeton) (v)<br /> * Katherine Lynch (Temple) (v)<br /> * Stephen Ng (Temple)<br /> * Brett Bonfield (Collingswood Public)<br /> * Lauren Gala (UPenn)<br /> * David Uspal (Villanova) (v)<br /> * Chris Clement (Drexel)<br /> <br /> == Website Working Group ==<br /> 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). <br /> <br /> * [[User:Cdmo|Charlie Morris]] (Penn State) - Primary Contact<br /> * ??? - Secondary Contact<br /> * ??? - Documentarian<br /> * [[User:Sdellis|Shaun Ellis]] (Princeton) - LPC Contact (v)<br /> <br /> == Additional Committees... Coming Soon! ==</div>

Cdmo https://wiki.code4lib.org/index.php?title=User:Cdmo&diff=42937 2015-04-14T20:30:31Z

<p>Cdmo: </p> <hr /> <div>Charlie Morris&lt;br&gt;<br /> Lead Web Developer&lt;br&gt;<br /> Penn State Libraries&lt;br&gt;<br /> State College, PA&lt;br&gt;<br /> cdm32 at psu dot edu</div>

Cdmo https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&diff=42077 2014-11-18T14:03:26Z

<p>Cdmo: /* Code Retreat */</p> <hr /> <div>== Instructions ==<br /> Thank you for considering proposing a pre-conference! Here are a few details:<br /> <br /> * We will be taking pre-conference proposals until '''November 7, 2014'''<br /> * If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu<br /> * Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]<br /> * If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)<br /> * If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu<br /> * '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions<br /> * Please use the template for proposals provided in the pre-formatted block below<br /> <br /> == Pre-conference Proposals ==<br /> <br /> === Delivering and Preserving GIS Data ===<br /> <br /> '''Half Day [Morning]'''<br /> <br /> * Darren Hardy, Stanford University, drh@stanford.edu<br /> * Jack Reed, Stanford University, pjreed@stanford.edu<br /> <br /> We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # [[User:Ssimpkin|Sarah Simpkin]]<br /> # Vicky Steeves<br /> # Andrew Battista<br /> # Peggy Griesinger<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === A hands-on introduction to GeoBlacklight ===<br /> <br /> '''Half Day [Afternoon]'''<br /> <br /> * Darren Hardy, Stanford University, drh@stanford.edu<br /> * Jack Reed, Stanford University, pjreed@stanford.edu<br /> <br /> GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop &quot;Delivering and Preserving GIS Data&quot;.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # [[User:Ssimpkin|Sarah Simpkin]]<br /> # Vicky Steeves<br /> # Andrew Battista<br /> # Peggy Griesinger<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> ===RailsBridge: Intro to programming in Ruby on Rails===<br /> <br /> '''&quot;Half-Day&quot; [morning]'''<br /> <br /> * Contact Carolyn Cole, Penn State University, carolyn@psu.edu<br /> * Additional instructors welcome<br /> <br /> Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.<br /> <br /> RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Maura Carbone<br /> #Vicky Steeves<br /> # Peggy Griesinger<br /> # Mike Price<br /> # Jean Rainwater<br /> # Coral Sheldon-Hess<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Replace yourself with a painfully complex bash script...or try Ansible ===<br /> <br /> '''Half Day [Morning]'''<br /> <br /> * Chad Nelson, chad dot nelson @ lyrasis dot org<br /> * Blake Carver, Blake dot carver @lyrasis dot org<br /> <br /> Abstract: <br /> <br /> [http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> # Ray Schwartz<br /> # Coral Sheldon-Hess<br /> # Kevin S. Clarke<br /> # Joshua Gomez<br /> # Charlie Morris<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Intro to Docker ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * John Fink, McMaster University, john dot fink at gmail dot com<br /> * Francis Kayiwa, University of Maryland Libraries , francis dot kayiwa at gmail dot com<br /> <br /> Abstract:<br /> <br /> [http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.<br /> <br /> ''Interested in Attending''<br /> <br /> # Jim Hahn<br /> # Joshua Gomez<br /> # Bobbi Fox<br /> # Ray Schwartz<br /> # Megan Kudzia<br /> # Coral Sheldon-Hess<br /> # Cary Gordon (uses Docker in production on AWS)<br /> # Eric Phetteplace<br /> # Esther Verreau<br /> # Charlie Morris<br /> #<br /> <br /> === Code Retreat ===<br /> <br /> '''Full Day'''<br /> <br /> * Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu<br /> * Additional facilitators welcome; Especially if you have CodeRetreat experience.<br /> <br /> Abstract:<br /> <br /> &quot;Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.<br /> By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.<br /> Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time.&quot; [http://coderetreat.org/about About Code Retreat]<br /> <br /> ''Interested in Attending''<br /> <br /> # Mike Giarlo<br /> # Charlie Morris<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Presentations workshop ===<br /> <br /> '''&quot;Half Day [Afternoon]&quot;''' (but could be expanded based on interest)<br /> <br /> * Chris Beer, Stanford University, cabeer@stanford.edu<br /> * Additional facilitators welcome.<br /> <br /> This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> #Vicky Steeves<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Dive into Hydra ===<br /> <br /> '''&quot;Half Day [Afternoon]&quot;''' <br /> <br /> * Justin Coyne, Data Curation Experts, justin@curationexperts.com<br /> * Bess Sadler, Stanford University, bess@stanford.edu<br /> <br /> Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend &quot;RailsBridge&quot; prior to this workshop.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Maura Carbone<br /> # Peggy Griesinger<br /> # Mike Price<br /> # Jean Rainwater<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === code4lib/Write The Docs barcamp ===<br /> <br /> '''&quot;Full Day&quot;''', with options for jumping in for half a day<br /> <br /> * code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu<br /> * Write the Docs contacts: TBA<br /> <br /> Abstract<br /> <br /> Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization. <br /> <br /> Remember, like metadata, documentation is a love note to the future.<br /> <br /> More information about Write the Docs at http://conf.writethedocs.org/<br /> <br /> There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> '''Full day'''<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> '''Morning'''<br /> # Ranti Junus<br /> # Mita Williams<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> '''Afternoon'''<br /> # Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon. <br /> # Kevin S. Clarke<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Linked Data Workshop ===<br /> <br /> '''&quot;Half Day [morning]&quot;''' <br /> <br /> * Karen Estlund, University of Oregon, kestlund@uoregon.edu<br /> * Tom Johnson, DPLA, tom@dp.la<br /> <br /> Abstract:<br /> <br /> Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Logan Cox<br /> # Ray Schwartz<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Code4Arc ===<br /> <br /> '''&quot;Full Day&quot;''' (with options for half day participation)<br /> <br /> * Sarah Romkey, Artefactual Systems, sromkey@artefactual.com<br /> * Justin Simpson, Artefactual Systems, jsimpson@artefactual.com<br /> * Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org<br /> * Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com<br /> <br /> Abstract:<br /> <br /> What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how? <br /> <br /> Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.<br /> <br /> The schedule may include the following:<br /> <br /> * Panel type conversations about the State of Art in Archives <br /> * Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed <br /> * Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)<br /> <br /> Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with. <br /> <br /> When signing up, please indicate if you are an end-user or a developer.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Laney McGlohon - developer<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Fail4Lib 2015 ===<br /> <br /> '''Half Day [TBD, probably afternoon]'''<br /> <br /> * Andreas Orphanides, akorphan (at) ncsu.edu<br /> * Jason Casden, jmcasden (at) ncsu.edu<br /> <br /> Abstract:<br /> <br /> Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.<br /> <br /> This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)<br /> <br /> The schedule may include the following:<br /> <br /> * Case studies. Avoid our own mistakes by bearing witness to the failures of others.<br /> * Confessionals, for those willing to share. Let's learn from our own (and each others') failures.<br /> * Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.<br /> <br /> ''Interested in attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ray Schwartz<br /> # Charlie Morris<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Coding Custom Solutions for Every Department in the Library with File Analyzer ===<br /> <br /> '''&quot;Half Day [Morning]&quot;''' <br /> <br /> * Terry Brady, Georgetown University Library, twb27@georgetown.edu<br /> <br /> Abstract<br /> <br /> The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.<br /> <br /> * Analyzing Marc Records for the Cataloging department<br /> * Transferring ILS invoices for the University Account System for the Acquisitions department <br /> * Delivering patron fines to the Bursar’s office for the Access Service department<br /> * Summarizing student worker timesheet data for the Finance department<br /> * Validating counter compliant reports for the Electronic Resources department<br /> * Preparing ingest packages for the Digital Services department<br /> * Validating checksums for the Preservation department<br /> <br /> This hands on workshop will step through the components of the application framework. Workshop participants will install and develop custom File Analyzer tasks in this session.<br /> <br /> The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Megan Kudzia<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * Karen A. Coombs, OCLC, coombsk@oclc.org<br /> <br /> Abstract<br /> Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.<br /> <br /> We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Peggy Griesinger<br /> # Ray Schwartz<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> <br /> === UXtravaganza ===<br /> '''&quot;Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]&quot;'''<br /> <br /> * William Hicks, University of North Texas, William.hicks@unt.edu<br /> * Volunteers?<br /> <br /> Abstract<br /> <br /> I’m envisioning a 1/2 of full day for front-end developers, content strategy people, and other misfits with an interest in user experience, where we can talk about our shared problems, use cases, the state of current research, and play with each other’s sites. A half day seems doable, but if there’s significant enough interest we could push for a full? Here are a few of the things I think might be interesting to see happen:<br /> <br /> * '''Analytics Share-fest:''' A few volunteers demonstrate data about their websites, catalogs, archival/digital collections. Most of us know our own sites but it would be interesting/validating to share this data with others so we can start to see commonalities between institutions, in certain kinds of systems, etc. For anyone using event tracking, or using click- or heat-maps, this would be a great opportunity to show off what people are seeing.<br /> <br /> * '''UX Best Practices Catch Up:''' This spring I had the opportunity to attend a few days worth of usability workshops from the Nielsen-Norman Group, most of which was focused on mobile. I could distill down a lot of the information into an short presentation. Since this is a constantly moving area of research it would be nice to see a few people do other similar short presentations on some current trends/findings relevant to libraries, search, etc.<br /> <br /> * '''Mobile Dev Lab:''' The UNT Libraries has been collecting a small set of smartphones and tablets for testing and development. Basically an [http://labup.org Open Device Lab]. We have about a dozen devices now of varying sizes, OS, OS Versions, + Google Glass. I’ll bring the devices, you can bring yours, and assuming we can get the wifi up and running we can test our sites/services with our big sausage fingers rather than pretending to do so through emulators and the one or two devices we each usually have on hand. If anyone is game they can do a tutorial on Browser-based Inspector Tools, Browser-Cams, or other testing services.<br /> <br /> * '''The Eye’s Have It.''' The UNT Libraries is also in the process of acquiring an eye tracker and software for usability and other gaze-based research studies. We’ll take possession of it shortly after this pre-conference proposal is due and will have a couple of months to play with them before the conference. Assuming we can get our act together learning the device and can get past the technical hurdles of setting it up at the pre-conference, we could try to do some live demos on each other’s sites; i.e. You nominate a site/service, someone in the audience volunteers to wear the device, and we all watch them struggle do the tasks you request on a projector. Rinse. Lather. Repeat. It would hardly be scientific, but it sure would be fun. As a backup, if we have some sites nominated beforehand, I can run a few students at my library through some tasks here and we can show off the results to the crowd.<br /> <br /> For those of you wanting to attend and help out, I’d really like to see some discussion on typography, writing for the web, “dealing with business/administrative requirements from on-high&quot;, maybe do some prototyping exercises, etc. Similarly if anyone is interested in doing some tutorials on bootstrap or how-to’s on running a usability test, that would be rad. But we need you to step up and steer part of the time for most of this to work, so if you are interested in some aspect, and especially if you want to volunteer to lead a bit of the time, contact me.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your<br /> name (but not email address, etc.) here<br /> <br /> # Ray Schwartz<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Intro to Git &amp; possibly beyond ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * Erin Fahy, Stanford University, efahy@stanford.edu<br /> * Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu<br /> <br /> We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:<br /> <br /> * What is a Distributed Version Control System?<br /> * What's the difference between Git and Github.com?<br /> * How to initialize new Git projects locally and on a remote server/Github<br /> * Cloning/Forking existing projects and keeping up to date<br /> * The wonderful world of Git branches<br /> * Interactive rebasing<br /> * Contributing code to existing projects &amp; what pull requests are<br /> * How to handle merge conflicts<br /> * Overview of workflows and branch best practices<br /> * (time allowing) Advanced git: pre/post hooks, submodules, anything else?<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Jeannie Graham<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Visualizing Library Data ===<br /> <br /> '''&quot;Half Day [Morning||Afternoon]&quot;''' <br /> <br /> * Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs<br /> <br /> Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ashley Blewer!<br /> # Bobbi Fox<br /> # Ray Schwartz<br /> # Ranti Junus<br /> # Eric Phetteplace<br /> # Joshua Gomez<br /> # Charlie Morris<br /> #<br /> #<br /> #<br /> <br /> === CollectionSpace: Getting it up and running at your museum ===<br /> <br /> '''Half Day [Afternoon]'''<br /> <br /> * Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org<br /> * TBD<br /> <br /> This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org<br /> <br /> Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.<br /> <br /> ''Interested in Attending''<br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === DPLA API Workshop: ===<br /> <br /> '''Half Day [Afternoon]''' <br /> <br /> * Audrey Altman, DPLA<br /> * Mark Breedlove, DPLA<br /> * Mark Matienzo, DPLA<br /> * Tom Johnson, DPLA<br /> <br /> The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ranti Junus<br /> # Jean Rainwater<br /> # Mita Williams<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> [[Category:Code4Lib2015]]</div>

Cdmo https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&diff=42076 2014-11-18T14:02:42Z

<p>Cdmo: /* Replace yourself with a painfully complex bash script...or try Ansible */</p> <hr /> <div>== Instructions ==<br /> Thank you for considering proposing a pre-conference! Here are a few details:<br /> <br /> * We will be taking pre-conference proposals until '''November 7, 2014'''<br /> * If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu<br /> * Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]<br /> * If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)<br /> * If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu<br /> * '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions<br /> * Please use the template for proposals provided in the pre-formatted block below<br /> <br /> == Pre-conference Proposals ==<br /> <br /> === Delivering and Preserving GIS Data ===<br /> <br /> '''Half Day [Morning]'''<br /> <br /> * Darren Hardy, Stanford University, drh@stanford.edu<br /> * Jack Reed, Stanford University, pjreed@stanford.edu<br /> <br /> We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # [[User:Ssimpkin|Sarah Simpkin]]<br /> # Vicky Steeves<br /> # Andrew Battista<br /> # Peggy Griesinger<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === A hands-on introduction to GeoBlacklight ===<br /> <br /> '''Half Day [Afternoon]'''<br /> <br /> * Darren Hardy, Stanford University, drh@stanford.edu<br /> * Jack Reed, Stanford University, pjreed@stanford.edu<br /> <br /> GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop &quot;Delivering and Preserving GIS Data&quot;.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # [[User:Ssimpkin|Sarah Simpkin]]<br /> # Vicky Steeves<br /> # Andrew Battista<br /> # Peggy Griesinger<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> ===RailsBridge: Intro to programming in Ruby on Rails===<br /> <br /> '''&quot;Half-Day&quot; [morning]'''<br /> <br /> * Contact Carolyn Cole, Penn State University, carolyn@psu.edu<br /> * Additional instructors welcome<br /> <br /> Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.<br /> <br /> RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Maura Carbone<br /> #Vicky Steeves<br /> # Peggy Griesinger<br /> # Mike Price<br /> # Jean Rainwater<br /> # Coral Sheldon-Hess<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Replace yourself with a painfully complex bash script...or try Ansible ===<br /> <br /> '''Half Day [Morning]'''<br /> <br /> * Chad Nelson, chad dot nelson @ lyrasis dot org<br /> * Blake Carver, Blake dot carver @lyrasis dot org<br /> <br /> Abstract: <br /> <br /> [http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> # Ray Schwartz<br /> # Coral Sheldon-Hess<br /> # Kevin S. Clarke<br /> # Joshua Gomez<br /> # Charlie Morris<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Intro to Docker ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * John Fink, McMaster University, john dot fink at gmail dot com<br /> * Francis Kayiwa, University of Maryland Libraries , francis dot kayiwa at gmail dot com<br /> <br /> Abstract:<br /> <br /> [http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.<br /> <br /> ''Interested in Attending''<br /> <br /> # Jim Hahn<br /> # Joshua Gomez<br /> # Bobbi Fox<br /> # Ray Schwartz<br /> # Megan Kudzia<br /> # Coral Sheldon-Hess<br /> # Cary Gordon (uses Docker in production on AWS)<br /> # Eric Phetteplace<br /> # Esther Verreau<br /> # Charlie Morris<br /> #<br /> <br /> === Code Retreat ===<br /> <br /> '''Full Day'''<br /> <br /> * Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu<br /> * Additional facilitators welcome; Especially if you have CodeRetreat experience.<br /> <br /> Abstract:<br /> <br /> &quot;Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.<br /> By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.<br /> Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time.&quot; [http://coderetreat.org/about About Code Retreat]<br /> <br /> ''Interested in Attending''<br /> <br /> # Mike Giarlo<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Presentations workshop ===<br /> <br /> '''&quot;Half Day [Afternoon]&quot;''' (but could be expanded based on interest)<br /> <br /> * Chris Beer, Stanford University, cabeer@stanford.edu<br /> * Additional facilitators welcome.<br /> <br /> This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> #Vicky Steeves<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Dive into Hydra ===<br /> <br /> '''&quot;Half Day [Afternoon]&quot;''' <br /> <br /> * Justin Coyne, Data Curation Experts, justin@curationexperts.com<br /> * Bess Sadler, Stanford University, bess@stanford.edu<br /> <br /> Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend &quot;RailsBridge&quot; prior to this workshop.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Maura Carbone<br /> # Peggy Griesinger<br /> # Mike Price<br /> # Jean Rainwater<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === code4lib/Write The Docs barcamp ===<br /> <br /> '''&quot;Full Day&quot;''', with options for jumping in for half a day<br /> <br /> * code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu<br /> * Write the Docs contacts: TBA<br /> <br /> Abstract<br /> <br /> Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization. <br /> <br /> Remember, like metadata, documentation is a love note to the future.<br /> <br /> More information about Write the Docs at http://conf.writethedocs.org/<br /> <br /> There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> '''Full day'''<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> '''Morning'''<br /> # Ranti Junus<br /> # Mita Williams<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> '''Afternoon'''<br /> # Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon. <br /> # Kevin S. Clarke<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Linked Data Workshop ===<br /> <br /> '''&quot;Half Day [morning]&quot;''' <br /> <br /> * Karen Estlund, University of Oregon, kestlund@uoregon.edu<br /> * Tom Johnson, DPLA, tom@dp.la<br /> <br /> Abstract:<br /> <br /> Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Logan Cox<br /> # Ray Schwartz<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Code4Arc ===<br /> <br /> '''&quot;Full Day&quot;''' (with options for half day participation)<br /> <br /> * Sarah Romkey, Artefactual Systems, sromkey@artefactual.com<br /> * Justin Simpson, Artefactual Systems, jsimpson@artefactual.com<br /> * Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org<br /> * Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com<br /> <br /> Abstract:<br /> <br /> What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how? <br /> <br /> Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.<br /> <br /> The schedule may include the following:<br /> <br /> * Panel type conversations about the State of Art in Archives <br /> * Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed <br /> * Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)<br /> <br /> Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with. <br /> <br /> When signing up, please indicate if you are an end-user or a developer.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Laney McGlohon - developer<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Fail4Lib 2015 ===<br /> <br /> '''Half Day [TBD, probably afternoon]'''<br /> <br /> * Andreas Orphanides, akorphan (at) ncsu.edu<br /> * Jason Casden, jmcasden (at) ncsu.edu<br /> <br /> Abstract:<br /> <br /> Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.<br /> <br /> This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)<br /> <br /> The schedule may include the following:<br /> <br /> * Case studies. Avoid our own mistakes by bearing witness to the failures of others.<br /> * Confessionals, for those willing to share. Let's learn from our own (and each others') failures.<br /> * Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.<br /> <br /> ''Interested in attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ray Schwartz<br /> # Charlie Morris<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Coding Custom Solutions for Every Department in the Library with File Analyzer ===<br /> <br /> '''&quot;Half Day [Morning]&quot;''' <br /> <br /> * Terry Brady, Georgetown University Library, twb27@georgetown.edu<br /> <br /> Abstract<br /> <br /> The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.<br /> <br /> * Analyzing Marc Records for the Cataloging department<br /> * Transferring ILS invoices for the University Account System for the Acquisitions department <br /> * Delivering patron fines to the Bursar’s office for the Access Service department<br /> * Summarizing student worker timesheet data for the Finance department<br /> * Validating counter compliant reports for the Electronic Resources department<br /> * Preparing ingest packages for the Digital Services department<br /> * Validating checksums for the Preservation department<br /> <br /> This hands on workshop will step through the components of the application framework. Workshop participants will install and develop custom File Analyzer tasks in this session.<br /> <br /> The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Megan Kudzia<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * Karen A. Coombs, OCLC, coombsk@oclc.org<br /> <br /> Abstract<br /> Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.<br /> <br /> We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Peggy Griesinger<br /> # Ray Schwartz<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> <br /> === UXtravaganza ===<br /> '''&quot;Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]&quot;'''<br /> <br /> * William Hicks, University of North Texas, William.hicks@unt.edu<br /> * Volunteers?<br /> <br /> Abstract<br /> <br /> I’m envisioning a 1/2 of full day for front-end developers, content strategy people, and other misfits with an interest in user experience, where we can talk about our shared problems, use cases, the state of current research, and play with each other’s sites. A half day seems doable, but if there’s significant enough interest we could push for a full? Here are a few of the things I think might be interesting to see happen:<br /> <br /> * '''Analytics Share-fest:''' A few volunteers demonstrate data about their websites, catalogs, archival/digital collections. Most of us know our own sites but it would be interesting/validating to share this data with others so we can start to see commonalities between institutions, in certain kinds of systems, etc. For anyone using event tracking, or using click- or heat-maps, this would be a great opportunity to show off what people are seeing.<br /> <br /> * '''UX Best Practices Catch Up:''' This spring I had the opportunity to attend a few days worth of usability workshops from the Nielsen-Norman Group, most of which was focused on mobile. I could distill down a lot of the information into an short presentation. Since this is a constantly moving area of research it would be nice to see a few people do other similar short presentations on some current trends/findings relevant to libraries, search, etc.<br /> <br /> * '''Mobile Dev Lab:''' The UNT Libraries has been collecting a small set of smartphones and tablets for testing and development. Basically an [http://labup.org Open Device Lab]. We have about a dozen devices now of varying sizes, OS, OS Versions, + Google Glass. I’ll bring the devices, you can bring yours, and assuming we can get the wifi up and running we can test our sites/services with our big sausage fingers rather than pretending to do so through emulators and the one or two devices we each usually have on hand. If anyone is game they can do a tutorial on Browser-based Inspector Tools, Browser-Cams, or other testing services.<br /> <br /> * '''The Eye’s Have It.''' The UNT Libraries is also in the process of acquiring an eye tracker and software for usability and other gaze-based research studies. We’ll take possession of it shortly after this pre-conference proposal is due and will have a couple of months to play with them before the conference. Assuming we can get our act together learning the device and can get past the technical hurdles of setting it up at the pre-conference, we could try to do some live demos on each other’s sites; i.e. You nominate a site/service, someone in the audience volunteers to wear the device, and we all watch them struggle do the tasks you request on a projector. Rinse. Lather. Repeat. It would hardly be scientific, but it sure would be fun. As a backup, if we have some sites nominated beforehand, I can run a few students at my library through some tasks here and we can show off the results to the crowd.<br /> <br /> For those of you wanting to attend and help out, I’d really like to see some discussion on typography, writing for the web, “dealing with business/administrative requirements from on-high&quot;, maybe do some prototyping exercises, etc. Similarly if anyone is interested in doing some tutorials on bootstrap or how-to’s on running a usability test, that would be rad. But we need you to step up and steer part of the time for most of this to work, so if you are interested in some aspect, and especially if you want to volunteer to lead a bit of the time, contact me.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your<br /> name (but not email address, etc.) here<br /> <br /> # Ray Schwartz<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Intro to Git &amp; possibly beyond ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * Erin Fahy, Stanford University, efahy@stanford.edu<br /> * Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu<br /> <br /> We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:<br /> <br /> * What is a Distributed Version Control System?<br /> * What's the difference between Git and Github.com?<br /> * How to initialize new Git projects locally and on a remote server/Github<br /> * Cloning/Forking existing projects and keeping up to date<br /> * The wonderful world of Git branches<br /> * Interactive rebasing<br /> * Contributing code to existing projects &amp; what pull requests are<br /> * How to handle merge conflicts<br /> * Overview of workflows and branch best practices<br /> * (time allowing) Advanced git: pre/post hooks, submodules, anything else?<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Jeannie Graham<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Visualizing Library Data ===<br /> <br /> '''&quot;Half Day [Morning||Afternoon]&quot;''' <br /> <br /> * Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs<br /> <br /> Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ashley Blewer!<br /> # Bobbi Fox<br /> # Ray Schwartz<br /> # Ranti Junus<br /> # Eric Phetteplace<br /> # Joshua Gomez<br /> # Charlie Morris<br /> #<br /> #<br /> #<br /> <br /> === CollectionSpace: Getting it up and running at your museum ===<br /> <br /> '''Half Day [Afternoon]'''<br /> <br /> * Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org<br /> * TBD<br /> <br /> This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org<br /> <br /> Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.<br /> <br /> ''Interested in Attending''<br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === DPLA API Workshop: ===<br /> <br /> '''Half Day [Afternoon]''' <br /> <br /> * Audrey Altman, DPLA<br /> * Mark Breedlove, DPLA<br /> * Mark Matienzo, DPLA<br /> * Tom Johnson, DPLA<br /> <br /> The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ranti Junus<br /> # Jean Rainwater<br /> # Mita Williams<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> [[Category:Code4Lib2015]]</div>

Cdmo https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&diff=42075 2014-11-18T14:01:20Z

<p>Cdmo: /* Visualizing Library Data */</p> <hr /> <div>== Instructions ==<br /> Thank you for considering proposing a pre-conference! Here are a few details:<br /> <br /> * We will be taking pre-conference proposals until '''November 7, 2014'''<br /> * If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu<br /> * Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]<br /> * If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)<br /> * If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu<br /> * '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions<br /> * Please use the template for proposals provided in the pre-formatted block below<br /> <br /> == Pre-conference Proposals ==<br /> <br /> === Delivering and Preserving GIS Data ===<br /> <br /> '''Half Day [Morning]'''<br /> <br /> * Darren Hardy, Stanford University, drh@stanford.edu<br /> * Jack Reed, Stanford University, pjreed@stanford.edu<br /> <br /> We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # [[User:Ssimpkin|Sarah Simpkin]]<br /> # Vicky Steeves<br /> # Andrew Battista<br /> # Peggy Griesinger<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === A hands-on introduction to GeoBlacklight ===<br /> <br /> '''Half Day [Afternoon]'''<br /> <br /> * Darren Hardy, Stanford University, drh@stanford.edu<br /> * Jack Reed, Stanford University, pjreed@stanford.edu<br /> <br /> GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop &quot;Delivering and Preserving GIS Data&quot;.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # [[User:Ssimpkin|Sarah Simpkin]]<br /> # Vicky Steeves<br /> # Andrew Battista<br /> # Peggy Griesinger<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> ===RailsBridge: Intro to programming in Ruby on Rails===<br /> <br /> '''&quot;Half-Day&quot; [morning]'''<br /> <br /> * Contact Carolyn Cole, Penn State University, carolyn@psu.edu<br /> * Additional instructors welcome<br /> <br /> Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.<br /> <br /> RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Maura Carbone<br /> #Vicky Steeves<br /> # Peggy Griesinger<br /> # Mike Price<br /> # Jean Rainwater<br /> # Coral Sheldon-Hess<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Replace yourself with a painfully complex bash script...or try Ansible ===<br /> <br /> '''Half Day [Morning]'''<br /> <br /> * Chad Nelson, chad dot nelson @ lyrasis dot org<br /> * Blake Carver, Blake dot carver @lyrasis dot org<br /> <br /> Abstract: <br /> <br /> [http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> # Ray Schwartz<br /> # Coral Sheldon-Hess<br /> # Kevin S. Clarke<br /> # Joshua Gomez<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Intro to Docker ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * John Fink, McMaster University, john dot fink at gmail dot com<br /> * Francis Kayiwa, University of Maryland Libraries , francis dot kayiwa at gmail dot com<br /> <br /> Abstract:<br /> <br /> [http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.<br /> <br /> ''Interested in Attending''<br /> <br /> # Jim Hahn<br /> # Joshua Gomez<br /> # Bobbi Fox<br /> # Ray Schwartz<br /> # Megan Kudzia<br /> # Coral Sheldon-Hess<br /> # Cary Gordon (uses Docker in production on AWS)<br /> # Eric Phetteplace<br /> # Esther Verreau<br /> # Charlie Morris<br /> #<br /> <br /> === Code Retreat ===<br /> <br /> '''Full Day'''<br /> <br /> * Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu<br /> * Additional facilitators welcome; Especially if you have CodeRetreat experience.<br /> <br /> Abstract:<br /> <br /> &quot;Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.<br /> By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.<br /> Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time.&quot; [http://coderetreat.org/about About Code Retreat]<br /> <br /> ''Interested in Attending''<br /> <br /> # Mike Giarlo<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Presentations workshop ===<br /> <br /> '''&quot;Half Day [Afternoon]&quot;''' (but could be expanded based on interest)<br /> <br /> * Chris Beer, Stanford University, cabeer@stanford.edu<br /> * Additional facilitators welcome.<br /> <br /> This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> #Vicky Steeves<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Dive into Hydra ===<br /> <br /> '''&quot;Half Day [Afternoon]&quot;''' <br /> <br /> * Justin Coyne, Data Curation Experts, justin@curationexperts.com<br /> * Bess Sadler, Stanford University, bess@stanford.edu<br /> <br /> Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend &quot;RailsBridge&quot; prior to this workshop.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Maura Carbone<br /> # Peggy Griesinger<br /> # Mike Price<br /> # Jean Rainwater<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === code4lib/Write The Docs barcamp ===<br /> <br /> '''&quot;Full Day&quot;''', with options for jumping in for half a day<br /> <br /> * code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu<br /> * Write the Docs contacts: TBA<br /> <br /> Abstract<br /> <br /> Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization. <br /> <br /> Remember, like metadata, documentation is a love note to the future.<br /> <br /> More information about Write the Docs at http://conf.writethedocs.org/<br /> <br /> There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> '''Full day'''<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> '''Morning'''<br /> # Ranti Junus<br /> # Mita Williams<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> '''Afternoon'''<br /> # Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon. <br /> # Kevin S. Clarke<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Linked Data Workshop ===<br /> <br /> '''&quot;Half Day [morning]&quot;''' <br /> <br /> * Karen Estlund, University of Oregon, kestlund@uoregon.edu<br /> * Tom Johnson, DPLA, tom@dp.la<br /> <br /> Abstract:<br /> <br /> Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Logan Cox<br /> # Ray Schwartz<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Code4Arc ===<br /> <br /> '''&quot;Full Day&quot;''' (with options for half day participation)<br /> <br /> * Sarah Romkey, Artefactual Systems, sromkey@artefactual.com<br /> * Justin Simpson, Artefactual Systems, jsimpson@artefactual.com<br /> * Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org<br /> * Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com<br /> <br /> Abstract:<br /> <br /> What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how? <br /> <br /> Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.<br /> <br /> The schedule may include the following:<br /> <br /> * Panel type conversations about the State of Art in Archives <br /> * Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed <br /> * Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)<br /> <br /> Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with. <br /> <br /> When signing up, please indicate if you are an end-user or a developer.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Laney McGlohon - developer<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Fail4Lib 2015 ===<br /> <br /> '''Half Day [TBD, probably afternoon]'''<br /> <br /> * Andreas Orphanides, akorphan (at) ncsu.edu<br /> * Jason Casden, jmcasden (at) ncsu.edu<br /> <br /> Abstract:<br /> <br /> Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.<br /> <br /> This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)<br /> <br /> The schedule may include the following:<br /> <br /> * Case studies. Avoid our own mistakes by bearing witness to the failures of others.<br /> * Confessionals, for those willing to share. Let's learn from our own (and each others') failures.<br /> * Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.<br /> <br /> ''Interested in attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ray Schwartz<br /> # Charlie Morris<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Coding Custom Solutions for Every Department in the Library with File Analyzer ===<br /> <br /> '''&quot;Half Day [Morning]&quot;''' <br /> <br /> * Terry Brady, Georgetown University Library, twb27@georgetown.edu<br /> <br /> Abstract<br /> <br /> The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.<br /> <br /> * Analyzing Marc Records for the Cataloging department<br /> * Transferring ILS invoices for the University Account System for the Acquisitions department <br /> * Delivering patron fines to the Bursar’s office for the Access Service department<br /> * Summarizing student worker timesheet data for the Finance department<br /> * Validating counter compliant reports for the Electronic Resources department<br /> * Preparing ingest packages for the Digital Services department<br /> * Validating checksums for the Preservation department<br /> <br /> This hands on workshop will step through the components of the application framework. Workshop participants will install and develop custom File Analyzer tasks in this session.<br /> <br /> The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Megan Kudzia<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * Karen A. Coombs, OCLC, coombsk@oclc.org<br /> <br /> Abstract<br /> Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.<br /> <br /> We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Peggy Griesinger<br /> # Ray Schwartz<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> <br /> === UXtravaganza ===<br /> '''&quot;Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]&quot;'''<br /> <br /> * William Hicks, University of North Texas, William.hicks@unt.edu<br /> * Volunteers?<br /> <br /> Abstract<br /> <br /> I’m envisioning a 1/2 of full day for front-end developers, content strategy people, and other misfits with an interest in user experience, where we can talk about our shared problems, use cases, the state of current research, and play with each other’s sites. A half day seems doable, but if there’s significant enough interest we could push for a full? Here are a few of the things I think might be interesting to see happen:<br /> <br /> * '''Analytics Share-fest:''' A few volunteers demonstrate data about their websites, catalogs, archival/digital collections. Most of us know our own sites but it would be interesting/validating to share this data with others so we can start to see commonalities between institutions, in certain kinds of systems, etc. For anyone using event tracking, or using click- or heat-maps, this would be a great opportunity to show off what people are seeing.<br /> <br /> * '''UX Best Practices Catch Up:''' This spring I had the opportunity to attend a few days worth of usability workshops from the Nielsen-Norman Group, most of which was focused on mobile. I could distill down a lot of the information into an short presentation. Since this is a constantly moving area of research it would be nice to see a few people do other similar short presentations on some current trends/findings relevant to libraries, search, etc.<br /> <br /> * '''Mobile Dev Lab:''' The UNT Libraries has been collecting a small set of smartphones and tablets for testing and development. Basically an [http://labup.org Open Device Lab]. We have about a dozen devices now of varying sizes, OS, OS Versions, + Google Glass. I’ll bring the devices, you can bring yours, and assuming we can get the wifi up and running we can test our sites/services with our big sausage fingers rather than pretending to do so through emulators and the one or two devices we each usually have on hand. If anyone is game they can do a tutorial on Browser-based Inspector Tools, Browser-Cams, or other testing services.<br /> <br /> * '''The Eye’s Have It.''' The UNT Libraries is also in the process of acquiring an eye tracker and software for usability and other gaze-based research studies. We’ll take possession of it shortly after this pre-conference proposal is due and will have a couple of months to play with them before the conference. Assuming we can get our act together learning the device and can get past the technical hurdles of setting it up at the pre-conference, we could try to do some live demos on each other’s sites; i.e. You nominate a site/service, someone in the audience volunteers to wear the device, and we all watch them struggle do the tasks you request on a projector. Rinse. Lather. Repeat. It would hardly be scientific, but it sure would be fun. As a backup, if we have some sites nominated beforehand, I can run a few students at my library through some tasks here and we can show off the results to the crowd.<br /> <br /> For those of you wanting to attend and help out, I’d really like to see some discussion on typography, writing for the web, “dealing with business/administrative requirements from on-high&quot;, maybe do some prototyping exercises, etc. Similarly if anyone is interested in doing some tutorials on bootstrap or how-to’s on running a usability test, that would be rad. But we need you to step up and steer part of the time for most of this to work, so if you are interested in some aspect, and especially if you want to volunteer to lead a bit of the time, contact me.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your<br /> name (but not email address, etc.) here<br /> <br /> # Ray Schwartz<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Intro to Git &amp; possibly beyond ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * Erin Fahy, Stanford University, efahy@stanford.edu<br /> * Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu<br /> <br /> We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:<br /> <br /> * What is a Distributed Version Control System?<br /> * What's the difference between Git and Github.com?<br /> * How to initialize new Git projects locally and on a remote server/Github<br /> * Cloning/Forking existing projects and keeping up to date<br /> * The wonderful world of Git branches<br /> * Interactive rebasing<br /> * Contributing code to existing projects &amp; what pull requests are<br /> * How to handle merge conflicts<br /> * Overview of workflows and branch best practices<br /> * (time allowing) Advanced git: pre/post hooks, submodules, anything else?<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Jeannie Graham<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Visualizing Library Data ===<br /> <br /> '''&quot;Half Day [Morning||Afternoon]&quot;''' <br /> <br /> * Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs<br /> <br /> Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ashley Blewer!<br /> # Bobbi Fox<br /> # Ray Schwartz<br /> # Ranti Junus<br /> # Eric Phetteplace<br /> # Joshua Gomez<br /> # Charlie Morris<br /> #<br /> #<br /> #<br /> <br /> === CollectionSpace: Getting it up and running at your museum ===<br /> <br /> '''Half Day [Afternoon]'''<br /> <br /> * Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org<br /> * TBD<br /> <br /> This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org<br /> <br /> Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.<br /> <br /> ''Interested in Attending''<br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === DPLA API Workshop: ===<br /> <br /> '''Half Day [Afternoon]''' <br /> <br /> * Audrey Altman, DPLA<br /> * Mark Breedlove, DPLA<br /> * Mark Matienzo, DPLA<br /> * Tom Johnson, DPLA<br /> <br /> The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ranti Junus<br /> # Jean Rainwater<br /> # Mita Williams<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> [[Category:Code4Lib2015]]</div>

Cdmo https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&diff=42074 2014-11-18T13:59:54Z

<p>Cdmo: /* Fail4Lib 2015 */</p> <hr /> <div>== Instructions ==<br /> Thank you for considering proposing a pre-conference! Here are a few details:<br /> <br /> * We will be taking pre-conference proposals until '''November 7, 2014'''<br /> * If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu<br /> * Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]<br /> * If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)<br /> * If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu<br /> * '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions<br /> * Please use the template for proposals provided in the pre-formatted block below<br /> <br /> == Pre-conference Proposals ==<br /> <br /> === Delivering and Preserving GIS Data ===<br /> <br /> '''Half Day [Morning]'''<br /> <br /> * Darren Hardy, Stanford University, drh@stanford.edu<br /> * Jack Reed, Stanford University, pjreed@stanford.edu<br /> <br /> We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # [[User:Ssimpkin|Sarah Simpkin]]<br /> # Vicky Steeves<br /> # Andrew Battista<br /> # Peggy Griesinger<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === A hands-on introduction to GeoBlacklight ===<br /> <br /> '''Half Day [Afternoon]'''<br /> <br /> * Darren Hardy, Stanford University, drh@stanford.edu<br /> * Jack Reed, Stanford University, pjreed@stanford.edu<br /> <br /> GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop &quot;Delivering and Preserving GIS Data&quot;.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # [[User:Ssimpkin|Sarah Simpkin]]<br /> # Vicky Steeves<br /> # Andrew Battista<br /> # Peggy Griesinger<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> ===RailsBridge: Intro to programming in Ruby on Rails===<br /> <br /> '''&quot;Half-Day&quot; [morning]'''<br /> <br /> * Contact Carolyn Cole, Penn State University, carolyn@psu.edu<br /> * Additional instructors welcome<br /> <br /> Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.<br /> <br /> RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Maura Carbone<br /> #Vicky Steeves<br /> # Peggy Griesinger<br /> # Mike Price<br /> # Jean Rainwater<br /> # Coral Sheldon-Hess<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Replace yourself with a painfully complex bash script...or try Ansible ===<br /> <br /> '''Half Day [Morning]'''<br /> <br /> * Chad Nelson, chad dot nelson @ lyrasis dot org<br /> * Blake Carver, Blake dot carver @lyrasis dot org<br /> <br /> Abstract: <br /> <br /> [http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> # Ray Schwartz<br /> # Coral Sheldon-Hess<br /> # Kevin S. Clarke<br /> # Joshua Gomez<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Intro to Docker ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * John Fink, McMaster University, john dot fink at gmail dot com<br /> * Francis Kayiwa, University of Maryland Libraries , francis dot kayiwa at gmail dot com<br /> <br /> Abstract:<br /> <br /> [http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.<br /> <br /> ''Interested in Attending''<br /> <br /> # Jim Hahn<br /> # Joshua Gomez<br /> # Bobbi Fox<br /> # Ray Schwartz<br /> # Megan Kudzia<br /> # Coral Sheldon-Hess<br /> # Cary Gordon (uses Docker in production on AWS)<br /> # Eric Phetteplace<br /> # Esther Verreau<br /> # Charlie Morris<br /> #<br /> <br /> === Code Retreat ===<br /> <br /> '''Full Day'''<br /> <br /> * Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu<br /> * Additional facilitators welcome; Especially if you have CodeRetreat experience.<br /> <br /> Abstract:<br /> <br /> &quot;Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.<br /> By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.<br /> Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time.&quot; [http://coderetreat.org/about About Code Retreat]<br /> <br /> ''Interested in Attending''<br /> <br /> # Mike Giarlo<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Presentations workshop ===<br /> <br /> '''&quot;Half Day [Afternoon]&quot;''' (but could be expanded based on interest)<br /> <br /> * Chris Beer, Stanford University, cabeer@stanford.edu<br /> * Additional facilitators welcome.<br /> <br /> This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> #Vicky Steeves<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Dive into Hydra ===<br /> <br /> '''&quot;Half Day [Afternoon]&quot;''' <br /> <br /> * Justin Coyne, Data Curation Experts, justin@curationexperts.com<br /> * Bess Sadler, Stanford University, bess@stanford.edu<br /> <br /> Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend &quot;RailsBridge&quot; prior to this workshop.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Maura Carbone<br /> # Peggy Griesinger<br /> # Mike Price<br /> # Jean Rainwater<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === code4lib/Write The Docs barcamp ===<br /> <br /> '''&quot;Full Day&quot;''', with options for jumping in for half a day<br /> <br /> * code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu<br /> * Write the Docs contacts: TBA<br /> <br /> Abstract<br /> <br /> Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization. <br /> <br /> Remember, like metadata, documentation is a love note to the future.<br /> <br /> More information about Write the Docs at http://conf.writethedocs.org/<br /> <br /> There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> '''Full day'''<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> '''Morning'''<br /> # Ranti Junus<br /> # Mita Williams<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> '''Afternoon'''<br /> # Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon. <br /> # Kevin S. Clarke<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Linked Data Workshop ===<br /> <br /> '''&quot;Half Day [morning]&quot;''' <br /> <br /> * Karen Estlund, University of Oregon, kestlund@uoregon.edu<br /> * Tom Johnson, DPLA, tom@dp.la<br /> <br /> Abstract:<br /> <br /> Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Logan Cox<br /> # Ray Schwartz<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Code4Arc ===<br /> <br /> '''&quot;Full Day&quot;''' (with options for half day participation)<br /> <br /> * Sarah Romkey, Artefactual Systems, sromkey@artefactual.com<br /> * Justin Simpson, Artefactual Systems, jsimpson@artefactual.com<br /> * Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org<br /> * Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com<br /> <br /> Abstract:<br /> <br /> What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how? <br /> <br /> Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.<br /> <br /> The schedule may include the following:<br /> <br /> * Panel type conversations about the State of Art in Archives <br /> * Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed <br /> * Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)<br /> <br /> Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with. <br /> <br /> When signing up, please indicate if you are an end-user or a developer.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Laney McGlohon - developer<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Fail4Lib 2015 ===<br /> <br /> '''Half Day [TBD, probably afternoon]'''<br /> <br /> * Andreas Orphanides, akorphan (at) ncsu.edu<br /> * Jason Casden, jmcasden (at) ncsu.edu<br /> <br /> Abstract:<br /> <br /> Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.<br /> <br /> This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)<br /> <br /> The schedule may include the following:<br /> <br /> * Case studies. Avoid our own mistakes by bearing witness to the failures of others.<br /> * Confessionals, for those willing to share. Let's learn from our own (and each others') failures.<br /> * Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.<br /> <br /> ''Interested in attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ray Schwartz<br /> # Charlie Morris<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Coding Custom Solutions for Every Department in the Library with File Analyzer ===<br /> <br /> '''&quot;Half Day [Morning]&quot;''' <br /> <br /> * Terry Brady, Georgetown University Library, twb27@georgetown.edu<br /> <br /> Abstract<br /> <br /> The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.<br /> <br /> * Analyzing Marc Records for the Cataloging department<br /> * Transferring ILS invoices for the University Account System for the Acquisitions department <br /> * Delivering patron fines to the Bursar’s office for the Access Service department<br /> * Summarizing student worker timesheet data for the Finance department<br /> * Validating counter compliant reports for the Electronic Resources department<br /> * Preparing ingest packages for the Digital Services department<br /> * Validating checksums for the Preservation department<br /> <br /> This hands on workshop will step through the components of the application framework. Workshop participants will install and develop custom File Analyzer tasks in this session.<br /> <br /> The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Megan Kudzia<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * Karen A. Coombs, OCLC, coombsk@oclc.org<br /> <br /> Abstract<br /> Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.<br /> <br /> We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Peggy Griesinger<br /> # Ray Schwartz<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> <br /> === UXtravaganza ===<br /> '''&quot;Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]&quot;'''<br /> <br /> * William Hicks, University of North Texas, William.hicks@unt.edu<br /> * Volunteers?<br /> <br /> Abstract<br /> <br /> I’m envisioning a 1/2 of full day for front-end developers, content strategy people, and other misfits with an interest in user experience, where we can talk about our shared problems, use cases, the state of current research, and play with each other’s sites. A half day seems doable, but if there’s significant enough interest we could push for a full? Here are a few of the things I think might be interesting to see happen:<br /> <br /> * '''Analytics Share-fest:''' A few volunteers demonstrate data about their websites, catalogs, archival/digital collections. Most of us know our own sites but it would be interesting/validating to share this data with others so we can start to see commonalities between institutions, in certain kinds of systems, etc. For anyone using event tracking, or using click- or heat-maps, this would be a great opportunity to show off what people are seeing.<br /> <br /> * '''UX Best Practices Catch Up:''' This spring I had the opportunity to attend a few days worth of usability workshops from the Nielsen-Norman Group, most of which was focused on mobile. I could distill down a lot of the information into an short presentation. Since this is a constantly moving area of research it would be nice to see a few people do other similar short presentations on some current trends/findings relevant to libraries, search, etc.<br /> <br /> * '''Mobile Dev Lab:''' The UNT Libraries has been collecting a small set of smartphones and tablets for testing and development. Basically an [http://labup.org Open Device Lab]. We have about a dozen devices now of varying sizes, OS, OS Versions, + Google Glass. I’ll bring the devices, you can bring yours, and assuming we can get the wifi up and running we can test our sites/services with our big sausage fingers rather than pretending to do so through emulators and the one or two devices we each usually have on hand. If anyone is game they can do a tutorial on Browser-based Inspector Tools, Browser-Cams, or other testing services.<br /> <br /> * '''The Eye’s Have It.''' The UNT Libraries is also in the process of acquiring an eye tracker and software for usability and other gaze-based research studies. We’ll take possession of it shortly after this pre-conference proposal is due and will have a couple of months to play with them before the conference. Assuming we can get our act together learning the device and can get past the technical hurdles of setting it up at the pre-conference, we could try to do some live demos on each other’s sites; i.e. You nominate a site/service, someone in the audience volunteers to wear the device, and we all watch them struggle do the tasks you request on a projector. Rinse. Lather. Repeat. It would hardly be scientific, but it sure would be fun. As a backup, if we have some sites nominated beforehand, I can run a few students at my library through some tasks here and we can show off the results to the crowd.<br /> <br /> For those of you wanting to attend and help out, I’d really like to see some discussion on typography, writing for the web, “dealing with business/administrative requirements from on-high&quot;, maybe do some prototyping exercises, etc. Similarly if anyone is interested in doing some tutorials on bootstrap or how-to’s on running a usability test, that would be rad. But we need you to step up and steer part of the time for most of this to work, so if you are interested in some aspect, and especially if you want to volunteer to lead a bit of the time, contact me.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your<br /> name (but not email address, etc.) here<br /> <br /> # Ray Schwartz<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Intro to Git &amp; possibly beyond ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * Erin Fahy, Stanford University, efahy@stanford.edu<br /> * Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu<br /> <br /> We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:<br /> <br /> * What is a Distributed Version Control System?<br /> * What's the difference between Git and Github.com?<br /> * How to initialize new Git projects locally and on a remote server/Github<br /> * Cloning/Forking existing projects and keeping up to date<br /> * The wonderful world of Git branches<br /> * Interactive rebasing<br /> * Contributing code to existing projects &amp; what pull requests are<br /> * How to handle merge conflicts<br /> * Overview of workflows and branch best practices<br /> * (time allowing) Advanced git: pre/post hooks, submodules, anything else?<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Jeannie Graham<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Visualizing Library Data ===<br /> <br /> '''&quot;Half Day [Morning||Afternoon]&quot;''' <br /> <br /> * Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs<br /> <br /> Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ashley Blewer!<br /> # Bobbi Fox<br /> # Ray Schwartz<br /> # Ranti Junus<br /> # Eric Phetteplace<br /> # Joshua Gomez<br /> #<br /> #<br /> #<br /> #<br /> <br /> === CollectionSpace: Getting it up and running at your museum ===<br /> <br /> '''Half Day [Afternoon]'''<br /> <br /> * Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org<br /> * TBD<br /> <br /> This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org<br /> <br /> Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.<br /> <br /> ''Interested in Attending''<br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === DPLA API Workshop: ===<br /> <br /> '''Half Day [Afternoon]''' <br /> <br /> * Audrey Altman, DPLA<br /> * Mark Breedlove, DPLA<br /> * Mark Matienzo, DPLA<br /> * Tom Johnson, DPLA<br /> <br /> The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ranti Junus<br /> # Jean Rainwater<br /> # Mita Williams<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> [[Category:Code4Lib2015]]</div>

Cdmo https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&diff=42073 2014-11-18T13:57:27Z

<p>Cdmo: /* Intro to Docker */</p> <hr /> <div>== Instructions ==<br /> Thank you for considering proposing a pre-conference! Here are a few details:<br /> <br /> * We will be taking pre-conference proposals until '''November 7, 2014'''<br /> * If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu<br /> * Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]<br /> * If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)<br /> * If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu<br /> * '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions<br /> * Please use the template for proposals provided in the pre-formatted block below<br /> <br /> == Pre-conference Proposals ==<br /> <br /> === Delivering and Preserving GIS Data ===<br /> <br /> '''Half Day [Morning]'''<br /> <br /> * Darren Hardy, Stanford University, drh@stanford.edu<br /> * Jack Reed, Stanford University, pjreed@stanford.edu<br /> <br /> We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # [[User:Ssimpkin|Sarah Simpkin]]<br /> # Vicky Steeves<br /> # Andrew Battista<br /> # Peggy Griesinger<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === A hands-on introduction to GeoBlacklight ===<br /> <br /> '''Half Day [Afternoon]'''<br /> <br /> * Darren Hardy, Stanford University, drh@stanford.edu<br /> * Jack Reed, Stanford University, pjreed@stanford.edu<br /> <br /> GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop &quot;Delivering and Preserving GIS Data&quot;.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # [[User:Ssimpkin|Sarah Simpkin]]<br /> # Vicky Steeves<br /> # Andrew Battista<br /> # Peggy Griesinger<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> ===RailsBridge: Intro to programming in Ruby on Rails===<br /> <br /> '''&quot;Half-Day&quot; [morning]'''<br /> <br /> * Contact Carolyn Cole, Penn State University, carolyn@psu.edu<br /> * Additional instructors welcome<br /> <br /> Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.<br /> <br /> RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Maura Carbone<br /> #Vicky Steeves<br /> # Peggy Griesinger<br /> # Mike Price<br /> # Jean Rainwater<br /> # Coral Sheldon-Hess<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Replace yourself with a painfully complex bash script...or try Ansible ===<br /> <br /> '''Half Day [Morning]'''<br /> <br /> * Chad Nelson, chad dot nelson @ lyrasis dot org<br /> * Blake Carver, Blake dot carver @lyrasis dot org<br /> <br /> Abstract: <br /> <br /> [http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> # Ray Schwartz<br /> # Coral Sheldon-Hess<br /> # Kevin S. Clarke<br /> # Joshua Gomez<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Intro to Docker ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * John Fink, McMaster University, john dot fink at gmail dot com<br /> * Francis Kayiwa, University of Maryland Libraries , francis dot kayiwa at gmail dot com<br /> <br /> Abstract:<br /> <br /> [http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.<br /> <br /> ''Interested in Attending''<br /> <br /> # Jim Hahn<br /> # Joshua Gomez<br /> # Bobbi Fox<br /> # Ray Schwartz<br /> # Megan Kudzia<br /> # Coral Sheldon-Hess<br /> # Cary Gordon (uses Docker in production on AWS)<br /> # Eric Phetteplace<br /> # Esther Verreau<br /> # Charlie Morris<br /> #<br /> <br /> === Code Retreat ===<br /> <br /> '''Full Day'''<br /> <br /> * Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu<br /> * Additional facilitators welcome; Especially if you have CodeRetreat experience.<br /> <br /> Abstract:<br /> <br /> &quot;Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.<br /> By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.<br /> Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time.&quot; [http://coderetreat.org/about About Code Retreat]<br /> <br /> ''Interested in Attending''<br /> <br /> # Mike Giarlo<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Presentations workshop ===<br /> <br /> '''&quot;Half Day [Afternoon]&quot;''' (but could be expanded based on interest)<br /> <br /> * Chris Beer, Stanford University, cabeer@stanford.edu<br /> * Additional facilitators welcome.<br /> <br /> This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> #Vicky Steeves<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Dive into Hydra ===<br /> <br /> '''&quot;Half Day [Afternoon]&quot;''' <br /> <br /> * Justin Coyne, Data Curation Experts, justin@curationexperts.com<br /> * Bess Sadler, Stanford University, bess@stanford.edu<br /> <br /> Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend &quot;RailsBridge&quot; prior to this workshop.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Maura Carbone<br /> # Peggy Griesinger<br /> # Mike Price<br /> # Jean Rainwater<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === code4lib/Write The Docs barcamp ===<br /> <br /> '''&quot;Full Day&quot;''', with options for jumping in for half a day<br /> <br /> * code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu<br /> * Write the Docs contacts: TBA<br /> <br /> Abstract<br /> <br /> Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization. <br /> <br /> Remember, like metadata, documentation is a love note to the future.<br /> <br /> More information about Write the Docs at http://conf.writethedocs.org/<br /> <br /> There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> '''Full day'''<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> '''Morning'''<br /> # Ranti Junus<br /> # Mita Williams<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> '''Afternoon'''<br /> # Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon. <br /> # Kevin S. Clarke<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Linked Data Workshop ===<br /> <br /> '''&quot;Half Day [morning]&quot;''' <br /> <br /> * Karen Estlund, University of Oregon, kestlund@uoregon.edu<br /> * Tom Johnson, DPLA, tom@dp.la<br /> <br /> Abstract:<br /> <br /> Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Logan Cox<br /> # Ray Schwartz<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Code4Arc ===<br /> <br /> '''&quot;Full Day&quot;''' (with options for half day participation)<br /> <br /> * Sarah Romkey, Artefactual Systems, sromkey@artefactual.com<br /> * Justin Simpson, Artefactual Systems, jsimpson@artefactual.com<br /> * Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org<br /> * Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com<br /> <br /> Abstract:<br /> <br /> What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how? <br /> <br /> Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.<br /> <br /> The schedule may include the following:<br /> <br /> * Panel type conversations about the State of Art in Archives <br /> * Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed <br /> * Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)<br /> <br /> Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with. <br /> <br /> When signing up, please indicate if you are an end-user or a developer.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Laney McGlohon - developer<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Fail4Lib 2015 ===<br /> <br /> '''Half Day [TBD, probably afternoon]'''<br /> <br /> * Andreas Orphanides, akorphan (at) ncsu.edu<br /> * Jason Casden, jmcasden (at) ncsu.edu<br /> <br /> Abstract:<br /> <br /> Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.<br /> <br /> This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)<br /> <br /> The schedule may include the following:<br /> <br /> * Case studies. Avoid our own mistakes by bearing witness to the failures of others.<br /> * Confessionals, for those willing to share. Let's learn from our own (and each others') failures.<br /> * Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.<br /> <br /> ''Interested in attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ray Schwartz<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Coding Custom Solutions for Every Department in the Library with File Analyzer ===<br /> <br /> '''&quot;Half Day [Morning]&quot;''' <br /> <br /> * Terry Brady, Georgetown University Library, twb27@georgetown.edu<br /> <br /> Abstract<br /> <br /> The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.<br /> <br /> * Analyzing Marc Records for the Cataloging department<br /> * Transferring ILS invoices for the University Account System for the Acquisitions department <br /> * Delivering patron fines to the Bursar’s office for the Access Service department<br /> * Summarizing student worker timesheet data for the Finance department<br /> * Validating counter compliant reports for the Electronic Resources department<br /> * Preparing ingest packages for the Digital Services department<br /> * Validating checksums for the Preservation department<br /> <br /> This hands on workshop will step through the components of the application framework. Workshop participants will install and develop custom File Analyzer tasks in this session.<br /> <br /> The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Megan Kudzia<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * Karen A. Coombs, OCLC, coombsk@oclc.org<br /> <br /> Abstract<br /> Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.<br /> <br /> We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Peggy Griesinger<br /> # Ray Schwartz<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> <br /> === UXtravaganza ===<br /> '''&quot;Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]&quot;'''<br /> <br /> * William Hicks, University of North Texas, William.hicks@unt.edu<br /> * Volunteers?<br /> <br /> Abstract<br /> <br /> I’m envisioning a 1/2 of full day for front-end developers, content strategy people, and other misfits with an interest in user experience, where we can talk about our shared problems, use cases, the state of current research, and play with each other’s sites. A half day seems doable, but if there’s significant enough interest we could push for a full? Here are a few of the things I think might be interesting to see happen:<br /> <br /> * '''Analytics Share-fest:''' A few volunteers demonstrate data about their websites, catalogs, archival/digital collections. Most of us know our own sites but it would be interesting/validating to share this data with others so we can start to see commonalities between institutions, in certain kinds of systems, etc. For anyone using event tracking, or using click- or heat-maps, this would be a great opportunity to show off what people are seeing.<br /> <br /> * '''UX Best Practices Catch Up:''' This spring I had the opportunity to attend a few days worth of usability workshops from the Nielsen-Norman Group, most of which was focused on mobile. I could distill down a lot of the information into an short presentation. Since this is a constantly moving area of research it would be nice to see a few people do other similar short presentations on some current trends/findings relevant to libraries, search, etc.<br /> <br /> * '''Mobile Dev Lab:''' The UNT Libraries has been collecting a small set of smartphones and tablets for testing and development. Basically an [http://labup.org Open Device Lab]. We have about a dozen devices now of varying sizes, OS, OS Versions, + Google Glass. I’ll bring the devices, you can bring yours, and assuming we can get the wifi up and running we can test our sites/services with our big sausage fingers rather than pretending to do so through emulators and the one or two devices we each usually have on hand. If anyone is game they can do a tutorial on Browser-based Inspector Tools, Browser-Cams, or other testing services.<br /> <br /> * '''The Eye’s Have It.''' The UNT Libraries is also in the process of acquiring an eye tracker and software for usability and other gaze-based research studies. We’ll take possession of it shortly after this pre-conference proposal is due and will have a couple of months to play with them before the conference. Assuming we can get our act together learning the device and can get past the technical hurdles of setting it up at the pre-conference, we could try to do some live demos on each other’s sites; i.e. You nominate a site/service, someone in the audience volunteers to wear the device, and we all watch them struggle do the tasks you request on a projector. Rinse. Lather. Repeat. It would hardly be scientific, but it sure would be fun. As a backup, if we have some sites nominated beforehand, I can run a few students at my library through some tasks here and we can show off the results to the crowd.<br /> <br /> For those of you wanting to attend and help out, I’d really like to see some discussion on typography, writing for the web, “dealing with business/administrative requirements from on-high&quot;, maybe do some prototyping exercises, etc. Similarly if anyone is interested in doing some tutorials on bootstrap or how-to’s on running a usability test, that would be rad. But we need you to step up and steer part of the time for most of this to work, so if you are interested in some aspect, and especially if you want to volunteer to lead a bit of the time, contact me.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your<br /> name (but not email address, etc.) here<br /> <br /> # Ray Schwartz<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Intro to Git &amp; possibly beyond ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * Erin Fahy, Stanford University, efahy@stanford.edu<br /> * Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu<br /> <br /> We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:<br /> <br /> * What is a Distributed Version Control System?<br /> * What's the difference between Git and Github.com?<br /> * How to initialize new Git projects locally and on a remote server/Github<br /> * Cloning/Forking existing projects and keeping up to date<br /> * The wonderful world of Git branches<br /> * Interactive rebasing<br /> * Contributing code to existing projects &amp; what pull requests are<br /> * How to handle merge conflicts<br /> * Overview of workflows and branch best practices<br /> * (time allowing) Advanced git: pre/post hooks, submodules, anything else?<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Jeannie Graham<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Visualizing Library Data ===<br /> <br /> '''&quot;Half Day [Morning||Afternoon]&quot;''' <br /> <br /> * Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs<br /> <br /> Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ashley Blewer!<br /> # Bobbi Fox<br /> # Ray Schwartz<br /> # Ranti Junus<br /> # Eric Phetteplace<br /> # Joshua Gomez<br /> #<br /> #<br /> #<br /> #<br /> <br /> === CollectionSpace: Getting it up and running at your museum ===<br /> <br /> '''Half Day [Afternoon]'''<br /> <br /> * Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org<br /> * TBD<br /> <br /> This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org<br /> <br /> Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.<br /> <br /> ''Interested in Attending''<br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === DPLA API Workshop: ===<br /> <br /> '''Half Day [Afternoon]''' <br /> <br /> * Audrey Altman, DPLA<br /> * Mark Breedlove, DPLA<br /> * Mark Matienzo, DPLA<br /> * Tom Johnson, DPLA<br /> <br /> The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ranti Junus<br /> # Jean Rainwater<br /> # Mita Williams<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> [[Category:Code4Lib2015]]</div>

Cdmo https://wiki.code4lib.org/index.php?title=2014_Lightning_Talks&diff=41150 2014-04-23T14:44:34Z

<p>Cdmo: /* Thursday 10:15 AM to 11:00 AM */</p> <hr /> <div>==Tuesday 15:40 PM to 16:40 PM==<br /> # [http://www.ResCarta.org: ResCarta Foundation]<br /> # [https://drive.google.com/file/d/0BzZt7DLxfV4Xd05lTXBjb0xQdGc/edit?usp=sharing SLiMS: Indonesia Grassroot Libraries Revolution] (Arie Nugraha)<br /> # Harvard Library Lab (Bobbi Fox)<br /> # Logs Are Your Friend (Rosalyn Metz)<br /> # Solr Browse &amp; Sort (Michael Gibney)<br /> # GeoHydra (Darren Hardy)<br /> <br /> ==Wednesday 11:00 AM to 12:00 PM==<br /> # Proxy Authentication with Google Open ID<br /> # [http://scholarsphere.psu.edu/files/6395w812z Paired Programming]<br /> # Dial-a-DPLA (Mark Matienzo)<br /> # Copy, Paste &amp; Search (Cory Lown)<br /> # qstat (Hillel Arnold)<br /> # Add map view to Your Blacklight app (Jack Reed)<br /> # Drupal 8: Of Course (Cary Gordan)<br /> # LTI Protocol + Discovery API (LMS &lt;3)<br /> # [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] (Terry Brady)<br /> # Highcharts JS (Heather RayL)<br /> # jQuery.xmleditor<br /> # This is my Search (Cynthia &quot;Arty&quot; Ng)<br /> <br /> ==Thursday 10:15 AM to 11:00 AM==<br /> <br /> # Bplgeo: A Gem to Process Geographic Data / Steven Anderson<br /> # [http://www.slideshare.net/cdmorris22/frogboil Frog Boiling] / Charlie Morris &amp; Angie Fullington<br /> # Dev Ops @ PSU / Justin Patterson<br /> # MozSuite Webmastery, Software Carpentry, Privacy, &amp; Archives / Jeannie Rose Halperin<br /> # Mass Digitization / Tim Shearer<br /> # Schema.org + Google CSE + Local Search / Sean Aery<br /> # Chicago Collections Consortium / Tracy Seneca &amp; Kate Flynn<br /> # Contrary Technologies / Ian Walls<br /> # Browse-Everything for Rails</div>

Cdmo https://wiki.code4lib.org/index.php?title=2014_Lightning_Talks&diff=41045 2014-03-31T13:08:27Z

<p>Cdmo: /* Thursday 10:15 AM to 11:00 AM */</p> <hr /> <div>==Tuesday 15:40 PM to 16:40 PM==<br /> # [http://www.ResCarta.org: ResCarta Foundation]<br /> # [https://drive.google.com/file/d/0BzZt7DLxfV4Xd05lTXBjb0xQdGc/edit?usp=sharing SLiMS: Indonesia Grassroot Libraries Revolution] (Arie Nugraha)<br /> # Harvard Library Lab (Bobbi Fox)<br /> # Logs Are Your Friend (Rosalyn Metz)<br /> # Solr Browse &amp; Sort (Michael Gibney)<br /> # GeoHydra (Darren Hardy)<br /> <br /> ==Wednesday 11:00 AM to 12:00 PM==<br /> # Proxy Authentication with Google Open ID<br /> # Paired Programming<br /> # Dial-a-DPLA (Mark Matienzo)<br /> # Copy, Paste &amp; Search (Cory Lown)<br /> # qstat (Hillel Arnold)<br /> # Add map view to Your Blacklight app (Jack Reed)<br /> # Drupal 8: Of Course (Cary Gordan)<br /> # LTI Protocol + Discovery API (LMS &lt;3)<br /> # [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] (Terry Brady)<br /> # Highcharts JS (Heather RayL)<br /> # jQuery.xmleditor<br /> # This is my Search (Cynthia &quot;Arty&quot; Ng)<br /> <br /> ==Thursday 10:15 AM to 11:00 AM==<br /> <br /> # Bplgeo: A Gem to Process Geographic Data / Steven Anderson<br /> # [http://www.slideshare.net/cdmorris22/frogboil: Frog Boiling] / Charlie Morris &amp; Angie Fullington<br /> # Dev Ops @ PSU / Justin Patterson<br /> # MozSuite Webmastery, Software Carpentry, Privacy, &amp; Archives / Jeannie Rose Halperin<br /> # Mass Digitization / Tim Shearer<br /> # Schema.org + Google CSE + Local Search / Sean Aery<br /> # Chicago Collections Consortium / Tracy Seneca &amp; Kate Flynn<br /> # Contrary Technologies / Ian Walls<br /> # Browse-Everything for Rails</div>

Cdmo https://wiki.code4lib.org/index.php?title=Sponsor_Logos_for_T-Shirt&diff=40287 2014-02-04T14:29:46Z

<p>Cdmo: </p> <hr /> <div>Where a link is provided, there are several versions - select the one that will work best for the particular use.<br /> <br /> * OCLC: http://oclc.org/en-US/news/media-kit/logos.html <br /> * Cherry Hill Company: contact Cary Gordon<br /> * Princeton University Library: http://www.princeton.edu/communications/services/image/graphic/logo/<br /> * DuraSpace: http://www.duraspace.org/logos.php<br /> * UCSD Library: http://www.publications.ucsd.edu/guidelines/logo-request.php (logo request form)<br /> * Penn State: http://agsci.psu.edu/communications/resources/marks<br /> * UPenn: http://www.upenn.edu/computing/web/webdev/style/resources/identity.html (request access)<br /> * Oregon State: http://oregonstate.edu/brand/logo-downloads<br /> * IndexData<br /> * Ebsco: http://support.epnet.com/knowledge_base/detail.php?id=6042<br /> * Kuali OLE<br /> * Proquest https://proquest.com/en-US/affiliates/toolkits/default.shtml<br /> * Nashville Public Library<br /> * Innovative Interfaces, Inc.<br /> * LucidWorks<br /> * User Friendly Consulting, Inc.<br /> * Blacklight: http://www.stanford.edu/~jchris/blacklight-logos/<br /> * DLF / CLIR<br /> <br /> [[Category:Code4Lib2014]]</div>

Cdmo https://wiki.code4lib.org/index.php?title=Sponsor_Logos_for_T-Shirt&diff=40286 2014-02-04T14:26:13Z

<p>Cdmo: </p> <hr /> <div>Where a link is provided, there are several versions - select the one that will work best for the particular use.<br /> <br /> * OCLC: http://oclc.org/en-US/news/media-kit/logos.html <br /> * Cherry Hill Company: contact Cary Gordon<br /> * Princeton University Library: http://www.princeton.edu/communications/services/image/graphic/logo/<br /> * DuraSpace: http://www.duraspace.org/logos.php<br /> * UCSD Library: http://www.publications.ucsd.edu/guidelines/logo-request.php (logo request form)<br /> * Penn State: http://agsci.psu.edu/communications/resources/marks<br /> * UPenn: http://www.upenn.edu/computing/web/webdev/style/resources/identity.html (request access)<br /> * Oregon State: http://oregonstate.edu/brand/logo-downloads<br /> * IndexData<br /> * Ebsco: http://support.epnet.com/knowledge_base/detail.php?id=6042<br /> * Kuali OLE<br /> * Proquest<br /> * Nashville Public Library<br /> * Innovative Interfaces, Inc.<br /> * LucidWorks<br /> * User Friendly Consulting, Inc.<br /> * Blacklight: http://www.stanford.edu/~jchris/blacklight-logos/<br /> * DLF / CLIR<br /> <br /> [[Category:Code4Lib2014]]</div>

Cdmo https://wiki.code4lib.org/index.php?title=Sponsor_Logos_for_T-Shirt&diff=40239 2014-01-11T09:55:53Z

<p>Cdmo: </p> <hr /> <div>Where a link is provided, there are several versions - select the one that will work best for the particular use.<br /> <br /> * OCLC: http://oclc.org/en-US/news/media-kit/logos.html <br /> * Cherry Hill Company: contact Cary Gordon<br /> * Princeton University Library: http://www.princeton.edu/communications/services/image/graphic/logo/<br /> * DuraSpace: http://www.duraspace.org/logos.php<br /> * UCSD Library: http://www.publications.ucsd.edu/guidelines/logo-request.php (logo request form)<br /> * Penn State: http://agsci.psu.edu/communications/resources/marks<br /> * UPenn: http://www.upenn.edu/computing/web/webdev/style/resources/identity.html (request access)<br /> * Oregon State: http://oregonstate.edu/brand/logo-downloads<br /> * IndexData<br /> * Ebsco: https://www.ebscohost.com/customerSuccess/default.php?id=189 (link didn't work for me, CDM)<br /> * Kuali OLE<br /> * Proquest<br /> * Nashville Public Library<br /> * Innovative Interfaces, Inc.<br /> * LucidWorks<br /> * User Friendly Consulting, Inc.<br /> * Blacklight: http://www.stanford.edu/~jchris/blacklight-logos/<br /> * DLF / CLIR<br /> <br /> [[Category:Code4Lib2014]]</div>

Cdmo https://wiki.code4lib.org/index.php?title=Sponsor_Logos_for_T-Shirt&diff=40238 2014-01-11T09:44:28Z

<p>Cdmo: </p> <hr /> <div>Where a link is provided, there are several versions - select the one that will work best for the particular use.<br /> <br /> * OCLC: http://oclc.org/en-US/news/media-kit/logos.html <br /> * Cherry Hill Company: contact Cary Gordon<br /> * Princeton University Library: http://www.princeton.edu/communications/services/image/graphic/logo/<br /> * DuraSpace: http://www.duraspace.org/logos.php<br /> * UCSD Library: http://www.publications.ucsd.edu/guidelines/logo-request.php (logo request form)<br /> * Penn State: http://agsci.psu.edu/communications/resources/marks<br /> * UPenn: http://www.upenn.edu/computing/web/webdev/style/resources/identity.html (request access)<br /> * Oregon State: http://oregonstate.edu/brand/logo-downloads<br /> * IndexData<br /> * Ebsco: https://www.ebscohost.com/customerSuccess/default.php?id=189<br /> * Kuali OLE<br /> * Proquest<br /> * Nashville Public Library<br /> * Innovative Interfaces, Inc.<br /> * LucidWorks<br /> * User Friendly Consulting, Inc.<br /> * Blacklight: http://www.stanford.edu/~jchris/blacklight-logos/<br /> * DLF / CLIR<br /> <br /> [[Category:Code4Lib2014]]</div>

Cdmo https://wiki.code4lib.org/index.php?title=Sponsor_Logos_for_T-Shirt&diff=40237 2014-01-11T09:43:07Z

<p>Cdmo: </p> <hr /> <div>Where a link is provided, there are several versions - select the one that will work best for the particular use.<br /> <br /> * OCLC: http://oclc.org/en-US/news/media-kit/logos.html <br /> * Cherry Hill Company: sent to Code4Lib2014 google group (TMM)<br /> * Princeton: http://www.princeton.edu/communications/services/image/graphic/logo/<br /> * DuraSpace: http://www.duraspace.org/logos.php<br /> * UCSD: http://www.publications.ucsd.edu/guidelines/logo-request.php (logo request form)<br /> * Penn State: http://agsci.psu.edu/communications/resources/marks<br /> * UPenn: http://www.upenn.edu/computing/web/webdev/style/resources/identity.html (request access)<br /> * Oregon State: http://oregonstate.edu/brand/logo-downloads<br /> * IndexData<br /> * Ebsco: https://www.ebscohost.com/customerSuccess/default.php?id=189<br /> * Kuali OLE<br /> * Proquest<br /> * Nashville Public Library<br /> * Innovative Interfaces, Inc.<br /> * LucidWorks<br /> * User Friendly Consulting, Inc.<br /> * Blacklight: http://www.stanford.edu/~jchris/blacklight-logos/<br /> * DLF / CLIR<br /> <br /> [[Category:Code4Lib2014]]</div>

Cdmo https://wiki.code4lib.org/index.php?title=Sponsor_Logos_for_T-Shirt&diff=40236 2014-01-11T09:32:24Z

<p>Cdmo: </p> <hr /> <div>Where a link is provided, there are several versions - select the one that will work best for the particular use.<br /> <br /> * OCLC: http://oclc.org/en-US/news/media-kit/logos.html <br /> * [http://wiki.code4lib.org/index.php/File:Cherryhill_logos.zip Cherry Hill Company] *use one of the logos with text<br /> * Princeton University Library<br /> * DuraSpace: http://www.duraspace.org/logos.php (looking for vector-based)<br /> * UCSD Library: http://www.publications.ucsd.edu/guidelines/logo-request.php (logo request form)<br /> * Penn State: http://agsci.psu.edu/communications/resources/marks<br /> * UPenn<br /> * Oregon State: http://oregonstate.edu/brand/logo-downloads<br /> * IndexData<br /> * Ebsco: https://www.ebscohost.com/customerSuccess/default.php?id=189<br /> * Kuali OLE http://wiki.code4lib.org/index.php/File:Kuali.png<br /> * Proquest<br /> * Nashville Public Library<br /> * Innovative Interfaces, Inc.<br /> * LucidWorks<br /> * User Friendly Consulting, Inc.<br /> * Blacklight: http://www.stanford.edu/~jchris/blacklight-logos/<br /> * DLF / CLIR<br /> <br /> [[Category:Code4Lib2014]]</div>

Cdmo https://wiki.code4lib.org/index.php?title=Sponsor_Logos_for_T-Shirt&diff=40235 2014-01-11T09:26:10Z

<p>Cdmo: </p> <hr /> <div>Where a link is provided, there are several versions - select the one that will work best for the particular use.<br /> <br /> * OCLC: http://oclc.org/en-US/news/media-kit/logos.html <br /> * [http://wiki.code4lib.org/index.php/File:Cherryhill_logos.zip Cherry Hill Company] *use one of the logos with text<br /> * Princeton University Library<br /> * DuraSpace: http://www.duraspace.org/logos.php<br /> * UCSD: http://www.publications.ucsd.edu/guidelines/logo-request.php (logo request form)<br /> * Penn State: http://agsci.psu.edu/communications/resources/marks<br /> * UPenn<br /> * Oregon State: http://oregonstate.edu/brand/logo-downloads<br /> * IndexData<br /> * Ebsco: https://www.ebscohost.com/customerSuccess/default.php?id=189<br /> * Kuali OLE http://wiki.code4lib.org/index.php/File:Kuali.png<br /> * Proquest<br /> * Nashville Public Library<br /> * Innovative Interfaces, Inc.<br /> * LucidWorks<br /> * User Friendly Consulting, Inc.<br /> * Blacklight: http://www.stanford.edu/~jchris/blacklight-logos/<br /> * DLF / CLIR<br /> <br /> [[Category:Code4Lib2014]]</div>

Cdmo https://wiki.code4lib.org/index.php?title=Sponsor_Logos_for_T-Shirt&diff=40234 2014-01-11T09:24:38Z

<p>Cdmo: removed these links because access is required</p> <hr /> <div>Where a link is provided, there are several versions - select the one that will work best for the particular use.<br /> <br /> * OCLC: http://oclc.org/en-US/news/media-kit/logos.html <br /> * [http://wiki.code4lib.org/index.php/File:Cherryhill_logos.zip Cherry Hill Company] *use one of the logos with text<br /> * Princeton <br /> * DuraSpace: http://www.duraspace.org/logos.php<br /> * UCSD: http://www.publications.ucsd.edu/guidelines/logo-request.php (logo request form)<br /> * Penn State: http://agsci.psu.edu/communications/resources/marks<br /> * UPenn<br /> * Oregon State: http://oregonstate.edu/brand/logo-downloads<br /> * IndexData<br /> * Ebsco: https://www.ebscohost.com/customerSuccess/default.php?id=189<br /> * Kuali OLE http://wiki.code4lib.org/index.php/File:Kuali.png<br /> * Proquest<br /> * Nashville Public Library<br /> * Innovative Interfaces, Inc.<br /> * LucidWorks<br /> * User Friendly Consulting, Inc.<br /> * Blacklight: http://www.stanford.edu/~jchris/blacklight-logos/<br /> * DLF / CLIR<br /> <br /> [[Category:Code4Lib2014]]</div>

Cdmo https://wiki.code4lib.org/index.php?title=Sponsor_Logos_for_T-Shirt&diff=40233 2014-01-11T01:15:51Z

<p>Cdmo: </p> <hr /> <div>Where a link is provided, there are several versions - select the one that will work best for the particular use.<br /> <br /> * OCLC: http://oclc.org/en-US/news/media-kit/logos.html <br /> * [http://wiki.code4lib.org/index.php/File:Cherryhill_logos.zip Cherry Hill Company] *use one of the logos with text<br /> * Princeton: http://www.princeton.edu/communications/services/image/graphic/logo/<br /> * DuraSpace: http://www.duraspace.org/logos.php<br /> * UCSD: http://www.publications.ucsd.edu/guidelines/logo-request.php (logo request form)<br /> * Penn State: http://agsci.psu.edu/communications/resources/marks<br /> * UPenn: http://www.upenn.edu/computing/web/webdev/style/resources/identity.html (request access)<br /> * Oregon State: http://oregonstate.edu/brand/logo-downloads<br /> * IndexData<br /> * Ebsco: https://www.ebscohost.com/customerSuccess/default.php?id=189<br /> * Kuali OLE http://wiki.code4lib.org/index.php/File:Kuali.png<br /> * Proquest<br /> * Nashville Public Library<br /> * Innovative Interfaces, Inc.<br /> * LucidWorks<br /> * User Friendly Consulting, Inc.<br /> * Blacklight: http://www.stanford.edu/~jchris/blacklight-logos/<br /> * DLF / CLIR<br /> <br /> [[Category:Code4Lib2014]]</div>

Cdmo https://wiki.code4lib.org/index.php?title=Sponsor_Logos_for_T-Shirt&diff=40232 2014-01-11T01:15:15Z

<p>Cdmo: </p> <hr /> <div>Where a link is provided, there are several versions - select the one that will work best for the particular use.<br /> <br /> * OCLC: http://oclc.org/en-US/news/media-kit/logos.html <br /> * [Cherry Hill Company http://wiki.code4lib.org/index.php/File:Cherryhill_logos.zip]<br /> * Princeton: http://www.princeton.edu/communications/services/image/graphic/logo/<br /> * DuraSpace: http://www.duraspace.org/logos.php<br /> * UCSD: http://www.publications.ucsd.edu/guidelines/logo-request.php (logo request form)<br /> * Penn State: http://agsci.psu.edu/communications/resources/marks<br /> * UPenn: http://www.upenn.edu/computing/web/webdev/style/resources/identity.html (request access)<br /> * Oregon State: http://oregonstate.edu/brand/logo-downloads<br /> * IndexData<br /> * Ebsco: https://www.ebscohost.com/customerSuccess/default.php?id=189<br /> * Kuali OLE http://wiki.code4lib.org/index.php/File:Kuali.png<br /> * Proquest<br /> * Nashville Public Library<br /> * Innovative Interfaces, Inc.<br /> * LucidWorks<br /> * User Friendly Consulting, Inc.<br /> * Blacklight: http://www.stanford.edu/~jchris/blacklight-logos/<br /> * DLF / CLIR<br /> <br /> [[Category:Code4Lib2014]]</div>

Cdmo https://wiki.code4lib.org/index.php?title=File:Cherryhill_logos.zip&diff=40231 2014-01-11T01:09:57Z

<p>Cdmo: </p> <hr /> <div></div>

Cdmo https://wiki.code4lib.org/index.php?title=Sponsor_Logos_for_T-Shirt&diff=40223 2014-01-08T20:58:02Z

<p>Cdmo: </p> <hr /> <div>Where a link is provided, there are several versions - select the one that will work best for the particular use.<br /> <br /> * OCLC: http://oclc.org/en-US/news/media-kit/logos.html <br /> * Cherry Hill Company: sent to Code4Lib2014 google group (TMM)<br /> * Princeton: http://www.princeton.edu/communications/services/image/graphic/logo/<br /> * DuraSpace: http://www.duraspace.org/logos.php<br /> * UCSD: http://www.publications.ucsd.edu/guidelines/logo-request.php (logo request form)<br /> * Penn State: http://agsci.psu.edu/communications/resources/marks<br /> * UPenn: http://www.upenn.edu/computing/web/webdev/style/resources/identity.html (request access)<br /> * Oregon State: http://oregonstate.edu/brand/logo-downloads<br /> * IndexData<br /> * Ebsco: https://www.ebscohost.com/customerSuccess/default.php?id=189<br /> * Kuali OLE http://wiki.code4lib.org/index.php/File:Kuali.png<br /> * Proquest<br /> * Nashville Public Library<br /> * Innovative Interfaces, Inc.<br /> * LucidWorks<br /> * User Friendly Consulting, Inc.<br /> * Blacklight: http://www.stanford.edu/~jchris/blacklight-logos/<br /> * DLF / CLIR<br /> <br /> [[Category:Code4Lib2014]]</div>

Cdmo https://wiki.code4lib.org/index.php?title=File:Kuali.png&diff=40222 2014-01-08T20:55:06Z

<p>Cdmo: Kuali logo</p> <hr /> <div>Kuali logo</div>

Cdmo https://wiki.code4lib.org/index.php?title=2014_t-shirt_design_proposals&diff=40189 2014-01-04T02:45:10Z

<p>Cdmo: </p> <hr /> <div>= Code4Lib 2014 T-Shirt Design Proposals =<br /> <br /> Designs for the official Code4Lib 2014 conference are now being solicited! Submit your proposal by &lt;strike&gt;January 3&lt;/strike&gt; '''January 6''' for consideration! <br /> <br /> What to do:<br /> * Post an image file of your print-ready proposal by editing this wiki page. You can host the image yourself or use the [[Special:Upload|Upload file]] feature of the wiki. If your print-ready document is different from your displayed image, include a link to the print-ready file.<br /> * Include your name and e-mail address with your proposal.<br /> * If you want, you can add a line or two of explanatory text, color specifications, etc., which will be included with your design on the Dieboldatron.<br /> * Place a horizontal rule (----) on a separate line after your submission.<br /> <br /> Design considerations:<br /> * T-shirt designs should be one-sided, single color designs suitable for screenprinting.<br /> * This year's shirt will NOT BE BLACK. We anticipate that it will be available in 3 colors: Carolina Blue (light blue), Duke blue (royal blue), and NC State red, as long as this works with the t-shirt design itself.<br /> <br /> Tedious administrivia:<br /> * All proposals posted to this wiki page before 11:59 PM EST &lt;strike&gt;January 3&lt;/strike&gt; '''January 6''' will be considered.<br /> * The winning design will be selected via community-wide voting in January.<br /> * Questions? Direct them to cdmorris22 (at) gmail (dot) com and joshwilsonnc (at) gmail (dot) com. One of us will get you an answer.<br /> <br /> == Sample submission == <br /> <br /> Joe Ouroboros, joe (at) loopback.edu :<br /> <br /> [[Image:Reset-200.png]]<br /> <br /> This is my awesome design. It'll win one of these years.<br /> <br /> ----<br /> <br /> == Submissions ==<br /> <br /> List your submissions below!<br /> <br /> ----<br /> <br /> Jeffrey Sabol jeffrey.sabol@cui.edu:<br /> <br /> [[File:code4lib_tshirt.jpeg]]<br /> <br /> White ink on a dark color T-shirt OR Black ink on a light color shirt <br /> <br /> ----<br /> <br /> <br /> <br /> Favenzio Calvo fcalvo at fsu dot edu<br /> <br /> [[File:Shirt_design_code4lib_small.png]]<br /> <br /> [http://lib.fsu.edu/sites/default/files/shirt_design_code4lib.png Print Ready File]<br /> <br /> ----<br /> <br /> Chris Markman cmarkman@clarku.edu<br /> <br /> [[file:cmarkman-shirt.gif]]</div>

Cdmo https://wiki.code4lib.org/index.php?title=2014_t-shirt_design_proposals&diff=40169 2013-12-23T15:55:00Z

<p>Cdmo: /* Submissions */</p> <hr /> <div>= Code4Lib 2014 T-Shirt Design Proposals =<br /> <br /> Designs for the official Code4Lib 2014 conference are now being solicited! Submit your proposal by '''January 3''' for consideration! <br /> <br /> What to do:<br /> * Post an image file of your print-ready proposal by editing this wiki page. You can host the image yourself or use the [[Special:Upload|Upload file]] feature of the wiki. If your print-ready document is different from your displayed image, include a link to the print-ready file.<br /> * Include your name and e-mail address with your proposal.<br /> * If you want, you can add a line or two of explanatory text, color specifications, etc., which will be included with your design on the Dieboldatron.<br /> * Place a horizontal rule (----) on a separate line after your submission.<br /> <br /> Design considerations:<br /> * T-shirt designs should be one-sided, single color designs suitable for screenprinting.<br /> * This year's shirt color is TBD. We are working with vendors to determine cost-effective options. Note that we anticipate that the t-shirts will NOT BE BLACK.<br /> <br /> Tedious administrivia:<br /> * All proposals posted to this wiki page before 11:59 PM EST January 3 will be considered.<br /> * The winning design will be selected via community-wide voting in January.<br /> * Questions? Direct them to cdmorris22 (at) gmail (dot) com and joshwilsonnc (at) gmail (dot) com. One of us will get you an answer.<br /> <br /> == Sample submission == <br /> <br /> Joe Ouroboros, joe (at) loopback.edu :<br /> <br /> [[Image:Reset-200.png]]<br /> <br /> This is my awesome design. It'll win one of these years.<br /> <br /> ----<br /> <br /> == Submissions ==<br /> <br /> List your submissions below!<br /> <br /> ----<br /> <br /> Jeffrey Sabol jeffrey.sabol@cui.edu:<br /> <br /> [[File:code4lib_tshirt.jpeg]]<br /> <br /> White ink on a dark color T-shirt OR Black ink on a light color shirt <br /> <br /> ----<br /> <br /> Charlie Morris cdmorris22 at gmail dot com<br /> <br /> [[File:C4l2014_piggy-_charlie_morris.png]]<br /> <br /> [http://thenounproject.com/term/pig/5271/ Pig] designed by aLf from the Noun Project. <br /> <br /> ----</div>

Cdmo https://wiki.code4lib.org/index.php?title=2014_t-shirt_design_proposals&diff=40168 2013-12-23T13:46:45Z

<p>Cdmo: /* Submissions */</p> <hr /> <div>= Code4Lib 2014 T-Shirt Design Proposals =<br /> <br /> Designs for the official Code4Lib 2014 conference are now being solicited! Submit your proposal by '''January 3''' for consideration! <br /> <br /> What to do:<br /> * Post an image file of your print-ready proposal by editing this wiki page. You can host the image yourself or use the [[Special:Upload|Upload file]] feature of the wiki. If your print-ready document is different from your displayed image, include a link to the print-ready file.<br /> * Include your name and e-mail address with your proposal.<br /> * If you want, you can add a line or two of explanatory text, color specifications, etc., which will be included with your design on the Dieboldatron.<br /> * Place a horizontal rule (----) on a separate line after your submission.<br /> <br /> Design considerations:<br /> * T-shirt designs should be one-sided, single color designs suitable for screenprinting.<br /> * This year's shirt color is TBD. We are working with vendors to determine cost-effective options. Note that we anticipate that the t-shirts will NOT BE BLACK.<br /> <br /> Tedious administrivia:<br /> * All proposals posted to this wiki page before 11:59 PM EST January 3 will be considered.<br /> * The winning design will be selected via community-wide voting in January.<br /> * Questions? Direct them to cdmorris22 (at) gmail (dot) com and joshwilsonnc (at) gmail (dot) com. One of us will get you an answer.<br /> <br /> == Sample submission == <br /> <br /> Joe Ouroboros, joe (at) loopback.edu :<br /> <br /> [[Image:Reset-200.png]]<br /> <br /> This is my awesome design. It'll win one of these years.<br /> <br /> ----<br /> <br /> == Submissions ==<br /> <br /> List your submissions below!<br /> <br /> ----<br /> <br /> Jeffrey Sabol jeffrey.sabol@cui.edu:<br /> <br /> [[File:code4lib_tshirt.jpeg]]<br /> <br /> White ink on a dark color T-shirt OR Black ink on a light color shirt <br /> <br /> ----<br /> <br /> Charlie Morris cdmorris22 at gmail dot com<br /> <br /> [[File:C4l2014_piggy-_charlie_morris.png]]<br /> <br /> [http://thenounproject.com/term/pig/16866/ Pig] designed by aLf from the Noun Project. <br /> <br /> ----</div>

Cdmo https://wiki.code4lib.org/index.php?title=File:C4l2014_piggy-_charlie_morris.png&diff=40167 2013-12-23T13:38:29Z

<p>Cdmo: c4l 2014 t-shirt design submission, it's a pig</p> <hr /> <div>c4l 2014 t-shirt design submission, it's a pig</div>

Cdmo https://wiki.code4lib.org/index.php?title=2014_preconference_proposals&diff=40080 2013-12-09T14:11:53Z

<p>Cdmo: /* Interested in Attending: */</p> <hr /> <div>==Code4Lib 2014 Pre-Conference Proposals==<br /> <br /> = PROPOSALS ARE CLOSED : PLEASE DO NOT EDIT THIS PAGE =<br /> <br /> Proposals were accepted through December 6th, 2013.<br /> <br /> <br /> <br /> <br /> ===Note===<br /> Attendance at a pre-conference will require a small fee ''due at the time of conference registration.<br /> <br /> Although this was specified in the email announcements relating to pre-conferences, it was not added to this page until December 2nd. I (Adam C.) apologize for the omission and I hope this will not cause any &quot;sticker shock.&quot; Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.<br /> <br /> Please put your pre-conference on the list in the following format:<br /> <br /> ===NAME===<br /> '''&quot;Full-Day|Half-Day&quot; [PREFERRED TIME]'''<br /> <br /> Description<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> ----<br /> <br /> <br /> <br /> ===Drupal4lib Sub-con Barcamp===<br /> =====Full Day=====<br /> <br /> * Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.<br /> <br /> This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).<br /> <br /> [[resources to help you learn drupal]]<br /> <br /> ====Interested in Attending:====<br /> <br /> =====All Day=====<br /> <br /> * Renna Tuten <br /> <br /> =====Morning=====<br /> <br /> * Kevin Reiss<br /> * Charlie Morris (NCSU) - glad to see this again this year!<br /> <br /> =====Afternoon=====<br /> <br /> &amp;nbsp;<br /> ----<br /> <br /> ===Open Refine Hackfest===<br /> '''&quot;Half-Day&quot;'''<br /> * Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com<br /> <br /> [http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control<br /> <br /> The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use. <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> Adam Constabaris<br /> <br /> ----<br /> <br /> ===Responsive Design Hackfest===<br /> '''&quot;Half-Day [Afternoon]&quot;''' <br /> * Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com<br /> * Contact David Ward, University of Illinois, dh-ward@illinois.edu<br /> <br /> This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php]. <br /> <br /> Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.<br /> <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> === Intro to Blacklight ===<br /> '''&quot;Half-Day [Morning]&quot;''' <br /> * Contact: Chris Beer, Stanford University, cabeer@stanford.edu<br /> * TA: Bess Sadler, Stanford University, bess@stanford.edu<br /> <br /> This session will be walk-through of the architecture of Blacklight, the community, and an introduction to building a Blacklight-based application. Each participant will have the opportunity to build a simple Blacklight application, and make basic customizations, while using a test-driven approach.<br /> <br /> 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.<br /> <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> #Megan Kudzia<br /> #Bret Davidson<br /> #Coral Sheldon-Hess<br /> <br /> ===Blacklight Hackfest===<br /> '''&quot;Half-Day [Afternoon]&quot;''' <br /> * Contact Chris Beer, Stanford University, cabeer@stanford.edu<br /> <br /> This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.<br /> <br /> For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ).<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> 1. Shaun Ellis<br /> 2. Kevin Reiss<br /> <br /> ===RailsBridge: Intro to programming in Ruby on Rails===<br /> '''&quot;Half-Day&quot; [morning]'''<br /> * Contact Justin Coyne, Data Curation Experts, justin@curationexperts.com<br /> <br /> Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! RailsBridge is a friendly place to get together and learn how to write some code.<br /> <br /> RailsBridge is a great workshop that opens the doors to projects like Blacklight and Hydra.<br /> <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> 1. Ayla Stein<br /> <br /> 2. Heidi Dowding<br /> <br /> ===Managing Projects: Or I'm in charge, now what? (aka PM4Lib)===<br /> '''Full-Day'''<br /> <br /> Contact: <br /> * [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com<br /> * [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu<br /> <br /> This will be a full day session on project management. We'll cover<br /> * '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment<br /> * '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets<br /> * '''Executing the Project''' -- status meeting, status reports, issue management<br /> * '''Finishing the Project''' -- achieving the goal, post mortems, project v. product<br /> This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good) and adapted to c4lib types.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> 1. Robin Dean<br /> <br /> ===Fail4Lib 2014===<br /> '''Half Day [TBD, probably afternoon]'''<br /> <br /> Contacts: <br /> * Andreas Orphanides, akorphan (at) ncsu.edu<br /> * Jason Casden, jmcasden (at) ncsu.edu<br /> <br /> The task of design (and the work that we do as library coders) is intimately tied to failure. Failures, both big and small, motivate us to create and improve. Failures are also occasionally the result of our work. Understanding and embracing failure, encouraging enlightened risk-taking, and seeking out opportunities to fail and learn are essential to success in our field. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be feared.<br /> <br /> The schedule may include the following:<br /> <br /> * Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?<br /> * Confessionals, for those willing to share. Talk about your own experiences with rough starts, labor pains, and doomed projects in your own work: What can we learn from our own (and each others') failures?<br /> * Group therapy. Let's talk about how to deal with risk management, failed projects, experimental endeavors, and more: How can we make ourselves, our colleagues, and our organizations more fault tolerant? How do we make sure we fail as productively as possible?<br /> <br /> ''Interested in attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> #Bret Davidson<br /> <br /> <br /> ===CLLAM @ code4lib===<br /> '''(Computational Linguistics for Libraries, Archives and Museums)'''<br /> <br /> '''Full Day'''<br /> <br /> Contacts: <br /> * Douglas W. Oard (primary), oard (at) umd.edu <br /> * Corey Harper, corey (dot) harper (at) nyu.edu<br /> * Robert Sanderson, azaroth42 (at) gmail.com <br /> * Robert Warren, rwarren (at) math.carleton.ca<br /> <br /> We will hack at the intersection of diverse content from Libraries, Archives and Museums and bleeding edge tools from computational linguistics for slicing and dicing that content. Did you just acquire the email archives of a startup company? Maybe you can automatically build an org chart. Have you got metadata in a slew of languages? Perhaps you can search it all using one query. Is name authority control for e-resources getting too costly? Let’s see if entity linking techniques can help. These are just a few teasers. <br /> <br /> There’ll be plenty of content and tools supplied, but please bring your own [data] too -- you’ll hack with it in new ways throughout the day. We’ll get started with some lightning talks on what we’ve brought,then we’ll break up into groups to experiment and work on the ideas that appeal. Three guaranteed outcomes: you’ll walk away with new ideas, new tools, and new people you’ll have met.<br /> <br /> ''Interested in attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Devon Smith<br /> # Kevin S. Clarke<br /> <br /> === GeoHydra: Managing geospatial content ===<br /> <br /> '''Half-day [Afternoon]'''<br /> <br /> * Contact: Darren Hardy, Stanford University, drh@stanford.edu<br /> * Moderator: Bess Sadler, Stanford University, bess@stanford.edu<br /> <br /> Do you have digitized maps, GIS datasets like Shapefiles, aerial photography,<br /> etc., all of which you want to integrate into your digital repository? In this<br /> workshop, we will discuss how Hydra can provide discovery, delivery, and<br /> management services for geospatial assets, as well as solicit questions about<br /> your own GIS projects. We aim to help answer the following questions you might have about putting geospatial data into your Hydra-based digital library:<br /> <br /> * What are the types of geospatial data?<br /> * How to dive into Hydra?<br /> * How to model geospatial holdings with Hydra?<br /> * How to discover and view geospatial data?<br /> * How to build a geospatial data infrastructure?<br /> * What are common approaches and problems?<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Esmé Cowles<br /> <br /> ===Technology, Librarianship, and Gender: Moving the conversation forward===<br /> '''Full Day'''<br /> <br /> Contact: Lisa Rabey lisa @ biblyotheke dot net | [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]<br /> <br /> '''Description'''<br /> <br /> Librarianship is largely made up of women, yet women are significantly underrepresented in tech positions, on any level, within libraries themselves. Why? What are we doing to encourage women to become more involved in STEM within librarianship? What kind of message are we sending when library technology keynotes remain almost resolutely male? How are we changing the face of technology, not only within libraries, but with the field itself? How are we training our staff and colleagues in the areas of fairness and removal of bias? Our vendors?<br /> <br /> Lots of tough questions.<br /> <br /> While the conversation has been going on via various blogs and articles within the last few years, it was given a public face at [http://infotoday.com/il2013/day.asp?day=Monday#session_D105 Internet Librarian 2013] where a panel of 7 (four women, three men) gave personal experiences on the above and then opened up the conversation to the audience. As eye opening and enriching the conversation was, a 45 minute panel was not enough. One thing remains clear: We need to keep the conversation moving forward and start making some radical changes in the way we think, act, and how we need to harness this to start making real changes within librarianship itself.<br /> <br /> Topics to include: Fairness, bias, impostor syndrome, code of conducts, sexual harassment, training opportunities, support systems, mentoring, ally support, and more<br /> <br /> Those attending should expect: Begin with opening up the conversation of experiences and talking about what is most needed, spending remaining time putting together live, usable solutions to start implementing as well as pushing the conversation forward at local levels<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> =====All Day=====<br /> 1. Kate Kosturski<br /> <br /> 2. Valerie Aurora<br /> <br /> 3. Declan Fleming<br /> <br /> =====Morning=====<br /> 1. Shaun Ellis<br /> <br /> 2. Jason Casden<br /> <br /> =====Afternoon=====<br /> 1. Ayla Stein<br /> <br /> 2. Heidi Dowding<br /> <br /> 3. Coral Sheldon-Hess<br /> ----<br /> <br /> ===FileAnalyzer: Rapid Development of File Manipulation Tasks===<br /> '''&quot;Half-Day&quot; [morning]'''<br /> * Contact Terry Brady, twb27@georgetown.edu<br /> <br /> The FileAnalyzer (https://github.com/Georgetown-University-Libraries/File-Analyzer) is an application designed to solve a number of library automation challenges:<br /> <br /> * validating digitized and reformatted files<br /> * validating vendor statistics for counter compliance<br /> * preparing collections of digital files for archiving and ingest<br /> * manipulating ILS import and export files<br /> <br /> The File Analyzer application was used by the US National Archives to validate 3.5 million digitized images from the 1940 Census. After implementing a customized ingest workflow within the File Analyzer, the Georgetown University Libraries was able to process an ingest backlog of over a thousand files of digital resources into DigitalGeorgetown, the Libraries’ Digital Collections and Institutional Repository platform. Georgetown is currently developing customized workflows that integrate Apache Tika, BagIt, and Marc conversion utilities.<br /> <br /> The File Analyzer is a desktop application with a powerful framework for implementing customized file validation and transformation rules. As new rules are deployed, they are presented to users within a user interface that is easy (and powerful) to use.<br /> <br /> The first half of this session will be targeted to potential users and developers. The second half of the session will be targeted towards developers who are interested in developing custom rules for the application.<br /> <br /> ''Session Overview''<br /> * Overview of the application<br /> * Running sample file tests/transformations through the application<br /> * Compiling and building the application<br /> * Coding a custom file processing task<br /> <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> ----<br /> <br /> <br /> ===Collecting social media data with Social Feed Manager===<br /> '''Half-Day [Morning]'''<br /> <br /> Contacts: <br /> * Dan Chudnov, GW Libraries, dchud (at) gwu.edu<br /> * Dan Kerchner, GW Libraries, kerchner (at) gwu.edu<br /> * Laura Wrubel, GW Libraries, lwrubel (at) gwu.edu<br /> <br /> Social media data is a popular material for research and a new format for building collections. What does it take to collect meaningfully from Twitter, Tumblr, YouTube, Weibo, Facebook, and other sites? We will:<br /> * Introduce options for collections, including both high- and low-end commercial offerings. Discuss what it means to collect these resources, covering boundaries, policies, and workflows required to develop a social media collection program in your institution.<br /> * Explore the Twitter API in depth, with hands-on opportunities for those w/laptops and others who want to team up w/them<br /> * Help you get started using the free [http://gwu-libraries.github.io/social-feed-manager Social Feed Manager] (SFM) app we're developing at GW to create your first collections. We’ll demo its use and demo a clean install (those w/environments can follow along)<br /> <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Declan Fleming<br /> # Esmé Cowles<br /> ----<br /> <br /> === Intro to Git ===<br /> '''&quot;Half-Day [tbd - probably afternoon]&quot;''' <br /> * Contact: Erin Fahy, Stanford University, efahy at stanford.edu<br /> * TA: Michael Klein, Northwestern University, michael.klein at northwestern.edu<br /> <br /> This session will cover the fundamentals of git by discussing/going through (time allowing):<br /> * what is a distributed version control system<br /> * what is git and github<br /> * initializing a repo on a remote server/github<br /> * cloning an existing repo<br /> * creating a branch<br /> * contributing code to a repo<br /> * how to handle merge conflicts<br /> <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> ----<br /> <br /> === Archival discovery and use ===<br /> '''Full Day''' <br /> <br /> Contacts: <br /> * Tim Shearer, UNC Chapel Hill, tshearer at email.unc.edu, <br /> * Will Sexton, Duke, will.sexton at duke.edu<br /> <br /> This is a full day pre-conference about archival collections and will cover the intersections of archives, workflows, technologies, discovery, and use.<br /> <br /> Morning agenda: focused talks around (but not limited to) issues such as:<br /> * Crowd-sourcing description to enhance collecitons<br /> * Linked data and authority<br /> * Mass digitization and sustainable workflows<br /> * Digitized objects in context (images and other objects in finding aids)<br /> * Too many cooks in the kitchen: versioning<br /> * Global-, intra-, and inter- discovery of archival materials via finding aids <br /> * and more...<br /> <br /> Afternoon agenda: Focused talks around specific tools followed by general discussion, connections, opportunities, aspirations, and planning.<br /> <br /> Tool examples:<br /> * Archivespace<br /> * STEADy<br /> * &quot;RAMP&quot; (Remixing Archival Metadata Project)<br /> * OpenRefine<br /> * Aeon<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> Morning:<br /> * your name<br /> <br /> Afternoon:<br /> * your name<br /> <br /> All day:<br /> * your name<br /> <br /> ----<br /> <br /> ===AV Content Slam===<br /> '''Half-Day [morning]'''<br /> Contacts:<br /> * Kara Van Malssen, kara (at) avpreserve.com<br /> * Lauren Sorenson, laurens (at) bavc.org<br /> * Steven Villereal , villereal (at) gmail.com<br /> A morning BarCamp/unconference for practitioners and coders who work with audiovisual content. The agenda will be attendee-driven, with a focus on sharing, synthesizing, and improving workflow strategies and documentation for software-based approaches to wrangling and providing access to audio and video content.<br /> Possible topics of discussion might include:<br /> * Use of format id and characterization/metadata extraction tools for AV<br /> * Creating and using time-based metadata<br /> * Managing (moving, fixity checking, etc) massive files (like uncompressed video)<br /> For a better idea of the topics and concerns that have informed some past AV-themed events, check out the event wikis for [http://wiki.curatecamp.org/index.php/CURATEcamp_AVpres_2013 CURATEcamp AVpres 2013] as well as the [http://wiki.curatecamp.org/index.php/Association_of_Moving_Image_Archivists_%26_Digital_Library_Federation_Hack_Day_2013 AMIA/DLF 2013 Hack Day] .<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:<br /> <br /> ----<br /> <br /> ===OCLC Web Services Hackfest===<br /> <br /> &quot;Half-Day&quot; [afternoon]<br /> <br /> Contact: Shelley Hostetler, Community Manager, Developer Network hostetls[at]oclc.org<br /> <br /> This half-day hackfest will explore some of the OCLC Developer Network web services. We will provide an overview of some of the common topics such as the general REST-based architecture for most services and how to use some new authentication clients. The group can then decide to take a deep dive into a particular API and/or write a client library for the community.<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:<br /> <br /> <br /> ----<br /> <br /> <br /> ===Obey the Testing Goat!: Test Driven Web Development From The Ground Up===<br /> '''Half-Day [tbd - probably afternoon]'''<br /> * Contact [[User:Mredar|Mark Redar]], mredar[at]gmail.com<br /> <br /> Test driven development is a proven method for producing better quality code. But I've found it hard to follow a strict TDD methodology when starting new web projects. How do you write that first test when there is no code or web pages created yet.<br /> <br /> In this session, we will follow the excellent book [http://shop.oreilly.com/product/0636920029533.do &quot;Test-Driven Web Development with Python&quot;] to create a simple web site in Django following TDD from the first character typed. Come ready to code and test. No prior knowledge of python or Django required.<br /> <br /> By the end of this session, you should be able to [http://www.obeythetestinggoat.com/ &quot;Obey the Testing Goat&quot;] from the start to finish for your next project.<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:<br /> <br /> * Charlie Morris (NCSU)<br /> <br /> ===Summon Camp===<br /> Placeholder by Tim McGeary for Gillian Cain (Serials Solutions)<br /> Description to be provided by Gillian after account issues resolved. <br /> <br /> ----<br /> <br /> [[:Category:Code4Lib2014]]</div>

Cdmo https://wiki.code4lib.org/index.php?title=2014_preconference_proposals&diff=40079 2013-12-09T14:10:43Z

<p>Cdmo: /* Obey the Testing Goat!: Test Driven Web Development From The Ground Up */</p> <hr /> <div>==Code4Lib 2014 Pre-Conference Proposals==<br /> <br /> = PROPOSALS ARE CLOSED : PLEASE DO NOT EDIT THIS PAGE =<br /> <br /> Proposals were accepted through December 6th, 2013.<br /> <br /> <br /> <br /> <br /> ===Note===<br /> Attendance at a pre-conference will require a small fee ''due at the time of conference registration.<br /> <br /> Although this was specified in the email announcements relating to pre-conferences, it was not added to this page until December 2nd. I (Adam C.) apologize for the omission and I hope this will not cause any &quot;sticker shock.&quot; Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.<br /> <br /> Please put your pre-conference on the list in the following format:<br /> <br /> ===NAME===<br /> '''&quot;Full-Day|Half-Day&quot; [PREFERRED TIME]'''<br /> <br /> Description<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> ----<br /> <br /> <br /> <br /> ===Drupal4lib Sub-con Barcamp===<br /> =====Full Day=====<br /> <br /> * Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.<br /> <br /> This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).<br /> <br /> [[resources to help you learn drupal]]<br /> <br /> ====Interested in Attending:====<br /> <br /> =====All Day=====<br /> Renna Tuten <br /> <br /> =====Morning=====<br /> <br /> Kevin Reiss<br /> <br /> =====Afternoon=====<br /> <br /> &amp;nbsp;<br /> ----<br /> <br /> ===Open Refine Hackfest===<br /> '''&quot;Half-Day&quot;'''<br /> * Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com<br /> <br /> [http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control<br /> <br /> The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use. <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> Adam Constabaris<br /> <br /> ----<br /> <br /> ===Responsive Design Hackfest===<br /> '''&quot;Half-Day [Afternoon]&quot;''' <br /> * Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com<br /> * Contact David Ward, University of Illinois, dh-ward@illinois.edu<br /> <br /> This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php]. <br /> <br /> Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.<br /> <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> === Intro to Blacklight ===<br /> '''&quot;Half-Day [Morning]&quot;''' <br /> * Contact: Chris Beer, Stanford University, cabeer@stanford.edu<br /> * TA: Bess Sadler, Stanford University, bess@stanford.edu<br /> <br /> This session will be walk-through of the architecture of Blacklight, the community, and an introduction to building a Blacklight-based application. Each participant will have the opportunity to build a simple Blacklight application, and make basic customizations, while using a test-driven approach.<br /> <br /> 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.<br /> <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> #Megan Kudzia<br /> #Bret Davidson<br /> #Coral Sheldon-Hess<br /> <br /> ===Blacklight Hackfest===<br /> '''&quot;Half-Day [Afternoon]&quot;''' <br /> * Contact Chris Beer, Stanford University, cabeer@stanford.edu<br /> <br /> This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.<br /> <br /> For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ).<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> 1. Shaun Ellis<br /> 2. Kevin Reiss<br /> <br /> ===RailsBridge: Intro to programming in Ruby on Rails===<br /> '''&quot;Half-Day&quot; [morning]'''<br /> * Contact Justin Coyne, Data Curation Experts, justin@curationexperts.com<br /> <br /> Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! RailsBridge is a friendly place to get together and learn how to write some code.<br /> <br /> RailsBridge is a great workshop that opens the doors to projects like Blacklight and Hydra.<br /> <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> 1. Ayla Stein<br /> <br /> 2. Heidi Dowding<br /> <br /> ===Managing Projects: Or I'm in charge, now what? (aka PM4Lib)===<br /> '''Full-Day'''<br /> <br /> Contact: <br /> * [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com<br /> * [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu<br /> <br /> This will be a full day session on project management. We'll cover<br /> * '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment<br /> * '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets<br /> * '''Executing the Project''' -- status meeting, status reports, issue management<br /> * '''Finishing the Project''' -- achieving the goal, post mortems, project v. product<br /> This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good) and adapted to c4lib types.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> 1. Robin Dean<br /> <br /> ===Fail4Lib 2014===<br /> '''Half Day [TBD, probably afternoon]'''<br /> <br /> Contacts: <br /> * Andreas Orphanides, akorphan (at) ncsu.edu<br /> * Jason Casden, jmcasden (at) ncsu.edu<br /> <br /> The task of design (and the work that we do as library coders) is intimately tied to failure. Failures, both big and small, motivate us to create and improve. Failures are also occasionally the result of our work. Understanding and embracing failure, encouraging enlightened risk-taking, and seeking out opportunities to fail and learn are essential to success in our field. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be feared.<br /> <br /> The schedule may include the following:<br /> <br /> * Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?<br /> * Confessionals, for those willing to share. Talk about your own experiences with rough starts, labor pains, and doomed projects in your own work: What can we learn from our own (and each others') failures?<br /> * Group therapy. Let's talk about how to deal with risk management, failed projects, experimental endeavors, and more: How can we make ourselves, our colleagues, and our organizations more fault tolerant? How do we make sure we fail as productively as possible?<br /> <br /> ''Interested in attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> #Bret Davidson<br /> <br /> <br /> ===CLLAM @ code4lib===<br /> '''(Computational Linguistics for Libraries, Archives and Museums)'''<br /> <br /> '''Full Day'''<br /> <br /> Contacts: <br /> * Douglas W. Oard (primary), oard (at) umd.edu <br /> * Corey Harper, corey (dot) harper (at) nyu.edu<br /> * Robert Sanderson, azaroth42 (at) gmail.com <br /> * Robert Warren, rwarren (at) math.carleton.ca<br /> <br /> We will hack at the intersection of diverse content from Libraries, Archives and Museums and bleeding edge tools from computational linguistics for slicing and dicing that content. Did you just acquire the email archives of a startup company? Maybe you can automatically build an org chart. Have you got metadata in a slew of languages? Perhaps you can search it all using one query. Is name authority control for e-resources getting too costly? Let’s see if entity linking techniques can help. These are just a few teasers. <br /> <br /> There’ll be plenty of content and tools supplied, but please bring your own [data] too -- you’ll hack with it in new ways throughout the day. We’ll get started with some lightning talks on what we’ve brought,then we’ll break up into groups to experiment and work on the ideas that appeal. Three guaranteed outcomes: you’ll walk away with new ideas, new tools, and new people you’ll have met.<br /> <br /> ''Interested in attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Devon Smith<br /> # Kevin S. Clarke<br /> <br /> === GeoHydra: Managing geospatial content ===<br /> <br /> '''Half-day [Afternoon]'''<br /> <br /> * Contact: Darren Hardy, Stanford University, drh@stanford.edu<br /> * Moderator: Bess Sadler, Stanford University, bess@stanford.edu<br /> <br /> Do you have digitized maps, GIS datasets like Shapefiles, aerial photography,<br /> etc., all of which you want to integrate into your digital repository? In this<br /> workshop, we will discuss how Hydra can provide discovery, delivery, and<br /> management services for geospatial assets, as well as solicit questions about<br /> your own GIS projects. We aim to help answer the following questions you might have about putting geospatial data into your Hydra-based digital library:<br /> <br /> * What are the types of geospatial data?<br /> * How to dive into Hydra?<br /> * How to model geospatial holdings with Hydra?<br /> * How to discover and view geospatial data?<br /> * How to build a geospatial data infrastructure?<br /> * What are common approaches and problems?<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Esmé Cowles<br /> <br /> ===Technology, Librarianship, and Gender: Moving the conversation forward===<br /> '''Full Day'''<br /> <br /> Contact: Lisa Rabey lisa @ biblyotheke dot net | [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]<br /> <br /> '''Description'''<br /> <br /> Librarianship is largely made up of women, yet women are significantly underrepresented in tech positions, on any level, within libraries themselves. Why? What are we doing to encourage women to become more involved in STEM within librarianship? What kind of message are we sending when library technology keynotes remain almost resolutely male? How are we changing the face of technology, not only within libraries, but with the field itself? How are we training our staff and colleagues in the areas of fairness and removal of bias? Our vendors?<br /> <br /> Lots of tough questions.<br /> <br /> While the conversation has been going on via various blogs and articles within the last few years, it was given a public face at [http://infotoday.com/il2013/day.asp?day=Monday#session_D105 Internet Librarian 2013] where a panel of 7 (four women, three men) gave personal experiences on the above and then opened up the conversation to the audience. As eye opening and enriching the conversation was, a 45 minute panel was not enough. One thing remains clear: We need to keep the conversation moving forward and start making some radical changes in the way we think, act, and how we need to harness this to start making real changes within librarianship itself.<br /> <br /> Topics to include: Fairness, bias, impostor syndrome, code of conducts, sexual harassment, training opportunities, support systems, mentoring, ally support, and more<br /> <br /> Those attending should expect: Begin with opening up the conversation of experiences and talking about what is most needed, spending remaining time putting together live, usable solutions to start implementing as well as pushing the conversation forward at local levels<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> =====All Day=====<br /> 1. Kate Kosturski<br /> <br /> 2. Valerie Aurora<br /> <br /> 3. Declan Fleming<br /> <br /> =====Morning=====<br /> 1. Shaun Ellis<br /> <br /> 2. Jason Casden<br /> <br /> =====Afternoon=====<br /> 1. Ayla Stein<br /> <br /> 2. Heidi Dowding<br /> <br /> 3. Coral Sheldon-Hess<br /> ----<br /> <br /> ===FileAnalyzer: Rapid Development of File Manipulation Tasks===<br /> '''&quot;Half-Day&quot; [morning]'''<br /> * Contact Terry Brady, twb27@georgetown.edu<br /> <br /> The FileAnalyzer (https://github.com/Georgetown-University-Libraries/File-Analyzer) is an application designed to solve a number of library automation challenges:<br /> <br /> * validating digitized and reformatted files<br /> * validating vendor statistics for counter compliance<br /> * preparing collections of digital files for archiving and ingest<br /> * manipulating ILS import and export files<br /> <br /> The File Analyzer application was used by the US National Archives to validate 3.5 million digitized images from the 1940 Census. After implementing a customized ingest workflow within the File Analyzer, the Georgetown University Libraries was able to process an ingest backlog of over a thousand files of digital resources into DigitalGeorgetown, the Libraries’ Digital Collections and Institutional Repository platform. Georgetown is currently developing customized workflows that integrate Apache Tika, BagIt, and Marc conversion utilities.<br /> <br /> The File Analyzer is a desktop application with a powerful framework for implementing customized file validation and transformation rules. As new rules are deployed, they are presented to users within a user interface that is easy (and powerful) to use.<br /> <br /> The first half of this session will be targeted to potential users and developers. The second half of the session will be targeted towards developers who are interested in developing custom rules for the application.<br /> <br /> ''Session Overview''<br /> * Overview of the application<br /> * Running sample file tests/transformations through the application<br /> * Compiling and building the application<br /> * Coding a custom file processing task<br /> <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> ----<br /> <br /> <br /> ===Collecting social media data with Social Feed Manager===<br /> '''Half-Day [Morning]'''<br /> <br /> Contacts: <br /> * Dan Chudnov, GW Libraries, dchud (at) gwu.edu<br /> * Dan Kerchner, GW Libraries, kerchner (at) gwu.edu<br /> * Laura Wrubel, GW Libraries, lwrubel (at) gwu.edu<br /> <br /> Social media data is a popular material for research and a new format for building collections. What does it take to collect meaningfully from Twitter, Tumblr, YouTube, Weibo, Facebook, and other sites? We will:<br /> * Introduce options for collections, including both high- and low-end commercial offerings. Discuss what it means to collect these resources, covering boundaries, policies, and workflows required to develop a social media collection program in your institution.<br /> * Explore the Twitter API in depth, with hands-on opportunities for those w/laptops and others who want to team up w/them<br /> * Help you get started using the free [http://gwu-libraries.github.io/social-feed-manager Social Feed Manager] (SFM) app we're developing at GW to create your first collections. We’ll demo its use and demo a clean install (those w/environments can follow along)<br /> <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Declan Fleming<br /> # Esmé Cowles<br /> ----<br /> <br /> === Intro to Git ===<br /> '''&quot;Half-Day [tbd - probably afternoon]&quot;''' <br /> * Contact: Erin Fahy, Stanford University, efahy at stanford.edu<br /> * TA: Michael Klein, Northwestern University, michael.klein at northwestern.edu<br /> <br /> This session will cover the fundamentals of git by discussing/going through (time allowing):<br /> * what is a distributed version control system<br /> * what is git and github<br /> * initializing a repo on a remote server/github<br /> * cloning an existing repo<br /> * creating a branch<br /> * contributing code to a repo<br /> * how to handle merge conflicts<br /> <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> ----<br /> <br /> === Archival discovery and use ===<br /> '''Full Day''' <br /> <br /> Contacts: <br /> * Tim Shearer, UNC Chapel Hill, tshearer at email.unc.edu, <br /> * Will Sexton, Duke, will.sexton at duke.edu<br /> <br /> This is a full day pre-conference about archival collections and will cover the intersections of archives, workflows, technologies, discovery, and use.<br /> <br /> Morning agenda: focused talks around (but not limited to) issues such as:<br /> * Crowd-sourcing description to enhance collecitons<br /> * Linked data and authority<br /> * Mass digitization and sustainable workflows<br /> * Digitized objects in context (images and other objects in finding aids)<br /> * Too many cooks in the kitchen: versioning<br /> * Global-, intra-, and inter- discovery of archival materials via finding aids <br /> * and more...<br /> <br /> Afternoon agenda: Focused talks around specific tools followed by general discussion, connections, opportunities, aspirations, and planning.<br /> <br /> Tool examples:<br /> * Archivespace<br /> * STEADy<br /> * &quot;RAMP&quot; (Remixing Archival Metadata Project)<br /> * OpenRefine<br /> * Aeon<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> Morning:<br /> * your name<br /> <br /> Afternoon:<br /> * your name<br /> <br /> All day:<br /> * your name<br /> <br /> ----<br /> <br /> ===AV Content Slam===<br /> '''Half-Day [morning]'''<br /> Contacts:<br /> * Kara Van Malssen, kara (at) avpreserve.com<br /> * Lauren Sorenson, laurens (at) bavc.org<br /> * Steven Villereal , villereal (at) gmail.com<br /> A morning BarCamp/unconference for practitioners and coders who work with audiovisual content. The agenda will be attendee-driven, with a focus on sharing, synthesizing, and improving workflow strategies and documentation for software-based approaches to wrangling and providing access to audio and video content.<br /> Possible topics of discussion might include:<br /> * Use of format id and characterization/metadata extraction tools for AV<br /> * Creating and using time-based metadata<br /> * Managing (moving, fixity checking, etc) massive files (like uncompressed video)<br /> For a better idea of the topics and concerns that have informed some past AV-themed events, check out the event wikis for [http://wiki.curatecamp.org/index.php/CURATEcamp_AVpres_2013 CURATEcamp AVpres 2013] as well as the [http://wiki.curatecamp.org/index.php/Association_of_Moving_Image_Archivists_%26_Digital_Library_Federation_Hack_Day_2013 AMIA/DLF 2013 Hack Day] .<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:<br /> <br /> ----<br /> <br /> ===OCLC Web Services Hackfest===<br /> <br /> &quot;Half-Day&quot; [afternoon]<br /> <br /> Contact: Shelley Hostetler, Community Manager, Developer Network hostetls[at]oclc.org<br /> <br /> This half-day hackfest will explore some of the OCLC Developer Network web services. We will provide an overview of some of the common topics such as the general REST-based architecture for most services and how to use some new authentication clients. The group can then decide to take a deep dive into a particular API and/or write a client library for the community.<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:<br /> <br /> <br /> ----<br /> <br /> <br /> ===Obey the Testing Goat!: Test Driven Web Development From The Ground Up===<br /> '''Half-Day [tbd - probably afternoon]'''<br /> * Contact [[User:Mredar|Mark Redar]], mredar[at]gmail.com<br /> <br /> Test driven development is a proven method for producing better quality code. But I've found it hard to follow a strict TDD methodology when starting new web projects. How do you write that first test when there is no code or web pages created yet.<br /> <br /> In this session, we will follow the excellent book [http://shop.oreilly.com/product/0636920029533.do &quot;Test-Driven Web Development with Python&quot;] to create a simple web site in Django following TDD from the first character typed. Come ready to code and test. No prior knowledge of python or Django required.<br /> <br /> By the end of this session, you should be able to [http://www.obeythetestinggoat.com/ &quot;Obey the Testing Goat&quot;] from the start to finish for your next project.<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:<br /> <br /> * Charlie Morris (NCSU)<br /> <br /> ===Summon Camp===<br /> Placeholder by Tim McGeary for Gillian Cain (Serials Solutions)<br /> Description to be provided by Gillian after account issues resolved. <br /> <br /> ----<br /> <br /> [[:Category:Code4Lib2014]]</div>

Cdmo https://wiki.code4lib.org/index.php?title=Resources_to_help_you_learn_drupal&diff=39290 2013-06-14T14:00:17Z

<p>Cdmo: added a slew of lnks</p> <hr /> <div>This page was created during a 2012 code4lib pre-conference. It is intended to be a list of helpful resources for any beginner. As such, things will change, so please update and add to this list as you see fit.<br /> <br /> === Resources, Places ===<br /> <br /> *google it!<br /> *Drupal.org starter packets:<br /> **[https://drupal.org/documentation/understand Understanding Drupal]<br /> **[https://drupal.org/documentation/build Site Building]<br /> **[https://drupal.org/documentation/theme Theming]<br /> **[https://drupal.org/documentation/develop Develop for Drupal]<br /> **[https://drupal.org/documentation More packets of documentation]<br /> *groups at drupal.org (like [http://groups.drupal.org/libraries library drupal group])<br /> *going to events: drupalcamp, code4lib, local meetups<br /> *[http://www.amazon.com/Pro-Drupal-Development-John-VanDyk/dp/1590597559 drupal pro development book]<br /> *[http://drupal4lib.org/ drupal4lib email list]<br /> *reading the code and documentation in the code, especially the [https://drupal.org/project/examples Examples] module<br /> *[http://drupal.stackexchange.com/ drupal.stackexchange] (other stackoverflow)<br /> *drupal.org<br /> *issue queues for modules<br /> *lynda.com, buildamodule.com, drupalize.me<br /> *[http://archive.org/search.php?query=drupalcon%20AND%20mediatype%3Amovies Internet Archive] has every drupalcon<br /> *YouTube videos<br /> *Vimeo videos<br /> *[http://drupal.org/planet Drupal Planet] <br /> *meetup.com<br /> *trial and error/trial by fire/experiments<br /> *asking and answering questions on [https://drupal.org/irc/channels IRC], [https://drupal.org drupal.org], [http://drupal.stackexchange.com/ stackexchange], at camps, etc<br /> *[http://drupalwatchdog.com/ Drupal Watchdog] articles<br /> <br /> === Tutorials ===<br /> <br /> *[http://drupal.org/node/803746 Building a Drupal Site in Git]<br /> *[http://drupal.org/node/244924 Securing file permissions and ownership]<br /> <br /> <br /> ===Other notes?===<br /> Add your comments too!</div>

Cdmo https://wiki.code4lib.org/index.php?title=Resources_to_help_you_learn_drupal&diff=39289 2013-06-14T13:52:26Z

<p>Cdmo: /* Resources, Places */</p> <hr /> <div>This page was created during a 2012 code4lib pre-conference. It is intended to be a list of helpful resources for any beginner. As such, things will change, so please update and add to this list as you see fit.<br /> <br /> === Resources, Places ===<br /> <br /> *groups at drupal.org (like [http://groups.drupal.org/libraries library drupal group])<br /> *going to events: drupalcamp, code4lib, local meetups<br /> *[http://www.amazon.com/Pro-Drupal-Development-John-VanDyk/dp/1590597559 drupal pro development book]<br /> *[http://drupal4lib.org/ drupal4lib email list]<br /> *reading the code and documentation in the code<br /> *google<br /> *[http://drupal.stackexchange.com/ drupal.stackexchange] (other stackoverflow)<br /> *drupal.org<br /> *issue queues for modules<br /> *irc<br /> *lynda.com, buildamodule.com, drupalize.me<br /> *Internet Archive has every drupalcon<br /> *YouTube videos<br /> *Vimeo videos<br /> *Drupal Planet (drupal.org/planet)<br /> *meetup.com<br /> *trial and error/trial by fire/experiments<br /> *answering questions on IRC, drupal.org, [http://drupal.stackexchange.com/ stackexchange], at camps, etc<br /> <br /> === Tutorials ===<br /> <br /> *[http://drupal.org/node/803746 Building a Drupal Site in Git]<br /> *[http://drupal.org/node/244924 Securing file permissions and ownership]<br /> <br /> === Creating Videos ===<br /> *jing<br /> *screencast.com<br /> <br /> ===Other notes?===<br /> Add your comments too!</div>

Cdmo https://wiki.code4lib.org/index.php?title=Resources_to_help_you_learn_drupal&diff=39288 2013-06-14T13:51:15Z

<p>Cdmo: </p> <hr /> <div>This page was created during a 2012 code4lib pre-conference. It is intended to be a list of helpful resources for any beginner. As such, things will change, so please update and add to this list as you see fit.<br /> <br /> === Resources, Places ===<br /> <br /> *groups at drupal.org (like [http://groups.drupal.org/libraries library drupal group])<br /> *going to events: drupalcamp, code4lib, local meetups<br /> *[http://www.amazon.com/Pro-Drupal-Development-John-VanDyk/dp/1590597559 drupal pro development book]<br /> *[http://drupal4lib.org/ drupal4lib email list]<br /> *reading the code and documentation in the code<br /> *google<br /> *[http://drupal.stackexchange.com/ drupal.stackexchange] (other stackoverflow)<br /> *drupal.org<br /> *issue queues for modules<br /> *irc<br /> *lynda.com, buildamodule.com, drupalize.me<br /> *Internet Archive has every drupalcon<br /> *YouTube videos<br /> *Vimeo videos<br /> *Drupal Planet (drupal.org/planet)<br /> *meetup.com<br /> *Google Hangouts<br /> *trial and error/trial by fire/experiments<br /> *answering questions on IRC, drupal.org, stackexchange, at camps, etc<br /> <br /> === Tutorials ===<br /> <br /> *[http://drupal.org/node/803746 Building a Drupal Site in Git]<br /> *[http://drupal.org/node/244924 Securing file permissions and ownership]<br /> <br /> === Creating Videos ===<br /> *jing<br /> *screencast.com<br /> <br /> ===Other notes?===<br /> Add your comments too!</div>

Cdmo https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39260 2013-06-03T19:57:51Z

<p>Cdmo: /* T-Shirt Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> * Jason Casden<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference.<br /> <br /> * Kevin S. Clarke<br /> <br /> == Pre-conference Committee ==<br /> <br /> 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.<br /> <br /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <br /> This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting both pre-conferences and regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.<br /> <br /> == Scholarships Committee ==<br /> <br /> 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.<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> - Francis Kayiwa<br /> <br /> == T-Shirt Committee ==<br /> <br /> 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.<br /> <br /> *Charlie Morris (NCSU)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Cdmo https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39259 2013-06-03T19:57:30Z

<p>Cdmo: /* T-Shirt Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> * Jason Casden<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference.<br /> <br /> * Kevin S. Clarke<br /> <br /> == Pre-conference Committee ==<br /> <br /> 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.<br /> <br /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <br /> This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting both pre-conferences and regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.<br /> <br /> == Scholarships Committee ==<br /> <br /> 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.<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> - Francis Kayiwa<br /> <br /> == T-Shirt Committee ==<br /> <br /> 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.<br /> <br /> Charlie Morris (NCSU)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Cdmo https://wiki.code4lib.org/index.php?title=Resources_to_help_you_learn_drupal&diff=36486 2013-02-12T16:06:47Z

<p>Cdmo: </p> <hr /> <div>=== Resources, Places ===<br /> <br /> *groups at drupal.org (like [http://groups.drupal.org/libraries library drupal group])<br /> *going to events: drupalcamp, code4lib, local meetups<br /> *[http://www.amazon.com/Pro-Drupal-Development-John-VanDyk/dp/1590597559 drupal pro development book]<br /> *[http://drupal4lib.org/ drupal4lib email list]<br /> *reading the code and documentation in the code<br /> *google<br /> *[http://drupal.stackexchange.com/ drupal.stackexchange] (other stackoverflow)<br /> *drupal.org<br /> *issue queues for modules<br /> *irc<br /> *lynda.com, buildamodule.com, drupalize.me<br /> *Internet Archive has every drupalcon<br /> *YouTube videos<br /> *Vimeo videos<br /> *Drupal Planet (drupal.org/planet)<br /> *meetup.com<br /> *Google Hangouts<br /> *trial and error/trial by fire/experiments<br /> *answering questions on IRC, drupal.org, stackexchange, at camps, etc<br /> <br /> === Tutorials ===<br /> <br /> *[http://drupal.org/node/803746 Building a Drupal Site in Git]<br /> *[http://drupal.org/node/244924 Securing file permissions and ownership]<br /> <br /> === Creating Videos ===<br /> *jing<br /> *screencast.com<br /> <br /> ===Other notes?===<br /> Add your comments too!</div>

Cdmo