BUILD.ZSR

FOSTERING & SUSTAINING

SCHOLARLY DIGITAL PROJECTS

AT WAKE FOREST

Chelcie Juliet Rowell

ER&L 2015

Austin, TX

@ararebit

FRAMING

THE

PROBLEMDESIGNING INFRASTRUCTURE AMIDST UNCERTAINTY

Digital humanities

is not a service.

So how should libraries

foster & sustain

scholarly digital

projects?

THE FACULTY WEBSITE PROBLEM

WHAT DOES ‘WEBSITE’

MEAN?

Wiki or blog

Custom database

Tools for collaboration

Integration with other platforms

Some combination of all these!

WHAT SUPPORT IS

NEEDED?

Single consultation

Semester-long course

collaboration

Open-ended commitment to

implement new tool or manage

scholarly digital collection

At New York University “we find ourselves challenged to respond

effectively to what we have come to call ‘the faculty website problem’

— an evergrowing number of requests for webbased spaces and

tools to collaborate on scholarly research and share the results.”

— Jennifer Vinopal & Monica McCormick

At Wake Forest, we scrambled to provide support for

18th-Century Common, a public humanities website and

flagship project of our Humanities Institute

FRAMING

THE

SOLUTIONA PROPOSED SERVICE MODEL

THE LIBRARY IS NOT A BOOKSHELF,

BUT A SPACE FOR THE

ACTIVE CREATION OF NEW KNOWLEDGE

WHO’S BUILDING BUILD.ZSR?

N O T A N E W U N I T, B U T A G R A S S R O O T S T E A MF R O M A C R O S S O U R L I B R A R Y ’ S O R G C H A R T

COMPONENTS OF BUILD.ZSR

tiered service model

project charter

web presence at build.zsr.wfu.edu

featured projects

wanna get started? people to help

related resources on-campus

SERVICE TIERS OF BUILD.ZSR

TIER 1

Provision

TIER 3

Creation

TIER 2

Customization

PROJECT CHARTER

Title:

Project Owner:

Project team:

Summary:

Bulleted list of deliverables:

Timeline for completion:

Launch or production plan:

End of life issues:

SUNSETTING SCHOLARLY

DIGITAL PROJECTS

SUNSETTING SCHOLARLY

DIGITAL PROJECTS

QUESTIONS?

SUGGESTIONS FOR FUTURE DEVELOPMENT?

APPENDIX:

ASSESSMENT OF BUILD.ZSR

determining success criteria

evaluating client satisfaction

identifying what did & didn’t work

calculating staff hours spent on

development & support activities

estimating costs & possible efficiencies

considering next steps

REFERENCES

DH curation guide: A community resource guide to data curation in the digital humanities. Retrieved fromhttp://guide.dhcuration.org.

Munoz, T. (2012) Digital humanities in the library isn’t a service. Retrieved from http://trevormunoz.com/notebook/2012/08/19/doing-dh-in-the-library.html.

Nowviskie, B. (2011) A skunk in the library: The path to production for scholarly R&D. Retrieved fromhttp://nowviskie.org/2011/a-skunk-in-the-library.

Varner, S. (2014). Project charter. Retrieved fromhttp://stewartvarner.com/2014/05/06/project-charter.

Vinopal, J., & McCormick, M. (2013). Supporting Digital Scholarship in Research Libraries: Scalability and Sustainability. Journal of Library Administration, 53(1), 27–42. doi:10.1080/01930826.2013.756689

IMAGE CREDITS

SLIDE 5: The 18th–Century Common, A Public Humanities

Website for Enthusiasts of 18th-Century Studies.

Retrieved from www.18thcenturycommon.org.

SLIDE 7: Hackathon. SPRUCE Digital Preservation

Illustrations. Retrieved from wiki.dpconline.org.

SLIDE 8: Branding People. City Park Technologies.

Retrieved from cityparktechnologies.com.

SLIDE 12: The Wake Forest Student viewed in the

Wayback Machine. Retrieved from

https://wayback.archive-

it.org/1104/20121231023944/http://wakestudent.com.

SLIDE 13: Humanities for the Environment. Retrieved from

http://hfe.wfu.edu.