Registration codes

[aschechtman]

Two suggestions/requests:

1. Change the algorithm to eliminate O's and 0's from registration codes. Too easy to get them mixed up.

2. When generating registration codes by serial number, make it possible to specify how many codes you want and generate an exported text file with a list of 10, 50, or 100 results instead of needing to generate them one by one.

Thanks,

Andrew Schechtman, M.D.
MeisterMed

[iSilo]

In a registration code, iSilo will actually accept 0 (zero) in place of O (the letter), and vice versa.

[aschechtman]

How thoughtful!

Thanks,

A.
In a registration code, iSilo will actually accept 0 (zero) in place of O (the letter), and vice versa.

[aschechtman]

First, I've had more than a couple users get confused between the registration code for iSilo and the registration code for a specific iSilo document.

Perhaps you could make the two types of registration codes easily distinguishable - instead of both being 16 digit alphanumeric, maybe make the document registration codes only 12 digits.

Second - a luxury really but an idea I thought I'd throw out there for consideration. It would be nice if by seeing a registration code one could identify which document it was for. What if the first four digits of the registration code were the same as the first four digits of the iSiloX document ID code. For example, for a Sherlock Holmes book in iSiloX I'd enter document ID code: SHER783yt34 and then all the generated registration codes would start with SHER (ie. SHER-HJR4-YR23-I98Q). That way, if a user said they were having problems with registration code XYZ I could instantly identify if the user was getting the codes from two separate docs confused for instance.

A.