To monitor an import job, see below for the required role.
For more information about record import, see Record Import. For information about import profile types, see Import Profile Types.
You can monitor an import job as it runs and view information about the job after it finishes. For information on running the job, see Importing Records Using an Import Profile
You monitor import jobs on any of the following pages:
Monitoring an Import Job
Acquisitions > Import > Monitor and View Imports
The Monitor and View Imports page.
|New Import (embedded order data (EOD)), Update Inventory
Resources > Import > Monitor and View Imports
The Monitor and View Imports page.
|Repository, Authority, Initial Authority, Digital
||Catalog Manager/Administrator, Repository Administrator
Resources > Import > Manage Import Profiles
Acquisitions > Import > Manage Import Profiles
Select History in the row actions list for a profile line to view the Job History page with the job history of that profile, or select the Monitor Imports button.
|All (if you select Job History in the row actions list for a profile line, you monitor only that profile)
Admin > Manage Jobs > Monitor Jobs
The Monitor Jobs page. Select the Running
tab to view running jobs or the History
tab to view completed jobs. Select Import
in the Job Category
For more information, see Viewing Running Jobs
and Viewing Completed Jobs
. For more information about jobs in general, see Managing Jobs
||General System Administrator
The Monitor and View Imports page lists all import jobs of the relevant type. The Job History page lists all jobs run using a specific profile and includes a short section with the profiles details at the top of the page.
Monitor and View Imports Page
The information shown on these pages is largely self-explanatory.
For the explanation of the naming convention of job history for Import Profiles configured with Import Protocol FTP, see naming convention of job history for import profiles with import protocol FTP
Note that for import profiles configured for the FTP import protocol, the import job has two parts / jobs (first to fetch the records, and second to load the files), and only the second job appears in the import profile history. In cases where there are no files on the FTP or the connection to the FTP server fails, the second job does not run and no import profile history is presented. To view the import history in these cases, use Admin > Manage Jobs and Sets > Monitor Jobs and select the History tab. The two FTP job names are: 1) Metadata Import w/FTP: <profile name> and 2) Metadata Import: <profile_name> (FTP).
Viewing an Import Profile Job Report
For more information about job reports, see Viewing Completed Jobs
(Import Profile) Job Report Page
The (Import Profile) Job Report page provides the following summary information for an import job:
- Records processed, imported, and deleted
- Records not imported or deleted
- PO lines processed and imported
- Physical/digital items and electronic portfolios processed and imported
- Holdings records processed and imported
The Total electronic portfolios imported count does not take into account the portfolios imported in the first file that is imported when the import is split into several files.
The report includes information organized into collapsible headings.
New Job Report Format and Content
The table below describes the less obvious information available in reports.
||The number of imported records that matched multiple existing records. Other fields in this area are subsets of this count.
|Unlinked from CZ
||The number of imported records unlinked from the Community Zone
|Newly added records
||The number of newly imported records with at least one match (that for some reason were not overlaid/merged if these options were selected)
|Records linked to CZ
The number of Community Zone records that were found as a match but skipped (due to the 'Skip record' option selected in the "Community Zone linked records handling" option of the import report, see Managing Import Profiles.)
Note that if no match is found in the Institution Zone, Alma makes no attempt to match with the Community Zone.
If during the import process you manually intervene to resolve a matching issue that results in more than a single match remaining, the other additional matching records that are automatically handled are not counted in the total number that appears in the Count column. This pertains to the following rows:
- Multi-matches resolved automatically
- Multi-matches resolved automatically, Disregard CZ records
- Multi-matches resolved automatically, Disregard invalid/canceled system
- Multi-matches resolved automatically, Prefer record with the same inventory type
In the row actions of the sections, you can view bibliographic records related to a result, create an itemized set for a row of results, or download sources as XML or binary files.
If Alma identifies more than 150 matches for a record being imported, Alma does not import that record and marks it as "Multi-matches, too many results were found" and "Records not imported, too many multi-matches results".
Records Not Imported can contain up to 1000 files.
If records were skipped, see Resolving Import Issues
for information on how to resolve this.
To preview the records from any row of results, select Preview Records
in the row actions list. Alma displays a record list of up to 50 bibliographic records to which the row refers (if there are more than 50 records and you want to see all of them, see Viewing Imported Records
When previewing records, it may happen that the number of records shown by selecting Preview Records
is lower than the number in the counter, for example:
This means that the other records are of a different inventory type. This happens when the option Single match - match only records with the same inventory type (electronic/physical)
is selected in the import profile (see Managing Import Profiles
). When this option is selected, the import job report provides additional information on an additional row "Match skipped - different inventory type" in the Bibliographic Record Matches section. This row shows a count of skipped matches due to a different inventory type.
To create an itemized set from any row of results, select Create itemized title set
in the row actions list. Complete the fields as you would for any itemized set (see Creating Itemized Sets
To download an XML or binary file containing the records, select Download sources (XML) or Download courses (binary) in the row actions list. The records are downloaded as a compressed file. To view or edit, unzip the file and open it in an XML or plain text editor or the program you use to work with binary files.
Records Not Imported Due to Version Prevention in a Job Report
Expand the Records Not Imported
section to view records prevented from overlaying or merging when a match was found during an import that utilized the Consider Originating System
or Ignore Originating System
options for the Do not override/merge record with an older version
parameter in the import profile (see Do not override/merge record with an older version
in Creating/Editing an Import Profile - Set Management Tags
for more information).
Report of Records Not Imported Due to Version Prevention
The Records with newer version in repository row shows the number of records that were not overlaid or merged as a result of the prevent option being selected in the import profile.
The Total records matched and skipped row includes as part of that number the records counted in the Records with newer version in repository row.
Holdings Records Report Details
When an import profile is configured to import holdings records, the import job report provides details regarding imported holdings.
Holdings Records Section in the Import Job Report
This section provides the following information:
- Total Holdings imported – This counter identifies the total number of holdings records that were imported. This number matches the Total Holdings imported counter in the Counters section of the import job report.
- Holdings added – This counter reports the number of new holdings records that were added as a result of the import job.
- Holdings updated – This counter reports the number of existing holdings records that were updated by imported holdings information.
- Holdings not imported – This counter reports the number of holdings records that were identified to be imported but were not imported for some particular reason.
Viewing File Details
The Import (Profile) Job Details page (on the Monitor and View Imports page, select View file details in the row actions list) displays details of the import job, including its status, the times at which the job run started and ended, the number of processed files, and the number of files rejected.
Import (Profile) Job Details Page
This page also shows details of each file included in the import job, including the file's size, creation date, the number of records it includes, its import status, and details of any problems that occurred during the import. Select Back to return to the Monitor and View Imports or Job History page.
When available, you can download the file to view it or to make corrections in order to re-upload / re-import the file. See Download Unimported Records
for more information.
For situations where an import job failed (such as Failed in Commit after calling NZ
) that is not due to a data error, you can select Rerun
to easily run the import again with the file in the row from which you selected Rerun
. See Rerun
for more information.
Download Unimported Records
To download the unimported records, on the Import (Profile) Job Details page select Download unimported records
in the row actions list. The file is opened or downloaded to your computer. Edit the file to correct the invalid records and then re-import the file, as described in Importing Records Using an Import Profile
The following is a partial example of a file that contains an unimported record.
When an import job fails that is not due to a data error (such as Failed in Commit after calling NZ), use the Rerun action to run the import job again with the import file that is specified in the row from which you select the Rerun action. Note that this action is available for Repository, New Order, and Update Inventory profile type import jobs that use the Upload file or FTP import protocol, and specify XML or Binary for the physical source format.
Viewing Import Job Events
You can view information for each event generated when an import job was run on the (Import Profile) Events Report page (on the Monitor and View Imports page, select Events in the row actions list), including:
- Event Description
- Event Date
Select Back to return to the Monitor and View Imports page.
Events Report Page (Import Job)
Viewing Imported Records
You can view the imported records on the Repository Search page (on the Monitor and View Imports page, select Imported Records
in the row actions list), filtered by the import job ID (see Searching in Alma
Viewing PO Lines Associated with an Import Job
To view the PO lines created by the import: On the Monitor and View Imports page, select Imported PO Lines
in the row actions list. A record list of PO lines appears, filtered by the import job ID (see Searching for PO Lines