Configure econtent management

You can use vendor APIs to load econtent records directly into the Vega context engine instead of manually loading and cataloging the records in your ILS.

The econtent management system provides a full extraction of your subscription content records from the vendor, daily updates, and weekly syncs (if required by the vendor). When the vendor adds or removes records from your subscription, Vega applies the updates to the records in the context engine and displays them in search results.

After configuration, the system sends a request to Innovative so that we can most efficiently schedule the extractions for your econtent records from the vendor. Our support team will reach out to your default support contact to let you know the extractions have been scheduled. Please allow sufficient time for econtent records to be extracted, transformed to BIBFRAME, and then indexed into Vega.

You can use APIs from the following vendors:

• OverDrive
• Hoopla
• Axis 360
• CloudLibrary
• BorrowBox

Important

In phase one of implementing this feature, we recommend that you use a vendor’s API to provide records directly to Vega only if you are comfortable with the following:

• Loading the entire subscription into your Vega Discover context engine.

Note that the Hoopla catalog contains over 1.5 million records.

• The level of cataloging detail provided by the vendor.

Loaded records cannot be individually updated like they can in the ILS. Some titles may not roll up with works based on vendor-provided data.

• ILS-cataloged copies of matching title IDs from vendor subscriptions will appear instead of the API-ingested record.
• You can use this feature to correct record metadata.
• You don't need to delete your current ILS econtent records before you load records via the APIs, and you can take your time to remove ILS copies of econtent records.

See also

• Configure consortia collection sites