CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site
This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Feature Requests and Suggestions (Moderator: Dave Greenberg) »
  • Name parsing on import
Pages: [1]

Author Topic: Name parsing on import  (Read 567 times)

JoeMurray

  • Administrator
  • Ask me questions
  • *****
  • Posts: 578
  • Karma: 24
    • JMA Consulting
  • CiviCRM version: 4.4 and 4.5 (as of Nov 2014)
  • CMS version: Drupal, WordPress, Joomla
  • MySQL version: MySQL 5.5, 5.6, MariaDB 10.0 (as of Nov 2014)
Name parsing on import
January 10, 2014, 08:21:25 am
Just want to log this idea: use http://jasonpriem.org/human-name-parse/ to parse full name fields during imports. Might be an extension or core.
Co-author of Using CiviCRM https://www.packtpub.com/using-civicrm/book

xavier

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4453
  • Karma: 161
    • Tech To The People
  • CiviCRM version: yes probably
  • CMS version: drupal
Re: Name parsing on import
January 11, 2014, 01:05:28 am
It's obviously going to fail on quite a few not so edge case (eg multiple-word first names like “Billy Joe.” that are pretty common over here).

This being said, might be better than nothing. To make it work, it's probably necessary to have a database of the most common firstnames, to decide if Murray is the first name and Joe the last or vice versa.
-Hackathon and data journalism about the European parliament 24-26 jan. Watch out the result
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Feature Requests and Suggestions (Moderator: Dave Greenberg) »
  • Name parsing on import

This forum was archived on 2017-11-26.