Access 2016

• Our transition from a server-centered thought process towards treating web instances as 'applications'.
• The determination and implementation of a common server OS across Development/Staging/Live platforms.
• Provisioning of hardware from bare-metal with razor-server.
• Server level configuration management in Git and deploying to instances via bare repos.
• Our Thoughts in Choosing Drupal as a core architecture.
• 'One Button' Drupal project and core update deployments via GitHub and Jenkins.
• Post-deployment testing with CucumberJS.
• Local development spin-up with docker, Vagrant, Chef.
• Audit of changes and team notifications through Amazon AWS Tools.
• Adoption of Slack as a core communication tool. 

Discussion will also include the key underpinnings to our decision, with a focus on metadata, identifiers, linked data, and the central role that publisher APIs can play, permitting us to grow our faculty publications 30 fold in less than six months.

 Finally, we’ll demonstrate how we can improve the value and interest in our open access repository by making a major shift to integrate selected non-open access content.

1. Tim Ribaric. A Twitter Bot for the Rest of Us. Twitter indignation, Python, and low-cost VPS services. To investigate all three I wanted to make a Twitter bot that exists at that intersection. To that end @LIS_Grievances was created. The bot that would allow all of us Information Professionals to air our grievances in anonymity. Visions of grandeur and @horse_ebooks ran through my mind. Instead I got a lesson in increasing bot popularity and a good dose of humility. This presentation will look at the components put together to create the bot as well as some of the interesting things it has said. The trickle of tweets it has been responsible for vary from benign to mildly insightful, and a bit obtuse. The best thing is no-one, including the guy that runs the bot, knows who wrote the message except the original author.
2. J Jack Unrau. Transmitting in Cleartext: Digital Privacy Education for Reluctant Technologists. Online privacy is a concern for everyone, not just technophiles. As issues of digital surveillance and its political ramifications become increasingly well-known, the public's appetite for skills and tools to cope has grown. Tor, encryption and the mechanics of online tracking are complicated and segments of the public that know they should care aren't people who've written a line of code or even read any Neal Stephenson novels. In public libraries we're leading electronic privacy workshops for users who know they don't want to be spied on but may not know what a web browser is. The challenges aren't just technological but communicative. I'll be talking about the techniques that have (and haven't) worked for me in helping users build these privacy-tech literacies, and what we tool-teachers need from tool-makers to be the badass profession Snowden says we are.
3. Naomi Eichenlaub. Making MARC Actionable: URIs in Subfield Zero ($0). Uniform Resource Identifiers (URIs) are globally unique character strings used to identify resources; they also play a critical role in linking data on the Web. The addition of dereferenceable (ie. actionable) URIs to MARC records is a significant step we can take in our current systems that will have meaningful impact when our data is taken out of the ILS and translated for external use, for example in discovery services. Moreover, the addition of URIs in our current systems will also aid in the reuse of MARC data in the linked environment by facilitating migration to other metadata formats. Making MARC actionable by adding URIs where appropriate and available will also make our library metadata interoperable within the larger metadata and controlled vocabulary communities. This lightning talk will survey work currently underway on implementing URIs in MARC using $0, including initiatives coming out of the Library of Congress Program for Cooperative Cataloging (PCC) Task Group on URIs in MARC, George Washington University Libraries, and a small experiment at Ryerson University Library & Archives (RULA).
4. Trina Grover. You Made that Yourself?!  Knitting is similar to coding because it’s binary, there are 2 stitches that are combined in various ways to make new things. What happens when we bring knitters and coders together? The Ryerson Digital Media Experience lab is building resources and communities around computational textiles in order to enhance diversity in our makerspace. Starting with beginner workshops to create simple knit fabrics, the program has progressed to wearable computational fabrics. This experimental program has empowered students and staff to merge old and new technologies to create objects that are both functional and decorative.
5. Wiktor Rzeczkowski. Easing the Collaboration Curse for Access. As people can achieve things collectively that they cannot achieve individually, the cult of collaboration has become ubiquitous and reached the knowledge work where uninterrupted concentration is the principal virtue and where the collaboration interruptions, meetings, emails, calls become a curse. In this lightning talk an approach will be presented to ease the collaboration curse in the area of development and maintenance of online user services .
6. Gillian Byrne. If 'Libraries are Software', What Does That Look Like? Cody Hanson’s Libraries are software [codyhanson.com/writing/software.html] argues that the library is now software; that our products and services can no longer live outside software, that all staff need to understand the critical importance of software to the library, and that we “must encode our services and our values in the software we provide.”If we accept Cody’s premise, it seems clear that the traditionally organized library isn’t well suited to achieving this vision. This ignite talk will riff off ideas of what a software-centred library looks like. How would it be organized? How would the mission, values and organization planning reflect this shift in outlook? 
7. Sam Popowich. Clojure for the Perplexed. In this Ignite talk, I will cover the principles of functional programming and Clojure, and give a few ideas as to how functional programming principles offer a different way of thinking about data and library technology.
8. Andrew Nagy. Introducing FOLIO – The Community-driven Open Source Library Services Platform. The future is bright – think of a time when we are all working from the same common platform to develop and deliver services to our users. No longer do we need to develop a data model to support our data stores.  No longer do we need to develop APIs to allow our disparate systems to interoperate.  Salesforce.com has its force.com platform and Amazon has its AWS offering. What if there was a Platform-as-a-Service offering for libraries? What if that platform was completely open? This is our bright future. FOLIO is a new initiative supported by the OLE community, EBSCO, IndexData, developers and other service providers to provide this future for us all as fully open source software.  With an app-store like environment, we can truly collaborate to offer the best of breed services and solutions that meet the needs of each and every library.
9. Laura Wrubel. Need Help with Your Code? Providing a Programming Consultation Service at the Library. George Washington University Libraries undertook a pilot to provide programming and software development consultation services for the university community.  The consultation services took the form of half hour appointments conducted by librarians with software development expertise, similar to other reference services offered by the library. I'll talk about why we did this, how we set it up, how it went, and what we've learned in offering this service.