Access 2012 Pre-Conference: Learning Python

Today’s preconference session was a great way to force me to learn a bit of Python. The very basics were somewhat of a review since I read the first couple of chapters of the recommended book and I actually already knew much of it, but for those interested in knowing, here’s what we learned.

The Book

Much of the material can be found in Think Python: How to Think Like a Computer Scientist by Allen B. Downey.

Another resource: Cheatsheet of common syntax and data structures

The Basics

We covered the basics including:

  • types (string, int, float)
  • arithmetic
  • concatenation
  • values, variables, expressions
  • arguments and basic functions
  • for loop

Read chapters 1-3 (and do the exercises) and you’ll cover it all.

Turtle World

Had some fun drawing with ‘Bob’ the turtle.

This is covered in chapter 4 of the book.

Conditionals and Recursion

We then covered the slightly less than basic of:

  • modulus
  • Boolean expressions
  • conditionals
  • recursions

See chapter 5 of the book.

At the End of the Day

Honestly, the session wasn’t exactly bad, but I think I would’ve learned more by being sat down and simply being told to follow the book. We didn’t have a bad instructor, but I would want to get more than just what the book tells you.

A simple example would be how to get the full list of functions in TurtleWorld for us to play around rather than just telling us the couple functions that are expected in the one or two exercises.

Overall, a good session if you’re a real beginning with absolutely no programming background, but I think that 90+% of the group would have benefited from a much faster pace session. Other than recursion, I noticed that almost all the other times, people around me were doing other things. So, good instructor and session, just too easy for many.

Register for Access Conference

I’m away this week, but felt the need to quickly post about the Access Conference. Last year, I requested the organizing committee to do something for students. In the end, they did two things: add student pricing, and allow volunteers to attend the number of hours they volunteer.

I’m happy to report that this year’s Access also has student pricing with no increase in price!

Register while there’s still space!

code4lib Cool Tool Day

So inspired by the ASIS&T Cool Tool Day, I thought it’d be neat to do one of these since there weren’t many volunteers to do lightning talks/presentations at the code4lib Toronto meetup this time around. Our attendance was a little… paltry, but we had some great presentations! Here are my notes from the session.

Presented by @waharnum

soapUI

  • working with REST based web services
  • testing automation tool for web services
  • best for building with other API
  • autogenerate stubs using WSDL
  • interface between internal systems
  • good for documenting web services, code style with examples
  • normally, mostly used for unit testing

Trello

  • virtual card based whiteboard
  • flexible for planning based
  • collaborative
  • great usability/UI
  • even has mobile apps

Mustache Templates

  • maintaining HTML email templates
  • also works as a crazy text editor for nerds

XSL Transforms plugin in Firefox

  • local reporting
  • anything XSLT with just a few security restrictions
  • e.g. SVN reporting

Presented by @adr

ShowOff

  • cross platform presentation
  • push from laptop to another computer

Sidenote: Other Presentation Tools

Presented by @ruebot

VIM Plugins

  • pathogen – linking for VIM plugins to automatically load VIM plugins
  • nerdtree – pull files quickly by displaying directory/tree

Presented by Pomax

Thimble HTML/CSS Live Web editor

  • teach anyone (kids, adults) HTML and CSS
  • use existing projects to make it fun!

FlickrFindr

  • easy inline flickr search of CC images
  • attribution in alt text

Presented by me

F.lux

  • monitor hue changer, supposedly to help people sleep better by telling your body what time of day it is

That’s it! Hope to do another one of these or lightning talks next time.

Ryerson Going Google with Google Apps: The Run Down

UPDATE: See my more recent blog post if you’re looking for my supplement materials (to the Ryerson Google site) on sync’ing Google Apps.

I attended a session to address concerns with privacy and security concerns in adopting Google apps at the university. Half of the session was actually a general how to protect your own information and your responsibilities as a user. I’ll focus more on the project itself than the second half since there’s a ton of resources about protecting your information already out there.

Google Apps

For the implementation, Sada Systems will be dealing with the actual implementation and migration. Roll out will be done in stages starting with the first four, and the rest will have to go through the evaluation process first.

  • mail
  • calendar
  • docs/drive
  • contact
  • chat
  • mobile
  • sites
  • app engine
  • plus
  • video

Options

  • Faculty and students will have an opt-in option for mail.
  • Staff, however, will be migrated (i.e. not optional).
  • Everyone will be moved to calendar in order to be rid of Groupwise (yay!).
  • Everyone will still keep their @ryerson.ca so there is no change in the email address itself.

Timeline & Next Steps

In a nutshell, there is none, and that’s because the legal agreement hasn’t actually been signed yet.

Once it does get signed, then alpha testing will be done with the CCS group (central IT) and then beta testing with a larger community group. They’re still hoping for a fall rollout though.

Legal Concerns

Most privacy and security concerns revolved around lawful access and warrantless searches with storing data in the US. It was explained that basically, it doesn’t make a difference. Canada has similar legislation and the Mutual Legal Assistance Treaties (with many countries) is a binding agreement to share information under lawful access or warrantless searches, which means the same thing will happen if your data is stored in any of the countries part of the agreement.

Privacy & Data Protection

To alleviate some concerns, the organizing group assured everyone that a Privacy Impact Assessment is done using the international standard, Privacy in Design and ensures that there are no breaches to:

Additionally,

  • all incoming mail goes through the university servers first
  • not opting in means that email stays on the university servers
  • opting in means the emails are then sent and stored on Google servers
  • students emails will not be visible in the global (internal?) address list
  • minimum identifying information (username, name) is used for authentication
  • drives/docs is private by default
  • calendars display only free/busy by default (as in Groupwise right now)

As I mentioned, in the second half of the presentation, we were all reminded that most email/information/data breaches are due to users, not email systems or hardware, and that email is not secure (although they’re looking into encryption for sensitive information). We got the usual spiel on our responsibilities not to include sensitive information in emails, having secure passwords, being careful of phishing, making sure websites use https, etc.

We’ll see how quickly they get things going, but I’m sure many staff will be happy to get rid of Groupwise (which likes to crash at least a couple of times a week and cancels shut down) at the very least.

For more updates, there is a dedicated blog for project updates.

OLITA Digital Odyssey 2012: Outside-In – Approach to Inclusiveness

The presenter spoke quite quickly,and there was a lot of points on the slides, so I didn’t catch everything. I also focused more on design aspects than anything else.

Defining Inclusive Design

  • design that is inclusive of the full range of human diversity with respect to ability, language, culture, gender, age, and other forms of human difference
  • designing for diversity

Digital Exclusion

  • access to online systems no longer an option
  • estimated social and economic cost of digital exclusion
  • required for government, commerce, education ,etc.

Bridging the Gap

  • developers design for the typical or average user
  • Assistive technology (AT) is intended to bridge the gap to reach anyone that requires alternative access systems
  • this bridge is inadequate: only some disabilities and only reaches a few countries

Specialized Assistive Technology

  • 28% of the world
  • rising in cost
  • decreasing in availability

Accessibility Legislation

  • necessary foundation for systematic change
  • AODA groundbreaking approach to legislating accessibility
  • but currently
    • hard to update
    • hard to keep current
    • accessibility requirements seen to constrain innovation
    • fear of implementing new technologies
    • one-size-fits-all solution

Global Consensus

  • need new approach
  • especially with an aging population, which needs more alternatives as they grow older

True Accessibility

Need New Approach

  • more inclusive of full diversity of learners
  • more relevant to educational demands
  • more timely and continuously renewable
  • contextualized or embedded in learner’s context