IGSN Landing Pages
All IGSNs must be associated with a resolvable URL pointing to a landing page that describes the sample being identified. The mandatory requirement for a URL ensures that each IGSN can be resolved end users can resolve IGSNs to a meaningful description for the end user.of the resource. Where the IGSN descriptive metadata contains sensitive or private information, the landing page may simply state that the IGSN is private or under embargo.
ARDC IGSN Portal pages can be used as the landing page URL for the IGSNs that you mint. When minting via the API, set the value of the landing page element in the descriptive metadata to
When manually minting through the IGSN Service Web Interface
, the form will automatically be populated with an ARDC IGSN Portal landing page URL for the IGSN. This may be changed to a landing page URL of your choice.
Production IGSNs can be resolved by prefixing the IGSN value with the IGSN resolver http://igsn.org/.
Resulting IGSN URI: <http://igsn.org/BGRB5054RX05201>
IGSNs may also be resolved through the Handle.net resolver. This means that resolving IGSNs is as simple as prefixing the IGSN with Simply prefix the production IGSN value with the following IGSN resolution service address http://hdl.handle.net/10273/ in a browser address bar
Note: Test IGSNs can only be resolved through the Handle.net resolver. This is due to the IGSN.org resolver only supporting production IGSNs. To resolve a test IGSN, prefix the IGSN with http://hdl.handle.net/20.500.11812/
It is important to understand that the Handle System (the technical infrastructure for IGSNs) is a distributed network system. The consequence of this is inherent latency. IGSNs have TTL (time to live) defaulted to 24 hours, so any changes will be visible to the resolution infrastructure only when the TTL expires.