db-http

The db-http plugin connects Brightspot to external content and asset services over HTTP so editors can find and import assets without leaving the CMS. Each integration exposes a remote service — a stock photo library, a video platform, a DAM, or a chat tool — as a searchable, importable source inside Brightspot's federated search.

Key capabilities

• Stock and editorial imagery search and import from Adobe Stock, Getty Images, Shutterstock, and the Associated Press Content API.
• Digital asset management (DAM) search and import from Aprimo, Box, Dropbox, Google Drive, and Microsoft Drives (OneDrive/SharePoint).
• Video search and import from Brightcove, JW Player, Vimeo, and YouTube.
• Product and collection import from Shopify, including automatic re-import when a product changes in Shopify.
• GIF and sticker search from Giphy, and file search from Slack.
• A shared HttpDatabase framework so new HTTP-backed sources can be added following the same search, pagination, and ID-mapping conventions as the built-in integrations.

How it works

Each service is backed by a database class that extends com.brightspot.dbhttp.HttpDatabase. When an editor runs a federated search, Brightspot routes the query to the matching database, which translates the search into the external service's own query syntax (keywords, filters, sort order) and returns a page of results. Selecting a result resolves its external identifier to a Brightspot asset: the plugin looks up or creates an ExternalId mapping between the external identifier and a Brightspot UUID, then builds and populates an asset of the corresponding content type (for example a GettyImage or a BrightcoveVideoExternalItem) with metadata fetched from the service. Because the mapping is persistent, reselecting the same external asset later resolves to the same Brightspot asset instead of creating a duplicate. Credentials for each service are entered by a site administrator in Site Settings or CMS Tool settings, and searches for an unconfigured service return no results (or prompt the user to authenticate, for services that use per-user OAuth linking).

Use cases

Stock and editorial photography

A publisher licenses images from multiple stock agencies and wants writers to search all of them from inside the CMS instead of downloading files and re-uploading them. An editor opens the image picker on an article, searches "hurricane damage," and filters results to only images that are safe to license (Associated Press) or a specific color palette (Getty Images). Selecting an image imports its caption, credit, and copyright metadata along with the file, and licensing the same image again elsewhere in the site reuses the already-imported asset instead of importing it twice.

Marketing and brand asset management

A brand team manages logos, product photography, and video b-roll in a corporate DAM (Aprimo, Box, Dropbox, Google Drive, or Microsoft Drives) and wants that library available to every site editor without duplicating storage. A marketer searches Aprimo by keyword and file type, imports an approved product image into a campaign page, and later syncs a Microsoft Drives document when the source file changes.

Video-driven content

A media company hosts its video library in Brightcove or JW Player and publishes clips to YouTube and Vimeo as well. A producer searches Brightcove by title and update date to find a recently published segment, imports it into a story page, and the embedded player preview renders directly in the CMS for review before publishing.

Commerce content

A retailer wants editors to feature live product and collection data from its Shopify store inside marketing pages without re-entering pricing or inventory. An editor searches Shopify products by title or status, drops a product into a landing page, and the store's webhook subscription keeps the imported product in sync as its price or availability changes.

Team collaboration and casual media

An editorial team shares reference files in Slack and wants to pull an approved graphic from a channel straight into an article, or add a reaction GIF to a lighter piece using Giphy. An editor searches Slack files from a linked workspace, or searches Giphy by keyword and content rating, and imports the result the same way as any other federated search source.

Who this documentation is for

• Configuring integrations — site administrators entering credentials and linking accounts for each service.
• Searching and importing assets — content editors searching for and importing external assets.
• Technical reference — developers installing a module, extending the HttpDatabase framework, or looking up the classes and fields behind each integration.