CETAF Stable Identifier Guide - Revision history

Wouter Addink: /* What data fields or elements are recommended or standardized? */

2026-05-27T09:38:34Z

What data fields or elements are recommended or standardized?

← Older revision		Revision as of 11:38, 27 May 2026
Line 113:		Line 113:

	Under modern iterations of the profile, it is highly recommended to include standard properties to express alternate persistent identifiers. Specifically:		Under modern iterations of the profile, it is highly recommended to include standard properties to express alternate persistent identifiers. Specifically:
	prov:hadDerivation or dcterms:identifier should be utilized within the RDF metadata record to explicitly declare the digital specimen DOI associated with that specific URI, allowing semantic web harvesters to bridge the gap between the LOD web and DOI registries.		* <b>prov:hadDerivation</b> or <b>dcterms:identifier</b> should be utilized within the RDF metadata record to explicitly declare the digital specimen DOI associated with that specific URI, allowing semantic web harvesters to bridge the gap between the LOD web and DOI registries.

	The {{abbr\|CSPP}} is not meant to be comprehensive, which means that Linked Open (collection) Data implementations of CETAF institutions will usually provide much richer metadata with additional RDF-elements.		The {{abbr\|CSPP}} is not meant to be comprehensive, which means that Linked Open (collection) Data implementations of CETAF institutions will usually provide much richer metadata with additional RDF-elements.

Wouter Addink: /* What data fields or elements are recommended or standardized? */

2026-05-27T09:37:19Z

What data fields or elements are recommended or standardized?

← Older revision		Revision as of 11:37, 27 May 2026
Line 110:		Line 110:
	== What data fields or elements are recommended or standardized? ==		== What data fields or elements are recommended or standardized? ==

	The [[CETAF Specimen Preview Profile (CSPP)]] is developed as a minimal set of agreed ({{abbr\|RDF}}) collection metadata elements implemented consistently across {{abbr\|CETAF}} organisations. ~~Its purpose~~ is to ~~provide a stable resource enabling preview functions in~~ specimen ~~portals~~. The {{abbr\|CSPP}} is not meant to be comprehensive, which means that Linked Open (collection) Data implementations of CETAF institutions will usually provide much richer metadata with additional RDF-elements.		The [[CETAF Specimen Preview Profile (CSPP)]] is developed as a minimal set of agreed ({{abbr\|RDF}}) collection metadata elements implemented consistently across {{abbr\|CETAF}} organisations.

			Under modern iterations of the profile, it is highly recommended to include standard properties to express alternate persistent identifiers. Specifically:
			prov:hadDerivation or dcterms:identifier should be utilized within the RDF metadata record to explicitly declare the digital specimen DOI associated with that specific URI, allowing semantic web harvesters to bridge the gap between the LOD web and DOI registries.

			The {{abbr\|CSPP}} is not meant to be comprehensive, which means that Linked Open (collection) Data implementations of CETAF institutions will usually provide much richer metadata with additional RDF-elements.

	== Further Questions ==		== Further Questions ==

Wouter Addink: /* Publishing CETAF IDs to {{abbr|GBIF}} */

2026-05-27T09:34:22Z

Publishing CETAF IDs to {{abbr|GBIF}}

← Older revision		Revision as of 11:34, 27 May 2026
Line 93:		Line 93:
	== Publishing CETAF IDs to {{abbr\|GBIF}} ==		== Publishing CETAF IDs to {{abbr\|GBIF}} ==

	If your institution is using CETAF IDs and ~~yout~~ want them (and potential Specimen RDF) to be included into the CETAF Specimen Catalogue, they need to be used as {{abbr\|GUIDs}} in the specimen data fed to GBIF. As described in [[CETAF Specimen Catalogue]], the GBIF Index is used to discover CETAF IDs.		If your institution is using CETAF IDs and digital specimen DOIs, and you want them (and potential Specimen RDF) to be included into the CETAF Specimen Catalogue and global indexes, they need to be used as authoritative{{abbr\|GUIDs}} in the specimen data fed to GBIF. As described in [[CETAF Specimen Catalogue]], the GBIF Index is used to discover CETAF IDs.
	* If ~~DarwinCore~~ is used, the ~~IDs must be mapped~~ to [http://rs.tdwg.org/dwc/terms/occurrenceID occurrence ID].
	* For {{abbr\|ABCD}}~~, the~~ concept [https://terms.tdwg.org/wiki/abcd2:UnitGUID UnitGUID] should be used.		* If Darwin Core (DwC) is used:
			** Map the CETAF URI to [http://rs.tdwg.org/dwc/terms/occurrenceID occurrence ID].
			** Map the digital specimen DOI to [http://rs.tdwg.org/dwc/terms/digitalSpecimenID digital specimen ID]
			As a TDWG-ratified term under the `MaterialEntity` class, `digitalSpecimenID` is explicitly reserved to hold the persistent, FAIR Digital Object identifier (a DataCite DOI) that references the internet-based digital surrogate of the physical specimen.

			For {{abbr\|ABCD}}:
			* The concept [https://terms.tdwg.org/wiki/abcd2:UnitGUID UnitGUID] should be used for the primary identifier (CETAF URI).
			* Use UnitGUID variations or specialized metadata elements to explicitly supply the Digital Specimen DOI.

	== How can I discover specimens with CETAF IDs and corresponding Linked Open Data ({{abbr\|LOD}})? ==		== How can I discover specimens with CETAF IDs and corresponding Linked Open Data ({{abbr\|LOD}})? ==

Wouter Addink: /* How can I implement CETAF Stable Identifiers for my collection? */

2026-05-27T09:20:38Z

How can I implement CETAF Stable Identifiers for my collection?

← Older revision		Revision as of 11:20, 27 May 2026
Line 83:		Line 83:
	* could change to telling people to cite HTTPS rather than HTTP for your specimens but it shouldn’t matter too much as these things are linked together. The recommendation would be to cite as HTTPS if you have it implemented as at some point in the future a client may refuse to trust even a redirect from an HTTP URI (which is a bit paranoid but may happen).		* could change to telling people to cite HTTPS rather than HTTP for your specimens but it shouldn’t matter too much as these things are linked together. The recommendation would be to cite as HTTPS if you have it implemented as at some point in the future a client may refuse to trust even a redirect from an HTTP URI (which is a bit paranoid but may happen).
	\|}		\|}

			=== Integrating Identifiers into Collection Management Systems ===

			<b>CRITICAL IMPLEMENTATION STEP</b>: To ensure the integrity of both CETAF URIs and digital specimen DOIs, <b>all identifiers must be stored directly within the primary Collection Management System (CMS) source systems</b> (e.g., Specify, Axiell EMu, Brahms, Jacq, etc.).

			* <b>Source System as Single Source of Truth</b>: Identifiers should never be generated ad-hoc during web publishing or aggregator exports. They must be generated or captured at the point of digitization or ingestion and written permanently into the local CMS database.
			* <b>Database Fields</b>: Ensure your CMS schema contains dedicated, indexed fields for the CETAF URI and the Digital Specimen DOI. This guarantees absolute consistency across internal curation workflows, localized public portals, and external data pipelines. For the DOI there is a dedicated DarwinCore field dwc:digitalSpecimenID

	== Publishing CETAF IDs to {{abbr\|GBIF}} ==		== Publishing CETAF IDs to {{abbr\|GBIF}} ==

Wouter Addink: /* How can I implement CETAF Stable Identifiers for my collection? */

2026-05-27T09:10:36Z

How can I implement CETAF Stable Identifiers for my collection?

← Older revision		Revision as of 11:10, 27 May 2026
Line 57:		Line 57:

	{{color\|green\|<b>✓</b>}} the machine-readable RDF metadata record of each of your collection objects encodes application specific data (e.g. is compliant to the [[CSPP\|CETAF Specimen Preview Profile—CSPP]])		{{color\|green\|<b>✓</b>}} the machine-readable RDF metadata record of each of your collection objects encodes application specific data (e.g. is compliant to the [[CSPP\|CETAF Specimen Preview Profile—CSPP]])

			{{color\|green\|<b>✓</b>}} (Recommended:) A Digital Specimen DOI is minted for the object by DiSSCo and bi-directionally linked within the RDF metadata once it exists.
	\|}		\|}

Wouter Addink: /* What can CETAF Stable Identifiers be used for? */

2026-05-27T09:06:05Z

What can CETAF Stable Identifiers be used for?

← Older revision		Revision as of 11:06, 27 May 2026
Line 28:		Line 28:
	As described above, CETAF Identifiers can first of all be used to redirect users and systems to images, websites and metadata of the physical objects they belong to.		As described above, CETAF Identifiers can first of all be used to redirect users and systems to images, websites and metadata of the physical objects they belong to.
	They can also be used to precisely reference specimens needed in scientific studies and serve as basis for data retrieval, integration and reproducibility of data experiments.		They can also be used to precisely reference specimens needed in scientific studies and serve as basis for data retrieval, integration and reproducibility of data experiments.

			When paired with Digital Specimen DOIs, they provide dual-layered tracking. The CETAF URI drives semantic web integrations and localized lookups, while the DOI ensures that when a specimen is cited in an academic journal, data citations are automatically tracked, aggregated, and credited back to the home institution via cross-repository indexing (e.g., DataCite, Crossref).

	Additionally, the stable identifiers enable new applications in the semantic web domain. An example for this is the Biology Pilot. The [https://www.bgbm.org/ Botanic Garden and Botanical Museum Berlin], [https://www.plantentuinmeise.be/en/home/ Meise Botanic Garden] and other collections annotated thousands of specimens with the [https://kiki.huh.harvard.edu/databases/botanist_index.html HUH] and [https://www.wikidata.org/wiki/Wikidata:Main_Page WikiData] IDs of their collectors. The CETAF Stable Identifiers of the annotated specimens are available on [https://www.gbif.org/ GBIF] and a server is crawling the identifiers to organize the RDF information in a Blaze Graph triple store. This graph enables us to search for specimen by their collector {{abbr\|ID}} of {{abbr\|HUH}} or WikiData, which is invariant to the different spelling variants the individual institutions may be using. The query will return all relevant specimens available in the joined set of specimens regardless of their origin institution. If the number of institutions using stable identifiers grows and the amount of machine readable annotations increases, this technology could be used to basically create a “google for specimens”.		Additionally, the stable identifiers enable new applications in the semantic web domain. An example for this is the Biology Pilot. The [https://www.bgbm.org/ Botanic Garden and Botanical Museum Berlin], [https://www.plantentuinmeise.be/en/home/ Meise Botanic Garden] and other collections annotated thousands of specimens with the [https://kiki.huh.harvard.edu/databases/botanist_index.html HUH] and [https://www.wikidata.org/wiki/Wikidata:Main_Page WikiData] IDs of their collectors. The CETAF Stable Identifiers of the annotated specimens are available on [https://www.gbif.org/ GBIF] and a server is crawling the identifiers to organize the RDF information in a Blaze Graph triple store. This graph enables us to search for specimen by their collector {{abbr\|ID}} of {{abbr\|HUH}} or WikiData, which is invariant to the different spelling variants the individual institutions may be using. The query will return all relevant specimens available in the joined set of specimens regardless of their origin institution. If the number of institutions using stable identifiers grows and the amount of machine readable annotations increases, this technology could be used to basically create a “google for specimens”.

Wouter Addink: /* How do CETAF Stable Identifier look like? */

2026-05-27T09:03:49Z

How do CETAF Stable Identifier look like?

← Older revision		Revision as of 11:03, 27 May 2026
Line 7:		Line 7:
	To align with modern global data infrastructures (such as DiSSCo and the Digital Specimen Architecture), CETAF strongly recommends provisioning for Digital Specimen DOIs. While CETAF URIs serve as the foundational, actionable Linked Open Data network entry points, Digital Specimen DOIs offer a globally recognized, persistent, and cross-disciplinary citation standard.		To align with modern global data infrastructures (such as DiSSCo and the Digital Specimen Architecture), CETAF strongly recommends provisioning for Digital Specimen DOIs. While CETAF URIs serve as the foundational, actionable Linked Open Data network entry points, Digital Specimen DOIs offer a globally recognized, persistent, and cross-disciplinary citation standard.

	== How do CETAF Stable ~~Identifier~~ look like? ==		== How do CETAF Stable Identifiers look like? ==

	[[File:Stable identifier example.png\|thumb\|Example for the syntax of a CETAF Stable Identifier.]]		[[File:Stable identifier example.png\|thumb\|Example for the syntax of a CETAF Stable Identifier.]]

Wouter Addink: /* {{abbr|CETAF}} {{abbr|ISTC}} Stable Identifier Initiative */

2026-05-27T09:00:38Z

{{abbr|CETAF}} {{abbr|ISTC}} Stable Identifier Initiative

← Older revision		Revision as of 11:00, 27 May 2026
Line 4:		Line 4:

	The Stable Identifiers of the Consortium of European Taxonomic Facilities (CETAF) are globally unique, consistent and reliable identifiers for specimens in natural history collections. These identifiers are used in the world wide web to redirect users and systems to images, websites and metadata of the physical objects and to integrate them with the semantic web.		The Stable Identifiers of the Consortium of European Taxonomic Facilities (CETAF) are globally unique, consistent and reliable identifiers for specimens in natural history collections. These identifiers are used in the world wide web to redirect users and systems to images, websites and metadata of the physical objects and to integrate them with the semantic web.

			To align with modern global data infrastructures (such as DiSSCo and the Digital Specimen Architecture), CETAF strongly recommends provisioning for Digital Specimen DOIs. While CETAF URIs serve as the foundational, actionable Linked Open Data network entry points, Digital Specimen DOIs offer a globally recognized, persistent, and cross-disciplinary citation standard.

	== How do CETAF Stable Identifier look like? ==		== How do CETAF Stable Identifier look like? ==

A.Guentsch: /* {{abbr|CETAF}} {{abbr|ISTC}} Stable Identifier Initiative */

2025-09-17T08:43:23Z

{{abbr|CETAF}} {{abbr|ISTC}} Stable Identifier Initiative

← Older revision		Revision as of 10:43, 17 September 2025
Line 3:		Line 3:
	== {{abbr\|CETAF}} {{abbr\|ISTC}} Stable Identifier Initiative ==		== {{abbr\|CETAF}} {{abbr\|ISTC}} Stable Identifier Initiative ==

	The Stable Identifiers of the Consortium of European Taxonomic Facilities (CETAF) are globally unique, consistent and reliable identifiers for specimens in natural ~~and botanical~~ collections. These identifiers are used in the world wide web to redirect users and systems to images, websites and metadata of the physical objects and to integrate them with the semantic web.		The Stable Identifiers of the Consortium of European Taxonomic Facilities (CETAF) are globally unique, consistent and reliable identifiers for specimens in natural history collections. These identifiers are used in the world wide web to redirect users and systems to images, websites and metadata of the physical objects and to integrate them with the semantic web.

	== How do CETAF Stable Identifier look like? ==		== How do CETAF Stable Identifier look like? ==

D.Fichtmüller: links to local version of BWF pages

2025-03-05T12:03:33Z

links to local version of BWF pages

← Older revision		Revision as of 14:03, 5 March 2025
Line 130:		Line 130:
	* [https://web.archive.org/web/20200318235750/https://wiki.pro-ibiosphere.eu/wiki/Workshop_Berlin_1:_How_to_improve_technical_cooperation_and_interoperability_at_the_e-infrastructure_level_Minutes Joint ISTC/pro-iBiosphere workshop Berlin, October 2013 (archived version)]		* [https://web.archive.org/web/20200318235750/https://wiki.pro-ibiosphere.eu/wiki/Workshop_Berlin_1:_How_to_improve_technical_cooperation_and_interoperability_at_the_e-infrastructure_level_Minutes Joint ISTC/pro-iBiosphere workshop Berlin, October 2013 (archived version)]
	* [[Geneva_meeting\|Geneva Meeting (October 2015)]]		* [[Geneva_meeting\|Geneva Meeting (October 2015)]]
	* [~~http://cetafdigitization.biowikifarm.net/cdig/~~ISTC_Meeting_Spring_2016_Bratislava#Minutes Joint CETAF-ISTC / CETAF-DWG meeting (May 2016) ]		* [[ISTC_Meeting_Spring_2016_Bratislava#Minutes\|Joint CETAF-ISTC / CETAF-DWG meeting (May 2016)]]
	* [~~http://cetafdigitization.biowikifarm.net/cdig/~~ISTC_Meeting_Spring_2017_Stuttgart Joint CETAF-ISTC / CETAF-DWG meeting (March 2017) ]		* [[ISTC_Meeting_Spring_2017_Stuttgart\|Joint CETAF-ISTC / CETAF-DWG meeting (March 2017)]]
	* [~~http://cetafidentifiers.biowikifarm.net/wiki/~~IDs_and_LOD_Discussion (Virtual) LOD Hackathon (October 2017)]		* [[IDs_and_LOD_Discussion\|(Virtual) LOD Hackathon (October 2017)]]
	* [~~http://cetafdigitization.biowikifarm.net/cdig/~~ISTC_DWG_Meeting_Spring_2018_Copenhagen Joint CETAF-ISTC / CETAF-DWG meeting (February 2018) ]		* [[ISTC_DWG_Meeting_Spring_2018_Copenhagen\|Joint CETAF-ISTC / CETAF-DWG meeting (February 2018)]]
	* [~~https://cetafdigitization.biowikifarm.net/cdig/~~ISTC_QoS_Workshop_Copenhagen_2018 ISTC QoS Workshop Copenhagen (June 2018)]		* [[ISTC_QoS_Workshop_Copenhagen_2018\|ISTC QoS Workshop Copenhagen (June 2018)]]
	* [~~https://cetafdigitization.biowikifarm.net/cdig/~~ISTC_DWG_Meeting_Spring_2019_Vienna Joint CETAF-ISTC / CETAF-DWG meeting (February 2019)]		* [[ISTC_DWG_Meeting_Spring_2019_Vienna\|Joint CETAF-ISTC / CETAF-DWG meeting (February 2019)]]

	[[Category: Guide for CETAF Stable Identifiers]]		[[Category: Guide for CETAF Stable Identifiers]]