Principles

ISAD(G) follows 4 general principles:^[2]

• Description from the general to the specific

Multilevel description starts from a general level of description, which is usually the fonds, and proceeds to more detailed levels, such as the subfonds, the series, the file, the item, etc. This hierarchical structure must be represented and properly defined in the archival description.^[2]

• Information relevant to the level of description

Information in each level of description must be related only to the archival unit described in that level.^[2]

• Linking of descriptions

Every archival unit must be linked to its parent level within the hierarchy and its level must be made explicit.^[2]

• Non-repetition of information

To avoid repetition, general information common to a group must be declared in the highest level possible. Sublevels must, in turn, contain common information applicable to its child levels.^[2]

Elements

ISAD(G) defines 26 data elements of description, 6 of which are mandatory, divided into 7 areas:

1.Identity Statement ^[3](All elements in the Identity Statement area are mandatory.)

• Reference Codes: Elements used to unequivocally identify the unit of description: country code, repository code, specific local reference code/control number/other unique identifier.

• Title: Name for the unit of description.

• Date: Dates of record creation during the conduction of affairs or dates of document creation.

• Level of Description: Level of the unit of description within the hierarchy.

• Extent and medium of the unit of description: Physical or logical extent and medium of the unit of description.

2.Context ^[3](Of the 4 elements that make up the Context Area, only the first one is mandatory.)

• Name: Creator of the unit of description.

• Administrative / Biographical history: Biographical or Administrative details pertaining to the creators of the unit of description.

• Archival history: Relevant historical information on the unit of description.

• Immediate source of acquisition or transfer: Source of acquisition of the material.

3.Content and Structure^[3]

• Scope and content: Summary of scope and content relevant to the level of description.

• Appraisal, destruction and scheduling information: Appraisal, destruction and scheduling actions taken on or planned for the unit of description.

• Accruals: Planned additions to the unit of description.

• System of Arrangement: To provide information on the internal structure, the order and/or the system of classification of the unit of description.

4.Conditions of Access and Use^[3]

• Conditions governing access: Information on legal status that may affect access to the unit of description.

• Conditions governing reproduction: Conditions for the reproduction of the unit of description after creation.

• Language/scripts of material: Languages, scripts and symbol systems used in the unit of description.

• Physical characteristics and technical requirements: Relevant physical conditions, software and hardware requirements for the access and preservation of the unit of description.

• Finding aids: Finding aids applicable to the unit of description.

5.Allied Materials^[3]

• Existence and location of originals: Information about the existence or destruction of the original unit of description.

• Existence and location of copies: Information about the existence and availability of copies of the unit of description.

• Related units of description: Information about units of description related by provenance or other associations with the unit of description.

• Publication note: Publications that are about or are based on the use, study, or analysis of the unit of description.

6.Notes^[3]

• Note: Information that does not fit in any of the previous areas.

7.Description Control^[3]

• Archivist's Note: Information on who prepared the description and how.

• Rules or Conventions: Protocols on which the description is based.

• Date(s) of descriptions: Dates of creation and revision.

The standard provides a framework for a common approach, rather than a rigid format.^[3][4]

Implementation of ISAD(G) using XML schemas

EAD: Encoded Archival Description (EAD) uses XML schemas to encode content descriptions mapped to ISAD(G) standards as a guide to determine required data elements and hierarchical relations between said elements. These protocols are not exclusive but complimentary. ISAD(G) is not as specific as EAD with respect to finding aid data, but it offers a useful model for determining both essential elements and the amount of descriptive detail an archivist may wish to gather at each hierarchical level.^[12]

Example: Excerpt of an XML schema describing the archival unit Records of the Global Environment Facility  from the World Bank Group Archive using the ISAD(G) protocol:^[13]

<archdesc level="fonds" relatedencoding="ISAD(G)v2">
<did>
<unittitle encodinganalog="3.1.2">Records of the Global Environment Facility</unittitle>
<unitid encodinganalog="3.1.1">WB IBRD/IDA GEF</unitid>
<unitdate id="atom_503_event" encodinganalog="3.1.3">1988 - 2007</unitdate>
<physdesc encodinganalog="3.1.5"> 265.00 linear feet of textual records (approximate) </physdesc>
<repository>
<corpname>World Bank Group Archives</corpname>
</repository>
<langmaterial encodinganalog="3.4.3">
<language langcode="eng">English</language>
<language langcode="fre">French</language>
</langmaterial>
<origination encodinganalog="3.2.1">
<name id="atom_503_actor">Global Environment Facility</name>
</origination>
</did>
<bioghist id="md5-f21fc51e335ca4fbfd1d0638c5abdd59" encodinganalog="3.2.2">
<note>
<p>
The Global Environment Facility (GEF) began operations in (...)
<lb/>
<lb/>
The purpose of the GEF is  (...)
<lb/>
<lb/>
Initially, the World Bank  (...)
<lb/>
<lb/>
At the conclusion of its pilot phase  (...)
<lb/>
<lb/>
The governance structure of the  (...)
<lb/>
<lb/>
* implementing the decisions of the GEF Assembly and Council;
<lb/>
<lb/>
* coordinating the formulation and overseeing  (...)
<lb/>
<lb/>
* ensuring the implementation of  (...)
<lb/>
<lb/>
* reviewing and reporting to  (...)
<lb/>
<lb/>
Its business activities include:  (...)
<lb/>
<lb/>
As of 2012, the GEF involves  (...)
</p>
</note>
</bioghist>
<odd type="publicationStatus">
<p>Published</p>
</odd>
<scopecontent encodinganalog="3.3.1">
<p>
The fonds consists of  (...)
<lb/>
<lb/>
Records related to GEF's role  (...)
<lb/>
<lb/>
The fonds also consists of  (...)
<lb/>
<lb/>
Also included are records related to  (...)
<lb/>
<lb/>
This fonds also consists of  (...)
<lb/>
<lb/>
Records related to  (...)
<lb/>
<lb/>
Also included are the  (...)
</p>
</scopecontent>
<arrangement encodinganalog="3.3.4">
<p>
The following arrangement is provisional. Records are arranged into eight series:
<lb/>
<lb/>
* Project files
<lb/>
<lb/>
* Monitoring and evaluation records
<lb/>
<lb/>
* Policy development and business strategy records
<lb/>
<lb/>
* Focal Area program records
<lb/>
<lb/>
* Corporateaffairs, liaison, and convention records
<lb/>
<lb/>
* Meetings
<lb/>
<lb/>
* Communications and outreach
<lb/>
<lb/>
* Senior management correspondence
</p>
</arrangement>
<acqinfo encodinganalog="3.2.4">
<p>Records were transferred directly from  (...)
</acqinfo>
<accruals encodinganalog="3.3.3">
<p>Accruals are expected.</p>
</accruals>
<processinfo>
<p>
<date>22 June 2012</date>
</p>
</processinfo>
<relatedmaterial encodinganalog="3.5.3">
<p>
* See Records of the Environment Sector  (...)
<lb/>
<lb/>
<lb/>
<lb/>
* See Records of the Operations  (...)*
<lb/>
<lb/>
<lb/>
<lb/>
* See Records of Individual Staff Members  (...)*
<lb/>
<lb/>
<lb/>
<lb/>
*See records related to the  (...)
</p>
</relatedmaterial>
<accessrestrict encodinganalog="3.4.1">
<p>Records are subject to the World Bank Policy on Access to Information.</p>
</accessrestrict>
<userestrict encodinganalog="3.4.2">
<p>Records are subject to the Copyright Policy of the World Bank Group.</p>
</userestrict>
<otherfindaid encodinganalog="3.4.5">
<p>A finding aid for this fonds does not exist.</p>
</otherfindaid>
<dsc type="combined"> </dsc>
</archdesc>