Uploading over FTP

    Follow

    All account have FTP enabled. To login to FTP use the username and password for Account Console.

    Recommended FTP client

    Any FTP client supporting FTPS works with Screen9 FTP. Screen9 does not endorse any specific FTP client.

    A popular free choice for FTP client for Windows and Mac is Cyberduck.

    FileZilla is another popular free choice for uploading via FTP. But users must always accept the certificate manually. See this article.

    Screen9 cannot provide support for any FTP software.

    Connecting

    To connect to Screen9 FTP use the following credentials:

    Server URI: ftp.screen9.com
    Protocol: Explicit FTP over TLS (FTPES)
    Username: Console user name
    Password: Console password

    Protocol

    In order to protect your account credential, explicit FTP over TLS must be used. This is sometimes called FTPS or FTPES. See this article for more information.

    How to enable explicit FTP over TLS depends on the FTP client. If you get errors, you may have selected implicit FTPS instead of explicit FTPS (FTPES).

    Unencrypted FTP access

    It is possible to use plain FTP (ftp://) but passwords will be sent in clear text.

    This is useful for external parties such as TT imports.

    If using plain FTP we recommend that a new console user is created with the user role Producer. Then that user cannot access other media. See the article User-roles-in-Account-Console.

    Filezilla Example

    If you are using FileZilla, type in the Host as ftpes://ftp.screen9.com and remaining connection credentials at the top (as highlighted in by the red rectangle) and click the Quickconnect button. In Filezilla the user needs to manually accept the Screen9 certificate.

    Screen_Shot_2012-02-12_at_9.28.32_PM.png

    Upload the files by dragging and dropping them from your local file browser to the remote machine in the FileZilla application.

    Uploading

    In the FTP each category in an account is presented as a folder. Uploading into a folder will give the video the respective category.

    Console users with multiple accounts will see each account as a folder.

    Once an FTP upload has completed the Screen9 service will pick up your uploaded file and put it in the processing queue. At this point, the uploaded files are visible in the Account Console interface and the filename of your uploaded file is set to the title of the video.

    Note that it can take up to 5 minutes before a video in an FTP folder is visible in Account Console.

    3rd party & external FTP uploads

    For 3rd parties uploading to FTP, we recommend that a new console user is created for them with the user role Producer. See the article User-roles-in-Account-Console.

    Assigning meta data with FTP uploads

    Once a video has been uploaded and the system has picked up the file for processing, meta data such as title, description and preview image can be edited using the Account Console. This works fine for individual videos but can be tedious and requires manual intervention. To make this process easier, Screen9 supports standards for assigning meta data to videos.

    Screen9 currently supports parts of 3 formats for metadata: NewsML, NewsML G2 and Nitf.

    NewsML

    The example in NewsML below illustrates how to add a title, description, property values and a preload image to an uploaded video. The tags HeadLine and SubHeadLine set the values of title and description respectively. Adding a preload image is done by adding a NewsComponent element with the image declared as a ContentItem. Adding StatusWillChange as Canceled with a date will result in a de-publishing at this date.

    <?xml version="1.0" encoding="UTF-8"?>
    <NewsML>
    <NewsItem>
    <NewsComponent>
    <NewsComponent>
    <Role FormalName="Video" />
    <NewsLines>
    <HeadLine>Title</HeadLine>
    <SubHeadLine>Description</SubHeadLine>
    </NewsLines>
    <AdministrativeMetadata>
    <Property FormalName="property key" Value="property value" />
    </AdministrativeMetadata>
    <ContentItem Href="filename.mp4">
    </ContentItem>
    </NewsComponent>
    <NewsComponent>
    <Role FormalName="photo" />
    <NewsComponent>
    <ContentItem Href="filename.jpg">
    </ContentItem>
    </NewsComponent>
    </NewsComponent>
    </NewsComponent>
    <NewsManagement>
    <StatusWillChange>
    <FutureStatus FormalName="Canceled" />
    <DateAndTime>20110518T0000+0200</DateAndTime>
    </StatusWillChange> </NewsManagement>
    </NewsItem>
    </NewsML>

    NewsML G2

    Screen9 has NewsML G2 support based on TTs implementation. Below is an incomplete NewsML G2 file showing which parts of the specification Screen9 picks up:

    <?xml version="1.0" encoding="UTF-8"?>
    <newsMessage>
      <itemSet>
        <newsItem guid="http://tt.se/media/video/20160615-SkaneregnFINAL2222" version="1" standard="NewsML-G2" standardversion="2.20" conformance="power">
          <contentMeta>
            <subject type="tt:product" literal="VIRINRTT0" typeuri="http://tt.se/spec/product/1.0">
              <name>Arkiv</name>
    </subject>
    <headline>Headline</headline>
    <description role="drol:caption">Description</description>
    <contentMetaExtProperty type="ttext:enddatetime" literal="2015-12-29T20:53:49.279Z"/>
    </contentMeta>
    <contentSet>
    <remoteContent href="https://beta.tt.se/media/video/filename.mp4" contenttype="video/mp4" size="107588292" width="1920" height="1080">
    </remoteContent>
    </contentSet>
    </newsItem>
    </itemSet>
    </newsMessage>

    Screen9 does not support pulling remote content referenced in NewsML G2. Instead Screen9 expects that a video will be uploaded with the same name as referenced in the <remoteContent> tag. E.g. the above example expects the video filename.mp4.

    Nitf

    For Nitf the xml file must have the same basename as the uploaded video file. E.g. testvideo.mp4 needs to have a Nitf file with the name testvideo.xml

    The below example illustrates how to set a title and a description. Currently a preload image must be provided in order for the upload to succeed. The preload image should have the same filename as the other files and have a .jpg file extension.

    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE nitf PUBLIC "nitf" "nitf-3-0.dtd">
    <nitf>
    <head>
    </head>
    <body>
    <body.head>
    <hedline>
    <hl1>Title</hl1>
    </hedline>
    </body.head>
    <body.content>
    <p>Description</p>
    </body.content>
    </body>
    </nitf>
    Was this article helpful?
    1 out of 1 found this helpful

    Comments

    • Avatar
      Daniel Berg

      it would be good to have a list of parameters you can use