Viewing Completed Jobs
The History tab of the Monitor Jobs page (Admin > Manage Jobs and Sets > Monitor Jobs) lists all the jobs that have completed. In addition, Alma includes pages that list running and completed jobs of specific types. For the list of job types with their own Alma pages, see Job Types with Their Own Management Pages.
On the History tab, you can view jobs in a specific time period, according to filter parameters and/or by search results. The history of a job is available for up to one year after it is completed.
If you do not see the job in the Completed tab list, check the Running jobs tab to determine whether the job is still running.
To view the history of a specific job, select Job History in the row actions list for that job in the Scheduled tab.
Monitor Jobs: History Tab
To filter the list of jobs on the page:
- Use Submit Date to enter a date range for the completed jobs. By default, this filter is set to the past day.
- Use Job Category to filter jobs by category.
- Use Status to filter jobs by status. All Unsuccessful matches all statuses except Completed Successfully.
- In the Network Zone in a collaborative network, you can also filter by Institution Name to view jobs run on a specific institution. When viewing a report as an administrator in the Network Zone, reports and event data are read-only - there are no Actions buttons or links inside the report.
- Use the secondary search to search free text that matches a job’s Name or Job Details. Searches return only jobs that completed in the last thirty days.
Selecting Name searches the Name column, which can be seen on the page. Selecting Job details searches the Description column, which cannot be seen on the page. The Description column sometimes provides more information about the job.
Select Refresh to update the list as jobs finish.
Each job in the list includes the following fields:
Aborted by System – Canceled by the system.
Completed successfully – The job was processed successfully.
Completed with Warnings – The job completed successfully, but produced warnings. If the number of errors is above a certain threshold (which is different for each job), the job ends as Completed with errors.The following table presents some common jobs that may appear in the list of completed jobs:
| Job Name | Description |
|---|---|
| Any manual job run on a defined set – see Running Manual Jobs on Defined Sets | |
| Any scheduled job – see Viewing Scheduled Jobs | |
| Any job that also appears on a dedicated management page, including jobs created using integration profiles, import profiles, or publishing profiles – see Job Types with Their Own Management Pages | |
| Apply Calendar Changes | Update changes to institution/library opening hours. See Managing Institution/Library Open Hours. |
| Change Vendor on PO | Change vendor on PO. See Changing Vendors in PO Lines and POs. |
| Invoice - Create From Spreadsheet | Upload invoice from an Excel file. See Creating an Invoice From a File. |
| <PDA action> PDA Program <PDA name> | Pause a patron-driven acquisition. See To pause a PDA program. |
| Network MMS Record Harvesting Sync Job | Update Institution Zone bibliographic records linked to Network Zone bibliographic records. See The Network Harvesting Report. |
| Distribute Network Zone configuration table changes to member institutions | Distribute table changes to member institutions in a Network Zone. For more information, see Jobs for Centrally Managing Configurations and Profiles in the Network Zone. |
| Distribute Network Zone resource management changes to members | Distribute resource management changes to member institutions in a Network Zone. For more information, see Jobs for Centrally Managing Configurations and Profiles in the Network Zone. |
|
Distribute changes made in the Network Zone to various configuration profiles to the member institutions. For more information, see Jobs for Centrally Managing Configurations and Profiles in the Network Zone. |
|
| Distribute Network User Management Changes to Members | Distributes changes made in the Network Zone for role profiles and role assignment rules to the member institutions. For more information, see Jobs for Centrally Managing Configurations and Profiles in the Network Zone. |
| Distribute Network Letter Templates Changes to Members | Distributes any changes made to letters in the Network Zone to the member institutions. See Centrally Managing Letters in a Network Zone. |
| Export Order (PO Job | Send POs to vendors. See Financial Systems . |
| Export PO Lines (POL) Job | Send closed or canceled PO lines to vendors. See Financial Systems . |
| Export CZ data for Non-ExLibris Link Loader | Export all portfolios in a collection to Excel (Tools > Extended Export). See Working with the Portfolio List . |
| Electronic Activation | Activates electronic resources. See Activating Electronic Resources. |
| Export Electronic Resources URLs | Synchronize electronic portfolio URLs with external system. See Extracting Electronic Portfolio URLs . |
| Link <electronic collection> to <electronic collection Job | Link electronic collection to the Community Zone. See Linking a Local Electronic Collection to the Community Zone . |
| Users IMPORT / SYNCHRONIZE / EXPORT / EXPORT_USERS using <integration profile> |
Import/export users from/to a student information system (SIS). See Student Information Systems. The EXPORT_USERS job may be slowed or disrupted due to higher priority jobs or connection timeouts. It is therefore not intended to be run for a large number of users at once.
In the Users SYNCHRONIZE, Alma alerts only upon a fail rate of 5%. If the number of rejected users is less than 5% of the total number of processed users, the job will be marked as "Completed Successfully". |
| Delete Electronic Collection / Delete Electronic Service | Deletes an electronic collection or service. See the Delete Electronic Collection Job Report and Delete Electronic Service Job Report sections below. |
| Delete Usage Data | Deletes COUNTER usage data according to file ID. See Manually Uploading and Deleting COUNTER Data. |
| Manage set members job | Adds a large amount of selected results to an itemized list. See Resource Management Sets. |
| Itemize a set from MD import report job. | Adds a large amount of selected results from an import report to an itemized list. |
| PO Line - Receive All | Receives all PO lines currently displayed on the Receive New Materials page. If a filter is applied, only those records that match the filter are received. See Receiving New Physical Material. |
| ORGANIZATION_IMPORT_JOB (Esploro only) | Imports Esploro organization units. See Importing Research Organization Units in Bulk. |
| IMPORT_COURSE_USER_ASSOCIATION
REMOVE_COURSE_USER_ASSOCIATION (Leganto only) |
Adds or removes associations between users and courses. See Configuring Importing Course Enrollment Jobs. |
| Duplicate Researcher Report (Esploro only) | Checks for potentially duplicate researchers. See Checking for Duplicate Researchers. |
| Portfolios activation job | Activates many portfolios; run when the user requests to activate a large number (> 200) of portfolios at once. See Activating an Electronic Collection Using the Activation Wizard. |
For each job, you can:
- View details of a job’s status – select the icon in the Status column.
- View a job report – see Viewing Job Reports.
- View a list of related job events – Viewing Job Events.
Viewing Job Reports
You view job reports for jobs in the History tab of the Monitor Jobs page (Admin > Manage Jobs and Sets > Monitor Jobs). In addition, Alma includes job-specific pages that enable you to view reports for jobs of specific types. For the list of job types with their own Alma pages, see Job Types with Their Own Management Pages.
To view a job report:
- In the History tab, select Report in the row actions list of the desired job OR select the icon in the Status column and then select View Report Details. The Job Report page appears.
Below you can find details about specific job reports.
Authority Processes Job Reports
The Authorities - Preferred Term Correction report provides a count for Number of Bib-Heading(s) where no appropriate authorized term was found. Generally, a number appears for this count if there is problem with an authority record where a non-preferred term was detected by the job. For example, a non-preferred term is found in the authority index, and there is a problem with the authority record: for example, the non-preferred term is registered in the 410 field and the preferred term is in the 100 field. When this happens, the term cannot be changed to the preferred term, and the record is counted in this count. This is a very rare situation, but it is taken into account.
The Excel file for this report contains up to 10,000 lines.
Deleted Records Job Report
The job report includes counts for the following and an option to download a detailed Excel file (see the illustration below) of the report (with MMS IDs):
- Number of bibliographic records deleted
- Number of bibliographic records that have inventory
- Number of bibliographic records with associated PO line(s)
- Number of records related to other records
- Number of bibliographic records that are used by collaborative network members
To download a Microsoft Excel file with the list of deleted bibliographic records for this job — including, for collaborative network users, a list of your institutions that are associated with retained records — select Select to download report.
Link Local Electronic Resources to the Community Zone Job Report
The linking job provides the following report information:
- Total number of local portfolios processed
- Number of local portfolios linked to the Community Zone
- Number of local portfolios with no match
- Number of multiple bibliographic records with matches (with a link to a set containing MMS IDs)
- Number of multiple portfolio matches (with a link to a set containing MMS IDs)
- Number of bibliographic records linked to the Network Zone for collaborative networks (with a link to a set containing MMS IDs)
- Number of duplicate portfolios
The following local electronic collection, electronic service, and electronic portfolio information is kept when the linking job is run:
- Group settings
- PO line and license
- Public name (electronic collection)
- Description
- Notes
- Library
- PDA ID (portfolios)
Overlap and Collection Analysis Job Reports
The reports provide the following summary information:
- Name (of the job)
- Process ID
- Started on/Finished on dates and time
- Total run time
- Status
- Status date
- Records processed (total number)
- Records with exceptions (number)
In the Counters section, the following information is provided:
- Overlap analysis population (the option that you selected for Detect overlap based on the following population when you submitted the analysis job)
- Links to the reports created
Select the links in the Counters section to view the following comparisons/reports (in Excel format).
The number in parenthesis by each report link indicates the number of titles in the report. For example, Selected Titles - Title Overlap report (1) indicates that there is one title in the Title Overlap Report report.
| Report | Description | Report columns | |||
|---|---|---|---|---|---|
| Set comparison | |||||
| Complete Overlap Report | Matching titles with identical coverage dates. |
|
|||
| Partial Overlap Report | Matching titles with partially overlapping coverage dates. | ||||
| Title Overlap Report | Matching titles with mutually exclusive coverage dates. | ||||
| Unique Titles Report | Titles that are unique to the source set you created for the comparison. |
|
|||
| Selected titles - Do not include titles from the Community (Note that this option compares titles only, it disregards the coverage information)
The following three reports are always processed when the Overlap and Collection Analysis job is run; and only when there are results to report, there is a link to the report in the Counters section on the Job Report page.
Below is an example of a Partial Overlap Report that contains matching titles with partially overlapping coverage dates. This illustration is displayed in three sections, showing rows 1 through 9 for columns A-C, D-G, and H-K of the report. Specifically, columns G and K show the source and target coverage overlap information. For example, in row 2, coverage years 2000 – 2011 overlap between the source and the target sets for the "The South African archeological bulletin" title.
|
|||||
|
Selected Titles – Title Overlap Report |
This report contains matching titles that exist more than once in the repository. The identifier specified in the Excel spreadsheet also exists in the Alma repository and has more than one portfolio. |
|
|||
|
Selected Titles – Unique Titles Report |
This report contains titles that exist only once in the repository. The identifier specified in the Excel spreadsheet also exists in the Alma repository and has only one portfolio. | The same columns as the Unique Titles Report report. | |||
| Selected Titles – Not in DB Report | This report contains titles that did not have any matches. The identifier specified in the Excel spreadsheet may 1) exist in the Alma repository but does not have any electronic inventory, or 2) does not exist in the Alma repository at all. | Only one column, Identifier. | |||
| Selected titles - Include titles from the Community that are not in the Institution | |||||
| Selected Titles – Title Overlap Report | as above | as above | |||
| Selected Titles – Unique Titles Report | as above | as above | |||
| Selected Titles – Not in DB Report as above, | as above | as above | |||
| Selected Titles – Not in CZ report | This report contains titles that did not have any matches in the Community Zone. | Only one column, Identifier. This is the identifier that you specified in the Excel file you created for the analysis job. | |||
| Selected Titles – In CZ report | This report contains titles in the Community Zone that are not in the Institution Zone that match titles in the Excel spreadsheet that you selected for the Overlap and Collection Analysis job. |
|
|||
| Selected titles - Include all titles from the Community | |||||
|
Selected Titles – Title Overlap Report
|
as above | as above | |||
| Selected Titles – Unique Titles Report | as above | as above | |||
| Selected Titles – Not in DB Report | as above | as above | |||
| Selected Titles – Not in CZ report | This report contains titles that did not have any matches in the Community Zone. | Only one column, Identifier. | |||
| Selected Titles – In CZ report | This report contains titles in the Community Zone that match titles in the Excel spreadsheet that you selected for the Overlap and Collection Analysis job. |
|
|||
This report contains data for the following four record types:
- D (= Digital)
- P (= Physical)
- E (= Electronic collections and portfolios)
- C (= Collection)
For each record type, the job report indicates the number of new, updated, and deleted records.
The report also indicates records that remained unchanged except for their update date.
In addition, the job report includes the number of new, updated, and deleted bibliographic records—that is, bibliographic records that have no inventory (D, P, or E records) associated with them.
There is a known display error that occurs when you try to download the ZIP file for manual FTP. As a temporary workaround: right-click and save the report as HTML, open the saved HTML in a web browser, and then select Download zip file to manual FTP.
Network Publishing Job Report
This report includes three tables that contain the following counts:
- For the Network Zone, the number of New, Updated, Deleted, and Not Published (not changed) records for each resource type. (Electronic Inventory and Bibliographic Records Inventory are currently the types supported).
- For each institution, the number of records (filtered by type and status) that are linked to the Network Zone and used to enrich the Network Zone’s bibliographic records.
- The number of each member’s proprietary records (not linked to the Network Zone), per resource type, that are New, Updated, Deleted, and Not Published (not changed)
Loans - Overdue and Lost Item Job Report
The Loans - Overdue and Lost Item job displays information for loans that are overdue and requiring action to notify the user, post a fine to the account, or mark an item as lost. The summary lists the numbers of transactions that were successfully and unsuccessfully processed. Below the summary, the following four sections offer additional detail:
- Change to Lost - by Profile
- Overdue Loan Fines Created - by Profile
- Loans Which Notification Was Sent For - by Profile
- Overdue Notifications Fees Created - by Profile
The sections display the results of the job in terms of items changed to lost, fines created, and notifications sent. Expand a section and select Actions, then select either View failed records or View succeeded records to view the page listing the Job Events.
Job Report Page
EDI Job Reports
The reports for outgoing POs are short, containing information on the success or failure of the job. Reports for incoming files are more detailed, containing statistics on the number of invoices and invoice lines processed with errors, the number of related PO lines for these invoices, and details of each of the processing errors.
The Job Reports page includes some of the following sections and fields, depending on the type of EDI file processed:
- A green checkmark if the job completed successfully, or a red checkmark if the job completed unsuccessfully.
- Name – The job name
- An info icon with user information about the job
- Process ID – The job ID [Note: This should be "Job ID"]
- Total run time
- Started on – The job start date and time
- Finished on – The job end date and time
Alerts
- If the job completed with errors, this section appears and contains a list of alerts about the file. Additional information is available in the second Alerts section below.
Job Results Summary
- Total records processed
- Total files handled
- Total invoices – The number of EDI invoice files
- Total shelf ready order responses – The number of EDI Shelf Ready files
- Total report task order responses – The number of EDI Order Report files
- Total Journal Claim Order Responses – The number of EDI claim response files (vendor responses to claims that were previously sent from Alma)
- Total PO lines – The total number of PO lines mentioned in the Order Response. Appears only for Order Responses.
Alerts – For each alert, the following fields appear:
- Error description
- Error value
- Entity number (does not appear for invoices)
Invoice – Appears only for invoices. For each invoice, the following fields appear:
- Invoice number
- Number of invoice lines
- Number of related PO lines
Select Preview Records to view the invoice.
Order Response Report Task – Appears only for Order Response: Order Report files. For each PO line, the following fields appear:
- PO line in order response
- Tasks updated
- Tasks created
Select Preview Records to view the PO line.
Order Response Shelf Ready – Appears only for Order Response: Shelf ready files. For each PO line, the following fields appear:
- PO line in order response
- Items updated
- Items not updated
Order Response Journal Claim – Appears only for Order Response: Journal Claim files. For each PO line, the following fields appear:
- PO line in order response
- Items updated
- Items not updated
Select Preview Records to view the PO line.
Export PO Lines (POL) Job Report
The report includes the following:
- Total records processed
- Total files sent
- Total POs processed
- Total PO lines processed
- For each PO, the number of PO lines
- Alerts raised when running the job, if any
The job Export PO Lines (POL) can export only up to 1,000 PO lines. If more than 1,000 PO lines are marked for export, the job exports 1,000 of them and the job report page includes an alert suggesting that the user rerun the job to export any remaining PO lines.
Exported URLs Job Report
The Exported URLs job report (see Export URLs in Running Manual Jobs on Defined Sets) appears as follows:
Select the link in Link to Exported records to view the results. See Viewing Files Exported Using Export Jobs.
Dematic ASRS Job Report
On the Monitor Jobs page (Administration > Manage Jobs > Monitor Jobs), select Actions > History for the Dematic ASRS Inventory Export Job.
The Reports page includes the following sections:
- Report run statistics (name, ID, user, and run time information)
- Failure alerts for messages that could not be sent
- Total counts of the messages processed
- Date range for the report
- Breakdown count of Inventory Add messages successfully sent and failed
- Breakdown count of Inventory Delete messages successfully sent and failed
ASRS Report
The Inventory Add and Inventory Delete messages can be viewed in more detail by selecting Preview Records next to each line. Messages sent successfully show the barcodes that were sent. Messages that failed to send show barcodes and error messages.
Inventory Add Messages - Error
Alma provides additional inventory updates to the Dematic Automated Storage Retrieval System (ASRS) database when the call number, author, or title changes for an item in the ASRS. These ASRS remote storage inventory updates are in addition to the updates that are triggered when there is a change to an item’s barcode or when items are added or removed from the remote storage inventory. With this additional function, be aware that changes in title or author resulting from a relink holdings operation is not a part of the inventory update capability.
Analytics Job Report
The Analytics jobs send Analytics refresh reports and dashboards to the subscribed users. After running, the results are written to a job report.
Analytics Job Report
The report includes one row for each report or dashboard generated by the job. The report includes successful and failed recipients, reports or dashboards with no subscribers, and “non-existent” reports, which can happen if, after the report or dashboard was scheduled, someone changed the name or location of the report or dashboard source in Design Analytics.
Aleph Central Catalog Job Report
For information regarding the job report results for the Aleph Central Catalog, see Retrieving Changed Records from the Aleph Central Catalog.
Add Reminders Job Report
The Add reminders job provides the following job report:
For more information, see the Add Reminders job in Running Manual Jobs on Defined Sets.
Delete Electronic Collection Job Report
When selecting Delete in the repository search for an electronic collection (see Searching in Alma), the Delete Electronic Collection job runs. The Delete Electronic Collection job report indicates how many records were processed, how many records were processed with exceptions, and how many portfolios were deleted.
Delete Electronic Collection Job Report
Identify Records that are not Used in the Network Job Report
The Identify records that are not used in the Network job report is the result of running the Identify records that are not used in the network job (see Running Manual Jobs on Defined Sets).
Identify records that are not used in the network job report
Select the link to the new set that identifies the unused bibliographic records. See Viewing and Removing Members of Itemized Sets.
To delete the unused records using the new output set that you just created, see Delete Bibliographic Records.
Delete Electronic Service Job Report
This report is generated when you delete a service from the Additional Information tab in the Services section in the Electronic Collection Editor (see the Managing Electronic Resources page). The report is named Delete Electronic Service:<number-service name>.
The report is the same as the one generated when deleting an electronic collection; see Delete Electronic Collection Job Report.
Delete Holdings Records Job Report
The Delete holdings records job report is the result of running the Delete holdings records with no items job (see Delete holdings records with no items on the Running Manual Jobs on Defined Sets page). The report provides the following information:
- Total records processed
- Total number of holdings records
- Total number of successfully deleted holdings
- Total number of unhandled records
If a holdings record is attached to a PO line or has items, it is not deleted and is counted with the unhandled records.
- Total number of holdings records which failed to delete
Delete Holdings Records Job Report
Select Preview records in a row actions list to view the MMS IDs of the records related to that section. In the example below, you can see the MMS IDs for the deleted holdings records.
Deleted Holdings Records
Unlink a Set of Records from the Network Job Report
The Unlink a set of records from the network job report results from running the Unlink a set of records from the Network job (see Unlink a set of records from the Network in Running Manual Jobs on Defined Sets). The report provides the following information:
- Total records processed
- Total records unlinked
- Total records skipped - Skipped records are valid records (not records with errors) that are already local records so there's nothing to unlink, or records that are linked to the Community Zone and the link to the Community Zone is maintained.
- Total records with errors
Unlink a Set of Records from the Network Job Report
Select Export List to export the MMS IDs of the records related to that section.
Rollover Ledgers Job Report
The Rollover Ledgers Job Report page displays the following:
- Fund type
- Number of successful rollovers for each fund type
- Number of failed rollovers for each fund type
Rollover Ledgers Job Report Page
Rollover PO Lines Job Report
The Rollover PO Lines Job Report page displays the following information:
- Job parameters, including:
- Process ID
- Name of the process
- Date and time on which the process started
- Date and time on which the process finished
- Total run time of the process
- User that created the process
- Process
- Date and time on which the process status was recorded
- Total number of records processed
- Number of records for which processing failed (exceptions)
- Job events, containing the following:
- A link to PO lines that succeeded with the rollover (PO line rollover success)
- Links to PO lines that failed, with a description of the failure reason and the number of PO lines that failed in the link
- An Export to Excel button which enables viewing the problematic PO lines in an Excel file. The PO lines are grouped by the error message with which they are associated, and the Excel tabs are named according to the generated error messages.
- Continuity type
- Number of PO line successes for each community type
- Number of PO line failures for each community type
- A table of errors, if relevant. The table contains:
- Error type
- Number of failed PO lines as a result of the error
Rollover PO Lines Job Report Page
HealthCheck Job Report
See HealthCheck Tool.
Move Electronic Portfolio Information Job Report
The Move electronic portfolio information job report summarizes the following counters:
- Total electronic portfolios processed – The total number of source portfolios that were part of the source electronic collection set that were processed.
- Total portfolios matched – The number of source portfolios with a PO line and/or a license that had a matching portfolio.
- Total portfolios unmatched – The number of source portfolios that had no matching portfolio.
- Total portfolios skipped due to multi match – The number of source portfolios that were not processed because they has several matching portfolios.
- Total portfolios without data – The number of source portfolios that had a match but had no PO line and/or license to move.
- Total PO lines successfully moved – The number of source portfolios where their main PO line was successfully moved to the matching portfolio.
- Total PO lines successfully disconnected from source – The number of PO lines that were successfully disconnected from their source portfolio.
- Total portfolios their additional PO lines moved – The number of source portfolios where their additional PO lines were successfully moved to the matching portfolio.
- Total licenses moved – The number of source portfolios where their license was successfully moved to the matching portfolio.
- Total portfolios their historical licenses moved – The number of source portfolios where their historical licenses were successfully moved to the matching portfolio.
- Selected access provider – The access provider vendor selected to fill or replace the PO line's access provider of the matching portfolio.
- Total portfolios with public access model – The number of source portfolios that have "Public access model" indicated.
- Total portfolios that their public access model successfully moved – The number of source portfolios whose public access model was successfully moved to the matching portfolio.
- Total portfolios that were skipped from being updated with a public access model – The number of source portfolios whose public access model was not moved to the matching portfolio because a public access model was already stated in the destination portfolio.
-
Detailed report – This line of the report contains a link to an Excel spreadsheet that contains the following columns of information:
- Title – Bibliographic title.
- Title ID – MMS ID of the portfolio's bibliographic record.
- Source ID – MID for the source portfolio.
- Target ID – MID for the target portfolio. Multiple portfolios are separated by a semicolon.
- PO Line ID – Main PO line ID for the source portfolio.
- PO Line Successfully Connected to Target – Yes appears if the main PO line was successfully connected to the target portfolio. Failed appears if it did not succeed. The cell is left blank if the target portfolio had no main PO line.
- PO Line Successfully Disconnected from Source – Yes appears if the main PO line was successfully disconnected from the source portfolio. Failed appears if it did not succeed. The cell is left blank if the source portfolio had no main PO line.
- Additional PO Line Moved – Skipped appears if the Main + additional PO lines option was not checked for the Move PO lines parameter. If the Main + additional PO lines option was checked for the Move PO lines parameter, the additional PO line IDs separated by a semicolon appear in this cell. The cell is left blank if the source portfolio had no additional PO lines.
- License ID – The source portfolio's license ID. The cell is left blank if the source portfolio had no license.
- License Successfully Connected to Target– Yes appears if the license was successfully connected to the target portfolio. Failed appears if it did not succeed. Skipped appears if the Skip option was selected for the If destination already has a license parameter. The cell is left blank if the source portfolio had no license.
- License Successfully Disconnected from Source – Yes appears if the license was successfully connected from the source portfolio. Failed appears if it did not succeed. The cell is left blank if the source portfolio had no license.
- Historical Licenses Moved – Skipped appears if the Move historical licenses was not selected. If the Move historical licenses was selected, the license IDs appear separated by a semicolon. The cell is left blank if the source portfolio had no historical license.
- Access Provider Set To – The cell is left blank if the If PO line already has an access provider parameter was not selected. Skipped appears if the Skip option was selected for the If PO line already has an access provider parameter and the target portfolio has a license. Otherwise, the access provider's vendor code from the PO line form appears. Failed appears if something happened, and it did not succeed.
- Job Final Process Status – For the processing related to each row of the spreadsheet, this column indicates Succeed, Failed, Skipped, or No data to move.
- Comment
See Move electronic portfolio information for more information.
Distribute Network Administration Changes to Members Job Report
The Distribute network administration changes to members job report identifies the number of profiles created, updated or stopped for each institution.
Distribute Network Administration Changes to Members Job Report
Distribute Network Zone Configuration Table Changes to Member Institutions Job Report
The Distribute network zone configuration table changes to member institutions job report identifies the configuration-table changes that were distributed to each member institution. The job report consists of two sections:
- Job Details - The changes that took place in the configuration table for which the job was activated.
- Processed Member Institutions - The member institutions for which the change was distributed.
Distribute network zone configuration table changes to member institutions Job Report
MMS – Build Record Relations Job Report
This job creates relationships between MMS (bibliographic) records. See Using the MARC Linking Fields for Related Records for more information.
The MMS – Build Record Relations job report provides the following counters:
- Records processed – This is the total number of records processed as identified in the job report header information
- Connector linked and Pointer linked – These counters identify the number of reciprocal links created by the MMS – Build Record Relations job. Since this involves related records that point to each other, the Connector linked and Pointer linked counts should be the same.
- MMS ID based linked – This counter identifies the number of bibliographic records that were linked based on a specified MMS ID.
MMS – Build Record Relations Job Report
Upload Electronic Holdings - Springer
The Upload electronic holdings - SPRINGER job report identifies the electronic collections that were updated and provides the following counters:
- Serial Collection name – This identifies the name of the serials electronic collection that was updated.
- Serial input file – This provides a link to the Excel input file for the serials electronic collection.
- Serial Collection new – This counter identifies the number of new bibliographic records for the serials electronic collection.
- Monograph Collection name – This identifies the name of the monograph electronic collection that was updated.
- Monograph input file – This provides a link to the Excel input file for the monograph electronic collection.
- Monograph Collection updates – This counter identifies the number of portfolios updated for the monograph electronic collection.
- Monograph Collection deletes – This counter identifies the number of portfolios deleted for the monograph electronic collection.
- Monograph Collection BIB deletes – This counter identifies the number of bibliographic records deleted for the monograph electronic collection.
- Monograph Collection new – This counter identifies the number of new bibliographic records for the monograph electronic collection.
See Upload Electronic Holdings from Springer for more information regarding the integration profile setup and scheduling the job.
Save Set in Network Report
The Save Set in Network report is generated as part of the process of saving local sets in the Network Zone. The report is generated only in the member institution that initiated this process.
The report provides the following information:
- The Network Set name, prefixed with the member institution's code.
- Number of records processed in the original member set.
The process takes all records in the set that are cached from the NZ and creates a set out of them in the NZ. Local (not cached) records are not part of the NZ set. This means that the number of records in the NZ set might be lower than the number of records in the IZ set. - Name of the original IZ set.
Viewing Job Events
Events reports list additional information about completed jobs, highlighting the significant actions such as successful completion of a job and information about any errors that occurred during the running.
To view job events for a completed job, on the Completed tab of the Monitor Jobs page (Admin > Manage Jobs and Sets > Monitor Jobs), select Events in the row actions list. The events related to the job appear on the Events Report page.
Events Report Page
Events vary according to the type of job and the job’s tasks and parameters.
Hover your cursor over any event description to view the complete description.
To view job events for imports, see Viewing Import Job Events.