Skip to content

Use alternate identifiers to identify people when adding memberships to an org. #352

@NateV

Description

@NateV

I think my question/request might be related to a few others, for example:
this one.

It can happen that a person's name on the main council page is not written the same way in the lists of committee members.

The main council site might list "Bartleby Scrivener", and the council memberships list "Bartelby T. Scriverer". The json_id for the council membership ends up failing to resolve to a person because its not quite the same. (At least i think that's what's going on).

Or it might actually be a typo, "Bartelby Scrivner"

Do you recommend a way to clean names that are written in different ways, so that json-ids with very slightly different values can resolve to the right person?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions