Who we are and how we got here
Defining the Who, Why, What of Each Function Area
Build networks, not silos.
Practice positive, solution-centered communication.
Learn constantly by taking strategic risks.
Invest in yourself and the profession.
Respect researchers’ privacy.
Support broad and equitable access to archival materials.
Open-sourced methodology
Iterative changes
Empowering users
Opportunity born of necessity
Let machines do the work
Changing landscape of donor interactions
Build upon existing technologies
Draw on existing standards
Value community knowledge
Acquire, manage, preserve, and facilitate access to digital records
Repository and REST API
User-centered design
Building a technical specification
Bag-It and profiles
Metadata requirements
Notifications with Activity Streams
Functional requirements from stories
Narrowing the field
Fedora just works
Test transfers
Preservation and staging storage
Building a data model
Small, iterative projects
Cross-function area project
Document and share work
Project with a concrete goal
Empowering new users and archivists
Value domain knowledge
Lightweight web application
Ref_id based location finder
Real-time ArchivesSpace API queries
Solution-centered approach
Small, iterative design
Planning for end of life
What to do with A/V?
User-demonstrated need for access
Reading room access was unwieldy
Digital and A/V in harmony
Teachable UX experiences
Casting a wide testing net
Helping guide ArcLight
Usability Testing
Documentation checks
Integrated, lightweight rails application
Support data reuse and mobility
Collaborate with Processing
Untenable tracking of digital media
Moving beyond an Access database
Identifying requirements
No existing product for needs