ITANA 2016: API Architecture and Implementation

Editor's Notes

• #11: Open Data does NOT include Personally Identifiable Data
• #12: Routine disclosure Open Data Access By Design
• #13: It was the classic Canadian maneuver. Do something that has already been done in another vertical here in Canada and jump on the train. (It very difficult to start a trend from scratch).
• #15: Open Data comes in a spectrum ★ Open License (OL): make your stuff available on the Web (whatever format) under an open license. Most importantly, to get any star at all, the data must be licensed to be explicitly as Open. ★★ (Machine) Readable (RE): make it available as structured data (e.g., Excel instead of image scan of a table).              ★★★ Open Formats: use non-proprietary formats (e.g., CSV instead of Excel).             ★★★★ Uniform Resource Identifier (URI): use URIs to denote things, so that people can point at your stuff.                ★★★★★ Linked Data (LD): link your data to other data to provide context. From <http://5stardata.info/> Open Data is about releasing human-targeted information in ways that are increasingly easier and more efficient to manipulate by 3rd parties.
• #17: The Data economy is about taking something with an initial value and driving a whole value chain around it so that it amplifies utility gained many fold. The utility Is gained though Increased Economies of scale. For example data which is usually disclosed on a piece meal basis can now be intentionally routinely disclosed. Increased value of data. While the originators of data are once uniquely positioned to amplify the reach and impact of their data, with routinely disclosed data, the network of people within the institutions and other related institutions can become many-fold force multipliers resulting in economic benefit.
• #18: Quite simply, Open Data allows for the network around the data purveyors to do more with less.
• #22: Open Data can be mashed up with private data to make service-based tools such as the Student Portal
• #25: Do the ETL work once, do it well. Reduce duplication of efforts. Cut down on costs because it comes in a ‘usable’ form. Referential links are moved around as URIs. (context) Access can be monitored and controlled.
• #29: Full room of 51 staff and students came to watch the demos and talk about open data. 9 demos presented, 8 of which were student-created projects. Connected ~14 new people to the Open Data mailing list & ~8 new people to the SDN mailing list. * Significant VeloCity turnout: 2 demos were VeloCity coding weekend projects; ~10 members of VeloCity were in attendance; Expressed great interest to participate in "building apps fast" with University data. * Collaboration with the Computer Science Club: Approached by the CSC Librarian to plan a Coding Party to work on the Open Data API/SDN project(s). * Spreading the story: An Imprint author was in attendance and are meeting with Giles to write a story that will loop in the broader student body about student development. * We were able to connect like-minded students in a way that fostered creative, energetic discussion about what's next in student development at University of Waterloo.
• #30: http://lists.uwaterloo.ca/pipermail/opendata/2011-October/000080.html
• #39: Locations https://uwaterloo.ca/food-services/content/revelation-ron-eydt-village https://uwaterloo.ca/food-services/node/143/edit https://uwaterloo.ca/food-services/locations-and-hours https://api.uwaterloo.ca/v2/foodservices/locations.json?key=dem0hash https://github.com/uWaterloo/api-documentation/blob/master/v2/foodservices/locations.md http://env-apps.uwaterloo.ca/campus-map-demo/leaflet.html# | POI | Places | Food Services https://uwportal.uwaterloo.ca/Index#/Home/FoodServices Menu Input Data: https://uwaterloo.ca/food-services/weekly-menu Serve Data: http://api.uwaterloo.ca/v2/foodservices/menu.json?key=dem0hash Document Serving of Data: https://github.com/uWaterloo/api-documentation/blob/master/v2/foodservices/menu.md
• #42: http://watpark.ca/home/ http://api.uwaterloo.ca/public/v1/?service=watpark&key=dem0hash http://api.uwaterloo.ca/docs/v1/#!/watpark http://env-apps.uwaterloo.ca/campus-map-demo/leaflet.html# | click on Parking | Visitor Parking E.g. http://i.imgur.com/b7pEvnX.png https://uwportal.uwaterloo.ca/Index#/Home/Parking
• #43: https://github.com/uWaterloo/Datasets https://github.com/uWaterloo/Datasets/tree/master/Salaries
• #47: News/Events/Blogs
• #60: Events Create Content: https://uwaterloo.ca/canary/node/add/uw-event Publish to Endpoint: https://uwaterloo.ca/canary/api/v1/events/all_events.json?api-key=96ab9383e6ad48c23aa1504dc9cc5c52 Proxy via a consistent endpoint (aggregated): http://api.uwaterloo.ca/v2/events.json?key=dem0hash https://uwportal.uwaterloo.ca/Index#/Home/News Syndication on other Drupal Sites
• #62: Aggregators are force multipliers because they are a form of 5 star data
• #63: Seeded: Buy vs. Build? How to build today? Start with Open Data to get started. Lean on IPC AbD. Stick with microframeworks, build light and build quick.  Fail early and learn often. Documentation -> RAML and Swagger, etc. ERP culture clash Data Governance…