1 Topic by SteveHannah

  • SteveHannah
  • Veteran
  • Offline
  • From: Midlothian
  • Registered: 02-09-2010
  • Posts: 84

Topic: Recorder 6 Name Import Problem

I think this might have been posted before, but when importing observer names that contain hyphens, apostrophes or are two part surnames (e.g. van Gogh), Recorder starts treating these as separate people i.e. K O'Brien would flag up as K and an O'Brien as two different people.  Although we can work around this, are there any plans to patch this in the future?

-----------------------------------------------------------------------
Steve Hannah - GIS and Data Infrastructure Officer
The Wildlife Information Centre

SteveHannah's Website

2 Reply by MikeWeideli

  • MikeWeideli
  • Administrator
  • Offline
  • From: Littlefield Consultancy
  • Registered: 05-07-2006
  • Posts: 2,645

Re: Recorder 6 Name Import Problem

This should be fixed in 6.23. This is available as release candidate, but there are a few problems
which need fixing before it can be made generally available.

Mike Weideli

MikeWeideli's Website

3 Reply by AndyFoy

  • AndyFoy
  • Consultant
  • Offline
  • Registered: 09-08-2006
  • Posts: 219

Re: Recorder 6 Name Import Problem

Hi Mike

Have the apostrophe (e.g. O'Brien) and two-part (e.g. van Hogh) surname problems also been fixed in the new release?  I can only see reference to the hyphens in the release notes.

Thanks
Andy

Andy Foy
Systems Manager
Greenspace Information for Greater London (GiGL) CIC
www.gigl.org.uk

4 Reply by MikeWeideli

  • MikeWeideli
  • Administrator
  • Offline
  • From: Littlefield Consultancy
  • Registered: 05-07-2006
  • Posts: 2,645

Re: Recorder 6 Name Import Problem

Unfortunately, the full change hasn't been implemented. The full change was included in the release  candidate, but was then removed for further investigation, because there were some combinations which did not work  ( eg 'Smith-White, Dr A.', 'Dr A Fred Smith' ,  'White-Smith D'  did not parse correctly).   Having looked at the issues again my feeling is that we should  implement what we have, because this would be a big improvement and there are limits on what can be parsed.   

I suspect there will be other issues arising out of 6.23 and I am hoping to do another release in just a few weeks, which will include this fix.

Mike Weideli

MikeWeideli's Website