Access 2018 Conference: Morning Sessions Day 1 #AccessYHM
Access 2018 Conference
User Experience (UX) at McGill: Case Studies in Applied User Research
Ekaterina Grguric
User experience is primary role, also supports website and service design. Serves as consultant within library as well as with others doing user research in context of specific services, also trains on best research practices. UX as concept and methods are not new at McGill, because UX shares a toolkit with assessment, communications, etc. UX as operational and UX as project based. Notion of ongoing service improvement. Doesn't seek REB/IRB for most projects so can quickly set up usability. (REB doesn't inherently make something ethical, remember.)
Toolbox model of UX - sum of many methods. Can ease, simplify, clarify, build consensus around an approach. Provide a check for assumptions we may or may not be aware of. Bringing UX doesn't have to be expensive. Not listed to before/after a project lifecycle, UX methodologies can be brought in at many stages. Traditional waterfall vs more iterative projects but bringing iterative components into even waterfall can be done and should be considered. UX is a decision making tool - about being intentional in questions we ask to better design services and tools.
Intentional UX inquiry at different stages with different goals, reflects contexts.
1. Improving UX of new self check machines (inform documentation). Immediate interaction problems. After configuring what was possible, usability testing helped intentionally identify core issues. Five 1.5 hour session up to 6 participants per session. Each session shifted one thing. Guerrilla testing. Used variant of Jenn Down's laptop hugging technique. Tasks were focused on very simple actions like signing out a book and checking account information. Focused on things they could change: button labels and error messages, signage, physical features of machine. A notable feature of self check was slide show ad space. Variant of 10 second test - asked to look away and ascribe top 3 features remembered. Overall identified a few core issues - changed button text, error messages to be clearer, documentation posted instead of ads, physical interventions, documentation instead of ads. Only so much you can do with out of box product. But can better provide use instructions and supported decisions around other forms of support. Did not delay roll-out of self checks.
2. Usability informed config of Worldcat discovery and search bar redesign. UX built into project b UX working group. Updated discovery layer to Worldcat Discovery. Hands tied for many UI decisions, but basic configuration decisions could be A/B tested. UX working group of 6 members from various parts of library, used as cross training space. 3 core methodologies: A/B testing using guerrilla usability methods. Also used to make decisions about search bar interaction design. Paper prototyping to speed things up - low cost and useful. Focus groups to get a sense of core user needs we may have missed - effective for UG and graduate students - gut reactions to catalog, duplicate searches from old system in new one. Uncovered known issues and got diverse viewpoints. Semistructured interviews with task based usability component. For faculty more structured interviews (town hall space for feedback), a way of understanding what needed ot be documented. For staff, internal interviews to prioritize. Working group approach was effective as cross training tool. Large team made sub teams possible for quick iterative tests. UX built in from day 1, group approach worked.
3. Ongoing usability testing series - making space ot test even when testing is not needed. Monthly series of slots dedicated to guerrilla usability tests. Can pivot and accommodate ad-hoc requests easily. Opportunity tot rail between branches regularly makes her more present more accessible and thus UX. Guerrilla testing approach with one note taker and one XX. Each tests asks 3-6 users, 20 minutes, no more than 3-4 tasks. Quick to train and easy to show benefits to show quick data to make decision.
Access Conference 2018
Libraries in the Age of Extended Reality: Virtual Reality (VR), Augmented Reality (AR), Mixed Reality (MR)
Ken Fujiuchi and Joseph Riggie
Virtual Reality - computer generated, controlled, immersive (headsets, AV gear, defined space because movement and tracking can be important). Computer degenerated world to exclusion of real world
Augmented reality - use of real world with data layer overlay. Live, physical view, overlaid sensory information, approachable. Pokemon Go. Not just visual - Microsoft's Soundscape.
Overlap Mixed Reality - a blend of the two.
Role of libraries and librarians in this new extended reality. Content curation and evaluation. 3D scanning and 3D capture, quality and authority control, digital curation is necessary. What content is deserving of digital preservation? What is real? Can librarians act as arbiters of genuine content? (EX - Nick Cage as Indiana Jones? Face replacement, how woiuld you know?)
Cataloging: cataloging for linked data environment, data can be independent of object, new ways to catalog and record metadata. Local historical data and records - we have that but how much of it is lined to external archival and local records?
User experiences: new user interface possibilities, new ways to interact with materials. new ways to access information. (Load typewriter in a field, experience and feel old fashioned typewriter, creates a good enough experience and it may be the only way to get that environment.) How would we recreate library?
Digital preservation - preserve interactions and experiences, 3D reproduction, preservation through data. Ex interview Holocaust survivor interview, asked over 200 questions, recorded in 3D, can store HIS experience as holographic image, kids can ask questions and knowledgeable rehashes his responses. We can now record not just content but experience - have conversations based on that person's responses, nuances, and physical expressions.
Examples
1. 360 recording kit. VR licensing not always licensed for academic libraries - no derivatives, etc. To make it easier to record VR content and make available: ESE - VR recording kit (Ricoh Theta V camera, low profile stand, 3D spatial audio recording, protective case, user guide, release template and legal guides - like avoiding bathroom entrances, law enforcement). Other project is portal through which these can be accessed. Ex - capture of night sky can be used by astronomy class - using Omeka S - working with local library consortium.
2. Shelvar - use AR and visual identifiers to find misplaced books. Discontinued due to patent dispute, Amazon has locked down patents. Can find missing or mishelved, and instructions on how to replace. We will be locked out because these patents and technologies will be patented by big media. Optical recognition tags. Use sensor based, measurement based - LIDAR. We already know things are in order, we have descriptive data in records. Like a robot comb the shelves at night, find missing items :) More accurate map via plane in 30 minutes than archaeology 50 years. Are libraries ready for this kind of content?
Old city of Dubrovnik - recreate spaces with existing datasets, public Flickr images, full 3d model without needing expert help - crowdsourced and AI algorithm combs through and creates 3D model.
Don't want paywalls to happen to reality - license Niagara Falls or Statue of Liberty, to be able to make the experience available. Content required to come back with creative commons license.
What about storage needs? Doesn't have to pull from video - create a reference point, not an exact replica.
Developing an Open Source Application for Managing EzProxy Configuration File
Juan Denzer
Gives access by using a proxy server - web prefix. Wanted to work on configuration file. Over time, can grow because you'll have folks who manage it who don't take things out as needed. Not uncommon for it to get really huge.
Purpose of config file - flat file, holds stanzas for each resource, contains EZProxy options and setting, manages authentication, includes external files (black/white lists), and comments which are important.
Overhauling the config file could take weeks of work. Need to develop something to do this. Why the application? Often years of neglect - comment something out, not sure why. Changing of the guard - someone leaves then flat file inherited. Thousands of lines. The time it takes. We have the computer technology and we should use it.
Parse program to manage config file. Need to break down stanzas, separate config settings and put stanzas in dataset so we can read it. Also important for it to be open source. Decided also to make sure is cross platform. initially wanted to develop in .net because one person knew it better, but student told about cross platforming in Java. Two CS students working on it (Abishek Rauniyar at SUNY Oswego and Marika Bajracharya SUNY Brockport. Run as non SQL database.
Want ot manage stanzas to search for stanzas, sort it as viewing it, viewing, being able to test stanzas. Also look into managing proxy settings. Commenting system is important - everyone has a different style - initials, date first, no date, etc. Want to recognize comments. .Exporting a managed config file in format you want. Future improvements: import stanzas from OCLC site or listserv, version control, backup file system for config file, Google calendar API config for alerts like expiries of trials.
User Experience (UX) at McGill: Case Studies in Applied User Research
Ekaterina Grguric
User experience is primary role, also supports website and service design. Serves as consultant within library as well as with others doing user research in context of specific services, also trains on best research practices. UX as concept and methods are not new at McGill, because UX shares a toolkit with assessment, communications, etc. UX as operational and UX as project based. Notion of ongoing service improvement. Doesn't seek REB/IRB for most projects so can quickly set up usability. (REB doesn't inherently make something ethical, remember.)
Toolbox model of UX - sum of many methods. Can ease, simplify, clarify, build consensus around an approach. Provide a check for assumptions we may or may not be aware of. Bringing UX doesn't have to be expensive. Not listed to before/after a project lifecycle, UX methodologies can be brought in at many stages. Traditional waterfall vs more iterative projects but bringing iterative components into even waterfall can be done and should be considered. UX is a decision making tool - about being intentional in questions we ask to better design services and tools.
Intentional UX inquiry at different stages with different goals, reflects contexts.
1. Improving UX of new self check machines (inform documentation). Immediate interaction problems. After configuring what was possible, usability testing helped intentionally identify core issues. Five 1.5 hour session up to 6 participants per session. Each session shifted one thing. Guerrilla testing. Used variant of Jenn Down's laptop hugging technique. Tasks were focused on very simple actions like signing out a book and checking account information. Focused on things they could change: button labels and error messages, signage, physical features of machine. A notable feature of self check was slide show ad space. Variant of 10 second test - asked to look away and ascribe top 3 features remembered. Overall identified a few core issues - changed button text, error messages to be clearer, documentation posted instead of ads, physical interventions, documentation instead of ads. Only so much you can do with out of box product. But can better provide use instructions and supported decisions around other forms of support. Did not delay roll-out of self checks.
2. Usability informed config of Worldcat discovery and search bar redesign. UX built into project b UX working group. Updated discovery layer to Worldcat Discovery. Hands tied for many UI decisions, but basic configuration decisions could be A/B tested. UX working group of 6 members from various parts of library, used as cross training space. 3 core methodologies: A/B testing using guerrilla usability methods. Also used to make decisions about search bar interaction design. Paper prototyping to speed things up - low cost and useful. Focus groups to get a sense of core user needs we may have missed - effective for UG and graduate students - gut reactions to catalog, duplicate searches from old system in new one. Uncovered known issues and got diverse viewpoints. Semistructured interviews with task based usability component. For faculty more structured interviews (town hall space for feedback), a way of understanding what needed ot be documented. For staff, internal interviews to prioritize. Working group approach was effective as cross training tool. Large team made sub teams possible for quick iterative tests. UX built in from day 1, group approach worked.
3. Ongoing usability testing series - making space ot test even when testing is not needed. Monthly series of slots dedicated to guerrilla usability tests. Can pivot and accommodate ad-hoc requests easily. Opportunity tot rail between branches regularly makes her more present more accessible and thus UX. Guerrilla testing approach with one note taker and one XX. Each tests asks 3-6 users, 20 minutes, no more than 3-4 tasks. Quick to train and easy to show benefits to show quick data to make decision.
Access Conference 2018
Libraries in the Age of Extended Reality: Virtual Reality (VR), Augmented Reality (AR), Mixed Reality (MR)
Ken Fujiuchi and Joseph Riggie
Virtual Reality - computer generated, controlled, immersive (headsets, AV gear, defined space because movement and tracking can be important). Computer degenerated world to exclusion of real world
Augmented reality - use of real world with data layer overlay. Live, physical view, overlaid sensory information, approachable. Pokemon Go. Not just visual - Microsoft's Soundscape.
Overlap Mixed Reality - a blend of the two.
Role of libraries and librarians in this new extended reality. Content curation and evaluation. 3D scanning and 3D capture, quality and authority control, digital curation is necessary. What content is deserving of digital preservation? What is real? Can librarians act as arbiters of genuine content? (EX - Nick Cage as Indiana Jones? Face replacement, how woiuld you know?)
Cataloging: cataloging for linked data environment, data can be independent of object, new ways to catalog and record metadata. Local historical data and records - we have that but how much of it is lined to external archival and local records?
User experiences: new user interface possibilities, new ways to interact with materials. new ways to access information. (Load typewriter in a field, experience and feel old fashioned typewriter, creates a good enough experience and it may be the only way to get that environment.) How would we recreate library?
Digital preservation - preserve interactions and experiences, 3D reproduction, preservation through data. Ex interview Holocaust survivor interview, asked over 200 questions, recorded in 3D, can store HIS experience as holographic image, kids can ask questions and knowledgeable rehashes his responses. We can now record not just content but experience - have conversations based on that person's responses, nuances, and physical expressions.
Examples
1. 360 recording kit. VR licensing not always licensed for academic libraries - no derivatives, etc. To make it easier to record VR content and make available: ESE - VR recording kit (Ricoh Theta V camera, low profile stand, 3D spatial audio recording, protective case, user guide, release template and legal guides - like avoiding bathroom entrances, law enforcement). Other project is portal through which these can be accessed. Ex - capture of night sky can be used by astronomy class - using Omeka S - working with local library consortium.
2. Shelvar - use AR and visual identifiers to find misplaced books. Discontinued due to patent dispute, Amazon has locked down patents. Can find missing or mishelved, and instructions on how to replace. We will be locked out because these patents and technologies will be patented by big media. Optical recognition tags. Use sensor based, measurement based - LIDAR. We already know things are in order, we have descriptive data in records. Like a robot comb the shelves at night, find missing items :) More accurate map via plane in 30 minutes than archaeology 50 years. Are libraries ready for this kind of content?
Old city of Dubrovnik - recreate spaces with existing datasets, public Flickr images, full 3d model without needing expert help - crowdsourced and AI algorithm combs through and creates 3D model.
Don't want paywalls to happen to reality - license Niagara Falls or Statue of Liberty, to be able to make the experience available. Content required to come back with creative commons license.
What about storage needs? Doesn't have to pull from video - create a reference point, not an exact replica.
Developing an Open Source Application for Managing EzProxy Configuration File
Juan Denzer
Gives access by using a proxy server - web prefix. Wanted to work on configuration file. Over time, can grow because you'll have folks who manage it who don't take things out as needed. Not uncommon for it to get really huge.
Purpose of config file - flat file, holds stanzas for each resource, contains EZProxy options and setting, manages authentication, includes external files (black/white lists), and comments which are important.
Overhauling the config file could take weeks of work. Need to develop something to do this. Why the application? Often years of neglect - comment something out, not sure why. Changing of the guard - someone leaves then flat file inherited. Thousands of lines. The time it takes. We have the computer technology and we should use it.
Parse program to manage config file. Need to break down stanzas, separate config settings and put stanzas in dataset so we can read it. Also important for it to be open source. Decided also to make sure is cross platform. initially wanted to develop in .net because one person knew it better, but student told about cross platforming in Java. Two CS students working on it (Abishek Rauniyar at SUNY Oswego and Marika Bajracharya SUNY Brockport. Run as non SQL database.
Want ot manage stanzas to search for stanzas, sort it as viewing it, viewing, being able to test stanzas. Also look into managing proxy settings. Commenting system is important - everyone has a different style - initials, date first, no date, etc. Want to recognize comments. .Exporting a managed config file in format you want. Future improvements: import stanzas from OCLC site or listserv, version control, backup file system for config file, Google calendar API config for alerts like expiries of trials.
Comments