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

    E-Resource Activations

    Ex Libris supports migration from certain link resolver systems, such as SFX and 360Link.  Other link resolver systems are not supported in migration, so customers may batch-active resources using the E-Resource Activation Form, an Excel worksheet which contains the current list of e-resources available in the Alma KB.
    Migrating from SFX and 360Link uses a different process and does not use this E-Resource activation form. See the SFX to Alma Migration Guide and the 360 and Intota to Alma Migration Guide for more information.
    The main steps for non-Ex Libris systems:
    1. Customer: Downloads an up-to-date Excel template. The Excel includes all potential global/CZ-managed electronic collections according to package type: Licensed Aggregators, Free Aggregators, and Selective Aggregators.
    2. Customer: Updates the Excel form to indicate the relevant global electronic collection (package) and selective title activations. Ex Libris recommends using your sandbox access to the community zone (CZ) search to help in the matching of your link resolver collection and title names to the CZ version names. Additionally, the particular title list for any package must be provided in the Excel Title tab along with at least one identifier of PORTFOLIO_PID, ISBN, or ISSN in order for the package activations to include any the titles. If the customer institution has multiple activations for the same resource, such as the law library and the main library, multiple forms may be submitted, which will result in double activations.  See the section on Multiple Activations below.
    3. Alma Migration Team: During Alma migration, processes and loads the Excel file to activate e-resources indicated by the customer in the Excel file.
      The Excel format used in the batch title activation flow described in this document is very similar to the one that can be used for batch activation in Alma for ongoing purposes. The main difference is that the ongoing process handles loading titles for a specific electronic collection, whereas this process handles activating electronic collections and loading all titles in one batch process. This process of batch activating all titles for all e-collections for the library is migration-specific and done only during implementation.

    Loading Options

    There are a few options that customers can consider when submitting the E-Resource Activation form for loading to Alma during migration.

    Combine activations (Yes/No) - When Combine Activations is set to Yes, if there are multiple input forms, then activations in the second input form will be combined with the existing activations in Alma.  This options works even when the previously loaded activations are from a different e-resource system, such as SFX.  For more information on this, see Multiple E-Resource Input, and also the "Multiple Activations" section below.

    Deduplicate Portfolios (Yes/No) - when Combine Activations = Yes, then if both activations are Selective (BY_TITLE), then portfolios in the packages will be deduplicated.  Please note that if the multiple portfolios have different date ranges, only the date range from the first portfolio will be used.

    Match by Title (Yes/No) - When a package is Selected (BY_TITLE), and the titles listed do not have an identifier such as ISSN or ISBN, then the loader can attempt to find a match by comparing the exact title of a portfolio with the titles of the portfolios in the specified package.  The title is an exact match, including punctuation, so 'Biology.' does not match 'Biology'. Match by title is not attempted if identifiers are present but failed to find a match. 

    The match by title option can currently process 10,000 titles per hour, which may add a significant amount of processing time to your overall migration timeline.    If you have 400,000 titles without an identifier, this could add 40 hours to your timeline. 

    If you wish to use one of these options, inform your Ex Libris representative so that they can inform the migration analyst.

    Customer fills in the form

    Packages Tabs

    In this document, and in the accompanying Excel spreadsheet, the term package is used to mean electronic collection which has a list of titles, either Activate All or Selective Activation.
    There are five tabs on the E-Resource Activation spreadsheet - the first three tabs are packages tabs, the fourth is the Database tab (zero-title packages), and the fifth is a TITLES tab that is used to list titles for packages indicated as Selective Databases (activated with BY_TITLE).
    The first three tabs, FREE_PKG, LICENSED_AGG, and SELECTIVE_PKG contain package information.
    Local packages cannot be activated using this tool. They must be activated in Alma manually post-migration. The standard Alma portfolio/title loader may be used to batch populate local packages after they are manually activated.
    Post-migration, the bibliographic records for the packages from FREE_PKG, LICENSED_AGG, and SELECTIVE_PKG are suppressed from discovery.  The titles in the packages are what is interesting to the customer, so they migrate as available in the discovery system.
    Free Packages vs Open Access (CDI)
    The FREE_PKG tab is populated automatically by checking the 'Free' flag on e-collections in Alma. 
    Free (Open Access in Alma) is not the same as the Open Access indication for CDI.  For more information on Open Access, see Open Access Content in CDI.

    Database Tab

    The DATABASE tab contains zero-title packages, and operates similarly to the three packages tabs as described above.  The dropdown contains Y, N, and BY_TITLES, but BY_TITLES is not actually used - if selected, this will act as if it is N.
    Post-migration, the bibliographic records for the databases migrate as unsuppressed and made available for discovery.  Additionally, if the database is linked to CDI content, the CDI content is also discoverable.

    Columns on Packages and Database tabs

    Field Name Notes
    PACKAGE_NAME The name of the package.  For Databases, there may be some packages with identical names.  See "Duplicate Database Names" section below.
    SERVICE_TYPE Some packages have multiple service options available, for example getFullTxt or getSelectedFullTxt.  
    ACTIVATE? 
    Indicate how you want the package to be activated (or not) using this column.
    • N – Do not activate any titles in the package. 
    • Y – Activate all titles in the package. Titles do not need to be listed in the TITLES tab.
    • BY_TITLES – Activate the package but only activate the titles that are listed in the TITLES tab. If you select BY_TITLES, but no titles are listed in the TITLES tab, the package still copied from CZ to IZ as INACTIVE, with no portfolios.
    Leaving the ACTIVATE? column blank defaults to N.
    AVAILABLE_FOR_GROUPS
    Here you can specify the name of the campuses/institutions for which the resource should be made available. For multiple values, use a semicolon separator with no spaces (for example GROUP1;GROUP2;GROUP3).  AF Groups are assigned at the service level.

    For multiple campuses/institutions that require specific access by certain groups of patrons, fill in the column AF GROUPS. In order to have the institute name (and the AF group for the default institute if you provide it) saved and assigned in Alma, the AF groups must be turned on in the Inventory Network Groups configuration area (Alma Configuration -> Resources -> Inventory Network Groups).  The value required here for the AF group is in the first column, 'Group Name'.

    clipboard_eb1e01508b9e1c401f1145bea8189ac3e.png

    It is not currently possible to assign AF groups to Databases via the E-Resource Activation Sheet.

    If you used AF GROUPS in the form, your PS representative must inform the migration analyst in the SF case for the load.

    USE_PROXY Yes or No.  Blank = No.
    If USE_PROXY = Yes and you filled in a group(s) in the AVAILABLE_FOR_GROUPS column, then the proxy will be made available for the specified group(s).  
    If USE_PROXY = Yes and there is no group in the AVAILABLE_FOR_GROUPS column, then the proxy will be made available for the entire package.
    Information on resolver proxies may be found at Resolver Proxies.
    LEAVE  BLANK This column is not used in this worksheet, but must be present for data consistency with the loader program.  Please leave this blank.
    PROXY_SELECTED

    If USE_PROXY = Y, then you may specify a proxy code in this column.  If you leave this column blank, the default proxy will be assigned.

    If USE_PROXY = N, then this column is not used.

    Multiple entries on the Database Tab

    There are some databases which have the exact same title as another database in the list, and it is impossible to tell the difference between the two databases from the title alone.  In this case, there are two hidden columns in the Database tab, columns A and B, which may be used to determine the correct database line to activate.  To see columns A and B on the spreadsheet, just drag the column headers. 

    clipboard_efc8d10474fdb7d6e1308968aabb96659.png

     

    Do not modify columns A and B, as they are used by the loader program to activate the collections/databases.

    The following image shows column A, which is the collection ID.  Customers can compare collection ID in the spreadsheet to the collection ID in Alma to identify the correct database.  The following examples show where to find the collection ID in the spreadsheet and in Alma.

     

    clipboard_e7da2f990f172112ed40fd686925a4560.png

    Multiple Activations

    Customers who have multiple administrative units migrating to a single institution in Alma may desire to manage their activated resources separately.  In this case, customers may fill out multiple forms and have them loaded into the same institution.   The multiple activations can be combined in Alma or activated separately depending on the response to the 'Combine Activations' flag - see "Loading Options" above for more information

    Available For groups: When the different administrative units have multiple Available For groups, Ex Libris recommends you use a different AF group for each form.  For example, the main library has an activation for Resource A, and so does the law library.   When Combine Activations = No, the main library form will activate this resource with AF group MAIN, and the Law library form will have this resource activated with AF group LAW.   When Combine Activations = Yes, the AF group LAW  will be added to the existing activation so the final activation has AF groups of MAIN and LAW.

    For more information on multiple e-resource input, see Multiple E-Resource Input.

    Ebook Central

    Packages for Ebook Central are not included in the E-Resource Activation Sheet.  Ebook Central resources are automatically updated by synchronizing directly with the Ebook activation system.  For more information, see PQIS and Ebook Central Activations in the Electronic Resources migration guide.

    Individual Titles/Portfolios

    On the TITLES tab, provide the following information in order to determine the relevant title activations and optional coverage characteristics to apply to those activations – per global package from package tabs described above.  Only one line per title is supported.  If your institution has multiple coverage dates, the title must be loaded once with a single coverage date span, and then the coverage dates corrected afterward in Alma.
    Globally managed titles that are part of globally managed packages (matched based on either ISBN, ISSN or Alma community zone’s internal PORTFOLIO_PID for the package indicated) automatically obtain the bibliographic information managed in the CZ and are activated accordingly in your institution. For every non-local portfolio listed in the titles tab, at least one ISBN, ISSN, or Alma portfolio PID must be provided in order to be considered for loading/activation.
    If you have multiple identifiers for a title, they may be provided in the three ISSN or three ISBN fields provided.  Do not provide multiple identifiers in a single field. 
    Creating local portfolios 
    Sometimes the titles on the TITLES tab do not find a match in the CZ.  This could be because the title is not in the CZ yet for this package (it may be there for a different package), or the identifiers provided are not the same as the identifiers in the CZ.  When the title is not found as a CZ match, it is automatically added as a local portfolio for the global package indicated.  Customers may request to have this title added to the CZ post-migration.
    When local portfolios are created, the default bibliographic record template is used.  If the default template is modified, some extraneous fields/punctuation may be present in locally-created portfolios.  We are working to correct this, but in the mean time as a workaround, wait to modify the default template until after go-live.
    In rare cases, locally managed titles that are not part of any package may be activated as local standalone portfolios (not associated with any package).
    This flow is intended mainly for activating global inventory managed in the community zone. Local e-inventory (of the package, database, or standalone type) can also be created from the title tab by indicating the package name STANDALONE (the last package name in the drop-down list). However, in most cases, standalones are created from the ILS system using the P2E process, so it is important NOT to load standalones that are also present in your ILS system (to avoid unnecessary duplication). Therefore, it is strongly discouraged to use this option without first ensuring the numbers provided are limited below 5K standalone portfolios and only after first consulting with your Ex Libris project consultant.
    Field Name Notes
    PACKAGE_NAME Should match a package name from tab 3 for global packages. Alternatively, if the Title being activated is a local standalone, choose STANDALONE (the last option in the dropdown list).  If you do not have any STANDALONE packages, go to the SELECTIVE_PKG tab and set STANDALONE to N so it does not appear in the dropdown.
    PORTFOLIO_PID Will generally be left blank – the internal PID # used in the community zone for this portfolio in Alma. This ID can only be determined by searching the community zone, opening the relevant community e-collection’s portfolio list within the community zone, and running an extended export as Excel.
    This is not to be confused with the institutional level portfolio PID (via institution-level search results instead of the Community-level results), which is activated in your institution, is not persistent, and is ignored.
    (Either Portfolio ID, ISSN, or ISBN are mandatory)
    ISSN  ISSN identifier (requires at least one Portfolio ID, ISSN, or ISBN). Note: more than one ISSN column value may be passed in the three available ISSN fields, if desired. This is intended in cases where more than one ISSN (for instance E-ISSN) exists.  Do not provide multiple ISSNs in the same field - they must be provided individually in the separate fields. If you provide a number with hyphens or other punctuation, it will be removed in order to find a match.
    ISBN ISBN identifier (Either Portfolio ID, ISSN or ISBN are mandatory). Note: more than one ISBN column value may be passed, if desired. This is intended in cases where more than one ISBN (for instance E-ISBN) exists. Do not provide multiple ISBNs in the same field - they must be provided individually in the separate fields. If you provide a number with hyphens or other punctuation, it will be removed in order to find a match.
    All fields are below are used if the portfolio being loaded is:
    • A local standalone portfolio – not linked to any package. Standalone portfolios require an identifier (ISBN/ISSN) along with Title, URL, and coverage.
    • A local portfolio linked to a global package.

     

    If the portfolio is CZ-linked, meaning a match was found, then the only fields which are added to the CZ-linked portfolio are: 

    FROM_*

    TO_*

    EMBARGO_* 

     

    TITLE The 245 |a to apply to this title. Will only be used if the title is local.
    PUBLISHER Free Text
    AUTHOR Free Text
    URL

    Linking URL: this is used as a match point to try to identify a CZ resource.  If a match is found in some other way, this URL is not used. This URL is only loaded to Alma for local (newly-added) portfolios.

    The migration programs use the Authoritative URL as the URL described above; Output URL is an ezproxy link and is not used.

    The FROM_*, TO_*, and EMBARGO_* fields below are placed in the "Local Coverage" fields in Alma.   Use these fields only if your coverage is different from the default (global) coverage.  If there is no local coverage, then the portfolio displays the global coverage which is inherited from the CZ.
    FROM_YEAR The YYYY coverage start date of the title.  
    FROM_MONTH The MM coverage start month of the title (used with FROM_YEAR).  Single digit month is acceptable, so 1 or 01 is fine.
    FROM_DAY The DD coverage start day (used with FROM_YEAR and FROM_MONTH).  Single digit day is acceptable, so 1 or 01 is fine.
    TO_YEAR The YYYY coverage end date of the title. Words like 'Present' not accepted.  If the content is currently received, leave this column blank.
    TO_MONTH The MM coverage end month of the title (used with FROM_YEAR). Words like 'Present' not accepted.  If the content is currently received, leave this column blank. Single digit month is acceptable, so 1 or 01 is fine.
    TO_DAY The DD coverage end day (used with FROM_YEAR and FROM_MONTH). Words like 'Present' not accepted.  If the content is currently received, leave this column blank. Single digit day is acceptable, so 1 or 01 is fine.
    FROM_VOLUME The numeric volume number of when the title coverage begins
    TO_VOLUME The numeric volume number of when the title coverage ends. Words like 'Present' not accepted.  If the content is currently received, leave this column blank.
    FROM_ISSUE The numeric issue number of when the title coverage starts
    TO_ISSUE The numeric issue number of when the title coverage ends. Words like 'Present' not accepted.  If the content is currently received, leave this column blank.
    EMBARGO_OPERATOR

    permitted values: >,>=, <,<= 

    Note: If EMBARGO_OPERATOR is filled, then either EMBARGO_YEARS or EMBARGO_MONTHS must be filled (one or the other).  Also, the opposite is true: if EMBARGO_YEARS or EMBARGO_MONTHS are filled, then you must use the EMBARGO_OPERATOR.

    EMBARGO_YEARS possible value: positive integer number.  
    EMBARGO_MONTHS possible value: positive integer number.  
    PUBLICATION_DATE_OPERATOR These PUBLICATION* fields are not used by the loader.  ExL is in the process of removing them for a future release.
    PUBLICATION_DATE_YEAR
    PUBLICATION_DATE_MONTH
    ELECTRONIC_MATERIAL_TYPE Acceptable values:
    BOOK
    JOURNAL
    DISSERTATION
    PROCEEDING
    CONFERENCE
    REPORT
    DOCUMENT
    SERIES
    NEWSPAPER
    TRANSCRIPT
    DATABASE
    WIRE
    CDROM
    MANUSCRIPT
    RECORD
    MAP
    OTHERVM
    SCORE
    AVAILABILITY ACTIVE or INACTIVE.  This is case sensitive, so 'Active' is not accepted.
    NOTES Placed in a general note in the portfolio

     

    Post-Migration Manual Steps, If Necessary

    Add Local Packages

    If any non-global packages need to be reflected in Alma, they can be added using standard Alma tools from the Resource Management > Create Inventory > Add Electronic Collection wizard.
    If additional portfolio titles need to be loaded (if, for instance, one or more were missed during the initial load), see Managing Electronic Collections for more information on the above process and format. This step may also be performed on production, if necessary.

    Set Up Special Institution-Specific Package Access Parameters

    The are some packages where you need to manually set the institution-specific linking parameters. This step must be performed manually, post-migration, from each relevant package.   There is a spreadsheet that customers can use to gather the necessary information, the Special Parameters for Link Resolver.   For information on these special packages, see the Alma documentation at https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/050Inventory/020Managing_Electronic_Resources

    Report of Loader Events

    A report of the events which took place during the E-Resource load is available upon request.  This report is usually very large, and many entries are purely informational.  However, it may be useful to review.  
    • Was this article helpful?