Systems/Web Services Digital Libraries & Technical Services

Progress Alexis Cavaretta Assistant Manager of Library Web Services

Alexis Cavaretta Web services Earned a MLIS from Pratt Institute in 2012 with a concentration on digital technology, human-computer design, human-information behavior, & usability. Before working with us, she worked with several not-for-profit (relief organizations, archives, & libraries) and for-profit organizations (marketing) doing user-experience design, front-end web development, & project coordination.

Stage 1: Hire a web developer/designer Stage 2: Planning – goals & objectives Stage 3: Implementation Stage 4: Next steps (server-side) Web Planning Overview

 Survey of current website and applications  Code eco-system & integrations  Information Architecture  Establish goals & objectives Web Development Planning

 Align with the look & feel of newschool.edu  Track versions of code using the Agile Framework  Focus on user behavior enhancements  Establish new content publishing workflow  Review Content on current website Web Development Goals & Objectives

 Align with the look & feel of newschool.edu  Coordinate with Marketing & Communication to share code and web property policies  Create a code repository to share code with M&C Web Development Goals & Objectives

 Version control  Maintain quality code  Track changes to files  Implement development workflow  Collaborate more effectively Web Development Goals & Objectives

 Iterative  Shorter Timescale  Collaborative review over sole authorship  Continuous testing  User behavior based Agile Framework

Github Workflow

 User-centered & data-driven design decisions  Using analytics and user research Web Development Goals & Objectives

Usage of index page

Spring – Fall 2014 Website Homepage Web development Updated Look & Feel

2015 Website Homepage Web development Updated Look & Feel

 LibCal hours API  Localist Events  Featured Resources – book slider  Rebrand 2015  Neue font & logo  Off-canvas global & mobile navigation  Parsons red Web Development Additional Functionality

 Find patterns in:  Users’ expectations, in general  Users’ needs  How users find information User experience Card Sort

Open card sort  They were asked to labeled each group.  Participants were not required to sort all the cards.  The cards were also randomized for each participant. User experience Methodology

 Qualitative: including participant comments.  Quantitative: including card sort and category ranking metrics as well as general frequency of similar terms used. User experience Data Collected

As facilitator, I conducted a card sort with 30 cards and a total of 16 participants over 3 weeks. User Experience Card Sort

Areas of strong agreement across the card sorters:  10 out of 16 people organized by interacting with staff versus general information  12 out of 16 differentiated between account specific, research specific, and library policy information  11 out of 16 didn’t know what to do with Subject Liaison Directory User Experience Data Collected

comments “ [Ask Us] should connect me to someone in the library – like or something, not a Q & A page.

comments “ Advertise NYU book returns at The New School.

comments “ Not sure what events in the library would be – highlighting aspects of the library’s collection?

THANKS!