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

    ERM to Alma Data Delivery Specification

    This document describes the migration process for non-Ex Libris ERM systems. Customers with non-Ex Libris ERMs who have purchased the migration add-on must develop their own conversion programs and validate their files against Ex Libris’ XSDs for ERM (generic) migration. The valid files can then be processed and loaded to Alma by Ex Libris. For information on how electronic resources are migrated from 360 and Intota, see the 360 and Intota to Alma Migration Guide. For information on how electronic resources are migrated from Verde, see the Verde to Alma Migration Guide.
    Before the migration from your local ERM can occur, all electronic inventory must be represented in SFX or your current ILS system. If the data from SFX is represented in your local ERM it must be active.  
    If you have e-products of type standalone, package or constituent that are not represented in SFX or are in SFX but are not active, they must be represented by a bibliographic record in the ILS system.
    The potential scope is separated into three main areas:
    • Licenses
    • Interfaces (Vendor-level administrative and access information)
    • E-inventory fields and linking
    Identify which electronic inventory record (and in some cases which order record) to enrich with ERM data. This will be done by populating an Excel sheet which contains relevant ERM e-product and related e-product fields (one e-product is listed per row). The enrichment process includes the following:
    • Linking the license to e-product
    • Linking the interface to e-product
    • Enriching the e-product with ERM e-product fields
    • Enriching ILS-originated orders with ERM Acquisition record fields (or e-inventory record fields if the order is not ILS-originated). There may be some local attributes configured in the e-product and acquisition fields (for example, non-CKB/global attributes) in your ERM.
    Relevant e-products for which information migrates include the following:
    • Packages
    • Portfolios (standalone)
    • Databases
    It is not recommended to provide ERM enrichment information for large amounts of portfolios that are part of a package or managed as a group in an e-collection. If the ILS has bibliographic records for individual portfolios that are part of a larger package, it is recommended to start managing these resources at the package level in Alma, rather than the portfolio level. Post-migration, you can associate the standalone portfolios that were created as a result of the p2e process with the package (local e-collection) in Alma. The advantages of managing resources at the package level are that any information about the package that changes will affect all resources, such as license and access information. You need only manage this information once at the package level instead of multiple times at the portfolio level.
    Ex Libris migrates your acquisitions data only if this service was purchased by your institution and is stipulated in your contract with Ex Libris.

    Licenses

    Licenses are implemented in Alma using the DLF-ERMI standard. The exchange format between your current ERM system licenses and Alma is via an XML format. Each license record is represented by a single output XML file and must be validated according to the data definition defined by Ex Libris.
    The output XML files provided must be validated according to the ERM License XSD.
    The following is the general structure of the license XML:
    • License details (core license attributes such as license code, start date, and vendor)
      The license code is the link between e-inventory and the license
    • Terms (the DLF-ERMI terms which represent the license terms) – non-repeatable
      Alma supports a fixed list of license terms, as listed in the XSD. The type of enumeration for the license terms is listed below in the License Terms and Types table.
    • Notes (repeatable)
    •  
    • License attachments (optional designation of related file attachments for the license)

    License attachments should be provided in a separate directory called 'attachments', on the same level as the license XMLs.  If the file names for the attachments overlap, the files can be placed in subdirectories under the attachments directory, for example 1/, 2/, etc.  The files and directories can be zipped in one large file or many files. In the license xml, include the full path of the file relative to the attachments directory, like <p:filename>1/APA_Local_Load_License_2012.pdf</p:filename>

    When a license is migrated to Alma, any vendor it lists is marked as a licensor. This makes it available to be a licensor for other licenses in Alma.

    License Terms and Types

    In the following table, the enumeration type is one of the following.
    • LicenseTermsYesNo = Yes, No
    • LicenseTermsPermittedProhibited = Prohibited, Permitted, Silent
    • LicenseTermsUOM = CALENDARDAY, BUSINESSDAY, WEEK or free text
    • FREE-TEXT = note field
    License Term License Term Code Type of Enumeration

    Accessibility Compliance Indicator

    ACCESSIBILITY

    LicenseTermsYesNo

    All Rights Reserved Indicator

    ALLRIGHTS

    LicenseTermsYesNo

    Applicable Copyright Law

    APPCLAW

    FREE-TEXT

    Archiving Right

    ARCHIVE

    LicenseTermsYesNo

    Archiving Format

    ARCHIVEFMT

    FREE-TEXT

    Archiving Note

    ARCHIVEN

    FREE-TEXT

    Authorized Users

    AUTHUSERDEF

    FREE-TEXT

    Citation Requirement Detail

    CITREQD

    FREE-TEXT

    Clickwrap Modification Clause Indicator

    CLICKWRAPI

    LicenseTermsYesNo

    Completeness of Content Clause Indicator

    COMPLETENESSI

    LicenseTermsYesNo

    Concurrency with Print Version Clause Indicator

    CONCURRPRINTI

    LicenseTermsYesNo

    Concurrent Users

    CONCURUSER

    FREE-TEXT

    Concurrent Users Note

    CONCURUSERN

    FREE-TEXT

    Confidentiality of Agreement

    CONFA

    FREE-TEXT

    Confidentiality of Agreement Note

    CONFAN

    FREE-TEXT

    Confidentiality of User Information Indicator

    CONFUSERI

    LicenseTermsYesNo

    Consortial Agreement Indicator

    CONSORTIALAGREEMENT

    LicenseTermsYesNo

    Content Warranty

    CONTWARR

    FREE-TEXT

    Course Pack Electronic

    COURSEPACKELEC

    LicenseTermsPermittedProhibited

    Course Pack Note

    COURSEPACKN

    FREE-TEXT

    Course Pack Print

    COURSEPACKPRINT

    LicenseTermsPermittedProhibited

    Course Reserve

    COURSERES

    LicenseTermsPermittedProhibited

    Course Reserve Note

    COURSERESNOTE

    FREE-TEXT

    Course Reserve Print

    COURSERESPRINT 

    LicenseTermsPermittedProhibited

    Cure Period for Breach (Number)

    CUREBREACH

    FREE-TEXT

    Cure Period for Breach (Unit)

    CUREBREACHUOM

    LicenseTermsUOM

    Database Protection Override Clause Indicator

    DATAPROTOVERC

    LicenseTermsYesNo

    Digitally Copy

    DIGCOPY

    LicenseTermsPermittedProhibited

    Digitally Copy Note

    DIGCOPYN

    FREE-TEXT

    Distance Learning

    DISTANCE

    LicenseTermsPermittedProhibited

    Distance Learning Note

    DISTANCEN

    FREE-TEXT

    Electronic Link

    ELECLINK

    LicenseTermsPermittedProhibited

    Electronic Link Note

    ELECLINKNOTE

    FREE-TEXT

    Fair Use Clause Indicator

    FAIRUSE

    LicenseTermsYesNo

    Governing Jurisdiction

    GOVJUR

    FREE-TEXT

    Governing Law

    GOVLAW

    FREE-TEXT

    ILL Electronic (email)

    ILLELEC

    LicenseTermsPermittedProhibited

    ILL Record Keeping Note

    ILLN

    FREE-TEXT

    ILL General

    ILLPRINTFAX

    LicenseTermsPermittedProhibited

    ILL Record Keeping

    ILLRKRI

    LicenseTermsYesNo

    ILL Secure Electronic

    ILLSET

    LicenseTermsPermittedProhibited

    Incorporation of Images Figures and Tables Note

    IMAGESNOTE

    FREE-TEXT

    Incorporation of Images Figures and Tables Right

    IMAGESRIGHT

    LicenseTermsPermittedProhibited

    Indemnification by Licensee Clause

    INDEMLEEC

    FREE-TEXT

    Indemnification by Licensor Clause

    INDEMLORC

    FREE-TEXT

    Indemnification Note

    INDEMN

    FREE-TEXT

    Intellectual Property Warranty Indicator

    IPWARRI

    LicenseTermsYesNo

    License Replaced By

    LICENSREPLACEDBY

    FREE-TEXT

    License Replaces

    LICENSEREPLACES

    FREE-TEXT

    Licenses Reviewer Note

    LICENSEREVIEWERNOTE

    FREE-TEXT

    Local Authorized Users 

    LAUTHUSERDEF

    FREE-TEXT

    Licensee Notice Period for Termination (Number)

    LEENOTICE

    FREE-TEXT

    Licensee Notice Period for Termination (Unit)

    LEENOTICEUOM

    LicenseTermsUOM

    Licensee Termination Condition

    LEETERMCON

    FREE-TEXT

    Licensee Termination Right

    LEETERMRIGHT

    LicenseTermsYesNo

    Licensor Notice Period for Termination (Number)

    LORNOTICE

    FREE-TEXT

    Licensor Notice Period for Termination (Unit)

    LORNOTICEUOM

    LicenseTermsUOM

    Licensor Termination Condition

    LORTERMCON

    FREE-TEXT

    Licensor Termination Right

    LORTERMRIGHT

    FREE-TEXT

    Maintenance Window

    MAINTWIN

    FREE-TEXT

    Non-Renewal Notice Period (Number)

    NONRNOTICE

    FREE-TEXT

    Non-Renewal Notice Period (Unit)

    NONRNOTICEUOM

    LicenseTermsUOM

    Other User Restriction

    OTHERUSERRSTRN

    FREE-TEXT

    Other Use Restrictions (Staff Note)

    OTHERUSERSTRN

    FREE-TEXT

    Performance Warranty Indicator

    PERFWARRIND

    LicenseTermsYesNo

    Performance Warranty Uptime Guarantee

    PERWARRUPTIME

    FREE-TEXT

    Perpetual Access Right

    PERPETUAL

    LicenseTermsYesNo

    Perpetual Access Holdings

    PERPETUALH

    FREE-TEXT

    Perpetual Access Note

    PERPETUALN

    FREE-TEXT

    Pooled Concurrent Users

    PCONCURUSER

    NUMERIC

    Print Copy

    PRINTCOPY

    LicenseTermsPermittedProhibited

    Print Copy Note

    PRINTCOPYN

    FREE-TEXT

    Remote Access

    REMOTE

    LicenseTermsYesNo

    Renewal Type

    RENEWTYPE

    FREE-TEXT

    Scholarly Sharing

    SCHOLSHARE

    LicenseTermsPermittedProhibited

    Scholarly Sharing Note

    SCHOLSHAREN

    FREE-TEXT

    Termination Requirements

    TERMREQS

    FREE-TEXT

    Termination Requirements Note

    TERMREQSN

    FREE-TEXT

    Termination Right Note

    TERMRIGHTN

    FREE-TEXT

    UCITA Override Clause Indicator

    UCITAOVERI

    LicenseTermsYesNo

    Usage Data Set Up Status

    USAGEDATASETUPSTATUS

    FREE-TEXT

    Walk-In User Term Note

    WALKIN

    FREE-TEXT

     

    If you cannot find a license term type, it is possible to add a new one.  For more information, see Managing License Term Types.  You can add the new term before or after loading the xml.

    Interfaces (Vendor Access/Admin Data)

    It is not recommended to provide interface records if your admin, access, and/or statistical information is e-inventory (package or portfolio) specific, since Alma’s design intends the interface record to be encompassing across all packages and constituents it serves. In such cases, it is recommended instead to provide additional e-inventory level notes via the E-inventory fields and linking Excel file noted in E-inventory Fields and Linking.
    If you have a resource that is in the Alma CZ but you have localized it in some way, you may provide local interface information here in the interface stanza.
    When an interface is migrated to Alma, it and all of its related field information is linked to a vendor in Alma. The vendor is then marked as an access provider, which makes it available for use by packages or standalone portfolios.
    Interfaces are implemented in Alma as a vendor sub-attribute. The exchange format between your current ERM system interfaces and Alma is via an XML format. Each vendor record is represented by a single output xml file. One or more interface records may be represented in each vendor XML file provided. These XML files must be validated according to the data definition defined by Ex Libris.
    The output XML files provided must be validated according to the Vendor Interface XSD.
    The following is the structure of the vendor interface XML:
    • Vendor / Vendor account details (core vendor/vendor account attributes such as codes and names)
      The vendor code is mandatory. It is used to match the vendor code loaded from your ILS. If the vendor codes match, the details from the vendor are ignored, and ONLY the interface section is added to Alma. If the vendor code does not match any ILS vendor code, the vendor information is loaded. In this case, the vendor account is also mandatory.
    • Contact information/Contact persons - Optional
      Do not enter valid email addresses for vendors during the testing period to prevent emails from being sent to the vendors. Common practice is to put the word SCRUBBED in the email address, for example, vendor.name@SCRUBBED_vendor.com.
    • Interface list (one or more interfaces)
      The interface name is the match key to match e- inventory to your vendor interface records. Each specific interface name must be unique across ALL interface names in your institution.
    • Admin fields
    • Access fields
    • Statistics fields
    • Notes (repeatable)

    E-inventory Fields and Linking

    ERM fields and inventory linking are moved to Alma via an Excel exchange format from your current ERM system. Each inventory record is represented by a single row in the output Excel representing the relevant linking / field information. Best practice dictates that a row be provided only if the specific inventory record has its own unique information. For example, a license related to a package whose constituents inherit this license reference is not considered unique information for the portfolio constituent and is not a sufficient reason to add the portfolio constituent line in the Excel. Also, you may decide to omit specific fields of an e-product if those fields already exist elsewhere, even if the rest of the e-product information is migrated.
    A sample ERM linking form is provided from the Alma Migration Guides main page.  The form should contain all fields, even if they are empty.  Meaning, even if you are only providing information for 4 or 5 different fields, you cannot only provide those fields. Provide all fields, and leave empty the ones you do not want to use.
    The process enriches relevant Alma e-inventory records with relevant fields and related license information, and optionally enriches po_line information. In addition, it creates license related notes. Each Excel row line specifies matching criteria for an e-inventory record and optional po_line record.

    In the following table

    • The Alma note records linked to e-inventory become Inventory notes
    • The Alma note records linked to po_lines become Poline notes.
    Matching Algorithm

    If Excel.match_id is equal to sfx_id (non case sensivite) – use SFX Matching algorithm. 

    If the E-INVENTORY record is not found - use PO Matching algorithm.

    If the E-INVENTORY record is not found – use ILS Matching algorithm.

    If Excel.match_id is equal to po_id or poline_id (not case sensitive) – use PO Matching algorithm.
    If the E-INVENTORY record is not found – use ILS Matching algorithm.

    If Excel.match_id is equal to ils_bib_id (not case sensitive) – use ILS Matching algorithm.
     

    Fields

    Field name Description Alma location
    match_id

    MANDATORY
    Enum:  sfx_id,poline_id po_id,ils_bib_id, non_sfx_id (At least one of the five keys are mandatory to match the match_id)

    This represents the e-inventory id which will be enriched. That e-inventory may have originated in your SFX system or in your ILS system. If it originated in your ILS system, it may be determined via an order referencing that e-inventory or directly via a Bibliographic id.  The non_sfx_id is the Alma resource ID. 

     
    sfx_id

    Used by SFX Matching Algorithm. 

    ID from SFX (Target ID for Packages/E-collections or Portfolio ID for Portfolios);  Should be equal to the E-INVENTORY ORIGINATING_SYSTEM_ID for an sfx record.  If Poline is matched, the Process creates Poline note with text: “ERM Linking SFX orig id = <sfx_id>”

    Shoud be equal to HDEMETADATA.ORIGINATING_SYSTEM_ID for an sfx record. 
    poline_id Used by PO Matching Algorithm. Should be equal to PO_LINE.PO_LINE_REFERENCE.
    If poline_id is not empty, the process creates an Inventory note with text: “ERM Linking PO Line Ref = <poline_id>”
    The poline_id is stored in the E-INVENTORY POLINEID attribute
    This is the primary orderid to which the relevant information will be mapped. associated_po lines if provided will be related to the primary one.The primary should be considered the most recent open order.

    PO_LINE.PO_LINE_REFERENCE: This is the PO Line Number in PO Line screens: PO Line details

    po_id If provided, will match PO.PO_NUMBER and will automatically determine this order's electronic PO_LINE. Do not use if poline_id is provided. Should be equal to PO.PO_NUMBER 
    If po_id is not empty, the loader creates an Inventory note  with text: “"ERM Linking PO Num = <po_id>”  This is the PO  Number in PO Line that were packed: 
    PO Line details - PO number
    ils_bib_id

    Only relevant if no sfx_id (or poline_id/po_id) was provided

    This is the bib ID from your incoming ILS.

    Should be equal to MMS_RECORD.ORIGINATION_SYSTEM_ID

    PO Line list >> MMS_ID

    resource_type

    MANDATORY.  Possible values:   PACKAGE, DATABASE, PORTFOLIO

    This is used for:

    1. determining if the resource is a package or portfolio along with sfx_id
    or
    2. determining if the resource is a DATABASE, in case the resource did not have an sfx_id, and instead an ils_bib_id was provided.

    When resource_type = PORTFOLIO, add '99' to the beginning of the sfx_id.

    when resource_type = PACKAGE, add '61' to the beginning of the sfx_id.

    associated_poline_id Will match the PO_LINE_REFERENCE in Alma

    Multiple associated_poline_ids may be passed with comma separation and will relate to the primary poline_id. 
     
    associated_po_id Will match PO.PO_NUMBER and will automatically determine this order's electronic POL witihn Alma. Do not use if asociated_poline_id was populated.  
    interface_id Interface name from Alma Interface List

    The interface_id is the name, for example 'ACM Digital Library'
    If matched E-INVENTORY is an e-collection/package , store interface_id in Package.INTERFACEPUBLICNAME;
    If matched E-INVENTORY is of type PORTFOLIO, store interface_id in Package.VENDORNAME of corresponding e-collection/package record.
    license_id Matches the LICENSE.CODE in Alma

    The process looks for Alma LICENSE where LICENSE.CODE = excel.license_id
    If found:
     if matching E-INVENTORY is  E-Collection/Package – store Alma LICENSE.ID as Package.LICENSEID; store <start_date> as Package.LICENSESTARTDATE
      if Alma LICENSE.LICENSE_BEGINS is defined use it as <start_date>,  otherwise use current data as <start_date>
      if matching E-INVENTORY is PORTFOLIO  - store Alma LICENSE.ID as  Portfolio.LICENSEID; store <start_date>  Portfolio.LICENSESTARTDATE;


     License details >> Start date

    original_resource_id For potential matches in future - the key used to match the e-inventory in the ERM system. If original_resource_id is not empty:
    Inventory note is created with content “ERM Linking original resource id = <original_resource_id>”
    If Poline is matched, Poline note is created with content “ERM Linking original resource id = <original_resource_id>”
    pol_subscr_start_date Subscription start date for E-subscription orders in format: YYYYMMDD

    If PO_LINE record is matched,
      The process stores pol_subscr_start_date in PO_LINE.  SUBSCRIPTION_FROM_DATE,
    otherwise Inventory Note with text: “pol_subscr_start_date:<the column content>” is created.

    This is the Subscription from date in Continuous PO Lines screen:PO Line details >> Summary tab >> Subscription from date

    pol_subscr_end_date Subscription end date for E-subscription orders in format: YYYYMMDD
    Important note: Filling this field and providing a pol_id or po_id will set the actual order subscription end date. In Alma, this field will cause automatic closure of the order when passed.

    If PO_LINE record is matched,
      The process stores pol_subscr_end_date in PO_LINE.  SUBSCRIPTION_END_DATE,
    otherwise Inventory Note with text: “pol_subscr_end_date:<the column content>” is created.

    This is the Subscription to date in Continuous PO Lines screen:PO Line details >> Summary tab >> Subscription to date

    pol_renewal_date Next date to renew the E-subscription in format: YYYYMMDD

    If PO_LINE record is matched,
    the process stores pol_renewal_date in PO_LINE. RENEWAL_DATE,
    otherwise Inventory Note with text: “pol_renewal_date:<the column content>” is created.

    This is the renewal date in Continuous PO Lines screen:PO Line details >> Summary tab >> Renewal date

    pol_renewal_reminder Numeric (days). The number of days before which the order, if matched, will appear in Alma's renewal task list.

    If PO_LINE record is matched,
      the process stores pol_renewal_reminder in PO_LINE. RENEWAL_REMINDER_PERIOD,
    otherwise Inventory Note with text: “pol_renewal_reminder:<the column content>” is created.

    This is the Renewal reminder period (days) in Continuous PO Lines screen:PO Line details >> Summary tab >>  Renewal reminder period (days)

    vendor_reference_number Text

    If PO_LINE record is matched,
      The process stores pol_renewal_date in PO_LINE. VENDOR_REFERENCE_NUMBER,
    otherwise Inventory Note with text: “vendor_reference_number:<the column content>” is created.

    This is the  Vendor reference number in PO Lines screen:PO Line details >> Summary tab >>   Vendor reference number

    pol_note_code_1 Text  
    pol_note_value_1 Text  
    pol_note_code_x and pol_note_value_x up through 200 Up to 200 pairs of columns pol_note_code_<num>, pol_note_value_<num> can be defined.
    For each pair of pol_node_code_<num>, pol_node_value_<num> columns:
    If PO_LINE record is matched, Poline note is created with content
    <CODE>:<VALUE> where <CODE> comes from pol_note_code_<num> and <VALUE> comes from pol_note_value_<num>
    If PO_LINE record is not matched, Inventory note with the same text is created.
     
    inv_note_code_1 Text  
    inv_note_value_1 Text  
    inv_note_code_x and inv_note_value_x up though 200 Up to 200 pairs of columns inv_note_code_<num>, inv_note_value_<num> can be defined.
    For each pair of inv_node_code_<num>, inv_node_value_<num> columns:
    Inventory note is created with content
    <CODE>:<VALUE> where <CODE> comes from inv_note_code_<num> and <VALUE> comes from inv_note_value_<num>.
     
    aggregator Enum: 0, 1
    (0 = Selective,1 = Aggregator)
    Only relevant for non-SFX packages
    Stored in Package.AGGREGATOR. Not visible in Acq
    active (not processed)  
    db_source Text
    Used in conjunction with db_source_id

    Stored in Package.SOURCE

    Not visible in Acq

    db_source_id Text
    Used in conjunction with db_source

    Stored in PackageEntityIECKB.SOURCEID

    Not visible in Acq

    id_type Text

    Stored in InternalIdentifier.INTERNALIDENTIFIERTYPE

    Not visible in Acq

    id_value Text

    Stored in InternalIdentifier.INTERNALIDENTIFIERVALUE

    Not visible in Acq

    is_free Boolean
    Only relevant for non-SFX e-products

    Stored in Package.ISFREE

    Not visible in Acq

    embargo_operator ENUM: &lt/&gt
    Only relevant for non-SFX e-products

    Stored in MovingwallInventory.OPERATOR

    Not visible in Acq

    embargo_month Numeric (# of months)
    Only relevant for non-SFX e-products

    Stored in MovingwallInventory.MONTH

    Not visible in Acq

     

    coverage_from_year Numeric (YYYY)
    Only relevant for non-SFX e-products

    Stored in DateInfoInventory.FROMYEAR

    Not visible in Acq

    coverage_from_month Numeric (MM)
    Only relevant for non-SFX e-products
     
    coverage_from_day Numeric (DD)
    Only relevant for non-SFX e-products
     
    coverage_to_year Numeric (YYYY)
    Only relevant for non-SFX e-products

    Stored in DateInfoInventory.TOYEAR

    Not visible in Acq

    coverage_to_month Numeric (MM)
    Only relevant for non-SFX e-products
     
    coverage_to_day Numeric (DD)
    Only relevant for non-SFX e-products
     
    coverage_from_vol Numeric
    Only relevant for non-SFX e-products

    Stored in DateInfoInventory.FROMVOLUME

    Not visible in Acq

    coverage_to_vol Numeric
    Only relevant for non-SFX e-products

    Stored in DateInfoInventory.TOVOLUME

    Not visible in Acq

    coverage_from_issue Numeric
    Only relevant for non-SFX e-products

    Stored in DateInfoInventory.FROMISSUE

    Not visible in Acq

    coverage_to_issue Numeric
    Only relevant for non-SFX e-products

    Stored in DateInfoInventory.TOISSUE

    Not visible in Acq

    public_note Text

    if matched E-INVENTORY is E-COLLECTION (PACKAGE or DATABASE)
      stored in Package.PUBLICNOTE;
    if matched E-INVENTORY is PORTFOLIO 
     store in  Portfolio.GENERALNOTE;

    Not visible in Acq

    cancellation_restriction Text If PO_LINE is matched
      If the column contains yes (case ignored) – set PO_LINE.CANCEL_RESTRICTION to true
      If the column contains no (case ignored) – set
    PO_LINE.CANCEL_RESTRICTION to false
    cancellation_restriction_note Text

    If PO_LINE is matched
      Stored in PO_LINE.CANCEL_RESTRICTION_NOTE

    This is the  Cancellation restriction note in PO Lines screen: PO Line details >> Summary tab >>   Cancellation restriction note

    access_type Text If matched E-INVENTORY is of type E-COLLECTION (PACKAGE or DATABASE)) and access_type is not empty:
      if access_type is "perpetual" (ignore case)
            store “perpetual” in  PackageEntityIEInventory.ACCESSTYPE
          else store “current” in  PackageEntityIEInventory.ACCESSTYPE
             add PackageEntityIEInventory.ACCESSTYPE = "current"
    cross_ref Boolean
    Only relevant for non-SFX e-products

    Stored in Dnx.PackageEntityServiceInventory.CROSSREFENABLED

    Not visible in Acq

    activate_from YYYYMMDD
    Only relevant for non-SFX e-products

    Stored in Dnx.PackageEntityServiceInventory.ACTIVATEFROM

    Not visible in Acq

    activate_to YYYYMMDD
    Only relevant for non-SFX e-products

    Stored in Dnx.PackageEntityServiceInventory.ACTIVATETO

    Not visible in Acq

    auto_active Boolean
    Only relevant for non-SFX e-products

    Stored in Dnx.PackageEntityServiceInventory.AUTOACTIVE

    Not visible in Acq

    service_down_reason Text

    Stored in Dnx.PackageEntityServiceInventory.SITEDOWNREASON

    Not visible in Acq

    FTP Drop Point Delivery and Form

    Each time data files are provided to Ex Libris in the formats indicated in the specification section above, place them on the MFT server specified to you by your Ex Libris project manager.
    The following is the default naming convention:
    CustomerName+DataType+sequence+date+[.<file_extension>].
    For example: centralu_bib_01_20200420.mrc, centralu_bib_02_20200420.mrc, centralu_bib_03_20200420.mrc, etc.
    Additionally, provide the 360 and Intota Migration Form along with your data.
    • Was this article helpful?