TOPIC: Token Database 2.0

Replies can now be made in this thread .

---

Don't panic!

In the next day or so (possibly today) As of now, the TDb will be has been updated to v2.0. The major changes include:

• More granular searching (10 options instead of just 4)
• The ability to do a text search on just the text printed on tokens
• Better rendering on mobile devices
• Faster response times
• The ability to email/post a URL with your search results
• Fresh lemony scent!

Text on Token fields are fully active as of May 28, 2016. will not be implemented for most tokens at launch. It will take a little while for them all to be converted.

Here's what you need to know:
You may not see the new site at the same time others do. Changes to web sites sometimes take a while to propagate to everywhere.

When using keywords, the default option is to look only in titles. If you want to switch to something else, check one of the boxes next to the text field. Unlike TDb 1.0, there is no specific checkbox for "Titles only".

Instead of "searching" for tokens, you filter them. Think of it this way: when you first load the site (or click the {Reset Filters} button), you will have the complete list of tokens queued up. Even though you don't see the full list, it's there. When you select a filter option, you pare down the list to display only those tokens which fit your criteria.

"We don't care what's under the hood. Why are you telling us this?"
Because it will affect how you use the site. Most notably, each time you check a box or select an item from a drop-down, the page will refresh. So unlike in TDb 1.0 where you'd make up to four selections and then click {Search}, now you can only make one selection at a time. You can make multiple selections, they just need to be made in stages. I'm sure you'll get accustomed to it quickly, but it's a very different way of using the site.

The filter process has a couple unfortunate, but hopefully livable side-effects:

• When your filtering results in only one match, you will need to click to see that token's full description.
• When viewing a specific token's page, you can only do a title search from that page. However, you can easily get back to the full filtering options by clicking the {Reset Filters} button.

If you have bookmarked the old TDb comment thread , please delete the old bookmark and use this thread for all future TDb change requests or error reporting.

---

ETA: The numbers you see in parenthesis after each item in a drop-down or checklist are the number of items that match that value. E.g., there are:

• 945 tokens usable by All
• 28 Back-slot items usable by All
• 3 Back-slot items usable by All from 2016
• 1 Back-slot item usable by All from 2016 that is Common

I never panic - I have my towel!

Thanks for the hard work towards improved progress in TDB. I look forward to using and providing constructive feedback!

Ed

The mere subject line of this topic gives chills!

If you have grunt work in the text of tokens you can outsource, (e.g. Fill this spreadsheet column with the text of the token as it appears in on the token face) I volunteer - pm me if interested.

Thanks Matthew. I think what I need now is some kind of prescription to deal with the forthcoming freak-out attacks.

I have a feature request before it has even been released.. Given the discussions around the possible changes in token backs, can we eventually get that data into the tokendb?

For example you could have a "Token Back Color" section which could be "Gold, Platinum, Onyx, Light Blue, etc", and a "Token Back Style" which could be "Generic, 2016, 2017 Special, etc". I think we'll need this if the 2017 tokens change again otherwise we'll all have trouble keeping it straight which tokens should have which colors and backs.

Kirk Bauer wrote: I have a feature request before it has even been released.. Given the discussions around the possible changes in token backs, can we eventually get that data into the tokendb?

For example you could have a "Token Back Color" section which could be "Gold, Platinum, Onyx, Light Blue, etc", and a "Token Back Style" which could be "Generic, 2016, 2017 Special, etc". I think we'll need this if the 2017 tokens change again otherwise we'll all have trouble keeping it straight which tokens should have which colors and backs.

I would add also showing the back would be a good idea. Luckily it wouldn't be that many scans just another image to associate with a record.

Ed

Kirk Bauer wrote: Given the discussions around the possible changes in token backs, can we eventually get that data into the tokendb?

When the backs are finalized, I'll consider adding that, but not until. I have too much to deal with at the moment and I'm not going to make changes based on something that's in limbo.

Yes, I did see that you said "eventually" ; - )

Thanks for your hard work. Looking forward to playing with the new TokenDB

Thank you for all the work you put into the DB.

Druegar wrote:

Kirk Bauer wrote: Given the discussions around the possible changes in token backs, can we eventually get that data into the tokendb?

When the backs are finalized, I'll consider adding that, but not until. I have too much to deal with at the moment and I'm not going to make changes based on something that's in limbo.

Yes, I did see that you said "eventually" ; - )

Of course, no rush!

Druegar wrote: The ability to do a text search on just the text printed on tokens

Nice! Definitely will be looking forward to that.

not to complain and I know it's a minor thing for most people but I really prefer an orangey scent to a lemony one.

any chance you could add that as a choice?

otherwise awesome work