Document specific available algorithms and their usage for both matching and merging about smart-mastering-core HOT 6 CLOSED

A particular gap found recently was that it was not clear how to configure merge options to pick the most recent value based on a field elsewhere in the document being merged.

That configuration (and documentation of the config) should include how to specify the timestamp-path inside the std-algorithm section of the merge configuration document. (the impact of the length weight vs timestamp weight should also be documented).

from smart-mastering-core.

➤ Kasey Alderete commented:

We will scope this story to clarifying the timestamp configuration, with inline examples, docs.

from smart-mastering-core.

➤ Kasey Alderete commented:

As part of evaluating this story:

• Review with field or customer user to see if explanation is clear on its own
• Consider replicating to other high priority (high use or high degree of confusion) areas - log new stories as part of wrap up

from smart-mastering-core.

➤ Kasey Alderete commented:

See also Andrew specific example. May be related to https://project.marklogic.com/jira/browse/MDM-530 - need higher level context for how to use an algorithm and what else is needed, steps/process for deploying.

from smart-mastering-core.

comment from Xavier regarding double-metaphone: "I think that the documentation should be a bit more detailed with more explanations to avoid digging too much into code (although understandable). The index thing setup is not mentioned anywhere in doc"

from smart-mastering-core.

Feedback from Andrew and Xavier: it would be much more helpful to have the algorithm notes in the documentation instead of in the code.

from smart-mastering-core.