Filtering content¶

By default, the Acquia Content Hub tab displays all content entities uploaded by all members of your content network in Acquia Content Hub, in chronological order from newest to oldest. You can use filters to limit which items display, helping you discover the items in which you are most interested. Filters group by AND, meaning items matching all conditions will display.

To create a filter, select one or more of the following filter criteria:

• Keyword: Acquia Content Hub searches with this string against each field in each shared entity.
• Date: You can filter by a start date (content created on or after that date), an end date (content created on or before that date), or both.
• Source: One or more members of your content network. Content from those sources displays in the results.
• Tags: Filter by one or more tags on your content.
• Type: Filter by one or more content types.
• Bundle: Filter by one or more bundles from entities, vocabularies, and blocks. For information about bundles, see Bundles on Drupal.org.

Acquia Content Hub displays all the available content entities matching the filter facets.

You may also sort the available content by selecting an option from the Sort by menu:

• Newest
• Oldest
• Relevance

Importing content¶

Each content item displayed on the Content > Content Hub tab can import to your website. Select the content items you want, then click Import. Items you have already imported display in the filter list and marked as Imported to site.

If there is no content to import, the website will display a No content is available for import. message.

If there is more than one page of available content, a pager will display at the bottom of the page.

Imported items will sometimes bring all dependent items with them during the import process. This includes images and files. If items aren’t imported, they will include a reference to the original.

Imported content will display the following data, when available:

• Content title or name
• Short description
• Publish date
• Source website
• Languages available
• A Read only indicator, if the content is read-only

Next, a collapsed fieldset named View Entity Info displays. Click the link to see this information:

• Bundle Type
• Source Name
• Source UUID
• Entity Type
• Entity UUID
• Tag IDs
• Tags Names

When using the Workbench Moderation module, some content may not be available for import. If your content type is defined using Workbench Moderation, and defaults to the Draft state, you may not always see all the content you expect. If you are importing content onto a website using Workbench Moderation, and that website uses the Draft state by default, you must process the imported content.

For information about using canonical URLs to improve your websites’ SEO (search engine optimization), see SEO and social publishing metadata with Content Hub 1.x.

Deleting content¶

If a content entity is deleted by the publishing website, by default, that action has no effect on the entity on the consuming website. Only changes to the existing text (and not the removal of the entity) will result in updates to the consuming website. Although the originating website sends a webhook to inform subscribers the content was removed, the content will remain on the subscriber websites unless you use a custom module to delete the content.

After a content entity imports to your subscriber, it has the same status as any other content entity of the same entity type on your website. You can change it, publish or unpublish it, or delete it. Actions you take on the content entity have no effect on the item on the source website, or on any other member of your content network which may have already imported the content entity or might import it in the future.

If no local changes have been made to an imported entity on a subscribing website, the imported entity updates when the original publisher website pushes a new version of the content. If the imported entity has local changes, a content update made on the original publisher website won’t update the imported entity unless the Enable Automatic Updates checkbox is selected.

Developers can write applications to watch for delete requests. The watchdog log tracks the webhook notifications. For example:

Webhook landing: @"uuid":"47c937d3-1504-46e6-6b68-a654620a279c",
"status":"successful","crud":"delete","assets":
[{"uuid":"23377268-4bb6-49db-97ff-bb024b82cde8","type":"node"],
"endpoint":"http://mytestsite.acquia.com/acquia-contenthub/webhook",
"initiator":"163ef3342-d2c2-49d9-5716-d25fc02ec7ac",...

Retries¶

Acquia Content Hub has different retry settings based on whether connections are active–where publishers and subscribers are both working, or inactive–where one end of the connection is down.