Crosswalk record-to-object matchers must not override matches created manually (user linked) #5

Closed
gregjan opened this Issue Jan 31, 2011 · 1 comment

Projects

None yet

1 participant

@gregjan
Member
gregjan commented Jan 31, 2011

Just noticed that each time a crosswalk runs it will reassign any user-linked records to it's own matcher-links. This is an edge case, b/c usually a user will not see any need to reassign a crosswalk matched record. Nonetheless, the record matching action of the user must be respected until they do something to un-match the record.

Note: this would be more visually apparent if user linked and matcher linked divs had distinct decor in the tree.

@gregjan gregjan was assigned Apr 26, 2011
@gregjan
Member
gregjan commented Jun 7, 2011

The jury is out on this. I need feedback. If a user matched a crosswalked record to a div "by hand" through drag and drop. Then later the crosswalk matcher logic was improved, such that a match was made automatically in the crosswalk.. Do we want the match found by the supposedly improved crosswalk to negate the "by hand" match?

The note on the UI in the description is important. I've been thinking that description records deserve their own rows in the arrangement, under the div they describe, similar to how links now work.. This would allow clear annotation of "user created", "user linked crosswalk record" or "auto-linked crosswalk record".

@gregjan gregjan closed this Jun 20, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment