Code4Lib - User contributions [en]

North

2012-05-25T13:35:11Z

Shadowspar: /* hashtag and twitter list */

Welcome to the home of the new Ontario/Canada chapter of [http://code4lib.org/ Code4Lib]. Our aim is to create more opportunities for Code4Lib folks in the Ontario/Quebec/Manitoba/Northeast USA area to meet up in person.

==Mailing list==

Want to participate in Code4Lib North meetups and receive "North"-oriented Code4Lib announcements? Join the code4lib mailing list. (The code4lib-north mailing list was discontinued.)

== Third Meeting: University of Windsor, May 24 and 25th, 2012 ==

[[Image:code4libnorth.png|code4libnorth logo]]

=== Schedule ===
The schedule has now been moved to an editable google doc at : http://led.uwindsor.ca/c4ln otherwise known as: https://docs.google.com/document/d/1dlTqrBNfiYwjRpVnUvJbtW0K7en1ndVp84WqWbfOrvE/edit

=== Cost ===
This unconference runs on love... and the kindness of the Leddy Library who will provide : coffee, lunch, and wireless and the space

=== When and Where ===
Dates: May 24 and 25th, 2012 (it's on!)
 
Times: 9 am start time. 4 pm end time
 
Location: 4th Floor, Leddy Library, University of Windsor: http://www.uwindsor.ca/
Google Map: http://tinyurl.com/7a79qvw
 
Contact: mita@uwindsor.ca
 

=== Accommodation ===
The University offers rooms and suites for travellers, youth, and families seeking overnight, short or extended accommodations through its [http://www.conferences.uwindsor.ca/accommodations-for-individuals-and-families Conference Services: description of services provided]. Use this [https://web4.uwindsor.ca/units/AEC/Hospitality/conferenceServices/Registrations.nsf/CODE4LIBNorth?OpenForm Registration Form] to book a room with Conference Services.
 
 
In addition, University of Windsor special visit rates may be available by calling the local number and asking for the University of Windsor rate at certain hotels (which shouldn't dissuade you from staying wherever you prefer):
 
 
[http://his-windsor.com/ Holiday Inn Select]
1855 Huron Church Road, Windsor
Tel: 1-800-465-4329 or 519-966-1200 (3 km from campus)
 
[http://hamptoninn.hilton.com/en/hp/hotels/index.jhtml?ctyhocn=YQGCNHX Hampton Inn & Suites]
1840 Huron Church Road, Windsor
Tel: 800-Hampton or 519-972-0770 (3 km from campus)
 
[http://www.qualityinn.com/hotel-windsor-canada-CN317 Quality Suites Downtown]
250 Dougall Ave., Windsor
Tel: 519-977-9707 (3 km from campus)
(frequently used hotel for participants in [http://projectconifer.ca Conifer] hackfests)
 
[http://www.ceasarswindsor.com/ Caesars Windsor]
377 Riverside Dr. East, Windsor
Tel: 800-991-8888 (3 km from campus)
 
[http://www.windsorriversideinn.com/ The Windsor Riverside Inn]
333 Riverside Dr. West
Tel: 519-977-9777 (2 km from campus)
 
[http://www.travelodge.ca/hotel-search/list/windsor/all/ Travelodge Hotel Windsor Downtown Windsor]
33 Riverside Dr. East
Tel: 519-258-7774 (3 km from campus)
 

There are no bed and breakfasts in the immediate area but the [http://www.bbcanada.com/ontario/southwestern_ontario/windsor Argyle and Olde Walkerville Bed and Breakfasts] are a bus ride away.

=== Social Events ===

There's nothing formal planned but on Wednesday and Thursday nights, we'll try to informally coordinate places to have supper together.
 

I suggest that those around on Wednesday night meet up at the [http://www.rockbottom.ca/ Rock Bottom Grill] at 3236 Sandwich Street, Windsor. It will busy because it's "2 for 1 Wing Night" but it should be worth it.

 
For those who love experimental film, there is the [http://mediacityfilmfestival.com/films-and-schedule-2012/ Media City Film Festival] taking place in Windsor and Detroit. Jason Scott aka textfiles will be speaking at the [http://www.aadl.org/events/list?id=14190 Ann Arbor Public Library] on Wednesday night
 

=== Food ===
We will be providing lunch and snacks. (please email organizers if you have a dietary restriction - we will be ordering vegetarian options but we want to make sure we have enough!)
 
Generally folks informally gather for supper.
 
Here are some of our nearby options:
[http://www.windsoreats.com/rest_search.php?rest_location=Windsor%20-%20West%20Windsor WindsorEats: Windsor West]
 
But there is much more if we wander farther afield: [http://www.windsoreats.com/ WindsorEats]
 
Near the university on Wyndotte Street are various Asian dining options including:
* [http://www.restaurantica.com/on/windsor/eros-restaurant/23004000/ Eros Restaurant]
* [http://www.urbanspoon.com/r/19/1482082/restaurant/Detroit/Windsor-Seoul-Windsor Windsor Seoul]
* [http://www.urbanspoon.com/r/19/1648665/restaurant/Detroit/Bibim-To-Go-Windsor Bibim-To-Go]
* [http://www.urbanspoon.com/r/19/1549919/restaurant/Detroit/Hoi-Sushi-Windsor Hoi Sushi]
 
And here's a list of places that could probably fit 40 people:
* [http://www.urbanspoon.com/r/19/1549919/restaurant/Detroit/Hoi-Sushi-Windsor Hoi Sushi]
* [http://www.urbanspoon.com/r/19/1426344/restaurant/Detroit/Bubis-Awsome-Eats-Windsor Bubis Awesome Eats]
* [http://www.urbanspoon.com/r/19/1435280/restaurant/Detroit/Hurricanes-Windsor Hurricane's]

=== Format ===

A combination of 20 talks, 5 minute lightning talks, an Ask Anything session, workshops / hackfest time. We will try to find time for everyone who wants to present!
 
We have talks in the morning and hackfests in the afternoon. We will finalize the speaking schedule Thursday morning but we will try to split the talks between the two days equally.

=== 20 minutes talks :: feel free to sign up ===

{| border=1
! Name
! Title
|-
| Ted Lawless || easyArticle - streamlining access to library materials with OpenURL, automated interlibrary loan submission, vendor APIs, Django/Python.
|-
| Mita Williams || my sekret art project
|-
| John Fink and Warren Layton|| Embedded Hardware Hijinx
|-
| Alison Hitchens || RDA for coders/systems folk
|-
| Andrew McAlorum || Our favorite jQuery modules for Drupal 7
|-
| David Fiander || The state of the ebook marketplace
|-
| Dan Chudnov || backplane
|-
| William Denton || Having provocative fun with reference desk statistics in R
|}

=== 5 minutes talks :: feel free to sign up ===

{| border=1
! Name
! Title
|-
| Nick Ruest || Other Redmine uses
|-
| Tim Ribaric || Circumvention using the Cloud?
|-
| Alison Hitchens || #catcode: Cataloguers embrace Code Year
|-
| Mita Williams || "My god, it's full of stars! lists": building the library website that will incorporate [http://librarian.newjackalmanac.ca/2011/05/code4lib-north-presentation-were-jamun.html Jamun.]
|-
| Dan Chudnov || occupy 1923
|-
| Graham Fawcett || A Web-based video annotation tool (for peer review, possibly captioning, maybe for some nefarious library uses we haven't imagined)
|}

=== 20 or 40 minute workshops: each one teach one ===

:: a workshop you are willing to lead
::* Intro to Git, if demand warrants -- if not, no big deal (John Fink)
::* Environmental monitoring on the cheap (Doug Sartori)
::* (I program in a few languages, and could do a teaser-session on one of them if there's interest. Maybe [http://www.python.org Python], [http://www.haskell.org/ Haskell], [http://clojure.org/ Clojure] or [http://dlang.org D]?) (Graham Fawcett)
::* [[C4LN 2012: Intro to the Twitter API|Intro to the Twitter API]], including how one might use it to make a Twitter bot ([[User:shadowspar|Rick Scott]])

:: a workshop of what you would love to attend
::* intro to IRC, meet zoia (Mita, Warren, Sarah, John F)
::* how to create a twitter bot (Mita, John F, David F)
::* intro to Git (Warren, Sarah, David F)

=== hackfest ideas :: scheme schemas ===
- build your own twitter bot; bot battles

=== hackfest ideas :: feel free to add to the list ===
*twitter bot war with code4lib The Great Eastern? http://wiki.code4lib.org/index.php/GreatEastern
*changing Odessi XML records to MARC XML so OCUL libraries can load MARC for Odessi, esp. Stats Can stuff. We started this project at TUG, so need someone to help me get further or finish! New note: Chris put what he did so far on [https://github.com/lib-uoguelph-ca/ddi2marc-xml github](Alison)
*[http://twitter.com/CanadianPoetry @CanadianPoetry] Sprint: [http://library.utoronto.ca/canpoetry Canadian Poetry Online] needs an overhaul! Canadian Poetry is a web anthology of contemporary Canadian poetry, providing biographies and full-text poems from Canada's leading poets. Join in this [http://drupal.org/node/247982 code sprint] to help with the migration to Drupal, site building, development, and theming of the new version. (Andrew)
*[http://www.jasongriffey.net/librarybox/ LibraryBox] is a customized version of PirateBox that can run be run on the inexpensive TP-Link MR 3020. Currently, it acts as a simple file server but it could potentially offer a more library-focused service, such as [https://twitter.com/#!/djfiander/status/184315493157576704 an eBook server for nearby devices using OPDS]. (Warren)
* [http://evergreen-ils.org/ Evergreen]: The Evergreen project is currently recruiting volunteers for the Google Summer of Code effort and has [http://evergreen-ils.org/dokuwiki/doku.php?id=dev:summer_of_coding_ideas#project_ideas a list of project ideas]. Some of these ideas, if not already claimed by a student GSoC participant, might make for interesting hackfest projects. Or we could rewrite the MARC editor in Dojo.
* [https://github.com/wdenton/splurge/ SPLURGE]: The Scholars Portal Library Usage-Based Recommendation Engine began at a hackfest in February and has been worked on since then, but it needs one last push to get all of the pieces joined together so that an easy-to-use "people who borrowed this also borrowed that" service built on shared circ data can be tested. There are four parts to SPLURGE: data cleanup, getting it into a properly configured database, a web service that talks to the database, some Javascript that can dropped into a catalogue to talk to the web service. They all exist, but not all of them are quite done and they don't all talk to each other. The purpose of this hackfest project would be for people to familiarize themselves with the work that's been done, and then try to finish it up.

=== code4lib north organizational team ===
*Mita Williams
*Karen Pillon
*Peter Zimmerman
*Jennifer Soutter
*Cathy Maskell
*Ranti Junus (Michigan State)

=== hashtag and twitter list ===
*c4ln2012
*c4ln
*https://twitter.com/#!/copystar/c4ln

== Code4lib North Meetups in Ottawa ==

'''Purpose:''' To connect with other code4libbers in the area and start building a code4lib community in Ottawa, Ontario

===Next Meetup===

The next meetup is scheduled for Wednesday June 13th 2012 at 5pm (we'll take May off for code4lib North in Windsor). Once again, we'll be in the private room downstairs in The Exchange Pub.

As usual, please bring your laptops, tablets, demos, problems, and topics of discussion. Beginners are always welcome!

Those interested in attending or speaking can e-mail warren.layton@gmail.com for more information and (if not on the code4lib mailing list) to be kept informed of future events.

===Past Meetups===

The inaugural code4lib Ottawa meetup occurred on March 28, 2012 and was a simple meet-and-greet at a local pub. Since then, we try to combine this social event with some short interesting talks. Here is what we have learned about in recent meetups:

'''April 24, 2012 - Show and Tell Session'''
{| border=1
! Presenter
! Description of Talk
|-
| [http://twitter.com/maxneuvians Max Neuvians] || [http://social-biblio.ca/ Social-biblio.ca] : An approach to Twitter data visualization, archiving, and the larger narrative.
|-
| [http://twitter.com/scilib Richard Akerman] || [http://twitter.com/scilib Richard Akerman] and [http://twitter.com/bethmaru Mary Beth Baker] are organizing a Reading Garden at the upcoming Canadian Library Association conference. They are seeking advice on how to provide wireless access. Anyone with ideas is encouraged to get in touch with them.
|-
| [http://twitter.com/warlayton Warren Layton] || A quick demo of [http://www.jasongriffey.net/librarybox/ LibraryBox], a wireless filesharing device, which may have interesting applications in government and other libraries where IT restrictions can limit network use.
|}

== Second Meeting: McMaster University, May 5-6, 2011 ==

=== Sign Up ===
We can handle a maximum of 50 people and you can signup here: http://c4ln2011.eventbrite.com/.

=== When and Where ===
Dates: May 5-6, 2011
 
Location:
* 1280 Main St. West, [http://www.google.com/maps/place?cid=4151756913136304412&q=mcmaster+university+mills+memorial+library&hl=en&dtab=0&sll=43.260928,-79.91933&sspn=0.773056,1.227722&ie=UTF8&ll=43.647007,-80.532532&spn=0,0&z=10 McMaster University, Hamilton, Ontario - ] (map)
* Mills Memorial Library, [http://library.mcmaster.ca/lyons Lyons New Media Centre] (4th floor)

=== Accommodation ===
Our helpful folks in Research Collections put this [http://library.mcmaster.ca/archives/visiting guide] together a while back.

=== Parking, Campus Map, Public Transit ===
* [http://parking.mcmaster.ca/ Parking] - I understand we have the most expensive parking in OCUL. I'm sorry :( - There is one bit of good news: if you park in the M lot, the day rate drops from $20 to $5. The M lot is about a 10-12 minute walk from the library, and there is a shuttle that will take you part of the way.
* [http://parking.mcmaster.ca/June25UpdatedMapWithAutomation.PDF Campus map] - we are building #10 - Mills Memorial Library
* [http://www.hamilton.ca/CityServices/transit?WT.mc_id=hsr&WT.hamilton_redirect_friendly=1/ Public Transit]
* HSR buses that come to campus are: [http://www.hamilton.ca/NR/rdonlyres/F831E17F-2373-48C8-A808-F7DB7873400E/0/JA11Route1.pdf 1], [http://www.hamilton.ca/NR/rdonlyres/FB34FB4E-EF3A-4154-AF2D-46C06F05F06F/0/JA11Route51.pdf 51], [http://www.hamilton.ca/NR/rdonlyres/53F0A87E-6DA9-4E04-A6A6-6BF5E7482806/0/JA11Route5.pdf 5c], [http://www.hamilton.ca/NR/rdonlyres/B25032CD-ABC4-40D3-8509-FA6CCB7DB4CA/0/JA11Route52A.pdf 52], and [http://www.hamilton.ca/NR/rdonlyres/650AA6C2-DD5F-422F-86A6-E0D6EA688CEE/0/JA11Route10.pdf 10] - The 10 and 52 drop off by the hospital, the others drop off right outside Mills.

=== Cost ===
Keep with tradition set last year - No cost and McMaster University has tentatively agreed to provided coffee, lunch, space, and wireless.

=== Format ===
Day 1:
* Hackfest (send problems/proposals to John Fink and Nick Ruest)
Day 2
* 5-minute lighting talks
* 20-minute talks
* BOAF/breakouts

=== 20-minute talks ===
I'd like to start a new tradition with Code4Lib North and deposit the slides and *maybe* recordings of the presentations in our IR. If people are cool with this, I can get it all setup prior to the event.

{| border=1
! Name
! Title
|-
| William J Turkel || [http://digitalcommons.mcmaster.ca/c4ln/9/ Functional Programming Workout]
|-
| Dileshni Jayasinghe & Majid Valipour || [http://digitalcommons.mcmaster.ca/c4ln/8/ Programming at Scholars Portal: apps and APIs]
|-
| William Wueppelmann || [http://digitalcommons.mcmaster.ca/c4ln/1/ The Canadiana Web API]
|-
| Dan Chudnov || [http://digitalcommons.mcmaster.ca/c4ln/7/ WWIC? Linked Library Data as a Customer Service Medium]
|-
| Mita Williams || [http://digitalcommons.mcmaster.ca/c4ln/3/ We're jamun (and we hope you like jamun too)]
|-
| William Denton || [http://digitalcommons.mcmaster.ca/c4ln/10/ Getting started with R]
|-
| Alan Harnum || [http://digitalcommons.mcmaster.ca/c4ln/5/ When All You Have Is XSLT, Everything Looks Like XML: Heterogeneous Cloud-Based Content Management Using Google Docs and Other Services]
|-
| Wendy Huot || [http://digitalcommons.mcmaster.ca/c4ln/12/ Why can't a web page be more like a book? Using LaTeX with Readability to generate better 'print friendly' versions of web pages]
|-
| Chris Charles || [http://digitalcommons.mcmaster.ca/c4ln/11/ Introduction to Google Refine]
|-
| Karen A. Coombs || [http://digitalcommons.mcmaster.ca/c4ln/2/ Zend Framework: making using web services easier]

|}

=== 5-minute lighting talks ===

{| border=1
! Name
! Title
|-
| Andrew McAlorum || [http://digitalcommons.mcmaster.ca/c4ln/4/ Transition to Unity]
|-
| Dale Askey || [http://digitalcommons.mcmaster.ca/c4ln/6/ Fun with Failure, or, Learning to Stick a Fork in Things]
|-
| Alison Hitchens || [http://digitalcommons.mcmaster.ca/c4ln/13/ Getting testers to test what you need to have tested!]
|-
| Alison Hitchens || [http://digitalcommons.mcmaster.ca/c4ln/13/ Using RT Tracker for user feedback]
|}

== First Meeting: Kingston ON, May 6-7, 2010 ==

=== Sign up ===

Free registration -- but registration is now closed (we have 40+ signed up).

=== When and Where ===

'''May 6-7, 2010'''
* Thursday: 2pm-5:30pm, followed by dinner and drinks
* Friday: 9am-4:30pm

Meeting location:
* [http://maps.google.com/maps/ms?hl=en&ie=UTF8&oe=UTF8&source=embed&msa=0&msid=103786326471006763157.0004700577498a9166e33&ll=44.227888,-76.494584&spn=0.009226,0.012875&z=15| 93 University Ave, Queen's University, Kingston Ontario] (map)
* Meeting room: [http://library.queensu.ca/library/floorplans/index.php?library=Douglas&floorpos=4F&section=North_Reading_Room#map| 1966 North Reading Room, Level 7, Douglas Library Building] (floorplan) - located on the top floor, just follow the signs to find the room.

=== Cost ===

There was no charge. Queen's University very generously supplied the space, the Internet connection, and free lunch on Friday!

=== How to get involved ===

Join the mailing list. That is where the planning will happen.

=== Format ===

* 5-minute lighting talks
* 20-minute talks
* BOAF sessions
* Maybe a hackfest.

=== How many are attending? ===

45 people have registered. Most will be attending.

=== Program ===

'''Thursday May 6:'''

* 2pm-5pm: Open format (hang out and hack)
* Evening: Go out for dinner and drinks

'''Friday:'''

* 9am-4:30pm: Schedule currently "under construction" -- see table below.

Morning Break: 10:30-10:45 .... Lunch: 12-1 ....

Afternoon: 5 minute lightning talks .... "Birds of a feather" breakout sessions (sign up sheets on front table)

{| border=1
! Name
! Description
|-
| William Denton || OpenFRBR
|-
| Walter Lewis || Exposing Linked Data
|-
| Art Rhyno || Open Layers and Newspapers (Walter Lewis)
|-
| MJ Suhonos || [http://mytpl.ca Location-aware Mobile Search]
|-
|Alan Harnum || Building A [http://beta.torontopubliclibrary.ca/ Library Website] with [http://www.endeca.com/ Endeca] technology
|-
|Wendy Huot || "Your feedback, please": library web design critique
|-
|Glen Newton || [http://zzzoot.blogspot.com/2009/07/project-torngat-building-large-scale.html Using Open Source Tools for Visualization and Semantic Mapping in a Large Scale Article Digital Library]
|-
| Eric Palmitesta || XQuery
|-
| John Miedema || [http://code.google.com/p/openbook4wordpress/wiki/index OpenBook WordPress Plugin Update - Why It's Cool to Love OpenURL +++]
|-
|Nasser Saleh || Coagmento!: a potential collaborative search tool
|}

== Who's interested in Code4Lib North? ==

Declare your interest in a Code4lib North chapter:

* Wendy Huot, Queen's University
* Michael Vandenburg, Queen's University
* [http://www.miskatonic.org/ William Denton], York University
* John Fink, McMaster University
* [http://ruebot.net/ Nick Ruest], [http://digitalcollections.mcmaster.ca/ McMaster University]
* Walter Lewis, Halton Hills/OurOntario
* Edward Corrado, Binghamton University (NY, USA)
* [http://thebookpile.wordpress.com Warren Layton], Library of Parliament (Ottawa)
* Pascal Calarco, University of Notre Dame (IN, USA)
* Rob Fox, University of Notre Dame (IN, USA)
* Mita Williams, University of Windsor
* John Fereira, Cornell University
* MJ Suhonos, Toronto Public Library
* Dianne Dietrich, Cornell University
* David Fiander, University of Western Ontario
* Peter Schlumpf, [http://www.avantilibrarysystems.com/ Avanti Library Systems]
* Roy Zimmer, Western Michigan University
* Kimberly Silk, Martin Prosperity Institute, University of Toronto
* Andrew Darby, Ithaca College (Ithaca, NY)
* Laura Harris, Grand Valley State University (western Michigan)
* Tim Ribaric, Brock University
* Sibyl Schaefer, University of Vermont
* Peter Ellinger, Ontario Legislative Library, Toronto
* Keith Jenkins, Cornell University
* [http://pmlozeau.ca/ Patrick M. Lozeau]
* Mike Kreyche, Kent State University
* Graham McCarthy, [http://www.ryerson.ca/library/ Ryerson University]
* [http://johnmiedema.ca John Miedema]
* Janey Chen, Ontario Legislative Library, Toronto
* Rob McDonald, Carleton University
* Amy Buckland, McGill University
* Tricia Williams (pgwillia), Consultant/[http://search.ourontario.ca OurOntario]
* Mike Beccaria, Paul Smith's College (Paul Smiths, NY)
* Amanda Etches-Johnson, McMaster University
* Art Rhyno, University of Windsor
* [http://bethmaru.com Mary Beth Baker], CIC (Ottawa)
* Wayne Schneider, Hennepin County Library
* Carol Serroul, CISTI
* Graham Stewart, University of Toronto Libraries
* Peter Zimmerman, University of Windsor
* Margaret Kipp, University of Wisconsin Milwaukee
* [http://coffeecode.net Dan Scott], Laurentian University
* Lawrence Wardroper (Courts Administration Services Library, Ottawa)
* Matt McCollow, McMaster University
* [http://www.parser.ca/z678/ George Duimovich], NRCan Library (Ottawa)
* [mailto:bobbi_fox@harvard.edu Bobbi Fox], Harvard University Library (Massachusetts)
* Dileshni Jayasinghe, OCUL, University of Toronto
* Eric Palmitesta, OCUL, University of Toronto
* [http://twitter.com/alxp Alexander O'Neill], Robertson Library, University of Prince Edward Island
* Chris Beer, WGBH (Massachusetts)
* Robin Isard, Algoma University (Sault Ste Marie ON)
* Pat Moore, Carleton University (Ottawa ON)
* [http://wagathon.tumblr.com/ Alan Harnum], Toronto Public LIbrary (Toronto ON)
* Colin Prince, University of Toronto Libraries
* Tom Keays, Syracuse University LIbrary (Syracuse, NY)
* Chris Charles, University of Guelph (Guelph, ON)
* John MacGillivray, Carleton University (Ottawa ON)
* Lester Webb, Kingston Frontenac Public Library (Kingston ON)
* Elizabeth Goldman, Kingston Frontenac Public Library (Kingston ON)
* Jennifer O'Donnell, Kingston Frontenac Public Library (Kingston ON)
* David Smith, Kingston Frontenac Public Library (Kingston ON)
* Loren Fantin, Our Ontario,Knowledge Ontario
* Daulton Theodore, Carleton University (Ottawa, ON)
* Peter MacDonald, Hamilton College (Clinton, NY)
* Rebecca Larocque, North Bay Public Library (North Bay, ON)
* Doris Rankin, Library and Information Management Consultant, Ottawa, ON
* Diane Bédard, Learn Ontario & Our Ontario; Knowledge Ontario
* [http://www.arts.uottawa.ca/eng/avellino.html Andre Vellino], CISTI / University of Ottawa
* [http://twitter.com/markswartz Mark Swartz], Queen's University
* Adam Wead, Rock and Roll Hall of Fame Library and Archives (Cleveland, OH)
* Pramila Thakur, Ontario Legislative Library, Toronto
* Anthony Petryk, University of Ottawa
* Jan Dawson, Ask Ontario, Knowledge Ontario
* [http://lab.cisti-icist.nrc-cnrc.gc.ca/cistilabswiki/index.php/Glen_Newton Glen Newton], Carleton University
* Patrick McMaster, Leeds & the 1000 Islands, Rideau Lakes, and North Grenville Public Libraries
* Nasser Saleh, Queen's University (Kingston ON)
* [http://stefansinclair.name/ Stéfan Sinclair], McMaster University
* [http://williamjturkel.net/ William J Turkel], University of Western Ontario
* Shirley Lew, [http://library.vcc.ca/ Vancouver Community College], (Vancouver BC)
* [http://twitter.com/edbilodeau Edward Bilodeau], [http://www.mcgill.ca/library/ McGill University]
* Andrew McAlorum, University of Toronto Libraries

== Meeting Location Suggestions for the Future ==

* Toronto, Ontario
* Sudbury, Ontario
* Ottawa, Ontario
* Montreal, Quebec

C4LN 2012: Intro to the Twitter API

2012-05-24T16:27:13Z

Shadowspar: ws

Presenter: [[User:Shadowspar|Rick Scott]] - [http://twitter.com/shadowspar @shadowspar]

== API Overview ==

'''https://dev.twitter.com/docs is the main documentation area''' -- you'll spend a lot of time here =)

Other useful things:

* https://dev.twitter.com/ is API central. Amongst other things, it links to:
** [https://dev.twitter.com/status API Status]
** [https://dev.twitter.com/issues API Known Issues]
** API blog, discussion, etc etc

=== Parts ===

* the '''REST API'''
* the '''Streaming API'''
* the '''Search API'''

==== REST API ====
* query→response based access
* the mainstay of the API; the first part of it you'll want to be concerned with, and the part you'll likely use most

==== Streaming API ====
* aka ''drinking from the firehose'' =)
* persistent connection
* push-based communication w/ v.high ratelimit (1% of ''all tweets'')

==== Search API ====
* just like it says on the tin
* also trending topics

== Find your library ==

https://dev.twitter.com/docs/twitter-libraries has a good list

* Perl: [http://search.cpan.org/dist/Net-Twitter Net::Twitter]
* Python: [https://github.com/tweepy/tweepy tweepy] and many others
* Ruby: [https://github.com/jnunemaker/twitter twitter] rubygem and others

== Creating a new app ==

=== BEFORE creating an app: Bot-specific stuff ===

If you're going to have a separate twitter account for your bot, the best thing to do is to create that account ''before you create your app''. Then create your new app under ''under the bot's account''. This will simplify doing the OAuth dance below.

=== First steps to create an app ===
* https://dev.twitter.com/apps/new
* sign in with your twitter (bot's) account
* fill out basic info about your app
* agree to be a good citizen, as detailed below

Huzzah! You have your very own app!

=== A brief segue into OAuth ===

http://hueniverse.com/oauth/guide/intro/

OAuth metaphor: ''valet key'' to your car
* lets an app act on behalf of a user when dealing with some service
* lets a user give an app specific permissions to interact with a service on their behalf

Roles in OAuth:
* consumer (client) -- ''your app''
* service provider (server) -- ''Twitter''
* user (resource owner) -- ''user''

Credentials
* consumer credentials (consumer key & consumer secret)
* access credentials (access token & access secret)
* (also request token & secret)

OAuth workflow:
* user goes to server and says they'd like to authorize application ''X'' to do action ''Y''
* server generates access token which represents the combination of the specific app & the specific user & the specific level of access the user has granted to that app
* user feeds the access token to the app
* the app can then present the access token to the server (in combination with its consumer credentials) and be permitted to do whatever's been authorized

=== Set up the App ===

After you've set up your app, you receive your OAuth consumer keys for the app:

* '''<tt>consumer_key</tt>'''
* '''<tt>consumer_secret</tt>'''

The first thing you're going to want to do is go into your app settings and set the correct level of access that your app is going to request from users. This is under the '''Settings''' tab:

* Application type:
** Read
** Read/Write
** Read/Write/Access DMs

You are probably going to want one of the latter two. Which one depends on whether or not your app is going to work with DMs (direct messages) or not.

You can also fill in the rest of the self-explanatory fields in the Details and Settings tabs as you like (organization, etc).

=== Authorize the App on your Bot's Account ===
While still logged in under the bot's account, navigate to the app's page and generate your access token:

Details tab → Your Access Token ''*click*''

Now your bot's twitter account has granted authorization to your app to act on its behalf. You'll that the relevant access token credentials have been created:

* '''<tt>access_token</tt>'''
* '''<tt>access_token_secret</tt>'''

== Getting started on the code ==

Each Twitter API library is going to have its own way to get initialized and set up. Usually it's going to start with creating an object to represent your connection to Twitter and feeding it ALL THE KEYS.

my $twitter = Net::Twitter->new(
traits => [qw/API::REST OAuth/],
consumer_key => $conf{'consumer_key'},
consumer_secret => $conf{'consumer_secret'},
access_token => $conf{'access_token'},
access_token_secret => $conf{'access_token_secret'},
);

...and then you'll be able to use the library methods to do the things that you might want to do.

== Rules of the Road ==

=== General Rules of Conduct and TOS ===

* https://dev.twitter.com/terms/api-terms
* https://support.twitter.com/articles/76915 - automation rules and best practices

=== Rate limits ===

Twitter has a very, very load/performance-centric outlook on the world because of the massive amounts of data and requests they deal with. If you don't play by the rules, twitter has absolutely no hesitation in going [http://i.imgur.com/bf1Xu.jpg NO SOUP FOR YOU].

* REST api is limited to...
** 350/reqs per hour ''per signed-in account''
** 150/reqs per hour ''per anonymous IP address''

Things that '''do''' count against your limit
* pretty much anything that involves hitting the REST API: fetching tweets from your timeline, fetching user profiles, fetching your @-replies, getting a list of followers, whatever.

Things that '''do not''' count against your limit (but see below)
* publishing status updates (sending tweets)
* sending direct messages
* following and unfollowing
* checking the rate limit by querying <tt>account/rate_limit_status</tt>
** it can change, though nowadays it rarely does
** note also that you get three headers describing how quickly you're nomming through your ratelimit as part of every REST API reply, eg:
*** <tt>X-RateLimit-Limit: 350</tt>
*** <tt>X-RateLimit-Remaining: 350</tt>
*** <tt>X-RateLimit-Reset: 1277485629</tt>

Other, service-specific limits
* 1,000 tweets per day
* 250 DMs per day
* follow limits: +1,000 per day plus additional monitoring once you hit 2,000 followed users

=== Other gotchas ===

* '''Repeated tweets'''
** You can't post a tweet that's an exact duplicate of any of your last few tweets. "Whoops! You already tweeted that!"
* '''Failed requests'''
** Twitter does crap out every now and again due to load or whatever other reason, so you need to watch for failures and catch the resulting exceptions. [500/502/503/504]

* [https://dev.twitter.com/docs/error-codes-responses HTTP responses / error codes] ''are'' meaningful and you must honour them in your bot's behaviour. In particular:
** '''400''' means you've hit the ratelimit on the REST API
** '''420''' means you've hit the ratelimit on the Search or Streaming API
** '''403''' means you've hit update (tweeting) limit.

== General things you may want to do ==

=== Tweet updates from elsewhere ===

twitter = TwitterConnection.new()

at (interval) {
msg = fetch_external_resource;
msg.truncate_to_140_chars;
twitter->update(msg)
}

=== Check for @-messages and reply ===

twitter = TwitterConnection.new()

mentions = twitter->mentions( since_id => last_mention )

at (interval) {
foreach mention in mentions {
mention.parse
mention.reply
last_mention = mention.id
}
}

sub reply(mention) {
msg = fetch_external_resource()

msg = '@' + mention.sending_user->screen_name + ' ' + msg
msg.truncate_to_140_chars
twitter->update(msg, in_reply_to => mention)
}

== Example: inetkami ==

* Twitter account: [http://twitter.com/inetkami @inetkami]
* Code: https://github.com/rickscott/inetkami

What it does: fetches, on request:
* [http://en.wikipedia.org/wiki/METAR METAR] (terse weather condition reports intended for aviators)
* [http://apps.cbp.gov/bwt/ Border Wait Times]

== Other Miscellany ==

* [http://www.readwriteweb.com/hack/2012/05/a-utility-that-makes-you-master-of-the-twitterverse.php t], a Ruby command-line interface to the Twitter API

C4LN 2012: Intro to the Twitter API

2012-05-24T16:24:59Z

Shadowspar: +getting started on code

C4LN 2012: Intro to the Twitter API

2012-05-24T16:05:49Z

Shadowspar: /* API Overview */

Presenter: [[User:Shadowspar|Rick Scott]] - [http://twitter.com/shadowspar @shadowspar]

== API Overview ==

'''https://dev.twitter.com/docs is the main documentation area''' -- you'll spend a lot of time here =)

Other useful things:

* https://dev.twitter.com/ is API central. Amongst other things, it links to:
** [https://dev.twitter.com/status API Status]
** [https://dev.twitter.com/issues API Known Issues]
** API blog, discussion, etc etc

=== Parts ===

* the '''REST API'''
* the '''Streaming API'''
* the '''Search API'''

==== REST API ====
* query→response based access
* the mainstay of the API; the first part of it you'll want to be concerned with, and the part you'll likely use most

==== Streaming API ====
* aka ''drinking from the firehose'' =)
* persistent connection
* push-based communication w/ v.high ratelimit (1% of ''all tweets'')

==== Search API ====
* just like it says on the tin
* also trending topics

== Find your library ==

https://dev.twitter.com/docs/twitter-libraries has a good list

* Perl: [http://search.cpan.org/dist/Net-Twitter Net::Twitter]
* Python: [https://github.com/tweepy/tweepy tweepy] and many others
* Ruby: [https://github.com/jnunemaker/twitter twitter] rubygem and others

== Creating a new app ==

=== BEFORE creating an app: Bot-specific stuff ===

If you're going to have a separate twitter account for your bot, the best thing to do is to create that account ''before you create your app''. Then create your new app under ''under the bot's account''. This will simplify doing the OAuth dance below.

=== First steps to create an app ===
* https://dev.twitter.com/apps/new
* sign in with your twitter (bot's) account
* fill out basic info about your app
* agree to be a good citizen, as detailed below

Huzzah! You have your very own app!

=== A brief segue into OAuth ===

http://hueniverse.com/oauth/guide/intro/

OAuth metaphor: ''valet key'' to your car
* lets an app act on behalf of a user when dealing with some service
* lets a user give an app specific permissions to interact with a service on their behalf

Roles in OAuth:
* consumer (client) -- ''your app''
* service provider (server) -- ''Twitter''
* user (resource owner) -- ''user''

Credentials
* consumer credentials (consumer key & consumer secret)
* access credentials (access token & access secret)
* (also request token & secret)

OAuth workflow:
* user goes to server and says they'd like to authorize application ''X'' to do action ''Y''
* server generates access token which represents the combination of the specific app & the specific user & the specific level of access the user has granted to that app
* user feeds the access token to the app
* the app can then present the access token to the server (in combination with its consumer credentials) and be permitted to do whatever's been authorized

=== Set up the App ===

After you've set up your app, you receive your OAuth consumer keys for the app:

* '''<tt>consumer_key</tt>'''
* '''<tt>consumer_secret</tt>'''

The first thing you're going to want to do is go into your app settings and set the correct level of access that your app is going to request from users. This is under the '''Settings''' tab:

* Application type:
** Read
** Read/Write
** Read/Write/Access DMs

You are probably going to want one of the latter two. Which one depends on whether or not your app is going to work with DMs (direct messages) or not.

You can also fill in the rest of the self-explanatory fields in the Details and Settings tabs as you like (organization, etc).

=== Authorize the App on your Bot's Account ===

While still logged in under the bot's account, navigate to the app's page and generate your access token:

Details tab → Your Access Token ''*click*''

Now your bot's twitter account has granted authorization to your app to act on its behalf. You'll that the relevant access token credentials have been created:

* '''<tt>access_token</tt>'''
* '''<tt>access_token_secret</tt>'''

== Rules of the Road ==

=== General Rules of Conduct and TOS ===

* https://dev.twitter.com/terms/api-terms
* https://support.twitter.com/articles/76915 - automation rules and best practices

=== Rate limits ===

Twitter has a very, very load/performance-centric outlook on the world because of the massive amounts of data and requests they deal with. If you don't play by the rules, twitter has absolutely no hesitation in going [http://i.imgur.com/bf1Xu.jpg NO SOUP FOR YOU].

* REST api is limited to...
** 350/reqs per hour ''per signed-in account''
** 150/reqs per hour ''per anonymous IP address''

Things that '''do''' count against your limit
* pretty much anything that involves hitting the REST API: fetching tweets from your timeline, fetching user profiles, fetching your @-replies, getting a list of followers, whatever.

Things that '''do not''' count against your limit (but see below)
* publishing status updates (sending tweets)
* sending direct messages
* following and unfollowing
* checking the rate limit by querying <tt>account/rate_limit_status</tt>
** it can change, though nowadays it rarely does
** note also that you get three headers describing how quickly you're nomming through your ratelimit as part of every REST API reply, eg:
*** <tt>X-RateLimit-Limit: 350</tt>
*** <tt>X-RateLimit-Remaining: 350</tt>
*** <tt>X-RateLimit-Reset: 1277485629</tt>

Other, service-specific limits
* 1,000 tweets per day
* 250 DMs per day
* follow limits: +1,000 per day plus additional monitoring once you hit 2,000 followed users

=== Other gotchas ===

* '''Repeated tweets'''
** You can't post a tweet that's an exact duplicate of any of your last few tweets. "Whoops! You already tweeted that!"
* '''Failed requests'''
** Twitter does crap out every now and again due to load or whatever other reason, so you need to watch for failures and catch the resulting exceptions. [500/502/503/504]

* [https://dev.twitter.com/docs/error-codes-responses HTTP responses / error codes] ''are'' meaningful and you must honour them in your bot's behaviour. In particular:
** '''400''' means you've hit the ratelimit on the REST API
** '''420''' means you've hit the ratelimit on the Search or Streaming API
** '''403''' means you've hit update (tweeting) limit.

== Getting started on the code ==

Each Twitter API library is going to have its own way to get initialized and set up.

== General things you may want to do ==

=== Check for @-messages and reply ===

=== Tweet updates from elsewhere ===

== Example: inetkami ==

* Twitter account: [http://twitter.com/inetkami @inetkami]
* Code: https://github.com/rickscott/inetkami

What it does: fetches, on request:
* [http://en.wikipedia.org/wiki/METAR METAR] (terse weather condition reports intended for aviators)
* [http://apps.cbp.gov/bwt/ Border Wait Times]

== Other Miscellany ==

* [http://www.readwriteweb.com/hack/2012/05/a-utility-that-makes-you-master-of-the-twitterverse.php t], a Ruby command-line interface to the Twitter API

C4LN 2012: Intro to the Twitter API

2012-05-24T16:04:53Z

Shadowspar: /* API Overview */

Presenter: [[User:Shadowspar|Rick Scott]] - [http://twitter.com/shadowspar @shadowspar]

== API Overview ==

'''https://dev.twitter.com/docs is the main documentation area''' -- you'll spend a lot of time here =)

* https://dev.twitter.com/ is API central.
* useful things linked from [https://dev.twitter.com/ dev.twitter.com]:
** [https://dev.twitter.com/status API Status]
** [https://dev.twitter.com/issues API Known Issues]
** blog, discussion, etc etc

=== Parts ===

* the '''REST API'''
* the '''Streaming API'''
* the '''Search API'''

==== REST API ====
* query→response based access
* the mainstay of the API; the first part of it you'll want to be concerned with, and the part you'll likely use most

==== Streaming API ====
* aka ''drinking from the firehose'' =)
* persistent connection
* push-based communication w/ v.high ratelimit (1% of ''all tweets'')

==== Search API ====
* just like it says on the tin
* also trending topics

== Find your library ==

https://dev.twitter.com/docs/twitter-libraries has a good list

* Perl: [http://search.cpan.org/dist/Net-Twitter Net::Twitter]
* Python: [https://github.com/tweepy/tweepy tweepy] and many others
* Ruby: [https://github.com/jnunemaker/twitter twitter] rubygem and others

== Creating a new app ==

=== BEFORE creating an app: Bot-specific stuff ===

If you're going to have a separate twitter account for your bot, the best thing to do is to create that account ''before you create your app''. Then create your new app under ''under the bot's account''. This will simplify doing the OAuth dance below.

=== First steps to create an app ===
* https://dev.twitter.com/apps/new
* sign in with your twitter (bot's) account
* fill out basic info about your app
* agree to be a good citizen, as detailed below

Huzzah! You have your very own app!

=== A brief segue into OAuth ===

http://hueniverse.com/oauth/guide/intro/

OAuth metaphor: ''valet key'' to your car
* lets an app act on behalf of a user when dealing with some service
* lets a user give an app specific permissions to interact with a service on their behalf

Roles in OAuth:
* consumer (client) -- ''your app''
* service provider (server) -- ''Twitter''
* user (resource owner) -- ''user''

Credentials
* consumer credentials (consumer key & consumer secret)
* access credentials (access token & access secret)
* (also request token & secret)

OAuth workflow:
* user goes to server and says they'd like to authorize application ''X'' to do action ''Y''
* server generates access token which represents the combination of the specific app & the specific user & the specific level of access the user has granted to that app
* user feeds the access token to the app
* the app can then present the access token to the server (in combination with its consumer credentials) and be permitted to do whatever's been authorized

=== Set up the App ===

After you've set up your app, you receive your OAuth consumer keys for the app:

* '''<tt>consumer_key</tt>'''
* '''<tt>consumer_secret</tt>'''

The first thing you're going to want to do is go into your app settings and set the correct level of access that your app is going to request from users. This is under the '''Settings''' tab:

* Application type:
** Read
** Read/Write
** Read/Write/Access DMs

You are probably going to want one of the latter two. Which one depends on whether or not your app is going to work with DMs (direct messages) or not.

You can also fill in the rest of the self-explanatory fields in the Details and Settings tabs as you like (organization, etc).

=== Authorize the App on your Bot's Account ===

While still logged in under the bot's account, navigate to the app's page and generate your access token:

Details tab → Your Access Token ''*click*''

Now your bot's twitter account has granted authorization to your app to act on its behalf. You'll that the relevant access token credentials have been created:

* '''<tt>access_token</tt>'''
* '''<tt>access_token_secret</tt>'''

== Rules of the Road ==

=== General Rules of Conduct and TOS ===

* https://dev.twitter.com/terms/api-terms
* https://support.twitter.com/articles/76915 - automation rules and best practices

=== Rate limits ===

Twitter has a very, very load/performance-centric outlook on the world because of the massive amounts of data and requests they deal with. If you don't play by the rules, twitter has absolutely no hesitation in going [http://i.imgur.com/bf1Xu.jpg NO SOUP FOR YOU].

* REST api is limited to...
** 350/reqs per hour ''per signed-in account''
** 150/reqs per hour ''per anonymous IP address''

Things that '''do''' count against your limit
* pretty much anything that involves hitting the REST API: fetching tweets from your timeline, fetching user profiles, fetching your @-replies, getting a list of followers, whatever.

Things that '''do not''' count against your limit (but see below)
* publishing status updates (sending tweets)
* sending direct messages
* following and unfollowing
* checking the rate limit by querying <tt>account/rate_limit_status</tt>
** it can change, though nowadays it rarely does
** note also that you get three headers describing how quickly you're nomming through your ratelimit as part of every REST API reply, eg:
*** <tt>X-RateLimit-Limit: 350</tt>
*** <tt>X-RateLimit-Remaining: 350</tt>
*** <tt>X-RateLimit-Reset: 1277485629</tt>

Other, service-specific limits
* 1,000 tweets per day
* 250 DMs per day
* follow limits: +1,000 per day plus additional monitoring once you hit 2,000 followed users

=== Other gotchas ===

* '''Repeated tweets'''
** You can't post a tweet that's an exact duplicate of any of your last few tweets. "Whoops! You already tweeted that!"
* '''Failed requests'''
** Twitter does crap out every now and again due to load or whatever other reason, so you need to watch for failures and catch the resulting exceptions. [500/502/503/504]

* [https://dev.twitter.com/docs/error-codes-responses HTTP responses / error codes] ''are'' meaningful and you must honour them in your bot's behaviour. In particular:
** '''400''' means you've hit the ratelimit on the REST API
** '''420''' means you've hit the ratelimit on the Search or Streaming API
** '''403''' means you've hit update (tweeting) limit.

== Getting started on the code ==

Each Twitter API library is going to have its own way to get initialized and set up.

== General things you may want to do ==

=== Check for @-messages and reply ===

=== Tweet updates from elsewhere ===

== Example: inetkami ==

* Twitter account: [http://twitter.com/inetkami @inetkami]
* Code: https://github.com/rickscott/inetkami

What it does: fetches, on request:
* [http://en.wikipedia.org/wiki/METAR METAR] (terse weather condition reports intended for aviators)
* [http://apps.cbp.gov/bwt/ Border Wait Times]

== Other Miscellany ==

* [http://www.readwriteweb.com/hack/2012/05/a-utility-that-makes-you-master-of-the-twitterverse.php t], a Ruby command-line interface to the Twitter API

C4LN 2012: Intro to the Twitter API

2012-05-24T16:04:33Z

Shadowspar: /* API Overview */

Presenter: [[User:Shadowspar|Rick Scott]] - [http://twitter.com/shadowspar @shadowspar]

== API Overview ==

* '''https://dev.twitter.com/docs is the main documentation area''' -- you'll spend a lot of time here =)

* https://dev.twitter.com/ is API central.
* useful things linked from [https://dev.twitter.com/ dev.twitter.com]:
** [https://dev.twitter.com/status API Status]
** [https://dev.twitter.com/issues API Known Issues]
** blog, discussion, etc etc

=== Parts ===

* the '''REST API'''
* the '''Streaming API'''
* the '''Search API'''

==== REST API ====
* query→response based access
* the mainstay of the API; the first part of it you'll want to be concerned with, and the part you'll likely use most

==== Streaming API ====
* aka ''drinking from the firehose'' =)
* persistent connection
* push-based communication w/ v.high ratelimit (1% of ''all tweets'')

==== Search API ====
* just like it says on the tin
* also trending topics

== Find your library ==

https://dev.twitter.com/docs/twitter-libraries has a good list

* Perl: [http://search.cpan.org/dist/Net-Twitter Net::Twitter]
* Python: [https://github.com/tweepy/tweepy tweepy] and many others
* Ruby: [https://github.com/jnunemaker/twitter twitter] rubygem and others

== Creating a new app ==

=== BEFORE creating an app: Bot-specific stuff ===

If you're going to have a separate twitter account for your bot, the best thing to do is to create that account ''before you create your app''. Then create your new app under ''under the bot's account''. This will simplify doing the OAuth dance below.

=== First steps to create an app ===
* https://dev.twitter.com/apps/new
* sign in with your twitter (bot's) account
* fill out basic info about your app
* agree to be a good citizen, as detailed below

Huzzah! You have your very own app!

=== A brief segue into OAuth ===

http://hueniverse.com/oauth/guide/intro/

OAuth metaphor: ''valet key'' to your car
* lets an app act on behalf of a user when dealing with some service
* lets a user give an app specific permissions to interact with a service on their behalf

Roles in OAuth:
* consumer (client) -- ''your app''
* service provider (server) -- ''Twitter''
* user (resource owner) -- ''user''

Credentials
* consumer credentials (consumer key & consumer secret)
* access credentials (access token & access secret)
* (also request token & secret)

OAuth workflow:
* user goes to server and says they'd like to authorize application ''X'' to do action ''Y''
* server generates access token which represents the combination of the specific app & the specific user & the specific level of access the user has granted to that app
* user feeds the access token to the app
* the app can then present the access token to the server (in combination with its consumer credentials) and be permitted to do whatever's been authorized

=== Set up the App ===

After you've set up your app, you receive your OAuth consumer keys for the app:

* '''<tt>consumer_key</tt>'''
* '''<tt>consumer_secret</tt>'''

The first thing you're going to want to do is go into your app settings and set the correct level of access that your app is going to request from users. This is under the '''Settings''' tab:

* Application type:
** Read
** Read/Write
** Read/Write/Access DMs

You are probably going to want one of the latter two. Which one depends on whether or not your app is going to work with DMs (direct messages) or not.

You can also fill in the rest of the self-explanatory fields in the Details and Settings tabs as you like (organization, etc).

=== Authorize the App on your Bot's Account ===

While still logged in under the bot's account, navigate to the app's page and generate your access token:

Details tab → Your Access Token ''*click*''

Now your bot's twitter account has granted authorization to your app to act on its behalf. You'll that the relevant access token credentials have been created:

* '''<tt>access_token</tt>'''
* '''<tt>access_token_secret</tt>'''

== Rules of the Road ==

=== General Rules of Conduct and TOS ===

* https://dev.twitter.com/terms/api-terms
* https://support.twitter.com/articles/76915 - automation rules and best practices

=== Rate limits ===

Twitter has a very, very load/performance-centric outlook on the world because of the massive amounts of data and requests they deal with. If you don't play by the rules, twitter has absolutely no hesitation in going [http://i.imgur.com/bf1Xu.jpg NO SOUP FOR YOU].

* REST api is limited to...
** 350/reqs per hour ''per signed-in account''
** 150/reqs per hour ''per anonymous IP address''

Things that '''do''' count against your limit
* pretty much anything that involves hitting the REST API: fetching tweets from your timeline, fetching user profiles, fetching your @-replies, getting a list of followers, whatever.

Things that '''do not''' count against your limit (but see below)
* publishing status updates (sending tweets)
* sending direct messages
* following and unfollowing
* checking the rate limit by querying <tt>account/rate_limit_status</tt>
** it can change, though nowadays it rarely does
** note also that you get three headers describing how quickly you're nomming through your ratelimit as part of every REST API reply, eg:
*** <tt>X-RateLimit-Limit: 350</tt>
*** <tt>X-RateLimit-Remaining: 350</tt>
*** <tt>X-RateLimit-Reset: 1277485629</tt>

Other, service-specific limits
* 1,000 tweets per day
* 250 DMs per day
* follow limits: +1,000 per day plus additional monitoring once you hit 2,000 followed users

=== Other gotchas ===

* '''Repeated tweets'''
** You can't post a tweet that's an exact duplicate of any of your last few tweets. "Whoops! You already tweeted that!"
* '''Failed requests'''
** Twitter does crap out every now and again due to load or whatever other reason, so you need to watch for failures and catch the resulting exceptions. [500/502/503/504]

* [https://dev.twitter.com/docs/error-codes-responses HTTP responses / error codes] ''are'' meaningful and you must honour them in your bot's behaviour. In particular:
** '''400''' means you've hit the ratelimit on the REST API
** '''420''' means you've hit the ratelimit on the Search or Streaming API
** '''403''' means you've hit update (tweeting) limit.

== Getting started on the code ==

Each Twitter API library is going to have its own way to get initialized and set up.

== General things you may want to do ==

=== Check for @-messages and reply ===

=== Tweet updates from elsewhere ===

== Example: inetkami ==

* Twitter account: [http://twitter.com/inetkami @inetkami]
* Code: https://github.com/rickscott/inetkami

What it does: fetches, on request:
* [http://en.wikipedia.org/wiki/METAR METAR] (terse weather condition reports intended for aviators)
* [http://apps.cbp.gov/bwt/ Border Wait Times]

== Other Miscellany ==

* [http://www.readwriteweb.com/hack/2012/05/a-utility-that-makes-you-master-of-the-twitterverse.php t], a Ruby command-line interface to the Twitter API

C4LN 2012: Intro to the Twitter API

2012-05-24T16:03:27Z

Shadowspar:

Presenter: [[User:Shadowspar|Rick Scott]] - [http://twitter.com/shadowspar @shadowspar]

== API Overview ==

* https://dev.twitter.com/ is API central.
* '''https://dev.twitter.com/docs is the main documentation area''' -- you'll spend a lot of time here =)
* other useful things linked from [https://dev.twitter.com/ dev.twitter.com]: [https://dev.twitter.com/status API Status], [https://dev.twitter.com/issues API Known Issues], blog & discussion

=== Parts ===

* the '''REST API'''
* the '''Streaming API'''
* the '''Search API'''

==== REST API ====
* query→response based access
* the mainstay of the API; the first part of it you'll want to be concerned with, and the part you'll likely use most

==== Streaming API ====
* aka ''drinking from the firehose'' =)
* persistent connection
* push-based communication w/ v.high ratelimit (1% of ''all tweets'')

==== Search API ====
* just like it says on the tin
* also trending topics

== Find your library ==

https://dev.twitter.com/docs/twitter-libraries has a good list

* Perl: [http://search.cpan.org/dist/Net-Twitter Net::Twitter]
* Python: [https://github.com/tweepy/tweepy tweepy] and many others
* Ruby: [https://github.com/jnunemaker/twitter twitter] rubygem and others

== Creating a new app ==

=== BEFORE creating an app: Bot-specific stuff ===

If you're going to have a separate twitter account for your bot, the best thing to do is to create that account ''before you create your app''. Then create your new app under ''under the bot's account''. This will simplify doing the OAuth dance below.

=== First steps to create an app ===
* https://dev.twitter.com/apps/new
* sign in with your twitter (bot's) account
* fill out basic info about your app
* agree to be a good citizen, as detailed below

Huzzah! You have your very own app!

=== A brief segue into OAuth ===

http://hueniverse.com/oauth/guide/intro/

OAuth metaphor: ''valet key'' to your car
* lets an app act on behalf of a user when dealing with some service
* lets a user give an app specific permissions to interact with a service on their behalf

Roles in OAuth:
* consumer (client) -- ''your app''
* service provider (server) -- ''Twitter''
* user (resource owner) -- ''user''

Credentials
* consumer credentials (consumer key & consumer secret)
* access credentials (access token & access secret)
* (also request token & secret)

OAuth workflow:
* user goes to server and says they'd like to authorize application ''X'' to do action ''Y''
* server generates access token which represents the combination of the specific app & the specific user & the specific level of access the user has granted to that app
* user feeds the access token to the app
* the app can then present the access token to the server (in combination with its consumer credentials) and be permitted to do whatever's been authorized

=== Set up the App ===

After you've set up your app, you receive your OAuth consumer keys for the app:

* '''<tt>consumer_key</tt>'''
* '''<tt>consumer_secret</tt>'''

The first thing you're going to want to do is go into your app settings and set the correct level of access that your app is going to request from users. This is under the '''Settings''' tab:

* Application type:
** Read
** Read/Write
** Read/Write/Access DMs

You are probably going to want one of the latter two. Which one depends on whether or not your app is going to work with DMs (direct messages) or not.

You can also fill in the rest of the self-explanatory fields in the Details and Settings tabs as you like (organization, etc).

=== Authorize the App on your Bot's Account ===

While still logged in under the bot's account, navigate to the app's page and generate your access token:

Details tab → Your Access Token ''*click*''

Now your bot's twitter account has granted authorization to your app to act on its behalf. You'll that the relevant access token credentials have been created:

* '''<tt>access_token</tt>'''
* '''<tt>access_token_secret</tt>'''

== Rules of the Road ==

=== General Rules of Conduct and TOS ===

* https://dev.twitter.com/terms/api-terms
* https://support.twitter.com/articles/76915 - automation rules and best practices

=== Rate limits ===

Twitter has a very, very load/performance-centric outlook on the world because of the massive amounts of data and requests they deal with. If you don't play by the rules, twitter has absolutely no hesitation in going [http://i.imgur.com/bf1Xu.jpg NO SOUP FOR YOU].

* REST api is limited to...
** 350/reqs per hour ''per signed-in account''
** 150/reqs per hour ''per anonymous IP address''

Things that '''do''' count against your limit
* pretty much anything that involves hitting the REST API: fetching tweets from your timeline, fetching user profiles, fetching your @-replies, getting a list of followers, whatever.

Things that '''do not''' count against your limit (but see below)
* publishing status updates (sending tweets)
* sending direct messages
* following and unfollowing
* checking the rate limit by querying <tt>account/rate_limit_status</tt>
** it can change, though nowadays it rarely does
** note also that you get three headers describing how quickly you're nomming through your ratelimit as part of every REST API reply, eg:
*** <tt>X-RateLimit-Limit: 350</tt>
*** <tt>X-RateLimit-Remaining: 350</tt>
*** <tt>X-RateLimit-Reset: 1277485629</tt>

Other, service-specific limits
* 1,000 tweets per day
* 250 DMs per day
* follow limits: +1,000 per day plus additional monitoring once you hit 2,000 followed users

=== Other gotchas ===

* '''Repeated tweets'''
** You can't post a tweet that's an exact duplicate of any of your last few tweets. "Whoops! You already tweeted that!"
* '''Failed requests'''
** Twitter does crap out every now and again due to load or whatever other reason, so you need to watch for failures and catch the resulting exceptions. [500/502/503/504]

* [https://dev.twitter.com/docs/error-codes-responses HTTP responses / error codes] ''are'' meaningful and you must honour them in your bot's behaviour. In particular:
** '''400''' means you've hit the ratelimit on the REST API
** '''420''' means you've hit the ratelimit on the Search or Streaming API
** '''403''' means you've hit update (tweeting) limit.

== Getting started on the code ==

Each Twitter API library is going to have its own way to get initialized and set up.

== General things you may want to do ==

=== Check for @-messages and reply ===

=== Tweet updates from elsewhere ===

== Example: inetkami ==

* Twitter account: [http://twitter.com/inetkami @inetkami]
* Code: https://github.com/rickscott/inetkami

What it does: fetches, on request:
* [http://en.wikipedia.org/wiki/METAR METAR] (terse weather condition reports intended for aviators)
* [http://apps.cbp.gov/bwt/ Border Wait Times]

== Other Miscellany ==

* [http://www.readwriteweb.com/hack/2012/05/a-utility-that-makes-you-master-of-the-twitterverse.php t], a Ruby command-line interface to the Twitter API

C4LN 2012: Intro to the Twitter API

2012-05-24T15:36:46Z

Shadowspar: +don't abide by the ratelimit? NO SOUP FOR YOU.

Presenter: [[User:Shadowspar|Rick Scott]] - [http://twitter.com/shadowspar @shadowspar]

== API Overview ==

* https://dev.twitter.com/ is API central.
* '''https://dev.twitter.com/docs is the main documentation area''' -- you'll spend a lot of time here =)
* other useful things linked from [https://dev.twitter.com/ dev.twitter.com]: [https://dev.twitter.com/status API Status], [https://dev.twitter.com/issues API Known Issues], blog & discussion

=== Parts ===

* the '''REST API'''
* the '''Streaming API'''
* the '''Search API'''

==== REST API ====
* query→response based access
* the mainstay of the API; the first part of it you'll want to be concerned with, and the part you'll likely use most

==== Streaming API ====
* aka ''drinking from the firehose'' =)
* persistent connection
* push-based communication w/ v.high ratelimit (1% of ''all tweets'')

==== Search API ====
* just like it says on the tin
* also trending topics

== Find your library ==

https://dev.twitter.com/docs/twitter-libraries has a good list

* Perl: [http://search.cpan.org/dist/Net-Twitter Net::Twitter]
* Python: [https://github.com/tweepy/tweepy tweepy] and many others
* Ruby: [https://github.com/jnunemaker/twitter twitter] rubygem and others

== Creating a new app ==

=== BEFORE creating an app: Bot-specific stuff ===

If you're going to have a separate twitter account for your bot, the best thing to do is to create that account ''before you create your app''. Then create your new app under ''under the bot's account''. This will simplify doing the OAuth dance below.

=== First steps to create an app ===
* https://dev.twitter.com/apps/new
* sign in with your twitter (bot's) account
* fill out basic info about your app
* agree to be a good citizen, as detailed below

Huzzah! You have your very own app!

=== A brief segue into OAuth ===

http://hueniverse.com/oauth/guide/intro/

OAuth metaphor: ''valet key'' to your car
* lets an app act on behalf of a user when dealing with some service
* lets a user give an app specific permissions to interact with a service on their behalf

Roles in OAuth:
* consumer (client) -- ''your app''
* service provider (server) -- ''Twitter''
* user (resource owner) -- ''user''

Credentials
* consumer credentials (consumer key & consumer secret)
* access credentials (access token & access secret)
* (also request token & secret)

OAuth workflow:
* user goes to server and says they'd like to authorize application ''X'' to do action ''Y''
* server generates access token which represents the combination of the specific app & the specific user & the specific level of access the user has granted to that app
* user feeds the access token to the app
* the app can then present the access token to the server (in combination with its consumer credentials) and be permitted to do whatever's been authorized

=== Set up the App ===

After you've set up your app, you receive your OAuth consumer keys for the app:

* '''<tt>consumer_key</tt>'''
* '''<tt>consumer_secret</tt>'''

The first thing you're going to want to do is go into your app settings and set the correct level of access that your app is going to request from users. This is under the '''Settings''' tab:

* Application type:
** Read
** Read/Write
** Read/Write/Access DMs

You are probably going to want one of the latter two. Which one depends on whether or not your app is going to work with DMs (direct messages) or not.

You can also fill in the rest of the self-explanatory fields in the Details and Settings tabs as you like (organization, etc).

=== Authorize the App on your Bot's Account ===

While still logged in under the bot's account, navigate to the app's page and generate your access token:

Details tab → Your Access Token ''*click*''

Now your bot's twitter account has granted authorization to your app to act on its behalf. You'll that the relevant access token credentials have been created:

* '''<tt>access_token</tt>'''
* '''<tt>access_token_secret</tt>'''

== Rules of the Road ==

=== General Rules of Conduct and TOS ===

* https://dev.twitter.com/terms/api-terms
* https://support.twitter.com/articles/76915 - automation rules and best practices

=== Rate limits ===

Twitter has a very, very load/performance-centric outlook on the world because of the massive amounts of data and requests they deal with. If you don't play by the rules, twitter has absolutely no hesitation in going [http://i.imgur.com/bf1Xu.jpg NO SOUP FOR YOU].

* REST api is limited to...
** 350/reqs per hour ''per signed-in account''
** 150/reqs per hour ''per anonymous IP address''

Things that '''do''' count against your limit

Things that '''do not''' count against your limit
* checking the rate limit (it can change, though nowadays it rarely does)

=== Other gotchas ===

* Repeated tweets
* failed reqs

== General things you may want to do ==

=== Check for @-messages and reply ===

=== Tweet updates from elsewhere ===

== Example: inetkami ==

* Twitter account: [http://twitter.com/inetkami @inetkami]
* Code: https://github.com/rickscott/inetkami

What it does: fetches, on request:
* [http://en.wikipedia.org/wiki/METAR METAR] (terse weather condition reports intended for aviators)
* [http://apps.cbp.gov/bwt/ Border Wait Times]

== Other Miscellany ==

* [http://www.readwriteweb.com/hack/2012/05/a-utility-that-makes-you-master-of-the-twitterverse.php t], a Ruby command-line interface to the Twitter API

C4LN 2012: Intro to the Twitter API

2012-05-24T15:14:02Z

Shadowspar: +much more detail

C4LN 2012: Intro to the Twitter API

2012-05-24T14:16:41Z

Shadowspar: +more OAuth and setup details

C4LN 2012: Intro to the Twitter API

2012-05-24T13:58:57Z

Shadowspar: working up a terse OAuth intro

C4LN 2012: Intro to the Twitter API

2012-05-24T13:25:41Z

Shadowspar: /* API Overview */

C4LN 2012: Intro to the Twitter API

2012-05-24T13:25:06Z

Shadowspar: /* API Overview */

C4LN 2012: Intro to the Twitter API

2012-05-24T12:25:29Z

Shadowspar:

Presenter: [[User:Shadowspar|Rick Scott]] - [http://twitter.com/shadowspar @shadowspar]

== API Overview ==

* https://dev.twitter.com/ is API central.
** other useful things linked therefrom: [https://dev.twitter.com/status API Status], [https://dev.twitter.com/issues API Known Issues], blog & discussion
* '''https://dev.twitter.com/docs is the main documentation area'''
** you'll find yourself spending a lot of time here =)

=== Parts ===

* the '''REST API'''
* the '''Streaming API'''
* the '''Search API'''

==== REST API ====
* query→response based access
* the mainstay of the API; the first part of it you'll want to be concerned with, and the part you'll likely use most

==== Streaming API ====
* aka ''drinking from the firehose'' =)
* persistent connection
* push-based communication w/ v.high ratelimit (1% of ''all tweets'')

==== Search API ====
* just like it says on the tin
* also trending topics

== Find your library ==

https://dev.twitter.com/docs/twitter-libraries has a good list

* Perl: [http://search.cpan.org/dist/Net-Twitter Net::Twitter]
* Python: [https://github.com/tweepy/tweepy tweepy] and many others
* Ruby: [https://github.com/jnunemaker/twitter twitter] rubygem and others

== Creating a new app ==

=== First steps ===
* https://dev.twitter.com/apps/new
* sign in with your twitter account
* fill out basic info about your app
* agree to be a good citizen, as detailed below

Huzzah! You have your very own app!

=== Setup ===

* Details tab
* Settings tab:
** Application type:
*** Read
*** Read/Write
*** Read/Write/Access DMs

* receive OAuth keys

== Bot-specific stuff ==

* create an account for your bot
* authorize it on your app

== Rules of Conduct ==

=== General Rules of the Road and TOS ===

* https://dev.twitter.com/terms/api-terms
* https://support.twitter.com/articles/76915 - automation rules and best practices

=== Rate limits ===

*

=== Other gotchas ===

* Repeated tweets

== Example ==

http://twitter.com/inetkami
https://github.com/rickscott/inetkami

== Other Miscellany ==

* [http://www.readwriteweb.com/hack/2012/05/a-utility-that-makes-you-master-of-the-twitterverse.php t], a Ruby command-line interface to the Twitter API

C4LN 2012: Intro to the Twitter API

2012-05-24T11:58:52Z

Shadowspar:

Presenter: [[User:Shadowspar|Rick Scott]] - [http://twitter.com/shadowspar @shadowspar]

== API Overview ==

* https://dev.twitter.com/ is API central.
** other useful things linked therefrom: [https://dev.twitter.com/status API Status], [https://dev.twitter.com/issues API Known Issues], blog & discussion
* https://dev.twitter.com/docs is the main documentation area
** you'll find yourself spending a lot of time here =)

=== Parts ===

The twitter API breaks down into three main areas
* the '''REST API'''
** query→response based access
** this is what you're most likely to use
* the '''Streaming API'''
** aka ''drinking from the firehose'' =)
** push-based communication w/ v.high ratelimit
* the '''Search API'''
** just like it says on the tin
** also trending topics

== Find your library ==

https://dev.twitter.com/docs/twitter-libraries

* Perl: [http://search.cpan.org/dist/Net-Twitter Net::Twitter]
* Python: [https://github.com/tweepy/tweepy tweepy] and many others
* Ruby: [https://github.com/jnunemaker/twitter twitter] rubygem and others

== Creating a new app ==

* https://dev.twitter.com/apps/new
* sign in with your twitter account

* https://dev.twitter.com/terms/api-terms
* https://support.twitter.com/articles/76915 - automation rules and best practices

== Rate limits ==

== Rules of Conduct ==

=== Repeated tweets ===

=== General TOS ===

== Example ==

http://twitter.com/inetkami
https://github.com/rickscott/inetkami

== Other Miscellany ==

* [http://www.readwriteweb.com/hack/2012/05/a-utility-that-makes-you-master-of-the-twitterverse.php t], a Ruby command-line interface to the Twitter API

C4LN 2012: Intro to the Twitter API

2012-05-23T19:42:00Z

Shadowspar:

Presenter: [[User:Shadowspar|Rick Scott]] - [http://twitter.com/shadowspar @shadowspar]

== API Overview ==

* https://dev.twitter.com/ is API central.
* https://dev.twitter.com/docs

=== Parts ===

The twitter API breaks down into three main areas
* the REST API (query→response based access)
* the Streaming API (drinking from the firehose)
* the Search API (just like it says on the tin)

== Find your library ==

== Creating a new app ==

* https://dev.twitter.com/apps/new
* sign in with your twitter account

* https://dev.twitter.com/terms/api-terms
* https://support.twitter.com/articles/76915 - automation rules and best practices

== Rate limits ==

== Rules of Conduct ==

=== Repeated tweets ===

=== General TOS ===

== Example ==

http://twitter.com/inetkami
https://github.com/rickscott/inetkami

C4LN 2012: Intro to the Twitter API

2012-05-23T18:45:57Z

Shadowspar: +beginning details

Presenter: [[User:Shadowspar|Rick Scott]] - [http://twitter.com/shadowspar @shadowspar]

== API Overview ==

* https://dev.twitter.com/ is API central.
* https://dev.twitter.com/docs

=== Parts ===

The twitter API breaks down into three main areas
* the REST API (query→response based access)
* the Streaming API (drinking from the firehose)
* the Search API (just like it says on the tin)

== Find your library ==

== Creating a new app ==

* https://dev.twitter.com/apps/new
* sign in with your twitter account

* https://dev.twitter.com/terms/api-terms

== Rate limits ==

== Rules of Conduct ==

=== Repeated tweets ===

=== General TOS ===

C4LN 2012: Intro to the Twitter API

2012-05-23T17:51:23Z

Shadowspar: +presenter info

Presenter: [[User:Shadowspar|Rick Scott]] - [http://twitter.com/shadowspar @shadowspar]

== API Overview ==

== Find your library ==

== Rate limits ==

== Rules of Conduct ==

=== Repeated tweets ===

=== General TOS ===

C4LN 2012: Intro to the Twitter API

2012-05-23T17:49:11Z

Shadowspar: +outline

== API Overview ==

== Find your library ==

== Rate limits ==

== Rules of Conduct ==

=== Repeated tweets ===

=== General TOS ===

North

2012-05-23T17:47:34Z

Shadowspar: /* 20 or 40 minute workshops: each one teach one */ linkify "Intro to Twitter API"

Welcome to the home of the new Ontario/Canada chapter of [http://code4lib.org/ Code4Lib]. Our aim is to create more opportunities for Code4Lib folks in the Ontario/Quebec/Manitoba/Northeast USA area to meet up in person.

==Mailing list==

Want to participate in Code4Lib North meetups and receive "North"-oriented Code4Lib announcements? Join the code4lib mailing list. (The code4lib-north mailing list was discontinued.)

== Third Meeting: University of Windsor, May 24 and 25th, 2012 ==

[[Image:code4libnorth.png|code4libnorth logo]]

=== Sign Up ===
We can handle a maximum of 40 people and you can signup here: https://c4ln2012.eventbrite.com/

=== Cost ===
This unconference runs on love... and the kindness of the Leddy Library who will provide : coffee, lunch, and wireless and the space

=== When and Where ===
Dates: May 24 and 25th, 2012 (it's on!)
 
Times: 9 am start time. 4 pm end time
 
Location: 4th Floor, Leddy Library, University of Windsor: http://www.uwindsor.ca/
Google Map: http://tinyurl.com/7a79qvw
 
Contact: mita@uwindsor.ca
 

=== Accommodation ===
The University offers rooms and suites for travellers, youth, and families seeking overnight, short or extended accommodations through its [http://www.conferences.uwindsor.ca/accommodations-for-individuals-and-families Conference Services: description of services provided]. Use this [https://web4.uwindsor.ca/units/AEC/Hospitality/conferenceServices/Registrations.nsf/CODE4LIBNorth?OpenForm Registration Form] to book a room with Conference Services.
 
 
In addition, University of Windsor special visit rates may be available by calling the local number and asking for the University of Windsor rate at certain hotels (which shouldn't dissuade you from staying wherever you prefer):
 
 
[http://his-windsor.com/ Holiday Inn Select]
1855 Huron Church Road, Windsor
Tel: 1-800-465-4329 or 519-966-1200 (3 km from campus)
 
[http://hamptoninn.hilton.com/en/hp/hotels/index.jhtml?ctyhocn=YQGCNHX Hampton Inn & Suites]
1840 Huron Church Road, Windsor
Tel: 800-Hampton or 519-972-0770 (3 km from campus)
 
[http://www.qualityinn.com/hotel-windsor-canada-CN317 Quality Suites Downtown]
250 Dougall Ave., Windsor
Tel: 519-977-9707 (3 km from campus)
(frequently used hotel for participants in [http://projectconifer.ca Conifer] hackfests)
 
[http://www.ceasarswindsor.com/ Caesars Windsor]
377 Riverside Dr. East, Windsor
Tel: 800-991-8888 (3 km from campus)
 
[http://www.windsorriversideinn.com/ The Windsor Riverside Inn]
333 Riverside Dr. West
Tel: 519-977-9777 (2 km from campus)
 
[http://www.travelodge.ca/hotel-search/list/windsor/all/ Travelodge Hotel Windsor Downtown Windsor]
33 Riverside Dr. East
Tel: 519-258-7774 (3 km from campus)
 

There are no bed and breakfasts in the immediate area but the [http://www.bbcanada.com/ontario/southwestern_ontario/windsor Argyle and Olde Walkerville Bed and Breakfasts] are a bus ride away.

=== Social Events ===

There's nothing formal planned but on Wednesday and Thursday nights, we'll try to informally coordinate places to have supper together.
 

I suggest that those around on Wednesday night meet up at the [http://www.rockbottom.ca/ Rock Bottom Grill] at 3236 Sandwich Street, Windsor. It will busy because it's "2 for 1 Wing Night" but it should be worth it.

 
For those who love experimental film, there is the [http://mediacityfilmfestival.com/films-and-schedule-2012/ Media City Film Festival] taking place in Windsor and Detroit. Jason Scott aka textfiles will be speaking at the [http://www.aadl.org/events/list?id=14190 Ann Arbor Public Library] on Wednesday night
 

=== Food ===
We will be providing lunch and snacks. (please email organizers if you have a dietary restriction - we will be ordering vegetarian options but we want to make sure we have enough!)
 
Generally folks informally gather for supper.
 
Here are some of our nearby options:
[http://www.windsoreats.com/rest_search.php?rest_location=Windsor%20-%20West%20Windsor WindsorEats: Windsor West]
 
But there is much more if we wander farther afield: [http://www.windsoreats.com/ WindsorEats]
 
Near the university on Wyndotte Street are various Asian dining options including:
* [http://www.restaurantica.com/on/windsor/eros-restaurant/23004000/ Eros Restaurant]
* [http://www.urbanspoon.com/r/19/1482082/restaurant/Detroit/Windsor-Seoul-Windsor Windsor Seoul]
* [http://www.urbanspoon.com/r/19/1648665/restaurant/Detroit/Bibim-To-Go-Windsor Bibim-To-Go]
* [http://www.urbanspoon.com/r/19/1549919/restaurant/Detroit/Hoi-Sushi-Windsor Hoi Sushi]
 
And here's a list of places that could probably fit 40 people:
* [http://www.urbanspoon.com/r/19/1549919/restaurant/Detroit/Hoi-Sushi-Windsor Hoi Sushi]
* [http://www.urbanspoon.com/r/19/1426344/restaurant/Detroit/Bubis-Awsome-Eats-Windsor Bubis Awesome Eats]
* [http://www.urbanspoon.com/r/19/1435280/restaurant/Detroit/Hurricanes-Windsor Hurricane's]

=== Format ===

A combination of 20 talks, 5 minute lightning talks, an Ask Anything session, workshops / hackfest time. We will try to find time for everyone who wants to present!
 
We have talks in the morning and hackfests in the afternoon. We will finalize the speaking schedule Thursday morning but we will try to split the talks between the two days equally.

=== 20 minutes talks :: feel free to sign up ===

{| border=1
! Name
! Title
|-
| Ted Lawless || easyArticle - steamlining access to library materials with OpenURL, automated interlibrary loan submission, vendor APIs, Django/Python.
|-
| Mita Williams || my sekret art project
|-
| John Fink and Warren Layton|| Embedded Hardware Hijinx
|-
| Alison Hitchens || RDA for coders/systems folk
|-
| Andrew McAlorum || Our favorite jQuery modules for Drupal 7
|-
| David Fiander || The state of the ebook marketplace
|-
| Dan Chudnov || backplane
|-
| William Denton || Having provocative fun with reference desk statistics in R
|}

=== 5 minutes talks :: feel free to sign up ===

{| border=1
! Name
! Title
|-
| Nick Ruest || Other Redmine uses
|-
| Tim Ribaric || Circumvention using the Cloud?
|-
| Alison Hitchens || #catcode: Cataloguers embrace Code Year
|-
| Mita Williams || "My god, it's full of stars! lists": building the library website that will incorporate [http://librarian.newjackalmanac.ca/2011/05/code4lib-north-presentation-were-jamun.html Jamun.]
|-
| Dan Chudnov || occupy 1923
|-
| Graham Fawcett || A Web-based video annotation tool (for peer review, possibly captioning, maybe for some nefarious library uses we haven't imagined)
|}

=== 20 or 40 minute workshops: each one teach one ===

:: a workshop you are willing to lead
::* Intro to Git, if demand warrants -- if not, no big deal (John Fink)
::* Environmental monitoring on the cheap (Doug Sartori)
::* (I program in a few languages, and could do a teaser-session on one of them if there's interest. Maybe [http://www.python.org Python], [http://www.haskell.org/ Haskell], [http://clojure.org/ Clojure] or [http://dlang.org D]?) (Graham Fawcett)
::* [[C4LN 2012: Intro to the Twitter API|Intro to the Twitter API]], including how one might use it to make a Twitter bot ([[User:shadowspar|Rick Scott]])

:: a workshop of what you would love to attend
::* intro to IRC, meet zoia (Mita, Warren, Sarah, John F)
::* how to create a twitter bot (Mita, John F, David F)
::* intro to Git (Warren, Sarah, David F)

=== hackfest ideas :: scheme schemas ===
- build your own twitter bot; bot battles

=== hackfest ideas :: feel free to add to the list ===
*twitter bot war with code4lib The Great Eastern? http://wiki.code4lib.org/index.php/GreatEastern
*changing Odessi XML records to MARC XML so OCUL libraries can load MARC for Odessi, esp. Stats Can stuff. We started this project at TUG, so need someone to help me get further or finish! New note: Chris put what he did so far on [https://github.com/lib-uoguelph-ca/ddi2marc-xml github](Alison)
*CanPoetry Sprint: [http://library.utoronto.ca/canpoetry Canadian Poetry Online] needs an overhaul! CanPoetry is a web anthology of contemporary Canadian poetry, providing biographies and full-text poems from Canada's leading poets. Currently, it is being migrated to Drupal from the static HTML. Join in this [http://drupal.org/node/247982 code sprint] to help with site building, development, and theming of the new version. More details to follow. (Andrew McAlorum)
*[http://www.jasongriffey.net/librarybox/ LibraryBox] is a customized version of PirateBox that can run be run on the inexpensive TP-Link MR 3020. Currently, it acts as a simple file server but it could potentially offer a more library-focused service, such as [https://twitter.com/#!/djfiander/status/184315493157576704 an eBook server for nearby devices using OPDS]. (Warren)
* [http://evergreen-ils.org/ Evergreen]: The Evergreen project is currently recruiting volunteers for the Google Summer of Code effort and has [http://evergreen-ils.org/dokuwiki/doku.php?id=dev:summer_of_coding_ideas#project_ideas a list of project ideas]. Some of these ideas, if not already claimed by a student GSoC participant, might make for interesting hackfest projects. Or we could rewrite the MARC editor in Dojo.
* [https://github.com/wdenton/splurge/ SPLURGE]: The Scholars Portal Library Usage-Based Recommendation Engine began at a hackfest in February and has been worked on since then, but it needs one last push to get all of the pieces joined together so that an easy-to-use "people who borrowed this also borrowed that" service built on shared circ data can be tested. There are four parts to SPLURGE: data cleanup, getting it into a properly configured database, a web service that talks to the database, some Javascript that can dropped into a catalogue to talk to the web service. They all exist, but not all of them are quite done and they don't all talk to each other. The purpose of this hackfest project would be for people to familiarize themselves with the work that's been done, and then try to finish it up.

=== code4lib north organizational team ===
*Mita Williams
*Karen Pillon
*Peter Zimmerman
*Jennifer Soutter
*Cathy Maskell
*Ranti Junus (Michigan State)

=== hashtag and twitter list ===
*c4ln2012
*https://twitter.com/copystar/c4ln2012

== Code4lib North Meetups in Ottawa ==

'''Purpose:''' To connect with other code4libbers in the area and start building a code4lib community in Ottawa, Ontario

===Next Meetup===

The next meetup is scheduled for Wednesday June 13th 2012 at 5pm (we'll take May off for code4lib North in Windsor). Once again, we'll be in the private room downstairs in The Exchange Pub.

As usual, please bring your laptops, tablets, demos, problems, and topics of discussion. Beginners are always welcome!

Those interested in attending or speaking can e-mail warren.layton@gmail.com for more information and (if not on the code4lib mailing list) to be kept informed of future events.

===Past Meetups===

The inaugural code4lib Ottawa meetup occurred on March 28, 2012 and was a simple meet-and-greet at a local pub. Since then, we try to combine this social event with some short interesting talks. Here is what we have learned about in recent meetups:

'''April 24, 2012 - Show and Tell Session'''
{| border=1
! Presenter
! Description of Talk
|-
| [http://twitter.com/maxneuvians Max Neuvians] || [http://social-biblio.ca/ Social-biblio.ca] : An approach to Twitter data visualization, archiving, and the larger narrative.
|-
| [http://twitter.com/scilib Richard Akerman] || [http://twitter.com/scilib Richard Akerman] and [http://twitter.com/bethmaru Mary Beth Baker] are organizing a Reading Garden at the upcoming Canadian Library Association conference. They are seeking advice on how to provide wireless access. Anyone with ideas is encouraged to get in touch with them.
|-
| [http://twitter.com/warlayton Warren Layton] || A quick demo of [http://www.jasongriffey.net/librarybox/ LibraryBox], a wireless filesharing device, which may have interesting applications in government and other libraries where IT restrictions can limit network use.
|}

== Second Meeting: McMaster University, May 5-6, 2011 ==

=== Sign Up ===
We can handle a maximum of 50 people and you can signup here: http://c4ln2011.eventbrite.com/.

=== When and Where ===
Dates: May 5-6, 2011
 
Location:
* 1280 Main St. West, [http://www.google.com/maps/place?cid=4151756913136304412&q=mcmaster+university+mills+memorial+library&hl=en&dtab=0&sll=43.260928,-79.91933&sspn=0.773056,1.227722&ie=UTF8&ll=43.647007,-80.532532&spn=0,0&z=10 McMaster University, Hamilton, Ontario - ] (map)
* Mills Memorial Library, [http://library.mcmaster.ca/lyons Lyons New Media Centre] (4th floor)

=== Accommodation ===
Our helpful folks in Research Collections put this [http://library.mcmaster.ca/archives/visiting guide] together a while back.

=== Parking, Campus Map, Public Transit ===
* [http://parking.mcmaster.ca/ Parking] - I understand we have the most expensive parking in OCUL. I'm sorry :( - There is one bit of good news: if you park in the M lot, the day rate drops from $20 to $5. The M lot is about a 10-12 minute walk from the library, and there is a shuttle that will take you part of the way.
* [http://parking.mcmaster.ca/June25UpdatedMapWithAutomation.PDF Campus map] - we are building #10 - Mills Memorial Library
* [http://www.hamilton.ca/CityServices/transit?WT.mc_id=hsr&WT.hamilton_redirect_friendly=1/ Public Transit]
* HSR buses that come to campus are: [http://www.hamilton.ca/NR/rdonlyres/F831E17F-2373-48C8-A808-F7DB7873400E/0/JA11Route1.pdf 1], [http://www.hamilton.ca/NR/rdonlyres/FB34FB4E-EF3A-4154-AF2D-46C06F05F06F/0/JA11Route51.pdf 51], [http://www.hamilton.ca/NR/rdonlyres/53F0A87E-6DA9-4E04-A6A6-6BF5E7482806/0/JA11Route5.pdf 5c], [http://www.hamilton.ca/NR/rdonlyres/B25032CD-ABC4-40D3-8509-FA6CCB7DB4CA/0/JA11Route52A.pdf 52], and [http://www.hamilton.ca/NR/rdonlyres/650AA6C2-DD5F-422F-86A6-E0D6EA688CEE/0/JA11Route10.pdf 10] - The 10 and 52 drop off by the hospital, the others drop off right outside Mills.

=== Cost ===
Keep with tradition set last year - No cost and McMaster University has tentatively agreed to provided coffee, lunch, space, and wireless.

=== Format ===
Day 1:
* Hackfest (send problems/proposals to John Fink and Nick Ruest)
Day 2
* 5-minute lighting talks
* 20-minute talks
* BOAF/breakouts

=== 20-minute talks ===
I'd like to start a new tradition with Code4Lib North and deposit the slides and *maybe* recordings of the presentations in our IR. If people are cool with this, I can get it all setup prior to the event.

{| border=1
! Name
! Title
|-
| William J Turkel || [http://digitalcommons.mcmaster.ca/c4ln/9/ Functional Programming Workout]
|-
| Dileshni Jayasinghe & Majid Valipour || [http://digitalcommons.mcmaster.ca/c4ln/8/ Programming at Scholars Portal: apps and APIs]
|-
| William Wueppelmann || [http://digitalcommons.mcmaster.ca/c4ln/1/ The Canadiana Web API]
|-
| Dan Chudnov || [http://digitalcommons.mcmaster.ca/c4ln/7/ WWIC? Linked Library Data as a Customer Service Medium]
|-
| Mita Williams || [http://digitalcommons.mcmaster.ca/c4ln/3/ We're jamun (and we hope you like jamun too)]
|-
| William Denton || [http://digitalcommons.mcmaster.ca/c4ln/10/ Getting started with R]
|-
| Alan Harnum || [http://digitalcommons.mcmaster.ca/c4ln/5/ When All You Have Is XSLT, Everything Looks Like XML: Heterogeneous Cloud-Based Content Management Using Google Docs and Other Services]
|-
| Wendy Huot || [http://digitalcommons.mcmaster.ca/c4ln/12/ Why can't a web page be more like a book? Using LaTeX with Readability to generate better 'print friendly' versions of web pages]
|-
| Chris Charles || [http://digitalcommons.mcmaster.ca/c4ln/11/ Introduction to Google Refine]
|-
| Karen A. Coombs || [http://digitalcommons.mcmaster.ca/c4ln/2/ Zend Framework: making using web services easier]

|}

=== 5-minute lighting talks ===

{| border=1
! Name
! Title
|-
| Andrew McAlorum || [http://digitalcommons.mcmaster.ca/c4ln/4/ Transition to Unity]
|-
| Dale Askey || [http://digitalcommons.mcmaster.ca/c4ln/6/ Fun with Failure, or, Learning to Stick a Fork in Things]
|-
| Alison Hitchens || [http://digitalcommons.mcmaster.ca/c4ln/13/ Getting testers to test what you need to have tested!]
|-
| Alison Hitchens || [http://digitalcommons.mcmaster.ca/c4ln/13/ Using RT Tracker for user feedback]
|}

== First Meeting: Kingston ON, May 6-7, 2010 ==

=== Sign up ===

Free registration -- but registration is now closed (we have 40+ signed up).

=== When and Where ===

'''May 6-7, 2010'''
* Thursday: 2pm-5:30pm, followed by dinner and drinks
* Friday: 9am-4:30pm

Meeting location:
* [http://maps.google.com/maps/ms?hl=en&ie=UTF8&oe=UTF8&source=embed&msa=0&msid=103786326471006763157.0004700577498a9166e33&ll=44.227888,-76.494584&spn=0.009226,0.012875&z=15| 93 University Ave, Queen's University, Kingston Ontario] (map)
* Meeting room: [http://library.queensu.ca/library/floorplans/index.php?library=Douglas&floorpos=4F&section=North_Reading_Room#map| 1966 North Reading Room, Level 7, Douglas Library Building] (floorplan) - located on the top floor, just follow the signs to find the room.

=== Cost ===

There was no charge. Queen's University very generously supplied the space, the Internet connection, and free lunch on Friday!

=== How to get involved ===

Join the mailing list. That is where the planning will happen.

=== Format ===

* 5-minute lighting talks
* 20-minute talks
* BOAF sessions
* Maybe a hackfest.

=== How many are attending? ===

45 people have registered. Most will be attending.

=== Program ===

'''Thursday May 6:'''

* 2pm-5pm: Open format (hang out and hack)
* Evening: Go out for dinner and drinks

'''Friday:'''

* 9am-4:30pm: Schedule currently "under construction" -- see table below.

Morning Break: 10:30-10:45 .... Lunch: 12-1 ....

Afternoon: 5 minute lightning talks .... "Birds of a feather" breakout sessions (sign up sheets on front table)

{| border=1
! Name
! Description
|-
| William Denton || OpenFRBR
|-
| Walter Lewis || Exposing Linked Data
|-
| Art Rhyno || Open Layers and Newspapers (Walter Lewis)
|-
| MJ Suhonos || [http://mytpl.ca Location-aware Mobile Search]
|-
|Alan Harnum || Building A [http://beta.torontopubliclibrary.ca/ Library Website] with [http://www.endeca.com/ Endeca] technology
|-
|Wendy Huot || "Your feedback, please": library web design critique
|-
|Glen Newton || [http://zzzoot.blogspot.com/2009/07/project-torngat-building-large-scale.html Using Open Source Tools for Visualization and Semantic Mapping in a Large Scale Article Digital Library]
|-
| Eric Palmitesta || XQuery
|-
| John Miedema || [http://code.google.com/p/openbook4wordpress/wiki/index OpenBook WordPress Plugin Update - Why It's Cool to Love OpenURL +++]
|-
|Nasser Saleh || Coagmento!: a potential collaborative search tool
|}

== Who's interested in Code4Lib North? ==

Declare your interest in a Code4lib North chapter:

* Wendy Huot, Queen's University
* Michael Vandenburg, Queen's University
* [http://www.miskatonic.org/ William Denton], York University
* John Fink, McMaster University
* [http://ruebot.net/ Nick Ruest], [http://digitalcollections.mcmaster.ca/ McMaster University]
* Walter Lewis, Halton Hills/OurOntario
* Edward Corrado, Binghamton University (NY, USA)
* [http://thebookpile.wordpress.com Warren Layton], Library of Parliament (Ottawa)
* Pascal Calarco, University of Notre Dame (IN, USA)
* Rob Fox, University of Notre Dame (IN, USA)
* Mita Williams, University of Windsor
* John Fereira, Cornell University
* MJ Suhonos, Toronto Public Library
* Dianne Dietrich, Cornell University
* David Fiander, University of Western Ontario
* Peter Schlumpf, [http://www.avantilibrarysystems.com/ Avanti Library Systems]
* Roy Zimmer, Western Michigan University
* Kimberly Silk, Martin Prosperity Institute, University of Toronto
* Andrew Darby, Ithaca College (Ithaca, NY)
* Laura Harris, Grand Valley State University (western Michigan)
* Tim Ribaric, Brock University
* Sibyl Schaefer, University of Vermont
* Peter Ellinger, Ontario Legislative Library, Toronto
* Keith Jenkins, Cornell University
* [http://pmlozeau.ca/ Patrick M. Lozeau]
* Mike Kreyche, Kent State University
* Graham McCarthy, [http://www.ryerson.ca/library/ Ryerson University]
* [http://johnmiedema.ca John Miedema]
* Janey Chen, Ontario Legislative Library, Toronto
* Rob McDonald, Carleton University
* Amy Buckland, McGill University
* Tricia Williams (pgwillia), Consultant/[http://search.ourontario.ca OurOntario]
* Mike Beccaria, Paul Smith's College (Paul Smiths, NY)
* Amanda Etches-Johnson, McMaster University
* Art Rhyno, University of Windsor
* [http://bethmaru.com Mary Beth Baker], CIC (Ottawa)
* Wayne Schneider, Hennepin County Library
* Carol Serroul, CISTI
* Graham Stewart, University of Toronto Libraries
* Peter Zimmerman, University of Windsor
* Margaret Kipp, University of Wisconsin Milwaukee
* [http://coffeecode.net Dan Scott], Laurentian University
* Lawrence Wardroper (Courts Administration Services Library, Ottawa)
* Matt McCollow, McMaster University
* [http://www.parser.ca/z678/ George Duimovich], NRCan Library (Ottawa)
* [mailto:bobbi_fox@harvard.edu Bobbi Fox], Harvard University Library (Massachusetts)
* Dileshni Jayasinghe, OCUL, University of Toronto
* Eric Palmitesta, OCUL, University of Toronto
* [http://twitter.com/alxp Alexander O'Neill], Robertson Library, University of Prince Edward Island
* Chris Beer, WGBH (Massachusetts)
* Robin Isard, Algoma University (Sault Ste Marie ON)
* Pat Moore, Carleton University (Ottawa ON)
* [http://wagathon.tumblr.com/ Alan Harnum], Toronto Public LIbrary (Toronto ON)
* Colin Prince, University of Toronto Libraries
* Tom Keays, Syracuse University LIbrary (Syracuse, NY)
* Chris Charles, University of Guelph (Guelph, ON)
* John MacGillivray, Carleton University (Ottawa ON)
* Lester Webb, Kingston Frontenac Public Library (Kingston ON)
* Elizabeth Goldman, Kingston Frontenac Public Library (Kingston ON)
* Jennifer O'Donnell, Kingston Frontenac Public Library (Kingston ON)
* David Smith, Kingston Frontenac Public Library (Kingston ON)
* Loren Fantin, Our Ontario,Knowledge Ontario
* Daulton Theodore, Carleton University (Ottawa, ON)
* Peter MacDonald, Hamilton College (Clinton, NY)
* Rebecca Larocque, North Bay Public Library (North Bay, ON)
* Doris Rankin, Library and Information Management Consultant, Ottawa, ON
* Diane Bédard, Learn Ontario & Our Ontario; Knowledge Ontario
* [http://www.arts.uottawa.ca/eng/avellino.html Andre Vellino], CISTI / University of Ottawa
* [http://twitter.com/markswartz Mark Swartz], Queen's University
* Adam Wead, Rock and Roll Hall of Fame Library and Archives (Cleveland, OH)
* Pramila Thakur, Ontario Legislative Library, Toronto
* Anthony Petryk, University of Ottawa
* Jan Dawson, Ask Ontario, Knowledge Ontario
* [http://lab.cisti-icist.nrc-cnrc.gc.ca/cistilabswiki/index.php/Glen_Newton Glen Newton], Carleton University
* Patrick McMaster, Leeds & the 1000 Islands, Rideau Lakes, and North Grenville Public Libraries
* Nasser Saleh, Queen's University (Kingston ON)
* [http://stefansinclair.name/ Stéfan Sinclair], McMaster University
* [http://williamjturkel.net/ William J Turkel], University of Western Ontario
* Shirley Lew, [http://library.vcc.ca/ Vancouver Community College], (Vancouver BC)
* [http://twitter.com/edbilodeau Edward Bilodeau], [http://www.mcgill.ca/library/ McGill University]
* Andrew McAlorum, University of Toronto Libraries

== Meeting Location Suggestions for the Future ==

* Toronto, Ontario
* Sudbury, Ontario
* Ottawa, Ontario
* Montreal, Quebec

North

2012-05-16T16:39:13Z

Shadowspar: /* 20 or 40 minute workshops: each one teach one */ +Twitter API session

Welcome to the home of the new Ontario/Canada chapter of [http://code4lib.org/ Code4Lib]. Our aim is to create more opportunities for Code4Lib folks in the Ontario/Quebec/Manitoba/Northeast USA area to meet up in person.

==Mailing list==

Want to participate in Code4Lib North meetups and receive "North"-oriented Code4Lib announcements? Join the code4lib mailing list. (The code4lib-north mailing list was discontinued.)

== Third Meeting: University of Windsor, May 24 and 25th, 2012 ==

[[Image:code4libnorth.png|code4libnorth logo]]

=== Sign Up ===
We can handle a maximum of 40 people and you can signup here: https://c4ln2012.eventbrite.com/

=== Cost ===
This unconference runs on love... and the kindness of the Leddy Library who will provide : coffee, lunch, and wireless and the space

=== When and Where ===
Dates: May 24 and 25th, 2012 (it's on!)
 
Location: 4th Floor, Leddy Library, University of Windsor: http://www.uwindsor.ca/
Google Map: http://tinyurl.com/7a79qvw
 
Contact: mita@uwindsor.ca
 

=== Accommodation ===
The University offers rooms and suites for travellers, youth, and families seeking overnight, short or extended accommodations through its [http://www.conferences.uwindsor.ca/accommodations-for-individuals-and-families Conference Services: description of services provided]. Use this [https://web4.uwindsor.ca/units/AEC/Hospitality/conferenceServices/Registrations.nsf/CODE4LIBNorth?OpenForm Registration Form] to book a room with Conference Services.
 
 
In addition, University of Windsor special visit rates may be available by calling the local number and asking for the University of Windsor rate at certain hotels (which shouldn't dissuade you from staying wherever you prefer):
 
 
[http://his-windsor.com/ Holiday Inn Select]
1855 Huron Church Road, Windsor
Tel: 1-800-465-4329 or 519-966-1200 (3 km from campus)
 
[http://hamptoninn.hilton.com/en/hp/hotels/index.jhtml?ctyhocn=YQGCNHX Hampton Inn & Suites]
1840 Huron Church Road, Windsor
Tel: 800-Hampton or 519-972-0770 (3 km from campus)
 
[http://www.qualityinn.com/hotel-windsor-canada-CN317 Quality Suites Downtown]
250 Dougall Ave., Windsor
Tel: 519-977-9707 (3 km from campus)
(frequently used hotel for participants in [http://projectconifer.ca Conifer] hackfests)
 
[http://www.ceasarswindsor.com/ Caesars Windsor]
377 Riverside Dr. East, Windsor
Tel: 800-991-8888 (3 km from campus)
 
[http://www.windsorriversideinn.com/ The Windsor Riverside Inn]
333 Riverside Dr. West
Tel: 519-977-9777 (2 km from campus)
 
[http://www.travelodge.ca/hotel-search/list/windsor/all/ Travelodge Hotel Windsor Downtown Windsor]
33 Riverside Dr. East
Tel: 519-258-7774 (3 km from campus)
 

There are no bed and breakfasts in the immediate area but the [http://www.bbcanada.com/ontario/southwestern_ontario/windsor Argyle and Olde Walkerville Bed and Breakfasts] are a bus ride away.

=== Social Events ===

There's nothing formal planned but on Wednesday and Thursday nights, we'll try to informally coordinate places to have supper together.
 
For those who love experimental film, there is the [http://mediacityfilmfestival.com/films-and-schedule-2012/ Media City Film Festival] taking place in Windsor and Detroit.

=== Food ===
We will be providing lunch and snacks. (please email organizers if you have a dietary restriction - we will be ordering vegetarian options but we want to make sure we have enough!)
 
Generally folks informally gather for supper.
 
Here are some of our nearby options:
[http://www.windsoreats.com/rest_search.php?rest_location=Windsor%20-%20West%20Windsor WindsorEats: Windsor West]
 
But there is much more if we wander farther afield: [http://www.windsoreats.com/ WindsorEats]
 
Near the university on Wyndotte Street are various Asian dining options including:
* [http://www.restaurantica.com/on/windsor/eros-restaurant/23004000/ Eros Restaurant]
* [http://www.urbanspoon.com/r/19/1482082/restaurant/Detroit/Windsor-Seoul-Windsor Windsor Seoul]
* [http://www.urbanspoon.com/r/19/1648665/restaurant/Detroit/Bibim-To-Go-Windsor Bibim-To-Go]
* [http://www.urbanspoon.com/r/19/1549919/restaurant/Detroit/Hoi-Sushi-Windsor Hoi Sushi]
 
And here's a list of places that could probably fit 40 people:
* [http://www.urbanspoon.com/r/19/1549919/restaurant/Detroit/Hoi-Sushi-Windsor Hoi Sushi]
* [http://www.urbanspoon.com/r/19/1426344/restaurant/Detroit/Bubis-Awsome-Eats-Windsor Bubis Awesome Eats]
* [http://www.urbanspoon.com/r/19/1435280/restaurant/Detroit/Hurricanes-Windsor Hurricane's]

=== Format ===
A combination of 20 talks, 5 minute lightning talks, an Ask Anything session, workshops / hackfest time. We will try to find time for everyone who wants to present!

Previous code4lib north days have had the hacking and the speaking events on separate days. We're thinking about doing a little bit each day. What do you think - we'd like your feedback : http://tinyurl.com/6obdnne

=== 20 minutes talks :: feel free to sign up ===

{| border=1
! Name
! Title
|-
| Ted Lawless || easyArticle - steamlining access to library materials with OpenURL, automated interlibrary loan submission, vendor APIs, Django/Python.
|-
| Mita Williams || my sekret art project
|-
| John Fink and Warren Layton|| Embedded Hardware Hijinx
|-
| Alison Hitchens || RDA for coders/systems folk
|-
| Andrew McAlorum || Our favorite jQuery modules for Drupal 7
|-
| David Fiander || The state of the ebook marketplace
|-
| Dan Chudnov || backplane
|-
| William Denton || Having provocative fun with reference desk statistics in R
|}

=== 5 minutes talks :: feel free to sign up ===

{| border=1
! Name
! Title
|-
| Nick Ruest || Other Redmine uses
|-
| Tim Ribaric || Circumvention using the Cloud?
|-
| Alison Hitchens || #catcode: Cataloguers embrace Code Year
|-
| Mita Williams || "My god, it's full of stars! lists": building the library website that will incorporate [http://librarian.newjackalmanac.ca/2011/05/code4lib-north-presentation-were-jamun.html Jamun.]
|-
| Dan Chudnov || occupy 1923
|-
|}

=== 20 or 40 minute workshops: each one teach one ===

:: a workshop you are willing to lead
::* Intro to Git, if demand warrants -- if not, no big deal (John Fink)
::* Environmental monitoring on the cheap (Doug Sartori)
::* (I program in a few languages, and could do a teaser-session on one of them if there's interest. Maybe [http://www.python.org Python], [http://www.haskell.org/ Haskell], [http://clojure.org/ Clojure] or [http://dlang.org D]?) (Graham Fawcett)
::* Intro to the Twitter API; how one might use it to make a Twitter bot ([[User:shadowspar|Rick Scott]])

:: a workshop of what you would love to attend
::* intro to IRC, meet zoia (Mita, Warren, Sarah, John F)
::* how to create a twitter bot (Mita, John F, David F)
::* intro to Git (Warren, Sarah, David F)

=== hackfest ideas :: scheme schemas ===
- build your own twitter bot; bot battles

=== hackfest ideas :: feel free to add to the list ===
*twitter bot war with code4lib The Great Eastern? http://wiki.code4lib.org/index.php/GreatEastern
*changing Odessi XML records to MARC XML so OCUL libraries can load MARC for Odessi, esp. Stats Can stuff. We started this project at TUG, so need someone to help me get further or finish! (Alison)
*CanPoetry Sprint: [http://library.utoronto.ca/canpoetry Canadian Poetry Online] needs an overhaul! CanPoetry is a web anthology of contemporary Canadian poetry, providing biographies and full-text poems from Canada's leading poets. Currently, it is being migrated to Drupal from the static HTML. Join in this [http://drupal.org/node/247982 code sprint] to help with site building, development, and theming of the new version. More details to follow. (Andrew McAlorum)
*[http://www.jasongriffey.net/librarybox/ LibraryBox] is a customized version of PirateBox that can run be run on the inexpensive TP-Link MR 3020. Currently, it acts as a simple file server but it could potentially offer a more library-focused service, such as [https://twitter.com/#!/djfiander/status/184315493157576704 an eBook server for nearby devices using OPDS]. (Warren)
* [http://evergreen-ils.org/ Evergreen]: The Evergreen project is currently recruiting volunteers for the Google Summer of Code effort and has [http://evergreen-ils.org/dokuwiki/doku.php?id=dev:summer_of_coding_ideas#project_ideas a list of project ideas]. Some of these ideas, if not already claimed by a student GSoC participant, might make for interesting hackfest projects. Or we could rewrite the MARC editor in Dojo.
* [https://github.com/wdenton/splurge/ SPLURGE]: The Scholars Portal Library Usage-Based Recommendation Engine began at a hackfest in February and has been worked on since then, but it needs one last push to get all of the pieces joined together so that an easy-to-use "people who borrowed this also borrowed that" service built on shared circ data can be tested. There are four parts to SPLURGE: data cleanup, getting it into a properly configured database, a web service that talks to the database, some Javascript that can dropped into a catalogue to talk to the web service. They all exist, but not all of them are quite done and they don't all talk to each other. The purpose of this hackfest project would be for people to familiarize themselves with the work that's been done, and then try to finish it up.

=== code4lib north organizational team ===
*Mita Williams
*Karen Pillon
*Peter Zimmerman
*Jennifer Soutter
*Cathy Maskell
*Ranti Junus (Michigan State)

=== hashtag and twitter list ===
*c4ln2012
*https://twitter.com/copystar/c4ln2012

== Code4lib North Meetups in Ottawa ==

'''Purpose:''' To connect with other code4libbers in the area and start building a code4lib community in Ottawa, Ontario

===Next Meetup===

The next meetup is scheduled for Wednesday June 13th 2012 at 5pm (we'll take May off for code4lib North in Windsor). Once again, we'll be in the private room downstairs in The Exchange Pub.

As usual, please bring your laptops, tablets, demos, problems, and topics of discussion. Beginners are always welcome!

Those interested in attending or speaking can e-mail warren.layton@gmail.com for more information and (if not on the code4lib mailing list) to be kept informed of future events.

===Past Meetups===

The inaugural code4lib Ottawa meetup occurred on March 28, 2012 and was a simple meet-and-greet at a local pub. Since then, we try to combine this social event with some short interesting talks. Here is what we have learned about in recent meetups:

'''April 24, 2012 - Show and Tell Session'''
{| border=1
! Presenter
! Description of Talk
|-
| [http://twitter.com/maxneuvians Max Neuvians] || [http://social-biblio.ca/ Social-biblio.ca] : An approach to Twitter data visualization, archiving, and the larger narrative.
|-
| [http://twitter.com/scilib Richard Akerman] || [http://twitter.com/scilib Richard Akerman] and [http://twitter.com/bethmaru Mary Beth Baker] are organizing a Reading Garden at the upcoming Canadian Library Association conference. They are seeking advice on how to provide wireless access. Anyone with ideas is encouraged to get in touch with them.
|-
| [http://twitter.com/warlayton Warren Layton] || A quick demo of [http://www.jasongriffey.net/librarybox/ LibraryBox], a wireless filesharing device, which may have interesting applications in government and other libraries where IT restrictions can limit network use.
|}

== Second Meeting: McMaster University, May 5-6, 2011 ==

=== Sign Up ===
We can handle a maximum of 50 people and you can signup here: http://c4ln2011.eventbrite.com/.

=== When and Where ===
Dates: May 5-6, 2011
 
Location:
* 1280 Main St. West, [http://www.google.com/maps/place?cid=4151756913136304412&q=mcmaster+university+mills+memorial+library&hl=en&dtab=0&sll=43.260928,-79.91933&sspn=0.773056,1.227722&ie=UTF8&ll=43.647007,-80.532532&spn=0,0&z=10 McMaster University, Hamilton, Ontario - ] (map)
* Mills Memorial Library, [http://library.mcmaster.ca/lyons Lyons New Media Centre] (4th floor)

=== Accommodation ===
Our helpful folks in Research Collections put this [http://library.mcmaster.ca/archives/visiting guide] together a while back.

=== Parking, Campus Map, Public Transit ===
* [http://parking.mcmaster.ca/ Parking] - I understand we have the most expensive parking in OCUL. I'm sorry :( - There is one bit of good news: if you park in the M lot, the day rate drops from $20 to $5. The M lot is about a 10-12 minute walk from the library, and there is a shuttle that will take you part of the way.
* [http://parking.mcmaster.ca/June25UpdatedMapWithAutomation.PDF Campus map] - we are building #10 - Mills Memorial Library
* [http://www.hamilton.ca/CityServices/transit?WT.mc_id=hsr&WT.hamilton_redirect_friendly=1/ Public Transit]
* HSR buses that come to campus are: [http://www.hamilton.ca/NR/rdonlyres/F831E17F-2373-48C8-A808-F7DB7873400E/0/JA11Route1.pdf 1], [http://www.hamilton.ca/NR/rdonlyres/FB34FB4E-EF3A-4154-AF2D-46C06F05F06F/0/JA11Route51.pdf 51], [http://www.hamilton.ca/NR/rdonlyres/53F0A87E-6DA9-4E04-A6A6-6BF5E7482806/0/JA11Route5.pdf 5c], [http://www.hamilton.ca/NR/rdonlyres/B25032CD-ABC4-40D3-8509-FA6CCB7DB4CA/0/JA11Route52A.pdf 52], and [http://www.hamilton.ca/NR/rdonlyres/650AA6C2-DD5F-422F-86A6-E0D6EA688CEE/0/JA11Route10.pdf 10] - The 10 and 52 drop off by the hospital, the others drop off right outside Mills.

=== Cost ===
Keep with tradition set last year - No cost and McMaster University has tentatively agreed to provided coffee, lunch, space, and wireless.

=== Format ===
Day 1:
* Hackfest (send problems/proposals to John Fink and Nick Ruest)
Day 2
* 5-minute lighting talks
* 20-minute talks
* BOAF/breakouts

=== 20-minute talks ===
I'd like to start a new tradition with Code4Lib North and deposit the slides and *maybe* recordings of the presentations in our IR. If people are cool with this, I can get it all setup prior to the event.

{| border=1
! Name
! Title
|-
| William J Turkel || [http://digitalcommons.mcmaster.ca/c4ln/9/ Functional Programming Workout]
|-
| Dileshni Jayasinghe & Majid Valipour || [http://digitalcommons.mcmaster.ca/c4ln/8/ Programming at Scholars Portal: apps and APIs]
|-
| William Wueppelmann || [http://digitalcommons.mcmaster.ca/c4ln/1/ The Canadiana Web API]
|-
| Dan Chudnov || [http://digitalcommons.mcmaster.ca/c4ln/7/ WWIC? Linked Library Data as a Customer Service Medium]
|-
| Mita Williams || [http://digitalcommons.mcmaster.ca/c4ln/3/ We're jamun (and we hope you like jamun too)]
|-
| William Denton || [http://digitalcommons.mcmaster.ca/c4ln/10/ Getting started with R]
|-
| Alan Harnum || [http://digitalcommons.mcmaster.ca/c4ln/5/ When All You Have Is XSLT, Everything Looks Like XML: Heterogeneous Cloud-Based Content Management Using Google Docs and Other Services]
|-
| Wendy Huot || [http://digitalcommons.mcmaster.ca/c4ln/12/ Why can't a web page be more like a book? Using LaTeX with Readability to generate better 'print friendly' versions of web pages]
|-
| Chris Charles || [http://digitalcommons.mcmaster.ca/c4ln/11/ Introduction to Google Refine]
|-
| Karen A. Coombs || [http://digitalcommons.mcmaster.ca/c4ln/2/ Zend Framework: making using web services easier]

|}

=== 5-minute lighting talks ===

{| border=1
! Name
! Title
|-
| Andrew McAlorum || [http://digitalcommons.mcmaster.ca/c4ln/4/ Transition to Unity]
|-
| Dale Askey || [http://digitalcommons.mcmaster.ca/c4ln/6/ Fun with Failure, or, Learning to Stick a Fork in Things]
|-
| Alison Hitchens || [http://digitalcommons.mcmaster.ca/c4ln/13/ Getting testers to test what you need to have tested!]
|-
| Alison Hitchens || [http://digitalcommons.mcmaster.ca/c4ln/13/ Using RT Tracker for user feedback]
|}

== First Meeting: Kingston ON, May 6-7, 2010 ==

=== Sign up ===

Free registration -- but registration is now closed (we have 40+ signed up).

=== When and Where ===

'''May 6-7, 2010'''
* Thursday: 2pm-5:30pm, followed by dinner and drinks
* Friday: 9am-4:30pm

Meeting location:
* [http://maps.google.com/maps/ms?hl=en&ie=UTF8&oe=UTF8&source=embed&msa=0&msid=103786326471006763157.0004700577498a9166e33&ll=44.227888,-76.494584&spn=0.009226,0.012875&z=15| 93 University Ave, Queen's University, Kingston Ontario] (map)
* Meeting room: [http://library.queensu.ca/library/floorplans/index.php?library=Douglas&floorpos=4F&section=North_Reading_Room#map| 1966 North Reading Room, Level 7, Douglas Library Building] (floorplan) - located on the top floor, just follow the signs to find the room.

=== Cost ===

There was no charge. Queen's University very generously supplied the space, the Internet connection, and free lunch on Friday!

=== How to get involved ===

Join the mailing list. That is where the planning will happen.

=== Format ===

* 5-minute lighting talks
* 20-minute talks
* BOAF sessions
* Maybe a hackfest.

=== How many are attending? ===

45 people have registered. Most will be attending.

=== Program ===

'''Thursday May 6:'''

* 2pm-5pm: Open format (hang out and hack)
* Evening: Go out for dinner and drinks

'''Friday:'''

* 9am-4:30pm: Schedule currently "under construction" -- see table below.

Morning Break: 10:30-10:45 .... Lunch: 12-1 ....

Afternoon: 5 minute lightning talks .... "Birds of a feather" breakout sessions (sign up sheets on front table)

{| border=1
! Name
! Description
|-
| William Denton || OpenFRBR
|-
| Walter Lewis || Exposing Linked Data
|-
| Art Rhyno || Open Layers and Newspapers (Walter Lewis)
|-
| MJ Suhonos || [http://mytpl.ca Location-aware Mobile Search]
|-
|Alan Harnum || Building A [http://beta.torontopubliclibrary.ca/ Library Website] with [http://www.endeca.com/ Endeca] technology
|-
|Wendy Huot || "Your feedback, please": library web design critique
|-
|Glen Newton || [http://zzzoot.blogspot.com/2009/07/project-torngat-building-large-scale.html Using Open Source Tools for Visualization and Semantic Mapping in a Large Scale Article Digital Library]
|-
| Eric Palmitesta || XQuery
|-
| John Miedema || [http://code.google.com/p/openbook4wordpress/wiki/index OpenBook WordPress Plugin Update - Why It's Cool to Love OpenURL +++]
|-
|Nasser Saleh || Coagmento!: a potential collaborative search tool
|}

== Who's interested in Code4Lib North? ==

Declare your interest in a Code4lib North chapter:

* Wendy Huot, Queen's University
* Michael Vandenburg, Queen's University
* [http://www.miskatonic.org/ William Denton], York University
* John Fink, McMaster University
* [http://ruebot.net/ Nick Ruest], [http://digitalcollections.mcmaster.ca/ McMaster University]
* Walter Lewis, Halton Hills/OurOntario
* Edward Corrado, Binghamton University (NY, USA)
* [http://thebookpile.wordpress.com Warren Layton], Library of Parliament (Ottawa)
* Pascal Calarco, University of Notre Dame (IN, USA)
* Rob Fox, University of Notre Dame (IN, USA)
* Mita Williams, University of Windsor
* John Fereira, Cornell University
* MJ Suhonos, Toronto Public Library
* Dianne Dietrich, Cornell University
* David Fiander, University of Western Ontario
* Peter Schlumpf, [http://www.avantilibrarysystems.com/ Avanti Library Systems]
* Roy Zimmer, Western Michigan University
* Kimberly Silk, Martin Prosperity Institute, University of Toronto
* Andrew Darby, Ithaca College (Ithaca, NY)
* Laura Harris, Grand Valley State University (western Michigan)
* Tim Ribaric, Brock University
* Sibyl Schaefer, University of Vermont
* Peter Ellinger, Ontario Legislative Library, Toronto
* Keith Jenkins, Cornell University
* [http://pmlozeau.ca/ Patrick M. Lozeau]
* Mike Kreyche, Kent State University
* Graham McCarthy, [http://www.ryerson.ca/library/ Ryerson University]
* [http://johnmiedema.ca John Miedema]
* Janey Chen, Ontario Legislative Library, Toronto
* Rob McDonald, Carleton University
* Amy Buckland, McGill University
* Tricia Williams (pgwillia), Consultant/[http://search.ourontario.ca OurOntario]
* Mike Beccaria, Paul Smith's College (Paul Smiths, NY)
* Amanda Etches-Johnson, McMaster University
* Art Rhyno, University of Windsor
* [http://bethmaru.com Mary Beth Baker], CIC (Ottawa)
* Wayne Schneider, Hennepin County Library
* Carol Serroul, CISTI
* Graham Stewart, University of Toronto Libraries
* Peter Zimmerman, University of Windsor
* Margaret Kipp, University of Wisconsin Milwaukee
* [http://coffeecode.net Dan Scott], Laurentian University
* Lawrence Wardroper (Courts Administration Services Library, Ottawa)
* Matt McCollow, McMaster University
* [http://www.parser.ca/z678/ George Duimovich], NRCan Library (Ottawa)
* [mailto:bobbi_fox@harvard.edu Bobbi Fox], Harvard University Library (Massachusetts)
* Dileshni Jayasinghe, OCUL, University of Toronto
* Eric Palmitesta, OCUL, University of Toronto
* [http://twitter.com/alxp Alexander O'Neill], Robertson Library, University of Prince Edward Island
* Chris Beer, WGBH (Massachusetts)
* Robin Isard, Algoma University (Sault Ste Marie ON)
* Pat Moore, Carleton University (Ottawa ON)
* [http://wagathon.tumblr.com/ Alan Harnum], Toronto Public LIbrary (Toronto ON)
* Colin Prince, University of Toronto Libraries
* Tom Keays, Syracuse University LIbrary (Syracuse, NY)
* Chris Charles, University of Guelph (Guelph, ON)
* John MacGillivray, Carleton University (Ottawa ON)
* Lester Webb, Kingston Frontenac Public Library (Kingston ON)
* Elizabeth Goldman, Kingston Frontenac Public Library (Kingston ON)
* Jennifer O'Donnell, Kingston Frontenac Public Library (Kingston ON)
* David Smith, Kingston Frontenac Public Library (Kingston ON)
* Loren Fantin, Our Ontario,Knowledge Ontario
* Daulton Theodore, Carleton University (Ottawa, ON)
* Peter MacDonald, Hamilton College (Clinton, NY)
* Rebecca Larocque, North Bay Public Library (North Bay, ON)
* Doris Rankin, Library and Information Management Consultant, Ottawa, ON
* Diane Bédard, Learn Ontario & Our Ontario; Knowledge Ontario
* [http://www.arts.uottawa.ca/eng/avellino.html Andre Vellino], CISTI / University of Ottawa
* [http://twitter.com/markswartz Mark Swartz], Queen's University
* Adam Wead, Rock and Roll Hall of Fame Library and Archives (Cleveland, OH)
* Pramila Thakur, Ontario Legislative Library, Toronto
* Anthony Petryk, University of Ottawa
* Jan Dawson, Ask Ontario, Knowledge Ontario
* [http://lab.cisti-icist.nrc-cnrc.gc.ca/cistilabswiki/index.php/Glen_Newton Glen Newton], Carleton University
* Patrick McMaster, Leeds & the 1000 Islands, Rideau Lakes, and North Grenville Public Libraries
* Nasser Saleh, Queen's University (Kingston ON)
* [http://stefansinclair.name/ Stéfan Sinclair], McMaster University
* [http://williamjturkel.net/ William J Turkel], University of Western Ontario
* Shirley Lew, [http://library.vcc.ca/ Vancouver Community College], (Vancouver BC)
* [http://twitter.com/edbilodeau Edward Bilodeau], [http://www.mcgill.ca/library/ McGill University]
* Andrew McAlorum, University of Toronto Libraries

== Meeting Location Suggestions for the Future ==

* Toronto, Ontario
* Sudbury, Ontario
* Ottawa, Ontario
* Montreal, Quebec

User:Shadowspar

2012-05-16T16:36:46Z

Shadowspar: New page: ...aka Rick Scott, Library Techologies Specialist at Wishart Library, Algoma University. Find me elsenet at these places: * Blog: http://rickscott.dreamwidth.org/ * Twitter: [http://twi...

...aka Rick Scott, Library Techologies Specialist at Wishart Library, Algoma University.

Find me elsenet at these places:

* Blog: http://rickscott.dreamwidth.org/
* Twitter: [http://twitter.com/shadowspar @shadowspar]
* GitHub: [http://github.com/rickscott rickscott]
* Gitorious: [http://gitorious.org/~rickscott rickscott]