Site Forum

NO SPACES in card numbers. Cards without numbers get NNO; not NNO1, NNO2. And a player's uniform number is not a card number.  Don't forget prefixes, suffixes, or dashes.  BEFORE uploading a checklist, visually verify card numbers. Don't trust another site's checklist. Here's the site's guidelines:

from FAQ:

How should card numbers be inputted for sets?
The card numbers listed on checklists should try to reflect the card numbers as they appear on the cards themselves, including any dashes, prefixes, or suffixes. Unnumbered cards should be entered in as "NNO".

from Level 5 Permissions:

Guidelines

• No spaces before the card number.
• No spaces within the card number.
• Cards with no number should be assigned NNO.

This conflicts itself. Some inserts have spaces in the number. Removing them would make it not match the card itself. Admin, guidance please?

I don't see a conflict. It states "including any dashes, prefixes, or suffixes". Nothing about including spaces.  Probably has something to do with the database's number reading, uploading, searching capabilites.

This I know: If an entry in the Note field has a space (e.g., "SN 800"), and you go to that set's glossary, click on the "SN 800" entry to locate those cards, it returns zero cards. Go to the checklist, and they are there. This may be the same for using the filter features for card numbers.

Thanks for the reminder C2C. We recently had a card of the day that didn't follow that guideline that I just fixed thanks to that reminder (as well as the others in that set).

Bit of a dilemma when they number a set such as 1 of 10, 2 of 10, etc. I've seen some order them as 1of10 in the database. The way I've been doing it is just 1, instead of 1 of 10.

I wondered the other day if a set pops up say with a -- as a number if that should be used or simple NNO.

The of xx should not be there.

If you find sets with -- instead of numbers or NNO, please fix to be NNO.

If you cannot fix them, that's fine, but please alert Admin.

Here's an example of a card with the space in the number. If we want to match the cards, this should be listed as HO 1, not HO1 as it currently is.

OK, I just dug a little deeper in the site, and this is my take.

What C2C quoted from were the requirements for a text checklist import. The system looks for the first space character to say "before this is number, after this is name." No where else does it say a space cannot be in the card number. (Now, I think I goofed and should not have changed the recent card of the day.)

I tested the system on a using the filters to find a card with a space in it - it worked fine - it found the card no problem.

In conclusion, if the card has "XX 88" as the card number, I think it should be in the TCDB as "XX 88" - space and all.