https://wiki.code4lib.org/api.php?action=feedcontributions&feedformat=atom&user=TimmcgearyCode4Lib - User contributions [en]2026-04-29T06:51:53ZUser contributionsMediaWiki 1.26.2https://wiki.code4lib.org/index.php?title=2014_Lessons_Learned&diff=412032014 Lessons Learned2014-05-13T13:52:10Z<p>Timmcgeary: </p>
<hr />
<div>Code4Lib 2014 Conference Planning -- Lessons Learned (and Ideas)<br />
<br />
'''Venue planning and negotiation'''<br />
* A conference services planning organization, like CONCENTRA, has significant experience in contract details that volunteer planners would unlikely have. <br />
* Venue negotiation takes a significant amount of time. Total of nearly four (5) months of visits, informational calls, and negotiations.<br />
* Hotel block negotiations are valuable, especially in the fine print of cancellation clauses, re-selling of unsold rooms, penalties of underselling, and scheduled kickbacks at certain increments.<br />
* When looking at space capacities, make sure you find out how many attendees can REALLY fit in a given space. The advertised numbers seem to be artificially inflated; ask to see a room layout graphic with A/V in place (we lost 15% of stated capacity at least to A/V).<br />
* Regardless of how strongly we communicate to the venue the pressures we'll be placing on their wifi, they almost always have trouble keeping up with our connection weight (especially hotels).<br />
* Overall, the 2014 group began working on venue negotiation and sponsorships in June 2013 for a conference taking place in March 2014.<br />
<br />
'''Registration'''<br />
* The venue of C4L2014 could hold 350 people<br />
* To ensure registration Presenters, Preconference Organizers, and Sponsors (Platinum, Gold, and Table), initial registration was capped at 325. This filled in approximately 48 hours.<br />
* Demand for Code4Lib 2014 was 450 based on registrations and wait list. <br />
* Local registrations by the hosting libraries (Duke, NCSU, UNC) was 41 registrations.<br />
* CONCENTRA's registration system had some technical limitations as to data input and flow, but CONCENTRA handled all processing with little assistance by volunteers.<br />
* Waitlist was well-handled by a Google Form, as the registration system didn't have built-in waitlist functionality.<br />
<br />
'''Sponsorships'''<br />
* 46.8% of the estimated cost of C4L2014 was provided by sponsorships. The registration cost of $165 per person covered another 46.8%. The remaining balance of C4L2013 covered the remaining 6-7%. <br />
* To keep registration costs low, it is critical the Sponsorship Committee raise a minimum of $50,000 per year. [This really depends on the overall venue costs. If the conference is hosted on a college campus, the costs tend to be much lower, and therefore the amount of sponsorship needed is much lower - jaf]<br />
* The [http://code4lib.org/node/487|Code4Lib2014 Sponsorship Prospectus] was a '''significant''' tool in raising money this year.<br />
<br />
'''T-shirts'''<br />
* Getting sizing that works for everyone is hard.<br />
** Nevertheless, there is value in providing as diverse a selection of sizes and cuts as is practicable.<br />
* There may be some design fatigue in the community.<br />
* Consider some other type of swag that doesn't involve sizing difficulties -- like re-usable coffee mugs (then attendees could use them all conference!)<br />
* When putting out a call for any graphics, ensure that the formats submitted are usable in production (e.g. vector formats).<br />
<br />
'''Food and Beverage'''<br />
* Coffee in unlimited quantities is valued more highly than food at breaks.<br />
* Using negotiation to buy "off menu" will save money.<br />
* Make sure that you ask about dietary requirements during registration so that you can accommodate vegan / vegetarian / gluten-free, etc.<br />
* Less than 65% of the attendees ate breakfast at the conference. Each day of the conference, the number of attendees at breakfast declined.<br />
* 97% of the attendees ate lunch at the conference. The number of attendees at lunch was consistent for both days.<br />
* Less than 100 cans of soda were taken during the afternoon break of the first day; 50 cans of soda were taken during the afternoon break of the second day.<br />
<br />
'''Pre-Conferences'''<br />
* Consider a winnowing process for pre-conferences to limit them in advance of registration to the number of rooms that you have. Could either do advance voting like with talks, or say that you have x number of rooms and take the top x pre-conferences, etc. We set a 5-person registration minimum for A/V support this year, and found that all the pre-conferences met that limit (all 19 of them!) so it was not particularly useful. (Adam Constabaris [first dot last, lowercased at gmail] from the 2014 committee has a working database schema and a vague idea about incorporating voting on preconferences into the Diebold-o-Tron)<br />
<br />
* Ask ahead of time to find out if pre-conf organizers are planning to open their pre-confs to non-conference attendees.<br />
* Some preconferences work a lot better with special seating arrangements, enrollment caps, etc. Some support for allowing preconf presenters to request/implement such arrangements would be worth considering.<br />
* Pre-conference organizers will likely want to know before registration opens whether or not their pre-conference is actually going to happen (relevant if there are two many proposed for the space to support).<br />
<br />
* Communicate early and often with organizers and have a plan for '''getting a solid schedule''' as early as possible (this can help some organizers provide the needed justification to their institutions for travel support). Consider this in light of your winnowing process.<br />
* (Also applies to the A/V section) find out as much as possible about the rooms at the venue, including the layout and suitability to different session styles, and wifi, power availability, etc. up front.<br />
<br />
'''A/V'''<br />
* When talking to sales folks, get the REAL numbers on how many attendees will fit in a space (this means WITH A/V included, which could be 15% less or more than advertised capacities).<br />
* Provide A/V info to speakers in advance (availability of computer, network availability, any additional software installs needed, etc.).<br />
<br />
'''Internet'''<br />
* Require in the contract that hotel or conference facility have a minimum of one (1) wireless access point per 75 attendees. <br />
* Require in the contract that hotel or conference facility plan to support 2 wireless connections per attendee<br />
* Require in the contract that hotel or conference facility have a minimum of 100 Mb per second bandwidth. Encourage hotel or conference facility to increase capacity to 1 Gb per second during conference. (Expect to pay more for this.)<br />
<br />
'''Organizing Volunteers'''<br />
* It's helpful to have a local representative on all volunteer committees to help grease the wheels.<br />
* A Google Calendar worked well this year in establishing all deadlines across all committees.<br />
* A regularly occurring meeting of some planning group helps keep things moving.<br />
* See [http://wiki.code4lib.org/index.php/Code4Lib_2014_Conference_Planning_Volunteers|documentation and timelines] for 2014 volunteer committees.<br />
<br />
'''IRC'''<br />
*Pay attention to the IPs you are assigned, make sure they are not PRIVATE (eg. 10,172.4-31,192.168) <br />
*Start the process to get the freenode limit raised a month before to plan for any kinks!<br />
*Announce channel logging a month or more ahead of time<br />
* One benefit of not have great wireless was that people couldn't be distracted by IRC and were much more focused on the talks. Perhaps we need to re-consider the value of the IRC during the conference and encourage Twitter use instead.<br />
<br />
'''Scholarships'''<br />
* Ask folks to follow a file naming convention for any files they send. Using their full name in the filename. <br />
* Make a note about how the committee ought to be addressed. Someone had a question about this and didn’t want to lose out because they weren’t formal enough. We can specify who the letter ought to be addressed to even if the packet is being sent to one person on the committee.<br />
* If we have many scholarships, consider opening up the categories to a consideration just of financial need or others. This might encourage other sponsors to give. (Institutional diversity for scholarships. Regional scholarships. Rural librarian.)<br />
* Ask that the statement of eligibility be in the first paragraph of the letter to make it easier to organize applications.<br />
* Keep a list of everyone who has won a scholarship in the past.<br />
* For the committee deliberations create a list of what factors to consider in selection. (e.g. How likely to be active in the community if awarded?) May allow some community supported guidelines to be put forward. <br />
* In the initial notification letter of selection, let the person know they will also be asked to write a short bio. These can then be used by sponsors to promote the scholarship sponsorship.<br />
* We got the suggestion to have badge ribbons for scholarship winners.<br />
* The lunch the first day was a success. Make sure someone is responsible for checking the day of that tables will be reserved for this purpose. <br />
* Promote the sponsors and the scholarship winners more via social media during the conference.<br />
* Automatically invite keynote speakers to the scholarship lunch.<br />
<br />
'''Keynotes'''<br />
* It's useful to ask nominees about their availability and willingness to attend before voting so that the community is only voting on real candidates (as opposed to wishful thinking).<br />
<br />
'''Ideas'''<br />
* Lanyards for whether it is OK to take photographs<br />
* Add chairs to the front of the room so that lightning talk presenters can sit before they talk<br />
** This needs to be planned in advance. C4L2014 was at capacity for the room, so this was not possible.<br />
* Do not place a conference goer near the hospitality suite! Maybe make the hang out place a different area in the hotel or conference.<br />
** Another possibility could be to have the room next to the hospitality room be reserved for a "suite steward" or "host" volunteer - aka a person that can look after the room in terms of cleanliness, drink/food stock, etc. <br />
* Make the podium laptop desktop background a plain color with good contrast. After every group of presenters clean off the desktop to keep it quicker and easier for presenters to find their slides.<br />
* Put someone at the front of the room who is responsible for helping presenters with the presenter computer. <br />
* Podium Computer<br />
** Most people use Mac laptops, so if there is only one podium computer, it should be a Mac. (TMM disagrees)<br />
** Ideally, both a Mac and a Windows computer should be available. (TMM disagrees, see sub-bullet below)<br />
*** Almost all of the presentations this year used standard formats (PPT, PDF, and HTML). The podium computer needs to be under the control of the A/V and Streaming Committees for their functions. Presenters should use a presentation standard.<br />
** Several presenters had trouble with not being able to see what was being presented -- the podium computer(s) should be mirrored by default.<br />
*** No, the podium computer should be setup as required for streaming and A/V setup. (TMM)<br />
* Consider pre-combining lightning talks into a single slide deck to keep the flow going.<br />
** This is difficult when lightning talk presenters want to do a live demo (TMM)<br />
* Consider live closed captioning software for talks and streaming<br />
* Twitter feed of #c4lYY on screens when no presenter is up (TMM edited IRC to Twitter because Twitter feed is safer, more professional, and more compliant to code of conduct)<br />
** Twitter is no more CoC compliant than other online venues, including IRC. Each feed has its own risks in being viewed on the big screen (IRC in jokes vs Twitter hijacking of hashtags). (yo_bj)<br />
* Consider switches at the tables<br />
** what kind of switches?<br />
* Add a Code4Lib logo to the podium<br />
* Have someone whose job it is to collect questions during a presentation and that can then ask them. Allowing for anonymous questions may lead to more folks asking.</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=2014_Lessons_Learned&diff=410512014 Lessons Learned2014-03-31T14:40:28Z<p>Timmcgeary: </p>
<hr />
<div>Code4Lib 2014 Conference Planning -- Lessons Learned (and Ideas)<br />
<br />
'''Venue planning and negotiation'''<br />
* A conference services planning organization, like CONCENTRA, has significant experience in contract details that volunteer planners would unlikely have. <br />
* Venue negotiation takes a significant amount of time. Total of nearly four (5) months of visits, informational calls, and negotiations.<br />
* Hotel block negotiations are valuable, especially in the fine print of cancellation clauses, re-selling of unsold rooms, penalties of underselling, and scheduled kickbacks at certain increments.<br />
* When looking at space capacities, make sure you find out how many attendees can REALLY fit in a given space. The advertised numbers seem to be artificially inflated; ask to see a room layout graphic with A/V in place (we lost 15% of stated capacity at least to A/V).<br />
* Regardless of how strongly we communicate to the venue the pressures we'll be placing on their wifi, they almost always have trouble keeping up with our connection weight (especially hotels).<br />
* Overall, the 2014 group began working on venue negotiation and sponsorships in June 2013 for a conference taking place in March 2014.<br />
<br />
'''Registration'''<br />
* The venue of C4L2014 could hold 350 people<br />
* To ensure registration Presenters, Preconference Organizers, and Sponsors (Platinum, Gold, and Table), initial registration was capped at 325. This filled in approximately 48 hours.<br />
* Demand for Code4Lib 2014 was 450 based on registrations and wait list. <br />
* Local registrations by the hosting libraries (Duke, NCSU, UNC) was 41 registrations.<br />
* CONCENTRA's registration system had some technical limitations as to data input and flow, but CONCENTRA handled all processing with little assistance by volunteers.<br />
* Waitlist was well-handled by a Google Form, as the registration system didn't have built-in waitlist functionality.<br />
<br />
'''Sponsorships'''<br />
* 46.8% of the estimated cost of C4L2014 was provided by sponsorships. The registration cost of $165 per person covered another 46.8%. The remaining balance of C4L2013 covered the remaining 6-7%. <br />
* To keep registration costs low, it is critical the Sponsorship Committee raise a minimum of $50,000 per year.<br />
* The [http://code4lib.org/node/487|Code4Lib2014 Sponsorship Prospectus] was a '''significant''' tool in raising money this year.<br />
<br />
'''T-shirts'''<br />
* Getting sizing that works for everyone is hard.<br />
** Nevertheless, there is value in providing as diverse a selection of sizes and cuts as is practicable.<br />
* There may be some design fatigue in the community.<br />
* Consider some other type of swag that doesn't involve sizing difficulties -- like re-usable coffee mugs (then attendees could use them all conference!)<br />
* When putting out a call for any graphics, ensure that the formats submitted are usable in production (e.g. vector formats).<br />
<br />
'''Food and Beverage'''<br />
* Coffee in unlimited quantities is valued more highly than food at breaks.<br />
* Using negotiation to buy "off menu" will save money.<br />
* Make sure that you ask about dietary requirements during registration so that you can accommodate vegan / vegetarian / gluten-free, etc.<br />
<br />
'''Pre-Conferences'''<br />
* Consider a winnowing process for pre-conferences to limit them in advance of registration to the number of rooms that you have. Could either do advance voting like with talks, or say that you have x number of rooms and take the top x pre-conferences, etc. We set a 5-person registration minimum for A/V support this year, and found that all the pre-conferences met that limit (all 19 of them!) so it was not particularly useful. (Adam Constabaris [first dot last, lowercased at gmail] from the 2014 committee has a working database schema and a vague idea about incorporating voting on preconferences into the Diebold-o-Tron)<br />
<br />
* Ask ahead of time to find out if pre-conf organizers are planning to open their pre-confs to non-conference attendees.<br />
* Some preconferences work a lot better with special seating arrangements, enrollment caps, etc. Some support for allowing preconf presenters to request/implement such arrangements would be worth considering.<br />
* Pre-conference organizers will likely want to know before registration opens whether or not their pre-conference is actually going to happen (relevant if there are two many proposed for the space to support).<br />
<br />
* Communicate early and often with organizers and have a plan for '''getting a solid schedule''' as early as possible (this can help some organizers provide the needed justification to their institutions for travel support). Consider this in light of your winnowing process.<br />
* (Also applies to the A/V section) find out as much as possible about the rooms at the venue, including the layout and suitability to different session styles, and wifi, power availability, etc. up front.<br />
<br />
'''A/V'''<br />
* When talking to sales folks, get the REAL numbers on how many attendees will fit in a space (this means WITH A/V included, which could be 15% less or more than advertised capacities).<br />
* Provide A/V info to speakers in advance (availability of computer, network availability, any additional software installs needed, etc.).<br />
<br />
'''Internet'''<br />
* Require in the contract that hotel or conference facility have a minimum of one (1) wireless access point per 75 attendees. <br />
* Require in the contract that hotel or conference facility plan to support 2 wireless connections per attendee<br />
* Require in the contract that hotel or conference facility have a minimum of 100 Mb per second bandwidth. Encourage hotel or conference facility to increase capacity to 1 Gb per second during conference. (Expect to pay more for this.)<br />
<br />
'''Organizing Volunteers'''<br />
* It's helpful to have a local representative on all volunteer committees to help grease the wheels.<br />
* A Google Calendar worked well this year in establishing all deadlines across all committees.<br />
* A regularly occurring meeting of some planning group helps keep things moving.<br />
* See [http://wiki.code4lib.org/index.php/Code4Lib_2014_Conference_Planning_Volunteers|documentation and timelines] for 2014 volunteer committees.<br />
<br />
'''IRC'''<br />
*Pay attention to the IPs you are assigned, make sure they are not PRIVATE (eg. 10,172.4-31,192.168) <br />
*Start the process to get the freenode limit raised a month before to plan for any kinks!<br />
*Announce channel logging a month or more ahead of time<br />
* One benefit of not have great wireless was that people couldn't be distracted by IRC and were much more focused on the talks. Perhaps we need to re-consider the value of the IRC during the conference and encourage Twitter use instead.<br />
<br />
'''Scholarships'''<br />
* Ask folks to follow a file naming convention for any files they send. Using their full name in the filename. <br />
* Make a note about how the committee ought to be addressed. Someone had a question about this and didn’t want to lose out because they weren’t formal enough. We can specify who the letter ought to be addressed to even if the packet is being sent to one person on the committee.<br />
* If we have many scholarships, consider opening up the categories to a consideration just of financial need or others. This might encourage other sponsors to give. (Institutional diversity for scholarships. Regional scholarships. Rural librarian.)<br />
* Ask that the statement of eligibility be in the first paragraph of the letter to make it easier to organize applications.<br />
* Keep a list of everyone who has won a scholarship in the past.<br />
* For the committee deliberations create a list of what factors to consider in selection. (e.g. How likely to be active in the community if awarded?) May allow some community supported guidelines to be put forward. <br />
* In the initial notification letter of selection, let the person know they will also be asked to write a short bio. These can then be used by sponsors to promote the scholarship sponsorship.<br />
* We got the suggestion to have badge ribbons for scholarship winners.<br />
* The lunch the first day was a success. Make sure someone is responsible for checking the day of that tables will be reserved for this purpose. <br />
* Promote the sponsors and the scholarship winners more via social media during the conference.<br />
* Automatically invite keynote speakers to the scholarship lunch.<br />
<br />
'''Keynotes'''<br />
* It's useful to ask nominees about their availability and willingness to attend before voting so that the community is only voting on real candidates (as opposed to wishful thinking).<br />
<br />
'''Ideas'''<br />
* Lanyards for whether it is OK to take photographs<br />
* Add chairs to the front of the room so that lightning talk presenters can sit before they talk<br />
** This needs to be planned in advance. C4L2014 was at capacity for the room, so this was not possible.<br />
* Do not place a conference goer near the hospitality suite! Maybe make the hang out place a different area in the hotel or conference.<br />
** Another possibility could be to have the room next to the hospitality room be reserved for a "suite steward" or "host" volunteer - aka a person that can look after the room in terms of cleanliness, drink/food stock, etc. <br />
* Make the podium laptop desktop background a plain color with good contrast. After every group of presenters clean off the desktop to keep it quicker and easier for presenters to find their slides.<br />
* Put someone at the front of the room who is responsible for helping presenters with the presenter computer. <br />
* Podium Computer<br />
** Most people use Mac laptops, so if there is only one podium computer, it should be a Mac. (TMM disagrees)<br />
** Ideally, both a Mac and a Windows computer should be available. (TMM disagrees, see sub-bullet below)<br />
*** Almost all of the presentations this year used standard formats (PPT, PDF, and HTML). The podium computer needs to be under the control of the A/V and Streaming Committees for their functions. Presenters should use a presentation standard.<br />
** Several presenters had trouble with not being able to see what was being presented -- the podium computer(s) should be mirrored by default.<br />
*** No, the podium computer should be setup as required for streaming and A/V setup. (TMM)<br />
* Consider pre-combining lightning talks into a single slide deck to keep the flow going.<br />
** This is difficult when lightning talk presenters want to do a live demo (TMM)<br />
* Consider live closed captioning software for talks and streaming<br />
* Twitter feed of #c4lYY on screens when no presenter is up (TMM edited IRC to Twitter because Twitter feed is safer, more professional, and more compliant to code of conduct)<br />
* Consider switches at the tables<br />
** what kind of switches?<br />
* Add a Code4Lib logo to the podium<br />
* Have someone whose job it is to collect questions during a presentation and that can then ask them. Allowing for anonymous questions may lead to more folks asking.</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=2014_Lessons_Learned&diff=410502014 Lessons Learned2014-03-31T14:35:58Z<p>Timmcgeary: </p>
<hr />
<div>Code4Lib 2014 Conference Planning -- Lessons Learned (and Ideas)<br />
<br />
'''Venue planning and negotiation'''<br />
* A conference services planning organization, like CONCENTRA, has significant experience in contract details that volunteer planners would unlikely have. <br />
* Venue negotiation takes a significant amount of time. Total of nearly four (5) months of visits, informational calls, and negotiations.<br />
* Hotel block negotiations are valuable, especially in the fine print of cancellation clauses, re-selling of unsold rooms, penalties of underselling, and scheduled kickbacks at certain increments.<br />
* When looking at space capacities, make sure you find out how many attendees can REALLY fit in a given space. The advertised numbers seem to be artificially inflated; ask to see a room layout graphic with A/V in place (we lost 15% of stated capacity at least to A/V).<br />
* Regardless of how strongly we communicate to the venue the pressures we'll be placing on their wifi, they almost always have trouble keeping up with our connection weight (especially hotels).<br />
* Overall, the 2014 group began working on venue negotiation and sponsorships in June 2013 for a conference taking place in March 2014.<br />
<br />
'''Registration'''<br />
* The venue of C4L2014 could hold 350 people<br />
* To ensure registration Presenters, Preconference Organizers, and Sponsors (Platinum, Gold, and Table), initial registration was capped at 325. This filled in approximately 48 hours.<br />
* Demand for Code4Lib 2014 was 420 based on registrations and wait list. <br />
* Local registrations by the hosting libraries (Duke, NCSU, UNC) was 41 registrations.<br />
* CONCENTRA's registration system had some technical limitations as to data input and flow, but CONCENTRA handled all processing with little assistance by volunteers.<br />
* Waitlist was well-handled by a Google Form, as the registration system didn't have built-in waitlist functionality.<br />
<br />
'''Sponsorships'''<br />
* 46.8% of the estimated cost of C4L2014 was provided by sponsorships. The registration cost of $165 per person covered another 46.8%. The remaining balance of C4L2013 covered the remaining 6-7%. <br />
* To keep registration costs low, it is critical the Sponsorship Committee raise a minimum of $50,000 per year.<br />
* The [http://code4lib.org/node/487|Code4Lib2014 Sponsorship Prospectus] was a '''significant''' tool in raising money this year.<br />
<br />
'''T-shirts'''<br />
* Getting sizing that works for everyone is hard.<br />
** Nevertheless, there is value in providing as diverse a selection of sizes and cuts as is practicable.<br />
* There may be some design fatigue in the community.<br />
* Consider some other type of swag that doesn't involve sizing difficulties -- like re-usable coffee mugs (then attendees could use them all conference!)<br />
* When putting out a call for any graphics, ensure that the formats submitted are usable in production (e.g. vector formats).<br />
<br />
'''Food and Beverage'''<br />
* Coffee in unlimited quantities is valued more highly than food at breaks.<br />
* Using negotiation to buy "off menu" will save money.<br />
* Make sure that you ask about dietary requirements during registration so that you can accommodate vegan / vegetarian / gluten-free, etc.<br />
<br />
'''Pre-Conferences'''<br />
* Consider a winnowing process for pre-conferences to limit them in advance of registration to the number of rooms that you have. Could either do advance voting like with talks, or say that you have x number of rooms and take the top x pre-conferences, etc. We set a 5-person registration minimum for A/V support this year, and found that all the pre-conferences met that limit (all 19 of them!) so it was not particularly useful. (Adam Constabaris [first dot last, lowercased at gmail] from the 2014 committee has a working database schema and a vague idea about incorporating voting on preconferences into the Diebold-o-Tron)<br />
<br />
* Ask ahead of time to find out if pre-conf organizers are planning to open their pre-confs to non-conference attendees.<br />
* Some preconferences work a lot better with special seating arrangements, enrollment caps, etc. Some support for allowing preconf presenters to request/implement such arrangements would be worth considering.<br />
* Pre-conference organizers will likely want to know before registration opens whether or not their pre-conference is actually going to happen (relevant if there are two many proposed for the space to support).<br />
<br />
* Communicate early and often with organizers and have a plan for '''getting a solid schedule''' as early as possible (this can help some organizers provide the needed justification to their institutions for travel support). Consider this in light of your winnowing process.<br />
* (Also applies to the A/V section) find out as much as possible about the rooms at the venue, including the layout and suitability to different session styles, and wifi, power availability, etc. up front.<br />
<br />
'''A/V'''<br />
* When talking to sales folks, get the REAL numbers on how many attendees will fit in a space (this means WITH A/V included, which could be 15% less or more than advertised capacities).<br />
* Provide A/V info to speakers in advance (availability of computer, network availability, any additional software installs needed, etc.).<br />
<br />
'''Internet'''<br />
* Require in the contract that hotel or conference facility have a minimum of one (1) wireless access point per 75 attendees. <br />
* Require in the contract that hotel or conference facility plan to support 2 wireless connections per attendee<br />
* Require in the contract that hotel or conference facility have a minimum of 100 Mb per second bandwidth. Encourage hotel or conference facility to increase capacity to 1 Gb per second during conference. (Expect to pay more for this.)<br />
<br />
'''Organizing Volunteers'''<br />
* It's helpful to have a local representative on all volunteer committees to help grease the wheels.<br />
* A Google Calendar worked well this year in establishing all deadlines across all committees.<br />
* A regularly occurring meeting of some planning group helps keep things moving.<br />
* See [http://wiki.code4lib.org/index.php/Code4Lib_2014_Conference_Planning_Volunteers|documentation and timelines] for 2014 volunteer committees.<br />
<br />
'''IRC'''<br />
*Pay attention to the IPs you are assigned, make sure they are not PRIVATE (eg. 10,172.4-31,192.168) <br />
*Start the process to get the freenode limit raised a month before to plan for any kinks!<br />
*Announce channel logging a month or more ahead of time<br />
* One benefit of not have great wireless was that people couldn't be distracted by IRC and were much more focused on the talks. Perhaps we need to re-consider the value of the IRC during the conference and encourage Twitter use instead.<br />
<br />
'''Scholarships'''<br />
* Ask folks to follow a file naming convention for any files they send. Using their full name in the filename. <br />
* Make a note about how the committee ought to be addressed. Someone had a question about this and didn’t want to lose out because they weren’t formal enough. We can specify who the letter ought to be addressed to even if the packet is being sent to one person on the committee.<br />
* If we have many scholarships, consider opening up the categories to a consideration just of financial need or others. This might encourage other sponsors to give. (Institutional diversity for scholarships. Regional scholarships. Rural librarian.)<br />
* Ask that the statement of eligibility be in the first paragraph of the letter to make it easier to organize applications.<br />
* Keep a list of everyone who has won a scholarship in the past.<br />
* For the committee deliberations create a list of what factors to consider in selection. (e.g. How likely to be active in the community if awarded?) May allow some community supported guidelines to be put forward. <br />
* In the initial notification letter of selection, let the person know they will also be asked to write a short bio. These can then be used by sponsors to promote the scholarship sponsorship.<br />
* We got the suggestion to have badge ribbons for scholarship winners.<br />
* The lunch the first day was a success. Make sure someone is responsible for checking the day of that tables will be reserved for this purpose. <br />
* Promote the sponsors and the scholarship winners more via social media during the conference.<br />
* Automatically invite keynote speakers to the scholarship lunch.<br />
<br />
'''Keynotes'''<br />
* It's useful to ask nominees about their availability and willingness to attend before voting so that the community is only voting on real candidates (as opposed to wishful thinking).<br />
<br />
'''Ideas'''<br />
* Lanyards for whether it is OK to take photographs<br />
* Add chairs to the front of the room so that lightning talk presenters can sit before they talk<br />
** This needs to be planned in advance. C4L2014 was at capacity for the room, so this was not possible.<br />
* Do not place a conference goer near the hospitality suite! Maybe make the hang out place a different area in the hotel or conference.<br />
** Another possibility could be to have the room next to the hospitality room be reserved for a "suite steward" or "host" volunteer - aka a person that can look after the room in terms of cleanliness, drink/food stock, etc. <br />
* Make the podium laptop desktop background a plain color with good contrast. After every group of presenters clean off the desktop to keep it quicker and easier for presenters to find their slides.<br />
* Put someone at the front of the room who is responsible for helping presenters with the presenter computer. <br />
* Most people use Mac laptops, so if there is only one podium computer, it should be a Mac.<br />
** Ideally, both a Mac and a Windows computer should be available.<br />
*** Almost all of the presentations this year used standard formats (PPT, PDF, and HTML). The podium computer needs to be under the control of the A/V and Streaming Committees for their functions. Presenters should use a presentation standard.<br />
** Several presenters had trouble with not being able to see what was being presented -- the podium computer(s) should be mirrored by default.<br />
*** No, the podium computer should be setup as required for streaming and A/V setup.<br />
* Consider pre-combining lightning talks into a single slide deck to keep the flow going.<br />
** This is difficult when lightning talk presenters want to do a live demo<br />
* Consider live closed captioning software for talks and streaming<br />
* Twitter feed of #c4lYY on screens when no presenter is up (was previously IRC, but twitter feed is safer, more professional, and more compliant to code of conduct<br />
* Consider switches at the tables<br />
** what kind of switches?<br />
* Add a Code4Lib logo to the podium<br />
* Have someone whose job it is to collect questions during a presentation and that can then ask them. Allowing for anonymous questions may lead to more folks asking.</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=2014_preconference_proposals&diff=403912014 preconference proposals2014-02-13T18:52:12Z<p>Timmcgeary: /* Summon Hackfest and ProQuest Discovery & Management Technologies Users Group */</p>
<hr />
<div>= PROPOSALS ARE CLOSED : PLEASE DO NOT ADD NEW PRECONFERENCES TO THIS PAGE =<br />
<br />
Proposals were accepted through December 6th, 2013.<br />
<br />
It would be really, super duper helpful if folks who think they might want to attend a pre-conference could indicate interest by adding your name to a session below. <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 "sticker shock." Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.<br />
<br />
Please put your pre-conference on the list in the following format:<br />
<br />
=Code4Lib 2014 Pre-Conference Proposals=<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 />
* Paula Gray-Overtoom<br />
* Laurie Lee Moses<br />
<br />
=====Afternoon=====<br />
<br />
&nbsp;<br />
<br />
----<br />
<br />
===Open Refine Hackfest===<br />
'''"Half-Day"'''<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 />
<ol><br />
<li>Adam Constabaris<br />
<li>Ray Schwartz<br />
<li>Jason Stirnaman<br />
<li>Joshua Gomez<br />
<li>Sam Kome<br />
<li>Mike Beccaria<br />
<li>Angela Zoss<br />
<li>A. Soroka<br />
<li> Matt Zumwalt<br />
</ol><br />
----<br />
<br />
===Responsive Design Hackfest===<br />
'''"Half-Day [Afternoon]"''' <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 />
<br />
=== Intro to Blacklight ===<br />
'''"Half-Day [Morning]"''' <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 />
# Cory Lown<br />
# Emily Daly<br />
# Angela Zoss<br />
# Sean Aery<br />
# Francis Kayiwa<br />
# Heidi Frank<br />
# Junior Tidal<br />
# Ian Chan<br />
----<br />
<br />
===Blacklight Hackfest===<br />
'''"Half-Day [Afternoon]"''' <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 />
# Shaun Ellis<br />
# Kevin Reiss<br />
# Megan Kudzia<br />
# Erik Hatcher<br />
# Emily Daly<br />
# Laurie Lee Moses<br />
# Francis Kayiwa<br />
<br />
----<br />
<br />
===RailsBridge: Intro to programming in Ruby on Rails===<br />
'''"Half-Day" [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 />
3. Caitlin Christian-Lamb<br />
<br />
4. Scott Bacon<br />
<br />
5. [[User:RileyChilds | Riley Childs]]<br />
<br />
6. Carolina Garcia<br />
<br />
----<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 />
# Robin Dean<br />
# Erin White<br />
# Andrew Darby<br />
# Sam Kome<br />
# Ryan Scherle<br />
# Will Shaw<br />
# Liz Milewicz<br />
# Cynthia "Arty" Ng<br />
# Laurie Lee Moses (if I don't do the Hackfest for Blacklight)<br />
# Ranti Junus<br />
# Bohyun Kim (Afternoon)<br />
<br />
----<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 />
#Mike Graves<br />
#Ray Schwartz<br />
#Jason Stirnaman<br />
#Julia Bauder<br />
#Linda Ballinger<br />
#Scott Hanrath<br />
#Caitlin Christian-Lamb<br />
#Ian Walls<br />
#Scott Bacon <br />
#mx matienzo<br />
#Chris Sharp<br />
#Junior Tidal<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 />
# Jason Stirnaman<br />
# Joshua Gomez<br />
# Carolina Garcia<br />
# Tom Burton-West<br />
# Dan Scott<br />
# Devin Higgins<br />
# Mark Breedlove<br />
----<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 />
<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 (I'd be good with a half day too)<br />
<br />
4. mx matienzo (likewise ok w/ half day)<br />
<br />
5. Ginny Boyer (I'd be good with a half day too)<br />
<br />
=====Morning=====<br />
1. Shaun Ellis<br />
<br />
2. Jason Casden<br />
<br />
3. Bohyun Kim<br />
<br />
=====Afternoon=====<br />
1. Ayla Stein<br />
<br />
2. Heidi Dowding<br />
<br />
3. Coral Sheldon-Hess<br />
<br />
4. Cory Lown<br />
----<br />
<br />
===FileAnalyzer: Rapid Development of File Manipulation Tasks===<br />
'''"Half-Day" [morning]'''<br />
* Contact Terry Brady, twb27@georgetown.edu<br />
<br />
The FileAnalyzer (http://georgetown-university-libraries.github.io/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 />
#Ray Schwartz<br />
# Michael Doran<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 />
# Jason Stirnaman<br />
# Ray Schwartz<br />
# Liz Milewicz<br />
# Ranti Junus<br />
<br />
----<br />
<br />
=== Intro to Git ===<br />
'''"Half-Day [tbd - probably afternoon]"''' <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 />
# Ray Schwartz<br />
# Sam Kome<br />
# Paula Gray-Overtoom<br />
# Liz Milewicz<br />
# Michael Doran<br />
# Caitlin Christian-Lamb<br />
# [[User:RileyChilds|Riley Childs]]<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 />
* "RAMP" (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 />
* Julia Bauder<br />
<br />
Afternoon:<br />
* your name<br />
<br />
All day:<br />
<br />
# Josh Wilson<br />
# Sam Kome<br />
# Linda Ballinger<br />
# Caitlin Christian-Lamb<br />
# Laurie Lee Moses (seriously hard to decide here!)<br />
# David Bass<br />
# John Rees<br />
# Lynn Eaton<br />
# Hillel Arnold<br />
# Susan Ivey<br />
# Kristen Merryman<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 />
# A. Soroka<br />
<br />
----<br />
<br />
===OCLC Web Services Hackfest===<br />
<br />
"Half-Day" [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 "Test-Driven Web Development with Python"] to create a simple web site in Django following TDD from the first character typed. Come ready to code and test. No prior knowledge of python or Django required.<br />
<br />
By the end of this session, you should be able to [http://www.obeythetestinggoat.com/ "Obey the Testing Goat"] from the start to finish for your next project.<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 />
# Jason Stirnaman<br />
# Joshua Gomez<br />
# Liz Milewicz<br />
# Scott Hanrath<br />
# Mike Beccaria<br />
# Sean Aery<br />
# Carolina Garcia<br />
# Heidi Frank<br />
----<br />
<br />
===Summon Hackfest ===<br />
<br />
Presenter: Eddie Newwirth and presenters from Summon libraries<br />
Contact: Scott Schuetze (first DOT last @ serialssolutions. com)<br />
<br />
The Summon Hackfest (10:30am-12pm) will be a great opportunity for libraries using the Summon service to talk about improving discovery of resources, share their creative customizations and code, and exchange ideas about ways they can leverage the Summon API to better meet the needs of their users.<br />
<br />
The Summon Hackfest is open to all libraries currently using ProQuest discovery and management services (Intota, Summon, Ulrich’s or the 360 suite of services), whether they are attending Code4Lib or are just in the area.<br />
<br />
----<br />
<br />
[[:Category:Code4Lib2014]]</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=2014_Lessons_Learned&diff=402822014 Lessons Learned2014-01-30T15:51:54Z<p>Timmcgeary: </p>
<hr />
<div>Code4Lib 2014 Conference Planning -- Lessons Learned<br />
<br />
'''Venue planning and negotiation'''<br />
* A conference services planning organization, like CONCENTRA, has significant experience in contract details that volunteer planners would unlikely have. <br />
* Venue negotiation takes a significant amount of time. Total of nearly four (5) months of visits, informational calls, and negotiations.<br />
* Hotel block negotiations are valuable, especially in the fine print of cancellation clauses, re-selling of unsold rooms, penalties of underselling, and scheduled kickbacks at certain increments.<br />
<br />
'''Registration'''<br />
* The venue of C4L2014 could hold 350 people<br />
* To ensure registration Presenters, Preconference Organizers, and Sponsors (Platinum, Gold, and Table), initial registration was capped at 325. This filled in approximately 48 hours.<br />
* Demand for Code4Lib 2014 was 420 based on registrations and wait list. <br />
* Local registrations by the hosting libraries (Duke, NCSU, UNC) was 41 registrations.<br />
* CONCENTRA's registration system had some technical limitations as to data input and flow, but CONCENTRA handled all processing with little assistance by volunteers.<br />
<br />
'''Sponsorships'''<br />
* 46.8% of the estimated cost of C4L2014 was provided by sponsorships. The registration cost of $165 per person covered another 46.8%. The remaining balance of C4L2013 covered the remaining 6-7%. <br />
* To keep registration costs low, it is critical the Sponsorship Committee raise a minimum of $50,000 per year.<br />
* The Code4Lib2014 Sponsorship Prospectus was a '''significant''' tool in raising money this year.<br />
<br />
'''T-shirts'''<br />
* Getting sizing that works for everyone is hard.<br />
* There may be some design fatigue in the community.<br />
* Consider some other type of swag that doesn't involve sizing difficulties -- like re-usable coffee mugs (then attendees could use them all conference!)<br />
<br />
'''Food and Beverage'''<br />
* Coffee in unlimited quantities is valued more highly than food at breaks.<br />
* Using negotiation to buy "off menu" will save money.<br />
<br />
'''Pre-Conferences'''<br />
* Consider a winnowing process for pre-conferences to limit them in advance of registration to the number of rooms that you have. Could either do advance voting like with talks, or say that you have x number of rooms and take the top x pre-conferences, etc. We set a 5-person registration minimum for A/V support this year, and found that all the pre-conferences met that limit (all 19 of them!) so it was not particularly useful.<br />
* Ask ahead of time to find out if pre-conf organizers are planning to open their pre-confs to non-conference attendees.<br />
<br />
'''A/V'''<br />
* When talking to sales folks, get the REAL numbers on how many attendees will fit in a space (this means WITH A/V included, which could be 15% less or more than advertised capacities).<br />
<br />
'''Organizing Volunteers'''<br />
* It's helpful to have a local representative on all volunteer committees to help grease the wheels.</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=2014_Lessons_Learned&diff=402812014 Lessons Learned2014-01-30T15:40:22Z<p>Timmcgeary: </p>
<hr />
<div>Code4Lib 2014 Conference Planning -- Lessons Learned<br />
<br />
'''Venue planning and negotiation'''<br />
* A conference services planning organization, like CONCENTRA, has significant experience in contract details that volunteer planners would unlikely have. <br />
* Venue negotiation takes a significant amount of time. Total of nearly four (5) months of visits, informational calls, and negotiations.<br />
* <br />
<br />
'''Sponsorships'''<br />
* 46.8% of the estimated cost of C4L2014 was provided by sponsorships. The registration cost of $165 per person covered another 46.8%. The remaining balance of C4L2013 covered the remaining 6-7%. <br />
* To keep registration costs low, it is critical the Sponsorship Committee raise a minimum of $50,000 per year.<br />
* The Code4Lib2014 Sponsorship Prospectus was a '''significant''' tool in raising money this year.<br />
<br />
'''T-shirts'''<br />
* Getting sizing that works for everyone is hard.<br />
* There may be some design fatigue in the community.<br />
* Consider some other type of swag that doesn't involve sizing difficulties -- like re-usable coffee mugs (then attendees could use them all conference!)<br />
<br />
'''Food and Beverage'''<br />
* Coffee in unlimited quantities is valued more highly than food at breaks.<br />
<br />
'''Pre-Conferences'''<br />
* Consider a winnowing process for pre-conferences to limit them in advance of registration to the number of rooms that you have. Could either do advance voting like with talks, or say that you have x number of rooms and take the top x pre-conferences, etc. We set a 5-person registration minimum for A/V support this year, and found that all the pre-conferences met that limit (all 19 of them!) so it was not particularly useful.<br />
* Ask ahead of time to find out if pre-conf organizers are planning to open their pre-confs to non-conference attendees.<br />
<br />
'''A/V'''<br />
* When talking to sales folks, get the REAL numbers on how many attendees will fit in a space (this means WITH A/V included, which could be 15% less or more than advertised capacities).<br />
<br />
'''Organizing Volunteers'''<br />
* It's helpful to have a local representative on all volunteer committees to help grease the wheels.</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=2014_Lessons_Learned&diff=402802014 Lessons Learned2014-01-30T15:39:51Z<p>Timmcgeary: </p>
<hr />
<div>Code4Lib 2014 Conference Planning -- Lessons Learned<br />
<br />
"Venue planning and negotiation"<br />
* A conference services planning organization, like CONCENTRA, has significant experience in contract details that volunteer planners would unlikely have. <br />
* Venue negotiation takes a significant amount of time. Total of nearly four (5) months of visits, informational calls, and negotiations.<br />
* <br />
<br />
"Sponsorships"<br />
* 46.8% of the estimated cost of C4L2014 was provided by sponsorships. The registration cost of $165 per person covered another 46.8%. The remaining balance of C4L2013 covered the remaining 6-7%. <br />
* To keep registration costs low, it is critical the Sponsorship Committee raise a minimum of $50,000 per year.<br />
* The Code4Lib2014 Sponsorship Prospectus was a '''significant''' tool in raising money this year.<br />
<br />
'''T-shirts'''<br />
* Getting sizing that works for everyone is hard.<br />
* There may be some design fatigue in the community.<br />
* Consider some other type of swag that doesn't involve sizing difficulties -- like re-usable coffee mugs (then attendees could use them all conference!)<br />
<br />
'''Food and Beverage'''<br />
* Coffee in unlimited quantities is valued more highly than food at breaks.<br />
<br />
'''Pre-Conferences'''<br />
* Consider a winnowing process for pre-conferences to limit them in advance of registration to the number of rooms that you have. Could either do advance voting like with talks, or say that you have x number of rooms and take the top x pre-conferences, etc. We set a 5-person registration minimum for A/V support this year, and found that all the pre-conferences met that limit (all 19 of them!) so it was not particularly useful.<br />
* Ask ahead of time to find out if pre-conf organizers are planning to open their pre-confs to non-conference attendees.<br />
<br />
'''A/V'''<br />
* When talking to sales folks, get the REAL numbers on how many attendees will fit in a space (this means WITH A/V included, which could be 15% less or more than advertised capacities).<br />
<br />
'''Organizing Volunteers'''<br />
* It's helpful to have a local representative on all volunteer committees to help grease the wheels.</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=Sponsor_Logos_for_T-Shirt&diff=40221Sponsor Logos for T-Shirt2014-01-07T21:43:46Z<p>Timmcgeary: </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>Timmcgearyhttps://wiki.code4lib.org/index.php?title=Sponsor_Logos_for_T-Shirt&diff=40220Sponsor Logos for T-Shirt2014-01-07T21:43:28Z<p>Timmcgeary: </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<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>Timmcgearyhttps://wiki.code4lib.org/index.php?title=Sponsor_Logos_for_T-Shirt&diff=40213Sponsor Logos for T-Shirt2014-01-06T18:38:08Z<p>Timmcgeary: </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<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>Timmcgearyhttps://wiki.code4lib.org/index.php?title=2014_preconference_proposals&diff=400732014 preconference proposals2013-12-07T05:24:16Z<p>Timmcgeary: </p>
<hr />
<div>==Code4Lib 2014 Pre-Conference Proposals==<br />
<br />
Proposals will be accepted through December 6th, 2013.<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 "sticker shock." Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.<br />
<br />
Please put your pre-conference on the list in the following format:<br />
<br />
===NAME===<br />
'''"Full-Day|Half-Day" [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 />
===Open Refine Hackfest===<br />
'''"Half-Day"'''<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 />
'''"Half-Day [Afternoon]"''' <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 />
'''"Half-Day [Morning]"''' <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 />
'''"Half-Day [Afternoon]"''' <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 />
'''"Half-Day" [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 />
===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 />
'''"Half-Day" [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 />
<br />
----<br />
<br />
<br />
=== Intro to Git ===<br />
'''"Half-Day [tbd - probably afternoon]"''' <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 />
* "RAMP" (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 />
"Half-Day" [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 "Test-Driven Web Development with Python"] to create a simple web site in Django following TDD from the first character typed. Come ready to code and test. No prior knowledge of python or Django required.<br />
<br />
By the end of this session, you should be able to [http://www.obeythetestinggoat.com/ "Obey the Testing Goat"] from the start to finish for your next project.<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:<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>Timmcgearyhttps://wiki.code4lib.org/index.php?title=2014_Invited_Speakers_Nominations&diff=394662014 Invited Speakers Nominations2013-08-20T15:37:09Z<p>Timmcgeary: /* David Silver */</p>
<hr />
<div>Nominations for invited speakers/keynotes for Code4Lib 2014. Please include a description and any relevant links and try to keep the list in alphabetical order. Suggestions will close on August 30, 2013 at midnight (EDT), which will be followed by a community vote. We will contact nominees before the vote to confirm their interest. <br />
<br />
<br />
==Sarah Allen==<br />
<br />
"Sarah Allen is a serial innovator with a history of developing leading-edge products, such as After Effects, Shockwave, Flash video, and OpenLaszlo. She has a habit of recognizing great and timely ideas, finding talented teams, and creating compelling software. She has led small and large teams and confidently turns vision into reality.<br />
<br />
...<br />
<br />
Sarah leads an innovative product strategy, design & development company, Blazing Cloud, and in her spare time works to diversify the Ruby on Rails with RailsBridge, which she co-founded in 2009. In keeping with her belief that programming is a life skill, she also regularly volunteers teaching programming to kids. Sarah believes that open source software provides solid technical foundations and compelling business models. She is an expert with Ruby and Rails and was a member of the OpenLaszlo core team, where she coded in asynchronous Javascript before it was cool."<br />
<br />
http://www.ultrasaurus.com/about/<br />
<br />
==John Allspaw==<br />
John Allspaw (https://twitter.com/allspaw) is the Senior Vice President for Technical Operations at Etsy (http://etsy.com). Prior to that he built infrastructure for Salon, InfoWorld, Flickr, and others. His publications include "Web Operations" and "The Art of Capacity Planning". You can find his blog at http://www.kitchensoap.com/. <br />
<br />
As library development teams grow from single programmers writing "glue" scripts to small teams working together on mid size web apps and further to large development shops producing complex and large scale systems, they find themselves struggling with issues of scale. These issues of scale are not just with the systems being built, but with the operations of the team itself. Operations can often be overlooked during the daily routine of project meetings, writing code, fixing bugs, etc. John's insights on operations and capacity planning would be useful to the library development community, particularly for those in departments that are maturing from one or two programmers to mid-size or larger development teams.<br />
<br />
==Cory Doctorow==<br />
BoingBoing.com, craphound.com. Author of sci-fi, copyright activist, etc. http://en.wikipedia.org/wiki/Cory_Doctorow<br />
<br />
==Jeri Ellsworth==<br />
<br />
Jerrielsworth.com, Jeri Ellsworth is an American entrepreneur and self-taught computer chip designer. She is best known for creating a Commodore 64 emulator within a joystick, in 2004, called C64 Direct-to-TV <br />
http://en.wikipedia.org/wiki/Jeri_Ellsworth<br />
<br />
==Sarah Lacy==<br />
<br />
Founder of PandoDaily, tech journalist and author. I (Roy) saw her speak and she was awesome. http://en.wikipedia.org/wiki/Sarah_Lacy<br />
<br />
== Jukka Pennanen & Mace Ojala ==<br />
<br />
Jukka Pennanen & Mace Ojala are the primary organizers of the Cycling For Libraries Unconference ( http://www.cyclingforlibraries.org/ )<br />
<br />
"Founded in 2011, the Cycling for libraries is an international cycling conference for librarians and library lovers. It aims to advocate libraries and increase awareness of the valuable services and resources that libraries offer to the community."<br />
<br />
I was lucky enough to participate in this event last summer and I think it was an incredible experience. I think Jukka and Mace have a great perspective in how to organize a wide encompassing international library community. <br />
<br />
== Daniel Reetz ==<br />
<br />
Daniel Reetz is the mastermind behind http://www.diybookscanner.org/ . It is an incredible community building open source software and hardware for book scanning using affordable consumer equipment. The project has evolved incredibly over the last few years and now include beautifully hackerspace-made scanner kits. He seems like a great speaker and I believe his perspective would be different from the traditional academic/research library focus. <br />
<br />
== Kathy Sierra ==<br />
<br />
Kathy Sierra has been interested in the brain and artificial intelligence since her days as a game developer (Virgin, Amblin', MGM). She is the co-creator of the bestselling Head First series (finalist for a Jolt Software Development award in 2003, and named to the Amazon Top Ten Editors Choice Computer Books for 2003 and 2004). She is also the founder of one of the largest community web sites in the world, javaranch.com. Kathy's passions are skiing, running, her Icelandic horse, gravity, and her latest favorite thing--Dance Dance Revolution.<br />
<br />
http://headrush.typepad.com/about.html<br />
<br />
== David Silver ==<br />
<br />
David Silver is an associate professor of media studies and environmental studies at the University of San Francisco where he teaches classes on media history, digital media production, and green media. David co-directs USF's Garden Project, a freshmen-to-senior living learning community built around an organic garden on campus. He blogs at http://silverinsf.blogspot.com/. He was the keynote at the TRLN Annual Meeting and talked about the importance of the Library as a keystone to his teaching of media studies, the Library as a keystone of collective curiosity and community action, and why we should enable students to contribute back to the Library. Some quotes I tweeted from his talk:<br />
<br />
* "Too often library instruction starts at library databases. Librarians, this has to stop." <br />
* "I want my seniors to contribute to the library, to give something back."<br />
* "Whenever there is community curiosity and collective action, that's where the library should be." <br />
<br />
I believe his keynote would be motivational in reflecting how what we do in Code4Lib is critical to Libraries support his mission as a professor and researcher, his students, and the community at large. Expect humor, humility, and creativity from David Silver.<br />
<br />
==Victoria Stodden==<br />
<br />
She is a co-founder of http://www.RunMyCode.org, an open platform for disseminating the code and data associated with published results, and enabling independent and public cloud-based verification of methods and findings, and an assistant professor of Statistics at Columbia University, and affiliated with the Columbia University Institute for Data Sciences and Engineering. She just recently gave a great keynote at Open Repositories. http://www.stanford.edu/~vcs/Bio.html<br />
<br />
==Andromeda Yelton==<br />
<br />
Formerly a developer with Unglue.it, she recently left full-time work there to work to help people learn to code. I (Roy) would love to hear her talk about how to help people break into coding. http://andromedayelton.com/about/<br />
<br />
==Gene Kim==<br />
<br />
Gene’s area of passion is helping companies build super-tribes where Development, IT Operations, Product and Project Management and Information Security simultaneously maximize throughput of features from “code complete” to “in production,” without causing chaos and disruption to the IT environment. He’s helped some of the largest Internet properties, such as Microsoft, Yahoo!, AOL and Microsoft companies he’s worked with Microsoft. He loves finding and fixing bottlenecks which impede and frustrate the entire organization, enabling management from each tribe to achieve the greater organizational goals.<br />
http://www.realgenekim.me/speaking/<br />
<br />
[[Category:Code4Lib2014]]</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=2014_Invited_Speakers_Nominations&diff=394652014 Invited Speakers Nominations2013-08-20T15:35:57Z<p>Timmcgeary: /* Andromeda Yelton */</p>
<hr />
<div>Nominations for invited speakers/keynotes for Code4Lib 2014. Please include a description and any relevant links and try to keep the list in alphabetical order. Suggestions will close on August 30, 2013 at midnight (EDT), which will be followed by a community vote. We will contact nominees before the vote to confirm their interest. <br />
<br />
<br />
==Sarah Allen==<br />
<br />
"Sarah Allen is a serial innovator with a history of developing leading-edge products, such as After Effects, Shockwave, Flash video, and OpenLaszlo. She has a habit of recognizing great and timely ideas, finding talented teams, and creating compelling software. She has led small and large teams and confidently turns vision into reality.<br />
<br />
...<br />
<br />
Sarah leads an innovative product strategy, design & development company, Blazing Cloud, and in her spare time works to diversify the Ruby on Rails with RailsBridge, which she co-founded in 2009. In keeping with her belief that programming is a life skill, she also regularly volunteers teaching programming to kids. Sarah believes that open source software provides solid technical foundations and compelling business models. She is an expert with Ruby and Rails and was a member of the OpenLaszlo core team, where she coded in asynchronous Javascript before it was cool."<br />
<br />
http://www.ultrasaurus.com/about/<br />
<br />
==John Allspaw==<br />
John Allspaw (https://twitter.com/allspaw) is the Senior Vice President for Technical Operations at Etsy (http://etsy.com). Prior to that he built infrastructure for Salon, InfoWorld, Flickr, and others. His publications include "Web Operations" and "The Art of Capacity Planning". You can find his blog at http://www.kitchensoap.com/. <br />
<br />
As library development teams grow from single programmers writing "glue" scripts to small teams working together on mid size web apps and further to large development shops producing complex and large scale systems, they find themselves struggling with issues of scale. These issues of scale are not just with the systems being built, but with the operations of the team itself. Operations can often be overlooked during the daily routine of project meetings, writing code, fixing bugs, etc. John's insights on operations and capacity planning would be useful to the library development community, particularly for those in departments that are maturing from one or two programmers to mid-size or larger development teams.<br />
<br />
==Cory Doctorow==<br />
BoingBoing.com, craphound.com. Author of sci-fi, copyright activist, etc. http://en.wikipedia.org/wiki/Cory_Doctorow<br />
<br />
==Jeri Ellsworth==<br />
<br />
Jerrielsworth.com, Jeri Ellsworth is an American entrepreneur and self-taught computer chip designer. She is best known for creating a Commodore 64 emulator within a joystick, in 2004, called C64 Direct-to-TV <br />
http://en.wikipedia.org/wiki/Jeri_Ellsworth<br />
<br />
==Sarah Lacy==<br />
<br />
Founder of PandoDaily, tech journalist and author. I (Roy) saw her speak and she was awesome. http://en.wikipedia.org/wiki/Sarah_Lacy<br />
<br />
== Jukka Pennanen & Mace Ojala ==<br />
<br />
Jukka Pennanen & Mace Ojala are the primary organizers of the Cycling For Libraries Unconference ( http://www.cyclingforlibraries.org/ )<br />
<br />
"Founded in 2011, the Cycling for libraries is an international cycling conference for librarians and library lovers. It aims to advocate libraries and increase awareness of the valuable services and resources that libraries offer to the community."<br />
<br />
I was lucky enough to participate in this event last summer and I think it was an incredible experience. I think Jukka and Mace have a great perspective in how to organize a wide encompassing international library community. <br />
<br />
== Daniel Reetz ==<br />
<br />
Daniel Reetz is the mastermind behind http://www.diybookscanner.org/ . It is an incredible community building open source software and hardware for book scanning using affordable consumer equipment. The project has evolved incredibly over the last few years and now include beautifully hackerspace-made scanner kits. He seems like a great speaker and I believe his perspective would be different from the traditional academic/research library focus. <br />
<br />
== Kathy Sierra ==<br />
<br />
Kathy Sierra has been interested in the brain and artificial intelligence since her days as a game developer (Virgin, Amblin', MGM). She is the co-creator of the bestselling Head First series (finalist for a Jolt Software Development award in 2003, and named to the Amazon Top Ten Editors Choice Computer Books for 2003 and 2004). She is also the founder of one of the largest community web sites in the world, javaranch.com. Kathy's passions are skiing, running, her Icelandic horse, gravity, and her latest favorite thing--Dance Dance Revolution.<br />
<br />
http://headrush.typepad.com/about.html<br />
<br />
== David Silver ==<br />
<br />
David Silver is an associate professor of media studies and environmental studies at the University of San Francisco where he teaches classes on media history, digital media production, and green media. David co-directs USF's Garden Project, a freshmen-to-senior living learning community built around an organic garden on campus. He blogs at http://silverinsf.blogspot.com/. He was the keynote at the TRLN Annual Meeting and talked about the importance of the Library as a keystone to his teaching of media studies, the Library as a keystone of collective curiosity and community action, and why we should enable students to contribute back to the Library. Some quotes I tweeted from his talk:<br />
<br />
* "Too often library instruction starts at library databases. Librarians, this has to stop." <br />
* "I want my seniors to contribute to the library, to give something back."<br />
* "Whenever there is community curiosity and collective action, that's where the library should be." <br />
<br />
I believe his keynote would be motivational in reflecting how what we do in Code4Lib is critical to Libraries support his mission as a professor and researcher, his students, and the community at large. Expect humor, humility, and creativity from David Silver.<br />
<br />
Submitted by Tim McGeary, UNC<br />
<br />
==Victoria Stodden==<br />
<br />
She is a co-founder of http://www.RunMyCode.org, an open platform for disseminating the code and data associated with published results, and enabling independent and public cloud-based verification of methods and findings, and an assistant professor of Statistics at Columbia University, and affiliated with the Columbia University Institute for Data Sciences and Engineering. She just recently gave a great keynote at Open Repositories. http://www.stanford.edu/~vcs/Bio.html<br />
<br />
==Andromeda Yelton==<br />
<br />
Formerly a developer with Unglue.it, she recently left full-time work there to work to help people learn to code. I (Roy) would love to hear her talk about how to help people break into coding. http://andromedayelton.com/about/<br />
<br />
==Gene Kim==<br />
<br />
Gene’s area of passion is helping companies build super-tribes where Development, IT Operations, Product and Project Management and Information Security simultaneously maximize throughput of features from “code complete” to “in production,” without causing chaos and disruption to the IT environment. He’s helped some of the largest Internet properties, such as Microsoft, Yahoo!, AOL and Microsoft companies he’s worked with Microsoft. He loves finding and fixing bottlenecks which impede and frustrate the entire organization, enabling management from each tribe to achieve the greater organizational goals.<br />
http://www.realgenekim.me/speaking/<br />
<br />
[[Category:Code4Lib2014]]</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=2014_Invited_Speakers_Nominations&diff=394642014 Invited Speakers Nominations2013-08-20T15:35:26Z<p>Timmcgeary: </p>
<hr />
<div>Nominations for invited speakers/keynotes for Code4Lib 2014. Please include a description and any relevant links and try to keep the list in alphabetical order. Suggestions will close on August 30, 2013 at midnight (EDT), which will be followed by a community vote. We will contact nominees before the vote to confirm their interest. <br />
<br />
<br />
==Sarah Allen==<br />
<br />
"Sarah Allen is a serial innovator with a history of developing leading-edge products, such as After Effects, Shockwave, Flash video, and OpenLaszlo. She has a habit of recognizing great and timely ideas, finding talented teams, and creating compelling software. She has led small and large teams and confidently turns vision into reality.<br />
<br />
...<br />
<br />
Sarah leads an innovative product strategy, design & development company, Blazing Cloud, and in her spare time works to diversify the Ruby on Rails with RailsBridge, which she co-founded in 2009. In keeping with her belief that programming is a life skill, she also regularly volunteers teaching programming to kids. Sarah believes that open source software provides solid technical foundations and compelling business models. She is an expert with Ruby and Rails and was a member of the OpenLaszlo core team, where she coded in asynchronous Javascript before it was cool."<br />
<br />
http://www.ultrasaurus.com/about/<br />
<br />
==John Allspaw==<br />
John Allspaw (https://twitter.com/allspaw) is the Senior Vice President for Technical Operations at Etsy (http://etsy.com). Prior to that he built infrastructure for Salon, InfoWorld, Flickr, and others. His publications include "Web Operations" and "The Art of Capacity Planning". You can find his blog at http://www.kitchensoap.com/. <br />
<br />
As library development teams grow from single programmers writing "glue" scripts to small teams working together on mid size web apps and further to large development shops producing complex and large scale systems, they find themselves struggling with issues of scale. These issues of scale are not just with the systems being built, but with the operations of the team itself. Operations can often be overlooked during the daily routine of project meetings, writing code, fixing bugs, etc. John's insights on operations and capacity planning would be useful to the library development community, particularly for those in departments that are maturing from one or two programmers to mid-size or larger development teams.<br />
<br />
==Cory Doctorow==<br />
BoingBoing.com, craphound.com. Author of sci-fi, copyright activist, etc. http://en.wikipedia.org/wiki/Cory_Doctorow<br />
<br />
==Jeri Ellsworth==<br />
<br />
Jerrielsworth.com, Jeri Ellsworth is an American entrepreneur and self-taught computer chip designer. She is best known for creating a Commodore 64 emulator within a joystick, in 2004, called C64 Direct-to-TV <br />
http://en.wikipedia.org/wiki/Jeri_Ellsworth<br />
<br />
==Sarah Lacy==<br />
<br />
Founder of PandoDaily, tech journalist and author. I (Roy) saw her speak and she was awesome. http://en.wikipedia.org/wiki/Sarah_Lacy<br />
<br />
== Jukka Pennanen & Mace Ojala ==<br />
<br />
Jukka Pennanen & Mace Ojala are the primary organizers of the Cycling For Libraries Unconference ( http://www.cyclingforlibraries.org/ )<br />
<br />
"Founded in 2011, the Cycling for libraries is an international cycling conference for librarians and library lovers. It aims to advocate libraries and increase awareness of the valuable services and resources that libraries offer to the community."<br />
<br />
I was lucky enough to participate in this event last summer and I think it was an incredible experience. I think Jukka and Mace have a great perspective in how to organize a wide encompassing international library community. <br />
<br />
== Daniel Reetz ==<br />
<br />
Daniel Reetz is the mastermind behind http://www.diybookscanner.org/ . It is an incredible community building open source software and hardware for book scanning using affordable consumer equipment. The project has evolved incredibly over the last few years and now include beautifully hackerspace-made scanner kits. He seems like a great speaker and I believe his perspective would be different from the traditional academic/research library focus. <br />
<br />
== Kathy Sierra ==<br />
<br />
Kathy Sierra has been interested in the brain and artificial intelligence since her days as a game developer (Virgin, Amblin', MGM). She is the co-creator of the bestselling Head First series (finalist for a Jolt Software Development award in 2003, and named to the Amazon Top Ten Editors Choice Computer Books for 2003 and 2004). She is also the founder of one of the largest community web sites in the world, javaranch.com. Kathy's passions are skiing, running, her Icelandic horse, gravity, and her latest favorite thing--Dance Dance Revolution.<br />
<br />
http://headrush.typepad.com/about.html<br />
<br />
== David Silver ==<br />
<br />
David Silver is an associate professor of media studies and environmental studies at the University of San Francisco where he teaches classes on media history, digital media production, and green media. David co-directs USF's Garden Project, a freshmen-to-senior living learning community built around an organic garden on campus. He blogs at http://silverinsf.blogspot.com/. He was the keynote at the TRLN Annual Meeting and talked about the importance of the Library as a keystone to his teaching of media studies, the Library as a keystone of collective curiosity and community action, and why we should enable students to contribute back to the Library. Some quotes I tweeted from his talk:<br />
<br />
* "Too often library instruction starts at library databases. Librarians, this has to stop." <br />
* "I want my seniors to contribute to the library, to give something back."<br />
* "Whenever there is community curiosity and collective action, that's where the library should be." <br />
<br />
I believe his keynote would be motivational in reflecting how what we do in Code4Lib is critical to Libraries support his mission as a professor and researcher, his students, and the community at large. Expect humor, humility, and creativity from David Silver.<br />
<br />
Submitted by Tim McGeary, UNC<br />
<br />
==Victoria Stodden==<br />
<br />
She is a co-founder of http://www.RunMyCode.org, an open platform for disseminating the code and data associated with published results, and enabling independent and public cloud-based verification of methods and findings, and an assistant professor of Statistics at Columbia University, and affiliated with the Columbia University Institute for Data Sciences and Engineering. She just recently gave a great keynote at Open Repositories. http://www.stanford.edu/~vcs/Bio.html<br />
<br />
==Andromeda Yelton==<br />
<br />
Formerly a developer with Unglue.it, she recently left full-time work there to work to help people learn to code. I (Roy) would love to hear her talk about how to help people break into coding. http://andromedayelton.com/about/<br />
<br />
<br />
==Gene Kim==<br />
<br />
Gene’s area of passion is helping companies build super-tribes where Development, IT Operations, Product and Project Management and Information Security simultaneously maximize throughput of features from “code complete” to “in production,” without causing chaos and disruption to the IT environment. He’s helped some of the largest Internet properties, such as Microsoft, Yahoo!, AOL and Microsoft companies he’s worked with Microsoft. He loves finding and fixing bottlenecks which impede and frustrate the entire organization, enabling management from each tribe to achieve the greater organizational goals.<br />
http://www.realgenekim.me/speaking/<br />
<br />
[[Category:Code4Lib2014]]</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=2014_Invited_Speakers_Nominations&diff=394332014 Invited Speakers Nominations2013-08-07T14:16:51Z<p>Timmcgeary: </p>
<hr />
<div>Nominations for invited speakers/keynotes for Code4Lib 2014. Please include a description and any relevant links and try to keep the list in alphabetical order. Suggestions will close on August 30, 2013 at midnight (EDT), which will be followed by a community vote. We will contact nominees before the vote to confirm their interest. <br />
<br />
<br />
==Sarah Allen==<br />
<br />
"Sarah Allen is a serial innovator with a history of developing leading-edge products, such as After Effects, Shockwave, Flash video, and OpenLaszlo. She has a habit of recognizing great and timely ideas, finding talented teams, and creating compelling software. She has led small and large teams and confidently turns vision into reality.<br />
<br />
...<br />
<br />
Sarah leads an innovative product strategy, design & development company, Blazing Cloud, and in her spare time works to diversify the Ruby on Rails with RailsBridge, which she co-founded in 2009. In keeping with her belief that programming is a life skill, she also regularly volunteers teaching programming to kids. Sarah believes that open source software provides solid technical foundations and compelling business models. She is an expert with Ruby and Rails and was a member of the OpenLaszlo core team, where she coded in asynchronous Javascript before it was cool."<br />
<br />
http://www.ultrasaurus.com/about/<br />
<br />
==John Allspaw==<br />
John Allspaw (https://twitter.com/allspaw) is the Senior Vice President for Technical Operations at Etsy (http://etsy.com). Prior to that he built infrastructure for Salon, InfoWorld, Flickr, and others. His publications include "Web Operations" and "The Art of Capacity Planning". You can find his blog at http://www.kitchensoap.com/. <br />
<br />
As library development teams grow from single programmers writing "glue" scripts to small teams working together on mid size web apps and further to large development shops producing complex and large scale systems, they find themselves struggling with issues of scale. These issues of scale are not just with the systems being built, but with the operations of the team itself. Operations can often be overlooked during the daily routine of project meetings, writing code, fixing bugs, etc. John's insights on operations and capacity planning would be useful to the library development community, particularly for those in departments that are maturing from one or two programmers to mid-size or larger development teams.<br />
<br />
==Cory Doctorow==<br />
BoingBoing.com, craphound.com. Author of sci-fi, copyright activist, etc. http://en.wikipedia.org/wiki/Cory_Doctorow<br />
<br />
==Jeri Ellsworth==<br />
<br />
Jerrielsworth.com, Jeri Ellsworth is an American entrepreneur and self-taught computer chip designer. She is best known for creating a Commodore 64 emulator within a joystick, in 2004, called C64 Direct-to-TV <br />
http://en.wikipedia.org/wiki/Jeri_Ellsworth<br />
<br />
==Sarah Lacy==<br />
<br />
Founder of PandoDaily, tech journalist and author. I (Roy) saw her speak and she was awesome. http://en.wikipedia.org/wiki/Sarah_Lacy<br />
<br />
==Victoria Stodden==<br />
<br />
She is a co-founder of http://www.RunMyCode.org, an open platform for disseminating the code and data associated with published results, and enabling independent and public cloud-based verification of methods and findings, and an assistant professor of Statistics at Columbia University, and affiliated with the Columbia University Institute for Data Sciences and Engineering. She just recently gave a great keynote at Open Repositories. http://www.stanford.edu/~vcs/Bio.html<br />
<br />
==Andromeda Yelton==<br />
<br />
Formerly a developer with Unglue.it, she recently left full-time work there to work to help people learn to code. I (Roy) would love to hear her talk about how to help people break into coding. http://andromedayelton.com/about/<br />
<br />
== David Silver ==<br />
<br />
David Silver is an associate professor of media studies and environmental studies at the University of San Francisco where he teaches classes on media history, digital media production, and green media. David co-directs USF's Garden Project, a freshmen-to-senior living learning community built around an organic garden on campus. He blogs at http://silverinsf.blogspot.com/. He was the keynote at the TRLN Annual Meeting and talked about the importance of the Library as a keystone to his teaching of media studies, the Library as a keystone of collective curiosity and community action, and why we should enable students to contribute back to the Library. Some quotes I tweeted from his talk:<br />
<br />
* "Too often library instruction starts at library databases. Librarians, this has to stop." <br />
* "I want my seniors to contribute to the library, to give something back."<br />
* "Whenever there is community curiosity and collective action, that's where the library should be." <br />
<br />
I believe his keynote would be motivational in reflecting how what we do in Code4Lib is critical to Libraries support his mission as a professor and researcher, his students, and the community at large. Expect humor, humility, and creativity from David Silver.<br />
<br />
Submitted by Tim McGeary, UNC<br />
<br />
<br />
[[Category:Code4Lib2014]]</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39397Code4Lib 2014 Conference Planning Volunteers2013-08-05T13:35:37Z<p>Timmcgeary: /* Code4Lib 2014 Committees */</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 />
A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. It has been shared with code4libcon and code4lib2014 google groups.<br />
<br />
The Code42014 Conference Committee meets bi-weekly on Tuesdays at 11am EDT. If you would like to join the calls or have an agenda item, email one or both of the co-Leads: Emily Lynema (NCSU) and Tim McGeary (UNC).<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 />
Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br />
<br />
* Kevin S. Clarke (O'Reilly) and general wrangling (nominated as lead)<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 />
Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013<br /><br />
Keynote speaker voting - September 9, 2013 - September 20, 2013<br /><br />
Have speakers finalized by November 15, 2013<br />
<br />
* Jason Casden (NCSU) -- lead<br />
* Tom Johnson (Johnson.tom@gmail.com)<br />
* Bret Davidson (NCSU)<br />
* Jeff Campbell (UNC)<br />
<br />
== Onsite Volunteer Committee ==<br />
<br />
This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br />
<br />
* Kevin S. Clarke<br />
* Kevin Beswick (NCSU)<br />
* Yan Wang (NCCU)<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 />
Call for pre-conf proposals -- October 14, 2013<br /><br />
Deadline for pre-conf proposals -- December 6, 2013 <br /><br />
Finalize pre-confs before registration opens -- January 3, 2014<br /><br />
Send rosters to pre-conf organizers -- by February 21, 2014<br />
<br />
* Adam Constabaris (NCSU) -- nominated as lead<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 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 />
Call for talk proposals -- October 14 - November 8, 2013<br /><br />
First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013<br /><br />
Voting on talks -- November 18, 203 - December 6, 2013<br /><br />
Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013<br /><br />
Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)<br /><br />
Post final program schedule with talks - January 13, 2014<br />
<br />
* Tom Johnson (Johnson.tom@gmail.com) -- lead<br />
* Kevin Beswick (NCSU)<br />
* Ranti Junus (MSU)<br />
* Roy Tennant (OCLC)<br />
* Trevor Thornton (hellotrevorthornton@gmail.com)<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 />
Call for applicants -- November 18, 2013 - December 13, 2013<br /><br />
Determine winners -- December 14, 2014 - January 5, 2014<br /><br />
Notify winners -- January 6, 2014 (must be before registration)<br />
<br />
* Jason Ronallo (NCSU) -- lead<br />
* Cory Lown (NCSU)<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 (UNC, Lead, tim.mcgeary@unc.edu)<br />
* Roy Tennant (OCLC)<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)<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 />
Work with local team to get solid A/V estimates by late November 2013 to use for final budget.<br />
<br />
- Francis Kayiwa<br />
* Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc 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. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.<br />
<br />
Call for T-shirt designs - December 2, 2014 - January 3, 2014<br /><br />
Voting on T-shirt designs - January 13, 2014 - January 24, 2014<br /><br />
Get bids based on sizes and design - January 27, 2014 - February 14, 2014<br /><br />
Order t-shirts by February 17, 2014<br />
<br />
*Charlie Morris (NCSU) -- lead<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 />
* Ranti Junus<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>Timmcgearyhttps://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39396Code4Lib 2014 Conference Planning Volunteers2013-08-05T13:35:07Z<p>Timmcgeary: /* Code4Lib 2014 Committees */</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 />
A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. It has been shared with code4libcon and code4lib2014 google groups.<br />
<br />
The Code42014 Conference Committee meets bi-weekly on Tuesdays at 11am EDT. If you would like to added or have an agenda item, email either of the co-Leads: Emily Lynema (NCSU) and Tim McGeary (UNC).<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 />
Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br />
<br />
* Kevin S. Clarke (O'Reilly) and general wrangling (nominated as lead)<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 />
Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013<br /><br />
Keynote speaker voting - September 9, 2013 - September 20, 2013<br /><br />
Have speakers finalized by November 15, 2013<br />
<br />
* Jason Casden (NCSU) -- lead<br />
* Tom Johnson (Johnson.tom@gmail.com)<br />
* Bret Davidson (NCSU)<br />
* Jeff Campbell (UNC)<br />
<br />
== Onsite Volunteer Committee ==<br />
<br />
This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br />
<br />
* Kevin S. Clarke<br />
* Kevin Beswick (NCSU)<br />
* Yan Wang (NCCU)<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 />
Call for pre-conf proposals -- October 14, 2013<br /><br />
Deadline for pre-conf proposals -- December 6, 2013 <br /><br />
Finalize pre-confs before registration opens -- January 3, 2014<br /><br />
Send rosters to pre-conf organizers -- by February 21, 2014<br />
<br />
* Adam Constabaris (NCSU) -- nominated as lead<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 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 />
Call for talk proposals -- October 14 - November 8, 2013<br /><br />
First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013<br /><br />
Voting on talks -- November 18, 203 - December 6, 2013<br /><br />
Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013<br /><br />
Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)<br /><br />
Post final program schedule with talks - January 13, 2014<br />
<br />
* Tom Johnson (Johnson.tom@gmail.com) -- lead<br />
* Kevin Beswick (NCSU)<br />
* Ranti Junus (MSU)<br />
* Roy Tennant (OCLC)<br />
* Trevor Thornton (hellotrevorthornton@gmail.com)<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 />
Call for applicants -- November 18, 2013 - December 13, 2013<br /><br />
Determine winners -- December 14, 2014 - January 5, 2014<br /><br />
Notify winners -- January 6, 2014 (must be before registration)<br />
<br />
* Jason Ronallo (NCSU) -- lead<br />
* Cory Lown (NCSU)<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 (UNC, Lead, tim.mcgeary@unc.edu)<br />
* Roy Tennant (OCLC)<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)<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 />
Work with local team to get solid A/V estimates by late November 2013 to use for final budget.<br />
<br />
- Francis Kayiwa<br />
* Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc 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. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.<br />
<br />
Call for T-shirt designs - December 2, 2014 - January 3, 2014<br /><br />
Voting on T-shirt designs - January 13, 2014 - January 24, 2014<br /><br />
Get bids based on sizes and design - January 27, 2014 - February 14, 2014<br /><br />
Order t-shirts by February 17, 2014<br />
<br />
*Charlie Morris (NCSU) -- lead<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 />
* Ranti Junus<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>Timmcgearyhttps://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39395Code4Lib 2014 Conference Planning Volunteers2013-08-05T13:32:16Z<p>Timmcgeary: /* Sponsorships 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 />
A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. It has been shared with code4libcon and code4lib2014 google groups.<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 />
Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br />
<br />
* Kevin S. Clarke (O'Reilly) and general wrangling (nominated as lead)<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 />
Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013<br /><br />
Keynote speaker voting - September 9, 2013 - September 20, 2013<br /><br />
Have speakers finalized by November 15, 2013<br />
<br />
* Jason Casden (NCSU) -- lead<br />
* Tom Johnson (Johnson.tom@gmail.com)<br />
* Bret Davidson (NCSU)<br />
* Jeff Campbell (UNC)<br />
<br />
== Onsite Volunteer Committee ==<br />
<br />
This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br />
<br />
* Kevin S. Clarke<br />
* Kevin Beswick (NCSU)<br />
* Yan Wang (NCCU)<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 />
Call for pre-conf proposals -- October 14, 2013<br /><br />
Deadline for pre-conf proposals -- December 6, 2013 <br /><br />
Finalize pre-confs before registration opens -- January 3, 2014<br /><br />
Send rosters to pre-conf organizers -- by February 21, 2014<br />
<br />
* Adam Constabaris (NCSU) -- nominated as lead<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 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 />
Call for talk proposals -- October 14 - November 8, 2013<br /><br />
First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013<br /><br />
Voting on talks -- November 18, 203 - December 6, 2013<br /><br />
Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013<br /><br />
Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)<br /><br />
Post final program schedule with talks - January 13, 2014<br />
<br />
* Tom Johnson (Johnson.tom@gmail.com) -- lead<br />
* Kevin Beswick (NCSU)<br />
* Ranti Junus (MSU)<br />
* Roy Tennant (OCLC)<br />
* Trevor Thornton (hellotrevorthornton@gmail.com)<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 />
Call for applicants -- November 18, 2013 - December 13, 2013<br /><br />
Determine winners -- December 14, 2014 - January 5, 2014<br /><br />
Notify winners -- January 6, 2014 (must be before registration)<br />
<br />
* Jason Ronallo (NCSU) -- lead<br />
* Cory Lown (NCSU)<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 (UNC, Lead, tim.mcgeary@unc.edu)<br />
* Roy Tennant (OCLC)<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 />
Work with local team to get solid A/V estimates by late November 2013 to use for final budget.<br />
<br />
- Francis Kayiwa<br />
* Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc 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. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.<br />
<br />
Call for T-shirt designs - December 2, 2014 - January 3, 2014<br /><br />
Voting on T-shirt designs - January 13, 2014 - January 24, 2014<br /><br />
Get bids based on sizes and design - January 27, 2014 - February 14, 2014<br /><br />
Order t-shirts by February 17, 2014<br />
<br />
*Charlie Morris (NCSU) -- lead<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 />
* Ranti Junus<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>Timmcgearyhttps://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39394Code4Lib 2014 Conference Planning Volunteers2013-08-05T13:31:27Z<p>Timmcgeary: /* Sponsorships 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 />
A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. It has been shared with code4libcon and code4lib2014 google groups.<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 />
Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br />
<br />
* Kevin S. Clarke (O'Reilly) and general wrangling (nominated as lead)<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 />
Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013<br /><br />
Keynote speaker voting - September 9, 2013 - September 20, 2013<br /><br />
Have speakers finalized by November 15, 2013<br />
<br />
* Jason Casden (NCSU) -- lead<br />
* Tom Johnson (Johnson.tom@gmail.com)<br />
* Bret Davidson (NCSU)<br />
* Jeff Campbell (UNC)<br />
<br />
== Onsite Volunteer Committee ==<br />
<br />
This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br />
<br />
* Kevin S. Clarke<br />
* Kevin Beswick (NCSU)<br />
* Yan Wang (NCCU)<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 />
Call for pre-conf proposals -- October 14, 2013<br /><br />
Deadline for pre-conf proposals -- December 6, 2013 <br /><br />
Finalize pre-confs before registration opens -- January 3, 2014<br /><br />
Send rosters to pre-conf organizers -- by February 21, 2014<br />
<br />
* Adam Constabaris (NCSU) -- nominated as lead<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 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 />
Call for talk proposals -- October 14 - November 8, 2013<br /><br />
First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013<br /><br />
Voting on talks -- November 18, 203 - December 6, 2013<br /><br />
Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013<br /><br />
Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)<br /><br />
Post final program schedule with talks - January 13, 2014<br />
<br />
* Tom Johnson (Johnson.tom@gmail.com) -- lead<br />
* Kevin Beswick (NCSU)<br />
* Ranti Junus (MSU)<br />
* Roy Tennant (OCLC)<br />
* Trevor Thornton (hellotrevorthornton@gmail.com)<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 />
Call for applicants -- November 18, 2013 - December 13, 2013<br /><br />
Determine winners -- December 14, 2014 - January 5, 2014<br /><br />
Notify winners -- January 6, 2014 (must be before registration)<br />
<br />
* Jason Ronallo (NCSU) -- lead<br />
* Cory Lown (NCSU)<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 (UNC-CH, Lead tim dot mcgeary at unc dot edu)<br />
* Roy Tennant (OCLC)<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 />
Work with local team to get solid A/V estimates by late November 2013 to use for final budget.<br />
<br />
- Francis Kayiwa<br />
* Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc 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. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.<br />
<br />
Call for T-shirt designs - December 2, 2014 - January 3, 2014<br /><br />
Voting on T-shirt designs - January 13, 2014 - January 24, 2014<br /><br />
Get bids based on sizes and design - January 27, 2014 - February 14, 2014<br /><br />
Order t-shirts by February 17, 2014<br />
<br />
*Charlie Morris (NCSU) -- lead<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 />
* Ranti Junus<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>Timmcgearyhttps://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39393Code4Lib 2014 Conference Planning Volunteers2013-08-05T13:30:24Z<p>Timmcgeary: /* Sponsorships 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 />
A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. It has been shared with code4libcon and code4lib2014 google groups.<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 />
Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br />
<br />
* Kevin S. Clarke (O'Reilly) and general wrangling (nominated as lead)<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 />
Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013<br /><br />
Keynote speaker voting - September 9, 2013 - September 20, 2013<br /><br />
Have speakers finalized by November 15, 2013<br />
<br />
* Jason Casden (NCSU) -- lead<br />
* Tom Johnson (Johnson.tom@gmail.com)<br />
* Bret Davidson (NCSU)<br />
* Jeff Campbell (UNC)<br />
<br />
== Onsite Volunteer Committee ==<br />
<br />
This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br />
<br />
* Kevin S. Clarke<br />
* Kevin Beswick (NCSU)<br />
* Yan Wang (NCCU)<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 />
Call for pre-conf proposals -- October 14, 2013<br /><br />
Deadline for pre-conf proposals -- December 6, 2013 <br /><br />
Finalize pre-confs before registration opens -- January 3, 2014<br /><br />
Send rosters to pre-conf organizers -- by February 21, 2014<br />
<br />
* Adam Constabaris (NCSU) -- nominated as lead<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 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 />
Call for talk proposals -- October 14 - November 8, 2013<br /><br />
First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013<br /><br />
Voting on talks -- November 18, 203 - December 6, 2013<br /><br />
Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013<br /><br />
Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)<br /><br />
Post final program schedule with talks - January 13, 2014<br />
<br />
* Tom Johnson (Johnson.tom@gmail.com) -- lead<br />
* Kevin Beswick (NCSU)<br />
* Ranti Junus (MSU)<br />
* Roy Tennant (OCLC)<br />
* Trevor Thornton (hellotrevorthornton@gmail.com)<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 />
Call for applicants -- November 18, 2013 - December 13, 2013<br /><br />
Determine winners -- December 14, 2014 - January 5, 2014<br /><br />
Notify winners -- January 6, 2014 (must be before registration)<br />
<br />
* Jason Ronallo (NCSU) -- lead<br />
* Cory Lown (NCSU)<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)<br />
* Roy Tennant (OCLC)<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 />
Work with local team to get solid A/V estimates by late November 2013 to use for final budget.<br />
<br />
- Francis Kayiwa<br />
* Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc 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. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.<br />
<br />
Call for T-shirt designs - December 2, 2014 - January 3, 2014<br /><br />
Voting on T-shirt designs - January 13, 2014 - January 24, 2014<br /><br />
Get bids based on sizes and design - January 27, 2014 - February 14, 2014<br /><br />
Order t-shirts by February 17, 2014<br />
<br />
*Charlie Morris (NCSU) -- lead<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 />
* Ranti Junus<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>Timmcgearyhttps://wiki.code4lib.org/index.php?title=2012_nominations_list&diff=91852012 nominations list2011-07-25T17:59:04Z<p>Timmcgeary: /* Damon Horowitz */</p>
<hr />
<div>Nominations for invited speakers for Code4Lib 2010. Alphabetical order.<br />
<br />
==Hanson Hosein==<br />
==Adam Jacob==<br />
"Adam Jacob is a co-founder of Opscode and the creator of Chef. Prior to Opscode, he founded HJK Solutions, an automated infrastructure consultancy. During two years at HJK, he built new infrastructures for 15 different startups. Including his time at HJK, Adam has 13 years of experience as a systems administrator, systems architect, and tools developer. He has been responsible for large production infrastructures, internal corporate automation, and Sarbanes-Oxley compliance efforts."<br />
[http://www.youtube.com/watch?v=Fx8OBeNmaWw| Adam is a good speaker.] --Anjanette<br />
==Aaron Swartz==<br />
<br />
<br />
== Damon Horowitz ==<br />
Damon Horowitz is a philosophy professor and serial entrepreneur. He recently joined Google as In-House Philosopher / Director of Engineering, heading development of several initiatives involving social and search. He came to Google from Aardvark, the social search engine, where he was co-founder and CTO, overseeing product development and research strategy. Prior to Aardvark, Horowitz built several companies around applications of intelligent language processing. He co-founded Perspecta (acquired by Excite), was lead architect for Novation Biosciences (acquired by Agilent), and co-founded NewsDB (now Daylife).<br />
Horowitz teaches courses in philosophy, cognitive science, and computer science at several institutions, including Stanford, NYU, University of Pennsylvania and San Quentin State Prison (source: [http://www.ted.com/speakers/damon_horowitz.html | TED Profiles])<br />
<br />
See this excellent article Damon wrote for the Chronicle of Higher Education. His thesis is why he would be a perfect keynote for Code4Lib 2012: http://chronicle.com/article/From-Technologist-to/128231/?sid=wc&utm_source=wc&utm_medium=en</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=2012_nominations_list&diff=91842012 nominations list2011-07-25T17:58:51Z<p>Timmcgeary: </p>
<hr />
<div>Nominations for invited speakers for Code4Lib 2010. Alphabetical order.<br />
<br />
==Hanson Hosein==<br />
==Adam Jacob==<br />
"Adam Jacob is a co-founder of Opscode and the creator of Chef. Prior to Opscode, he founded HJK Solutions, an automated infrastructure consultancy. During two years at HJK, he built new infrastructures for 15 different startups. Including his time at HJK, Adam has 13 years of experience as a systems administrator, systems architect, and tools developer. He has been responsible for large production infrastructures, internal corporate automation, and Sarbanes-Oxley compliance efforts."<br />
[http://www.youtube.com/watch?v=Fx8OBeNmaWw| Adam is a good speaker.] --Anjanette<br />
==Aaron Swartz==<br />
<br />
<br />
== Damon Horowitz ==<br />
Damon Horowitz is a philosophy professor and serial entrepreneur. He recently joined Google as In-House Philosopher / Director of Engineering, heading development of several initiatives involving social and search. He came to Google from Aardvark, the social search engine, where he was co-founder and CTO, overseeing product development and research strategy. Prior to Aardvark, Horowitz built several companies around applications of intelligent language processing. He co-founded Perspecta (acquired by Excite), was lead architect for Novation Biosciences (acquired by Agilent), and co-founded NewsDB (now Daylife).<br />
Horowitz teaches courses in philosophy, cognitive science, and computer science at several institutions, including Stanford, NYU, University of Pennsylvania and San Quentin State Prison (source: [http://www.ted.com/speakers/damon_horowitz.html | TED Profiles]<br />
<br />
See this excellent article Damon wrote for the Chronicle of Higher Education. His thesis is why he would be a perfect keynote for Code4Lib 2012: http://chronicle.com/article/From-Technologist-to/128231/?sid=wc&utm_source=wc&utm_medium=en</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=2011talks_Submissions&diff=62702011talks Submissions2010-11-10T16:54:29Z<p>Timmcgeary: </p>
<hr />
<div>Deadline for talk submission is ''Saturday, November 13''. See [http://www.mail-archive.com/code4lib@listserv.nd.edu/msg08878.html this mailing list post for more details], or the general [http://code4lib.org/conference/2011 Code4Lib 2011] page.<br />
<br />
See the [http://wiki.code4lib.org/index.php/2011talkscall_Call_for_Submissions Call for Submissions] for guidelines on appropriate topic talks and the criteria on which submissions are evaluated.<br />
<br />
Please follow the formatting guidelines:<br />
<br />
<pre><br />
== Talk Title: ==<br />
<br />
* Speaker's name, affiliation, and email address<br />
* Second speaker's name, affiliation, email address, if second speaker<br />
<br />
Abstract of no more than 500 words.<br />
</pre><br />
<br />
== How "great" are the Great Books? ==<br />
<br />
* Eric Lease Morgan, University of Notre Dame (emorgan at nd.edu)<br />
<br />
In the 1960s a set of books called the Great Books of the Western World was published. It was supposed to represent the best of Western literature and enable the reader to further their liberal arts education. Sixty volumes in all, it included works by Plato, Aristotle, Shakespeare, Milton, Galileo, Kepler, Melville, Darwin, etc. These great books were selected based on the way they discussed a set of 102 "great ideas" such as art, astronomy, beauty, evil, evolution, mind, nature, poetry, revolution, science, will, wisdom, etc. How "great" are these books, and how "great" are the ideas expressed in them?<br />
<br />
Given full text versions of these books it is almost trivial to use the "great ideas" as input and apply relevancy ranking algorithms against the texts thus creating a sort of score -- a "Great Ideas Coefficient". Term Frequency/Inverse Document Frequency (TFIDF) is a well-established algorithm for computing just this sort of thing:<br />
<br />
relevancy = ( c / t ) * log( d / f ) where:<br />
<br />
* c = number of times a given word appears in a document<br />
* t = total number of words in a document<br />
* d = total number of documents in a corpus<br />
* f = total number of documents containing a given word<br />
<br />
Thus, to calculate our Great Ideas Coefficient I sum the relevancy score for each "great idea" for each "great book". Plato's Republic might have a cumulative score of 525 while Aristotle's On The History Of Animals might have a cumulative score of 251. Books with a larger Coefficient could be considered greater. Given such a score a person could measure a book's "greatness". We could then compare the score to the scores of other books. Which book is the "greatest"? We could compare the score to other measurable things such as book's length or date to see if there were correlations. Are "great books" longer or shorter than others? Do longer books contain more "great ideas"? Are there other books that were not included in the set that maybe should have been included?<br />
<br />
The first part of this talk describes the different steps involved in the text pre-processing to calculate an accurate TFIDF value for each item of the corpus. The results and statistical analysis are discussed in the second part. Finally I will outline the remaining work such as refining the analysis and extending the current quantitative process to a web implementation.<br />
<br />
== UNR BookFinder: Leveraging Google Books to Move Beyond Catalog Search ==<br />
* Will Kurt, University of Nevada, Reno, (wkurt at unr.edu)<br />
Google Books is a great tool, but it lacks an easy method allowing users to access the items they find through their library. The UNR BookFinder is a mashup of the Google Books and WorldCat APIs (and some ugly hacks) which allows users to search for items with the power of Google’s fulltext search while eliminating the need to search all of the library’s various resources to find an item. The UNR BookFinder automatically searches the catalog and consortial ILL for the item, if these fail an ILLiad request form as automatically filled out. The end result is that the user can explore an universe of books and access them as fast as possible through the university library. A video of the alpha version can be found [http://www.youtube.com/watch?v=qaqcUSTtdVk here].<br />
<br />
== Moving a large multi-tiered search architecture from dedicated hosts to the cloud ==<br />
* Peter Ciuffetti, Senior Software Engineer, Credo Reference Ltd. (pete at credoreference.com)<br />
So you want to move a large production search service from dedicated hosts to the cloud? The flexibility is enticing, the costs are attractive, the geek cred is undeniable. Our cloud adventure came with many undocumented surprises ranging from mysterious server behavior to sales engineers suggesting that 'maybe the cloud isn't for you'. We eventually made it all work and our production service is now on the cloud. This talk will cover what the cloud product FAQs don't say, what their tech support doesn't know (or won't say) and mistakes you can avoid by talking to the guys with the arrows in their backs.<br />
<br />
== VuFind Beyond MARC: Discovering Everything Else ==<br />
* Demian Katz, Library Technology Development Specialist, Villanova University (demian dot katz at villanova dot edu)<br />
The VuFind[http://vufind.org] discovery layer has been providing a user-friendly interface to MARC records for several years now. However, library data consists of more than just MARC records, and VuFind has grown to accommodate just about anything you can throw at it. This presentation will examine the new workflows and tools that enable discovery of non-MARC resources and some of the non-traditional applications of VuFind that they make possible. Technologies covered will include OAI-PMH, XSLT, Aperture, Solr and, of course, VuFind itself.<br />
<br />
== Linked data apps for medical professionals ==<br />
* Rurik Thomas Greenall, NTNU Library, (rurik dot greenall at ub dot ntnu dot no)<br />
The promise of linked data for libraries has yet to be realized, as a demonstration of the power of RDF, HTTP-URIs and SPARQL, NTNU Library together with the Norwegian Electronic Health Library produced a linked data representation of MeSH and created a small translation app that can be used to help health professionals identify the right term and apply it in their database searches. This talk presents the simple ways in which the core technologies and concepts in linked data provide a solid, time-saving way of developing usable applications.<br />
<br />
== fiwalk With Me: Building Emergent Pre-Ingest Workflows for Digital Archival Records using Open Source Forensic Software ==<br />
* Mark A. Matienzo, Manuscripts and Archives, Yale University Library (mark at matienzo dot org)<br />
Many of the complications of born-digital records involve preparing them for transfer into a storage or preservation environment. Digital evidence of any kind is easily susceptible to unintentional and intentional modification. This presentation will describe the use of open source forensic software in pre-ingest workflows for digital archives. Digital archivists and other digital curation practitioners can develop emergent processes to prepare records for ingest and transfer using a combination of relatively simple tools. The granularity and simplicity of these tools and procedures provides the possibility for their smooth integration into a digital curation environment built on micro-services.<br />
== Why (Code4) Libraries Exist ==<br />
* Eric Hellman, President, Gluejar, Inc. (eric at hellman dot net)<br />
Libraries have historically delivered value to society by facilitating the sharing of books. The library "brand" is built around the building and exploitation of their collections. These collections have been acquired and owned. As ebook readers become the preferred consumption platform for books, libraries are beginning to come to terms with the fact that they don't own their digital collections, and can't share books as they'd like to. Yet libraries continue to be valuable in many ways. In this transitional period, only one thing can save libraries from irrelevance and dissipation: Code.<br />
== The Story of TILE: Making Modular & Reusable Tools ==<br />
* Doug Reside, MITH, University of Maryland (dougreside at gmail dot com)<br />
<br />
The Text Image Linking Environment (TILE) is a collaborative project between the Maryland Institute for Technology in the Humanities (MITH), the Digital Library Program at Indiana University, and the School of Library and Information Science at Indiana University Bloomington. Since May 2009, the TILE project team has been developing through NEH Research & Development funding a web-based, modular, image markup tool for both semi-automated linking between encoded text and image of text, and image annotation. The software will be complete and ready for release in June 2011. <br />
<br />
The basic functionality of TILE is to create links between images and text that relates to that image – either annotations or transcriptions. We have paid particular attention to linking between image of text and transcription of text. These links may be made manually, but the project also includes an algorithm, written in JavaScript, for recognizing text within an image and automatically associating the coordinates with a Unicode transcription. Additionally, the tool can import and export transcriptions and links from and to a variety of metadata formats (TEI, METS, OWL) and will provide an API for developers to write mappings for additional formats. Of course, this functionality is immediately useful to a relatively limited set of editors of digital materials, but we have made modularity and extensibility primary goals of the project.<br />
<br />
Many members of the TILE development team are also members of the Open Annotation Collaboration (OAC), and have therefore attempted to develop TILE’s annotation features to be OAC compliant. Like OAC, TILE assumes that the text and the images to be linked may exist at separate and completely unconnected servers. When a user starts the TILE tool for the first time, she is prompted to supply a URI to a TILE compliant JSON file. <br />
<br />
TILE’s JSON is simple and thoroughly documented, and we provide several translators to map common existing metadata formats to the format. We have already created a PHP script that will generate TILE JSON from a TEI P5 document and are currently working to do the same for the METS files used in the Indiana University’s METS navigator tool. <br />
<br />
Additionally, TILE provides a modular exporting tool that allows users to run the work they’ve done in TILE through an external translator and then download the result to the client computer. For example, a user may import a set of images and transcripts from a METS file at the Library of Congress, use TILE to link images and text, and then export the result as a TEI file. The TEI file may then be reimported to TILE at a later data to further edit or convert the file.<br />
<br />
At Code4Lib, we will demonstrate the functionality of TILE and display a poster and provide handouts that describe the thinking behind TILE, how it is intended to be used, and details on how TILE is built and functions.<br />
<br />
== We Don’t Server Their Kind : Managing E-resources with Flat-File Databases ==<br />
* Junior Tidal, Multimedia and Web Services Librarian, New York City College of Technology, CUNY (jtidal at citytech dot cuny dot edu)<br />
Managing E-resources can be a daunting challenge. URLs, database names, and even vendors can change, go down, or simply cease to exist. My proposal involves the use of a PHP-based, flat-file database driven web tool for database management. The design of this program was to fulfill two needs: ease of use for librarians with a lack of programming experience and to meet the security and technical restrictions placed by the college’s IT department. My presentation will explore the development of this tool, challenges within its development, and future improvements. PHP code and the flat-file database will also be explained and provided to attendees. For a working demonstration feel free to visit the New York City College of Technology’s A-Z database [http://library.citytech.cuny.edu/research/AToZ/index.php page] or the subject database [http://library.citytech.cuny.edu/research/subject/index.php page].<br />
<br />
== Drupal 7 as a Rapid Application Development Tool ==<br />
<br />
* Cary Gordon, President, The Cherry Hill Company & Board Member, The Drupal Association (cgordon at chillco dawt com)<br />
Five years ago, I discovered that the Drupal CMS had a programming framework disguised as an API, and learned that I could use it to solve problems.<br />
<br />
Drupal 7 builds on that to provide a powerful toolset for interfacing with, manipulating and presenting data. It empowers tool-builders by providing a minimal install option, along with a more powerful installation profile system makes it easier for developers to package and distribute their applications.<br />
<br />
== Helping Open Source Succeed ==<br />
<br />
* [[User:DataGazetteer|Peter Murray]], LYRASIS, [mailto:Peter.Murray@lyrasis.org Peter.Murray@lyrasis.org] <br />
* Tim Daniels, LYRASIS, [mailto:Tim.Daniels@lyrasis.org Tim.Daniels@lyrasis.org]<br />
<br />
Deciding if open source is an option for your institution, or what open source software matches your institution’s needs and capabilities, is a complex decision. LYRASIS is developing a new area of focus to assist libraries with decision tools and an open source software registry. We want to learn from the creators of open source software what questions institutions have when considering the adoption of open source software and what information you would like to see in a registry that compares various open source tools. A summary of topics discussed in this session will be openly published as part of LYRASIS’ program development plans and decision support resources.<br />
<br />
The mission of the new and emerging LYRASIS Technology Services area is to serve members and the broader library community as a provider of expertise and capacity in open source based technology solutions. We think that viable roles for an organization supporting open source software are to: a) Increase understanding of open source technology within the library community, including value, benefits, risks, and costs; b) Assist in decision-making by providing resources to help libraries evaluate open source technologies, institutional readiness, and capacity for adoption; c) Support adoption and use of open source technologies and systems within libraries and consortia; d) Foster integration of open source software tools to expand the ability of existing programs to meet a range of library user needs; e) Develop and test new open source software programs, and contribute to the development of existing programs; f) Support long-term sustainability of viable, library-based open source software and systems. We recognize that these roles exist to some extent on a continuum, with latter services related to development and sustainability building on the knowledge and experience gained through deployment of existing open source systems. In turn, effective adoption and use depends on understanding open source systems and having resources to assist in decision-making and implementation.<br />
<br />
With open source software in the “innovator” and “early adopter” stages in the library community, we intend to focus its initial efforts on roles A-D in the above list: increased understanding, decision-support, and effective adoption and integration of existing library-focused open source systems. This session is focused on the decision-support services area of activity.<br />
<br />
The impact of this session is expected to be far reaching, if initially subtle. With most of the session time devoted to discussion and interaction among peers on questions surrounding the adoption of open source software, participants will take away a deeper understanding of topics each institution should consider when looking at open source software. These findings, along with that of similar sessions around the country, will inform the creation and expansion of the free decision support tools being developed by LYRASIS.<br />
<br />
== Letting in the light: using Solr as an external search component ==<br />
<br />
* Jay Luker, IT Specialist, ADS (jluker at cfa dot harvard dot edu)<br />
* Benoit Thiell, ADS (bthiell at cfa dot harvard dot edu)<br />
<br />
It’s well-established that [http://lucene.apache.org/solr/ Solr] provides an excellent foundation for building a faceted search engine. But what if your application’s foundation has already been constructed? How do you add Solr as a federated, fulltext search component to an existing system that already provides a full set of well-crafted scoring and ranking mechanisms?<br />
<br />
This talk will describe a work-in-progress project at the [http://adswww.harvard.edu/ Smithsonian/NASA Astrophysics Data System] to migrate its aging search platform to [http://invenio-software.org/ Invenio], an open-source institutional repository and digital library system originally developed at CERN, while at the same time incorporating Solr as an external component for both faceting and fulltext search.<br />
<br />
In this presentation we'll start with a short introduction of Invenio and then move on to the good stuff: an in-depth exploration of our use of Solr. We'll explain the challenges that we faced, what we learned about some particular Solr internals, interesting paths we chose not to follow, and the solutions we finally developed, including the creation of custom Solr request handlers and query parser classes.<br />
<br />
This presentation will be quite technical and will show a measure of horrible Java code. Benoit will probably run away during that part.<br />
<br />
== Working with DuraCloud: How to preserve your data in the cloud ==<br />
<br />
* Bill Branan, DuraSpace, bbranan at duraspace dot org<br />
* Andrew Woods, DuraSpace, awoods at duraspace dot org<br />
<br />
Ever expanding digital collections have become the norm in academic libraries. As the size of collections grow, the need for simple-to-deploy yet powerful preservation strategies becomes increasingly important. The [http://duracloud.org DuraCloud] project, a cloud-hosted service for data management and preservation, is committed to bringing the availability and elasticity of the cloud to bear on the issue of digital preservation. This session will discuss the APIs and tools which can be used to communicate and integrate with the DuraCloud platform, providing an immediate connection to scalable storage available from multiple cloud storage providers, configurable services which can be run over your content out-of-the-box, and a development platform which can serve as the basis for ongoing data mining and analysis.<br />
<br />
== Visualizing Library Data ==<br />
<br />
* Karen Coombs, OCLC, coombsk at oclc dot org<br />
<br />
Visualizations can be powerful tools to give context to library users<br />
and to provide a clear picture for data-driven decision-making in<br />
libraries. Map mashups, tag clouds and timelines can be used to show<br />
information to users in new ways and help them locate materials to meet<br />
their needs. QR codes can help link users to materials that libraries<br />
have in their collections. Charts and graphs can be used to help analyze<br />
library collections (holdings) and compare them to other libraries. This<br />
session will show prototypes which combine tools like Google Chart API,<br />
Protovis and Simile Widgets with data from WorldCat, WorldCat Registry,<br />
Classify, Terminology Services, and Dewey.info to create vivid<br />
illustrations in library user interfaces and administration tools.<br />
<br />
== Kuali OLE: Architecture for Diverse and Linked Data ==<br />
<br />
* Tim McGeary, Lehigh University, Kuali OLE Functional Council, tim dot mcgeary at lehigh dot edu<br />
* Brad Skiles, Project Manager, Kuali OLE, Indiana University, bradskil at indiana dot edu<br />
<br />
With programming scheduled to be begin in January 2011 on the Kuali Open Library Environment (OLE), the Kuali OLE Functional Council is developing the requirements for an architecture for diverse data sets and linked data. With no frontrunner for one bibliographic data standard, and local requirements on what data will be accompanying or linked to the main record store, Kuali OLE needs to build a flexible environment for records management and access.<br />
<br />
We will present the concepts of our planned architecture, a multi-repository framework, using a document repository, a semantic repository, and a relational repository, brokered on top of the enterprise service bus of Kuali Rice. As a community source project, this is an opportunity for the Kuali OLE partners to present our plans for discussion with the community, and we look forward to feedback, questions, and comments. <br />
<br />
<br />
[[Category:Code4Lib2011]]</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=2011talks_Submissions&diff=62692011talks Submissions2010-11-10T16:53:52Z<p>Timmcgeary: /* Kuali OLE: Architecture for Diverse and Linked Data */</p>
<hr />
<div>Deadline for talk submission is ''Saturday, November 13''. See [http://www.mail-archive.com/code4lib@listserv.nd.edu/msg08878.html this mailing list post for more details], or the general [http://code4lib.org/conference/2011 Code4Lib 2011] page.<br />
<br />
See the [http://wiki.code4lib.org/index.php/2011talkscall_Call_for_Submissions Call for Submissions] for guidelines on appropriate topic talks and the criteria on which submissions are evaluated.<br />
<br />
Please follow the formatting guidelines:<br />
<br />
<pre><br />
== Talk Title: ==<br />
<br />
* Speaker's name, affiliation, and email address<br />
* Second speaker's name, affiliation, email address, if second speaker<br />
<br />
Abstract of no more than 500 words.<br />
</pre><br />
<br />
== How "great" are the Great Books? ==<br />
<br />
* Eric Lease Morgan, University of Notre Dame (emorgan at nd.edu)<br />
<br />
In the 1960s a set of books called the Great Books of the Western World was published. It was supposed to represent the best of Western literature and enable the reader to further their liberal arts education. Sixty volumes in all, it included works by Plato, Aristotle, Shakespeare, Milton, Galileo, Kepler, Melville, Darwin, etc. These great books were selected based on the way they discussed a set of 102 "great ideas" such as art, astronomy, beauty, evil, evolution, mind, nature, poetry, revolution, science, will, wisdom, etc. How "great" are these books, and how "great" are the ideas expressed in them?<br />
<br />
Given full text versions of these books it is almost trivial to use the "great ideas" as input and apply relevancy ranking algorithms against the texts thus creating a sort of score -- a "Great Ideas Coefficient". Term Frequency/Inverse Document Frequency (TFIDF) is a well-established algorithm for computing just this sort of thing:<br />
<br />
relevancy = ( c / t ) * log( d / f ) where:<br />
<br />
* c = number of times a given word appears in a document<br />
* t = total number of words in a document<br />
* d = total number of documents in a corpus<br />
* f = total number of documents containing a given word<br />
<br />
Thus, to calculate our Great Ideas Coefficient I sum the relevancy score for each "great idea" for each "great book". Plato's Republic might have a cumulative score of 525 while Aristotle's On The History Of Animals might have a cumulative score of 251. Books with a larger Coefficient could be considered greater. Given such a score a person could measure a book's "greatness". We could then compare the score to the scores of other books. Which book is the "greatest"? We could compare the score to other measurable things such as book's length or date to see if there were correlations. Are "great books" longer or shorter than others? Do longer books contain more "great ideas"? Are there other books that were not included in the set that maybe should have been included?<br />
<br />
The first part of this talk describes the different steps involved in the text pre-processing to calculate an accurate TFIDF value for each item of the corpus. The results and statistical analysis are discussed in the second part. Finally I will outline the remaining work such as refining the analysis and extending the current quantitative process to a web implementation.<br />
<br />
== UNR BookFinder: Leveraging Google Books to Move Beyond Catalog Search ==<br />
* Will Kurt, University of Nevada, Reno, (wkurt at unr.edu)<br />
Google Books is a great tool, but it lacks an easy method allowing users to access the items they find through their library. The UNR BookFinder is a mashup of the Google Books and WorldCat APIs (and some ugly hacks) which allows users to search for items with the power of Google’s fulltext search while eliminating the need to search all of the library’s various resources to find an item. The UNR BookFinder automatically searches the catalog and consortial ILL for the item, if these fail an ILLiad request form as automatically filled out. The end result is that the user can explore an universe of books and access them as fast as possible through the university library. A video of the alpha version can be found [http://www.youtube.com/watch?v=qaqcUSTtdVk here].<br />
<br />
== Moving a large multi-tiered search architecture from dedicated hosts to the cloud ==<br />
* Peter Ciuffetti, Senior Software Engineer, Credo Reference Ltd. (pete at credoreference.com)<br />
So you want to move a large production search service from dedicated hosts to the cloud? The flexibility is enticing, the costs are attractive, the geek cred is undeniable. Our cloud adventure came with many undocumented surprises ranging from mysterious server behavior to sales engineers suggesting that 'maybe the cloud isn't for you'. We eventually made it all work and our production service is now on the cloud. This talk will cover what the cloud product FAQs don't say, what their tech support doesn't know (or won't say) and mistakes you can avoid by talking to the guys with the arrows in their backs.<br />
<br />
== VuFind Beyond MARC: Discovering Everything Else ==<br />
* Demian Katz, Library Technology Development Specialist, Villanova University (demian dot katz at villanova dot edu)<br />
The VuFind[http://vufind.org] discovery layer has been providing a user-friendly interface to MARC records for several years now. However, library data consists of more than just MARC records, and VuFind has grown to accommodate just about anything you can throw at it. This presentation will examine the new workflows and tools that enable discovery of non-MARC resources and some of the non-traditional applications of VuFind that they make possible. Technologies covered will include OAI-PMH, XSLT, Aperture, Solr and, of course, VuFind itself.<br />
<br />
== Linked data apps for medical professionals ==<br />
* Rurik Thomas Greenall, NTNU Library, (rurik dot greenall at ub dot ntnu dot no)<br />
The promise of linked data for libraries has yet to be realized, as a demonstration of the power of RDF, HTTP-URIs and SPARQL, NTNU Library together with the Norwegian Electronic Health Library produced a linked data representation of MeSH and created a small translation app that can be used to help health professionals identify the right term and apply it in their database searches. This talk presents the simple ways in which the core technologies and concepts in linked data provide a solid, time-saving way of developing usable applications.<br />
<br />
== fiwalk With Me: Building Emergent Pre-Ingest Workflows for Digital Archival Records using Open Source Forensic Software ==<br />
* Mark A. Matienzo, Manuscripts and Archives, Yale University Library (mark at matienzo dot org)<br />
Many of the complications of born-digital records involve preparing them for transfer into a storage or preservation environment. Digital evidence of any kind is easily susceptible to unintentional and intentional modification. This presentation will describe the use of open source forensic software in pre-ingest workflows for digital archives. Digital archivists and other digital curation practitioners can develop emergent processes to prepare records for ingest and transfer using a combination of relatively simple tools. The granularity and simplicity of these tools and procedures provides the possibility for their smooth integration into a digital curation environment built on micro-services.<br />
== Why (Code4) Libraries Exist ==<br />
* Eric Hellman, President, Gluejar, Inc. (eric at hellman dot net)<br />
Libraries have historically delivered value to society by facilitating the sharing of books. The library "brand" is built around the building and exploitation of their collections. These collections have been acquired and owned. As ebook readers become the preferred consumption platform for books, libraries are beginning to come to terms with the fact that they don't own their digital collections, and can't share books as they'd like to. Yet libraries continue to be valuable in many ways. In this transitional period, only one thing can save libraries from irrelevance and dissipation: Code.<br />
== The Story of TILE: Making Modular & Reusable Tools ==<br />
* Doug Reside, MITH, University of Maryland (dougreside at gmail dot com)<br />
<br />
The Text Image Linking Environment (TILE) is a collaborative project between the Maryland Institute for Technology in the Humanities (MITH), the Digital Library Program at Indiana University, and the School of Library and Information Science at Indiana University Bloomington. Since May 2009, the TILE project team has been developing through NEH Research & Development funding a web-based, modular, image markup tool for both semi-automated linking between encoded text and image of text, and image annotation. The software will be complete and ready for release in June 2011. <br />
<br />
The basic functionality of TILE is to create links between images and text that relates to that image – either annotations or transcriptions. We have paid particular attention to linking between image of text and transcription of text. These links may be made manually, but the project also includes an algorithm, written in JavaScript, for recognizing text within an image and automatically associating the coordinates with a Unicode transcription. Additionally, the tool can import and export transcriptions and links from and to a variety of metadata formats (TEI, METS, OWL) and will provide an API for developers to write mappings for additional formats. Of course, this functionality is immediately useful to a relatively limited set of editors of digital materials, but we have made modularity and extensibility primary goals of the project.<br />
<br />
Many members of the TILE development team are also members of the Open Annotation Collaboration (OAC), and have therefore attempted to develop TILE’s annotation features to be OAC compliant. Like OAC, TILE assumes that the text and the images to be linked may exist at separate and completely unconnected servers. When a user starts the TILE tool for the first time, she is prompted to supply a URI to a TILE compliant JSON file. <br />
<br />
TILE’s JSON is simple and thoroughly documented, and we provide several translators to map common existing metadata formats to the format. We have already created a PHP script that will generate TILE JSON from a TEI P5 document and are currently working to do the same for the METS files used in the Indiana University’s METS navigator tool. <br />
<br />
Additionally, TILE provides a modular exporting tool that allows users to run the work they’ve done in TILE through an external translator and then download the result to the client computer. For example, a user may import a set of images and transcripts from a METS file at the Library of Congress, use TILE to link images and text, and then export the result as a TEI file. The TEI file may then be reimported to TILE at a later data to further edit or convert the file.<br />
<br />
At Code4Lib, we will demonstrate the functionality of TILE and display a poster and provide handouts that describe the thinking behind TILE, how it is intended to be used, and details on how TILE is built and functions.<br />
<br />
== We Don’t Server Their Kind : Managing E-resources with Flat-File Databases ==<br />
* Junior Tidal, Multimedia and Web Services Librarian, New York City College of Technology, CUNY (jtidal at citytech dot cuny dot edu)<br />
Managing E-resources can be a daunting challenge. URLs, database names, and even vendors can change, go down, or simply cease to exist. My proposal involves the use of a PHP-based, flat-file database driven web tool for database management. The design of this program was to fulfill two needs: ease of use for librarians with a lack of programming experience and to meet the security and technical restrictions placed by the college’s IT department. My presentation will explore the development of this tool, challenges within its development, and future improvements. PHP code and the flat-file database will also be explained and provided to attendees. For a working demonstration feel free to visit the New York City College of Technology’s A-Z database [http://library.citytech.cuny.edu/research/AToZ/index.php page] or the subject database [http://library.citytech.cuny.edu/research/subject/index.php page].<br />
<br />
== Drupal 7 as a Rapid Application Development Tool ==<br />
<br />
* Cary Gordon, President, The Cherry Hill Company & Board Member, The Drupal Association (cgordon at chillco dawt com)<br />
Five years ago, I discovered that the Drupal CMS had a programming framework disguised as an API, and learned that I could use it to solve problems.<br />
<br />
Drupal 7 builds on that to provide a powerful toolset for interfacing with, manipulating and presenting data. It empowers tool-builders by providing a minimal install option, along with a more powerful installation profile system makes it easier for developers to package and distribute their applications.<br />
<br />
== Helping Open Source Succeed ==<br />
<br />
* [[User:DataGazetteer|Peter Murray]], LYRASIS, [mailto:Peter.Murray@lyrasis.org Peter.Murray@lyrasis.org] <br />
* Tim Daniels, LYRASIS, [mailto:Tim.Daniels@lyrasis.org Tim.Daniels@lyrasis.org]<br />
<br />
Deciding if open source is an option for your institution, or what open source software matches your institution’s needs and capabilities, is a complex decision. LYRASIS is developing a new area of focus to assist libraries with decision tools and an open source software registry. We want to learn from the creators of open source software what questions institutions have when considering the adoption of open source software and what information you would like to see in a registry that compares various open source tools. A summary of topics discussed in this session will be openly published as part of LYRASIS’ program development plans and decision support resources.<br />
<br />
The mission of the new and emerging LYRASIS Technology Services area is to serve members and the broader library community as a provider of expertise and capacity in open source based technology solutions. We think that viable roles for an organization supporting open source software are to: a) Increase understanding of open source technology within the library community, including value, benefits, risks, and costs; b) Assist in decision-making by providing resources to help libraries evaluate open source technologies, institutional readiness, and capacity for adoption; c) Support adoption and use of open source technologies and systems within libraries and consortia; d) Foster integration of open source software tools to expand the ability of existing programs to meet a range of library user needs; e) Develop and test new open source software programs, and contribute to the development of existing programs; f) Support long-term sustainability of viable, library-based open source software and systems. We recognize that these roles exist to some extent on a continuum, with latter services related to development and sustainability building on the knowledge and experience gained through deployment of existing open source systems. In turn, effective adoption and use depends on understanding open source systems and having resources to assist in decision-making and implementation.<br />
<br />
With open source software in the “innovator” and “early adopter” stages in the library community, we intend to focus its initial efforts on roles A-D in the above list: increased understanding, decision-support, and effective adoption and integration of existing library-focused open source systems. This session is focused on the decision-support services area of activity.<br />
<br />
The impact of this session is expected to be far reaching, if initially subtle. With most of the session time devoted to discussion and interaction among peers on questions surrounding the adoption of open source software, participants will take away a deeper understanding of topics each institution should consider when looking at open source software. These findings, along with that of similar sessions around the country, will inform the creation and expansion of the free decision support tools being developed by LYRASIS.<br />
<br />
== Letting in the light: using Solr as an external search component ==<br />
<br />
* Jay Luker, IT Specialist, ADS (jluker at cfa dot harvard dot edu)<br />
* Benoit Thiell, ADS (bthiell at cfa dot harvard dot edu)<br />
<br />
It’s well-established that [http://lucene.apache.org/solr/ Solr] provides an excellent foundation for building a faceted search engine. But what if your application’s foundation has already been constructed? How do you add Solr as a federated, fulltext search component to an existing system that already provides a full set of well-crafted scoring and ranking mechanisms?<br />
<br />
This talk will describe a work-in-progress project at the [http://adswww.harvard.edu/ Smithsonian/NASA Astrophysics Data System] to migrate its aging search platform to [http://invenio-software.org/ Invenio], an open-source institutional repository and digital library system originally developed at CERN, while at the same time incorporating Solr as an external component for both faceting and fulltext search.<br />
<br />
In this presentation we'll start with a short introduction of Invenio and then move on to the good stuff: an in-depth exploration of our use of Solr. We'll explain the challenges that we faced, what we learned about some particular Solr internals, interesting paths we chose not to follow, and the solutions we finally developed, including the creation of custom Solr request handlers and query parser classes.<br />
<br />
This presentation will be quite technical and will show a measure of horrible Java code. Benoit will probably run away during that part.<br />
<br />
== Working with DuraCloud: How to preserve your data in the cloud ==<br />
<br />
* Bill Branan, DuraSpace, bbranan at duraspace dot org<br />
* Andrew Woods, DuraSpace, awoods at duraspace dot org<br />
<br />
Ever expanding digital collections have become the norm in academic libraries. As the size of collections grow, the need for simple-to-deploy yet powerful preservation strategies becomes increasingly important. The [http://duracloud.org DuraCloud] project, a cloud-hosted service for data management and preservation, is committed to bringing the availability and elasticity of the cloud to bear on the issue of digital preservation. This session will discuss the APIs and tools which can be used to communicate and integrate with the DuraCloud platform, providing an immediate connection to scalable storage available from multiple cloud storage providers, configurable services which can be run over your content out-of-the-box, and a development platform which can serve as the basis for ongoing data mining and analysis.<br />
<br />
== Visualizing Library Data ==<br />
<br />
* Karen Coombs, OCLC, coombsk at oclc dot org<br />
<br />
Visualizations can be powerful tools to give context to library users<br />
and to provide a clear picture for data-driven decision-making in<br />
libraries. Map mashups, tag clouds and timelines can be used to show<br />
information to users in new ways and help them locate materials to meet<br />
their needs. QR codes can help link users to materials that libraries<br />
have in their collections. Charts and graphs can be used to help analyze<br />
library collections (holdings) and compare them to other libraries. This<br />
session will show prototypes which combine tools like Google Chart API,<br />
Protovis and Simile Widgets with data from WorldCat, WorldCat Registry,<br />
Classify, Terminology Services, and Dewey.info to create vivid<br />
illustrations in library user interfaces and administration tools.<br />
<br />
<br />
== Kuali OLE: Architecture for Diverse and Linked Data ==<br />
<br />
* Tim McGeary, Lehigh University, Kuali OLE Functional Council, tim dot mcgeary at lehigh dot edu<br />
* Brad Skiles, Project Manager, Kuali OLE, Indiana University, bradskil at indiana dot edu<br />
<br />
With programming scheduled to be begin in January 2011 on the Kuali Open Library Environment (OLE), the Kuali OLE Functional Council is developing the requirements for an architecture for diverse data sets and linked data. With no frontrunner for one bibliographic data standard, and local requirements on what data will be accompanying or linked to the main record store, Kuali OLE needs to build a flexible environment for records management and access.<br />
<br />
We will present the concepts of our planned architecture, a multi-repository framework, using a document repository, a semantic repository, and a relational repository, brokered on top of the enterprise service bus of Kuali Rice. As a community source project, this is an opportunity for the Kuali OLE partners to present our plans for discussion with the community, and we look forward to feedback, questions, and comments. <br />
<br />
<br />
[[Category:Code4Lib2011]]</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=2011talks_Submissions&diff=62682011talks Submissions2010-11-10T16:53:28Z<p>Timmcgeary: </p>
<hr />
<div>Deadline for talk submission is ''Saturday, November 13''. See [http://www.mail-archive.com/code4lib@listserv.nd.edu/msg08878.html this mailing list post for more details], or the general [http://code4lib.org/conference/2011 Code4Lib 2011] page.<br />
<br />
See the [http://wiki.code4lib.org/index.php/2011talkscall_Call_for_Submissions Call for Submissions] for guidelines on appropriate topic talks and the criteria on which submissions are evaluated.<br />
<br />
Please follow the formatting guidelines:<br />
<br />
<pre><br />
== Talk Title: ==<br />
<br />
* Speaker's name, affiliation, and email address<br />
* Second speaker's name, affiliation, email address, if second speaker<br />
<br />
Abstract of no more than 500 words.<br />
</pre><br />
<br />
== How "great" are the Great Books? ==<br />
<br />
* Eric Lease Morgan, University of Notre Dame (emorgan at nd.edu)<br />
<br />
In the 1960s a set of books called the Great Books of the Western World was published. It was supposed to represent the best of Western literature and enable the reader to further their liberal arts education. Sixty volumes in all, it included works by Plato, Aristotle, Shakespeare, Milton, Galileo, Kepler, Melville, Darwin, etc. These great books were selected based on the way they discussed a set of 102 "great ideas" such as art, astronomy, beauty, evil, evolution, mind, nature, poetry, revolution, science, will, wisdom, etc. How "great" are these books, and how "great" are the ideas expressed in them?<br />
<br />
Given full text versions of these books it is almost trivial to use the "great ideas" as input and apply relevancy ranking algorithms against the texts thus creating a sort of score -- a "Great Ideas Coefficient". Term Frequency/Inverse Document Frequency (TFIDF) is a well-established algorithm for computing just this sort of thing:<br />
<br />
relevancy = ( c / t ) * log( d / f ) where:<br />
<br />
* c = number of times a given word appears in a document<br />
* t = total number of words in a document<br />
* d = total number of documents in a corpus<br />
* f = total number of documents containing a given word<br />
<br />
Thus, to calculate our Great Ideas Coefficient I sum the relevancy score for each "great idea" for each "great book". Plato's Republic might have a cumulative score of 525 while Aristotle's On The History Of Animals might have a cumulative score of 251. Books with a larger Coefficient could be considered greater. Given such a score a person could measure a book's "greatness". We could then compare the score to the scores of other books. Which book is the "greatest"? We could compare the score to other measurable things such as book's length or date to see if there were correlations. Are "great books" longer or shorter than others? Do longer books contain more "great ideas"? Are there other books that were not included in the set that maybe should have been included?<br />
<br />
The first part of this talk describes the different steps involved in the text pre-processing to calculate an accurate TFIDF value for each item of the corpus. The results and statistical analysis are discussed in the second part. Finally I will outline the remaining work such as refining the analysis and extending the current quantitative process to a web implementation.<br />
<br />
== UNR BookFinder: Leveraging Google Books to Move Beyond Catalog Search ==<br />
* Will Kurt, University of Nevada, Reno, (wkurt at unr.edu)<br />
Google Books is a great tool, but it lacks an easy method allowing users to access the items they find through their library. The UNR BookFinder is a mashup of the Google Books and WorldCat APIs (and some ugly hacks) which allows users to search for items with the power of Google’s fulltext search while eliminating the need to search all of the library’s various resources to find an item. The UNR BookFinder automatically searches the catalog and consortial ILL for the item, if these fail an ILLiad request form as automatically filled out. The end result is that the user can explore an universe of books and access them as fast as possible through the university library. A video of the alpha version can be found [http://www.youtube.com/watch?v=qaqcUSTtdVk here].<br />
<br />
== Moving a large multi-tiered search architecture from dedicated hosts to the cloud ==<br />
* Peter Ciuffetti, Senior Software Engineer, Credo Reference Ltd. (pete at credoreference.com)<br />
So you want to move a large production search service from dedicated hosts to the cloud? The flexibility is enticing, the costs are attractive, the geek cred is undeniable. Our cloud adventure came with many undocumented surprises ranging from mysterious server behavior to sales engineers suggesting that 'maybe the cloud isn't for you'. We eventually made it all work and our production service is now on the cloud. This talk will cover what the cloud product FAQs don't say, what their tech support doesn't know (or won't say) and mistakes you can avoid by talking to the guys with the arrows in their backs.<br />
<br />
== VuFind Beyond MARC: Discovering Everything Else ==<br />
* Demian Katz, Library Technology Development Specialist, Villanova University (demian dot katz at villanova dot edu)<br />
The VuFind[http://vufind.org] discovery layer has been providing a user-friendly interface to MARC records for several years now. However, library data consists of more than just MARC records, and VuFind has grown to accommodate just about anything you can throw at it. This presentation will examine the new workflows and tools that enable discovery of non-MARC resources and some of the non-traditional applications of VuFind that they make possible. Technologies covered will include OAI-PMH, XSLT, Aperture, Solr and, of course, VuFind itself.<br />
<br />
== Linked data apps for medical professionals ==<br />
* Rurik Thomas Greenall, NTNU Library, (rurik dot greenall at ub dot ntnu dot no)<br />
The promise of linked data for libraries has yet to be realized, as a demonstration of the power of RDF, HTTP-URIs and SPARQL, NTNU Library together with the Norwegian Electronic Health Library produced a linked data representation of MeSH and created a small translation app that can be used to help health professionals identify the right term and apply it in their database searches. This talk presents the simple ways in which the core technologies and concepts in linked data provide a solid, time-saving way of developing usable applications.<br />
<br />
== fiwalk With Me: Building Emergent Pre-Ingest Workflows for Digital Archival Records using Open Source Forensic Software ==<br />
* Mark A. Matienzo, Manuscripts and Archives, Yale University Library (mark at matienzo dot org)<br />
Many of the complications of born-digital records involve preparing them for transfer into a storage or preservation environment. Digital evidence of any kind is easily susceptible to unintentional and intentional modification. This presentation will describe the use of open source forensic software in pre-ingest workflows for digital archives. Digital archivists and other digital curation practitioners can develop emergent processes to prepare records for ingest and transfer using a combination of relatively simple tools. The granularity and simplicity of these tools and procedures provides the possibility for their smooth integration into a digital curation environment built on micro-services.<br />
== Why (Code4) Libraries Exist ==<br />
* Eric Hellman, President, Gluejar, Inc. (eric at hellman dot net)<br />
Libraries have historically delivered value to society by facilitating the sharing of books. The library "brand" is built around the building and exploitation of their collections. These collections have been acquired and owned. As ebook readers become the preferred consumption platform for books, libraries are beginning to come to terms with the fact that they don't own their digital collections, and can't share books as they'd like to. Yet libraries continue to be valuable in many ways. In this transitional period, only one thing can save libraries from irrelevance and dissipation: Code.<br />
== The Story of TILE: Making Modular & Reusable Tools ==<br />
* Doug Reside, MITH, University of Maryland (dougreside at gmail dot com)<br />
<br />
The Text Image Linking Environment (TILE) is a collaborative project between the Maryland Institute for Technology in the Humanities (MITH), the Digital Library Program at Indiana University, and the School of Library and Information Science at Indiana University Bloomington. Since May 2009, the TILE project team has been developing through NEH Research & Development funding a web-based, modular, image markup tool for both semi-automated linking between encoded text and image of text, and image annotation. The software will be complete and ready for release in June 2011. <br />
<br />
The basic functionality of TILE is to create links between images and text that relates to that image – either annotations or transcriptions. We have paid particular attention to linking between image of text and transcription of text. These links may be made manually, but the project also includes an algorithm, written in JavaScript, for recognizing text within an image and automatically associating the coordinates with a Unicode transcription. Additionally, the tool can import and export transcriptions and links from and to a variety of metadata formats (TEI, METS, OWL) and will provide an API for developers to write mappings for additional formats. Of course, this functionality is immediately useful to a relatively limited set of editors of digital materials, but we have made modularity and extensibility primary goals of the project.<br />
<br />
Many members of the TILE development team are also members of the Open Annotation Collaboration (OAC), and have therefore attempted to develop TILE’s annotation features to be OAC compliant. Like OAC, TILE assumes that the text and the images to be linked may exist at separate and completely unconnected servers. When a user starts the TILE tool for the first time, she is prompted to supply a URI to a TILE compliant JSON file. <br />
<br />
TILE’s JSON is simple and thoroughly documented, and we provide several translators to map common existing metadata formats to the format. We have already created a PHP script that will generate TILE JSON from a TEI P5 document and are currently working to do the same for the METS files used in the Indiana University’s METS navigator tool. <br />
<br />
Additionally, TILE provides a modular exporting tool that allows users to run the work they’ve done in TILE through an external translator and then download the result to the client computer. For example, a user may import a set of images and transcripts from a METS file at the Library of Congress, use TILE to link images and text, and then export the result as a TEI file. The TEI file may then be reimported to TILE at a later data to further edit or convert the file.<br />
<br />
At Code4Lib, we will demonstrate the functionality of TILE and display a poster and provide handouts that describe the thinking behind TILE, how it is intended to be used, and details on how TILE is built and functions.<br />
<br />
== We Don’t Server Their Kind : Managing E-resources with Flat-File Databases ==<br />
* Junior Tidal, Multimedia and Web Services Librarian, New York City College of Technology, CUNY (jtidal at citytech dot cuny dot edu)<br />
Managing E-resources can be a daunting challenge. URLs, database names, and even vendors can change, go down, or simply cease to exist. My proposal involves the use of a PHP-based, flat-file database driven web tool for database management. The design of this program was to fulfill two needs: ease of use for librarians with a lack of programming experience and to meet the security and technical restrictions placed by the college’s IT department. My presentation will explore the development of this tool, challenges within its development, and future improvements. PHP code and the flat-file database will also be explained and provided to attendees. For a working demonstration feel free to visit the New York City College of Technology’s A-Z database [http://library.citytech.cuny.edu/research/AToZ/index.php page] or the subject database [http://library.citytech.cuny.edu/research/subject/index.php page].<br />
<br />
== Drupal 7 as a Rapid Application Development Tool ==<br />
<br />
* Cary Gordon, President, The Cherry Hill Company & Board Member, The Drupal Association (cgordon at chillco dawt com)<br />
Five years ago, I discovered that the Drupal CMS had a programming framework disguised as an API, and learned that I could use it to solve problems.<br />
<br />
Drupal 7 builds on that to provide a powerful toolset for interfacing with, manipulating and presenting data. It empowers tool-builders by providing a minimal install option, along with a more powerful installation profile system makes it easier for developers to package and distribute their applications.<br />
<br />
== Helping Open Source Succeed ==<br />
<br />
* [[User:DataGazetteer|Peter Murray]], LYRASIS, [mailto:Peter.Murray@lyrasis.org Peter.Murray@lyrasis.org] <br />
* Tim Daniels, LYRASIS, [mailto:Tim.Daniels@lyrasis.org Tim.Daniels@lyrasis.org]<br />
<br />
Deciding if open source is an option for your institution, or what open source software matches your institution’s needs and capabilities, is a complex decision. LYRASIS is developing a new area of focus to assist libraries with decision tools and an open source software registry. We want to learn from the creators of open source software what questions institutions have when considering the adoption of open source software and what information you would like to see in a registry that compares various open source tools. A summary of topics discussed in this session will be openly published as part of LYRASIS’ program development plans and decision support resources.<br />
<br />
The mission of the new and emerging LYRASIS Technology Services area is to serve members and the broader library community as a provider of expertise and capacity in open source based technology solutions. We think that viable roles for an organization supporting open source software are to: a) Increase understanding of open source technology within the library community, including value, benefits, risks, and costs; b) Assist in decision-making by providing resources to help libraries evaluate open source technologies, institutional readiness, and capacity for adoption; c) Support adoption and use of open source technologies and systems within libraries and consortia; d) Foster integration of open source software tools to expand the ability of existing programs to meet a range of library user needs; e) Develop and test new open source software programs, and contribute to the development of existing programs; f) Support long-term sustainability of viable, library-based open source software and systems. We recognize that these roles exist to some extent on a continuum, with latter services related to development and sustainability building on the knowledge and experience gained through deployment of existing open source systems. In turn, effective adoption and use depends on understanding open source systems and having resources to assist in decision-making and implementation.<br />
<br />
With open source software in the “innovator” and “early adopter” stages in the library community, we intend to focus its initial efforts on roles A-D in the above list: increased understanding, decision-support, and effective adoption and integration of existing library-focused open source systems. This session is focused on the decision-support services area of activity.<br />
<br />
The impact of this session is expected to be far reaching, if initially subtle. With most of the session time devoted to discussion and interaction among peers on questions surrounding the adoption of open source software, participants will take away a deeper understanding of topics each institution should consider when looking at open source software. These findings, along with that of similar sessions around the country, will inform the creation and expansion of the free decision support tools being developed by LYRASIS.<br />
<br />
== Letting in the light: using Solr as an external search component ==<br />
<br />
* Jay Luker, IT Specialist, ADS (jluker at cfa dot harvard dot edu)<br />
* Benoit Thiell, ADS (bthiell at cfa dot harvard dot edu)<br />
<br />
It’s well-established that [http://lucene.apache.org/solr/ Solr] provides an excellent foundation for building a faceted search engine. But what if your application’s foundation has already been constructed? How do you add Solr as a federated, fulltext search component to an existing system that already provides a full set of well-crafted scoring and ranking mechanisms?<br />
<br />
This talk will describe a work-in-progress project at the [http://adswww.harvard.edu/ Smithsonian/NASA Astrophysics Data System] to migrate its aging search platform to [http://invenio-software.org/ Invenio], an open-source institutional repository and digital library system originally developed at CERN, while at the same time incorporating Solr as an external component for both faceting and fulltext search.<br />
<br />
In this presentation we'll start with a short introduction of Invenio and then move on to the good stuff: an in-depth exploration of our use of Solr. We'll explain the challenges that we faced, what we learned about some particular Solr internals, interesting paths we chose not to follow, and the solutions we finally developed, including the creation of custom Solr request handlers and query parser classes.<br />
<br />
This presentation will be quite technical and will show a measure of horrible Java code. Benoit will probably run away during that part.<br />
<br />
== Working with DuraCloud: How to preserve your data in the cloud ==<br />
<br />
* Bill Branan, DuraSpace, bbranan at duraspace dot org<br />
* Andrew Woods, DuraSpace, awoods at duraspace dot org<br />
<br />
Ever expanding digital collections have become the norm in academic libraries. As the size of collections grow, the need for simple-to-deploy yet powerful preservation strategies becomes increasingly important. The [http://duracloud.org DuraCloud] project, a cloud-hosted service for data management and preservation, is committed to bringing the availability and elasticity of the cloud to bear on the issue of digital preservation. This session will discuss the APIs and tools which can be used to communicate and integrate with the DuraCloud platform, providing an immediate connection to scalable storage available from multiple cloud storage providers, configurable services which can be run over your content out-of-the-box, and a development platform which can serve as the basis for ongoing data mining and analysis.<br />
<br />
== Visualizing Library Data ==<br />
<br />
* Karen Coombs, OCLC, coombsk at oclc dot org<br />
<br />
Visualizations can be powerful tools to give context to library users<br />
and to provide a clear picture for data-driven decision-making in<br />
libraries. Map mashups, tag clouds and timelines can be used to show<br />
information to users in new ways and help them locate materials to meet<br />
their needs. QR codes can help link users to materials that libraries<br />
have in their collections. Charts and graphs can be used to help analyze<br />
library collections (holdings) and compare them to other libraries. This<br />
session will show prototypes which combine tools like Google Chart API,<br />
Protovis and Simile Widgets with data from WorldCat, WorldCat Registry,<br />
Classify, Terminology Services, and Dewey.info to create vivid<br />
illustrations in library user interfaces and administration tools.<br />
<br />
<br />
== Kuali OLE: Architecture for Diverse and Linked Data ==<br />
<br />
* Tim McGeary, Lehigh University, Kuali OLE Functional Council, tim dot mcgeary at lehigh dot edu<br />
* Brad Skiles, Project Manager, Kuali OLE, Indiana University, bradskil at indiana dot edu<br />
<br />
With programming scheduled to be begin in January 2011 on the Kuali Open Library Environment (OLE), the Kuali OLE Functional Council is developing the requirements for an architecture for diverse data sets and linked data. With no frontrunner for one bibliographic data standard, and local requirements on what data will be accompanying or linked to the main record store, Kuali OLE needs to build a flexible environment for records management and access.<br />
<br />
We will present the concepts of our planned architecture, a multi-repository framework, using a document repository, a semantic repository, and a relational repository, brokered on top of the enterprise service bus of Kuali Rice. <br />
<br />
As a community source project, this is an opportunity for the Kuali OLE partners to present our plans for discussion with the community, and we look forward to feedback, questions, and comments. <br />
<br />
<br />
[[Category:Code4Lib2011]]</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=CSE_Reference_Style&diff=6070CSE Reference Style2010-08-10T14:49:53Z<p>Timmcgeary: </p>
<hr />
<div>==Book==<br />
<br />
Bibliography:<br />
McCormac JS, Kennedy G. 2004. Birds of Ohio. Auburn (WA): Lone Pine. p. 77-78.<br />
<br />
In-Text:<br />
(McCormac and Kennedy 2004)<br />
<br />
==Book Chapter==<br />
<br />
Bibliography:<br />
McDaniel TK, Valdivia RH. 2005. New tools for virulence gene discovery. In: Cossart P, Boquet P, Normark S, Rappuoli R, editors. Cellular microbiology. 2nd ed. Washington (DC): ASM Press. p. 473-488.<br />
<br />
In-Text:<br />
(McDaniel and Valdivia 2005)<br />
<br />
==Electronic Book==<br />
<br />
Bibliography:<br />
Rollin, BE. The unheeded cry: animal consciousness, animal pain, and science [Internet]. Ames (IA): The Iowa State University Press; 1998 [cited 2007 August 27]. Available from: http://www.netlibrary.com<br />
<br />
In-Text:<br />
(Rollin 1998)<br />
<br />
==Journal Article (Print)==<br />
<br />
Bibliography:<br />
Meise CJ, Johnson DL, Stehlik LL, Manderson J, Shaheen P. 2003. Growth rates of juvenile Winter Flounder under varying environmental conditions. Trans Am Fish Soc 132(2):225-345.<br />
<br />
In-Text:<br />
(Meise et al. 2003)<br />
<br />
==Electronic Article (From OpenURL link)==<br />
<br />
Bibliography:<br />
Parmentier H, Golding S, Ashworth M, Rowlands G. 2004. Community pharmacy treatment of minor ailments in refugees. Journal of Clinical Pharmacy and Therapeutics [Internet]. [cited 2007 Jul 24]; 29(5):465-469. Available from: http://journals.ohiolink.edu/ejc/pdf.cgi/Parmentier_H.pdf?issn=02694727&issue=v29i0005&article=465_cptomair<br />
<br />
In-Text:<br />
(Parmentier et al. 2004)<br />
<br />
==Electronic Article (From Publisher's Website)==<br />
<br />
Bibliography:<br />
Leng F, Amado L, McMacken R. 2004. Coupling DNA supercoiling to transcription in defined protein systems. Journal of Biological Chemistry [Internet]. [cited 2007 Jul 24];279(46):47564-47571. Available from: http://www.jbc.org/cgi/reprint/279/46/47564<br />
<br />
In-Text:<br />
(Leng et al. 2004)<br />
<br />
==Electronic Article (From Online-Only Journal)==<br />
<br />
Bibliography:<br />
Hong P, Wong W. 2005. GeneNotes: a novel information management software for biologists. BMC Bioinformatics [Internet]. [cited 2007 July 24]; 6:20. Available from: http://www.biomedcentral.com/1471-2105/6/20<br />
<br />
In-Text:<br />
(Hong and Wong 2005)<br />
<br />
==Electronic Encyclopedia Article (From Database)==<br />
<br />
Bibliography:<br />
Wang C. c2007. Stem Cells. In: AccessScience@McGraw-Hill. [Internet][Hightstown (NJ)]: McGraw-Hill Education; [cited 2007 Sept 10]. Available from: http://www.accessscience.com/content.aspx?id=800100<br />
<br />
In-Text:<br />
(Wang c2007)<br />
<br />
==Dissertation/Thesis==<br />
<br />
Bibliography:<br />
Dettmers JM. 1995. Assessing the trophic cascade in reservoirs: the role of an introduced predator [dissertation]. [Columbus (OH)]: Ohio State University. p. 7-14.<br />
<br />
In-Text:<br />
(Dettmers 1995)<br />
<br />
==Conference Paper==<br />
<br />
Bibliography:<br />
Clarke A, Crame JA. 2003. Importance of historical processes in global patterns of diversity. In: Blackburn TM, Gaston KJ, editors. Macroecology: concepts and consequences. Proceedings of the 43rd annual symposium of the British Ecological Society; 2002 Apr 17-19; Birmingham. Malden (MA): Blackwell. p. 130-152.<br />
<br />
In-Text:<br />
(Clarke and Crame 2003)<br />
<br />
==Conference Abstract==<br />
<br />
Bibliography:<br />
Swanson TA, Blair P, Madigan L. 2004. Reduction in medication errors through redesign of the medication use system [abstract]. In: American Society of Health-system Pharmacists 39th midyear meeting; 2004 Dec 5-9; Orlando. Bethesda (MD): American Society of Health-System Pharmacists. MCS-28.<br />
<br />
In-Text:<br />
(Swanson et al. 2004)<br />
<br />
==Technical Report==<br />
<br />
Bibliography:<br />
Ford PL, Fagerlund RA, Duszynski DW, Polechla PJ. 2004. Fleas and lice of mammals in New Mexico. Fort Collins (CO): USDA Forest Service Rocky Mountain Research Station. General Technical Report No. RMRS-GTR-123.<br />
<br />
In-Text:<br />
(Ford et al. 2004)<br />
<br />
==Web Page (With No Author Listed)==<br />
<br />
Bibliography:<br />
Emerald Ash Borer (EAB) [Internet]. [updated 2007 Feb 27]. Columbus (OH): Ohio Department of Natural Resources, Division of Forestry; [cited 2007 Jul 24]. Available from: http://www.dnr.state.oh.us/forestry/health/eab.htm<br />
<br />
In-Text:<br />
(Emerald Ash Borer ... [updated 2007])<br />
<br />
==Notes==<br />
(Page adapted from The Ohio State University Libraries guide on reference styles http://library.osu.edu/help/research-strategies/)</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=CSE_Reference_Style&diff=6069CSE Reference Style2010-08-10T14:47:58Z<p>Timmcgeary: New page: ==Book== Bibliography: McCormac JS, Kennedy G. 2004. Birds of Ohio. Auburn (WA): Lone Pine. p. 77-78. In-Text: (McCormac and Kennedy 2004) ==Book Chapter== Bibliography: McDaniel TK, V...</p>
<hr />
<div>==Book==<br />
<br />
Bibliography:<br />
McCormac JS, Kennedy G. 2004. Birds of Ohio. Auburn (WA): Lone Pine. p. 77-78.<br />
<br />
In-Text:<br />
(McCormac and Kennedy 2004)<br />
<br />
==Book Chapter==<br />
<br />
Bibliography:<br />
McDaniel TK, Valdivia RH. 2005. New tools for virulence gene discovery. In: Cossart P, Boquet P, Normark S, Rappuoli R, editors. Cellular microbiology. 2nd ed. Washington (DC): ASM Press. p. 473-488.<br />
<br />
In-Text:<br />
(McDaniel and Valdivia 2005)<br />
<br />
==Electronic Book==<br />
<br />
Bibliography:<br />
Rollin, BE. The unheeded cry: animal consciousness, animal pain, and science [Internet]. Ames (IA): The Iowa State University Press; 1998 [cited 2007 August 27]. Available from: http://www.netlibrary.com<br />
<br />
In-Text:<br />
(Rollin 1998)<br />
<br />
==Journal Article (Print)==<br />
<br />
Bibliography:<br />
Meise CJ, Johnson DL, Stehlik LL, Manderson J, Shaheen P. 2003. Growth rates of juvenile Winter Flounder under varying environmental conditions. Trans Am Fish Soc 132(2):225-345.<br />
<br />
In-Text:<br />
(Meise et al. 2003)<br />
<br />
==Electronic Article (From OpenURL link)==<br />
<br />
Bibliography:<br />
Parmentier H, Golding S, Ashworth M, Rowlands G. 2004. Community pharmacy treatment of minor ailments in refugees. Journal of Clinical Pharmacy and Therapeutics [Internet]. [cited 2007 Jul 24]; 29(5):465-469. Available from: http://journals.ohiolink.edu/ejc/pdf.cgi/Parmentier_H.pdf?issn=02694727&issue=v29i0005&article=465_cptomair<br />
<br />
In-Text:<br />
(Parmentier et al. 2004)<br />
<br />
==Electronic Article (From Publisher's Website)==<br />
<br />
Bibliography:<br />
Leng F, Amado L, McMacken R. 2004. Coupling DNA supercoiling to transcription in defined protein systems. Journal of Biological Chemistry [Internet]. [cited 2007 Jul 24];279(46):47564-47571. Available from: http://www.jbc.org/cgi/reprint/279/46/47564<br />
<br />
In-Text:<br />
(Leng et al. 2004)<br />
<br />
==Electronic Article (From Online-Only Journal)==<br />
<br />
Bibliography:<br />
Hong P, Wong W. 2005. GeneNotes: a novel information management software for biologists. BMC Bioinformatics [Internet]. [cited 2007 July 24]; 6:20. Available from: http://www.biomedcentral.com/1471-2105/6/20<br />
<br />
In-Text:<br />
(Hong and Wong 2005)<br />
<br />
==Electronic Encyclopedia Article (From Database)==<br />
<br />
Bibliography:<br />
Wang C. c2007. Stem Cells. In: AccessScience@McGraw-Hill. [Internet][Hightstown (NJ)]: McGraw-Hill Education; [cited 2007 Sept 10]. Available from: http://www.accessscience.com/content.aspx?id=800100<br />
<br />
In-Text:<br />
(Wang c2007)<br />
<br />
==Dissertation/Thesis==<br />
<br />
Bibliography:<br />
Dettmers JM. 1995. Assessing the trophic cascade in reservoirs: the role of an introduced predator [dissertation]. [Columbus (OH)]: Ohio State University. p. 7-14.<br />
<br />
In-Text:<br />
(Dettmers 1995)<br />
<br />
==Conference Paper==<br />
<br />
Bibliography:<br />
Clarke A, Crame JA. 2003. Importance of historical processes in global patterns of diversity. In: Blackburn TM, Gaston KJ, editors. Macroecology: concepts and consequences. Proceedings of the 43rd annual symposium of the British Ecological Society; 2002 Apr 17-19; Birmingham. Malden (MA): Blackwell. p. 130-152.<br />
<br />
In-Text:<br />
(Clarke and Crame 2003)<br />
<br />
==Conference Abstract==<br />
<br />
Bibliography:<br />
Swanson TA, Blair P, Madigan L. 2004. Reduction in medication errors through redesign of the medication use system [abstract]. In: American Society of Health-system Pharmacists 39th midyear meeting; 2004 Dec 5-9; Orlando. Bethesda (MD): American Society of Health-System Pharmacists. MCS-28.<br />
<br />
In-Text:<br />
(Swanson et al. 2004)<br />
<br />
==Technical Report==<br />
<br />
Bibliography:<br />
Ford PL, Fagerlund RA, Duszynski DW, Polechla PJ. 2004. Fleas and lice of mammals in New Mexico. Fort Collins (CO): USDA Forest Service Rocky Mountain Research Station. General Technical Report No. RMRS-GTR-123.<br />
<br />
In-Text:<br />
(Ford et al. 2004)<br />
<br />
==Web Page (With No Author Listed)==<br />
<br />
Bibliography:<br />
Emerald Ash Borer (EAB) [Internet]. [updated 2007 Feb 27]. Columbus (OH): Ohio Department of Natural Resources, Division of Forestry; [cited 2007 Jul 24]. Available from: http://www.dnr.state.oh.us/forestry/health/eab.htm<br />
<br />
In-Text:<br />
(Emerald Ash Borer ... [updated 2007])</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=Code4Lib_Style_Guide&diff=6068Code4Lib Style Guide2010-08-10T14:45:19Z<p>Timmcgeary: /* End of Document */</p>
<hr />
<div>== Start of Article ==<br />
<br />
Article titles are in Title Case -- all major words capitalized. The title is followed by an abstract, which will be pulled from the excerpt section lower on the post page, and byline of the form "by Author" or "by Author 1, Author 2, and Author 3".<br />
<br />
== Headings ==<br />
<br />
Use H2 for main section headings, H3 for sub-sections, H4 if you need a lower level. H2 are in "Title Case" -- all words capitalized, short words (the, a, in, up, over, about) should not be. H3 and H4 are in "Sentence case" -- only the first word is capitalized.<br />
<br />
== Figures & Tables ==<br />
<br />
Figures and tables are centered, placed inside a P or DIV with class of "caption". For example:<br />
<br />
<pre><br />
&lt;p class = "caption"&gt;<br />
&lt;img src = "...."&gt;<br />
&lt;strong&gt;Caption for Figure&lt;/strong&gt;<br />
&lt;p&gt;<br />
<br />
&lt;div class = "caption"&gt;<br />
&lt;table&gt;<br />
&lt;tr&gt;...&lt;/tr&gt;<br />
&lt;/table&gt;<br />
&lt;/div&gt;<br />
</pre><br />
<br />
Captions for figures appear beneath the figure, centered, with "Figure X:" in bold, the descriptive text in sentence case, plain text.<br />
<br />
Captions for tables and code appear above the table, centered, with "Table X:" in bold, the descriptive text in sentence case, plain text.<br />
<br />
== Code ==<br />
<br />
Code samples entered as preformatted text, as in the following example, are automagically color highlighted in Wordpress by the [http://wordpress.org/extend/plugins/syntaxhighlighter/ SyntaxHighlighter] plugin:<br />
<br />
<pre><br />
&lt;pre&gt;<br />
[sourcecode language='php']<br />
RAW HTML/PHP/XML/Etc. code goes here; change language (in above line) as needed<br />
[/sourcecode]<br />
&lt;/pre&gt;<br />
</pre><br />
<br />
Supported formats include <tt>cpp, c, c++, c#, c-sharp, csharp, css, delphi, java, js, jscript, javascript, pascal, php, py, python, rb, ruby, rails, ror, sql, vb, vb.net, xml, html, xhtml, and xslt</tt>. Pretty much everything except <tt>perl</tt>.<br />
<br />
== End of Document ==<br />
<br />
=== Recommended Reference Style Discussion: ===<br />
<br />
CSE has been voted in as the official recommended style (see: [[Citation_discussion]])<br />
<br />
=== Endnote & Endnote References ===<br />
<br />
A Bibliography and Notes section (if needed) immediately follows the last of the article's narrative text. References are indicated by author and year (Smith, 2007). Notes are indicated in the text either by note number in square brackets [1]. <br />
<br />
Bibliographies are recommended to follow CSE reference style. An author may choose to use a different bibliographic reference style, but should follow that style accurately.<br />
<br />
Authors can refer to this guide for using the [[CSE Reference Style]]<br />
<br />
Where notes refer to articles, books, etc., that are not available by direct link, insert a [[COinS (layman's description) | COINS]] element after the note.<br />
<br />
=== About the Author ===<br />
<br />
A sentence or two of brief biography, provided by the author(s), appears listed after the Notes.<br />
<br />
=== Appendices ===<br />
<br />
If there are appendices, they appear after the author biography.<br />
<br />
<br />
<br />
[[Category: Code4Lib Journal]]</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=Code4Lib_Style_Guide&diff=6067Code4Lib Style Guide2010-08-10T14:44:51Z<p>Timmcgeary: /* End of Document */</p>
<hr />
<div>== Start of Article ==<br />
<br />
Article titles are in Title Case -- all major words capitalized. The title is followed by an abstract, which will be pulled from the excerpt section lower on the post page, and byline of the form "by Author" or "by Author 1, Author 2, and Author 3".<br />
<br />
== Headings ==<br />
<br />
Use H2 for main section headings, H3 for sub-sections, H4 if you need a lower level. H2 are in "Title Case" -- all words capitalized, short words (the, a, in, up, over, about) should not be. H3 and H4 are in "Sentence case" -- only the first word is capitalized.<br />
<br />
== Figures & Tables ==<br />
<br />
Figures and tables are centered, placed inside a P or DIV with class of "caption". For example:<br />
<br />
<pre><br />
&lt;p class = "caption"&gt;<br />
&lt;img src = "...."&gt;<br />
&lt;strong&gt;Caption for Figure&lt;/strong&gt;<br />
&lt;p&gt;<br />
<br />
&lt;div class = "caption"&gt;<br />
&lt;table&gt;<br />
&lt;tr&gt;...&lt;/tr&gt;<br />
&lt;/table&gt;<br />
&lt;/div&gt;<br />
</pre><br />
<br />
Captions for figures appear beneath the figure, centered, with "Figure X:" in bold, the descriptive text in sentence case, plain text.<br />
<br />
Captions for tables and code appear above the table, centered, with "Table X:" in bold, the descriptive text in sentence case, plain text.<br />
<br />
== Code ==<br />
<br />
Code samples entered as preformatted text, as in the following example, are automagically color highlighted in Wordpress by the [http://wordpress.org/extend/plugins/syntaxhighlighter/ SyntaxHighlighter] plugin:<br />
<br />
<pre><br />
&lt;pre&gt;<br />
[sourcecode language='php']<br />
RAW HTML/PHP/XML/Etc. code goes here; change language (in above line) as needed<br />
[/sourcecode]<br />
&lt;/pre&gt;<br />
</pre><br />
<br />
Supported formats include <tt>cpp, c, c++, c#, c-sharp, csharp, css, delphi, java, js, jscript, javascript, pascal, php, py, python, rb, ruby, rails, ror, sql, vb, vb.net, xml, html, xhtml, and xslt</tt>. Pretty much everything except <tt>perl</tt>.<br />
<br />
== End of Document ==<br />
<br />
=== Recommended Reference Style Discussion: ===<br />
<br />
CSE has been voted in as the official recommended style (see: [[Citation_discussion]])<br />
<br />
=== Endnote & Endnote References ===<br />
<br />
A Bibliography and Notes section (if needed) immediately follows the last of the article's narrative text. References are indicated by author and year (Smith, 2007). Notes are indicated in the text either by note number in square brackets [1]. <br />
<br />
Bibliographies are recommended to follow CSE reference style. An author may choose to use a different bibliographic reference style, but should follow that style accurately.<br />
<br />
Authors can refer to this guide for using the [CSE Reference Style]<br />
<br />
Where notes refer to articles, books, etc., that are not available by direct link, insert a [[COinS (layman's description) | COINS]] element after the note.<br />
<br />
=== About the Author ===<br />
<br />
A sentence or two of brief biography, provided by the author(s), appears listed after the Notes.<br />
<br />
=== Appendices ===<br />
<br />
If there are appendices, they appear after the author biography.<br />
<br />
<br />
<br />
[[Category: Code4Lib Journal]]</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=Code4Lib_Style_Guide&diff=5936Code4Lib Style Guide2010-05-25T12:52:18Z<p>Timmcgeary: /* End of Document */</p>
<hr />
<div>== Start of Article ==<br />
<br />
Article titles are in Title Case -- all major words capitalized. The title is followed by an abstract, which will be pulled from the excerpt section lower on the post page, and byline of the form "by Author" or "by Author 1, Author 2, and Author 3".<br />
<br />
== Headings ==<br />
<br />
Use H2 for main section headings, H3 for sub-sections, H4 if you need a lower level. H2 are in "Title Case" -- all words capitalized, short words (the, a, in, up, over, about) should not be. H3 and H4 are in "Sentence case" -- only the first word is capitalized.<br />
<br />
== Figures & Tables ==<br />
<br />
Figures and tables are centered, placed inside a P or DIV with class of "caption". For example:<br />
<br />
<pre><br />
&lt;p class = "caption"&gt;<br />
&lt;img src = "...."&gt;<br />
&lt;strong&gt;Caption for Figure&lt;/strong&gt;<br />
&lt;p&gt;<br />
<br />
&lt;div class = "caption"&gt;<br />
&lt;table&gt;<br />
&lt;tr&gt;...&lt;/tr&gt;<br />
&lt;/table&gt;<br />
&lt;/div&gt;<br />
</pre><br />
<br />
Captions for figures appear beneath the figure, centered, with "Figure X:" in bold, the descriptive text in sentence case, plain text.<br />
<br />
Captions for tables and code appear above the table, centered, with "Table X:" in bold, the descriptive text in sentence case, plain text.<br />
<br />
== Code ==<br />
<br />
Code samples entered as preformatted text, as in the following example, are automagically color highlighted in Wordpress by the [http://wordpress.org/extend/plugins/syntaxhighlighter/ SyntaxHighlighter] plugin:<br />
<br />
<pre><br />
&lt;pre&gt;<br />
[sourcecode language='php']<br />
RAW HTML/PHP/XML/Etc. code goes here; change language (in above line) as needed<br />
[/sourcecode]<br />
&lt;/pre&gt;<br />
</pre><br />
<br />
Supported formats include <tt>cpp, c, c++, c#, c-sharp, csharp, css, delphi, java, js, jscript, javascript, pascal, php, py, python, rb, ruby, rails, ror, sql, vb, vb.net, xml, html, xhtml, and xslt</tt>. Pretty much everything except <tt>perl</tt>.<br />
<br />
== End of Document ==<br />
<br />
=== Footnotes & Footnote References ===<br />
<br />
A Notes section (if needed) immediately follows the last of the article's narrative text. Notes are indicated in the text either by note number in square brackets [1] or by author and year [Smith, 2007]. Where notes refer to articles, books, etc., that are not available by direct link, insert a [[COinS (layman's description) | COINS]] element after the note.<br />
<br />
==== Recommended Reference Style Discussion: ====<br />
<br />
Editors, please vote at [[Citation_discussion]]<br />
<br />
=== About the Author ===<br />
<br />
A sentence or two of brief biography, provided by the author(s), appears listed after the Notes.<br />
<br />
=== Appendices ===<br />
<br />
If there are appendices, they appear after the author biography.<br />
<br />
<br />
<br />
[[Category: Code4Lib Journal]]</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=Code4Lib_Style_Guide&diff=5935Code4Lib Style Guide2010-05-25T12:51:42Z<p>Timmcgeary: /* End of Document */</p>
<hr />
<div>== Start of Article ==<br />
<br />
Article titles are in Title Case -- all major words capitalized. The title is followed by an abstract, which will be pulled from the excerpt section lower on the post page, and byline of the form "by Author" or "by Author 1, Author 2, and Author 3".<br />
<br />
== Headings ==<br />
<br />
Use H2 for main section headings, H3 for sub-sections, H4 if you need a lower level. H2 are in "Title Case" -- all words capitalized, short words (the, a, in, up, over, about) should not be. H3 and H4 are in "Sentence case" -- only the first word is capitalized.<br />
<br />
== Figures & Tables ==<br />
<br />
Figures and tables are centered, placed inside a P or DIV with class of "caption". For example:<br />
<br />
<pre><br />
&lt;p class = "caption"&gt;<br />
&lt;img src = "...."&gt;<br />
&lt;strong&gt;Caption for Figure&lt;/strong&gt;<br />
&lt;p&gt;<br />
<br />
&lt;div class = "caption"&gt;<br />
&lt;table&gt;<br />
&lt;tr&gt;...&lt;/tr&gt;<br />
&lt;/table&gt;<br />
&lt;/div&gt;<br />
</pre><br />
<br />
Captions for figures appear beneath the figure, centered, with "Figure X:" in bold, the descriptive text in sentence case, plain text.<br />
<br />
Captions for tables and code appear above the table, centered, with "Table X:" in bold, the descriptive text in sentence case, plain text.<br />
<br />
== Code ==<br />
<br />
Code samples entered as preformatted text, as in the following example, are automagically color highlighted in Wordpress by the [http://wordpress.org/extend/plugins/syntaxhighlighter/ SyntaxHighlighter] plugin:<br />
<br />
<pre><br />
&lt;pre&gt;<br />
[sourcecode language='php']<br />
RAW HTML/PHP/XML/Etc. code goes here; change language (in above line) as needed<br />
[/sourcecode]<br />
&lt;/pre&gt;<br />
</pre><br />
<br />
Supported formats include <tt>cpp, c, c++, c#, c-sharp, csharp, css, delphi, java, js, jscript, javascript, pascal, php, py, python, rb, ruby, rails, ror, sql, vb, vb.net, xml, html, xhtml, and xslt</tt>. Pretty much everything except <tt>perl</tt>.<br />
<br />
== End of Document ==<br />
<br />
=== Footnotes & Footnote References ===<br />
<br />
A Notes section (if needed) immediately follows the last of the article's narrative text. Notes are indicated in the text either by note number in square brackets [1] or by author and year [Smith, 2007]. Where notes refer to articles, books, etc., that are not available by direct link, insert a [[COinS (layman's description) | COINS]] element after the note.<br />
<br />
==== Recommended Reference Style Discussion: ====<br />
<br />
Tim McGeary proposes that the Editorial Committee chose a recommended style for all authors. Authors that do not choose recommended style need to follow another documented style and communicate that to their assigned editor. Using a documented style will provide a clear editorial guidelines for consistency, and ensure proper citations and references of literature and resources.<br />
<br />
jrochkind's proposal: Citations should be clear and unambiguous, and reasonably consistent within an article. Authors are welcome but not required to use a formal style. Editors will ensure readability, clarity, and reasonable consistency of citations, but will not check citations for compliance with stylebooks.<br />
<br />
==== Voting on Recommended Style: ====<br />
{| border="1" cellpadding="5" class="sortable" <br />
|- style="text-align: left;"<br />
<br />
Editors, please vote at [[Citation_discussion]]<br />
<br />
=== About the Author ===<br />
<br />
A sentence or two of brief biography, provided by the author(s), appears listed after the Notes.<br />
<br />
=== Appendices ===<br />
<br />
If there are appendices, they appear after the author biography.<br />
<br />
<br />
<br />
[[Category: Code4Lib Journal]]</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=Code4Lib_Style_Guide&diff=5934Code4Lib Style Guide2010-05-25T12:50:27Z<p>Timmcgeary: /* End of Document */</p>
<hr />
<div>== Start of Article ==<br />
<br />
Article titles are in Title Case -- all major words capitalized. The title is followed by an abstract, which will be pulled from the excerpt section lower on the post page, and byline of the form "by Author" or "by Author 1, Author 2, and Author 3".<br />
<br />
== Headings ==<br />
<br />
Use H2 for main section headings, H3 for sub-sections, H4 if you need a lower level. H2 are in "Title Case" -- all words capitalized, short words (the, a, in, up, over, about) should not be. H3 and H4 are in "Sentence case" -- only the first word is capitalized.<br />
<br />
== Figures & Tables ==<br />
<br />
Figures and tables are centered, placed inside a P or DIV with class of "caption". For example:<br />
<br />
<pre><br />
&lt;p class = "caption"&gt;<br />
&lt;img src = "...."&gt;<br />
&lt;strong&gt;Caption for Figure&lt;/strong&gt;<br />
&lt;p&gt;<br />
<br />
&lt;div class = "caption"&gt;<br />
&lt;table&gt;<br />
&lt;tr&gt;...&lt;/tr&gt;<br />
&lt;/table&gt;<br />
&lt;/div&gt;<br />
</pre><br />
<br />
Captions for figures appear beneath the figure, centered, with "Figure X:" in bold, the descriptive text in sentence case, plain text.<br />
<br />
Captions for tables and code appear above the table, centered, with "Table X:" in bold, the descriptive text in sentence case, plain text.<br />
<br />
== Code ==<br />
<br />
Code samples entered as preformatted text, as in the following example, are automagically color highlighted in Wordpress by the [http://wordpress.org/extend/plugins/syntaxhighlighter/ SyntaxHighlighter] plugin:<br />
<br />
<pre><br />
&lt;pre&gt;<br />
[sourcecode language='php']<br />
RAW HTML/PHP/XML/Etc. code goes here; change language (in above line) as needed<br />
[/sourcecode]<br />
&lt;/pre&gt;<br />
</pre><br />
<br />
Supported formats include <tt>cpp, c, c++, c#, c-sharp, csharp, css, delphi, java, js, jscript, javascript, pascal, php, py, python, rb, ruby, rails, ror, sql, vb, vb.net, xml, html, xhtml, and xslt</tt>. Pretty much everything except <tt>perl</tt>.<br />
<br />
== End of Document ==<br />
<br />
=== Footnotes & Footnote References ===<br />
<br />
A Notes section (if needed) immediately follows the last of the article's narrative text. Notes are indicated in the text either by note number in square brackets [1] or by author and year [Smith, 2007]. Where notes refer to articles, books, etc., that are not available by direct link, insert a [[COinS (layman's description) | COINS]] element after the note.<br />
<br />
==== Recommended Reference Style Discussion: ====<br />
<br />
Tim McGeary proposes that the Editorial Committee chose a recommended style for all authors. Authors that do not choose recommended style need to follow another documented style and communicate that to their assigned editor. Using a documented style will provide a clear editorial guidelines for consistency, and ensure proper citations and references of literature and resources.<br />
<br />
jrochkind's proposal: Citations should be clear and unambiguous, and reasonably consistent within an article. Authors are welcome but not required to use a formal style. Editors will ensure readability, clarity, and reasonable consistency of citations, but will not check citations for compliance with stylebooks.<br />
<br />
==== Voting on Recommended Style: ====<br />
{| border="1" cellpadding="5" class="sortable" <br />
|- style="text-align: left;"<br />
<br />
Editors, please vote at [Citation_discussion]<br />
<br />
=== About the Author ===<br />
<br />
A sentence or two of brief biography, provided by the author(s), appears listed after the Notes.<br />
<br />
=== Appendices ===<br />
<br />
If there are appendices, they appear after the author biography.<br />
<br />
<br />
<br />
[[Category: Code4Lib Journal]]</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=Citation_Format_Recommendations&diff=5933Citation Format Recommendations2010-05-25T12:49:21Z<p>Timmcgeary: </p>
<hr />
<div>[[Category: Code4Lib Journal]]<br />
<br />
==== Recommended Reference Style Information: ====<br />
<br />
Tim McGeary proposes that the Editorial Committee chose a recommended style for all authors. Authors that do not choose recommended style need to follow another documented style and communicate that to their assigned editor. Using a documented style will provide a clear editorial guidelines for consistency, and ensure proper citations and references of literature and resources.<br />
<br />
[http://owl.english.purdue.edu/owl/resource/560/10/ APA Style Example (Purdue)]<br />
<br />
[http://www.library.cornell.edu/resrch/citmanage/mla MLA Style Example (Cornell)]<br />
<br />
[http://library.osu.edu/help/research-strategies/how-do-i-cite-references/cse-citation-guide CSE Style Example (Ohio State)]<br />
<br />
jrochkind's proposal: Citations should be clear and unambiguous, and reasonably consistent within an article. Authors are welcome but not required to use a formal style. Editors will ensure readability, clarity, and reasonable consistency of citations, but will not check citations for compliance with stylebooks.<br />
<br />
==== Voting on Recommended Style: ====<br />
{| border="1" cellpadding="5" class="sortable" <br />
|- style="text-align: left;"<br />
<br />
!Name !! Recommend Style? (Y/N) !! Which Style? (Vote even if N)<br />
|-<br />
| Tim McGeary || Y || CSE<br />
|-<br />
| J Rochkind || N ||<br />
|-<br />
| Carol Bean || Y || CSE<br />
<br />
|-<br />
| Your Name || Vote || Style<br />
<br />
|}</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=Citation_Format_Recommendations&diff=5932Citation Format Recommendations2010-05-25T12:48:58Z<p>Timmcgeary: </p>
<hr />
<div>[[Category: Code4Lib Journal]]<br />
<br />
==== Recommended Reference Style Information: ====<br />
<br />
Tim McGeary proposes that the Editorial Committee chose a recommended style for all authors. Authors that do not choose recommended style need to follow another documented style and communicate that to their assigned editor. Using a documented style will provide a clear editorial guidelines for consistency, and ensure proper citations and references of literature and resources.<br />
<br />
[http://owl.english.purdue.edu/owl/resource/560/10/ APA Style Example (Purdue)]<br />
<br />
[http://www.library.cornell.edu/resrch/citmanage/mla MLA Style Example (Cornell)]<br />
<br />
[http://library.osu.edu/help/research-strategies/how-do-i-cite-references/cse-citation-guide CSE Style Example (Ohio State)]<br />
<br />
jrochkind's proposal: Citations should be clear and unambiguous, and reasonably consistent within an article. Authors are welcome but not required to use a formal style. Editors will ensure readability, clarity, and reasonable consistency of citations, but will not check citations for compliance with stylebooks.</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=Code4Lib_Style_Guide&diff=5929Code4Lib Style Guide2010-05-24T20:03:01Z<p>Timmcgeary: /* End of Document */</p>
<hr />
<div>== Start of Article ==<br />
<br />
Article titles are in Title Case -- all major words capitalized. The title is followed by an abstract, which will be pulled from the excerpt section lower on the post page, and byline of the form "by Author" or "by Author 1, Author 2, and Author 3".<br />
<br />
== Headings ==<br />
<br />
Use H2 for main section headings, H3 for sub-sections, H4 if you need a lower level. H2 are in "Title Case" -- all words capitalized, short words (the, a, in, up, over, about) should not be. H3 and H4 are in "Sentence case" -- only the first word is capitalized.<br />
<br />
== Figures & Tables ==<br />
<br />
Figures and tables are centered, placed inside a P or DIV with class of "caption". For example:<br />
<br />
<pre><br />
&lt;p class = "caption"&gt;<br />
&lt;img src = "...."&gt;<br />
&lt;strong&gt;Caption for Figure&lt;/strong&gt;<br />
&lt;p&gt;<br />
<br />
&lt;div class = "caption"&gt;<br />
&lt;table&gt;<br />
&lt;tr&gt;...&lt;/tr&gt;<br />
&lt;/table&gt;<br />
&lt;/div&gt;<br />
</pre><br />
<br />
Captions for figures appear beneath the figure, centered, with "Figure X:" in bold, the descriptive text in sentence case, plain text.<br />
<br />
Captions for tables and code appear above the table, centered, with "Table X:" in bold, the descriptive text in sentence case, plain text.<br />
<br />
== Code ==<br />
<br />
Code samples entered as preformatted text, as in the following example, are automagically color highlighted in Wordpress by the [http://wordpress.org/extend/plugins/syntaxhighlighter/ SyntaxHighlighter] plugin:<br />
<br />
<pre><br />
&lt;pre&gt;<br />
[sourcecode language='php']<br />
RAW HTML/PHP/XML/Etc. code goes here; change language (in above line) as needed<br />
[/sourcecode]<br />
&lt;/pre&gt;<br />
</pre><br />
<br />
Supported formats include <tt>cpp, c, c++, c#, c-sharp, csharp, css, delphi, java, js, jscript, javascript, pascal, php, py, python, rb, ruby, rails, ror, sql, vb, vb.net, xml, html, xhtml, and xslt</tt>. Pretty much everything except <tt>perl</tt>.<br />
<br />
== End of Document ==<br />
<br />
=== Footnotes & Footnote References ===<br />
<br />
A Notes section (if needed) immediately follows the last of the article's narrative text. Notes are indicated in the text either by note number in square brackets [1] or by author and year [Smith, 2007]. Where notes refer to articles, books, etc., that are not available by direct link, insert a [[COinS (layman's description) | COINS]] element after the note.<br />
<br />
==== Recommended Reference Style Information: ====<br />
<br />
Tim McGeary proposes that the Editorial Committee chose a recommended style for all authors. Authors that do not choose recommended style need to follow another documented style and communicate that to their assigned editor. Using a documented style will provide a clear editorial guidelines for consistency, and ensure proper citations and references of literature and resources.<br />
<br />
[http://owl.english.purdue.edu/owl/resource/560/10/ APA Style Example (Purdue)]<br />
<br />
[http://www.library.cornell.edu/resrch/citmanage/mla MLA Style Example (Cornell)]<br />
<br />
[http://library.osu.edu/help/research-strategies/how-do-i-cite-references/cse-citation-guide CSE Style Example (Ohio State)]<br />
<br />
jrochkind's proposal: Citations should be clear and unambiguous, and reasonably consistent within an article. Authors are welcome but not required to use a formal style. Editors will ensure readability, clarity, and reasonable consistency of citations, but will not check citations for compliance with stylebooks.<br />
<br />
==== Voting on Recommended Style: ====<br />
{| border="1" cellpadding="5" class="sortable" <br />
|- style="text-align: left;"<br />
<br />
!Name !! Recommend Style? (Y/N) !! Which Style? (Vote even if N)<br />
|-<br />
| Tim McGeary || Y || CSE<br />
|-<br />
| J Rochkind || N ||<br />
<br />
|-<br />
| Your Name || Vote || Style<br />
<br />
|}<br />
<br />
=== About the Author ===<br />
<br />
A sentence or two of brief biography, provided by the author(s), appears listed after the Notes.<br />
<br />
=== Appendices ===<br />
<br />
If there are appendices, they appear after the author biography.<br />
<br />
<br />
<br />
[[Category: Code4Lib Journal]]</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=Code4Lib_Style_Guide&diff=5928Code4Lib Style Guide2010-05-24T19:58:34Z<p>Timmcgeary: /* Voting on Recommended Style: */</p>
<hr />
<div>== Start of Article ==<br />
<br />
Article titles are in Title Case -- all major words capitalized. The title is followed by an abstract, which will be pulled from the excerpt section lower on the post page, and byline of the form "by Author" or "by Author 1, Author 2, and Author 3".<br />
<br />
== Headings ==<br />
<br />
Use H2 for main section headings, H3 for sub-sections, H4 if you need a lower level. H2 are in "Title Case" -- all words capitalized, short words (the, a, in, up, over, about) should not be. H3 and H4 are in "Sentence case" -- only the first word is capitalized.<br />
<br />
== Figures & Tables ==<br />
<br />
Figures and tables are centered, placed inside a P or DIV with class of "caption". For example:<br />
<br />
<pre><br />
&lt;p class = "caption"&gt;<br />
&lt;img src = "...."&gt;<br />
&lt;strong&gt;Caption for Figure&lt;/strong&gt;<br />
&lt;p&gt;<br />
<br />
&lt;div class = "caption"&gt;<br />
&lt;table&gt;<br />
&lt;tr&gt;...&lt;/tr&gt;<br />
&lt;/table&gt;<br />
&lt;/div&gt;<br />
</pre><br />
<br />
Captions for figures appear beneath the figure, centered, with "Figure X:" in bold, the descriptive text in sentence case, plain text.<br />
<br />
Captions for tables and code appear above the table, centered, with "Table X:" in bold, the descriptive text in sentence case, plain text.<br />
<br />
== Code ==<br />
<br />
Code samples entered as preformatted text, as in the following example, are automagically color highlighted in Wordpress by the [http://wordpress.org/extend/plugins/syntaxhighlighter/ SyntaxHighlighter] plugin:<br />
<br />
<pre><br />
&lt;pre&gt;<br />
[sourcecode language='php']<br />
RAW HTML/PHP/XML/Etc. code goes here; change language (in above line) as needed<br />
[/sourcecode]<br />
&lt;/pre&gt;<br />
</pre><br />
<br />
Supported formats include <tt>cpp, c, c++, c#, c-sharp, csharp, css, delphi, java, js, jscript, javascript, pascal, php, py, python, rb, ruby, rails, ror, sql, vb, vb.net, xml, html, xhtml, and xslt</tt>. Pretty much everything except <tt>perl</tt>.<br />
<br />
== End of Document ==<br />
<br />
=== Footnotes & Footnote References ===<br />
<br />
A Notes section (if needed) immediately follows the last of the article's narrative text. Notes are indicated in the text either by note number in square brackets [1] or by author and year [Smith, 2007]. Where notes refer to articles, books, etc., that are not available by direct link, insert a [[COinS (layman's description) | COINS]] element after the note.<br />
<br />
==== Recommended Reference Style Information: ====<br />
<br />
[http://owl.english.purdue.edu/owl/resource/560/10/ APA Style Example (Purdue)]<br />
<br />
[http://www.library.cornell.edu/resrch/citmanage/mla MLA Style Example (Cornell)]<br />
<br />
[http://library.osu.edu/help/research-strategies/how-do-i-cite-references/cse-citation-guide CSE Style Example (Ohio State)]<br />
<br />
jrochkind's proposal: Citations should be clear and unambiguous, and reasonably consistent within an article. Authors are welcome but not required to use a formal style. Editors will ensure readability, clarity, and reasonable consistency of citations, but will not check citations for compliance with stylebooks.<br />
<br />
==== Voting on Recommended Style: ====<br />
{| border="1" cellpadding="5" class="sortable" <br />
|- style="text-align: left;"<br />
<br />
!Name !! Recommend Style? (Y/N) !! Which Style? (Vote even if N)<br />
|-<br />
| Tim McGeary || Y || CSE<br />
|-<br />
| J Rochkind || N ||<br />
<br />
|-<br />
| Your Name || Vote || Style<br />
<br />
|}<br />
<br />
=== About the Author ===<br />
<br />
A sentence or two of brief biography, provided by the author(s), appears listed after the Notes.<br />
<br />
=== Appendices ===<br />
<br />
If there are appendices, they appear after the author biography.<br />
<br />
<br />
<br />
[[Category: Code4Lib Journal]]</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=Code4Lib_Style_Guide&diff=5925Code4Lib Style Guide2010-05-24T19:35:02Z<p>Timmcgeary: /* End of Document */</p>
<hr />
<div>== Start of Article ==<br />
<br />
Article titles are in Title Case -- all major words capitalized. The title is followed by an abstract, which will be pulled from the excerpt section lower on the post page, and byline of the form "by Author" or "by Author 1, Author 2, and Author 3".<br />
<br />
== Headings ==<br />
<br />
Use H2 for main section headings, H3 for sub-sections, H4 if you need a lower level. H2 are in "Title Case" -- all words capitalized, short words (the, a, in, up, over, about) should not be. H3 and H4 are in "Sentence case" -- only the first word is capitalized.<br />
<br />
== Figures & Tables ==<br />
<br />
Figures and tables are centered, placed inside a P or DIV with class of "caption". For example:<br />
<br />
<pre><br />
&lt;p class = "caption"&gt;<br />
&lt;img src = "...."&gt;<br />
&lt;strong&gt;Caption for Figure&lt;/strong&gt;<br />
&lt;p&gt;<br />
<br />
&lt;div class = "caption"&gt;<br />
&lt;table&gt;<br />
&lt;tr&gt;...&lt;/tr&gt;<br />
&lt;/table&gt;<br />
&lt;/div&gt;<br />
</pre><br />
<br />
Captions for figures appear beneath the figure, centered, with "Figure X:" in bold, the descriptive text in sentence case, plain text.<br />
<br />
Captions for tables and code appear above the table, centered, with "Table X:" in bold, the descriptive text in sentence case, plain text.<br />
<br />
== Code ==<br />
<br />
Code samples entered as preformatted text, as in the following example, are automagically color highlighted in Wordpress by the [http://wordpress.org/extend/plugins/syntaxhighlighter/ SyntaxHighlighter] plugin:<br />
<br />
<pre><br />
&lt;pre&gt;<br />
[sourcecode language='php']<br />
RAW HTML/PHP/XML/Etc. code goes here; change language (in above line) as needed<br />
[/sourcecode]<br />
&lt;/pre&gt;<br />
</pre><br />
<br />
Supported formats include <tt>cpp, c, c++, c#, c-sharp, csharp, css, delphi, java, js, jscript, javascript, pascal, php, py, python, rb, ruby, rails, ror, sql, vb, vb.net, xml, html, xhtml, and xslt</tt>. Pretty much everything except <tt>perl</tt>.<br />
<br />
== End of Document ==<br />
<br />
=== Footnotes & Footnote References ===<br />
<br />
A Notes section (if needed) immediately follows the last of the article's narrative text. Notes are indicated in the text either by note number in square brackets [1] or by author and year [Smith, 2007]. Where notes refer to articles, books, etc., that are not available by direct link, insert a [[COinS (layman's description) | COINS]] element after the note.<br />
<br />
==== Recommended Reference Style Information: ====<br />
<br />
[http://owl.english.purdue.edu/owl/resource/560/10/ APA Style Example (Purdue)]<br />
<br />
[http://www.library.cornell.edu/resrch/citmanage/mla MLA Style Example (Cornell)]<br />
<br />
[http://library.osu.edu/help/research-strategies/how-do-i-cite-references/cse-citation-guide CSE Style Example (Ohio State)]<br />
<br />
==== Voting on Recommended Style: ====<br />
{| border="1" cellpadding="5" class="sortable" <br />
|- style="text-align: left;"<br />
<br />
!Name !! Recommend Style? (Y/N) !! Which Style? (Vote even if N)<br />
|-<br />
| Tim McGeary || Y || CSE<br />
<br />
|-<br />
| Your Name || Vote || Style<br />
<br />
|}<br />
<br />
=== About the Author ===<br />
<br />
A sentence or two of brief biography, provided by the author(s), appears listed after the Notes.<br />
<br />
=== Appendices ===<br />
<br />
If there are appendices, they appear after the author biography.<br />
<br />
<br />
<br />
[[Category: Code4Lib Journal]]</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=C4L2010rideshare&diff=3828C4L2010rideshare2010-01-07T16:30:03Z<p>Timmcgeary: /* Asheville/Arden Regional Airport */</p>
<hr />
<div>== Rideshare Info ==<br />
<br />
Several people have made vague but curious noises about trying to share transportation to and from Asheville. This page will attempt to organize the details relevant to help attendees make appropriate travel/transportation plans.<br />
<br />
Each table below represents a group of attendees with relatively common transportation needs. Feel free to combine/split/add tables to suit different needs. The columns should be self-explanatory, with '''Driving?''' indicating that you're willing/able to share the driving (even if it's someone else's car/rental), and '''Van?''' indicating whether you would be interested in taking one of the App. State vans (if it were to make a couple runs to the airport). <br />
<br />
=== Charlotte Douglas International Airport ===<br />
{| border="1" cellpadding="5" class="sortable" <br />
|- style="text-align: left;"<br />
! Name !! Arriving !! Departing !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van?<br />
|-<br />
| Julia Bauder || 2010-02-21 (Sunday; mid-afternoon) || 2010-02-25 (Thursday; late afternoon) || No || Yes || Yes || Yes || Yes<br />
|-<br />
| Michael Klein || 2010-02-21 (Sunday; late afternoon/evening) || 2010-02-26 (Friday) || No || Yes || Yes || Yes || Yes<br />
|-<br />
| Tim Dennis || 2010-02-21 (Sunday; 4pm) || 2010-02-25 (Thurs. 5pm) || No || Yes || Yes || Yes || Yes <br />
|}<br />
<br />
=== Asheville/Arden Regional Airport ===<br />
{| border="1" cellpadding="5" class="sortable"<br />
|- style="text-align: left;"<br />
! Name !! Arriving !! Departing !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van?<br />
|-<br />
| Mike Giarlo || 2010-02-21 (Sunday) 11:38am || 2010-02-26 (Friday) 12:03pm || No || Yes || Yes || No || Yes<br />
|- <br />
| Daniel Lovins || 2010-02-21 (Sunday) 11:57am || 2010-02-25 (Thursday) 2:21pm || No || Yes || Yes || Yes || Yes<br />
|-<br />
| Tom Keays || 2010-02-21 (Sunday) 12:09pm || 2010-02-25 (Thursday) 12:55pm || No || Yes || Yes || No || Yes<br />
|-<br />
| Jean Rainwater || 2010-02-21 (Sunday) 12:15pm || 2010-02-26 (Friday) 4:00pm || No || Yes || Yes || No || Yes<br />
|-<br />
| Michael Doran || 2010-02-21 (Sunday) 6:14pm || 2010-02-26 (Friday) 11:25am || No || No || No || No || Yes<br />
|-<br />
| Andrew Darby || 2010-02-21 (Sunday) 6:15pm || 2010-02-26 (Friday) 11:25am || No || Yes || Yes || No || Yes<br />
|-<br />
| Sam Kome || 2010-02-21 (Sunday) 7:50pm || 2010-02-25 (Thursday) 4:30pm || No || Yes || Yes || Yes || Yes<br />
|-<br />
| Dhanushka S || 2010-02-21 (Sunday) 8:39pm || 2010-02-25 (Thursday) 2:26pm || No || Yes || Yes || Yes || Yes<br />
|-<br />
|<strike> Tim McGeary</strike> || <strike>2010-02-22 (Monday) 9:35pm</strike> || <strike>2010-02-25 (Thursday) 4:30pm</strike> || || || || || <br />
|-<br />
| Cody Hennesy || 2010-02-21 (Sunday) 9:55pm || 2010-02-25 (Thursday) 4:17pm || No || Yes || Yes || No || Yes<br />
|-<br />
| Lori Stethers || 2010-02-21 (Sunday) 10:55pm || 2010-02-25 (Thursday) 3:21pm || No || Yes || Yes || Yes || Yes<br />
|-<br />
| Carol Bean || 2010-02-21 (Sunday) || 2010-02-25 (Thursday) || No || Yes || Yes || Yes || Yes <br />
|}<br />
<br />
=== Northeast (VA/DC/MD/DE/PA/NJ/NY/New England) ===<br />
{| border="1" cellpadding="5" class="sortable"<br />
|- style="text-align: left;"<br />
! Name !! Traveling From !! Plan to Arrive !! Plan to Depart !! Car? !! Share rental cost? !! Gas? !! Driving?<br />
|-<br />
| Ray Schwartz || New York City Metro || Before Preconferences || Thurs aftn || no, willing to rent || Yes || Yes || Yes<br />
|-<br />
| Cory Rockliff || New York City Metro || Before Preconferences || Thurs aftn || no, willing to rent || Yes || Yes || No<br />
|-<br />
| Yitzchak Schaffer || NJ (near Secaucus) || Monday (not for precon), negotiable || Thurs aftn || no, willing to rent || yes || yes || yes<br />
|-<br />
| Jodi Schneider || NJ Turnpike/Philly Metro || Before Preconferences || Thurs aftn || no || Yes || Yes || No<br />
|}<br />
<br />
=== Kentucky/Michigan/Ohio/West Virginia ===<br />
{| border="1" cellpadding="5" class="sortable"<br />
|- style="text-align: left;"<br />
! Name !! Traveling From !! Plan to Arrive !! Plan to Depart !! Car? !! Share rental cost? !! Gas? !! Driving?<br />
|-<br />
| Peter Murray || Columbus, OH || Monday afternoon || Thursday after conference close || Yes || Yes || Yes || Yes<br />
|-<br />
| Becky Yoose || Oxford, OH || Sunday afternoon (before preconference) || Thursday after conference close || Yes || N/A || Yes || Yes<br />
|-<br />
| Devon Smith || Columbus, OH || Monday early || Thursday || Yes (rental) || Yes || Yes || Yes<br />
|}<br />
<br />
=== Eastern Tennessee (Chattanooga/Knoxville) ===<br />
{| border="1" cellpadding="5" class="sortable"<br />
|- style="text-align: left;"<br />
! Name !! Traveling From !! Plan to Arrive !! Plan to Depart !! Car? !! Share rental cost? !! Gas? !! Driving?<br />
|-<br />
| Carol Bean || Chattanooga, TN || Sunday || Thursday after Conference close || Yes (rental) || Yes || Yes || Yes<br />
|-<br />
[[Category: Code4Lib2010]]</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=C4L2010rideshare&diff=3734C4L2010rideshare2009-12-17T14:20:52Z<p>Timmcgeary: </p>
<hr />
<div>== Rideshare Info ==<br />
<br />
Several people have made vague but curious noises about trying to share transportation to and from Asheville. This page will attempt to organize the details relevant to help attendees make appropriate travel/transportation plans.<br />
<br />
Each table below represents a group of attendees with relatively common transportation needs. Feel free to combine/split/add tables to suit different needs. The columns should be self-explanatory, with '''Driving?''' indicating that you're willing/able to share the driving (even if it's someone else's car/rental), and '''Van?''' indicating whether you would be interested in taking one of the App. State vans (if it were to make a couple runs to the airport). <br />
<br />
=== Charlotte Douglas International Airport ===<br />
{| border="1" cellpadding="5" class="sortable" <br />
|- style="text-align: left;"<br />
! Name !! Arriving !! Departing !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van?<br />
|-<br />
| Michael Klein || 2009-02-21 (Sunday; late afternoon/evening) || 2009-02-26 (Friday) || No || Yes || Yes || Yes || Yes<br />
|}<br />
<br />
<br />
=== Asheville/Arden Regional Airport ===<br />
{| border="1" cellpadding="5" class="sortable"<br />
|- style="text-align: left;"<br />
! Name !! Arriving !! Departing !! Renting Car? !! Share rental cost? !! Gas? !! Driving? !! Van?<br />
|- <br />
| Daniel Lovins || 2009-02-21 (Sunday) 11:57am || 2009-02-25 (Thursday) 2:21pm || No || Yes || Yes || Yes || Yes<br />
|-<br />
| Mike Giarlo || 2009-02-21 (Sunday) 11:38am || 2009-02-26 (Friday) 12:03pm || No || Yes || Yes || No || Yes<br />
|-<br />
| Jean Rainwater || 2009-02-21 (Sunday) 12:15pm || 2009-02-26 (Friday) 4:00pm || No || Yes || Yes || No || Yes<br />
|-<br />
| Tim McGeary || 2009-02-22 (Monday) 9:35pm || 2009-02-25 (Thursday) 4:30pm || No || Yes || Yes || No || Yes<br />
|<br />
|}<br />
<br />
<br />
=== Northeast (VA/DC/MD/DE/PA/NJ/NY/New England) ===<br />
{| border="1" cellpadding="5" class="sortable"<br />
|- style="text-align: left;"<br />
! Name !! Traveling From !! Plan to Arrive !! Plan to Depart !! Car? !! Share rental cost? !! Gas? !! Driving?<br />
|-<br />
| Ray Schwartz || New York City Metro || Before Preconferences || To get to prefconfs in time || N/A || Yes || Yes || Yes<br />
|-<br />
| Yitzchak Schaffer || New York City Metro || Monday (not for precon) || Thurs aftn || no, willing to rent || yes || yes || yes<br />
|-<br />
| Jodi Schneider || NJ Turnpike/Philly Metro || Before Preconferences || Thurs aftn || no || Yes || Yes || No<br />
|}<br />
[[Category: Code4Lib2010]]</div>Timmcgearyhttps://wiki.code4lib.org/index.php?title=2009_Conference_Buzz&diff=23512009 Conference Buzz2009-02-24T13:49:29Z<p>Timmcgeary: </p>
<hr />
<div>== Announcements From the Organizers ==<br />
<br />
* twitter hashtag: #c4l09<br />
* [http://code4lib.org/conference/2009/schedule Conference Program]<br />
* [http://code4lib.org/conference/2009/breakouts Breakout Sessions]<br />
* [http://code4lib.org/conference/2009/lightning Lightning Talks]<br />
* Internet in guest rooms at the Renaissance Providence is FREE. You have to accept payment on the login screen but internet charges will NOT be added to your bill. Free internet in guest rooms is part of our contract with the hotel. This applies whether you are in the discounted block or at a higher rate.<br />
* [http://maps.google.com/maps/ms?ie=UTF8&hl=en&msa=0&msid=107701218656997471821.00046117cc493635eebc1&ll=41.825572,-71.390877&spn=0.090438,0.152092&z=13 Annotated Google Map]<br />
* The Handel meeting room is available for "whatever" to conference attendees from 7pm to 11pm Monday through Wednesday evenings.<br />
<br />
== Does Anybody Want To...? ==<br />
<br />
* go see some live music? see below under Things To Do: Clubs and Culture > Music.<br />
<del>* Hit the rock climbing gym? See below under Things To Do: Saturday-Friday > Activities</del><br />
<br />
== Eats ==<br />
* '''Breakfast''' Tuesday - Thursday is continental (pastry, bagels, fruit). If you want something more substantial the Temple Restaurant in the hotel serves breakfast starting at 6:30am.<br />
* '''Lunch''' is provided on Tuesday and Wednesday. Lunch options on other days:<br />
** '''Renaissance area'''<br />
*** Temple (in the hotel - macaroni & cheese is yummy)<br />
*** [http://www.thecubanrevolution.com/ Cuban Revolution], 50 Aborn Street<br />
*** [http://www.providenceplace.com/html/mallattractions.asp Providence Place Mall] - The Mall is just down the hill from the Renaissance (exit the hotel and turn right down the hill). You can check out the Apple store while you're there. <br />
**** Street Level (Francis St): [http://www.napavalleygrille.com/providence/about.php Napa Valley Grille] (upscale, local seasonal), Cheesecake Factory, [http://www.joesamerican.com/ Joe's American Bar & Grill], [http://www.fire-ice.com/locations/providence.html Fire + Ice]<br />
**** Food Court (Level 3): Cathay Cathay, Charley's Grilled Subs, Gourmet India, Johnny Rocket's, Pizzera Regina, Popeye's Chicken and Biscuits, Surf and Turf, Taco Bell, Subway<br />
**** Best Kept Secret: Cafe Nordstrom (inside Nordstrom's, level 3)<br />
**** Entertainment Level (above food court): Dave & Buster's (adult arcade with food)<br />
** '''Brown Campus area''' - Thayer St. vicinity - a few Ground Crew recommendations, but there are many others<br />
*** Quick: Au Bon Pain (233 Thayer), [http://www.meetingstreetcafe.com Meeting Street Cafe] (220 Meeting St), [http://www.eastsidepocket.com/ East Side Pockets] (278 Thayer)<br />
**** Meeting Street's sandwiches are delicious. Also the size of your head. Save yourself and order a half sandwich.<br />
*** Sit down: [http://www.paragonandviva.com/ Paragon] (234 Thayer), Kartabar (284 Thayer)<br />
*** Ethnic: Kabob & Curry (Indian, 261 Thayer), Andreas (Greek, 268 Thayer), Phonatic (Asian, 165 Angell)<br />
*** Coffee shops: Starbucks (218 Thayer), Brown Bookstore Cafe (244 Thayer), [http://www.bluestatecoffee.com/ Blue State Coffee] (300 Thayer)<br />
*** Best reasonably priced sushi: Sakura, 231 Wickenden St. They have a tatami room for those so inclined.<br />
* '''Dinner''' (in addition to places mentioned for lunch)<br />
''This is just a sample of the restaurants in the neighborhoods listed below.''<br />
** '''Exchange Terrace''' - formerly the city's train station - 0.4 miles<br />
***RuthChris Steak House<br />
***Union Station Brewery, 36 Exchange Terrace<br />
***Capital Grill<br />
***[http://www.rira.com/providence/home.html RiRa]<br />
** '''North & South Main Street''' - Providence's original settlement, then on the waterfront - 0.5-0.75 miles<br />
***Hemenways - seafood<br />
***ParkSide<br />
***Mills Tavern<br />
***XO<br />
** '''Down City''' <br />
***[http://www.downcityfood.com/ DownCity Diner]<br />
***[http://www.local121.com/home Local 121]<br />
***[http://www.trinitybrewhouse.com/ Trinity Brewhouse], 186 Fountain St<br />
** '''Federal Hill''' - famed for its Italian restaurants, but there's quite a mix; might want a cab<br />
** '''South Water & Wickenden''' - artsy area, antique stores & funky shops; might want a cab<br />
***Al Forno - considered by some the best restaurant in Providence<br />
***The Old Colonial<br />
<br />
More options at [http://foam.lib.muohio.edu/ProvidenceRestaurantsCMA.pdf PDF of recommendations from Miami University of Ohio]<br />
<br />
== Dinner Plans ==<br />
* '''Sunday & Monday'''<br />
If your travel plans include arriving in Providence on Sunday or Monday, you may want to hook up with other code4libbers for dinner. We suggest that you go to the lobby fireplace to identify like-minded souls at 5pm, 6pm or 7pm. We will point out a few nearby restaurants for your consideration, including the hotel's Temple Restaurant (http://www.temple-downtown.com/).<br />
* '''Tuesday & Wednesday'''<br />
We're expecting some kind-of-organized group dining options, possibly with signups in the registration area. Watch this spot for more details.<br />
<br />
== Discounts ==<br />
* $15.00 off per table for lunch or dinner at [http://www.napavalleygrille.com/providence/about.php Napa Valley Grille] with your Code4Lib badge<br />
<br />
== Things To Do: Monday ==<br />
If you have the time and inclination on Monday, you may want to head up College Hill, about 1 mile, to see historic Benefit Street, visit the Brown campus or go to lunch on Thayer Street. If so, you can walk or take advantage of shuttles we’ve arranged for the pre-conferences (but please give priority to pre-conference attendees).<br />
* 7:45 am – 9:45 pm <br />
* 11:45 am – 1:45 pm <br />
* 4:15 pm – 6:15 pm<br />
<br />
== Things To Do: Tuesday ==<br />
<br />
== Things To Do: Wednesday ==<br />
[http://www.local121.com/news American Farm documentary, Dinner Buffet of locally sourced food] ($15) at 6:15pm, Film at 7pm at Local 121, 121 Washington Street<br />
<br />
== Things To Do: Thursday ==<br />
<br />
== Things To Do: Saturday-Friday == <br />
''nearly all are easily walkable from the Renaissance''<br />
* '''Fresh Air'''<br />
** [http://www.providenceskating.com/ Bank of America Skating Center], 2 Kennedy Plaza (daily 11am-10pm)<br />
** [http://www.pps.org/great_public_spaces/one?public_place_id=86 Riverwalk & Waterplace Park] - access across the street from the Mall<br />
* '''Beer'''<br />
** Union Station Brewery, 36 Exchange Terrace<br />
** [http://www.trinitybrewhouse.com/ Trinity Brewhouse], 186 Fountain St<br />
* '''Clubs'''<br />
**[http://www.lupos.com Lupo's Heartbreak Hotel], 79 Washington St. <br />
*** '''State Radio''' (Sat 2/21, 7pm)<br />
*** '''Tokyo Police Club''' (Tue 2/24, 8:30pm) - [[User:fak3r|fak3r]] and kat3 are interested in going to this ([http://www.etix.com/ticket/servlet/onlineSale?action=selectPerformance&searchType=venue&displayType=list&cobrand=lupos&performance_id=889136 tickets])<br />
** [http://www.as220.org/ AS220] - 115 Empire Street<br />
*** '''[http://www.myspace.com/witchofficial Earthless] and [http://www.myspace.com/witchofficial Witch]''' (Sun 2/22) - [[User:Anarchivist|anarchivist]] is interested in this, and probably robcaSSon and gsf and kat3<br />
*** '''[http://www.myspace.com/officialjuiceboxxx Juiceboxxx], Javelin, and Jazz Hand Job''' (Mon 2/23) - [[User:Anarchivist|anarchivist]]<br />
* '''Culture'''<br />
** Art<br />
*** RISD Museum of Art<br />
**** [http://greenlee.02909.com/ Shawn Greenlee] - '''Occasions''': ''Occasions produces subtle interactions of synthetic tones mediated by the resonance of space and the reception of the listener. It is a long form, audio-installation utilizing a 12-channel speaker array to project sound in the exhibition space. Each of the twelve speakers produces a unique tone gliding between established frequencies. The twelve speakers are divided into two groups which move asynchronously thus creating a fluctuation in acoustic and psychoacoustic phenomena as the glissandi interact. When listening, what one will notice most obviously are several beating frequencies and difference tones - and that the perception of these is in large part due to where the listener positions herself in relationship to the speakers. The sound of the HVAC will begin to wax and wane as Occasions interferes with its site.''<br />
** Music<br />
*** [http://vmari.org/inner/events/ripo-rush-feb26.php RI Philharmonic], next door to the Renaissance - '''Rush Hour Series: Copland, Britten, Shostakovich''' (Thur 6:30)<br />
** Theater<br />
*** [http://www.ppacri.org/ Providence Performing Arts Center], 220 Weybosset St - '''Stomp''' (Sat 5 & 9, Sun 1 & 6:30)<br />
*** [http://www.trinityrep.com/ Trinity Repertory Theater], 201 Washington St - '''A Raisin in the Sun''' (7:30 on Sat, Sun, Tue, Thu, also 2 on Sun) - '''The Secret Rapture''' (7:30 on Sat, Sun, Tue, Thu)<br />
*** [http://www.blackrep.org/ Black Repertory Theater], 276 Westminster St - '''A Time of Fire''' (Sat 7, Sun 3, Thu 7)<br />
* '''Activities'''<br />
** <del>Rock Climbing - [[User:Dcloutman|David Cloutman]] wouldn't mind getting a few hours in at the local rock climbing gym one evening during the conference. Looking for interested attendees. Would probably involve a cab ride. [http://www.rhodeislandrockgym.com/ "Rhode Island Rock Gym"]</del><br />
* '''Movies'''<br />
** [http://www.providenceplace.com/html/movielisting.asp Providence Place Mall], 1st run & IMAX<br />
** [http://www.cablecarcinema.com/ Cable Car Cinema & Cafe], 204 South Main St <br />
* '''Sports''' - [http://www.dunkindonutscenter.com/ Dunkin Donuts Center], 1 LaSalle Square<br />
** Basketball: Providence College vs. Notre Dame (Sat., noon), Providence College vs. Pitt (Tue 7pm)<br />
** Hockey: Providence Bruins vs. Springfield Falcons (Sun 4)<br />
** "Monster Jam" (Fri 7:30)<br />
* '''Other''' - [http://www.flowershow.com/ Flower & Garden Show] (RI Convention Center, 1 Sabin St, Sat 10-9, Sun 10-6)<br />
<br />
== Divine Providence ==<br />
* Seeing the Sites<br />
** don't miss: top EZ cheap visits that prove you left the hotel at least some duringall of code4lib. Arranged in an order that could be a walking tour. [under construction]<br />
*** RI State House - When built in early 20th century RI was 2nd richest state; now we're tied with Michigan for highest unemployment, and continue to rely on the state motto: "Hope". Still, it remains a majestic space, worth a visit, and so close to code4lib! Give a call-out to the guy on top: the Independent Man.<br />
*** Roger Williams National Memorial - Thank Roger for separation of church & state and freedom of religion; nice video gives the basics of Providence's founding after Massachusetts kicked him out, his unique respect and cooperation with Native Americans, etc. A visit here qualifies you to say "What Cheer, Netop!" with aplomb.<br />
*** Cross Main Street, and walk up Star or Church Street next to the (Episcopal) Cathedral of St. John, to Benefit Street, and turn right for a stroll along "a mile of history" past a variety of 18th and 19th century buildings, a blend of residential and RISD. Notice the old State House, where Rhode Island declared independence in May 1776, two months prior to July 4th. <br />
***First Baptist Church of America. One of those enchanting "colonial" churches, lovely inside and out. Unlike most of the rest of New England, Rhode Islanders didn't build their churches on village greens, lest the clergy keep too close an eye on things. <br />
*** RISD (riz-dee) Museum. With a little bit of everything, this gem serves up art from ancient Egypt to now in easily digestible morsels. Wonderful new addition provides, among other things, an excellent 20th century gallery. Also, don't miss the Buddha. Enter on South Main or Benefit.<br />
***Providence Athenaeum - Helps you remember why you care about libraries. Edgar Allen Poe is said to have had trysts with his sweetie, Helen, here, adding to the charm. Going up College Street, you arrive at Prospect Street, with Brown's John Hay Library to the left and the John D. Rockefeller Library, Jr. Library to the right. <br />
***Lincoln and Lovecraft at the John Hay Library. John Hay was Abe Lincoln's Secretary of State and a Brown alum; give his nose a rub as generations of Brown students have. Currently some very nice Lincoln material is on exhibit on the main floor, and nine display cases of quirky Providence native son H. P. Lovecraft manuscripts and publications are in the Lownes Room. Check out the room devoted to toy soldiers (Anne S. K. Brown Military Collection, 3rd floor) and the Audubon elephant folio in the lobby.<br />
***Brown University central campus. Enter through the Van Wickle gates (that open in for opening convocation, and open out for commencement.) University Hall, the "college edifice" housed French soldiers during the Revolutionary War. The Greek Temple next to it was the second building: a library of course! Now it houses an always-interesting selection of artifacts from the Haffenreffer Museum of Anthrolopology. Walk between these two buildings, and cross the main green; one of the perks for Brown presidents is the right to graze sheep here. Head between the next row of buildings and go down the steps (notice Marcus Aurelius, copied from Rome). This green, Lincoln Field, was the original athletic field. (Aside: Brown was in--and lost--the first Rose Bowl game.) Pass through Soldiers Arch, memorializing Brown men and women who died in military service. <br />
***Thayer Street. The 14-story concrete monolith to your left (a much-maligned example of the brutalist style of the 1970's) is the Sciences Library. Nice view from the upper floors; on the 13th floor look south to see Narragansett Bay. You might want to visit our newish 24-hour Friedman Study Center on the lower level--hugely popular with students. Beyond it, to the north, are several blocks of restaurants and shops, Providence's mini-version of Harvard Square. But go south instead.<br />
***Power Street.<br />
* History<br />
* Trivia<br />
* [http://travel.nytimes.com/2008/08/03/travel/03hours.html "36 Hours in Providence, R.I."] piece in the New York Times TRAVEL section from August, 2008.<br />
<br />
== iPhone / iTouch Wireless Info ==<br />
To connect with the ibahn_conf wireless on iPhone or iTouch, you need to call the iBahn Conference Technical Support at 877-787-6266. It is best to have the main hotel phone # to reference: 401-919-5000.<br />
<br />
To connect with the guest room ibahn wireless, you need to call from your room to the iBahn Technical Support number found on the card on the desk.<br />
<br />
== Ground Crew Contacts ==<br />
Please feel free to contact us about anything, any time, between now and the end of the conference.<br />
* Birkin James Diana, birkin_diana@brown.edu, cell 401-378-8246<br />
* Bonnie Buzzell, bonnie_buzzell@brown.edu, cell 401-487-0245<br />
* Jean Rainwater, jean_rainwater@brown.edu, cell 401-241-0098</div>Timmcgeary