If you are searching for how to translate an IGSN, how to translate an IGSN ID, how to preserve physical-sample identity across languages, or how to translate sample metadata without breaking persistent links, the central rule is that the identifier is not prose. Translate the sample title, material description, collection notes and explanatory metadata; preserve the IGSN ID exactly as the authoritative record supplies it.
This matters in geoscience, archaeology, biology, materials science, environmental research, laboratories, museums, repositories, field notebooks, analytical facilities, sample catalogues and research data management. A multilingual record can read perfectly and still become scientifically wrong if a sample ID is changed, if a child sample is confused with a collection, if a feature-of-interest is mistaken for the material object taken from it, or if a translated sample name becomes detached from the physical specimen that the persistent identifier represents.
This guide explains how to translate around the IGSN ID in the current IGSN–DataCite infrastructure. DataCite describes IGSN IDs as globally unique persistent identifiers for physical or material samples, and current registration uses DataCite DOI services and metadata. The goal is to let sample language change while the physical object, collection or feature-of-interest remains traceable across repositories, analyses, publications and research projects.
1. IGSN IDs identify physical or material samples
DataCite defines the IGSN ID as a globally unique persistent identifier for physical samples, with physical sample and material sample used interchangeably in current guidance. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
2. IGSN IDs are functionally DOIs
Current IGSN registration uses DataCite DOI infrastructure, APIs and metadata, so identifier handling should follow DOI-aware workflows. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
3. Canonical long display uses the DOI URL
The recommended long form is the complete https://doi.org/ URL, which should remain unchanged across language versions. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
4. Short display forms still need IGSN context
When a shortened representation is used, the surrounding label should make clear that the string is an IGSN ID rather than an unrelated DOI or local code. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
5. The identifier is not the sample title
A material sample can have descriptive titles in several languages while one persistent ID continues to identify the same object. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
6. IGSN can identify an individual sample
A rock, tissue specimen, water sample, test coupon or other physical object can receive its own identifier. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
7. IGSN can identify a sample collection
An aggregation can be identified as a whole when the collection itself is the object of reference. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
8. IGSN can identify a feature-of-interest
The real-world feature from which a sample is taken can have an IGSN relationship distinct from the sample itself. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
9. Feature-of-interest and material sample are different
A lake, borehole, tree or transect is not the same object as the material removed from it. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
10. IGSN is not for an image of a sample
Images and digital representations are not the physical object and should use appropriate digital-object identifiers instead. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
11. IGSN is not a dataset DOI
Analytical data can have its own DOI while remaining linked to the physical sample’s IGSN. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
12. IGSN is not a publication DOI
A paper can cite multiple IGSNs while the article itself has a separate DOI. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
13. IGSN is not a local laboratory number
Local specimen or accession numbers can remain useful metadata but should not replace the globally resolvable identifier. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
14. Local sample numbers can support discovery
A repository can index local codes alongside the IGSN without treating those strings as alternate global identifiers. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
15. Sample names can be multilingual
Translated or transliterated sample names are display metadata and do not justify minting duplicate identifiers. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
16. Material terminology needs precision
Granite, tissue, sediment, ceramic, water, alloy and other material labels can affect scientific interpretation. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
17. Sample form matters
Core, thin section, powder, aliquot, fragment, solution and specimen describe physically different forms that should not be flattened. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
18. Creator metadata can reflect sample workflow
Creator information can represent collectors, curators, chief scientists or other responsible researchers depending on the registration context. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
19. Publisher metadata reflects the registering organization
Current guidance uses the entity registering the IGSN ID as the publisher for the physical-sample record. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
20. Publication year is not the age of the material
The DataCite publication year concerns availability or registration context, not geological, biological or manufacturing age. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
21. ResourceTypeGeneral is PhysicalObject
IGSN IDs registered through DataCite use PhysicalObject as the general resource type. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
22. Resource type can distinguish sample and feature
Specific type metadata should tell readers whether the record represents a material sample or a feature-of-interest. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
23. Subject metadata can describe materials
Materials and scientific classifications can be recorded as subjects or controlled terms without becoming part of the persistent identifier. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
24. Contributor roles should remain distinct
Collection, curation, analysis, storage and other roles can involve different people and organizations. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
25. Collection dates are lifecycle metadata
When a sample was collected is separate from when its identifier was registered or when data about it was published. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
26. Destruction or consumption can be lifecycle events
A physical sample can be consumed during analysis or destroyed while its identifier and metadata remain important for provenance. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
27. Parent-child sample relationships need integrity
A derivative object can come from a parent sample or collection and should remain linked correctly after translation. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
28. Collections can have individually identified children
A collection can have one IGSN while selected objects inside it receive their own IGSN IDs. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
29. Subsampling can create a distinct object
An aliquot, slice or powder produced from a parent may need a separate identifier relationship rather than silently inheriting the parent ID. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
30. Laboratory synthesis can create material samples
IGSN is not restricted to field collection; synthesized experimental material can also be persistently identified. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
31. IGSN extends beyond geoscience
Although the system originated in geosciences, current guidance supports material samples across research domains. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
32. Archaeological material fits the framework
Artifacts, fragments and sediments can be identified while domain-specific archaeology metadata remains in specialized schemas. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
33. Biological specimens fit the framework
Tissue and environmental samples can retain persistent sample identity while taxonomic information stays in separate metadata. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
34. Materials-science specimens fit the framework
Manufactured samples, alloys and test pieces can be identified independently of descriptive terminology. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
35. Environmental samples need location context
Soil, water and sediment records can include geolocation without turning coordinates into the sample identifier. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
36. Repositories can store richer disciplinary metadata
DataCite provides the PID layer while institutional or disciplinary repositories can maintain more detailed sample descriptions. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
37. Metadata crosswalks should preserve semantics
Mapping domain-specific sample fields into DataCite metadata is a semantic process, not simple word-for-word translation. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
38. IGSN can connect to ORCID
Researcher identifiers can link collectors or curators to the physical sample without becoming the sample ID. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
39. IGSN can connect to ROR
Organization identifiers can connect repositories and institutions to the sample record. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
40. IGSN can connect to RAiD
A sample can be related to the research activity in which it was collected, created or analyzed. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
41. IGSN can connect to instruments
Instrument identifiers or descriptions can be related metadata while the IGSN remains the object identity. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
42. IGSN can connect to grants
Funding context can be preserved with grant identifiers that remain separate from the sample PID. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
43. IGSN can connect to datasets and publications
Downstream outputs can cite the same sample so measurements and conclusions remain traceable to the physical object. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
44. Assigning an IGSN early reduces ambiguity
Current guidance recommends assigning identifiers as early as practical in the sample lifecycle. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
45. Field workflows can preassign identifiers
Draft or preassigned identifiers can support fieldwork where network access is limited. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
46. QR codes should carry the complete DOI URL
Current DataCite guidance recommends encoding the full DOI URL in QR codes used for IGSN IDs. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
47. Human-readable labels should accompany machine codes
A sample container should also show a readable identifier so identity is not trapped inside a QR code. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
48. Barcode technology is not the identity
Changing from QR to another carrier does not create another sample identifier. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
49. Labels and repository records must agree
Printed ID, QR payload and digital record should all resolve to the same sample. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
50. Machine translation should not process the identifier
IGSN strings and DOI URLs contain no prose and should be locked before automated language processing. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
51. Translation memory can carry the wrong sample ID
Repeated laboratory phrases can insert stale identifiers unless IGSNs are treated as variables. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
52. CSV and spreadsheet workflows can shift relationships
A correct IGSN in the wrong row is scientifically wrong even if the code itself is valid. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
53. JSON APIs should separate identifier and display fields
Changing locale should alter titles or descriptions, not the IGSN returned by the backend. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
54. OCR can corrupt container labels
When text extraction is uncertain, use the repository record or decoded QR code as the identity source. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
55. Right-to-left interfaces need identifier isolation
The DOI URL should remain in canonical order while Arabic or Hebrew prose follows the target direction. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
56. Search intent: translate an IGSN
Users normally need to know whether the identifier changes with language and how sample metadata should be translated. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
57. Search intent: translate sample metadata
Material descriptions, titles, contributor roles and notes can change language while the IGSN remains stable. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
58. Search intent: identify a sample PID
A code may be an IGSN, local accession number or ordinary DOI, so repository context should be verified before translation. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
59. Worked example: field sample
A geologist can register a collected specimen and later publish several language versions of its description under one persistent ID. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
60. Worked example: child thin section
A thin section derived from a parent rock can have its own identity relationship while preserving provenance to the original material. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
61. Worked example: archaeological assemblage
A collection can be identified as an aggregate while selected artifacts receive individual child identifiers. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
62. Worked example: synthesized material
A laboratory-made alloy can be persistently identified even though it has no natural collection site. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
63. Worked example: dataset cites the sample
An analytical dataset with a DOI can point back to the IGSN so future researchers know exactly which object was measured. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
64. Reference route: DataCite IGSN documentation
Current DataCite documentation covers IGSN registration, metadata, display forms and sample use cases. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
65. Connection to RAiD, ROR and ORCID
RAiD identifies activity, ROR identifies organizations and ORCID identifies people, while IGSN identifies the physical sample. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
66. Connection to the protected language ecosystem
Vocabulary Learning and How English Works support scientific material and relationship language while this page preserves sample identity. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
67. Connection to the master translation architecture
The master system owns broad QA and terminology governance; this specialist page remains focused on IGSN material-sample identity. Keep the IGSN or canonical DOI URL as protected reference data while translating the human-readable sample title, material, role or explanation. QA must verify both the literal string and the relationship: the identifier must still belong to the same physical sample, collection or feature. If hierarchy, material type or repository identity is uncertain, resolve the record through DataCite or the responsible sample catalogue instead of guessing from the translated wording.
68. Release checklist
Before release, preserve the IGSN exactly; use the canonical DOI URL where required; distinguish samples, collections and features-of-interest; keep local numbers separate; preserve parent-child, project and output relationships; protect identifiers from MT, OCR and spreadsheet corruption; verify QR or barcode representations; and check that every translated material description still belongs to the same physical object. Then review scientific terminology, collection notes, contributors, dates and descriptions for target-language accuracy.
69. Final rule: translate the sample description, preserve the material identity
Physical samples can outlive projects, laboratories, software systems and languages. IGSN IDs give those objects persistent identity so analyses, datasets, publications and future researchers can still refer to the same material. Translate what readers need to understand, preserve what systems need to resolve, and keep the sample’s relationships traceable throughout its lifecycle. See DataCite IGSN guidance.