Configure Metadata Fields
You define the metadata fields of your procedure to make them available in the Content Capture Client during document indexing and batch processing. You can configure metadata fields in a variety of ways. Metadata fields can be made mandatory, which means they must be completed to allow a document to be successfully committed. Metadata values can also be auto populated, derived from bar codes read by the recognition processor, or selected from choice lists.
Here are the tasks you do when you are configuring metadata fields:
Delete a Metadata Field
Deleting a metadata field permanently removes it from the procedures in which this field is used. If you delete a metadata field that is in use in a client profile or a batch processor, errors may occur at different stages of batch processing. Before deleting a metadata field, ensure that it is not mapped to metadata fields in a commit profile.
To delete a metadata field from a selected procedure:
Configure a Metadata Field's Input Mask
An input mask is a filter that controls what you can enter in a metadata field. For example, a mask might allow you to enter numbers but not alphabetic characters. The application doesn't accept a character that does not conform to the mask.
Table 9-1 Alphanumeric Input Mask Characters
Mask Character | Description |
---|---|
# |
Requires a number to be entered. |
' (single quote) |
Escape character to skip any of the special formatting characters. |
U |
Accepts any letter and converts it to uppercase. |
L |
Accepts any letter and converts it to lowercase. |
A |
Accepts any letter or number. |
? |
Accepts any letter. |
* |
Accepts any character. |
H |
Accepts any hexadecimal character (0-9, a-f, or A-F). |
Table 9-2 Alphanumeric Input Mask Examples
Input Mask | Description | Example Format |
---|---|---|
###-##-#### |
Social Security Number |
123-45-6789 |
UU |
State |
AZ |
Table 9-3 Numeric and Float Input Mask Characters
Mask Character | Description |
---|---|
0 |
Requires a digit to be entered. |
# |
Requires a digit to be entered. If you enter zero as a value, it is considered absent. For example, 12.0 is considered 12. But if you enter 12.5, it is considered 12.5. |
. |
Include as a decimal separator or monetary decimal separator. |
- |
Include as a minus sign. |
, |
Include as a grouping separator. |
; |
Include to separate positive and negative subpatterns. |
Note:
A DecimalFormat
pattern contains a positive and negative
subpattern; for example, "#,##0.00;(#,##0.00)"
. Each subpattern
has a prefix, numeric part, and suffix. The negative subpattern is optional; if
absent, then the positive subpattern prefixed with the localized minus sign
('-'
in most locales) is used as the negative subpattern.
That is, "0.00"
alone is equivalent to
"0.00;-0.00"
. If there is an explicit negative subpattern,
it serves only to specify the negative prefix and suffix; the number of digits,
minimal digits, and other characteristics are all the same as the positive
pattern. This means that "#,##0.0#;(#)"
produces precisely the
same behavior as "#,##0.0#;(#,##0.0#)"
.
To allow the user to enter decimal values, you must create a format that forces at
least one decimal (#.0#
). In the client, to change a number's
sign, enter the number first, then press the + or the - key.
Table 9-4 Numeric and Float Input Mask Examples
Input Mask | Description | Example Format |
---|---|---|
#,###.0## |
Decimal Value |
1,234.567 |
#,##0.00 |
Currency |
2,500.00 |
Configure a Metadata Field's Display Format
When you define the display format in a procedure, the data entered using the client displays in this format irrespective of what you specify in the client.
To set up a display format that changes metadata value display:
Set Metadata Fields to Auto Populate
You can configure metadata fields to automatically contain certain values. For example, you might want to automatically populate a date field with a batch's scan date instead of having users enter it. Or, you might provide a default value for a field that users can change.
To configure a metadata field to auto populate:
Configure Regular Expression Validation
Regular expressions in metadata fields apply only to alphanumeric type fields. For more information, see documentation relating to using and formatting regular expressions, such as the following:
http://docs.oracle.com/javase/tutorial/essential/regex/
To configure and test a regular expression: