No Slide Title - Archivists` Toolkit

Download Report

Transcript No Slide Title - Archivists` Toolkit

Staffing Chart
Principal Investigator
Advisory Board
UCSD: Brian Schottlaender
Robin Chandler, Michael Fox, Lee Mandell, Merrilee Proffitt,
Richard V. Szary, Guenter Waibel, and Beth Yakel
Project Manager
UCSD: Brad Westbrook
Project Management Assistant
Frieda Romero
Aplication Manager &
Lead Developer
Archivist/Designers
Kelcy Shepherd, Brian Stevens
Student Programmers
Dorren Chen
Gaurav Arora
Archivists' Toolkit - All Hands
Meeting 2004
1
Collective goals
•
•
Carried out by teams – design,
documentation, testing, etc.
Individual staff members assigned to and
given team leader positions.
Archivists' Toolkit - All Hands
Meeting 2004
2
Associated
Administrators
Lorna Peterson (5C)
Marie Hess (5C)
Renee Fall (5C)
Gai Carpenter (5C)
Daria D'Arienzo (5C)
Nancy Cricco (NYU)
Ann Butler (NYU)
Archivists' Toolkit Team Chart
Leslie Myrick (NYU)
Allyson Collins
(UCSD)
Advisory Board
SPOT TEAM
Robin Chandler, Michael Fox, Lee Mandell, Merrilee Proffitt,
Richard V. Szary, Guenter Waibel, and Beth Yakel
Senior Project Oversight Team
Carol Mandel, Luc Declerck, David Ackerman, Jerome McDonough,
Brad Westbrook, Brian Schottlaender
Documentation Team
Testing Team
(Design Team & Develpment Team)
(Design Team)
Development Team
Bryan Kehr (UCSD)
Tina Nguyen (UCSD)
Design Team/
Liaison Team
Programming
Design and interface with participating repositories
Brad Westbrook (UC), Kelcy Sheperd (5C), Brian Stevens (NYU, NYC)
Participating Repositories
UC, Five Colleges, NYU, and NYC
Archivists' Toolkit - All Hands
Meeting 2004
3
Design “The Whats”
• Establish a formal liaison relationship with the partnering repositories in her or his
location
• Inform partners of project expectations
• Acquire EADs and MARC to develop the ingest function to populate the application
• Acquire information about partners’ accession, provenance registration, location
procedures and workflows
• Solicit feedback from partners regarding development of functional specifications and
application interface and keep the partners apprised of and involved in the
development of the application
• Express the functional specifications for the application, including inputs, outputs,
processes, interfaces, and supporting tools such as look-up tables and help screens
• Define the basic modules (input screens) and the processes for customizing them to
reflect alternative workflow patterns
•Documentation of functional specifications
Archivists' Toolkit - All Hands
Meeting 2004
4
Development “The Hows”
• Transforming the design and functional specifications into technical
specifications and executable program code
• Design of those portions of the relational database for storing
information needed for EAD Finding Aid and MARC record ingest
• Extend the initial functionality of the system to support creation,
editing, and deletion of information not included in the EAD and
MARC standards (such as technical metadata, item-level descriptive
metadata, as well as, accession, location, and provenance details).
• Documentation of technical specifications
Archivists' Toolkit - All Hands
Meeting 2004
5
Testing
• Perform basic verification tests of each module and application
build produced by the development team to assure the build
conforms to functional specifications, works correctly, and is labeled
and formatted correctly
• Test integration of modules to assure that the modules work
together correctly
• Conduct onsite tests of the application to determine that the
functionality of the application is satisfactory to the partner
repositories and determine the usability of the application interface,
the help screens, and the customization tools
• Test installation of the application to ensure that it can be
successfully installed in either its online or CD version
Archivists' Toolkit - All Hands
Meeting 2004
6
Documentation
• Project process - to capture the project process from
first planning to release of the application.
• Application - to identify and describe every
component of the application
• Use - to develop a user manual to be released with
the application.
• Project results- to prepare administrative reports
that will be submitted to the Principal Investigator and
then to The Andrew W. Mellon Foundation
Archivists' Toolkit - All Hands
Meeting 2004
7
Management/On-going
Support
•Ensure project teams are maintaining goals and
schedules
•Provide guidance as to the efficacy of project methods
• Oversee ongoing licensing, outreach, and
dissemination issues regarding the toolkit
Archivists' Toolkit - All Hands
Meeting 2004
8