Import resources
For training resources
|
The Add/Update tab lets you import new or updated resource and item records.
note If you are importing updated resource and item records that were exported from this installation of Destiny®, use the Update Only tab.
Before you begin
Make sure:
- Your import file is in the same XML format as that generated by Destiny Resource Manager, the Asset Import Converter, or Follett School Solutions, Inc.
- You have already created or imported the resource templates that define the contents of the incoming records. Destiny skips any incoming records that do not have existing templates.
To import new and updated resources

- If you are not on the Import Resources page, then follow the steps in the blue title bar.
- Select Add / Update.
- In the Resource Matching section, choose to skip the incoming resource or replace the existing resource when Destiny determines that an incoming record is a duplicate.
- In the Item Matching section, choose to skip the incoming item, replace the existing item, or always add the incoming item.
- If you always add the items, select the method for assigning the barcode numbers:
- Select the first option, and enter a starting barcode number.
- To allow Destiny to find and use the next available barcode numbers, select Assign next barcode.
This option is not available for district resource managers. - To find your import file, click Browse.
- For a complete listing of the resources and items imported, deselect the Limit the Job Summary details… checkbox. Otherwise, the summary includes only errors.
- To check the results before importing, click Preview.
note 'Preview' reads the incoming records, compares them to the existing records, and generates a job summary, but does not actually import the records. After the preview, you can look over the report and decide whether your import settings need any adjustments before you do the actual import.
- To begin the import, click Import. The Job Manager page appears.
- To review the import, click View.
note If you are updating existing resource items, the import does not replace existing information in the following fields: Resource Type, Condition, or Status.
Additional information

Invalid records
Destiny skips invalid records.
To be considered valid, a resource record must include the following:
- Data in at least one of the required fields that make up its Displayable Name.
- Data in the Template field that is the fully qualified resource type from your resource template hierarchy.
For example:
Template
Computers|Desktop|Library|Search stations
/Template
A valid item record must include the following:
- A unique barcode number.
- A Short Site Name that exists in the district.
If the item record includes a District Identifier, it must be unique, or Destiny skips the record.
Any license or media item records must be of a resource type that is designated as software.
Any items that are not license or media items cannot be of a resource type designated as software.
Incomplete records
If a resource or item record is incomplete, Destiny imports the record if it has the two required fields (above).
If there is no incoming Status, it is set to Available.
If there is no incoming Condition, it is set to Usable.
If there is no incoming Home Location, Custodian, Department, or Funding Source, it is set to Undefined.
It also adds a message to the job summary when encountering the following conditions:
- A record is missing one or more required fields.
- A record has fields that do not exist in the template.
- A record has data that does not match the data type defined in the template.
- A record contains a Department, Funding Source, Home Location, or Custodian that did not exist.
- A record has an unknown Status, or a Status of Checked Out or In Transit. (The Status is set to Available.) If you chose to replace existing item records, the Status does not change.
After the import, you need to review the job summary and edit these records.
Job summary
The job summary for an import or a preview includes the following information:
- Whether the job was an import or a preview
- The number of records read
- The numbers of resources and items that were (or would be) added, skipped, or replaced
- The number of errors that occurred during the import
- A summary of the errors and warnings encountered during your import
- The name of any resources that were (or would be) skipped, and the reason
- The barcode number of any items that were (or would be) skipped
If you deselected the Limit the Job Summary details…
checkbox, the job summary also includes a complete list of the resources and items that were imported.
The job summary provides links to edit any records that have incomplete information.
Note About Preview and the job summary:
When you choose to preview an import and then perform an actual import, the numbers in the two job summaries might be slightly different. This is because of the matching process and the state of the database.
Preview compares each incoming record with those in the database. It determines whether the incoming record matches one already in the database. If it does not find a match, the job summary reports a resource added. If it does find a match, the job summary reports the resource skipped or replaced (depending on the settings chosen). During Preview, the database does not change.
Import first compares each incoming record with those in the database. It determines whether the incoming record matches one already in the database. If it does not find a match, it adds the record to the database. If it does find a match, it skips or replaces it (depending on the settings chosen). During Import, the database changes with every added record.
Since Preview does not change the database and Import does, the numbers reported in the job summaries might be slightly different.
example In the import file, there are two records of the same resource, A and B. Import would add A to the database. When Import encounters B, it would recognize it as a match to A and skip or replace it. Preview would import record A and, because Preview does not see A in the database, Preview would import B as well.
The difference between Preview and Import also applies to items. Duplicate barcodes can cause similar differences in the number of items replaced or skipped.