Allowing for the Matching Rule to be specified per Form or even per Contact

I'm not sure how broad the need for this would be. Can you give more details on the use-case?

I realize this is super old (but still open.)

I have an application with many contacts who are not authenticated in drupal. Often using webforms for some form of communication. At the backend, the user has to lookup the contact. Since we have matching built in, we can hide the existing contact field from the user, but show it to the email recipient of the request and include additional information. Since we have the contact id, we can perform click operations right from the email (like approve for a specific event or add to group.)

Here the matching rules are very important. In some cases, matching is helpful, others very important. Adding to a group (say teachers vs. student) is important, whereas allow to go to an event is less stringent. Since there are many operations that may require matching, would be useful to add matching rule as a setting on the matched contact or for the form as a whole.

I tried to track in down in the code, but got a little lost. I can see about patch or providing something more concrete if you can point me to the contact matching code.

Not critical, but I do see more opportunities open up here.

Shawn are you interested in being a co-maintainer of this project?

I think you'll find what you're looking for in wf_crm_webform_postprocess::findDuplicateContact

Would you guys be willing to chip in a little $ to sponsor this? I would. Coleman, what's the estimate?

Adding a per-contact, option of choosing a dedupe rule (with _none_ as an option if you want to always create a new contact) would be a 3-5 hr project. Core team rates are: https://civicrm.org/work-core-team

Ok I've added the feature (took 3 hrs) and pushed it into the 4.x branch. Ought to appear in the -dev tarball shortly.
Stoob will you test it out and let me know?