Intota: Offline Date and Status Editor: Record-Matching Logic
- Product: Intota
What are the required fields and values for a successful ODSE upload?
When you use the Offline Date and Status Editor (ODSE) to change the status, custom dates, etc., of resources (titles) in a database, the file you upload into our system needs to have certain information about each resource so that we can match the resource to the appropriate record in the 360 KB knowledgebase.
The best results come from using ODSE as it was designed: From Intota download the title list -- which includes Title IDs assigned by our knowledgebase -- make changes and additions to the spreadsheet, and then upload the file again.
However, if you will be using your own file (or one supplied by a provider), you may be limited in terms of available metadata (for example, a provider-supplied file may not necessarily include titles, ISBNs and URLs for Ebooks). The logic displayed in the below tables shows you what combinations of fields the ODSE system can use to match resource information to the records in the knowledgebase.
For information on the error messages that the system can generate after an upload, see Upload Errors.
- NOTE: If a title does not have a publication date in 360 KB -- which sometimes happens for e-books -- the ODSE system will be unable to make changes to the title, and won't show you an error message to that effect. You'll be able to tell it happened because your changes won't appear in your Intota profile.
E-books
Four fields are used for matching resources to the appropriate E-book records in the knowledgebase:
- Title ID (assigned by the knowledgebase)
- ISBN/ISSN
- Title
- Default URL
ODSE only requires a match on one of these four fields. As shown in the below table, ODSE will attempt to match on the Primary Match Field. If that fails, ODSE will attempt to match on the Secondary Match Field, or if need be, the Tertiary Match Field. Once a match is made, the other match fields are ignored.
The title field must always be populated to avoid an error, but the title field is only used for matching in limited cases.
| Field Combinations Accepted | Primary Match Field | Secondary Match Field * | Tertiary Match Field ** | |||
|---|---|---|---|---|---|---|
| Title ID | ISBN/ISSN | Title | Title ID | --- | --- | |
| Title ID | Title | Title ID | --- | --- | ||
| Title ID | ISBN/ISSN | Title | Default URL | Title ID | --- | --- |
| Title ID | Title | Default URL | Title ID | --- | --- | |
| ISBN/ISSN | Title | ISBN/ISSN | Title | --- | ||
| ISBN/ISSN | Title | Default URL | ISBN/ISSN | Title | Default URL | |
| Title | Default URL | Title | Default URL | --- | ||
| Title | Title | --- | --- | |||
* Only used if there is no match on the Primary Match Field.
** Only used if there is no match on the Primary or Secondary Match Field.
E-journals
Two fields are used for matching resources to the appropriate E-journal records in the knowledgebase:
- Title ID (assigned by the knowledgebase)
- ISSN/ISBN
ODSE only requires a match on one of these fields. As indicated in the below table, once a match is found, the other match field is ignored.
The title field must always be populated to avoid an error, but it is not used for matching E-journals.
| Field Combinations Accepted | Match Field | ||
|---|---|---|---|
| Title ID | ISSN/ISBN | Title | Title ID |
| Title ID | Title | Title ID | |
| ISSN/ISBN | Title | ISSN/ISBN | |
- Date Created: 25-May-2014
- Last Edited Date: 7-Oct-2016
- Old Article Number: 10789