Editing the Coverage Spreadsheet Conversion Rules
To edit the Coverage Spreadsheet Conversion Rules, you must be assigned permission 554 (Edit Coverage Conversion Rules). See Permissions Used by Sierra for more information.
The Coverage Spreadsheet Conversion Rules are used to map the coverage data from coverage spreadsheet format into a format that:
- is readable by the Innovative system
- can be stored in the coverage table
To convert coverage data correctly from coverage spreadsheets (files in TXT or CSV format) to the format used in the Innovative system, maintain the Coverage Spreadsheet Conversion Rules.
The system applies the Coverage Spreadsheet Conversion Rules when it "preprocesses" the coverage spreadsheet in Coverage Load. Preprocessing maps coverage data from the spreadsheet format into a format used by Innovative.
To edit the Coverage Spreadsheet Conversion Rules, follow these steps:
- Choose Admin | Parameters | General | Coverage Spreadsheet Conversion Rules.
- Edit the Coverage Spreadsheet Conversion Rules file. See Mapping Data in the Rules Text File.
- Choose Save.
Mapping Data in the Rules Text File
The Coverage Spreadsheet Conversion Rules window contains three sections:
- The Special Date Handling section allows you to
- convert the date in the coverage spreadsheet to the current date, an earlier date, or a later date
To change the date to an earlier or later date, use the special term "_today", which is defined in the header for this section, to calculate the current date and then add or subtract years, months, or days. For example, the entry date|1 month ago |_today-1m, converts the date from the file to a date that is one month earlier.
- specify the date format of dates in the coverage spreadsheet
To specify the date format of dates in the coverage spreadsheet, use the special rule type datefmt. The datefmt rule applies to hyphen-delimited and slash-delimited dates in the coverage spreadsheet. While the datefmt rule appears to be a key/value pair, it has special requirements. The "value" of the key/value pair must be left blank. The "key" must be either:
- MDY
Interprets dates in the coverage spreadsheet as month followed by day followed by year. - DMY
Interprets dates in the coverage spreadsheet as day followed by month followed by year.
For example, enter "datefmt|DMY| " to interpret 05-06-2005 as 5 June 2005. The system stores this as 20050605 in the coverage table.
If the file does not contain a datefmt rule, dates are interpreted as month followed by day followed by year. - MDY
- convert the date in the coverage spreadsheet to the current date, an earlier date, or a later date
The Provider Conversion section maps provider names in the coverage spreadsheet to the provider names you use in your Innovative system.
If a provider name is not listed in the Coverage Spreadsheet Conversion Rules file, it is loaded into the coverage table as it appears in the coverage spreadsheet.
The Heading Conversion section maps fields (also known as headers or headings) in the coverage spreadsheet to the fields in the coverage table.
Any fields not listed in the Coverage Spreadsheet Conversion Rules are not loaded into the coverage table. This can be helpful for excluding extraneous fields.
Each of the section names, like the file header, is prepended with a "#" sign and is not "read" by the system. Each section contains rules. Each rule consists of a vertical bar delimited line with the following three fields:
| Column | Description |
|---|---|
| type | The type of field for which you are specifying a conversion, for example date, provider, or fields. See the example below. |
| key | The value to match in the input file, for example "JSTOR Business Collection." This field is case sensitive. Trailing spaces are ignored. See the example below. |
| value | The value to map the key to for the output file, for example "JSTOR:Business Collection." See the example below. |
Mapping Example
provider|JSTOR Business Collection |JSTOR:Business Collection
