was.cdlib.org California Digital Library University of California Rosalie Lack
LIFE CYCLE “What aspects of the web archiving life cycle model does the tool cover?”
Scoping: expand our options Access/Use/Reuse: create researcher tools QA: develop sophisticated tools LIFE CYCLE “What aspects of the model would you like to build into the Tool?” metadata: robust cataloging tools Selection: tools to help curators locate all sites on a topic
No additional functionality LIFE CYCLE “What functionality does the tool provide that isn't reflected in the model?”
Appraisal and Selection
Scoping
Data Capture
Storage and Organization/ Preservation University of California Data Center (Oakland, CA) San Diego Super Commuting Center
Quality Assurance and Analysis
Access/Use/Reuse
Metadata/Description
DEVELOPMENT “What resources are committed to the tool's ongoing development?” Service Manager : 1 60% time: customer support, outreach, project management Tech support : 10-25% time:1 system admin support + 1 technical project manager Developers : 2 (almost) full-time
DEVELOPMENT “What are major features in the roadmap?” Updates to Curator Tools on hold at this time as we focus on infrastructure upgrades. We had a big release in 2013; see:
DEVELOPMENT “Is the code open source?” Yes and no We are happy to share, but we don’t have the resources to bundle the code for sharing
ADOPTION “What is the user base for the tool?” 33 institutions across North America Librarians and colleges, universities and organizations
ADOPTION “How environment-specific is the tool as opposed to readily reusable by other organizations?” Tools are configured for implementation at the CDL
FUNCTIONALITY “What are the tool's unique features?” XML metadata export Compare feature Branding/Identity options WAS Site Registry
FUNCTIONALITY “What are its shortcomings?” Not packaged for open source Tools to help curators find all sites on a topic Lack of an easy export of ARC files Flexible storage options
For questions or to try WAS… contact me was.cdlib.org