uo march2015 talk

R E P O S I T O R Y S E R V I C E S : C H A L L E N G E S A N D O P P O R T U N I T I E S

B U I L D I N G A N D S U S TA I N I N G C O M M U N I T Y E N G A G E M E N T A R O U N D

Patricia Hswe | @pmhswe

University of Oregon Libraries | 23 March 2015

Graphic created by Michael Tribone

W H AT T H E TA L K W I L L C O V E R

• Context: Laying a foundation for repository services (infrastructure)

• How we invested & continue to invest in user engagement

• “ScholarSphere the project” (development)

• “ScholarSphere the service” (production)

• Where we are now — two-and-a-half years later

B U T, R E A L LY, T H E S U B T E X T I S WAY M O R E I N T E R E S T I N G . . .

• What is “community”? What community/communities? Who?

• What is “engagement”?

• Operationalizing the above concepts

• Sustainability challenges


• What is “community”? What community/communities? Who?

• What is “engagement”?

• Operationalizing the above concepts

• Sustainability challenges

• Defining / transforming other concepts, e.g.:

• “Beta release” and evolving a service

• Service/product management

• Digital scholarship

• Collection development

• Liaison librarianship


M Y C O N T E X T, M Y R O L E S

D I G I TA L S C H O L A R S H I P -


D I G I TA L S C H O L A R S H I P -• P R O G R A M M I N G


D I G I TA L S C H O L A R S H I P -• P R O G R A M M I N G• S U P P O R T


D I G I TA L S C H O L A R S H I P -• P R O G R A M M I N G• S U P P O R T• S E R V I C E S


D I G I TA L S C H O L A R S H I P -• P R O G R A M M I N G• S U P P O R T• S E R V I C E S• C O L L A B O R AT I O N S


L AY I N G A F O U N D AT I O N F O R R E P O S I T O R Y S E R V I C E S ( I N F R A S T R U C T U R E )

C O N T E X T:

S C H O L A R S P H E R E T I M E L I N E


• 2010


• 2010

• Platform review - carried out by new hires in Libraries and ITS (assignment from Content Stewardship Council)


• 2010


• 2011


• 2010


• 2011

• Curation Architecture Prototype Services (CAPS) pilot project


• 2010


• 2011


• 2011 Open Repositories Conference led to Hydra/Fedora


• 2010


• 2011



• 2012 - year of ScholarSphere’s release


• 2010


• 2011




• Program Sigma (for “services”)


• 2010


• 2011




• Program Sigma (for “services”)

• Nine months to a production release

C O N T E N T

dm

E T D db

D P u b S

O L I V E

“Grain elevators, Caldwell, Idaho (LOC)” by Russell Lee/LOC Public Domain

https://www.flickr.com/photos/library_of_congress/2178285893/

https://www.flickr.com/photos/library_of_congress/

Got platforms - uh, silos? In 2010 we had these four.

C O N T E N T

dm

E T D db

D P u b S

O L I V E

“Grain elevators, Caldwell, Idaho (LOC)” by Russell Lee/LOC Public Domain

https://www.flickr.com/photos/library_of_congress/2178285893/

https://www.flickr.com/photos/library_of_congress/

P L AT F O R M R E V I E W

2014-04-30 17.09.53 by Nicholas Wang via Flickr CC BY-SA 2.0

At right: Excerpt of rubric used for platform review.

https://www.flickr.com/photos/cloneofsnake/14150603002


• User interviews and demos





• User interviews and demos

• Developed rubric for platform assessment




U S E R E N G A G E M E N TH O W W E I N V E S T E D I N

I N F O R M AT I O N T E C H N O L O G Y

S E R V I C E SU N I V E R S I T Y L I B R A R I E S

P R O J E C T H Y D R A

( O P E N - S O U R C E S O F T WA R E

C O M M U N I T Y )

!!!

FA C U LT Y S T U D E N T S

S TA F F

What communities?

Who?





C O M M U N I T Y )

!!!


S TA F F

What is “community”? What communities? Who?





C O M M U N I T Y )

!!!


S TA F FLibrarians & users






C O M M U N I T Y )

!!!


S TA F F Technologists & users

Librarians & users






C O M M U N I T Y )

!!!


S TA F F

Librarians & technologists

Technologists & users

Librarians & users






C O M M U N I T Y )

!!!


S TA F F



Librarians & users

Use case and user stories driven






C O M M U N I T Y )

!!!


S TA F F



Librarians & users

[To beaddressed] Use case and

user stories driven


Getting buy-in. Opposite of isolation, vacuum, going it alone.

What is “engagement”?

“ScholarSphere the Project” (development)

~ Operationalizing community engagement ~

T E A M M E M B E R S H I P A N D S P O N S O R S

• UL: Digital collections curator, metadata librarian, 20+ stakeholders

• ITS (central IT): Project manager, digital library architect, applications developer (eventually two), dev ops

• Sponsors (why is this important?)

• UL: Associate Dean, Research & Scholarly Communications

• ITS: Senior Director, then Digital Library Technologies

S TA K E H O L D E R E N G A G E M E N T A C R O S S T H E L I B R A R I E S

• Arts & Humanities

• Architecture & Landscape Architecture

• Cataloging & Metadata Services

• Digitization & Preservation

• Earth & Mineral Sciences

• Education & Behavioral Sciences

• Engineering

• Life Sciences

• Maps Library

• News & Microforms

• Physical & Mathematical Sciences

• Social Sciences

• Special Collections

O P E R AT I O N A L I Z I N G S TA K E H O L D E R E N G A G E M E N T

• Scaled out stakeholder efforts from CAPS project

• Use cases / user scenarios

User Experience by James Royal-Lawson via Flickr CC BY-SA 2.0

https://www.flickr.com/photos/beantin/12650723674/

https://www.flickr.com/photos/beantin/

O P E R AT I O N A L I Z I N G S TA K E H O L D E R E N G A G E M E N T

• Scaled out stakeholder efforts from CAPS project

• Use cases / user scenarios

• Stakeholders talked, we listened

• Developers in the room

• Regular demos of emerging tool => stakeholder feedback => iterative improvements

• Evidence, affirmation, trust User Experience by James Royal-Lawson via Flickr CC BY-SA 2.0

https://www.flickr.com/photos/beantin/12650723674/

https://www.flickr.com/photos/beantin/

E N G A G E M E N T O P E R AT I O N A L I Z E D : F O C U S G R O U P + U S A B I L I T Y T E S T I N G


• Word-of-mouth promotion



• Faculty, student, staff as test users





• Iterative improvements





• Iterative improvements

• Role of user empowerment

“ScholarSphere the Service” (production)

~ Sustaining community engagement ~

Frequent releases = keeping pulse on user needs.

R E L E A S E S C O N TA I N F I X E S A N D F E AT U R E S B A S E D O N U S E R F E E D B A C K


My files are bigger than the

maximum allowed size.




I don’t have time to deposit all my files. Can

someone else do it?





someone else do it?

I would like to be able to group my

files.





someone else do it?


files.

What if I have files in Dropbox and

Box?





someone else do it?


files.

What if I have files in Dropbox and

Box?

We’ve also done short surveys to current users.

D E D I C AT E D M A R K E T I N G

• ITS (IT Comm) offered to do a ScholarSphere campaign -

• Fall 2013 - faculty

• Spring 2014 - students

• Boost in new users, new inquiries

S C H O L A R S P H E R E U S E R S G R O U P ( S U G )


Initially to provide feedback loop for development of ScholarSphere 2.0 in 2014



• Core set of diverse users




• Participatory design





• Direct access to service development





• Direct access to service development

• Insight into user behavior, expectations, goals

S U G A N D D E S I G N P R O C E S S F O R 2 . 0

Post (re-)design

Get feedback

Post re-design Get more feedback

Tweak / (possibly) finalize

Not unlike stakeholder engagement process for 1.0

Examples of wireframes that were posted

to Yammer . . .

ScholarSphere 2.0 was released on 9/10/2014 -

2 years after beta.

W H E R E W E A R E N O WT W O - A N D - A - H A L F Y E A R S L A T E R

U S E R S E R V I C E S : B L E N D O F D I Y A N D WD IFY *

• Prioritize:

• What users want

• User experience and design

• Ease of use, ease of support

• Service request model

• Define/demo/sell the service - the value

• Outreach / Train the trainer

• High touch, “low” tech

• Digital preservationbest laundromat in seattle by gothopotam via Flickr CC BY 2.0

* “We Do It for You.”

https://www.flickr.com/photos/zagrobot/2676921966/

https://www.flickr.com/photos/zagrobot/

S O M E S C H O L A R S P H E R E S TAT S — S U C C E S S E S / O P P O R T U N I T I E S• Almost 500 new users

since March 2014

• 3/2013-3/2014: a little more than 100 new users

• Most files are open access (default) - 60%

• Private - 36%

• Penn State only - 4%

• Most frequent resource types

• Books

• Articles

• Data sets

• Most active users - collection creators

C H A L L E N G E S — W H I C H A R E A L S O O P P O R T U N I T I E S . S C A D S O F T H E M !

• Notion of an “evolving” service / experimentation

• Definition of “user”?

• Researcher workflow

• Discovery, metadata

• Promotion / marketing / communication

• Service / product management

• Collection development

• Governance/policies

• Developer resources

• Scaling / distributing - repurposing of roles?





C O M M U N I T Y )

!!!


S TA F F



Librarians & users

Use case and user stories driven






C O M M U N I T Y )

!!!


S TA F F



Librarians & users

Workforceneeds Use case and

user stories driven


Images from ScholarSphere repurposed for

homepage banner

Thank you! Keep in touch: [email protected]

Graphic created by Michael Tribone

mailto:[email protected]

uo march2015 talk

Technology

o r e i n t e r e s

r s p h e r e t i

e n g e s

c e s c o

c e s i n f r

r s h i p p r o g r

t i e sb u i

t h e ta