Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Running Manual Jobs on Defined Sets

    Translatable

    Overview

    This section presents how to run a job manually on a defined set of objects. To see how to view running, completed jobs and scheduled jobs see here.

    To run a manual job, you must have roles that enable you to a) access the Run a Job – Select a Job to Run page, and b) run the job.
    To access the page, you must have one of the following roles:
    • General System Administrator
    • Repository Administrator
    • Repository Manager
    • User Administrator
    • User Manager
    Only jobs that you can run (that are available to you because of your user roles) appear to you on the Run a Job – Select Job to Run page. See the table below for the required roles for each job.

    How to Run Jobs on Sets

    To run a job on a set:
    1. If there are no sets defined or if you require a specific set for the job you are running, you must first define the set. For information on defining sets, see Managing Search Queries and Sets.
    2. On the Run a Job – Select Job to Run page (Admin > Manage Jobs and Sets > Run a Job), find the job you want to run. Note that each job requires you to have a certain role to view the job in the table; see Manual Jobs and Their Relevant Parameters.
      Run a Job.png
      Run a Job - Select Job to Run Page
      For each job, the following information appears:
      Run a Job – Select Job to Run Page Columns
      Name Description
      Name The name of the job.
      Description A description of the job.
      Content Type The type of set that the job processes. For example, researchers, research assets, etc.
      Type The type of request or job that runs (for example, export, move items, or requests).
    3. Select a job and select Next.
      The Run a Job - Select Set page appears.
      Run a job page 2.png
      Run a Job - Select Set Page
    4. Select a set and select Next.
      If there are parameters to set, the Run a Job - Enter Task Parameters page appears. If there are no parameters to set, the workflow skips this page.
      Run a job page 3.png
      Run a Job - Enter Task Parameters (Example) Page
      The number of members in the set that you selected in the last step appears on this page. Verify that this number is similar to what you expected based on the selected set.
      Enter the required parameters. To see the parameters required to configure for each job, see Manual Jobs and Their Relevant Parameters.
    5. Select  Next. The Run a Job - Review and Confirm page appears.
      Run a job page 4.png
      Run a Job - Review and Confirm (Example) Page
    6. Optionally enter a more descriptive job name to replace the default one. The name identifies this job for editing and monitoring.
      • The number of members in the set that you selected in the last step appears on this page. Verify that this number is similar to what you expected based on the selected set.
      • For more information on the API Information section, see the Developer's Network documentation.
    7. Review the job information and:
      • Select Submit and select Confirm in the dialog box to run the job.
      • Select Back to go back and correct any information that you entered.
        When you select Back, you are taken back one page at a time. You can select Back on any page to go back to the previous page.
      • Select Cancel to delete what you entered and return to the home page.

    Manual Jobs and Their Relevant Parameters

    The following table lists the available manual jobs that can be run on defined sets. To run the job you must have one or more of the roles in the Roles column.
    Manual Jobs by Content Type
    Name Content Type (set type) Type Description and Parameters Roles
    Update Set of Research Assets Research Assets

    Research Assets

    Updates research assets.

    Parameters:

    • Creator or Contributor -
      • replaces the affiliation that the creator or contributor had at the time that the asset was created
      • Display or hide asset in public profile of researcher
    • Academic Unit - adds, replaces, or remove an asset's current affiliation.
    • Access Rights - replaces or removes the access rights granted to an asset.
    • License - replaces or removes the license held by an asset.
     
    Delete Set of Research Assets Research Assets Research Assets

    Deletes research assets.

    Parameters (checkboxes):

    • Do not delete if related to other assets - if checked, will not delete assets related to other assets.
    • Do not delete if includes a file - if checked, will not delete assets that include a file.
    • Do not delete if includes a reserved DOI - if checked, will not delete assets that include a DOI.
     
    Register DOI for Research Assets Research Assets

    Research Assets

    Registers DOIs for asset sets. 

    This job needs to be run on assets with 'reserved' DOIs in order to register them.

     
    Import Research Assets Files Research assets Research assets

    This job iterates over the assets in the set, finds any files at the end of links, uploads them to Esploro, and then changes the link to be a pointer to the (now local file).

    Research Assets Manager
    Import Research Assets Relations Research Assets Research assets Once assets have been imported from another system, this job creates the relations for each asset in the set. Research Assets Manager
    Export Esploro Handles Research assets Research assets Updates your local Handle server with Esploro inventory. Run the job on the Approved Handles for Export set. 
    Parameters:
    • General Information
    • Authentication
      • Authentication
        • No Authentication (default) – no authentication information is added
        • Public/Private Key
        • Secret Key
      • Admin Handle – the Admin handle to add to the exported file for authentication
      • Admin Index – the Admin index to add to the exported file for authentication
      • Private Key File Path (for Public/Private Key authentication)
      • Passphrase (for Public/Private Key authentication)
      • Password (for Secret Key authentication)
    • Parameters
      • Operation
        • Create
        • Add
        • Modify
        • Remove
        • Delete
      • Add Index
        • Index – the index to add to the handle
        • URL – the URL to add to the handle
    Research Assets Manager
    Index Research Assets Research assets Research assets

    Push research assets to Primo / Primo VE when you don't want to wait for the scheduled re-indexing.

     
    user defined research assets normalization jobs Research assets normalization Research assets Appears if you have defined a research assets normalization process. This job normalizes the contents of research assets. See Asset Normalization.
    Parameters:
    Each task has a normalization rule (drools file key) predefined. You can select a different one, if you prefer.
    Research Assets Manager
    Research Assets CSV Export RESEARCH_ASSETS_EXPORT Export research assets in CSV format for update and import. Exports asset metadata to a file.
    Parameters:
    • Physical format - Currently, CSV is the only option.
    • Export into folder - Private or Institution; see Viewing Files Exported Using Export Jobs
    • FTP configuration - Select a predefined FTP configuration; see Configuring S/FTP Configurations.
    • Sub-directory - The path relative to the FTP configuration.
    • Export type – Selective or full export. Selective export allows choosing which fields will be included in the export file. 
     
    Update/Notify Users User Users Updates parameters for users and/or notifies users.
    This job lets you add roles to users. For roles that have the role parameter "Read Only", this job does not let you set that parameter to selected when adding the role. This job does not let you add roles with other types of role parameters.
    For more information on this job, see the Bulk Actions on a Set of Users video (4:33 mins).
    Parameters:
    For the field Added/changed field:
    • By user account type: Handles specific fields according to the account type (internal or external).
      For example, if using the job to add a block, the block is added as external for external users and as internal for internal users.
      Internal field values are not overridden during an SIS update. External field values are overridden during an SIS update.
    • Internal: Handles specific fields as if they are internal, even when belonging to an external account.
      For example, if using the job to add a block, the block is added as internal even if the block is being attached to an external user.
      Internal field values are not overridden during an SIS update.
      The fields affected by this setting are:
      • User group
      • Campus
      • Resource sharing library
      • Add block type
      • Add statistics category
      • Add note
    To change internal users to external, or vice versa, select Set Account To and the relevant target account type. If external users are changed to internal users, the users’ passwords are reset to 10 random characters. If you select Don't Generate Password, no password is set; this field appears only if you select one of the Set Account To options.
    To email/notify users, select Send Notification to User and select the notification type. To configure notification types, see Configuring User Notification Types and the User Notifications Letter in Configuring Alma Letters.
    The roles that cannot be updated by this job are:
    • Circulation Desk Operator
    • Circulation Desk Operator - Limited
    • Circulation Desk Manager
    • Requests Operator
    • Work Order Operator
    • Receiving Operator
    • Receiving Operator Limited
    • Fulfillment Services Operator
    User Administrator, User Manager
    • Was this article helpful?