Honestly people aren't going to enter these right no matter how much we hound them, and setting loose an automatic fix script is just bound to be a disaster at some point. Wouldn't it make more sense for the scraper to simply accept both commas and pipes?
sure, it woulf be better to "educate" the users, but a small SQL should fix all errors at once. something like this should work:
// first set beginning & ending delimiters for fields with commata
UPDATE <table> SET <field>='|'||<field>||'|' WHERE <field> LIKE '%,%';
// then replace all occurences of ", " and "," with the pipe
UPDATE <table> SET <field>=(SELECT REPLACE((SELECT REPLACE(<field>,', ','|')),',','|')) WHERE <field> LIKE '%,%';
on the other hand, if you redesign the db-scheme in the next release, we could wait a little bit. But I doubt all the scrapers adopt to the new api (for example my favorite media manager Ember Media Manager isn't developed any more)