Note: Only Certified Manager's with full template access have the permissions to create new jobs.
Overview
If not already familiar with Jobs you should read the BLOX Jobs Overview document before this one. Use the following steps to setup a Job to allow you to upload videos via FTP and have them come into the system as a video sset. You will need to upload an XML file with the video. Click New to create a new job
HTTP Upload (in the admin), you can set up this job process. Please note that the larger the file, the longer the download time for the end user. Large files may also incur additional monthly bandwidth and/or storage charges.
Setting Options
Under Source
Values in the location field are limited to 100 characters.
- Module: nitf_media
- Location: feeds/videos/*
Under Destination
Values in the location field are limited to 100 characters.
- Module: tncms
- Location: leave empty
Destination Options (click Add)
For a full list of Destination Options, view Jobs Overview.
- Name: use_site_timezone
- Value: 1
Saving and Running
Click Save at the bottom of the popup window when complete. You can set a for the job or run it manually. Create a directory under /data/feeds/videos/ via FTP (if not already created) and upload your video and XML file to it. Once the job runs the video will show up in the admin in 5-10 minutes as a Video Asset.
XML Example
- <?xml version="1.0" encoding="utf-8"?>
- <!DOCTYPE nitf PUBLIC "-//IPTC-NAA//DTD NITF 2.1//EN" "http://www.iptc.org/std/NITF/3.4/specification/dtd/nitf-3-4.dtd">
- <nitf>
- <head>
- <docdata management-status="bank_robber_fail"/>
- <date.release norm="20091002T000000"/>
- </docdata>
- <ppubdata type="web" position.section="video" position.sequence="0"/>
- </head>
- <body>
- <body.head>
- <hedline>
- <hl1>Bank Robbery Failure</hl1>
- </hedline>
- </body.head>
- <body.content>
- <media media-type="video">
- <media-reference source="bank_robber_fail.fly"/>
- <media-caption>This robber fails miserably at trying to rob this bank!</media-caption>
- <media-producer>Staff Videographer</media-producer>
- </media>
- </body.content>
- </body>
- </nitf>
Copy and paste the above code into Notepad or another program that allows for editing XML. You'll want to click the view plain button in the above example before copying the code. After pasting into Notepad or other program, make sure to save the file with a .xml extension. Example: my-video.xml.
Note the above example is using NITF format. Some editorial systems allow for the exporting of articles and media into NITF format. If editing by hand, you may want to change the following fields in your XML file before saving and uploading via ftp:
- doc-id id-string: If you are compiling your xml files by hand, it is recommended that you remove this field all together. This specifies the id for the video asset in the system. If not specified, the system will create its own id. The field is valuable if your editorial system is generating the files.
- NOTE: if the doc-id matches one already in the system, the new files will replace those already in the system with the matching doc-id.
- date.release: This field is REQUIRED for the job to work. Assets will come into the system with a start time matching this field. Use the following format: YYYYMMDDTHHMMSS where Y represents the year, M the month, D the day, T remains the letter T, H represents the hour, M the minute and S the second.
- pubdata position.section: this should be the section the video should belong to. Can leave blank if you don't wish to specify a section.
- hl1: This is the headline or title your video asset should have.
- media below are some fields included within the media field:
- media-reference source: should be the name of the video being uploaded. Example: my-video.flv. This field is REQUIRED. The only video type that will work is .FLV
- media-caption: this will be the description/caption for the video. This field is not required.
- media-producer: this will be the byline for the video, usually the videographers name. This field is not required.
Note: Browsers not supporting HTML5 or old Video Assets still containing FLV data are no longer supported. These types of Video Assets will now present a simple download link instead of an inline player.