https://wiki.code4lib.org/api.php?action=feedcontributions&user=Lq1356716&feedformat=atomCode4Lib - User contributions [en]2024-03-29T01:17:38ZUser contributionsMediaWiki 1.26.2https://wiki.code4lib.org/index.php?title=2013_committees_sign-up_page&diff=297852013 committees sign-up page2012-12-24T01:25:37Z<p>Lq1356716: </p>
<hr />
<div>= Code4Lib 2013 Committees =<br />
<br />
If you are interested in helping out with a particular part of the Code4Lib 2013 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 />
[http://www.relojesreplicas7.net/ replicas relojes]<br />
<br />
'''[[2013 During the Conference Volunteers | During the Conference Volunteers]]''' - If you're going to be at the conference, sign up to help out!<br />
<br />
== Book Give-Away Committee ==<br />
*Anjanette Young<br />
<br />
== Sponsorships Committee ==<br />
<br />
This committee organizes the sponsorship activities. Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br />
<br />
* Margaret Heller mheller@dom.edu<br />
* [[User:DataGazetteer|Peter Murray]], peter.murray@lyrasis.org<br />
* Kyle Banerjee banerjek@uoregon.edu<br />
* Bohyun Kim kimb et fiu dot edu<br />
* [http://roytennant.com/ Roy Tennant], roytennant@gmail.com<br />
* [http://twitter.com/TheRealArty Cynthia Ng], cynthia.s.ng at gmail<br />
* [[User:highermath|Cary Gordon]], cgordon@chillco.com<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) and work with the speakers to arrange their travel and arrangements.<br />
<br />
*Francis Kayiwa kayiwa@ YOU EYE SEE DOT edu<br />
*Anjanette Young<br />
*Kevin Reiss kr2 @ princeton . edu<br />
*Jim Rible rible@sou.edu<br />
<br />
== Program Committee ==<br />
<br />
This committee plans the structure of the program, arranges the voting on presentations, etc. These folks will also announce speakers, etc.<br />
* [[User:DataGazetteer|Peter Murray]], peter.murray@lyrasis.org<br />
* [http://twitter.com/ranti Ranti Junus], ranti.junus@gmail.com<br />
* Ray Schwartz, schwartzr2@wpunj.edu<br />
* [http://twitter.com/TheRealArty Cynthia Ng], cynthia.s.ng at gmail<br />
* Tom Johnson, thomas.johnson@oregonstate.edu<br />
* Tod Olson, tod at uchicago dot edu<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 />
* [http://jodischneider.com/jodi.html Jodi Schneider]<br />
* [http://ecorrado.us/ Edward M. Corrado]<br />
* Santi Thompson, sathompson3@uh.edu<br />
* Christina Salazar (christina.salazar AT csuci DOT edu)<br />
<br />
== T-Shirt Committee ==<br />
<br />
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes.<br />
<br />
* akorphan (akorphan AT ncsu DOT edu)<br />
* [[User:Pberry|Pberry]] Patrick Berry (pberry@csuchico.edu)<br />
* Shaun Ellis (shaune@princeton.edu)<br />
<br />
== Social Activities Committee ==<br />
<br />
The committee plans, proposes, and organizes the evening activities.<br />
<br />
*Francis Kayiwa kayiwa@ YOU EYE SEE DOT edu<br />
*Ray Schwartz, schwartzr2@wpunj.edu<br />
*Bohyun Kim kimb et fiu dot edu<br />
*Shane Beers, sbeers depaul edu<br />
*[[User:JonGorman|Jon Gorman]], jtgorman @ illinois dot edu<br />
*Becky Yoose, b.yoose cinnamon roll gmail speck com<br />
* [http://twitter.com/danwho Dan "lampshade" Suchy], dansuchy at gmail<br />
*Margaret Heller, mheller@dom.edu<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 />
* [http://twitter.com/jlefager Jim LeFager], jameslefager at gmail<br />
<br />
== Whatever Committee ==<br />
<br />
This committee does whatever the organizers can't talk anyone else into doing.<br />
<br />
* [[User:highermath|Cary Gordon]], cgordon@chillco.com<br />
* [http://twitter.com/jlefager Jim LeFager], jameslefager at gmail<br />
* [[User:Wolf29|Wolf Halton]], wolf.halton@lyrasis.org./dev/null<br />
* [[User:crowesn|Sean Crowe]], sean.crowe@ uc dot edu<br />
* [[User:shawnc12|Shawn Carraway]], carraways@ midlandstech dot edu<br />
* [[User:mackeral|Michael Lindsey]], mackeral at gmail<br />
* [[User:Mnorth|Michael North]], m-north AT northwestern DOT edu<br />
* [[User:Tracy.seneca|Tracy Seneca]], tjseneca at uic dot edu<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: Code4Lib2013]]</div>Lq1356716https://wiki.code4lib.org/index.php?title=Useful_information_from_2012&diff=29784Useful information from 20122012-12-24T01:22:18Z<p>Lq1356716: </p>
<hr />
<div>=='''Suggestions for streamlining registration:'''==<br />
<br />
*Have the pre-conference and conference presentations and presenters voted on before the registration opens. <br />
**This will decrease the chaos that results in having presenters joining in the open registration and then having to account for their spots at a later date. <br />
<br />
*Do not open the hotel or the payment links to whomever registers. Open registration and then those who get into the allotted spots would be contacted with the links for payment and hotel reservation.<br />
**This will decrease the need for refunds (which cost time and money).<br />
**This will decrease the chaos of needing to account for people who have hotel rooms who did not get into the conference. <br />
*Guest room counts and other information useful for venue negotiations are at the end of the document<br />
<br />
===How Code4Lib National was handled for 2012.===<br />
'''''These are not recommendations. Registration was a nightmare.'''''<br />
<br />
*Presentations were not chosen before open registration. <br />
**In 2010 there was a demand to have an earlier registration release date to accommodate for bureaucratic slowness at institutions. <br />
**The voting for the presenters went for another 2 weeks beyond the registration opening. This seriously delayed the finalization of the participant list and the release of the wait list. <br />
**Each presenter (or person on the wait list who then could fill the space left vacant) had to be individually contacted to get their payment and connect with the hotel about their lodging.<br />
[http://www.welwatch.com TAG Heuer Replica Watches]<br />
<br />
*We started with 213 spots open for general registration because pre-conference, conference presentations were not chosen yet and we didn’t know who the sponsors would be.<br />
**This was an issue because some pre-conference and conference presentations had more than one presenter and some sponsors get more than one spot, so, again, having presentations chosen before registration would preclude those issues.<br />
<br />
*We opened registration at a certain time and date. The payment and hotel reservation links were open to whomever registered. <br />
**Opening conference registration and hotel registrations at the same time proved difficult for several reasons:<br />
***People who did not get into the conference made hotel reservations. These individuals needed to be individually contacted to cancel their reservations. <br />
***The hotel had difficulty tracking the cancellations, and opening those spots for other participants.<br />
***Based on the information from the 2011 host, the need for hotel rooms was seriously under estimated creating the need for several different blocks of rooms with several rooming contracts with different rates and different deadlines.<br />
***The hotel reservation system was not prepared for the onslaught and we broke their registration system, creating more chaos. <br />
<br />
*Those 213 spots were filled in within the hour. The payment and hotel information was then moved so that no one else could access it. This created issues with registrations bouncing. <br />
<br />
*Around 15 people canceled their registrations 2 weeks before the conference which necessitated individually contacting those on the wait list and arranging for payment.<br />
<br />
*The participants list was not finalized until 7 working days before the conference.<br />
**There continue to be messages on the lists offering spots even up to the Thursday and Friday before the start of the conference. Keeping track of dietary needs and cancellations have taken considerable Administrative time. <br />
<br />
*Original projection of Admin time was grossly under estimated. Based on other conventions of generally the same size and geographically diverse, the Admin time was estimated at 10 working days, not including actual time/overtime at the conference. Actual time was about 29 full working days, again, not including the actual time/overtime at the conference. <br />
<br />
===Statistics to help with 2013 Code4Lib Hosting===<br />
<br />
*Strict 250 participant cap – mandate from the community<br />
*Adequate bandwidth for wireless usage at conference is vital<br />
**Ended up needing wired internet access for streaming – was not part of the original negotiations<br />
**Some questions that we asked the venues:<br />
***Is your venue able to provide at least 8 mb/sec guaranteed service, either through a dedicated connection or a private VLAN?<br />
***Can you provide multi-band access points that support both 24 & 5 Ghz service -- 802.11b, g, n and, ideally, 802.11a?<br />
***Can your system accommodate at least 300 simultaneous connections?<br />
*Make sure there are Vegetarian meals (30 Vegetarians; 4 Vegans; 3 Gluten-free; 12 Food Allergies)<br />
*Anticipated Admin time usage (Not including actual time at conference): 10 working days<br />
*Actual Admin time usage (Not including actual time at conference): 29 working days<br />
<br />
===Guest Room Pick up===<br />
'''''We have use of the same room rate 2 days on both sides of the conference.'''''<br />
<br />
Total room Pick-up: 633<br />
<br />
:Feb 4 - 9 (2 days before conference)<br />
:Feb 5 - 102 (day before pre-conference)<br />
:Feb 6 - 155 (Pre-conference)<br />
:Feb 7 – 156 (Conference)<br />
:Feb 8 – 155 (Conference)<br />
:Feb 9 – 47 (Last ½ day of conference)<br />
:Feb 10 – 7<br />
:Feb 11 – 2<br />
<br />
===T-shirt Amounts and Sizes===<br />
'''''This is to give you an idea of what quantities you are looking for if you decide to do T-shirts again.'''''<br />
<br />
:Did not want a T-shirt - 9<br />
:Small - 32 <br />
:Medium - 82 <br />
:Large - 66 <br />
:X-large - 52 <br />
:2x - 9 <br />
:3X - 3 <br />
:4X - 1<br />
<br />
===Budgetary Considerations===<br />
'''''This is not a comprehensive list'''''<br />
<br />
When budgeting, things to account for are:<br />
*Credit Card Charges (how much it will cost to take credit cards)<br />
*Scholarships<br />
*T-shirts (this are more expensive than originally thought)<br />
*Loss from Cancellations (Credit Card refund costs, lost revenue, other things such as T-shirts and lowering minimum participant counts for hotel contracts)<br />
*Internet usage and Networks<br />
*Video and Streaming<br />
*Key Note Speaker Costs, Complimentary registrations<br />
*Logistics of payments and refunds for out of Country participants<br />
<br />
===Things to think about…===<br />
<br />
*Not having A/V available for the pre-conference did not work well. There were numerous requests for projectors and screens<br />
*Don’t forget the need for extra extension cords and surge protectors. It was much less expensive to purchase the power cords than to pay for the use through the hotel <br />
*The Hospitality suite needs to have room for around 50 people and the ability to bring alcohol<br />
*Think about getting a list of programs and software needed for presenters before the beginning of the conference and setting up an equipment check when the A/V is set up or the night before the beginning of the conference<br />
*The ‘Ask Anything’ sessions needs 3 microphones – 1 for the presenter and 2 for the audience<br />
*There was a request for a Book/Magazine exchange</div>Lq1356716https://wiki.code4lib.org/index.php?title=Emilda&diff=29783Emilda2012-12-24T01:05:43Z<p>Lq1356716: </p>
<hr />
<div>[[Category:OSSDirectory]]<br />
* http://www.emilda.org/<br />
* License: [[GPL]]<br />
<br />
The Emilda project began in 2000 as a simple Perl-based ILS. It then grew into a more full-featured PHP-based ILS which was released under the GPL in March 2003. The last version listed on their website is 1.2.3 which was released in 2005. This version uses [[Zebra]] for [[MARC]] indexing, MySQL for other functions and includes an OPAC, circulation and various administrative functions. Emilda is no longer under active development [http://thread.gmane.org/gmane.education.libraries.emilda.devel/442/focus=443 as discussed on their mailing list]:<br />
<br />
"Emilda is currently undergoing a fairly stagnated phase. The company behind Emilda, Realnode Oy, is realigning its business focus which implies that Emilda no longer fits into the core portfolio of the company."<br />
[http://www.welwatch.net/ replica rolex subamriner watch]<br />
<br />
"Emilda is however currently also being developed in cooperation with other parties, however not under any strict or binding release schedule. This means that every now and then there are new features being added to the SVN-repository, but there are no plans to release any stable releases any time soon. The code on SVN is currently in production use, so it IS stable, but not a release."</div>Lq1356716https://wiki.code4lib.org/index.php?title=Main_Page&diff=29782Main Page2012-12-24T00:58:00Z<p>Lq1356716: </p>
<hr />
<div>{|align=right<br />
|__TOC__<br />
|}<br />
<br />
== About Code4Lib ==<br />
<br />
* [[About Code4Lib]] - Background and history of the community<br />
* [[A Guide for the Perplexed]] - Building skills for working with library technologies<br />
* [[How to hack code4lib]] - For those newer to the community<br />
* [https://docs.google.com/document/d/1m-9VtL7L_fUxl2hTF_YZSdFRfucaLtmHvLSzom6XPVM/edit?pli=1 Code4Lib Indoctrination] (This is a Google doc open to all including anonymous feedback.)<br />
**"How do we make code4lib a more inclusive place for newcomers? <br/> Or, how do we quickly indoctrinate newbies to our values and ways of doing things?" <br />
**Suggestions, ideas, and follow-up actions solicited.<br />
* [[One recommended tool/resource for n00bs]] - For new coding librarians/library Coders<br />
* [[Mentorship Program]]<br />
<br />
==Code4Lib 2013 Conference==<br />
See also the ''[[:Category:Code4Lib2013]] category''<br />
*[[2013_committees_sign-up_page|Volunteer to help plan 2013 conference]]<br />
*[[2013_During_the_Conference_Volunteers|During the conference volunteer signup]]<br />
*[[2013 Invited Speakers Nominations]] -- nominations close Aug. 31, 2012.<br />
*[[2013 talks proposals]] - due Friday, Nov 9<br />
*[[2013 preconference proposals]] - due Friday, Nov 9<br />
*[[2013 t-shirt design proposals]] - due Monday, Dec. 31<br />
<br />
*[[2013_social_activities|Social Activities for 2013 Conference]]<br />
*[[2013_travel|Travel Advice and Getting To and From the 2013 Conference]]<br />
*[[2013_room_ride_share|2013 Conference Room and Ride Share]]<br />
<br />
== Local / Regional Groups ==<br />
<br />
* [[NYC|Code4LibNYC]] - NYC and surrounding areas<br />
* [[NEC4L|New England Code4lib]] - New England<br />
* [[NL|Code4Bib]] - Dutch Code4Bib<br />
* [[MDC|Code4libMDC]] - Maryland, Washington D.C, Virginia, and surrounding areas<br />
* [http://groups.google.com/group/pnwcode4lib?hl=en PNWCode4Lib] - Pacific Northwest<br />
* [[North|code4lib North]] - Ontario and surrounding areas ''(new for Jan 2010!)''<br />
* [[Midwest|Code4Lib Midwest]] - Wherever that is...<br />
* [http://groups.google.com/group/ikr-fejlesztok/ Code4lib.hu] - Group of Hungarian library developers<br />
* [http://www.code4lib.jp/ Code4Lib Japan] - ''(new in 2010!)'', see also [http://twitter.com/yesonline/statuses/28561046501 tweet from Jerry Lee]<br />
* [http://groups.google.com/group/code4glam Code4GLAM Australia] - coders, hackers, developers and technologists in the Australian GLAM (Galleries, Libraries, Archives & Museums) sector.<br />
* [[GreatEastern|Code4Lib Great Eastern]] - Atlantic Provinces<br />
* [[Code4lib_Mid-Atlantic|Code4Lib Mid-Atlantic]] - Philadelphia and the Greater Tri-State Area<br />
<br />
== Interest Groups ==<br />
<br />
* [[ILS_Interop|ILS Interoperability]] - A group working to develop an infrastructure for interoperating between discovery layers and integrated library systems.<br />
* [[Open_Source_Book_Widgets|Open Source Book Widgets]] - A list of open source book widgets<br />
* [[Discovery|Open Source Discovery]] - Open Source application to enhance and support "discovery" in libraries<br />
* [[Mobile_Apps|Mobile Applications]] - A group interested in mobile web and native application development for libraries<br />
* [[Sources_Of_Metadata|Sources Of Metadata]] - list of api's and sources of interest to libraries<br />
<br />
== Software Usage and Documentation ==<br />
<br />
* [[Umlaut]] - OpenURL link resolving middleware<br />
* [[:Category:Patterns|Patterns for Collaborative Code]] - Patterns to make your open source 'more open', more amenable to distributed development and use at multiple institutions without forking. <br />
* [[ILS Documentation]]<br />
* [[OSS Directory]]<br />
* [[Working with MARC]]<br />
* [[Rogue]] - principles for standards creation<br />
<br />
== Code4Lib Journal ==<br />
<br />
* [[:Category:Code4Lib Journal|Code4Lib Journal]] - information and working documents<br />
<br />
== Current topics ==<br />
<br />
* [[Code4Lib Website Update]]<br />
* [[OCLC Policy Change]]<br />
* [[SirsiDynix: Integrated Library System Platforms on Open Source]]<br />
* [[Parsing Library Data]]<br />
* [[Robots Are Our Friends]]<br />
<br />
== Other Code4Lib Sites ==<br />
<br />
* [http://www.code4lib.org/ code4lib.org]<br />
* [http://planet.code4lib.org planet.code4lib.org]<br />
* [http://journal.code4lib.org journal.code4lib.org]<br />
<br />
== Earlier Conferences and events ==<br />
[[Conference Financial History At A Glance]]<br />
<br />
===Code4Lib 2012 Conference===<br />
''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2012 Code4lib2012 category]''<br />
<br />
* [http://code4lib.org/conference/2012/ 2012 home]<br />
* [[During_the_Conference_Volunteers|Volunteer to help at code4lib 2012]]<br />
* [[2012_committees_sign-up_page|Volunteer to help plan 2012 conference]]<br />
* [[2012_preconference_proposals|2012 Preconference Proposals]]--due Sunday, November 20<br />
* [[2012_talks_proposals|2012 Talk Proposals]]--due Sunday, November 20<br />
* [[2012_c4l2012_social_activities|Social Activities]] - ideas and sign-up<br />
* [[c4l2012_rideshare|Rideshare-Roomshare]]<br />
* [[c4l2012_t-shirtcontest|T-shirt contest]]<br />
* [[ideas_for_2012|Put your ideas for 2012 here!]]<br />
* [[C4L2012_Call_For_Host|2012 Call For Host]]<br />
* [[How To Plan A Code4LibCon]]<br />
* [http://linkd.in/unhJsR LinkedIn Event]<br />
* [[2012_twitter_list|List your Twitter handle here]]<br />
* [[2012_Lightning_Talks_Signup|Lightning Talks Signup]]<br />
* [http://irc.code4lib.org/ IRC Channel Timeline & Log]<br />
* [http://www.livestream.com/code4lib Conference Livestream] (non-attendees only, please!)<br />
<br />
=== Code4Lib 2011 Conference ===<br />
''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2011 Code4lib2011 category]''<br />
<br />
* [http://code4lib.org/conference/2011 C4L2011 Home]<br />
* [[C4L2011_registration | Registration Information!]]<br />
* [[2011_committees_sign-up_page | 2011 Committees Sign-Up]] - '''Volunteer to help'''<br />
* [[How To Plan A Code4LibCon]]<br />
* [[C4L2011_social_activities|Social Activities]] - ideas & sign-up<br />
* [[C4L2011_planning_wishlist|'''Put your ideas for 2011 here!''']]<br />
* [http://www.facebook.com/event.php?eid=161853827200024 Facebook Event Page]<br />
* [http://events.linkedin.com/Code4Lib-2011/pub/448897 LinkedIn Event Page]<br />
<!-- commenting out until later * '''[[2011 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff''' --><br />
* [[C4L2011_rideshare|Airport Ride Share and Carpooling]]<br />
* [[C4L2011_roomshare | Hotel room share]]<br />
<br />
=== Code4Lib 2010 Conference ===<br />
<br />
''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2010 Code4lib2010 category]''<br />
* [http://code4lib.org/conference/2010/schedule Finalized schedule]<br />
* [[2010 Lightning Talks Signup]] - sign up to give a lightning talk<br />
* [[2010 Breakout Sessions]] - suggest a breakout here<br />
* '''[[2010 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff'''<br />
* [[C4L2010_social_activities|Social Activities]] - ideas & sign-up<br />
* [[Committees sign-up page]] - '''Volunteer to help'''<br />
* [[C4L2011_planning_wishlist|'''Put your ideas for 2011 here!''']]<br />
* [[Asheville Airport to Hotel Van Manifest]] <br />
* [[C4L2010rideshare|General shared travel/transportation planning]]<br />
* [[C4L2010planning:RoommatesRidesEtc|Roommates, Rides, Etc]]<br />
* [[C4L2010_manning_discount|Manning Publications Discount]] - discount code (40% off) for use by attendees through Feb. 28, 2010<br />
* Thanks also to our other sponsors!<br />
* [[C4L2010planning|2010 Planning]]<br />
* [[C4L2010planning:_wishlist | 2010 Planning Wishlist]] - planning page for issues, expectations, etc. for the 2010 conference<br />
<br />
=== Code4Lib 2009 Conference ===<br />
<br />
* [[BookRaffle]] - coordinate begging publishers for books to raffle off at the conference<br />
* [http://inkdroid.org/c4l2009/attendees Get FOAFed] - add your FOAF profile to the network of c4l2009 attendees<br />
* PreConferences:<br />
** [[GIS_preconf_code4libcon2009]] - Open source GIS just like mom used to make<br />
** [[LinkedData]] - A proposal for a linked-data code4lib2009 pre-conference<br />
** [[LibX_Preconference]] - Proposal for a half-day pre-conference targeted at developers who wish to use the LibX 2.0 platform<br />
** [http://code4lib.org/2009/oclc-precon OCLC Grid Services Preconference]<br />
* [[RoommatesRidesEtc]] - Find roommates for Code4Lib 2009, share rides, etc.<br />
* [[2009 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff<br />
[http://www.piumino138.com woolrich arctic parka]<br />
<br />
=== Other workshops ===<br />
* [http://barcamp.org/SearchCampDC SearchCampDC] - barcamp style event in DC with usual suspects from code4lib<br />
* [[code4lib/elag2010]] - 1-day code4lib preconference at elag2010<br />
<br />
== Archived topics ==<br />
<br />
* [[Logo Design Process]]<br />
<br />
<br />
[[AdminToDo]] - ideas and tasks for maintaining the Code4Lib sites</div>Lq1356716