futurefirst / capscorrect

Scan a set number of contacts each day and correct contact names capitalisation on first and last names.

capscorrect

Scan a set number of contacts each day, correcting the capitalisation of individual contacts' first, middle and last names.

The rules for deciding whether a name needs to be corrected are based on Xavier's normalise extension. Any string that is all uppercase, all lowercase, or contains leading/trailing whitespace, will be trimmed and have the first letter in uppercase, and the rest of the string in lowercase.

Now compatible with 4.6, thanks to this PR.

Please note: As from some point in summer 2016, Future First is moving its technology platform away from CiviCRM. This means that our extensions will no longer be officially maintained on work time, and we will not be upgrading our installation beyond 4.4. However, I am happy to accept good/useful pull requests, and hope to maintain some involvement privately.
-- Dave (@davidknoll on GitHub)

capscorrect's Issues

No settings in "Scheduled Jobs"

Hi Vitor,
I've just installed the extension, but have no settings available on the "Scheduled Jobs" page. Do I have to create the job by hand? Civi doesn't seem to recognise the commands you've given in the documentation.

I'm also not sure of the best way to check whether the extension is running / changing entries. Could you advise as to the order that contacts are updated?

Thanks.

suggestion for a few functional aditions

Hello,
great extension! A few thoughts:

1. would it be possible to configure cases like "JAmes Moris" to be ignored or processed
   or to include middle name and make it configurable (in Holland this is in all small caps)
2. would it be possible to extend the functiolality to the street adress & city?

Ability to select a group?

It would be awesome to be able to select a group in the scheduled job settings (e.g. gid=123).
This would benefit performance on some sites, but also speed up correcting relevant addresses (for instance registrations of this year's events).

It would also allow for multiple jobs to be scheduled:

1. one slow background job (like now) that runs 500 contacts at a time, daily
2. one 'fast' job that only corrects a specific group and runs hourly (on sites where this is preferable)

Would be great. Love it.

1.1 reports 1.02 as an update

Hi

Many thanks for this extension. I've just installed the 1.1 release, but when I view the extension from within CiviCRM at https://www.example.org/civicrm/admin/extensions?reset=1 the extension reports that an update is available, this being the 1.02 release.

If I install the 1.02 release no update is notified.

Update for 4.7

Hi,

did you test your extension for 4.7.? I just did it on my test-system and it worked for my mistyped contacts.
What do I have to do to test it, whether it is really stable for 4.7.

Greetings
Benedikt

upgrade to 4.6?

Hi Vitor,
Thanks for the Module btw :)
Are you likely to be upgrading this module to work with 4.6?
Martin

missing valid contacts & cycling very clowly

Hi Vitor,
Using this plugin on a D6 site, it's taken over two months to check arounf 8000 contacts.
here's a screensshot of the last 2 days... this is repetitive since installation (nov 2014).

There are around 10000 contacts on the site, and around 14 contacts have been overlooked ie:

[ccjs_civicrm]> select id, first_name, last_name, is_deleted
-> from civicrm_contact
-> where contact_type = "Individual"
-> AND (last_name = BINARY LOWER(last_name) OR last_name = BINARY LOWER(last_name))
-> AND is_deleted = 0;
| 1577 | chaxxxx | weixxxxx | 0 |
| 5909 | Amxx | kexxx | 0 |
| 7306 | suxxxxx | ferxxxxxx | 0 |
| 7463 | axxxxx | mexxx | 0 |
| 7694 | agxxxx | burxxx | 0 |
...
.... more with greater cid's...

all with a lower cid than the "offset" of 8006 shown in the logs (sorry about the x's - they replace lower case letters).
These contacts are not deleted (there are around 35 missed (a few upper & 28 lower case)

You know of any reason for this not to work?
Had a dev look over it and he says yr code is good and should work, but for some reason it's falling over. You have any suggestions why this may be the case?

Thanks,
Martin