Configuring RTA for III Millennium

Mapping RTA Statuses

• Enabled – Select this field to enable the mapping row.
• Status – Specify a value or regular expression that matches an availability status in the III Millennium response. The system uses this regular expression to map entries in the response to the statuses specified in the Code field.
• Code – Select the availability status to display in Primo from the drop-down list. The valid availability statuses are Available, Un-Available, and Check Holdings.
  With SP 3.1.1, you can display the due date instead of the Un-Available status. For more information, see Mapping Due Dates.
• Description – This field contains an optional description of the mapping entry.

Mapping Due Dates

1. A row that uses a regular expression to find responses that contain a due date. This regular expression must contain two groups that are enclosed with parentheses, such as (DUE) (.*). The first group is used to match the text label, and the second group is used to extract the date.
   For Example:
   If the due dates in the III Millennium responses display as follows:
   DUE 01-01-2011
   You can define the mapping row as follows to find the word DUE (as shown in the first group) and extract the date (as shown in the second group):
   
2. A row that indicates the format of the dates displayed in the III Millennium responses. To specify the format, you must specify a date pattern (such as yyyyMMdd) that uses the following reserved characters:
   • y – Indicates the year. If the number of pattern letters is two, the year is truncated to two digits. Otherwise, it is interpreted as a number:
     • yyyyy – 01991
     • yyyy – 1991
     • yy – 91
   • M – Indicates the month. If the number of pattern letters is three or more, the month is interpreted as text. Otherwise, it is interpreted as a number:
     • MMMM – August
     • MMM – Aug
     • MM – 08
   • d – Indicates the day. The number of pattern letters is the minimum number of digits, and shorter numbers are zero-padded to this amount:
     • dd – 07
     • d – 7
     Text in date patterns can be quoted using single quotes (') to prevent them from being interpreted by the system. All non-reserved characters are simply copied into the output string by the system.
     For Example:
     If the format of the dates in the III Millennium responses display as follows:
     DUE 01-01-2011
     You can define this mapping row as follows to specify the format of the date in the second group:
     
     After you have mapped the due date to a code, you can configure how the code displays in the results. For more information, see Displaying Due Dates.

Mapping RTA Locations

Displaying Due Dates

• Calculated Availability Text – The following codes define the format of the due date and location in the Brief Results:
  • default.delivery.code.duedate – Due {2}} {1}}
  • default.delivery.class.duedate – getItRed
  • default.delivery.gadgetclass.duedate – getItRed
    The placeholder {2}} is used for the due date and {1}} is used for the best location.
• Getit Tile – The following code defines the format of the due date in the Locations tab:
  default.fulldisplay.availabilty.due_date – Due {0}}
  The placeholder {0}} is used for the due date.

Defining the Additional Source Record ID in the PNX

1. On the Primo Home > Advanced Configuration > Full Normalization Rule Configuration page, click Edit in the row that contains your normalization rules set.
   The Manage Normalization Rules page opens:
   
   Manage Normalization Rules Page
2. Select the Display empty PNX fields check box.
3. Click Edit in the row containing the control:addsrcrecordid field.
   The Normalization Set Editor page opens:
   
   Normalization Set Editor Page
4. Click Create to add a rule for the control/addsrcrecordid field.
   A new rules section opens:
   
   New Rules Section
5. Configure the rule as follows:
   
   Rule Added to Rules Section
   If the contents of the control/sourcerecordid field contains extra leading or trailing characters, you must add transformation routines to remove them.
6. Click Save.
   To apply this change to the PNX records, you must re-run the pipe. You can use the No harvesting - Update Data Source pipe type to run the pipe without re-harvesting.