Powered by
JSPWiki v2.8.2
g2gp 17-01-2009
View PDF

Appendix 2: Documentation checklist #

A2.1 Introduction

As discussed throughout this Guide, in order to support later reuse it is necessary to record information during the project in addition to creating a virtual reality model.

A2.2 Core metadata for the AHDS

The metadata requested by the AHDS for digital archiving, listed below, is based on Dublin Core Metadata and is used for resource recovery through the AHDS on-line catalogues.

Resource discovery metadata is the index-level information that is used by gateways through which users seek archival material. 'Metadata', put simply, is data which describes the original information. The Arts and Humanities Data Service, along with a growing number of organisations around the world, advocates the use of the Dublin Core metadata set. This comprises a series of fifteen broad categories or elements, each of which is optional or may be repeated as many times as required. The elements may also be refined through the use of a developing set of sub-elements. The use of the Dublin Core within the Archaeology Data Service is discussed further elsewhere (Miller and Greenstein 1997; Wise and Miller 1997), and the current element definitions laid down across the Dublin Core community are available on the Internet.

Table 6: ADS Core metadata for virtual reality models
Information typeScope note
TitleThe name of the bubble world, panorama or virtual reality model.
CreatorThe name(s), address(es) and roles of the creator(s), compiler(s), funding agencies, or other bodies or people intellectually responsible for the model.
Subject.typeKeywords indexing the subject content of the model. If possible these can be drawn from existing documentation standards, e.g. for archaeology the English Heritage Thesaurus of Monument Types, the mda Archaeological Objects Thesaurus. If a local documentation standard is used a copy should be included with the dataset.
Subject.periodThe time period covered by the virtual reality model.
DescriptionA brief summary of the main aims and objectives of the project for which the model was developed and a summary description of the model itself.
PublisherList details of any organisation that has published the model including the URL of on-line resources.
DepositorThe name, address and role of the organisation or individual(s) who deposited the data related to the virtual reality model.
DateThe dates of the first and last day of the virtual reality modelling project.
TypeThe type of resource, e.g. three-dimensional model, interactive resource, collaborative virtual environment.
FormatThe data format of the resource, e.g. VRML 97.
IdentifierThe identification number/code used internally for the project.
SourceReferences to the original material from which the model was derived in whole or in part from published or unpublished sources, whether printed or digital.
LanguageAn indication of the program language(s) in which interactions take place in the virtual reality model, e.g. Javascript.
Relation.archiveReferences to the storage location of archives associated with the creation of the model. This element includes the name and address of the archive repository, a description of the archive and details of how it is identified within the repository (e.g. by file name or accession number).
Relation.Has partReferences to the component elements of the virtual reality model (e.g. image files, sound clips, video clips etc.) including details of their storage location, file names etc.
CoverageWhere the model relates to a real world location, give the current and contemporary name(s) of the country, region, county, town or village covered by the model and map coordinates (e.g. in the UK national grid).
Rights.copyrightA description of any known copyrights held in respect of the virtual reality model, its component elements or in its source materials.

A2.2 A check-list for documenting virtual reality models

This section offers a check-list of all the information recommended in this Guide indexed against the metadata requested by the AHDS. This is intended to assist project managers in compiling a summary of the project documentation that should be provided with a virtual reality archive.

Table 7: A documentation checklist

TypeFor AHDS
Project documentation
(Section 5.2)
Y
TitleY
CreatorY
Subject
- Subject discipline
- Subject type
- Subject period
Y
DescriptionY
Publisher
- Funding body
- Client
- Depositor
Y
DateY
TypeY
FormatY
IdentifierY
Source
- Primary archive
Y
LanguageY
Relation
- Archive
- Component data files
- Report
- Bibliographic references
Y
Coverage
- Country
- Contemporary or current placename
- Administrative area
- Map coordinates
Y
Rights
- Copyright
Y
Target Audience
(Section 5.3)
Y
AudienceY
MediatorY
Education StandardY
Interactivity typeY
Interactivity level
Typical Learning Time
Application development
(Section 5.4)
Y
Model typeY
Application formatY
Application specificationY
Hardware platformY
Authoring tools
3-D drawing tools
3-D scanners
Object libraries
Animation scriptsY
Sound clipsY
ImagesY
Real-world objectsY
Interpretative objectsY
Delivery platform
(Section 5.5)
Y
Operating systemY
BrowserY
Plug-in/viewerY
Scripting languageY
Hardware systemY
Network connection
Reporting project outcomes
(Section 5.6)
Y
Report title and reference number Y
Report authorY
Report holder
Report summaryY
Description of archive
(Section 5.7)
Y
List of all file namesY
Explanation of codes used in file namesY
Description of file formatsY
List of codes used in filesY
Date of last modificationY