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

    WMS (OCLC) to Alma Data Delivery Specifications

    This migration document is intended to be used by customers who are coming from the World Management Share (WMS) integrated library system, developed by OCLC.  Customers are expected to provide extracts for their inventory and fulfillment data directly from OCLC WMS, and map them into the expected fields using this guide and the WMS (OCLC) Field Mapping form.
    The procedure for migrating from WMS to Ex Libris’ Alma consists of the following steps:
    1. Indicate which local fields correspond to Ex Libris' expected fields using the WMS (OCLC) Field Mapping form, prior to data delivery (customer responsibility).
    2. Validate the flat files using Non-Ex Libris to Alma Validation Tool Excel. It is recommended that this step be done against a small sub-set of data to ensure that the header of each of your flat files and the filled in WMS (OCLC) Field Mapping form match each other.
    3. Extract the relevant data elements from WMS into flat files (customer responsibility).
    4. Upload the files to Ex Libris’ FTP server along with the WMS (OCLC) Delivered Files List and the executed/validated Non-Ex Libris to Alma Validation Tool (customer responsibility).
    5. Transform the data elements, based on the Field Mapping form, into an intermediate conversion XML format (Ex Libris responsibility).
    6. Load the transformed data into Alma (Ex Libris responsibility).
    Deliver the WMS (OCLC) Field Mapping Form and validated data validation output form to Ex Libris along with the WMS (OCLC) Migration Form prior to the actual delivery of the data. The lead time depends on your project schedule. Provide the WMS (OCLC) Delivered Files form, which lists the file names and the record counts for each file, at the same time that you provide your data extract files.
    Provide the data elements in flat files, and place them on an Ex Libris FTP server. Prepare the data files in the exact format as specified in Appendix A – FTP Drop Point Delivery and Delivered Files Form with the naming conventions as described there.

    Files Requested from your ILS

    Ex Libris expects a certain set of files to be exported from the incoming ILS, listed below. As files are extracted, be sure that the extracted file description, such as data elements and lengths, matches the description in Expected File Formats.
    The data elements listed are those that Ex Libris expects to use in conversion. Not all data elements that exist in WMS are necessary to transfer to Alma.
    The scope of your specific conversion is agreed upon in your Alma contract.
    • As you extract data from any area listed below, provide it to Ex Libris via an FTP connection. This facilitates the transformation analysis and expedites the conversion process. For FTP delivery instructions, see Appendix A – FTP Drop Point Delivery and Delivered Files Form.
    • DO NOT OPEN/UPDATE any delimited file extracts you provide to Ex Libris in Excel. This may ruin the appropriate delimiter formatting and text formatting and may result in corrupted data.

    Expected File Formats

    All the files listed in the tables below are expected in CSV format with one record per line, and fields delimited by commas and multi-values within fields delimited by semicolons. The following is an example of a record with multiple values for the third field:
    “field1”,”field2”,”field3a”;”field3b”,”field4”
    The following are the only exceptions to this expected format:
    • Bibliographic records (which are MARC standard files)
    • MARC Holdings records

    For all files, the maximum file size is 2GB.

    WMS (OCLC) Field Mapping Form

    Prior to submitting your extracted files, complete the OCLC (WMS) Field Mapping form. Indicate which data elements (files) you plan to provide in the Overview tab of the spreadsheet. On the subsequent tabs, indicate your local field names and how they map to Alma's expected field names.
    On all of the tabs in the form, there is a ##Foreign Key## column. Customers should not fill out this column – it is for internal use only.
    In addition, there are various note fields for each data element. Fields that are not expected by Ex Libris (because there is no functional place for the data element in the corresponding Alma data structure) can be placed in a note in the record. Specify the note type that you want the field to go to at the bottom of each tab in the form.

    WMS (OCLC) Delivered Files Form

    At the time you submit the requested data files, submit the completed Excel spreadsheet WMS (OCLC) Delivered FIles form. List the files, record counts, and encoding for each file delivered to the FTP server.  Indicate the type of encoding and bib format (for bib files).

    Inventory

    Bibliographic Records

    Bibliographic records are expected in MARC, UNIMARC or KORMARC format. Binary MARC, UNIMARC or KORMARC is preferred, but Ex Libris also accepts files in MARCXML, UNIMARCXML or KORMARCXMLformat as well. The character encoding expected is UTF-8 (preferred) or ANSEL/MARC8. If your library prefers to export in a different format, inform your Ex Libris project manager. All files should be delivered with the same character encoding.
    Each Bibliographic record MUST have a single unique source key/identifier in a consistent single source MARC/UNIMARC/KORMARC field, which is specified on the Bib tab of the Field mapping form. Records which do not conform will be rejected.
    The following sections explain additional bibliographic use-cases which are supported.

    Suppressed Records

    Suppressed records are those bibliographic records that you want to have in the database, but not show to the public. Examples of this are:
    • titles on order
    • missing or damaged titles where you want to keep the record but not show it to the public
    • titles that are for internal management only, such as equipment
    Provide a text file that contains the source BIB key/ID, one key per line, for bibliographic records that are suppressed.

    Boundwiths

    WMS does not have functionality to maintain boundwith items, but some libraries may have reports from their previous systems which show boundwith relationships.  In this case, the customer may modify their reports from the previous system and put them into the following format.

    Examples of boundwiths:

    • Bound journals with a title change in the middle of the year. For example, if January – April is “Journal of Mathematics Education” and May – December is “Mathematics Educator”, and all 12 of the issues are bound in the same volume with a single barcode.
    • Pamphlets or small volumes with similar content which were combined into the same item/barcode, either by binding or in a folder.

    Provide boundwith information in a separate file as follows:

    bib ID (host), bib ID, bib ID etc

    456,457,458,459

    In the above example, bib 456 has the shared item attached to it.  The other bib IDs in the line are bound with the shared item. Since Alma supports standard bibliographic record relationships using Marc 21/UNIMARC/KORMARC linking fields at the bib level, the migration processing associates this shared item by linking the sharing bibliographic records via the standard linking fields.  Therefore, the actual item that is shared is not necessary for migration processing.

    Linked Bibliographic Records

    If you use standard 7XX fields for linking between MARC bibliographic records (or standard linking fields for UNIMARC), they are leveraged during migration and create appropriate bibliographic-level linking in Alma.
    No exported files are necessary for this category: use the migration form, Questionnaire tab, to indicate if your bibliographic records contain linking fields.

    Electronic Link Resolver Records

    If you have SFX MARCIt bib records or equivalent electronic records in WMS that are also represented by your link resolver system, it is suggested that they be excluded from the data provided to Ex Libris to avoid unnecessary duplication with the link resolver system data. If these records are NOT removed, you will likely see a record in Alma migrated from the ILS and the same record migrated from your link resolver system, and the duplicates will have to be managed post-go live.
    An exception to this is if the records have active orders or physical inventory that are also being migrated, these records should be kept. If you choose to provide a string to indicate records to be removed/not migrated, the migration programs remove records with no attached orders or inventory and keep records with attached orders and items.
    No exported files are necessary for this category: use the Questionnaire tab of the migration form to indicate a string that will be checked in the 035 field. Example: ‘(SFX)’.

    Holding Records

    Provide MARC holdings records in a separate file from the MARC bibliographic records.  Do not send the Bibs and Holdings in an interleaved (combined) file.

    MARC Holdings 

    If MARC holdings are provided, each record MUST have a single unique source identifier in a consistent single source MARC/UNIMARC/KORMARC field as well as a valid unique bibliographic identifier in the 004 in order to link it to its correct bibliographic record. Records that do not conform are rejected.
     

    Holding Records from a Summary Statement in a Bibliographic Record

    If the customer has serial holdings which are only represented by a summary statement such as Vol. 1 (1980) – Vol. 21 (2000), these statements may be included in a tag in the bibliographic record. Use the Holdings tab of the WMS (OCLC) Field Mapping form to indicate which field and subfield contents to use for generating holdings records from summary statements embedded in the bibliographic record.  No external file is needed here: the migration program would look for the specified tag in the delivered bib record file.
    Fill in the values of the following fields in the Holdings tab of the WMS (OCLC) Field Mapping form. If the SUMM_LOC_CODE matches an existing holdings record on the same bibliographic record, even a holdings record that was generated from items attached to the same holdings record, then the summary holdings statement is attached to that holdings record, regardless of call number. In other words, the summary holdings is placed on the holdings record with the same location, even if 852_SUBFIELDS_FOR_HOL contains call number subfields for matching like bchi. If there is no existing holdings record on the bibliographic record with the same location, a new holdings record is generated.
    Holding Records from a Summary Statement in a Bibliographic Record
    Expected Field Name Value Notes
    SUMM_TAG   Five characters; tag+2 indicators. May use # as wildcard, for example, 866##
    SUMM_SUBFIELDS   Multiple subfields allowed,for example, abz. May use # to indicate all subfields.
    SUMM_CALLNO   Textual call number to be used in all newly generated holdings records, if desired.
    SUMM_LIB_SUBF   A single subfield code (like 'a') which contains a library code in local ILS format. DO NOT enter a different bib tag: the migration program searches for a subfield within the SUMM_TAG BIB tag.
    SUMM_LOC_SUBF   A single subfield code (such as a) that contains a location code in local ILS format. Do NOT enter a different bib tag: the migration program searches for a subfield within the SUMM_TAG BIB tag.
    SUMM_LIB_CODE   If SUMM_LIB_SUBF is not provided or the subfield is not found, this is used for all records as a default. Provide a library code in local ILS format.
    SUMM_LOC_CODE   If SUMM_LOC_SUBF is not provided or the subfield is not found, this is used for all records as a default. Provide a location code in local ILS format.
    SUMM_PUBLIC_NOTE_SUBF   Public note, is placed in 852 $z of the generated holding record.
    SUMM_NON_PUBLIC_NOTE_SUBF   Non-public note, is placed in 852 $x of the generated holding record.

    Item Records

    Ex Libris expects item records in CSV delimited format. Items that do not have a BIB key are not migrated.

    Serial description information from tag in holding

    Additionally, WMS stores serial description information (such as 'v. 1 no. 3 July 2017) in the holding record related to the item - not in the exported item record itself.  Therefore, Ex Libris migration programs transfer the description from the holding to the associated item when there is a barcode in the 876 $p which matches the barcode from the item.

    When an 876, 877, or 878 contains a $p with the item barcode, then one of the following will happen:

    a) if the 876/7/8 contains $3 with a description field, it will be transferred directly to the item description field.

    b) if the 876/7/8 contains $8 with a linking number, the programs will search for a related 853/4/5 and 863/4/5, and construct a description field from those paired tags for this item.

    If the item has a field 'Textual Holdings', that field is preferred over bringing the description over from the serial holding record.

    Suppressed Item Records
    All suppressed item records are migrated to Alma as regular items (not suppressed). However, specific locations can be marked as suppressed in Alma so that groups of items can be suppressed from public view.

    Item Record

    The following format is used for an item record from WMS (OCLC) in CSV format. Records should be provide one record per line, with quotes and commas. Provide a header at the top. If something is allowed to be repeatable, provide the repeated information with a semicolon.
    Dates can be in any format, but they must be consistent. Do not use YYYYMMDD and then MMDDYYYY in the same file.
    Item Record
    Expected Field Name Notes
    Holding Location use as Library in Alma Location mapping tab
    Shelving Location use as Location in Alma Location mapping tab
    Temp Shelving Location  
    Item Type use in Item Type mapping tab
    Call Number  
    Textual Holdings maps to item's Description field
    OCLC Number bib key
    Item Barcode  
    Current Status use in Item Base Status mapping tab
    Issued Count  
    Last Issued Date  
    Last Inventoried Date  
    Soft Total maps to Total In House Use
    Soft Last Date maps to Last In House Use Date
    Item Deleted Date If this field has value '---' (no date) then the item is migrated.  If there is a date present, the item is not migrated.
    LHR Item Shelving Scheme use in Shelving Sheme map
    LHR Item Copy Number  
    LHR Date Entered on File  
    REPLACEMENT_COST Place a field name here ONLY IF this will be used an actual replacement cost for a lost item in Fulfillment.
    INVENTORY_PRICE Place a field name here for information purposes about the original cost of the item.
    Any additional fields not listed above may be put into notes. The possible note fields in Alma items are listed in the following chart in the Note Name column. The fields listed in the Default Local Field column are those that are expected by Ex Libris. If you use other field names or have fields that you want to include in the migration but are not expected by Ex Libris, you can rearrange, add, or subtract fields on the right, as necessary. If you want to include multiple local fields in the same Alma note, make as many copies of the line in the spreadsheet as needed for all note name/local field combinations.
    Fulfillment notes
    For every note in the note fields PUBLIC_NOTE and the NON_PUBLIC_NOTE_N fields, the migration program will check for a ! at the beginning of the field and make it a fulfillment note.  That is, the field you put in PUBLIC_NOTE might have a mixture of regular notes and notes with '!' at the beginning.  Notes without '!' will go to PUBLIC_NOTE, and notes with '!' will go to FULFILMENT_NOTE.    Field labels are not available for fulfillment notes that are generated from notes with '!'.  If you want a field label for a fufillment note, you must provide the fulfillment note in a separate field.
    If you have a field which is entirely fulfillment notes, and these don't have '!' at the beginning, you can put that field into FULFILMENT_NOTE and every note in the field will be considered a fulfillment note.
    Note Name Default Local Field
    PUBLIC_NOTE Shows to the public
    FULFILMENT_NOTE Pops up at circulation activity.  See section on Fulfillment notes above for an explanation on how to use this field.
    NON_PUBLIC_NOTE_1 Internal notes
    NON_PUBLIC_NOTE_2  
    NON_PUBLIC_NOTE_3  
    STAT_NOTE_1 Statistical notes
    STAT_NOTE_2  
    STAT_NOTE_3  
    Secondary Item File  

    You may want to provide item descriptive information in a secondary file. The description in the format Vol. 12 No. 2 (2015 January) is used for display purposes, and not for sorting purposes.  In order to sort items by enumeration and chronology fields, the enumeration and chronology must be stored in separate fields, without labels.  Most previous ILS systems do not provide enum/chron in separate fields, but if you wish to do so you can with the secondary item file.

    Provide the secondary item file in csv format, with the following fields:

    Expected Field Name Notes
    item_key Provide either itemKey or itemBarcode, but not both. If both are provided, itemKey is preferred.
    barcode
    description Provide in a format such as: Vol. 12, No. 6 (February 2015).
    enumA For example, “12”.
    enumB For example, "6".
    enumC  
    enumD  
    enumE  
    enumF  
    enumG  
    enumH  
    chronI For example, "2015".
    chronJ For example, "2".  Do not use words, like 'February' - use numbers.
    chronK  
    chronL  
    chronM  

    E-Resources Indication (P2E)

    Provide a list of bibliographic system numbers that represent electronic resources and an indication if these electronic resources are portfolios, packages, or database resources. Prepare the list as a comma separated text file containing lines that represent each e-resource. Structure each line as follows:
    <bibnumber>,<resource type>
    For example:
    b000000001,Portfolio
    b000000002,DB
    b000000003,Package
    Note that the words portfolio, package, and db are not case-sensitive, therefore both portfolio and Portfolio are acceptable.
    Number of 856 links in a bib record

    In the P2E process, an electronic resource is made for each matching 856 tag found in the bib record, or holding record, if one was available there.

    In the specific case of OCLC shared bibliographic records, there may be a very large amount of 856 tags in the bib record.  Sometimes this results in an extraordinary number of portfolios created.

    Customers should be advised to either limit the number of 856 tags in a bib record, or if that is not possible, reconsider providing a p2e file in case the number of extra tags is extraordinary.

    Fulfillment

    Patrons

    Ex Libris expects patron records in CSV delimited format. Patron records without a record key identifier are skipped, since this is the minimum required patron information. The record key identifier is used to link the patron to other records such as loans and fines.
    The following fields are expected. Indicate the local field names for the expected fields in the Patrons tab of the WMS (OCLC) Field Mapping form.
    Patrons
    Field Name Repeat-able? Notes
    Patron Given Name N  
    Patron Family Name N  
    Patron Middle Name N  
    Patron Gender N  
    Patron Date of Birth N  
    Patron Borrower Category N use in User Group tab in migration form
    Patron Home Branch Name N use in Campus tab in migration form
    Patron Registration Date N  
    Patron Last Modified Date N  
    Patron Last Modified User N  
    Patron Expiration Date N if empty, migration fills in conversion date + 1 year
    Patron Blocked Flag N use in User Block tab in migration form

    User Identifiers

    There can be a number of fields in the patron record that are user identifiers. The types of identifiers that are available for migration into Alma are listed in the left column. Enter fields from your institution’s patron extract that include identifiers. The values in the left column cannot be changed. Use the values in the left column to select the appropriate primary identifier in the Questionnaire tab of the WMS (OCLC) Migration Form.
    All patron primary identifiers MUST be unique across all users, as required by Alma. If they are not, the migration program disambiguates them.
    User Identifiers
    Alma Identifier Type Local Field Migration Form Value
    UNIV_ID   UNIV_ID
    BAR   BAR
    ADDL_ID_1   ADDL_ID_1
    ADDL_ID_2   ADDL_ID_2
    ADDL_ID_3   ADDL_ID_3
    ADDL_ID_4   ADDL_ID_4

    User Preferred Address

    There may be a number of addresses, phone numbers, and email addresses in the patron record. You may decide which addresses, phone numbers, or email addresses are the preferred ones in Alma. If the preferred entry is empty, the secondary one is preferred.
    Additionally, select a type for each address, phone, or email. All can be selected so that the address, phone, or email can be used as any type.
    User Preferred Address
    ExL Expected Field Local Field  Instructions
    Primary Address    
    Patron Street Address 1   If city, state, zip and country are all together on one line, you can put them into one of the ADDRESS_LINE_x fields
    Patron Street Address 2    
    Patron City/Locality    
    Patron State/Province    
    Patron Postal Code    
    Patron Address Type    
    Address Type (Select):   Select one: HOME, WORK, SCHOOL, ALTERNATIVE, ALL
    Secondary Address    
    secondaryStreetAddressLine1    
    secondaryStreetAddressLine2    
    secondaryCityOrLocality    
    secondaryStateOrProvince    
    secondaryPostalCode    
    Address Type (Select):   Select one: HOME, WORK, SCHOOL, ALTERNATIVE, ALL
    Patron Phone Number    
    Select type from dropdown -->   Select one: Home, Mobile, Office, OfficeFax, All
    secondaryPhone    
    Select type from dropdown -->   Select one: Home, Mobile, Office, OfficeFax, All
    Patron Email Address    
    Select type from dropdown -->   Select one: Personal, School, Work, All
    secondaryEmail    
    Select type from dropdown -->   Select one: Personal, School, Work, All

    User Statistical Categories

    There may be a number of fields in the patron record that function as a statistical category only, for example, a student’s department or major. The way the student borrows can be determined by the User Group, but you may want to track the department, so that you can get more detailed statistics on how Law students borrow, for example. Since various ILS systems have different fields for tracking statistical categories, we provide you the option to map the data from any field in your local ILS to the User Statistical Categories in Alma.
    User Statistical Categories
    User Statistical Category Local Field Name Field Label
    USER_STAT_CATEGORY   SCHOOL:
    USER_STAT_CATEGORY   DEPT:
    USER_STAT_CATEGORY    
    Up to 10 incoming fields can be mapped. To map the values, use the UserStatCategories map in the WMS (OCLC) Migration Form. f a value is not found in the map, it is migrated as is. If you use a label, the userStatCategory map tries to map the field including the label. The first column in the userStatCategory map would be: LABEL: value, for example: SCHOOL:Law.  The migration program does not include the colon, so if you want the colon include it in the label as above.

    Notes

    Any additional fields not listed above may be put into notes. The possible note fields in Alma items are listed in the following chart in the Note Name column. The fields listed in the Default Local Field column are those that are expected by Ex Libris. If you use other field names or have fields that you want to include in the migration but are not expected by Ex Libris, you can rearrange, add, or subtract fields on the right, as necessary. If you want to include multiple local fields in the same Alma note, make as many copies of the line in the spreadsheet as needed for all note name/local field combinations.
    Notes
    Note Name Information
    LIBRARY_NOTE  
    BARCODE_NOTE  
    ADDRESS_NOTE  
    OTHER_NOTE OTHER_NOTE is set to User Viewable by the migration programs

    Loans/Circ Transactions

    Extract only current circulation transactions.
    Provide the loan files in comma delimited format. The following fields are expected. Use the Loans tab of the WMS (OCLC) Field Mapping Form to indicate local field names for the expected fields.
    Loans/Circ Transactions
    Field Name Repeatable? Notes
    Item Barcode N links to item barcode in item file
    Loan Checked Out Date N  
    Item Due Date N  
    Item Long Overdue Date/Time N if a valid date is here, migration will set loan to LOST.  If you *also* want to keep the date, then put this field in notes below.
    Patron Barcode N links to patron barcode in patron file
    Any additional fields not listed above may be put into notes. The possible note fields in Alma items are listed in the following chart in the Note Name column. The fields listed in the Default Local Field column are those that are expected by Ex Libris. If you use other field names or have fields that you want to include in the migration but are not expected by Ex Libris, you can rearrange, add, or subtract fields on the right, as necessary. If you want to include multiple local fields in the same Alma note, make as many copies of the line in the spreadsheet as needed for all note name/local field combinations.
    Note Name Default Local Field
    NON_PUBLIC_NOTE  

    Active Hold Requests

    Extract only those hold requests which are on the hold shelf, waiting for pickup.
    Provide the request file in comma delimited format. The following fields are expected. Use the Requests tab of the WMS (OCLC) Field Mapping Form to indicate local field names for the expected fields.  
    Loans/Circ Transactions
    Field Name Repeatable? Notes
    Item Barcode N links to item barcode in item file
    Hold Pickup Branch Name N  
    Hold Expiration Date N  
    Patron Barcode N links to patron barcode in patron file
    Any additional fields not listed above may be put into notes. The possible note fields in Alma items are listed in the following chart in the Note Name column. The fields listed in the Default Local Field column are those that are expected by Ex Libris. If you use other field names or have fields that you want to include in the migration but are not expected by Ex Libris, you can rearrange, add, or subtract fields on the right, as necessary. If you want to include multiple local fields in the same Alma note, make as many copies of the line in the spreadsheet as needed for all note name/local field combinations.
    Note Name Default Local Field
    NON_PUBLIC_NOTE  

    Fines/Fees

    Fine and fees information is not mandatory, but when it is provided, Ex Libris expects active fine and fee information in csv format (preferably as an outstanding active balance total in the patron CSV extract). Only active (outstanding) fine and fee information is migrated, and only the outstanding balance of each individual fine/fee; partial payment information is not preserved. The following fields are expected. Indicate the local field names for the expected fields in the Fines/Fees tab of the WMS (OCLC) Field Mapping form.
    Fines/Fees
    Field Name Repeatable? Notes
    Item Barcode N matches barcode in item file. This is not mandatory for fines.
    Patron Barcode N matches barcode in patron file
    Fiscal Bill Reason N use in fine fee type map in migration form
    Fiscal Transaction Original Bill Date/Time N  
    Fiscal Currency N  
    Fiscal Transaction Outstanding Amount N  
    Any additional fields not listed above may be put into notes. The possible note fields in Alma items are listed in the following chart in the Note Name column. The fields listed in the Default Local Field column are those that are expected by Ex Libris. If you use other field names or have fields that you want to include in the migration but are not expected by Ex Libris, you can rearrange, add, or subtract fields on the right, as necessary. If you want to include multiple local fields in the same Alma note, make as many copies of the line in the spreadsheet as needed for all note name/local field combinations.
    Note Name Default Local Field
    NON_PUBLIC_NOTE  

    Course Reserves

    Course Reserves can be migrated with premium migration. The following fields are expected. Indicate the local field names for the expected fields in the Course Reserves tab of the WMS (OCLC) Field Mapping form.
    Fines/Fees
    Field Name Repeatable? Notes
    CLASS_CODE N  
    COURSE_NAME N  
    PROFESSOR N This can only be used if the value in the field is an actual patron identifier; do not use if the field contains a name (text).  
    SECTION N  
    OCLC N This is the bib key.  Alma does not use individual item barcodes for course reserves migration, only the bib key.
    CAMPUS N use in Course Unit map
    Any additional fields not listed above may be put into notes. The possible note fields in Alma items are listed in the following chart in the Note Name column. The fields listed in the Default Local Field column are those that are expected by Ex Libris. If you use other field names or have fields that you want to include in the migration but are not expected by Ex Libris, you can rearrange, add, or subtract fields on the right, as necessary. If you want to include multiple local fields in the same Alma note, make as many copies of the line in the spreadsheet as needed for all note name/local field combinations.
    Note Name Default Local Field
    NON_PUBLIC_NOTE  

    Acquisitions

    Ex Libris does not expect to receive Acquisitions information from WMS (OCLC) customers.

    Appendix A – FTP Drop Point Delivery and Delivered Files Form

    Place any data files that you provide to Ex Libris in the formats indicated in Expected File Formats on an FTP drop-point on the Ex Libris FTP server. Use the access credentials provided by your Ex Libris project manager to connect to the FTP server.
    The following is the default naming convention:
    CustomerName+DataType+sequence+date+[.<file_extension>].</file_extension>
    For example: centralu_bib_01_20120420.mrc, centralu_bib_02_20120420.mrc, centralu_bib_03_20120420.mrc
    Ex Libris recommends a maximum of 200,000 records per MARC file, and 400,000 for other types of records (items, orders, etc).
    All records in a single file must be homogenous – all of the lines in the file must have the same number of fields, and those fields must contain the same type of data. Additionally, all of the records must be delimited in the same manner. For example, do not delimit with quotes and commas for some records and pipes for others within the same file.
    For security purposes, the file names listed on the FTP server are not displayed after you upload them.
    Provide the WMS (OCLC) Delivered Files List form along with the submitted files.
    • Was this article helpful?