Configure consortia collection sites

Libraries that belong to a consortium can customize their Vega Discover user interface. Consortium administrators must set up individual libraries in Vega before the libraries can perform customization tasks. For information on customization, see the following topics:

The ability to configure consortia collection sites is available to libraries that are set up as consortia during Vega implementation.

For information on setting session timeouts, see Set the session timeout period.

Collection site configuration overrides consortia-level configuration for that site.

Ingesting bibliographic records directly from a vendor

If you want to ingest bibliographic records directly from a vendor into your Vega collection site, first make sure that the vendor format mappings exist for the vendor you want to configure. If they’re blank, you need to configure them in the third-party connection settings before you proceed. For more information on vendor format mapping, see Configure material type settings.

Once the vendor format mapping is configured, you can enable the option called Use API to provide records directly to Vega and save your configuration. Vega schedules an ingest of records from the configured vendor to begin in 10 minutes, and checks for new, updated, and deleted materials from the vendor every 24 hours. For more information, see Configure third-party connections.

Consortia member libraries that purchase econtent independently

If your consortia member library purchases econtent subscriptions independently of the consortia, you can configure your econtent subscriptions in your collection site for all vendors except Hoopla. For information on how to configure Hoopla econtent purchased independently, see Configure econtent for consortia collection sites.

Before you begin

Before you can configure econtent for consortia collection sites, you must configure econtent mapping. For more information, see Configure econtent mapping.