Differences

This shows you the differences between two versions of the page.

--- igsn:glossary [2012/03/14 07:52]
jklump [Metadata Profile and Schema]
+++ igsn:glossary [2016/03/24 10:13] (current)
ulbricht
@@ Line 1: / Line 1: @@
-====== Glossary ======
-===== Allocating Agent =====
+:!: The documentation of the IGSN has moved to [[http://igsn.github.io/]] :!:
-An [[igsn:statutes&#definitions|Allocating Agent]] is an institution which allocates IGSN names on behalf of the IGSN registration agency of IGSN. An Allocating Agent may delegate technical functions and services to one or more data centres.
-===== Community =====
-An IGSN Community is a scientific community of practice, e.g. petrology, ocean sediments, critical zone, etc. The samples registered by a community are made accessible through a :?: common portal. The community also defines the IGSN [[igsn:glossary#igsn_syntax|Naming Convention]] and [[igsn:glossary#metadata_profile_and_schema|metadata]] application application profile.
-===== Domain =====
-Group of related topics, e.g. earth science, exogeology, biomedical research, material science, etc. Each domain will be given a separate handle prefix. This will make [[igsn:glossary#namespace|namespace]] governance more transparent and help to keep naming of entities unique within the respective namespances.
-===== IGSN Syntax =====
-The IGSN is organised by [[igsn:glossary#namespace|namespaces]] to ensure globally unique allocation of IGSNs to samples. The standard format of the IGSN is a nine character string consisting of a three character namespace identifier and a six character sample number.
-FIXME Example: PRR001407 (a sample from the US Polar Rock Repository)
-The Handle value is concatenated by the following rule:
-	prefix/<igsn>
-where prefix is 10273 and  <igsn> is the value (IGSN) assigned by an [[igsn:glossary#allocating_agent|Allocating Agent]].
-FIXME Example: 10273/PRR001407
-This identifier can be resolved to the URL of the metadata page of the sample through any handle resolver, e.g. http://hdl.handle.net
-FIXME Example: http://hdl.handle.net/10273/PRR001407
-IGSN user [[igsn:glossary#community|communities]] may adopt their own IGSN formats, if necessary.
-Example (IGSN): GeoB3375-1 (a gravity core from the core repository of MARUM, Univ. Bremen, Germany)
-Example (Handle): 10273/GeoB3375-1
-CrossRef recommended PID syntax: [[http://www.crossref.org/help/Content/02_Getting_started/Establishing_a_DOI_suffix_pattern.htm]]
-===== Metadata Profile and Schema =====
-DRAFT
-Due to the diversity of samples that IGSN tries to accommodate, including historic samples with a very limited set of available metadata, the only mandatory metadata in an [[igsn:earth_science_metadata|IGSN Metadata Profile]] are the sample name and the sample type. Nevertheless, IGSN highly recommends to include the following metadata when you register your samples:
-FIXME
-  * Latitude
-  * Longitude
-  * Elevation (or water depth)
-  * Material
-  * Classification (if applicable)
-  * Age
-  * Field Program (cruise or land-based expedition)
-  * Field Name/Sample Name
-  * Collection date
-  * Parent IGSN (if applicable)
-An IGSN [[igsn:glossary#community|Community]] can define a more detailed metadata application profile.
-===== Namespace =====
-In order to assure the uniqueness of assigned IGSN names, the space of IGSN identifiers is subdivided into namespaces. Namespaces are assigned to [[igsn:glossary#allocating_agent|Allocating Agents]] by the IGSN Registration Agency. The allocation of IGSNs within a namespace is governed by the allocation agents.
-Example: FIXME
-======  ======
-----
-[[igsn:start|Back]] to IGSN overview

DataWiki

User Tools

Site Tools

Differences

Page Tools