-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Old DCI Number Conversion #4
Comments
I'll ask my judge friends to find out how to do the conversion. |
The process for generating DCI numbers is: Prepend a zero |
Wow, that's complicated. On the bright side, it looks like this should be usable to validate ALL DCI numbers - past, present, and future - regardless of length. That's handy. |
Totally! They have the most complicated check digit system I have ever seen. O_o But now can validate all DCI numbers, which is pretty sweet. :) On Sep 29, 2014, at 4:03 PM, Jordan [email protected] wrote:
|
Alrighty, just checking in on this again, since I'm nearly done with the validation methods for #5, and I want to be sure they're all working before implementing the display status and tooltips for the fields. As I understand this, the code in the pastebin does two things:
With that in mind, we could effectively break it up into those two parts - one for validation and one for check digit generation? From there, we can use part 1 to check a given number. If it's an invalid number, the process is to prepend a 0 and use part 2 to get a valid number, and that's it, regardless of length? Or do we repeat that until a 9- or 10-digit number, exactly is reached? |
@Nightfirecat after doing some research, there seem to be 3 kinds of numbers
for a 1 you do both steps |
I'm planning to take a shot at it now. |
I think I got everything except the wording for the warning message for shorter (older) dci numbers. Currently: |
I'm leaning toward wanting this to be a warning (eg. |
Current behavior is convert and warning. The issue is that they don't have a checksum, so theoretically they could have an entry error that is another valid number (someone else's) that then gets compounded by doing the conversion process on the wrong number. With a 8/10 digit number, the checksum can be validated, but with a <8 digit, there is simply no way to check. (unless we can get wizards to give us an api endpoint) |
@Nightfirecat oh, and to be clear, this is in pr #29 |
I'd like to see the DCI number validation become optional, like with a checkbox below the DCI number input textbox that reads "Validate my DCI Number", checked by default. Two reasons:
|
If I understand it correctly there are two steps performed automatically right now:
We still never know if it is a real or valid DCI number, correct? |
@tooomm basically, yes to all |
I'm okay with just validating and warning, without changing the official number in the PDF. Any objections to that? |
Seems reasonable, I can do that in a little bit. |
So you prefer to remove the If the second... it could be an expanded warning message instead an option present to everybody next to the DCI field to keep the interface clean - just a huge minority is using the old numbers I would assume: The expanded warning message as alternative was just my first idea, there are other options too, I'm sure. |
Closed via #29? Unless we want to change the behavior to "Don't change the number entered, but notify user of the expanded 10-digit number" |
It's a bit confusing when a user enters an old (short) DCI number and it gets changed with no warning. Would be better to do as @tooomm suggests, make it a button and optionally convert. |
I actually have time now, so I'll probably work on it this week. |
Older (smaller) DCI numbers will need to be converted into the new format. Currently don't know the formula to do this, though.
The text was updated successfully, but these errors were encountered: