U bent hier

Metadata Requirements for Evidence

TitelMetadata Requirements for Evidence
PublicatietypeWeb artikel
AuteursBearman, D., & Sochats K.
Secondaire titelThe Pittsburgh Project
UitgeverUniversity of Pittsburgh
Plaats uitgavePitsburgh
Type of MediumWebsite
Trefwoord(en)2.3 Bepalen van de grondslag en de betrouwbaarheid, 3.2 Vaststellen verantwoordelijkheden, 4.2 Bewaren context, archiefwaardig, authenticiteit, betrouwbaarheid, litterary warrant, oorkondenleer, recordness, records management

Managers in application domains from commerce to health care, and from research and development to manufacturing, are seeking to define standards for data interchange adequate for their business purposes. The literature is replete with discussions of how to enable end-to-end electronic business interaction, how to support the requirements of electronic patient records or electronic laboratory notebooks, and how to implement the documentation demanded by CALS or ISO-9000.

At the same time, managers of existing information networks and technical personnel charged with planning the National Information Infrastructure of the future, are encountering the requirements to identify, control access, manage software dependencies, represent the business meaning, and document the use of data, in these vast, distributed, heterogeneous, computing environments.Many observers feel that unless we can satisfy requirements for "integrity", "authenticity", "reliability" and "archiving" of digital information, the National and Global Information Infrastructures will never be able to support serious work.

The professions traditionally concerned with evidence and records have not ignored these emerging requirements.  At the University of Pittsburgh School of Library and Information Science, faculty and students engaged in a research project funded by the National Historical Publications and Records Commission have been examining the "Functional Requirements for Recordkeeping" as defined in a broad range of sources from law, regulation and best practices. From this "literary warrant" they have derived a specification of the attributes of "recordness" or evidentiality.


Records are at one and the same time the carriers, products and documentation, of business transactions.

De tekst staat op de site van Archives & Museum Informatics Archimuse.com .


"Functional Requirements for Evidence in Recordkeeping: The Pittsburgh Project

This site was recovered in 2002 (using the Wayback Machine) following its disappearance from the Web site of the University of Pittsburgh. Unfortunately, not all pages were retrievable."

Dat is het risico die resultaten van projecten lopen. Een project is altijd een eenmalige activiteit, er wordt een product geleverd en in de meeste gevallen blijven de resultaten verweesd achter. Vaak worden er geen (beheers)maatregelen genomen die de continuiteit van het product garanderen. 

Citation Keyref_314
Datum eerste publicatie: 
woensdag, 26 januari 2011 - 9:00am