no image

Data Error 852: GEDCOM uncleaned Parse Lastname

Privacy Level: Public (Green)
Date: 2 Apr 2017
Location: Worldwidemap
Surnames/tags: data_doctors db_error_852
This page has been accessed 325 times.

Categories: DD Suggestions Help.

Description of Warning - 852: GEDCOM uncleaned Parse Lastname

In biography, there is a GEDCOM import warning, that last name couldn't be parsed. It looks something like this The last name Pers (Peirce) couldn't be parsed, so used UNKNOWN instead.

Content of info column: Line with the last name that wasn't used.

Possible Causes

use of special characters in last name.

Action Steps

Check if the last name was already added to the profile. If not, add it to appropriate field. And then delete this line from biography. Delete it also it there is no useful name in it.

Warning Status

For each Warning you can set status. You can set it as Corrected, Not corrected, False Warning, Proposed merge or just add a Comment.

If there are related errors for the profile, you will also see them on status page.

Full description is available on Status Help Page.

Questions and Discussions on this Warning

You can read what other people have asked here db_error_852.

You can also share your best practices, experiences, problems about this Warning by posting a questions in G2G. If you create a new G2G discussion for this Warning add tag data_doctors and db_error_852.

Technical Stuff

Bio is checked for phrase "couldn't be parsed, so used UNKNOWN instead".

This page is part of the Data Doctors Project.
Latest report: February 10th 2019 and the Spreadsheet.
Custom reports by: Suggestion lists, Unsourced lists, Unconnected lists.
See WikiTree+ for custom reports and statistics.
Data Doctors Challenge: Dates_VIII .