Media Submission

This functionality is available in ENPS Mobile only.

ENPS users in the field can add media, such as images and video clips, directly to a story. The content can then be automatically transferred to an FTP server in the newsroom and re-directed to the site's audio, video, or graphics server for additional editing or on-air playback.

The item reference placed in the story has a MOSID of local.enps.mos and the objPath/objProxyPath of the item points to the server to which the item has been sent via FTP. This allows MOS-compliant third party systems to potentially "fetch" the media and to update the objPaths tags to point to the media's new location.

Configuration

To configure media submission functionality:

  1. Set up a web server on your local network that also works as an FTP server.

    This will be your Media FTP Server. The FTP service will be used for transferring media from clients in the field. The web server component is used to allow previews of the media inside the ENPS client and for other systems to retrieve the files.

    If you have a large enterprise, you may want set up multiple Media FTP servers to more evenly distribute network traffic. You can create a single FTP destination for use with multiple ENPS groups, or you can create a separate directory on the server for each ENPS group that will access it. You can also create multiple Media FTP servers.

  2. Open the System Maintenance > Local Media FTP table.

  3. Add a new entry in the table and configure the Settings as appropriate.

  4. Click Save.

  5. Open System Maintenance > Groups.

  6. Set the Media FTP column to the Media FTP Server to assign to the selected group.

    When a Mobile user adds media to a story, the media is sent to the Media FTP Server associated with parent ENPS folder. If the media is added to a personal story, the content is uploaded to the Media FTP Server associated with the user's home folder.

  7. Open System Maintenance > Global Configuration Options.

  8. Set the following options to specify the media file extensions that are allowed to be sent to the new Media FTP server. Lists must be comma-separated with no spaces.

    Field

    Description

    MOSVideoFileExtensions

    List of allowed video extensions.

    For example, wmv,mov,avi

    MOSAudioFileExtensions

    List of allowed audio extensions.

    For example, mp3,wav,wma

    MOSStillFileExtensions

    List of allowed image extensions.

    For example, e.g. gif,jpg,bmp

    MOSBrowseMediaExtensions

    Merged list of all the extensions listed in the settings above.

    These should be ordered based on which file type should be previewed if a media item reference contains more than one type of proxy. For example, if a media item contains both WMV and MOV proxies, only the MOV proxy can be previewed if MOV appears ahead of WMV in this list.

  9. Click Save.

  10. If the Primary Server you are working on is not your organization's Central server:

    1. Open NOM Maintenance (Maint).

    2. Select Window > Synchronization.

    3. Click Sync Now.

    4. Open the News Object Manager (NOM).

    5. Select File > Reload Global tables.

If media is dragged into a story and uploaded via the MOS FTP function, the MOS Item Reference that is created in the story is given a MOS ID of local.enps.mos.

Since this MOS ID has no ActiveX associated with it, users must double-click the media thumbnail in order to see a preview of the media. Double-clicking the text portion of the MOS Item Reference results in a dialog box warning the user that no ActiveX is configured for that item.

Media uploaded in this manner can be redirected to a MOS device using the Groups > MOS Redirection setting, allowing users to open the item in that device's ActiveX as expected.