TOPIC: TDCollection - What Features Do You Want?

Been busy with other projects (such as my +3 Deathcleaver prop), but I have started on this. I registered tdcollection.net , though it is currently devoid of anything.

I've also been working on getting the entity relationship diagram together before I start hammering away at the code.

Just wanted to give everyone an update!

Nearly 2 years later and I haven't made much progress. Life got hectic for a while in there, but I'm getting back on this horse with the intention to have it ready before GenCon.

Wanted to take a quick poll on usage though. So far, I've been constructing my data structure similar to TokenDB in that each token is linked to all it's available years, rarities (if multiple), etc. So if you own a +1 Bastard Sword, you currently can't mark if you own the 2007 or 2011 version.

It occurred to me working on the ERD this morning that some may prefer to keep track of those kinds of properties separately.

So, to those stumbling back into this topic after so long, what would -you- prefer? A separate entry in your collection for each tokens year, backing, etc? Or single token entry with a note box to keep track of any extra details freely?

Separate entries could lead to a bloat in collection sizes for you long time collectors, but would be more detailed.

I will note that I'm already intending each user can have multiple collections. So I'm the current instance your default could be overall totals, and then you can make a 2011 collection to keep track of which 2011 tokens you have.

PanoramicPanda wrote: Nearly 2 years later and I haven't made much progress. Life got hectic for a while in there, but I'm getting back on this horse with the intention to have it ready before GenCon.

Wanted to take a quick poll on usage though. So far, I've been constructing my data structure similar to TokenDB in that each token is linked to all it's available years, rarities (if multiple), etc. So if you own a +1 Bastard Sword, you currently can't mark if you own the 2007 or 2011 version.

It occurred to me working on the ERD this morning that some may prefer to keep track of those kinds of properties separately.

So, to those stumbling back into this topic after so long, what would -you- prefer? A separate entry in your collection for each tokens year, backing, etc? Or single token entry with a note box to keep track of any extra details freely?

Separate entries could lead to a bloat in collection sizes for you long time collectors, but would be more detailed.

I will note that I'm already intending each user can have multiple collections. So I'm the current instance your default could be overall totals, and then you can make a 2011 collection to keep track of which 2011 tokens you have.

Maybe just give the different years and give a area for people to put custom notes for themselves on any odd tokens or cases.

That's what I'm leaning towards. So the +1 Bastard Sword lists '2007, 2011' for it's Years, and it's up to notes/different lists for those that want to keep track separately. As opposed to a 2007 entry and a 2011 entry.

This would also stop a lot of database bloat for tokens that a handful of years attached to them.

PanoramicPanda wrote: Nearly 2 years later and I haven't made much progress. Life got hectic for a while in there, but I'm getting back on this horse with the intention to have it ready before GenCon.

Wanted to take a quick poll on usage though. So far, I've been constructing my data structure similar to TokenDB in that each token is linked to all it's available years, rarities (if multiple), etc. So if you own a +1 Bastard Sword, you currently can't mark if you own the 2007 or 2011 version.

It occurred to me working on the ERD this morning that some may prefer to keep track of those kinds of properties separately.

So, to those stumbling back into this topic after so long, what would -you- prefer? A separate entry in your collection for each tokens year, backing, etc? Or single token entry with a note box to keep track of any extra details freely?

Separate entries could lead to a bloat in collection sizes for you long time collectors, but would be more detailed.

I will note that I'm already intending each user can have multiple collections. So I'm the current instance your default could be overall totals, and then you can make a 2011 collection to keep track of which 2011 tokens you have.

I'd like to be able to keep track of the different years and backing types. If someone wants a Plat of a certain year I'd like to be able to quickly see if I have it. And for the Woodies (2003-2006) there were a lot of repeat Tokens from one year to the next. If someone is looking for a Woodie they will want to know the year.

Backing type is something I haven't seen documented (perhaps I've just missed it). Can Plat and Onyx apply to any token?

PanoramicPanda wrote: Backing type is something I haven't seen documented (perhaps I've just missed it). Can Plat and Onyx apply to any token?

For most tokens you could put a drop box with options for back of Standard, platinum, Onyx
Someone with more knowledge of wood tokens would need to discuss them.
But if standard represents the way most of the token come (gold for most, blue or orange for others) it would make things simpler

As a collector, would you want by year and backing, or would those be separate entries?

I'm trying to architect the database structure in a way that makes sense for detailed collection, but is also optional details for those that only care about the token in general.

PanoramicPanda wrote: Can Plat and Onyx apply to any token?

no
Check out Appendix 2 in the PHB . It's got a Token Traits Table. (currently page 64, but that could change in a future edition, so using the ToC link is your best bet)

Rob F wrote:

PanoramicPanda wrote: Nearly 2 years later and I haven't made much progress. Life got hectic for a while in there, but I'm getting back on this horse with the intention to have it ready before GenCon.

Wanted to take a quick poll on usage though. So far, I've been constructing my data structure similar to TokenDB in that each token is linked to all it's available years, rarities (if multiple), etc. So if you own a +1 Bastard Sword, you currently can't mark if you own the 2007 or 2011 version.

It occurred to me working on the ERD this morning that some may prefer to keep track of those kinds of properties separately.

So, to those stumbling back into this topic after so long, what would -you- prefer? A separate entry in your collection for each tokens year, backing, etc? Or single token entry with a note box to keep track of any extra details freely?

Separate entries could lead to a bloat in collection sizes for you long time collectors, but would be more detailed.

I will note that I'm already intending each user can have multiple collections. So I'm the current instance your default could be overall totals, and then you can make a 2011 collection to keep track of which 2011 tokens you have.

I'd like to be able to keep track of the different years and backing types. If someone wants a Plat of a certain year I'd like to be able to quickly see if I have it. And for the Woodies (2003-2006) there were a lot of repeat Tokens from one year to the next. If someone is looking for a Woodie they will want to know the year.

My thoughts exactly. I'd primarily be using this for the woodies, and year information is key. Plus, year info for 2005 would have to break out 2005a and 2005b.

Would it have the ability to document both what you have and what you're looking for. The old database (over 10 years ago) let you list what extras you had available for trade, and what you were looking for. It also had the ability I think to cross reference lists and match what you wanted with what was available. I do understand there were a lot fewer tokens and a lot fewer collectors back then.

Mike Steele wrote: Plus, year info for 2005 would have to break out 2005a and 2005b.

I'm fetching the token data from TokenDB, so I'll have whatever years are listed in the year field on tokens there.

As for the trade/want list and finder, easy-peasy. I'm still in the air on if it should function as a 100% separate tracker, or interact with a "primary" collection to limit how many you can list for trade, etc. Since I'm allowing people to have separate collections, I'm leaning toward not cross-limiting them.

Alright, I think I have the structure to allow for three different levels of detail for collections. Here's some plain English on what each level would represent.

• Basic (Default) - I have 3 +1 Bastard Swords
• Intermediate - I have 3 +1 Bastard Swords. 1 has an Onyx Backing, 2 are Standard Backings.
• Advanced - I have 3 +1 Bastard Swords. 1 is from 2007 and has a Standard Backing. 2 are from 2011, 1 is Standard and 1 is Onyx.

Hopefully this works as a good start for both casual and serious collectors.