Import CableLabs™ Packages (Hot Folder)

The /import/cable_labs hot folder can be used to import CableLabs media files and associated ADI XML files directly into the content database. The ADI XML and the assets included in the XML must all be present for the import to trigger. Successfully imported media files are moved to the root media folder. If you previously added a TBD placeholder for a file, the file will attach when you move it into /import/cable_labs. Files that fail to import are moved to the “failed” sub-folder (directory). After the import process is complete, the original source ADI XML is moved into the “xml” sub-folder (directory). These archived XML files do not take up significant disk space, and can always be deleted via FTP or Samba.

  1. On a PC or Mac connected to your TelVue Princeton™ server’s network, navigate to the /import/cable_labs folder.
  2. Make sure your MPEG file has a valid filename. Acceptable characters are:
    • Upper- and lower-case letters
    • Numbers
    • Underscore (_), space ( ), parentheses [( )], pound sign (#), and period (.)
    • If you previously added a TBD for this content, make sure the filenames match.
  3. Open a new window and show the contents of the drive where your MPEG file is. Find the MPEG file.
  4. Drag the MPEG file onto the /import/cable_labs folder.
  5. Refresh the Content screen on the Digital Broadcaster UI and look for the file. When the MPEG file has been successfully imported, the /import/cable_labs folder will be empty and an icon with the filename will appear on the Content page. If you had a TBD placeholder for the file and the filenames match, the imported file will attach. If the import failed, the file or a fragment will appear in /import/cable_labs/failed.

The core TelVue Princeton content metadata fields including program (title), episode, and description are populated based on the corresponding ADI XML fields. The Auto Delete date is auto populated with the License Window End date in the ADI XML. The full ADI XML can be viewed in the TelVue Princeton web application. From the Content page, click on the content title to go to the Show Content page, then click on the CableLabs Metadata link.

The CableLabs feature is not enabled by default, so it may not be enabled on your system. If you have interest in this feature, please contact a TelVue Technical Support representative.

Facebooktwittergoogle_pluslinkedin

2 Comments

  1. Bob Hassinger says:

    Hi,

    I support the Grafton, MA access studio where we have a B3400 and a C500W. I just came across the API page (http://cms.telvue.com/support/product-documentation/princeton-server-api-docs/content-workflow/using-a-hot-folder-to-import-cablelabs-packages-automatically/) where you mention importing Cable Labs packages, and says to contact Technical Support if you are interested in thefeature. I am not familiar with what this is or how it might be of use to us. Could you give me some information?

    Thanks,
    Bob Hassinger
    Grafton Town PEG Coordinator

  2. rbrooks says:

    CableLabs is a metadata-standards organization. They create and publicize different video-metadata formats so that the Cable industry can exchange metadata between different systems using an agreed-upon standard. ADI XML is one such standard. ADI stands for “Asset Distribution Interface”.

    As an example of its benefits, if I am a cable operator and I have an Asset-Management System (AMS) that is CableLabs ADI-enabled, and one of my content providers offers content that has ADI-standard metadata, I know I can import that content into my AMS with ease – no manual entry of metadata or complicated data mapping. The bulk-import process of videos and their associated metadata can essentially be a single drag and drop operation. Our Princeton Server is an example of an ADI-enabled AMS (with the CableLabs features enabled, of course).

    Regarding the last part of your questions, the Princeton Server’s CableLabs feature is somewhat of a “pilot program” feature right now. The CableLabs standards are complex, and each customer’s needs are often specialized. So, we are manually installing it (via a remote-control session) upon customer request so that we can ensure that we meet those unique needs. Our customers that are using it are using it because they have content providers that supply their content with ADI-XML metadata. If you don’t have content providers that offer their metadata in this format, this feature likely won’t be of use.

    Thanks, Bob!