drneau.com

[drneau]

For release 3, you'll be able to track players using:
- First Name
- Last Name
- Email Address
- Phone
- ID (you determine what ID means...just a freeform text field)
- Address

I'm looking into the ability for you to define other fields at runtime. And "looking into" usually means I'll end up challenging myself to complete it.


Players are grouped into "Player Collections". A collection is simply a grouping of players but it also ensures uniqueness within the collection. In v2, a player was unique if they had a unique name. In v3, YOU will be able to define what "unique" means to you by selecting the fields that should make up the key (choose among First Name, Last Name and ID). So, should the combo of First and Last Name be unique? Should just the ID be unique? (so that you allow multiple John Smiths?) You decide!

So, a PlayerDB is simply a "Player Collection" that's saved to its own file. In v3, a "League" will contain its own built-in collection...and the tournaments within the league will have access to it.
_________________
--
Dr. Neau (not a real doctor)
http://drneau.com
http://home.comcast.net/~jneau

[MaxPower]

So does this mean I can set up a list of expected players, and have that list available for any tournament, like a component?

Max
_________________
Oh, Yeah! Check out the all new TheMiddleClassBlog.com for all of us that aren't exactly "High Rollers"!

[drneau]

[LA_Rounder]

that last would be great. i'd love to be able to remove a permanently-disinvited player from the league rankings...

[drneau]

[drneau]

Done a little rethinking on the "unique key" thing.

Now I'm thinking you have two choices for the unique key:
- ID
- Full Name (which is firstName + " " + lastName)

Can anyone think of a reason you want something else other than one of these two?

As a reminder, "Unique Key" determines how a player is distinguished from another player. For instance, if your 'unique key" were "FullName", you couldn't have two John Smiths in your tournament. However, if your unique key were "ID", then you COULD have two John Smiths, but you couldn't have two players with the same "ID".

I'd probably end up having some global setting for a tournament that determines how a player is displayed on the console. Choices would include:
- "ID"
- "Full Name" (this is how it is done in v2)
- "Full Name (ID)"
- "First Name (ID)"
- "Full Name (ID, if there is one)" - This would probably be the new default. It would display the player's full name and also their ID in parens...but the parens and ID would only display if there were an ID.

In fact, I might just go with the last option unless someone can convince me otherwise!

Thoughts?
_________________
--
Dr. Neau (not a real doctor)
http://drneau.com
http://home.comcast.net/~jneau

[5thStreetPokerParties.com]

I am in complete agreement with your functional requirements... It fits right into what we do as we currently have each participants displayed as FIRSTNAME LASTNAME (999).

Would this mean the columns under the player area would now include ID, First Name, Last Name rather than the Full Name? Or would the column set up be dependent upon your preferences?

In order to convert all the TM information into viable data used by our database, we have to select all the rows in the player area and paste into excel. We then select the name column and run a script to remove all characters and special characters leaving just the ID number. It would be nice to have a seperate ID column in the players area.

It would also be nice to have an 'Export to Excel' option in addition to the Export to HTML option but that may be out of scope for version 3.

What's up with the new STAR WARS looking forum?
_________________
"Play Like The Pros Play"
http://www.5thStreetPokerParties.com

[drneau]

[drneau]

Okay...

I'm leaning toward having "Address1" and "Address2" so that you could use those fields however you want. You could use "Address1" as the street address and "Address2" as the city, state, zip (or whatever tickles your fancy).

But then I'm ordering off of a Swedish website today and they asked for the following:
- First name (Christian name actually...are there any Swedish Jews?)
- Last name (Family name)
- Street address
- City
- Country
- ZIP
- State (if US or Canada)

Are those pretty standard across the board? I know I've got users in UK, France, Hungary, etc...I don't want to make the player tracking unusable...
_________________
--
Dr. Neau (not a real doctor)
http://drneau.com
http://home.comcast.net/~jneau

[murv500]

I would love the ability to "create Bought-In Player" using the ID and it pull in the player first & last Name....etc.

Thanks!

-Murv
www.BigSlickAK.com

[5thStreetPokerParties.com]

Most of the web/e-commerce apps I have ever been a part of have been North Amerian driven, but adaptable to European addresses as well...

Address1
Address2
City
StateProvince
ZipPostalCode
Country
_________________
"Play Like The Pros Play"
http://www.5thStreetPokerParties.com

[drneau]

Okay. A few updates after more thinking.

A player will always be uniquely identified by the combintion of "ID", "FirstName" and "LastName". That means if you don't use ID, which is fine, then your players are really uniquely identified by the combination of their first and last names.

I may also add a "display name" attribute to a player. Options for this field would be:
- Automatic - This would just be <FirstName> + " " + <LastName>, and if the ID was present, then it would be <FirstName> + " " + <LastName> + " (" + <ID> + ")"
- ID only
- Custom - You could put whatever you want in this field, including a nickname.

You'd also have a way of setting all players' display names to Auto or IDonly at one time.
_________________
--
Dr. Neau (not a real doctor)
http://drneau.com
http://home.comcast.net/~jneau