1 / 13

Project Objectives

Project Objectives. Build an application for creating and managing archival information Target core archival functions Decrease costs and promote standardization Standards compliant Open source Customizable. Communications. Website (http://euterpe.bobst.nyu.edu/toolkit/):

ray
Télécharger la présentation

Project Objectives

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project Objectives • Build an application for creating and managing archival information • Target core archival functions • Decrease costs and promote standardization • Standards compliant • Open source • Customizable Archivists' Toolkit - All Hands Meeting 2004

  2. Communications • Website (http://euterpe.bobst.nyu.edu/toolkit/): • Communicate to all participants and to the public • Storage site for key project documents • List serves • “toolkit-project-members@forums.nyu.edu”: for communicating among project staff, administrators, and advisory board • “toolkit-repositories@forums.nyu.edu “: for communicating among 17 partner repositories • AT Project Calendar: for keeping track of project schedule and staff • Telephone conferences, IM Chats, WebCam: all means for project team and sub-team meetings. Archivists' Toolkit - All Hands Meeting 2004

  3. Archivists' Toolkit - All Hands Meeting 2004

  4. 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

  5. Associated Administrators Lorna Peterson (5C) Marie Hess (5C) Renee Fall (5C) Gai Carpenter (5C) Daria D'Arienzo (5C) Nancy Cricco (NYU) Ann Butler (NYU) Leslie Myrick (NYU) Allyson Collins (UCSD) Bryan Kehr (UCSD) Tina Nguyen (UCSD) Archivists' Toolkit - All Hands Meeting 2004

  6. 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

  7. 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

  8. 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

  9. 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

  10. 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

  11. Work Plan • Planning • Design • Development • Testing • Documentation • Launch • Ongoing Support Archivists' Toolkit - All Hands Meeting 2004

  12. Scope • Operating Environment • General Characteristics • Archival Functions • Additional Features • Out of Scope Archivists' Toolkit - All Hands Meeting 2004

  13. Project Schedule Archivists' Toolkit - All Hands Meeting 2004

More Related