MediaCentral | UX User’s Guide : Getting Started : Support for iNEWS Communities

Support for iNEWS Communities
 
MediaCentral UX supports iNEWS communities. The iNEWS Community feature allows customers with multiple iNEWS systems to share content and collaborate on stories. An iNEWS user can work with content stored on any of the iNEWS systems in a community from a single iNEWS Workstation. MediaCentral UX provides similar functionality.
MediaCentral UX requires you to supply credentials to sign in to one iNEWS system. This system is considered your local system. If your local system is configured in an iNEWS community, you are able to automatically sign in to other systems in the community. These systems are considered your remote systems. In the Launch pane, your local iNEWS system is listed first, followed by the remote systems. To connect to a remote system, double-click the system name.
In the following illustration, MUCINEWS is the local system and KIEV-JEN and KIEV-MOB are the remote systems.
Any projects listed are associated with your local system. You cannot show projects that are associated with remote systems.
In MediaCentral UX, you can perform the following tasks on iNEWS remote systems:
Browse stories in the Assets pane.
Load queues in the Queue/Story pane.
Display stories in the Queue/Story pane.
Create and edit stories.
Copy production cues from a story on one iNEWS system to a story on another.
Search a selected remote system.
*When searching an iNEWS database, you can simultaneously search multiple indexed queues. However, you can only choose one non-indexed queue path at a time. Attempts to choose more than one result in an invalid selection error message.
Display and play sequences associated with a story if the sequence is stored in the Interplay Production database configured with the MediaCentral UX system you are signed in to.
In other words, if you load a story from a remote system that is associated with a sequence, then click the Open Sequence button, the associated sequence will open if it is stored in the Interplay Production database listed in the Launch pane. You can then edit and save the sequence.
If you load a story from a remote system, but the associated sequence is stored in a different Interplay Production database, you cannot view, play, or edit the sequence. If you click the Open Sequence button, a message tells you that the “mob_id cannot be resolved.” (A mob ID is a software object that identifies the sequence).
*Do not edit a story after you receive the message that the mob ID cannot be resolved. There is a risk of data loss if you remove or modify the existing attached mob ID information
Float stories so that they remain in the queue but do not appear in the rundown.
Limitation for MOS Placeholder and Project Bucket Features
MediaCentral UX checks if the iNEWS server supports the MOS placeholder and project bucket features. These features were added in iNEWS 4.0.0, but the check only succeeds with iNEWS server versions 4.0.3 and later. For this reason, MediaCentral UX only enables workflows using MOS placeholders and project bucket features in iNEWS 4.0.3 and later.