knobit.org

I1 (2.5 points)

edu:Question

https://knobit.org/id/task/rmd-matching/I1

Also as Turtle · JSON-LD · RDF/XML

dcterms:licensehttps://creativecommons.org/licenses/by/4.0/
owl:sameAshttps://bitbucket.org/reffa/ontology/id/task/rmd-matching/I1
rdfs:labelI1 (2.5 points) en
schema:hasPartrmd-matching I1: a shared family e-mail as a deterministic key
schema:hasPartrmd-matching I1: first-hit rule order
schema:hasPartrmd-matching I1: blocking on surname loses the married name
schema:hasPartrmd-matching I1: no false-merge rate measured
schema:hasPartrmd-matching I1: personal code required of card-system records
schema:identifierI1
schema:position3
schema:text0.5 each. (a) MR-001 e-mail exact → auto-merge, but families share an e-mail (P-05): not a deterministic key. (b) Rules applied in order with the first hit deciding: all rules scored, then banded. (c) Blocking on surname alone keeps a woman's records apart after her surname changed at marriage (P-06, P-07): extra blocking passes (personal code; date of birth + first name). (d) No false-merge or false-split rate is measured: a labelled sample, before go-live and periodically. (e) MR-002 requires the personal code of card-system records, which have none: scoped to sources that hold it. en

Used by

has questionRetail customer matching - rules that merge father and son (matching anomaly skills)
schema:isPartOfrmd-matching I1: a shared family e-mail as a deterministic key
schema:isPartOfrmd-matching I1: first-hit rule order
schema:isPartOfrmd-matching I1: blocking on surname loses the married name
schema:isPartOfrmd-matching I1: no false-merge rate measured
schema:isPartOfrmd-matching I1: personal code required of card-system records