Editing ADDML

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
{{Infobox format}} <b>NB! Under construction!</b>
+
{{Infobox format}}
ADDML (Archival Data Description Markup Language) is a format for describing technical structures in a dataset. The format was developed by the National Archives of Norway in the late 1990s. Today normally used versions are ADDML 8.2 or ADDML 8.3. The format are today in use in Norway and Sweden. It is open for everyone interested to take part in the further developement of the format and it is free of use.
+
ADDML (Archival Data Description Markup Language) is a format for describing technical structures in a dataset. The format was developed by the National Archives of Norway in the late 1990s. Todays normally used versions are ADDML 8.2 or ADDML 8.3. The format are today in use in Norway and Sweden. It is open for everyone interested to take part in the further developement of the format and it is free of use.
  
[[File:Coptr ADDML Fig1.jpg|thumb]]
+
The format is describing datasets, hence the element "dataset" is the top level. It is open to describe many datasets within one description. Next level is consisting of three elements that forms a section each. The element "references" is used to describe metadata about the dataset, both contextual and content types of metadata. The element "flatFiles" is used to describe a flat file structure of the form - File / Record / Field. The element "dataObjects" is used to describe other structures. This element is not described, but has a structure that is generic and gives the user the possibility to design a structure of need.
 
 
The format is describing datasets, hence the element "dataset" is the top level. It is open to describe many datasets within one description. Next level is consisting of three elements that forms a section each. The element "reference" is used to describe metadata about the dataset and the original system from where it is generated, both contextual and content types of metadata. The element "flatFiles" is used to describe in derail a flat file structure of the form - File / Record / Field. The element "dataObjects" is used to describe other structures. This element is not described in detail, but has a structure that is generic and gives the user the possibility to design a structure of need. The top structure would be as shown in figure 1.
 
 
 
Under the element "reference" there is two defined elements - the element "context" and the element "content". The element context is referring to the original system and metadata about this system. The element content is referring to the dataset and metadata about the dataset itself. Under both of them there is defined the element "additionalElements", with the element "additionalElement" as sublevel. There can be many additionalElement under additionalElements, and it is possible to define an additionalElements under additionalElement. This way it is possible to create a hierarchical structure for each ones need. The standard itself do not define any metadata elements. But using the generic posibillities with additionalElements and additionalElement, each user can define what kind of metadata elements they want.
 
 
 
[[File:Coptr ADDML Fig2.jpg|thumb]]
 
 
 
Under the element "flatFiles" there is a structure shown in figure 2 where it is possible to describe files, records and fields in detail. It is possible to define types of files, records and fields and connect a definition to a type at the same level. In this structure there is many elements defined on each level for the descriptive use.
 
 
 
Under the element "dataObjects" it is possible to describe structures which are not flat files. This is again based on a generic structure where the user have to define himself the actual structure.
 
 
 
In addition it is possible on spesific elements to specify a process. This will not actually be a process, but a flag indicating to an application that a certain process should be performed while reading the datafiles.
 

Please note that all contributions to COPTR are considered to be released under the Attribution-ShareAlike 3.0 Unported (see COPTR:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)

Template used on this page: