If you are uncertain what the policy numbers are for your libraries, contact SirsiDynix Customer Support.
| • | Our library would like to customize some of the auto–generated IDs that SirsiDynix Symphony creates. How do we do this? |
| • | What about customizing user IDs and item IDs? |
| • | How do we customize the PINs that SirsiDynix Symphony creates? |
Our library would like to customize some of the auto–generated IDs that SirsiDynix Symphony creates. How do we do this?
Each library may customize some key fields that use AUTO number generation. These fields include purchase order numbers, packing list IDs, fund IDs, PINs, and more. The custom patterns for these fields are established in the /Unicorn/Autoids directory.
To set a specific auto–generated AUTO number pattern, a file is created for each library that needs a specific pattern. Each file is named for the AUTO generation function and the number of the library in policies. Each file contains a single line for the pattern. The first character in the file is a delimiter, such as #. Then the prefix is specified, then another delimiter, then the number to be incremented, then another delimiter, then a suffix (if desired).
If you are uncertain what the policy numbers are for your libraries, contact SirsiDynix Customer Support.
For example, AUTO Order IDs Order ID pattern files are named po<n>, where <n> is the number of the library in policies. For example, an AUTO order ID pattern might be: #PO–#5000#. This would be in a file named po1 if this pattern is for library 1 in policies. When AUTO is selected when an order ID is created at library 1, the order IDs generated are PO–5001, PO–5002, PO–5003, and so on. If there is no po file for a library, AUTO generation cannot be used when creating or duplicating an order.
The following custom patterns are delivered.
|
Type of ID |
Pattern File Name |
Example Pattern |
Example of ID |
|
BISAC Purchase Order ID |
bisacpo |
##1# |
123 |
|
Booking ID |
booking1 |
#BKG1–#1000# |
BKG1–1534 |
|
CD Receipts (Accountability) |
cdreceipts |
#1# |
123 |
|
Charge Receipts (Accountability) |
chgreceipts |
##1# |
123 |
|
EDI ID |
edi_id |
##1001# |
1003 |
|
Fund ID |
fund1 |
#FUND1738211;#1# |
FUND1–192 |
|
Holdings (Serial MARC holdings) |
holdings |
##101# |
103 |
|
Invoice ID |
inv1 |
#INV–#1# |
INV–12 |
|
Item ID |
itemid1 |
##1000# |
32620000010014 |
|
Mail Service Tracking ID |
tracking1 |
#TR—#1# |
TRACKING1-35 |
|
Packing List ID |
packing1 |
#PACKING1–#1# |
PACKING1–35 |
|
Purchase Order Number |
po1 |
#PO–#101# |
PO–172 |
|
Request ID |
request1 |
#REQ–#101# |
REQ–345 |
|
Selection List ID |
sl1 |
#SL–#1# |
SL–44 |
|
Serial Control ID |
serctl1 |
#SC–#101# |
SC–357 |
|
Set ID (Circulation sets) |
groupcirc |
##SET# |
3SET |
|
User ID |
userid1 |
##1000# |
22620000010016 |
|
Vendor ID |
vendor1 |
#VENDOR1–#1# |
VENDOR1–7 |
The number 1 in pattern file name represents the library policy number.
What about customizing user IDs and item IDs?
Custom user ID and item ID patterns are only used if custom barcode validation is configured for your system. (See FAQs: Using the Barcode Validation Feature.) This allows your site to generate user or item IDs using the selected Barcode Validation policies. The pattern number (or example pattern) should be the starting number for the significant digit portion of the barcode. This number should be set so that barcodes generated will not duplicate existing barcodes in the system. For example, if the significant portion of your barcodes begins with a lower number such as 22620000000157, then the starting number in the autoid file should be high (such as ##1000#) so that the auto generated IDs do not match an existing ID.
When the system is auto-generating an ID using Barcode Validation policies and finds a duplicate ID, the system will try to generate a valid ID again before creating the item or user record with an auto-generated SirsiDynix ID.
Also, when using WorkFlows in the Offline mode, SirsiDynix auto-generated IDs cannot be validated. In order to validate a SirsiDynix auto-generated ID, the client must have access to the user or item database. Unlike other barcode formats, the routine used for SirsiDynix auto-generated IDs is not defined in a policy that can be downloaded to the Offline client.
How do we customize the PINs that SirsiDynix Symphony creates?
PIN strings can be created either according to a pattern or randomly. The PIN pattern, if one exists, is found in the /Unicorn/Autoids directory. Its name is of the form, pin<n>, where <n> is the library number in policies. The pattern consists of one or more lines, each containing one instruction for adding one or more characters to the end of the accumulating PIN as follows.
|
A<n> |
Adds <n> characters from the front of the alternate ID |
|
B<n> |
Adds <n> characters from the end of the alternate ID |
|
R<n> |
Adds <n> randomly generated digits |
|
L<string> |
Adds the contents of <string> (no whitespace) |
|
N |
Creates an empty PIN (None) |
|
U<n> |
Adds <n> characters from the front of the user ID |
|
V<n> |
Adds <n> characters from the end of the user ID |
The command character (A, B, L, N, R, U, or V) must be the first character on the line. The argument for the command may be separated by whitespace. Any additional characters on the line are ignored. The reading of the pattern will terminate when either the PIN has reached its maximum length (10 characters) or when an invalid instruction is found. If either no pattern file is found, or if an invalid instruction is found in the pattern file, the PIN will default to a randomly generated value. The returned PIN string will be null–terminated.
The maximum size of a user pin is 10 characters. You can use the pattern file to shorten the PIN size, but you cannot increase the size beyond 10 characters.
© 2006, 2014 SirsiDynix