Same object and registry
Compare identifier system and value together, not an isolated character string. An establishment and its legal unit need linked records.
OSINT / IDENTITY
Two similar records do not necessarily describe the same object. Matching must retain sources, dates and decision reasons, including when no merge is possible.

AI-generated illustration
First state whether the record represents a person, legal unit, establishment, brand or research organisation. A relationship between objects is not identity. A normalised name helps find candidates; it is not a merge key.
| ID | Identified object | Check |
|---|---|---|
| SIREN | Legal unit | Nine digits. Check the registry and store as text to preserve leading zeros. A trading name does not replace the identifier. |
| SIRET | Establishment | Fourteen digits; the first nine are the SIREN. Two SIRETs with the same prefix may refer to one legal unit but to two distinct establishments. |
| ORCID iD | Person in research | Retain the full URI and leading zeros. The last character can be X. An ORCID identifies a person record; it does not automatically certify every profile statement. |
| ROR ID | Research organisation | Review the candidate, location and relationships. An affiliation string may mix department, parent organisation and address; do not automatically pick the first similar name. |
Compare identifier system and value together, not an isolated character string. An establishment and its legal unit need linked records.
Retain the URL or document, observation date and known effective date for names, addresses and status. An aggregated profile does not replace the source document.
Different addresses may reflect a move; another name may be historical. Check periods before replacing an old value.
Different IDs in the same registry or incompatible places require review. Do not erase conflicts to tidy the record.
Keep original row IDs, rule, reviewer, date and a mapping table. Later corrections must allow records to be separated.
Store original labels and identifiers separately from normalised values.
Normalise spacing and case for searching. Preserve accents, alternative names and transliterations as variants; avoid dropping suffixes that distinguish objects.
Check the ID in its registry and other attributes against appropriate sources. Two portals copying one registry are not independent confirmations.
Use “documented same object”, “distinct objects”, “relationship to retain” or “undetermined”. Similarity is not certainty.
Compare row counts, broken links and lost attributes. Review rejected matches too, to find missed duplicates.
These are schematic cases, not accounts of real people or businesses.
Decision : Keep two candidates
Decisive check : Check registry, object and period; a name alone cannot decide.
Decision : Link establishments to the legal unit
Decisive check : Keep establishment records, addresses and dates. Do not merge them into one location.
Decision : Retain the history
Decisive check : Check source and effective date; distinguish a real change from a typing error.
Decision : Create a documented relationship
Decisive check : Check record granularity and institutional relationship. Affiliation is not identity.
For each decision retain: record IDs A and B; object type; registry and identifiers; raw labels; sources and dates; agreements; contradictions; reasoned decision; reviewer; revision date. A missing field means “not supplied”, not “false”.
No. Format or checksum catches some typing errors. Check the official registry record and whether it identifies the intended object.
Not automatically. Multiple organisations may share an address and one website may represent a group. Treat these fields as clues.
Retain published name, language, variants and a verified shared identifier. Similar transliterations do not prove two people are the same.
No. They may identify distinct related objects or belong to different registries. Document the relationship instead of inventing equivalence.
No. Collection, internal analysis and publication are separate decisions. Keep attributes needed for the subject and adapt disclosure.
Use reviewed cases with false matches and missed duplicates. Measure precision and recall within the test set’s stated scope; a similarity score is not a reliability rate.
DOCUMENTED REFERENCE
A direct entity-to-value link does not carry all statement context. Wikibase RDF separates subject, statement node, qualifiers and references. This matters for dated roles, measurement methods and multiple values. Prefixes express graph roles, not trust levels.
| Reference | Value or form | What it identifies |
|---|---|---|
| wd: | Entity | Entity identifier, such as Canada wd:Q16 in official examples. Translated labels do not replace identifiers for joins. |
| p: | Entity → statement | Links an entity to a statement for a property. Several statements need not be duplicates. |
| ps: | Statement → value | Links a statement to its simple main value. Full value nodes can add quantity or time components. |
| pq: | Qualifier | Statement qualifier. In the population example pq:P585 supplies point in time, not necessarily data-entry time. |
| prov:wasDerivedFrom | Statement → reference | Links a statement to a reference node. Open the source and check actual support for the value. |
| pr: | Reference property | Property inside a reference. Multiple references supporting one statement must not be counted as extra people or events. |
| wds: | Statement identifier | Statement-node identifier. Its internal format and meaning are not guaranteed; do not infer dates or business identity from the string. |
Choose entity, statement or reference as row unit before flattening. Multiple qualifiers and references can multiply rows for one statement. DISTINCT removes identical rows, not a wrong counting unit. Preserve query, execution date and identifiers.
Only with a justified selection rule. Dates may qualify measurements or historical periods; a maximum without correct statement links can combine unrelated values.
Documentation consulted on .
DOCUMENTED REFERENCE
ORCID helps distinguish namesakes, but a record combines assertions from different origins. ORCID separates who adds an item from who connects it to the person. Holder-controlled visibility also limits what a public reader can observe.
| Reference | Value or form | What it identifies |
|---|---|---|
| Source | Who added the item | Source is the person or system adding the item. An organisation source name indicates a deposit role, not intellectual authorship of all data. |
| Assertion origin | Who made the connection | Assertion origin made the connection to the holder. A researcher can initiate an import while a service technically adds the item. |
| Affiliation | Assertion + source | Read affiliation with source, organisation and available dates. Self-added and institution-added affiliations have different provenance paths. |
| PUBLIC | Everyone | Public items can be read in the public record and public API. Visibility is not independent proof of each claim. |
| LIMITED | Trusted parties | Trusted-party items are not part of the public record. Reading depends on permission; outsiders cannot infer their content. |
| PRIVATE | Only me | Private items are not publicly visible. Documentation details holder, delegate and, where applicable, depositing-integration access. |
An empty or incomplete public record does not prove no employment, funding or publications. Preserve access date and do not reconstruct biography from visible fields alone. An authenticated ORCID workflow links an account, not automatic certification of every qualification.
No. Inspect each item’s provenance and distinguish source from assertion origin. An institution-added affiliation need not validate articles separately added by the holder.
Documentation consulted on .
DEEPER READING / PRACTICE
Two lines seem to describe the same organization, but their names or addresses are different. The approximation must be based on several attributes and preserve the initial data.
Updated on .
Compare stable identifiers, territory, period, name form and other available attributes. Examine cases of homonymity and names change before a merger.
Aggressive normalization can make a significant difference disappear. A automatic approach must be able to be revised when the indicators are low or contradictory.
The approximation journal retains original lines, rule, indications, decision and reserves. The ambiguous cases remain separate as long as an additional element does not justify their meeting.
PRACTICAL CASE / WORKED EXAMPLE
The example below is pedagogical. It shows how to move from a document to a qualified proposal, preserving the context, the contradictory elements and the information that the research does not yet allow to establish.
Two organizations share an address and close names. A approach rule brings them together while their identifiers and their documented activities remain separate.
Back to the original lines, compare several attributes and examine the available evidence. Separate case of proximity from case of identity. Documentation of the fusion corrections.
The newspaper retains the revised decision and its reasons. The rule is adjusted so that the address serves as a complementary index rather than sufficient identity proof.
Keep them in a category to be examined, with the indicators for and against. This separation preserves the data and prevents unjustified fusion in the following analyses.
DETAILED WORKSHOP / APPLICATION
Select attributes, identifiers and original data. Preparing known correspondences as well as homonyms or structures that share an address.
Test the rule, examine the indications and keep the decisions. Check the false approaches and missed cases. Document the transformations of the names or codes used for the comparison.
If a fusion depends on a single low index, keep the lines separate. An uncertain category allows a review without immediately imposing a common identity.
The rule is acceptable for its scope when major errors are examined. Manual and automatic decisions remain identifiable with their motives.
Transmitting marriage journal and examples of control. A review can recover the original values and correct the analyses depending on an incorrect merger.
ANNOTATED WORKING DOCUMENT / REVIEW GRID
The journal retains original lines, transformations, rules and decisions. It distinguishes confirmed correspondence, separation and uncertain case so that the approaches can be revised.
On a small screen, scroll the grid horizontally to read all three columns.
| Observation | Supported interpretation | Next step |
|---|---|---|
| Several stable attributes agree. | The identity is supported according to the evidence and the documented context. | Keep the reasons and check the limit cases of the rule. |
| A close name and a shared address agree alone. | The approximation remains fragile in the face of homonymities and neighboring structures. | Search for identificators or maintain an uncertain category. |
| The fusion produces attributes that are incompatible in the same period. | The rule can gather separate objects. | Back to the original and correct the dependent analyses. |
The final verification must be able to cancel a merger and recover the source values. Normalizations must be kept separately so that research aid cannot be converted into evidence of identity.
REPORTING / EXAMPLE WORDING
A fusion decision must be able to be reviewed from the initial data.
Check the contradictory indications and the effects of the merger on the analyses.
The match relies on the stated clues. Keep ambiguous cases separate and retain attribute transformations together with their rules.