Apparently It Does Happen

[LAblondeGPhi]

I would imagine that full name (including middle), date of birth, and school initiated would suffice. It sounds like most of our databases are complete enough for most of us to confirm membership when we need to in a matter of minutes (Miss America contestants in the Miss America thread, for example).

The big concern I see is the inclusion of resigned and terminated members - that might require a separate database for NPC or HQ officials.

I think the simplest solution would just be for each NPC to designate one HQ staff member of each of the other NPCs access to their member databases for cross-checking.

The second solution would be a running master list housed with the NPC that just includes names of those initiated (and omits any information on current standing, addresses, etc.)

[Nanners52674]

Originally Posted by LAblondeGPhi

I would imagine that full name (including middle), date of birth, and school initiated would suffice. It sounds like most of our databases are complete enough for most of us to confirm membership when we need to in a matter of minutes (Miss America contestants in the Miss America thread, for example).

The big concern I see is the inclusion of resigned and terminated members - that might require a separate database for NPC or HQ officials.

I think the simplest solution would just be for each NPC to designate one HQ staff member of each of the other NPCs access to their member databases for cross-checking.

The second solution would be a running master list housed with the NPC that just includes names of those initiated (and omits any information on current standing, addresses, etc.)

If this master list did exist would it be possible to somehow integrate it into the RFM program and checked before girls are assigned a recruitment counselor group or a similar setup?

[sigmadiva]

Originally Posted by LAblondeGPhi

I would imagine that full name (including middle), date of birth, and school initiated would suffice. It sounds like most of our databases are complete enough for most of us to confirm membership when we need to in a matter of minutes (Miss America contestants in the Miss America thread, for example).

The big concern I see is the inclusion of resigned and terminated members - that might require a separate database for NPC or HQ officials.

I think the simplest solution would just be for each NPC to designate one HQ staff member of each of the other NPCs access to their member databases for cross-checking.

The second solution would be a running master list housed with the NPC that just includes names of those initiated (and omits any information on current standing, addresses, etc.)

A lot of the NPHC orgs publicly list the names of expelled / suspended members and chapters that have had their charter revoked on the international web site.

I know for SGR, Delta and AKA the information is out there on the web.

Before the internet it was all by word of mouth.

I guess for NPC, each org could submit a list of names to be placed on the NPC web site, or, it could be a feature where you could search a name on the NPC website.

[aephi alum]

Originally Posted by LAblondeGPhi

The second solution would be a running master list housed with the NPC that just includes names of those initiated (and omits any information on current standing, addresses, etc.)

One problem with this: A lot of people have the same names. Say Jane Smith #1 is initiated into ABC (an NPC sorority) as a freshman at PrivateU, spends a year there, and then transfers to StateU where there is no chapter of ABC. And say, at the same time, Jane Smith #2 goes to PrivateU, does not go greek, and then transfers after one year to StateU. Jane Smith #2 wants to rush at StateU. Both women are named Jane Smith, they're both sophomores, and they both transferred from the same school. How does Jane Smith #2 prove she's not Jane Smith #1, an initiated ABC who is ineligible to rush and join a different NPC?

[LAblondeGPhi]

Originally Posted by aephi alum

One problem with this: A lot of people have the same names. Say Jane Smith #1 is initiated into ABC (an NPC sorority) as a freshman at PrivateU, spends a year there, and then transfers to StateU where there is no chapter of ABC. And say, at the same time, Jane Smith #2 goes to PrivateU, does not go greek, and then transfers after one year to StateU. Jane Smith #2 wants to rush at StateU. Both women are named Jane Smith, they're both sophomores, and they both transferred from the same school. How does Jane Smith #2 prove she's not Jane Smith #1, an initiated ABC who is ineligible to rush and join a different NPC?

Originally Posted by LAblondeGPhi

I would imagine that full name (including middle), date of birth, and school initiated would suffice. It sounds like most of our databases are complete enough for most of us to confirm membership when we need to in a matter of minutes (Miss America contestants in the Miss America thread, for example).

I meant that the NPC database would still include the above info. Our database includes more information than that (addresses, collegiate/alumna status, etc.) which needs regular updating and would be unnecessary for an NPC database. I assume ours also removes the names of women who have resigned their membership, and that would also be counter-productive for this project.