Alternate last name in parentheses is parsed into nickname field

Apparently putting maiden or married names into parentheses directly following the last name is not uncommon. In 0.3.2, this is parsed into the nickname field even if it doesn't follow the first name. As an example, parsing "Baker (Johnson), Jenny" yields:
first: "Jenny"
last: "Baker"
nickname: "Johnson"

This is correctly parsed, which is nice:

>>> HumanName("MURDOCK, Orrice Abram, Jr. (Abe)")
<HumanName : [
    title: '' 
    first: 'Orrice' 
    middle: 'Abram' 
    last: 'MURDOCK' 
    suffix: 'Jr.'
    nickname: 'Abe'
]>

I am parsing names from obituaries and placing the maiden name in parenthesis at the end of the name is VERY common as are nicknames. Examples:
Barbara "Bobbie" Loy (Cox). (Cox) is the maiden name.
GLENDA FAYE NICELY (VESS) (Vess) is the maiden name.

Is there any way to distinguish the two forms of nicknames? Is a maiden name attribute an option?

Merge pull request #199 from derek73/worktree-maiden-name-bucket

Fix stale maiden-field docs in index.rst and CONTRIBUTING.md (#251)

Navigation Menu

Repository navigation

Alternate last name in parentheses is parsed into nickname field #22

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Alternate last name in parentheses is parsed into nickname field #22

Description

Activity

adamboche commented on Jul 24, 2016

martin-affinitas commented on Feb 16, 2023

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions