This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
igsn:glossary [2012/07/09 15:49] jklump [Metadata Profile and Schema] description updated to core v1.0 |
igsn:glossary [2016/03/24 10:13] (current) ulbricht |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Glossary ====== | ||
| - | ===== Allocating Agent ===== | + | :!: The documentation |
| - | + | ||
| - | An [[igsn:statutes&# | + | |
| - | + | ||
| - | ===== 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. | + | |
| - | ===== 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: | + | |
| - | ===== IGSN Syntax ===== | + | |
| - | + | ||
| - | The IGSN is organised by [[igsn: | + | |
| - | + | ||
| - | FIXME Example: PRR001407 (a sample from the US Polar Rock Repository) | + | |
| - | + | ||
| - | The Handle value is concatenated by the following rule: | + | |
| - | + | ||
| - | prefix/< | + | |
| - | + | ||
| - | where prefix is 10273 and < | + | |
| - | + | ||
| - | FIXME Example: 10273/ | + | |
| - | + | ||
| - | This identifier can be resolved to the URL of the metadata page of the sample through any handle resolver, e.g. http:// | + | |
| - | + | ||
| - | FIXME Example: http:// | + | |
| - | + | ||
| - | IGSN user [[igsn: | + | |
| - | + | ||
| - | Example (IGSN): GeoB3375-1 (a gravity core from the core repository of MARUM, Univ. Bremen, Germany) | + | |
| - | + | ||
| - | Example (Handle): 10273/ | + | |
| - | + | ||
| - | CrossRef recommended PID syntax: [[http:// | + | |
| - | + | ||
| - | + | ||
| - | ===== Metadata Profile and Schema ===== | + | |
| - | + | ||
| - | Due to the diversity of samples that IGSN tries to accommodate, | + | |
| - | + | ||
| - | Metadata elements are: | + | |
| - | + | ||
| - | ^ Element ^ Definition | + | |
| - | | sampleNumber | The IGSN that identifies the registered object. | + | |
| - | | registrant | The allocating agent registering the object. | + | |
| - | | relatedResourceIdentifier | The identifiers of other objects (literature, | + | |
| - | | log | Date and Time relevant to events concerning the registered object and its metadata. | | + | |
| - | + | ||
| - | The XML schema can be downloaded from our code repository: (Trac) [[http:// | + | |
| - | + | ||
| - | The documentation of the metadata and schema | + | |
| - | + | ||
| - | An IGSN [[igsn:glossary# | + | |
| - | + | ||
| - | ===== 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# | + | |
| - | + | ||
| - | Example: FIXME | + | |
| - | + | ||
| - | + | ||
| - | ====== | + | |
| - | + | ||
| - | + | ||
| - | ---- | + | |
| - | + | ||
| - | + | ||
| - | [[igsn: | + | |