Releases: marklogic-community/smart-mastering-core
v1.3.1
Implemented enhancements:
- Matching needs path support #320
Closed issues:
- Missing permissions on audit records #324
- Fuzzy matching (e.g. double-metaphone) should dynamically generate dictionaries #321
- Non-deterministic conflicting update bug when saving a merged document #318
- Matching is too slow for 100K+ documents #317
- Mastered documents are missing their "Info" section #315
- Hard to figure out when options are missing #313
- resultsToJson losing match results #307
Note: 1.3.1 is our final feature release of Smart Mastering in the Smart Mastering Core repository. As of Data Hub 5.0.0, Smart Mastering is fully integrated into MarkLogic Data Hub as a built-in capability, and the recommended way to use the Smart Mastering capability is by configuring a mastering step in Data Hub. Existing users should migrate their Smart Mastering configuration to MarkLogic Data Hub. See Import Your Smart Mastering Core Projects for instructions.
v1.2.4
- Maintenance focusing on bug fixes
- Update DHF example to 4.1.1 and use gradle property to determine DHF version
See full changelog for more details.
v1.2.2
- Several bug fixes
- Performance changes for the match and merging batches of documents.
- Updated DHF example to DHF 4.1.0
See full changelog for more details.
v1.2.1
Numerous bug fixes and a few conveniences added.
Highlights from full changelog:
- basic URI collector added for convenience when working with the
sm-match-and-merge
REST endpoint. https://marklogic-community.github.io/smart-mastering-core/docs/rest/#sm-match-and-merge - max-sources merge option added to allow merge results to be filtered by the number of sources instead of the number of values (e.g., useful for carrying forward full Arrays from a single or a limited number of sources.) https://marklogic-community.github.io/smart-mastering-core/docs/merging-options/#standard-merging
- Updated DHF example to version 4.0.3 and altered README to reflect new
sm-match-and-merge
REST endpoint method of mastering. https://marklogic-community.github.io/smart-mastering-core/docs/merging-options/#standard-merging
v1.2.0
Highlights from the full changelog:
- Allow override of collection names that have semantic meaning to Smart Mastering via match and merge option files.
- Control how collections are applied to documents during various events of the merge process via 2 approaches. (https://marklogic-community.github.io/smart-mastering-core/docs/merging-options/#collections-algorithm)
- Simple collection override via merge options for controlling collections using simple option rules.
- Advanced collection override via custom function for setting collections that may require more complex logic.
- New match and merge endpoint that is compatible Data Hub Framework (DHF) harmonize flow collectors. https://marklogic-community.github.io/smart-mastering-core/docs/rest/#sm-match-and-merge
- Updated DHF example project to work with version 4. https://github.com/marklogic-community/smart-mastering-core/tree/master/examples/dhf-flow
v1.1.1
Bug fixes related to JSON handling and REST extensions. Several documentation improvements. Full Changelog
v1.1.0
Highlights from the full change log:
- Fixes related to JSON handling
- Improved documentation
- Merging control over nested properties
v1.0.0
Change Log
v1.0.0 (2018-08-13)
Implemented enhancements:
- Change sm-merge REST extension to accept more than two URIs #120
Fixed bugs:
- property-history returns empty strings for simple JSON fields #108
- sm-match only returns one result, and no matches #100
- sm-history-document returns blank activities #99
- POSTing pseudo-document to sm-match #98
- Not able to add merge configuration using Rest api in minimal-project. #82
Closed issues:
- Documentation - Wrong Namespace in Merge Options #116
- node() instead of object-node() #102
- Documentation - required roles #40
Merged pull requests:
- use camel case for JSON matching options #132 (dmcassel)
- removing unused algorithms #131 (paxtonhare)
- MDM-455 #130 (paxtonhare)
- Ensure consistent object vs array #129 (dmcassel)
- Mdm 338: document JSON options format #128 (dmcassel)
- Fix options as json #127 (dmcassel)
- fixing deadlock with notifications. #126 (paxtonhare)
- Mdm 395: adding more developer documentation #125 (dmcassel)
- updating parameter #124 (dmcassel)
- Mdm 94 #123 (paxtonhare)
- fixing mdm-332 #122 (paxtonhare)
- Mdm 466 #121 (dmcassel)
- Support more complex json #119 (ryanjdew)
- MDM-451 add telemetry #118 (paxtonhare)
- fixing json matching. newer version of marklogic no longer match json… #117 (paxtonhare)
- Mdm 395: documenting the code #115 (dmcassel)
- adding documentation about match results #114 (dmcassel)
- documenting the role requirements #113 (dmcassel)
- Mdm 339: minimal privileges for examples #112 (dmcassel)
- correcting version number #111 (dmcassel)
- fixing build: problem in normalize-value-for-tracing #110 (dmcassel)
- Handle text nodes in history:normalize-value-for-tracing #109 (patrickmcelwee)
- stating that content is expected not to be mixed #107 (dmcassel)
- tests for Ryan's PR #106 (dmcassel)
- adding information about path properties #105 (dmcassel)
- Fix XPath grouping to account for es:info under es:instance #104 (ryanjdew)
- #100 #102 fixed JSON serialization of match results #103 (dmcassel)
- Issue 98 #101 (dmcassel)
- Mdm 348 #97 (dmcassel)
- Mdm 348 #95 (dmcassel)
- mdm 391 - adding docs for custom actions #94 (paxtonhare)
- mdm 391 #93 (paxtonhare)
- updating to talk about the optional filtering query #92 (paxtonhare)
- MDM-403 #91 (paxtonhare)
- Ignoring dhf-flow gradle-local.properties #90 (rjrudin)
- Feature/minimal project #89 (rjrudin)
- changes happen on develop branch now #88 (dmcassel)
- adding a non-person test #86 (paxtonhare)
- adding profiling to the dhf-flow example #85 (paxtonhare)
- MDM-397 #84 (paxtonhare)
- fixing demos #83 (paxtonhare)
- Updates #81 (dmcassel)
- adding more comments in the code #80 (dmcassel)