The following is a summary of the syntax guidelines for the IGSN:
Unlike many other persistent identifiers, an IGSN is used not only used by machines but also needs to be handled by humans. The labelling of sample containers prescribes a limit to the number of characters that fit on a label. Also, IGSNs in lists and tables will often need editing by humans. Long character strings increase the risk of mistypings. To reduce the risk of mistypings, the IGSN is case insensitive and we recommend to avoid characters that can easily be confused, such as ‘1’ and ‘I’, or ‘0’ and ‘O’.
Since IGSNs are intended to be combined into a URI, in order to retain maximum compatibility with URI production rules it is suggested to limit the characters that can be used in the Code to the so-called ‘unreserved’ + ‘reserved’ set, but not allow any other or percent-encoded characters which may exist on the keyboard or other character sets (e.g. no accented characters or non-latin alphabets, no space, CR, LF characters). Using ABNF notation the syntax proposed syntax for an IGSN is:
<IGSN> = <Namespace><Code> <Namespace> = UPPER ; namespace adminstrated by the allocating agent <Code> = CHAR ; UPPER = %x41-5A (A-Z) DIGIT = %x30-39 (0-9) CHAR = UPPER and DIGIT unreserved = UPPER / DIGIT / "-" / "." reserved = ":" / "/" / "?" / "#" / "[" / "]" / "@" / "!" / "$" / "&" / "'" / "(" / ")" / "*" / "+" / "," / ";" / "=" / "_" / "~"
Characters a-z and A-Z in the IGSN string are case insensitive (e.g. ABC is identical to AbC). It is recommended to use upper case characters in all cases. If an IGSN were registered as ABC, then abc would resolve it and a later attempt to register AbC would be rejected with an error message stating that the IGSN was already in existence. Comparison of two IGSNs (to decide if they match or not) should be done by first converting all characters ‘a’ - ‘z’ in IGSN strings to upper case, followed by octet-by-octet comparison of the entire IGSN string.
Characters that may be confused with digits should be avoided (I = %x49, O = %x4F, i = %x69, o = %x6F)
The standard way to resolve IGSN is through http://igsn.org/
Example (IGSN): BGRB5054RX05201 Resulting IGSN URI: <http://igsn.org/BGRB5054RX05201>
The resolvable handle URI of an IGSN is made up of three components: a resolving service (http://dx.doi.org or http://hdl.handle.net), the IGSN Handle prefix 10273, and the IGSN, separated by a forward slash. It is concatenated by the following rule:
where <resolver>/<prefix> is http://hdl.handle.net/10273 and <igsn> is the value (IGSN) assigned by an Allocating Agent. This is the native Handle.net resolver for IGSN. The example used above would be http://hdl.handle.net/10273/BGRB5054RX05201.
A sample from the Susquehanna Shale Hills Critical Zone Observatory, registered through SESAR on behalf of the Department of Geosciences, Pennsylvania State University
Example (IGSN): SSH000SUA
A sample from the collection of Geoscience Australia.
Example (IGSN): AU1101
Resulting handle URI: http://igsn.org/AU1101
Example from the International Scientific Continental Drilling Program (ICDP), registered by MARUM on behalf of ICDP:
Example (IGSN): MBCR5034RC57001
Resulting handle URI: http://igsn.org/MBCR5034RC57001
Example from the core repository of the German Federal Geological Survey (BGR), registered by MARUM on behalf of BGR:
Example (IGSN): BGRB5054RX05201
Resulting handle URI: http://igsn.org/BGRB5054RX05201
Example from the International Scientific Continental Drilling Program (ICDP), registered by GFZ Potsdam on behalf of ICDP:
Example (IGSN): ICDP5054ESYI201
Resulting handle URI: http://igsn.org/ICDP5054ESYI201
Example of assigning an IGSN to a drill hole (sampling feature):
Example (IGSN): ICDP5054EEW1001
Resulting handle URI: http://igsn.org/ICDP5054EEW1001
Example from the collection of CSIRO at the Australian Resources Research Centre in Kensington, Western Australia:
Example (IGSN): CSRWA275
Resulting handle URI: http://igsn.org/CSRWA275
The above example is part of a sub-collection with its own IGSN:
Example (IGSN): CSRWASC00001
Resulting Handle URI: http://igsn.org/CSRWASC00001
IGSN e.V., Allocating Agents and academic publishers ask authors to tag IGSNs in their manuscripts. This will enable publishers to link the IGSN number to the respective samples sample when the paper is published online. To tag an IGSN, please use the syntax
In a journal article or manuscript a sample identified by IGSN SSH000SUA may look like this (tagged IGSN):
Tagging IGSNs in manuscripts in this way allows publishers to automatically link samples identified by IGSN to their respective descriptive pages on the web. See also http://www.geosamples.org/news/tag for more information about journals using IGSN.
Since May 2017 IGSN can be included in the asset tabs of all Copernicus earth science journals. The use of IGSN is also endorsed by the Coalition for Publishing Data in the Earth and Space Sciences.
An example of a publication using live IGSNs can be found here: