Search and the Central Index
MediaCentral UX provides two methods of searching your asset database. Federated search uses the search capabilities of MediaCentral databases to provide the full search functionality that individual databases provide, with the limitations that are imposed by those databases. Media Index search does not directly search iNEWS, Interplay MAM, and Interplay Production databases but instead queries a central index synced with multiple databases and finds anything stored in the index.
Using Media Index with the central index provides a unified view of multiple asset management systems and focuses on simplicity and speed in finding assets. This does not replace existing asset management solutions, and you can continue to use the federated search for detailed asset information.
Indexed search requires Media Index to be installed and configured in your MediaCentral Platform environment.
Multi-zone search gives you access to media stored in zones other than the one you log in to when you sign on with MediaCentral UX. Your MediaCentral administrator must configure your user roles and permissions to view multi-zone databases, and you must have the proper permission settings to edit or play media assets found in a search. For playback and remote asset delivery, you must log in at least once to the remote system with MediaCentral UX in order to configure your Interplay Production credentials.
There currently are some limitations in using an indexed search with iNEWS:
• You cannot use the indexed search with iNEWS in a multi-zone environment. If your configuration includes multiple zones, the indexed search works only on the iNEWS system connected to the local zone.
• You cannot search the content of any custom fields of your iNEWS stories. Media Index cannot search fields that have customized field names.
• Searching the central index returns all items that meet the criteria specified in the search, regardless of read permissions set in iNEWS. You cannot open an iNEWS story listed in the search results that you do not have the appropriate permissions to view.
• The default search type for the Search bar is the federated search.
The following limitations apply when using an indexed search with Interplay Production assets:
• No per asset/per user permission. You can hide parts of the database by using a PEBCo user account with limited access for indexing. If the PEBCo user is not an administrator, database access can be limited to certain directories, and only those directories are indexed. For information on configuring a PEBCo user for Media Index, see “Configuring and Using the PEBco Service” in the Avid Media | Index Configuration Guide.
Since indexed searches respect the permissions of this account and not that of individuals logging into MediaCentral UX, users with permissions different from the PEBCo user might be exposed to assets that they could not otherwise view in Interplay Access. Although MediaCentral UX users can view names and metadata for assets they do not have permission to view, they are blocked from playing the assets.
• No folder locations. Assets in Interplay Production can be linked to multiple locations. In Media Index, these locations are not stored and you cannot display or search by folder locations.
The following limitations apply when using an indexed search with Interplay MAM assets:
• All attributes marked as “searchable” in the Interplay MAM data model are always sent to the central index during the sync process. Attributes marked as “not-searchable” are not sent to the central index and are not be available for searching or in search result lists. Your Interplay MAM administrator sets asset permissions for search results using Interplay MAM.
• When using legal list attributes in Interplay MAM CBA rules, MAM allows to build rules using “>=”, “<“ for legal list values, since these values are integer values in MAM. On Central Index side, legal list values are treated as “ID-string,” and only comparisons like “=” or “!=” are supported.