Skip to content

Elimination of redundant data property values #4184

Description

@brianjlowe

Is your feature request related to a problem? Please describe.
Part of Hosting MVP Disambiguation/Deduplication Module specifications. This component allows configuration of elimination of conflicting or redundant data property values gathered from individuals determined to be sameAs one another.

Describe the solution you'd like
A preferred value for certain data properties like label, abstract, and those declared as functional in the ontology will need to be selected where different values exist among the clustered individuals. One value per language should be retained. vCard parts (name, address, etc.) will be handled the same way. Selection criteria, configurable in the admin interface per entity type and property, might include:

  • Value from list of sources in preference order. Examples:
    -- Take a foaf:Person’s rdfs:label from URI in HR data, otherwise ORCID, then DSpace).
    -- Take a bibo:Article’s c4o:hasGlobalCitationFrequency from OpenAlex, then Web of Science.
    -- Take a bibo:Journal’s rdfs:label from Web of Science, then PubMed, then ORCID.
  • Longest value (e.g. “Johnson, Dave” over “Johnson, D.”).
  • Value with mixed case preferred over uppercase-only (e.g. “Journal of Stuff” over “JOURNAL OF STUFF”).

Sensible defaults should be provided.

See also: Disambiguation/Deduplication Specifications

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status
No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions