It ’ s their cloud, not yours!

1. It’s their cloud, not yours!

2. contents • residents & visitors • bring your own everything • approaches to personalisation • emerging issues • the personal cloud: a glimpse at a future • how do we respond?

3. residents & visitors

4. Web-users are either residents or visitors • a new way of framing types of users conceived by David White (Oxford University) • “We found that our students could not be usefully categorised as Digital Natives or Digital Immigrants. i.e. This distinction does not help guide the implementation of technologies it simply provides the excuse that “some people ‘just don’t get it’ which is why your new approach has failed so badly…” • “In effect the Resident has a presence online which they are constantly developing while the Visitor logs on, performs a specific task and then logs off.” • http://tallblog.conted.ox.ac.uk/index.php/2008/07/23/not-natives-immigrants-but-visitors-residents/

5. bring your own everything

6. bring your own device?

7. bring your own infrastructure!

8. approaches to personalisation

9. “It's Not Information Overload. It's Filter Failure” • Clay Shirky, 2008

10. building better filters

11. library activity data • The University of Huddersfield Library • “We have collected 3.9 million library circulation records over 15 years.” • “If you do not use the library, you are over seven times more likely to drop out of your degree. 7.19 to be precise." • http://www.jisc.ac.uk/publications/reports/2012/activity-data-delivering-benefits.aspx

12. Local context, expressed as activity data • analytics are fashionable • evidence-based service provision is the goal • highly responsive service delivery is something to aim for • predictive analytics are the holy grail • http://www.jisc.ac.uk/publications/reports/2012/activity-data-delivering-benefits.aspx

13. Jerome: axes of personalisation • Where? • which campus do you study on? Which library do you want to use? how far from the University do you live? Are you a distance learner/researcher? • Who? • are you a student? Undergraduate or postgrad? Or a member of staff? Teaching- or research-focused [or both]? Or maybe you’re one of our Associate Readers or a visitor to the Library? • What? • which subject(s) do you study/teach/research, within which of the University’s faculties? • http://jerome.blogs.lincoln.ac.uk/

14. emerging issues:accuracy, privacy, control

15. poor characterisations of individual users • current recommender systems do not work so well, especially when the context is broad. Within a single, focussed application, they can be made to work, but not across the internet • data is gathered anonymously and from poorly differentiated contexts • this adds up to what Eli Pariser, in The Filter Bubble, calls: • “a bad theory of you”

16. cookies From the Wall Street Journal’s What do they Know About You? "The one site that installed the most was Dictionary.com. A visit to Dictionary.com resulted in 234 trackers being installed on our test computer [...] the vast majority of the trackers (200 out of 234) were installed by companies that the person visiting the site probably had never heard of." http://www.npr.org/templates/story/story.php?storyId=129298003

17. privacy, control & the Facebook experiment • we gain personalised services at the expense of the possibility of having any control over what we’re willing to reveal • the regular “mistakes” made by Facebook have all eroded the user’s control over their privacy in the system by making it very, very hard to understand • contract of adhesion - “a contract between parties of greatly unequal bargaining power....” • http://en.wikipedia.org/wiki/Friedrich_Kessler • but - this is not the internet, it’s just one application. Facebook will fade.... • the world is experimenting with privacy

18. uncoordinated personalisation everywhere • the only place this can really be coordinated in a future-proof way is by the client • either acting directly as a user • or • through some proxy which is instructed and trusted by the user • attention (data) is a valuable currency

19. expectations are changing - VRM • from Customer Relationship Manager (CRM) to Vendor Relationship Management (VRM) • Principles of VRM • Customers must enter relationships with vendors as independentactors • Customers must be the points of integration for their own data • Customers must have control of data they generate and gather. This means they must be able to share data selectively and voluntarily • Customers must be able to assert their own terms of engagement • Customers must be free to express their demands and intentions outside of any one company's control • http://cyber.law.harvard.edu/projectvrm/Main_Page

20. the personal cloud: a glimpse at a future

21. The Personal Cloud will replace the Personal Computer as the centre of users' digital lives by 2014 • http://www.gartner.com/it/page.jsp?id=1947315

22. defining the personal cloud (1) • those remote, digital services used by you, personally • essentially, you have your own infrastructure, provided by a number of suppliers • you choose (within quite narrow constraints) which systems you use

23. defining the personal cloud (2) • as for definition 1, but with the following constraints: • data: you decide what data to store and control access to it • apps: you decide which apps to use from which vendors and what data they can access • terms: you define your own terms of service for anybody interacting with the data or the apps on your personal cloud. You can easily move your personal cloud to a competing hosting vendor if you so desire http://personal-clouds.org/wiki/Main_Page

24. VRM: fourth parties • a new type of business on the net • third parties who work for the user, rather than the service provider • the fourth party represents the user’s interests • in other words, an agent, or broker, or mediator • a new breed of companies providing such services starting to appear

25. the live web • a very different way of looking at the Web • the Web is fundamentally based on a request-response paradigm • the requests can be enriched by applying contextual information supplied by the client - under the control of the user • mixing APIs, rules and events • when this event happens, send this message to this service

26. the future - APIs for users? • agents which can act as the user’s persona - presenting a constrained and focussed interface to the world • filters which learn and adapt to changing priorities, sources & rules in a chaotic world • a secure place for them to curate data about themselves and their preferences • resulting in: • systems which use contextual information curated by the user or by their agent, and which deliver accurately personalised services and recommendations

27. how do we respond?

28. responsive (Web?) design • designing for interaction with users through the same systems interface but on different: • devices (desktop & laptop computers, tablets, smart-phones, even not-so-smart phones) • applications (‘apps’) Image taken from the Kineo website: http://www.kineo.com/mobile-learning/responsive-e-learning-for-multi-devices.html

29. new patterns - notifications, trusted application... • users have expectations about the sorts of features they expect from online services, e.g.: • notifications - presented in a standard way (not so much through RSS as through dedicated apps) • integration and ‘trust’ relationships between systems they are already happily using - e.g. OAuth

30. changing attitude of institutional IT support • BYOE is welcome opportunity for customers, unwelcome problem for staff • What excites IT leaders in higher education most about BYOE are opportunities to diversify and expand the teaching and learning environment, while the greatest challenges are issues that pertain to faculty and staff use of their own devices for work-related purposes. • IT infrastructure is middle-ware between institution and users’ infrastructure • Think of IT infrastructure as BYOE "middleware" — the commodities that bridge users, their devices, and their consumer-level applications to the institution's data, services, systems, and enterprise-level applications. IT middleware should be robust, yet nimble. • Eden Dahlstrom, BYOD and Consumerization of IT in Higher Education Research, 2013, • http://www.educause.edu/ero/article/executive-summary-byod-and-consumerization-it-higher-education-research-2013

31. serve residents & visitors • build a picture of which of your users are residents, and which are visitors • be mindful that users who are visitors in the library context, may be residents elsewhere • consider how you might reach out to the residents in their wider ‘residency’ • consider how library services (will) appear in each user’s personal ‘cloud’

32. turn the problem into an opportunity • new literacies • Those of us who work with students must guide them to build their own personal cyberinfrastructures [...] And yes, we must be ready to receive their guidance as well. • Gardner Campbell, A Personal Cyberinfrastructure, http://www.educause.edu/ero/article/personal-cyberinfrastructure • we should surely embrace this empowerment of the user? • Very few faculty or administrators are curious enough about the Internet, or eager enough to learn about the participatory culture it empowers, to even begin to imagine how to use or empower personal, interactive, networked computing in meaningful, effective ways in teaching and learning. • Gardner Campbell http://www.educause.edu/ero/article/wild-card-character-bring-your-own-panel-discussion

33. implications for the library • we need to: • be ready to anticipate a growing demand from our users that theycontrol the relationship more than we • be ready to respond to pressure to reform how user’s activities are tracked (c.f. new ‘Cookie legislation) • consider how our services (will) fit into each user’s personal cloud • the library system: • the notion of the user ‘visiting’ the library system to find resources will become increasingly anachronistic • browsing as a human activity will fall away, search is king for now • over time, search will gradually become less apparent to the user too • the ratio of software to human ‘agents’ interfacing with the LMS will shift away from the human

34. thank you! Paul Walk paul@paulwalk.net @paulwalk http://www.paulwalk.net

35. image credits • Iphone: http://commons.wikimedia.org/wiki/File:Iphone_4G.jpg • Google logo: http://commons.wikimedia.org/wiki/File:Googlelogo.png • iCloud: http://en.wikipedia.org/wiki/File:Apple_iCloud.png • Amazon: http://en.wikipedia.org/wiki/File:Amazon.com-Logo.svg • Amazon Kindle: http://en.wikipedia.org/wiki/File:Amazon_Kindle_logo.svg