Field data validation using algorithms in QF

asked on October 13, 2014 • Show version history

Hi,

I have a client that would like to use a Modulus-11 check-digit algorithm to validate data entered into fields in Quick Fields. Here are some specifics regarding this validation procedure:

The steps for computing the SCOMIS case number check digit are:

·       From February 1977 through July 1997, the case number format was "03ccyytsssssk", where
o       03 = a constant for "superior court"
o       cc = See "Check Digit County Number" in table below
o       yy = last two digits of year filed
o       t = last digit of case type code (1 through 9 at this time)
o       sssss = sequence number within year and case type
o       k = check digit
·       Multiply the last digit of the court initials and each digit of the case number by its weight factor. The weight factors are 7,6,5,4,3,2,7,6,5,4,3,2. Therefore,the first digit is multiplied by seven, the second by six, the third digit by five, etc.

·       Sum the results of each of the 12 products.
·       Divide the sum by 11 to get the remainder.
·       Subtract the remainder from 11.
·       Drop the tens position and use only the units position for the check digit.

Snohomish County SCOMIS Case number 88-1-01234-x

Full Case Number : 0 3 3 1 8 8 1 0 1 2 3 4

Weight Factors : 7 6 5 4 3 2 7 6 5 4 3 2

-- -- -- -- -- -- -- -- -- -- -- --

·       Compute products: 0+18+15 +4+24+16+ 7+ 0 +5 +8 +9 +8
·       Sum of the products = 114.
·       Divide 114 by 11 giving 10, remainder 4.
·       Subtract 4 from 11, giving 7.
·       The check digit is 7.

This table documents the custom county number used in place of the standard county number for check digit calculations in SCOMIS. The Check Digit County Number was selected to 1) provide King County a check digit that would not match any other county, and 2) provide check digits to all other counties in the state so that no two adjacent counties shared the same check digit. This was established to minimize the chance of documents being accidently filed in the wrong county.

In the following list: SC = Standard County Number, CC = Check Digit County Number.

SC CC County Name

-- -- -----------

01 29 ADAMS

02 46 ASOTIN

03 05 BENTON

04 26 CHELAN

05 21 CLALLAM

06 06 CLARK

07 16 COLUMBIA

08 10 COWLITZ

09 28 DOUGLAS

10 35 FERRY

11 15 FRANKLIN

12 40 GARFIELD

13 14 GRANT

14 08 GRAYS HARBOR

15 03 ISLAND

16 22 JEFFERSON

17 07 KING

18 18 KITSAP

19 38 KITTITAS

20 17 KLICKITAT

21 02 LEWIS

22 27 LINCOLN

23 12 MASON

24 24 OKANOGAN

25 30 PACIFIC

26 20 PEND OREILLE

27 23 PIERCE

28 33 SAN JUAN

29 09 SKAGIT

30 47 SKAMANIA

31 31 SNOHOMISH

32 32 SPOKANE

33 19 STEVENS

34 34 THURSTON

35 45 WAHKIAKUM

36 04 WALLA WALLA

37 37 WHATCOM

38 25 WHITMAN

39 39 YAKIMA

Any input would be helpful on this. Feel free to ask any questions. I'll try to answer them as best I can, but this is quite a bit beyond my knowledge already.

0 0

SELECTED ANSWER

replied on October 15, 2014

Hey Eric,

We don't have anything built in to Quick Fields to perform actions like this. If this process is absolutely necessary, you may be able to manually perform these tasks in Quick Fields using tokens, pattern matching, and perhaps a bit of scripting. It sounds like a very complicated process, so I'd revisit the topic from a process standpoint and think about why this check digit calculation is needed to see if there are other ways to form a solution.

0 0

replied on October 16, 2014

Thanks Rob,

I did try to create this process through tokens (lots and lots of tokens......) and was able to get about halfway there. Without a token calculator activity in Quick Fields, the process had to stop at the division step. I was able to mimic the multiplication step with multi-value tokens and the "sum" token function.

I think another option would be to not allow the check-digit field to be filled by QF - and only fill the case number. From there, I think having Workflow do the calculations and fill the field on its own would avoid entry error.

Thanks again,

Eric

0 0

replied on October 16, 2014

Why not let Workflow do all the calculations, check the value and route the mismatched docs to some folder for further review/re-processing? Or is the scanner operator expected to correct data entry mistakes at scan time?

1 0

Question

Question

Field data validation using algorithms in QF

Answer

Replies

Sign in to reply to this post.