Matching needs path support

[anthony-gray]

Matching does not support matching by path, but only element name. So, an expression like identifiers/identifierRecord[identifierTypeCode='MEDICAID_ID']/identifier is not supported. This means a data model itself needs to be changed in such cases to accommodate this shortcoming (e.g. add a uniquely named medicaidId element to every document).

[ryanjdew]

Thank you for the feedback. I will pursue adding this feature in a future release, with the understanding that this will require a path range index (http://docs.marklogic.com/guide/admin/range_index#id_40666) and will only work with exact matches (or only as flexible as collations will allow: http://docs.marklogic.com/guide/search-dev/encodings_collations#id_24886).

Are you currently using Smart Mastering as part of Data Hub 5 or as an independent library? Thanks!

[anthony-gray]

I’m using it independently. I do not intend to use DHF. In addition to path support, in general range indexes (element and path) should be supported. When dealing with 100K+ documents this makes a significant difference. However, I have filed a separate issue related to performance anyway.

Fuzzy matching is feasible for range indexes in the same way as you currently implement double-metaphone by looking up element values similar to a given value and use these values to query. I have done this already in our mastering solution, which works well and performs well.

[ryanjdew]

This will be possible in 1.3.1 with a path range index and a cts:path-reference being associated with the property.

[anthony-gray]

Nice. I will have to test this.