Feature availability 🛈
⭕ Personal ✔️ Suite
Shared Content Metadata guide section overview:
1. Setting up the Shared Content Metadata Feature
2. Switching Between Shared and Local Content Metadata
3. Content Metadata Harvesting
4. Starting Metadata Harvesting
5. Scheduling
6. Performance and Resource Management
7. Stopping the Harvesting
8. Metadata Harvesting Errors
9. Indexed Search
10. Filtering by Content Metadata
11. Using Shared Preview Thumbnails Metadata
Teams using Connecter Suite Workspaces can set up an advanced feature to allow the use of shared content metadata. Using shared content metadata means that each Connecter instance can show it to the user immediately by sourcing readily available metadata without the need to process assets' content locally.
A dedicated Metadata Harvester tool harvests the metadata and syncs it with the metadata pool in the cloud storage enabled for this feature in the workspace. All Connecter instances connected to the workspace can then pull the available metadata from the cloud to use it in various features and tools like asset preview thumbnails, indexed search, metadata filtering, etc.
!!BEFORE YOU START!!
IMPORTANT: Storing and sharing metadata dependent on constant changes in assets' content simultaneously on many Connecter instances connected to the same workspace is highly complex.
This feature's successful setup and error-free use require complete comprehension of file systems and content in general, plus a great understanding of how assets, cataloged assets, and asset metadata in Connecter work. Only experienced admins who take time to get into the details and do the necessary tests before deploying a new tool for their teams should engage in setting up the Shared Content Metadata feature.
Ensure you read all relevant articles and contact us before proceeding to avoid costly mistakes. Note that we cannot provide support with custom solutions to fix issues due to the wrong implementation. Also, ensure all team members receive proper guidance on using the feature to avoid frustration from unexpected behavior.
It's critical to understand that the Shared Content Metadata feature doesn't guarantee correctness by design. It stores a snapshot of the state of the asset's content when the dedicated Metadata Harvester tool processes the content to gather its current metadata.
So if the asset's content gets updated, all team users will continue to work with possibly incorrect metadata until the harvesting tool processes the updated content and updates the metadata.
Search engines and other popular applications use this industry-standard technique to deliver their services, as keeping the metadata in sync with thousands of assets all the time is impossible. The benefit is speed and availability, and the trade-off is potentially outdated data.