Software Requirements Specification Media Overviewmaria-hutchinson.com/pdfs/ptc-video-library-srs.pdfSoftware Requirements Specification for the Media Overview Project Page ii

Software Requirements Specification

For

Media Overview

Version 1.0 approval pending

Prepared by Maria Hutchinson

PTC

1/22/10

Software Requirements Specification for the Media Overview Project Page ii

Table of Contents Table of Contents .......................................................................................................................... iiRevision History ............................................................................................................................ ii1. Introduction ..............................................................................................................................1

1.1 Purpose ........................................................................................................................................ 11.2 Intended Audience and Reading Suggestions ............................................................................. 11.3 References ................................................................................................................................... 1

2. Overall Description ..................................................................................................................32.1 Product Perspective ..................................................................................................................... 32.2 Product Features .......................................................................................................................... 3

3. System Features ........................................................................................................................33.1 PTC.com Functional Requirements ............................................................................................ 33.2 WCMS Functional Requirements ............................................................................................... 93.3 Universal Search ........................................................................................................................ 163.4 Accessing Secure and Form Protected Video Content .............................................................. 163.5 Captions (Subtitles) ................................................................................................................... 183.6 Chapters ..................................................................................................................................... 183.7 PTC Internal (PTConnector) ..................................................................................................... 193.8 Email .......................................................................................................................................... 223.9 Software Upgrade Flowplayer ................................................................................................... 23

4. Other Nonfunctional Requirements .....................................................................................23Appendix A: Glossary ..................................................................................................................23Appendix B: Future considerations ..........................................................................................24

Revision History Name Date Reason For Changes Version

Software Requirements Specification for the Media Overview Project Page 1

1. Introduction

1.1 Purpose

The goals of the Media Overview Project are - Integrating content which was previously in the Presentation Replays content group into the

Videos content Group. - Making Support video content available through the Videos content group. - Displaying Presentation Replays and Support video content on PTC.com. - Enhancing User Experience for accessing video content on PTC.com - Making streaming video content that will be hosted on Akamai available on PTConnector. - Create an Internal Videos content group. - Users will be able to access and view internal and external streaming video content through

PTConnector site search and video library across content groups.

1.2 Intended Audience and Reading Suggestions

This document is intended for, developers, management, project managers, marketing staff, users, business owners, testers, and documentation writers. The rest of this SRS contains functional requirements for the Media Overview Project. Developers will find functional requirements listed by feature in Section 3: System Features. Please refer to Appendix A: Glossary for definition of terms

1.3 References

A. Use Case Diagrams and Wireframes https://pds.ptc.com/Windchill/servlet/AttachmentsURLRedirectServlet?oid=VR:wt.doc.WTDocument:617912516

B. PTC.com Media Wrappers SRS

https://pds.ptc.com/Windchill/servlet/AttachmentsDownloadDirectionServlet?oid=OR:wt.doc.WTDocument:598483033&cioids=wt.content.ApplicationData:598483053&role=PRIMARY

C. Documentation: Supported Products (Dave Suter)

https://pds.ptc.com/Windchill/servlet/TypeBasedIncludeServlet?oid=OR:wt.content.ApplicationData:610588379

D. Documentation: Accessing Marketing Assets on PTC.com – basic and detailed account

creation (Eric Kristoff) 1. https://pds.ptc.com/Windchill/servlet/TypeBasedIncludeServlet?oid=OR:wt.content.Appl

icationData:624453242

2. https://pds.ptc.com/Windchill/servlet/TypeBasedIncludeServlet?oid=OR:wt.content.ApplicationData:624455001

E. Guidelines for Video:

https://pds.ptc.com/Windchill/servlet/AttachmentsURLRedirectServlet?oid=VR:wt.doc.WTDocument:617912516�


https://pds.ptc.com/Windchill/servlet/AttachmentsDownloadDirectionServlet?oid=OR:wt.doc.WTDocument:598483033&cioids=wt.content.ApplicationData:598483053&role=PRIMARY�


https://pds.ptc.com/Windchill/servlet/TypeBasedIncludeServlet?oid=OR:wt.content.ApplicationData:610588379�







1. External Video Creation Guidelines: creating video for ptc.com (Ben Roberts) https://pds.ptc.com/Windchill/servlet/AttachmentsDownloadDirectionServlet?oid=OR:wt.doc.WTDocument:623882376&cioids=wt.content.ApplicationData:623882381&role=PRIMARY

2. Internal Video Creation Guidelines: creating video for PTConnector: Will be made available on PTConnector along with existing PTC.com guidelines

3. Existing guidelines for PTC.com video on PTConnector:

http://internal.ptc.com/WCMS/files/96637/en/Video_Guidelines.pdf

4. Aspect Ratios Vector Video Standards2: http://en.wikipedia.org/wiki/File:Vector_Video_Standards2.svg

F. Current links as of 11/2009:

1. Current presentation replays "Unique Url" page

http://www.ptc.com/appserver/wcms/replay/index.jsp?im_dbkey=40488&icg_dbkey=362

2. Current WCMS "Unique URL"

http://www.ptc.com/appserver/wcms/media/streamed.jsp?&im_dbkey=97810&icg_dbkey=904

3. Example of Filtering on PTConnector

http://internal.ptc.com/appserver/wcms/search/index.jsp?&cg=847

4. Example of Filtering: Search results page PTC.com PTC.com Search Results page

5. Current example of chapters as of 10/2009

http://www.ptc.com/WCMS/files/99882/en/flash/index.htm?&im_dbkey=99882&im_language=en

6. Example of file collections currently used for conferencing as of 10/2009

http://salesdev03d/web/samples/Articulate1/player.html



http://salesdev03d/web/samples/Camtasia1/BarrryAP_small.html

G. Navigator Labels for Video Library Pages https://pds.ptc.com/Windchill/servlet/AttachmentsURLRedirectServlet?oid=VR:wt.doc.WTDocument:648288328




http://internal.ptc.com/WCMS/files/96637/en/Video_Guidelines.pdf�

http://en.wikipedia.org/wiki/File:Vector_Video_Standards2.svg�

http://www.ptc.com/appserver/wcms/replay/index.jsp?im_dbkey=40488&icg_dbkey=362�

http://www.ptc.com/appserver/wcms/replay/index.jsp?im_dbkey=40488&icg_dbkey=362�

http://www.ptc.com/appserver/wcms/media/streamed.jsp?&im_dbkey=97810&icg_dbkey=904�

http://www.ptc.com/appserver/wcms/media/streamed.jsp?&im_dbkey=97810&icg_dbkey=904�

http://internal.ptc.com/appserver/wcms/search/index.jsp?&cg=847�

http://www.ptc.com/appserver/search/results.jsp?q=Pro%2FENGINEER�

http://www.ptc.com/WCMS/files/99882/en/flash/index.htm?&im_dbkey=99882&im_language=en�

http://www.ptc.com/WCMS/files/99882/en/flash/index.htm?&im_dbkey=99882&im_language=en�

http://salesdev03d/web/samples/Articulate1/player.html�



http://salesdev03d/web/samples/Camtasia1/BarrryAP_small.html�




2. Overall Description

2.1 Product Perspective

The Media Overview project specified in this Software Requirements Specification is a follow on to the Media Wrappers project, which was a part of the PTC.com Redesign.

2.2 Product Features

All PTC.com video content will be integrated into the External Videos content group to be accessed through media wrappers, and libraries on PTC.com. An Internal Videos content group will be created for PTConnector video content. All video content will be accessible through video library pages on both the internal and external sites. The ability to add captioning will be added for video accessibility in all languages. Chaptering features will be available for longer videos. Existing media wrappers on PTC.com will be enhanced. Presentation Replays video content will be integrated in to the videos content group. Support video content will be made available. Site search for video content will be enhanced. Usability enhancements for optional cross promotional advertising and will be added to media wrappers. Some advantages of using the .flv format and Akamai streaming are:

• In streaming, each client opens a persistent connection back to the video server, and there is a tight relationship between the video being delivered and the client interaction.

• This approach lets you deliver features such as bandwidth detection to serve up the right size video.

• A swf will not allow a user to jump to the last frame of the swf until the entire swf has downloaded, but with streaming an flv, you can jump to the end of the movie before the entire movie loads completely (which also saves bandwidth)

• FLV has the advantage that it is not capped by the 16,000 frames limit of an SWF, so it is ideal if you have a movie with higher frame rates or a longer movie.

• Flv format is the standard used by YouTube and id the most widely accessible.

3. System Features Functional requirements for the project are listed by the major services provided by the project.

3.1 PTC.com Functional Requirements

3.1.1 Media Wrappers: FLV is the required file type for external video content. External video will be streaming and will be hosted on Akamai streaming servers. Aspect ratio will be 16:9.

REQ-1: Homepage: enhancements, changes, and issue resolutions

A. Animation will auto play, Video will not. If user doesn’t have Flash player installed, they should be prompted to install. Currently video doesn’t show and there is no prompt to install player.


B. Homepage Flash Animation (SWF files) : Currently:

• There are 2 frames. In the first frame Animations (.SWF) are displayed using the SWFObject library. In the second frame, Videos (.FLV) are displayed using Flowplayer.

• The JSP media include is a hard-coded page of one SWFObject element placed on top of one Flowplayer element.

• Clicking on the different tabs determines will cause one of the elements to appear on top. While the Flowplayer frame can handle many videos, SWFOBject can handle only one animation.

• If there is a flash animation or swf file, it will always be in position 1. • If there are no animations, the SWFOBject frame is set to disappear. • If there are no videos, Flowplayer frame is set to disappear.

Requirements:

1. The potential to have more than one flash or swf file in the homepage media wrapper must exist.

2. The potential for all combinations of video (flv) and animation (swf) must exist.

3. Ideally swf and flv could be in any order. For Example: 3 videos, 3 Animations, 2 Videos 1 Animation, 2 Animation 1 Video etc... There are 14 possible combinations.

4. SWF files must still pull translated text from .txt files as they do now 5. Animations (.SWF) are displayed using the SWFObject library. 6. Videos (.FLV) are displayed using Flowplayer.

C. Call to Action: The potential exists for the user to click the Video itself, and be

brought to a URL. A visual cue (For Example: learn more, would you like to be contacted by a Sales Rep? etc…), will be added.

REQ-2: External (PTC.com) Non-Homepage Media Wrappers - See section 1.3

References section A (Use Case Diagrams and Wireframes: 4.0.1) A. Call to Action B. Downloads C. User is prompted (with visual cue) when there is a larger size, longer or full

version download available. D. View at Larger Size E. Share - Addthis F. Availability of video content in all languages and improving accessibility and

SEO through captioning or subtitles. G. Tabs – A third tab will be added to the non-homepage media wrapper in the tabs

section. It will be labeled Demos and will contain demos and tech tips content. The tab that is currently labeled videos will have support and marketing content.

H. Captions I. Chapters J. View at larger size from non-homepage Media Wrappers, Video Library page

and Unique URLs. 1. Similar to the enlarge/zoom button for images) video can play at its

maximum size in a modal or window. The full screen button in Flowplayer will be used to access this functionality.

2. The full screen functionality from flowplayer will not be used because the aspect ratio of the user's screen and aspect ratio of the content may not match and video will appear distorted.


3. Use JavaScript to determine width and height based on monitor resolution. We currently use 4 separate bit rates on ptc.com. Ptc.com determines the best availability for bit rate when you go full screen. [150, 256, 640, 1024] - See section 1.3 References section A (Use Case Diagrams and Wireframes: 4.0.0)

4. Chapters must be available when viewing larger size. The chapters list may appear over the video if necessary

K. Presentation Replays Content in Non-Homepage Media Wrappers: Media wrappers will have all presentation replays flv content which will be newly formatted. Content may appear in any page’s media wrapper, depending on where it is tagged. A third tab will be added to non-homepage media wrappers in the scrolling list section for demo and tech tip content. When an aspect ratio used besides 16:9, black bars will show. A higher bitrate may be needed and a high quality download will be needed for demo videos to give quality results as well as a high enough resolution so that the demos effectively show enough detail. Currently the types of content in the Presentation Replays Content Group are:

• Webcasts: average 1 hour long. usually it is a speaker going through a PowerPoint

• demos • tech tips – currently for maintenance customers only

L. Support Video Initiative: Video Content that will only be available only to maintenance account users. Users may access Support Video in media wrappers on the support pages of ptc.com, by direct link (unique URL), and on the video library page. A support tab won’t be required in media wrappers. Support videos will appear under the demos tab in support page media wrappers. See requirement 2 above (A-I) for available features.

1. WCMS categorization: supported products are not in the current products list

in WCMS. There is a separate products list. The categorization and product list are available in the Product Reference Documents Content Group. The product lists will be combined (602 with 163).

2. Support Video content will not be available on YouTube 3. Entitlement checking is required for support content. 4. Languages: support videos will be in English with translated subtitles or

captions. 5. Search: caption/ subtitles 6. Security: videos content group has security built into step 2

M. General: Non-Homepage Media Wrapper Enhancements, changes, and issue

resolutions 1. Scrolling Issues – Currently, the last description and thumbnail gets cut off if

there are long descriptions. Scrolling goes the wrong direction in cases where there are long lists (for example, on some of the product pages). Make area for thumbnails and title a fixed height in the scrolling list in the media wrapper tabs section. • Image and Video thumbnails are different aspect ratios the width is

consistent for video and images: 90px. Thumbnail image and description areas may be different heights for the images and video tabs

• Videos Content Group Thumbnail Image - In the videos content group, the acceptable dimensions are 160px wide; 60–240px tall, but the image actually displays at height: 50px width: 90px. A height of 100px video would allow for approximately 5 lines of text.

• Image Gallery content group thumbnail images - The acceptable dimensions of the image thumbnail in the image gallery content group is:


120px wide; 80–140px tall. The height of the thumbnail image/title area would need to be approximately 145px.

• CSS adjustments: font size, margin, padding, line-height to get 2 decent sized words on a line

• In WCMS existing titles may need to be shortened or truncated with ellipses ... because the amount of text for titles will be limited to fit in the fixed height space.

• When there are less than 3 thumbnail images the bottom scroll arrow shouldn’t appear. Disabled class is needed.

• Scrolling is controlled in the tab, by arrows above and below the lists. Keyboard arrow keys won’t control scrolling for image or video thumbnail lists.

2. When a video is playing and the image tab is selected, the video and sound

should stop playing 3. User will be prompted to install flash if they don’t have it already. 4. Video tracking in Site Catalyst

3.1.2 External Video Library Page Combine Company, Demo, Tech Tip, and Support content onto one library page.

The page will serve as a collection or catch all. All video, demo, and support content will be collected here including that for products that don’t have their own page and/or media wrapper.

Users may navigate to this page by About PTC / Company Overview on PTC.com.

The Video Library Page will be a jsp and it will pull video content from wcms. There won’t be any Animation or Images on the library page. Content will be filtered by WCMS categorization and Fast Search. Results will display and refresh on the page. - See section 1.3 References section A (Use Case Diagrams and Wireframes: 1.0.0)

REQ-1: JSP page with media wrapper will serve as a collection or catch all for

external video. REQ-2: Navigator modifiers filter or narrow selections: by parallel selection,

allowing for multiple filter values Use Case:

• User arrives at video library page • By default all videos appear in the results list by date • User may filter or narrow results by making selections from the navigator

modifier list. • User may deselect any selection to clear the associated results from the results

list • If everything is deselected, all videos appear in the results list • user selects item from results list video player opens in a modal

A. Ability for user to add or remove filter values and select multiples by

checking and un-checking boxes, and clicking x in breadcrumb. B. Filter by WCMS categorization and Fast Search Navigators - See section

1.3 References section A (Use Case Diagrams and Wireframes: 1.0.6, 1.0.7, and 1.0.8) and


C. See section 1.3 References section G for Navigator Labels for Internal and External Video Library Pages

REQ-3: On Page Search A. Search Criteria:

• Title • Description • Author • wcms categorization • captions or subtitles

REQ-4: Results A. Featured Video or Promotional area - There will be a promotional or featured

area. It will be used to highlight 3 videos. This area will have 3 images with the title displaying underneath and user clicks to open a modal with a player. Only title and image display. The featured items are determined by setting priority in WCMS. If none set it is by most recent. Because of where the prioritization is stored in the database for WCMS, it can be integrated with fast.

B. Non Featured Results - The general results appear below the featured area on the page. Title of the content item, description, and the image thumbnail display in a paginated results list. Videos results default by date before the user has made any navigator modifier or tag cloud selections and before the user has performed an on page search.

C. Results refresh on page like on the current site search page on PTC.com. Results will display in a paginated list in increments of 10 by default. For Numbering, See section 1.3 References section A (Use Case Diagrams and Wireframes: 1.0.1-1.0.5)

D. Modal - On the external library page, clicking a result, in the featured area or in the general results area, the item opens a modal with a player in it. The player is the same size as the homepage of PTC.com, height: 396px by width: 704px. - See section 1.3 References section A (Use Case Diagrams and Wireframes: 1.0.9) Player will have: 1. chapters 2. call to action 3. captions 4. downloads 5. share 6. view at larger size – use full screen button on flowplayer to enlarge in modal

E. Use Case: 1. User comes to library page and may access all video: Company, Demo, Tech

Tips, and Support content (the default is all content) 2. User may Search Content 3. User may parallel select content by navigator modifiers 4. A results list is returned – on page (in paginated list). Results area contains

thumbnail image, title, and description. 5. User selects a result and video plays in a modal

REQ-5: Tag Cloud

3.1.3 External Unique URL


A Unique URL is for a single Video content item or URL instance of one video. A user would access this URL from a bookmark, email, share functionality, search result, or direct link etc.... Related videos appear in a scrolling list to the right. Unique urls may be form protected - See section 1.3 References section A (Use Case Diagrams and Wireframes: 2.0.2)

REQ-1: Call to action REQ-2: Downloads: A. WMV B. MOV

REQ-3: View at a larger size REQ-4: Share REQ-5: Captions available if applicable REQ-6: Chapters available if applicable REQ-7: Player size: same as the non-homepage media wrapper on PTC.com. Height:

288px by width: 512px REQ-8: Related Video A. will be driven from WCMS categorization B. To insure videos that are actually related are showing up (for example: if it is a

demo, only demo content shows up) additional categorization is needed for : 1. Company 2. Demos 3. Tech Tips 4. Support

C. Located in the scrolling list to the right instead of related resources. Tagged by existing WCMS categorization. Web team is the only ones tagging videos. They will display in a list by

1. thumbnail image 2. Title

D. Selecting a video from related videos brings the user to unique URL. 3.1.4 PTC.com site search video results - See section 1.3 References section A (Use Case Diagrams and Wireframes: 3.0.0)

Improve video results and the display of results. Results should pull Meta description or wcms description.

REQ-1: Improve Video Results in Fast A. search collections: limit to search within a collection in search appliance B. Internal - ability to search across content groups REQ-2: search criteria: A. Title B. Description C. Author D. content group or wcms categories E. captions or subtitles


REQ-3: improve Keywords/Meta Description A. 2 gigs worth of key words are allowed REQ-4: Results: improve user experience how results display. A. Results display in a paginated list in increments of 10 by default. B. Results include: Thumbnail image, title, description and URL C. Narrow Results:

1. Navigators: they are the headings, for example: Product, or Process and Initiatives.

2. A list of up to five modifiers will display under each navigator and are determined by frequency as opposed to alphabetical order. Six modifiers will display if there are only 6 total.

3. If there are 7 or more modifiers under a navigator, the word more with an arrow that will expand/ collapse the rest of the list when it’s toggled displays.

4. Number of results are displayed in parentheses after each term D. Search terms are highlighted. E. Number of results found displays but not the # of seconds it took to return the

results. F. Add images for video results – use existing thumbnail image size

1. currently images are created and uploaded manually and separately

3.2 WCMS Functional Requirements

CMA requirements for External (PTC.com) and Internal (PTConnector) Mapping the video content from the presentation replays content group to videos content group. Combining product lists.

3.2.1 Videos Content Group - External: This content group will be the one central location for all external videos on PTC.com.

REQ-1: Non-Homepage Media Wrappers - General enhancements A. Resolve scrolling issues by limiting the amount of text allowed for title and setting

a fixed height in the thumbnail/title area. REQ-2: Library page: catch all or collection of all video content. All Video will be

displayed on the Video library page as well as media wrappers on other pages, according to where it has been tagged.

A. Navigators and Modifiers - Filtering (See References section 1.3 G) B. Merge the 2 “Products” list, 602 with 163 (Marketing Products and Support

Products) • de-duplication needed

C. There will be Featured or Promotional area for 3 videos at the top of the page. 1. The videos that will appear in this area will be determined by prioritization 2. If no prioritization is set, then they are determined by date or most recent. 3. Owners of the content group may set priority. 4. Results are displayed in the featured section based on prioritization. 5. There has to be one prioritized video to show the featured section at all. If

only one or two are prioritized, the rest are determined by date. 6. Results below the featured section are displayed by date or relevance (user

enters a search term).


7. If the featured video section is present, the results below it are numbered. 8. The promotional Area will have an image displaying at 240px width by

135px height. 9. The title will display below the image

D. The ability to set “Include Availability: None”. Categorization will exist in order to exclude videos from appearing on the video library pages. It would be for instances when you need to exclude something like intros to specific pages (called 101 videos) from the library page.

E. Tag Cloud: User may filter selections by clicking words in the tag cloud. User may deselect from the breadcrumb, by clicking on the “x”. The tag cloud and navigator modifiers are searching the same content group on the page. Select by a cloud and a modifier at the same time. The selections will be indicated in breadcrumb. Tags will be based on: 1. Content on page 2. Keywords 3. Body text 4. Video captions

F. On page Search G. Setting Priority in the CMA will correspond with Fast search appliance because

of where the prioritization is stored in the database for WCMS; it can be integrated with fast.

H. Modal - Selecting a result or a featured video opens a modal with a player. Player is the same size as the player on the homepage of ptc.com height: 396px width: 704px

I. Results: The General results not featured in the promotional section appear below the section and display by:

. The existing splash image size 704px wide; 396–704px tall may be used for player in the modal.

• Thumbnail image measuring 160px width by 90px height (same as existing Non-Homepage Media Wrapper thumbnail image size)

• Title • Description

J. Categorization needed for External Videos Content Group 1. Video Type

• Company • Demos • Tech Tips • Support

2. Release REQ-3: Unique URL: Player size: same as the non-homepage media wrapper on

PTC.com. Height: 288px by width: 512px. Call to Action, Downloads, View at larger size, Share, Captions, Chapters will be available.

A. Related Videos section

1. Categorization is needed for Related Videos section: • Company • Demos • Tech Tips • Support

2. Splash Image - Acceptable dimensions are the same as existing splash image in the videos content group: 704px wide; 396–704px tall.

3. Thumbnail Image - Acceptable dimensions are the same as existing thumbnail image in the videos content group: 160px wide; 60–240px tall.


4. User is brought to unique urls by selecting a video in the related videos section

B. Unique Urls may be form protected it is optional REQ-4: Accommodating presentation replays content A. Call to Action field for call to action/ promotion URL Call to Action, so when

user is prompted by a visual cue built into the wrapper they click and can be brought to another page

B. Security: applicable video may be available to maintenance account customers only such as Tech Tips

C. Ability to have non-homepage media wrappers on the Demos and Tech Tips page on PTC.com

D. Ability to have demos and techtips content under a dedicated tab in all non-homepage media wrappers. http://www.ptc.com/products/tutorials/index.htm

REQ-5: Accommodating Support content. A. Support currently uses the Product Reference Documents Content Group product

list. That list will be merged. Module list is already combined in the Product Reference Documents Content Group. Merge Product lists 602 with 163

B. Categorization is needed for Release in the Videos Content group C. Security: video may be available to account users only. entitlement checking

needed D. Ability to have non-homepage media wrappers on Support pages on PTC.com REQ-6: Availability of videos in all languages REQ-7: define who the content submitters/ approvers (owners are approvers) are, and

who gets the email REQ-8: Chapters: A. If the video has corresponding XML

• Upload from WCMS Content Group like the Freeform Content Template • There is a limit of one xml file per video

B. If the video does not have corresponding XML, the ability is needed to Add, Remove, and Edit chapters from the CMA (WCMS) • Add chapter • Remove chapter • Edit chapter • Start time hh:mm:ss • End time hh:mm:ss • Chapter duration • plain text entry field for titles of chapters

C. Chapters must be available when viewing video at larger size in modal REQ-9: Captions or Subtitles: A. If the video has corresponding XML file or external captions file

• Upload from WCMS Content Group like the Freeform Content Template • There is a limit of one xml file per video

B. If the video does not have corresponding XML, the ability is needed to Add, Remove, and Edit captions. • Add

http://www.ptc.com/products/tutorials/index.htm�


• Remove • Edit • Start time hh:mm:ss • End time hh:mm:ss • Duration • plain text entry field for captions

REQ-10: Call to Action – For both Homepage and Non-Homepage media Wrappers, The user currently has the option to enter a target destination URL. The option to add corresponding instructional text will be added for the visual prompt. Examples of a visual cue: learn more, would you like to be contacted by a Sales Rep?, click below to download the full or a larger version of the video, contact me, take survey, etc…), will be added. The visual cue informs the user to perform an action or it is instructional for promotional purposes and to advance the sales process. There may be one call to action URL associated with a video at a time. A. Target Destination URL B. Free Text field for instructional text C. Similar to a caption REQ-11: Site Search: ability to search across external site PTC.com for video content A. Results display by:

• Thumbnail image measuring 160px width by 90px height (same as existing Non-Homepage Media Wrapper thumbnail image size)

• Title • Description • URL

REQ-12: Security - See Accessing Secure and Form Protected Content (Section 3.4) REQ-13: Images A. Splash Image - Acceptable dimensions are the same as existing splash image in

the videos content group: 704px wide; 396–704px tall. B. Thumbnail Image - Acceptable dimensions are the same as existing thumbnail

image in the videos content group: 160px wide; 60–240px tall. C. Featured Video section Image – displays at 240px width by 135px height.

REQ-14: Downloads - User should have the ability to download and save all corresponding downloads for flv files from all browsers. They will be available from non-homepage Media Wrappers, Library pages and Unique URLs. A. Corresponding downloads for flv. Users may download and save files by clicking

the MOV, WMV buttons. B. Download files will be hosted on Akamai REQ-15: Form Protected Content A. Video Library will be added to the category called Include Availability. Video

Library and Product Page will be used to display videos in a certain area. Determining when to display an access form before a video on ptc.com will be built into WCMS. If a video is tagged for the Product Page using the Include Availability keyword, it will appear there whether it is supposed to have an access form in front of it or not.

B. The ability to multi-select will be available. For example, include availability to both the Video Library and the Product Page will be available.


3.2.2 Internal Videos Content Group: There will be a separate content group for internal (PTConnector) video. This will be a catch all place for all internal video. There will be templates for flv, wmv and mini-sites.

REQ-1: all video content for Internal (PTConnector) will be in the Internal Videos content group.

REQ-2: The Real Media Server is going away A. the media server will no longer be used B. files will be hosted on Akamai Content Distribution Server REQ-3: Templates - There will be templates needed for the following content types: A. flv B. embedded wmv C. mini-sites or file collections

REQ-4: Uploads similar to the current presentation replays content group A. Mini-Sites - For mini-sites or file collections, the ability to upload multiple files

such as mov, html, flash, swf, Mpg4 as a package similar to the existing presentation replays content group is needed.

B. WMV – The ability is needed to upload files for wmv that will be embedded and opened in a modal. There may be corresponding files that will be available for users to download and save such as MOV and WMV by clicking corresponding buttons

REQ-5: Unique URL A. Scaled down version is needed for conferencing purposes, It will be just a URL of

the video and it will play it won’t have header, footer, navigation, related videos, downloads, share, chapters, captions, call to action etc…

B. Unique URL like external ptc.com Player size: same as the non-homepage media wrapper on PTC.com. Height: 288px by width: 512px. Related Videos section links go to unique urls. FLV Unique URLs and Embedded WMV Unique URLs appear in the Related Videos list:

1. FLV: like External Unique URL Call to Action, Downloads, View at larger size, Share, Captions, Chapters will be available.

• Splash image will be the same size as external. • Thumbnail image will be the same size as external.

2. Embedded WMV: The only control available is downloads (WMV and MOV).

REQ-6: The Internal Video Library Page (see External Video Library page: section

3.2.1 REQ-2) will be a home for all video Internal and External A. Ability to filter and search internal and external content is needed. B. Featured or Promotional area – The Featured video area will be for flv only.

Videos in this section will be determined by priority in wcms, if no priority is set then videos in the featured section are determined by most recent. Owners of the content group may set priority. In the results that are not featured results, the speaker displays, with title and description. 1. The promotional Area will have an image displaying at 240px width by 135px

height. 2. The title will display below the image

C. Results: videos results default by date before the user has made any navigator modifier or tag cloud selections and before the user has performed an on page


search. The General results not featured in the promotional section appear below the section and display by: • Thumbnail image (for flv content only) measuring 160px width by 90px

height (same as existing Non-Homepage Media Wrapper thumbnail image size)

• Title • Speaker • Description • URL :where result is not opening a modal (mini-site and external flv)

D. Modal - Selecting an flv or wmv result, or a featured video, opens a modal with a

player. Player is the same size as the player on the homepage of ptc.com height: 396px width: 704px1. A Splash image is required for Flv only. The existing splash image size 704px

wide; 396–704px tall may be used for player in the modal.

. See external library page modal for controls.

E. Navigators/Modifiers – Filtering and WCMS Categorization see References 1.3 section G: 1. Site

• Internal • External

2. Product 3. Department and Sub-Department 4. Categorization is needed for videos to appear on Department Pages and

Product Pages. F. Tag Cloud: User may filter selections by clicking words in the tag cloud. User

may deselect from the breadcrumb, by clicking on the “x”. The tag cloud and navigator modifiers are searching the same content group on the page. Select by a cloud and a modifier at the same time. The selections will be indicated in breadcrumb. Tags will be based on:

1. Content on page 2. Keywords 3. Body text 4. Video captions

G. On Page Search REQ-7: Site Search: ability to search across multiple content groups and return video

results for internal and external (see 3.2.1 REQ-10 External Site Search) A. Video results display:

• Thumbnail Images - Internal and External flv only • Title • Description • url

REQ-8: Homepage of PTConnector – Widget for video search on homepage like

address book. Users may turn it off, but by default it is there results go to site search results page. Add Videos to PTContent list.

REQ-9: Security - See Accessing Secure and Form Protected Content (Section 3.4) A. For anonymous access videos, content must be expired B. Partners will need access to internal video content C. Form content will be indicated by a graphic


REQ-10: The ability to set “Include Availability: None”. Categorization will exist in order to exclude videos from appearing on the video library pages. It would be for rare instances when you need to exclude something like intros to specific pages (called 101 videos) and it wouldn't make sense for them to be on the library page. REQ-11: Downloads – The corresponding downloads for flv files will be available to

users to download and save and will be hosted on Akamai. (See external videos content group)

REQ-12: Call to Action REQ-13: Images – Images required for flv content A. Splash Image - Acceptable dimensions are the same as existing splash image in

the videos content group: 704px wide; 396–704px tall. B. Thumbnail Image - Acceptable dimensions are the same as existing thumbnail

image in the videos content group: 160px wide; 60–240px tall. C. Featured Video section Image – displays at 240px width by 135px height.

REQ-14: All downloads available from Video Library pages and Unique URLs should be available for user to download and save from all browsers. A. Users may download and save files by clicking the MOV, WMV buttons. B. files will be hosted on Akamai REQ-15: View at larger size from Video Library page and Unique URLs. See

External Videos Content Group REQ-16: Captions See External Videos Content Group REQ-17: Chapters See External Videos Content Group REQ-18: Content Submitters/Approvers (TBD) REQ-19: Department (Department Content Group) and Product (Product Information

Content Group) pages - See section 1.3 References section A (Use Case Diagrams and Wireframes: 5.0.0)

A. There will be a videos box with thumbnail image if applicable, title and URL if it is a page instead of a modal.

B. In the Videos box, there will be 3 items with a more link. The user clicks an item and is brought to a Unique URL. Inside the box items display : 1. Flv: has thumbnail image and title 2. Embedded Wmv: no thumbnail image title only 3. mini-site: no thumbnail image title only

3.2.3 Presentation Replays Content Group:

REQ-1: All video content will be moved to the Videos content group. Going forward the Videos Content Group will be used for all video content on ptc.com.

REQ-2: Conversion of existing video content according to guidelines. See References section SRS 1.3, E of this SRS.


REQ-3: Content Placement: Currently most of the content placement actually depends on the forms content group, not the presentation replays content group. It goes by: • Product/product group • security for maintenance customers

3.3 Universal Search

Google, Yahoo, Bing, etc... Optimize for Google it is 80%. REQ-1: Video Results take the user to PTC.com Unique URL REQ-2: Improve search engine optimization for video content A. title B. description C. author D. meta keywords E. Captions or subtitles for video will be used, in an external file to make video

content more easily indexed and more searchable.

3.4 Accessing Secure and Form Protected Video Content

See section 1.3 References: Section A - Use Case Diagrams and Wireframes: Flowchart 1 and 2, and Section D - Accessing Marketing Assets on PTC.com – basic and detailed account creation Use Case: Accessing Form Protected and Maintenance Content on PTC.com from the video library page

• On the video Library pages Internal and External the user clicks content in the results list indicated by a key graphic

• They are brought to authenticate on a login page • User is brought back to library results page with the modal open of the video

they clicked on

REQ-1: Secure Video Content - Maintenance Content Some Video Content will only be available to paying account users. Users will only see secure video content if they have an account and are signed in. Who sees what content is based on permissions. LDAP accounts. User accesses Secure Video Content from:

• Non-Homepage Media Wrappers on PTC.com – Yes if logged in and have an account. Not shown to anonymous users.

• Video Library Pages - Internal and External Yes, it will be indicated by a key icon in the results list on external

• Site Search Results Pages - Internal and External – yes indicated by a key icon in the results list on external

• Unique URL or deep link -yes • Internal – Department and Product Pages - yes

1. WCMS

1. Activate and Expire during that particular time. 2. Video content group has security built into step 2 for accounts.


2. Downloads for corresponding flv’s (WMV, MOV) will not be available for secure content

3. Security based on the referrer is required for Support content REQ-2: Form Protected Content If there is a form in front of an item it appears in the media wrapper with no form and the form only appears in front of the unique URL (deep link). A. WCMS – Video Library will be added to the category called Include Availability.

Video Library and Product Page will be used to display videos in a certain area. Determining when to display an access form before a video on ptc.com will be built into WCMS. If a video is tagged for the Product Page using the Include Availability keyword, it will appear there whether it is supposed to have an access form in front of it or not. The ability to multi-select will be available. For example, include availability to both the Video Library and the Product Page will be available.

User accesses form protected content from:

• Non-Homepage Media Wrappers on PTC.com – form protected content is in media wrappers without the form

• Video Library Pages Internal and External – yes • Site Search Results Internal and External – yes • Unique URL or deep link - Yes • Internal – Department and Product Pages – No

REQ-3: Use Cases for form protected Content A. Use Case (level 1 - high level): 1. If user has account and is signed in, user accesses content 2. If user has account and is not signed in, login screen, user signs in with username

and password and accesses video asset 3. If user does not have an account, user creates account profile, user answers

questions, and accesses video asset 4. A visitor whose 90-day cookie has expired

• Fills in username and password • Verifies pre-filled form, correcting any information • Presented with asset

B. Use Case (level 2 – high level): 1. If user has level 2 account and is signed in, user accesses content 2. If user has level 2 account and is not signed in, login screen, user signs in with

username and password and accesses video asset 3. If user does not have an account, user creates account profile, user answers 5

custom questions, and accesses video asset 4. Level 1 account-holder who is logged in

• Edits contact information and answers 5 custom questions • Presented with asset

5. Level 1 account-holder who is NOT logged in • Fills in username and password • Edits contact information and answers 5 custom questions • Presented with asset

6. A visitor whose 90-day cookie has expired • Fills in username and password • Verifies pre-filled form, correcting any information • Presented with asset


3.5 Captions (Subtitles)

Captions or Subtitles will be an overlay at the bottom of the video. The purpose of having captions is for language translation, for search engine optimization, and to make video content more accessible. The Flowplayer captions plugin will be used. There will be an upload feature in WCMS content groups to upload an external captions file and fields in WCMS videos content group to create captions. From the perspective of indexing and SEO having the media transcript separate from the media itself is the preferred method over “embedded” captioning, because it makes video content more easily indexed and more searchable. Captions will be available for internal and external video.

REQ-1: The ability will exist to upload an external file for captions if there are xml or

text files that contain captioning data and that are exported from video creation software.

A. The web team will require a DTD (Document Type Definitions) or a document

defining the elements in the file from the WCMS user. The DTD will only be required 1 time.

REQ-2: If the video does not have corresponding XML, the ability is needed to Add, Remove, and Edit from the CMA (WCMS).

A. Add caption B. Edit caption C. Remove caption D. Timestamp information

1. Start time 2. End time 3. Duration

E. There will be open text fields in the CMA to enter captions.

3.6 Chapters

Some video (where applicable) will require chapter lists and corresponding navigation elements. One video may contain several chapters. The chapter list will show chapter number, chapter title, description and time-stamp. Chapters will be available for internal and external video.

REQ-1: Existing XML - Upload Feature is needed in both content groups for existing xml or text files that contain chapter data and that are exported from video creation software.

A. Chapter information will be pulled like timestamp, and name of chapter. B. Determine the formatting for timestamp for example: hh:mm:ss C. The web team will require a DTD (Document Type Definitions) or a document

defining the elements in the xml from wcms user uploading an xml. The DTD will only be required 1 time.

REQ-2: If the video does not have corresponding XML for chapters, the ability is needed to Add, Remove, and Edit chapters from the CMA (WCMS). A. Determine the formatting for timestamp hh:mm:ss B. Add/Remove chapter C. Edit chapter


D. Title of chapter – text entry E. Start time F. End time hh:mm:ss G. Chapter duration REQ-3: User Experience: The Chapter list appears directly below the player and would not appear if there are no chapters for a video. A. DHTML dropdown or YUI split button to open and close chapter list B. Selected chapter is indicated visually REQ-4: Flowplayer A. Flowplayer seek function will be used for chapters. Seeks to the specified time of

the current clip, in seconds. When using streaming server, it is not necessary for the buffer to have loaded to the point of seeking.

3.7 PTC Internal (PTConnector)

REQ-1: Display streaming video on PTConnector without directing user to ptc.com or requiring users to download a player or files. Files will be hosted on Akamai streaming server.

A. Streaming video FLV 1. FLV file is required. Any other file type must be manually converted to FLV

to play in media wrapper. Video will display with black bars "letterbox" scenario when s a different aspect ratio besides 16:9 is used. See References Section 1.3 Video guidelines for more details.

2. The wrapper uses Flowplayer and will be embedded in the page or modal. 3. If the aspect ratio of original is not 16:9, it will have black bars. 4. The flv is uploaded manually along with any applicable, corresponding WMV

or MOV files to be available for download. 5. Share – Currently the email function of Addthis goes to the junk folder

internally because of the addthis address. The spam filter may need adjusting internally.

B. WMV 1. Not streaming. http progressive download 2. Will not play in Flowplayer 3. hosted on the Akamai content distribution server 4. The ability will exist to upload WMV files through WCMS for internal use

only. The WMVs will be used for embedded WMVs. This feature will be similar to how the Presentation Replays content group on external. 10MB allowed

5. No thumbnail or splash images 6. Embedded in a unique url

C. File Collections or Mini Sites The common publication tools are Camtasia, Articulate, and some Adobe Captivate. Articulate offers the most options to deliver a mix of interactive content (movies, file delivery, interaction, localizable UI, presentation search ability, etc.)

1. .mov, mpg4, html, .swf, .flv, etc… 2. Articulate and Adobe Captivate files have their own wrapper 3. No streaming 4. use functionality for upload like the presentation replays content group 5. No thumbnail or splash images 6. Will not play in Flowplayer


REQ-2: Internal Video Library Page – The video library page will be a home for

Video like on ptc.com (See requirements for external video library page 3.1.2 REQ-4) and section 1.3 References section A (Use Case Diagrams and Wireframes: 1.1.0). Users may navigate to this page by Content Type/Video Internal Video types:

• Internal flv: modal • Wmv: modal • mini-site: page • External flv: page

A. Featured Video or Promotional area - There will be a promotional or featured

area. For Internal only flv video may appear in the featured video section. It will be used to highlight 3 videos. This area will have 3 images with the title displaying underneath and user clicks to open a modal with a player. Only title and image display. The featured items are determined by setting priority in WCMS. If none set it is by most recent. Because of where the prioritization is stored in the database for WCMS, it can be integrated with fast. Modals have players that are 704px wide; 396px tall. See External video library page for controls available in the modal.

H. Results: videos results default by date before the user has made any navigator modifier or tag cloud selections and before the user has performed an on page search.

1. Results display in a paginated list in increments of 10 by default. 2. Results will include:

• Internal Videos o Internal flv: modal (indicated by a graphic) o Wmv: modal o Mini-site: page

• External Videos or ptc.com o unique urls

3. The General results not featured in the promotional section appear below the section and display by: • Thumbnail image measuring 160px width by 90px height (same as

existing External Non-Homepage Media Wrapper thumbnail image size)

• Title • Speaker • Description • URL if applicable

B. Navigator/Modifiers - Filter by: 1. Site – Internal and External 2. Department 3. Product

REQ-3: Internal Site Search Video Results– The ability will exist to search across

multiple content groups. Internal and external video will be returned in the results. Results should pull Meta description or wcms description. - See section 1.3 References section A (Use Case Diagrams and Wireframes: 3.0.1)

A. Internal - ability to search across content groups internal and external and return video results.

B. improve Keywords/Meta Description


1. 2 gigs worth of keywords are allowed C. Search Criteria:

1. search collections: limit to search within a collection in search appliance 2. Title 3. Description 4. Author 5. content group or wcms categories 6. captions or subtitles

D. Results will include: 1. Internal Videos

• Internal flv: unique url • Wmv: unique url • Mini-site: page

2. External Videos or ptc.com • External unique urls

3. Results may be narrowed by • Site (Internal/External) • Department • Product

E. Results: improve user experience how results display. 1. Results display in a paginated list in increments of 10 by default. 2. Navigators are the headings 3. A list of up to 5 modifiers displays under each navigator. Six modifiers will

display only if there are a total of six. 4. If there are seven or more modifiers under a navigator, five modifiers with the

word more and an arrow will display to expand the rest of the list when toggled.

5. The number of results is displayed in parentheses after each modifier. F. Number of results found will display but not the number for seconds it took to

return results. G. Search terms are highlighted H. Add images for video results for flv results only – use existing thumbnail image

size 1. currently images are created and uploaded manually and separately

REQ-4: Unique URLS A. A URL of direct link to the video. It plays automatically and will be sent out for

conferencing purposes. 1. No PTC stuff like header, footer, other links, navigation, No related video

section, downloads, share or view at the largest size, chapters, captions or call to action, etc…

2. url auto generated 3. send streaming with bandwidth checking template url to video 4. only anonymous access videos would play 5. set start and end time/expire 6. plan for existing content - go thru old content items to find owner 7. Unique Url will be sent to conference users, it’s ok if users are not in sync as

long as it’s streaming and the video just plays

B. Unique URL like ptc.com - See section 1.3 References section A (Use Case Diagrams and Wireframes: 2.1.0 and 2.1.1) 1. Related video section – for flv video content only 2. Player is the same size as external site: height: 288px by width: 512px


3. For flv and wmv only • Flv – same as ptc.com (see External Unique URL section 3.1.3 ) • Wmv – It will be embedded in an object tag. Looks the same as

flv but does not have: related video section downloads, share or view at the largest size, chapters, captions or call to action, etc…

4. Mini-Sites have their own html page and do not have does not have: related video section, downloads, share or view at the largest size, captions or call to action, etc…

REQ-5: Department and Product pages - See section 1.3 References section A (Use

Case Diagrams and Wireframes: 5.0.0) A. There will be a videos box with thumbnail image if applicable, title and URL if it

is a page instead of a modal. The Videos Box will appear in Alphabetical Order on the page.

B. Inside the Videos Box there will be 3 items with a more link, following current behavior: 1. Flv: has thumbnail image and title 2. Embedded Wmv: no thumbnail image just title 3. mini-site: no thumbnail image title 4. No form Protected content

C. User is brought to unique URL when accessing an item in the Videos Box REQ-6: Video hosted on Akamai A. Move content from media server B. WMV content will be hosted on Akamai content distribution server, it will not

stream. C. FLV content for media wrappers will be hosted on Akamai streaming server REQ-7: Conferencing video for use with LiveMeeting or Goto meeting. The video

plays in a shared meeting, and speakers talk over it. A. The Media Server is where files were located. It will no longer be used. B. Files will be hosted on Akamai. C. Preferred way would be wmv upload into wcms. (wmv may be converted to other

file types such as FLV as necessary) D. maintain quality when compressing E. For streaming video, to play in media wrappers files are required to be converted

to flv with corresponding WMV download available if applicable. F. file size: most current LiveMeeting files are under 10mb 80% are 1 hour or less G. Available for Internal use only - not outside of ptc.com H. Partners will need access and have access to internal.

REQ-8: Homepage of PTConnector – Widget for video search on homepage like address book. Users may turn it off, but by default it is there results go to site search results page.

3.8 Email

REQ-1: General emails A. email links to unique URL page on ptc.com


REQ-2: WCMS emails (such as here is your Requested info) A. email links to unique URL page for video content B. splash images for video in the email C. interactive content 1. Flash 2. Video 3. Twitter streams 4. Invites to connect to PTC Facebook fan page D. User Experience

3.9 Software Upgrade Flowplayer

Upgrade to latest version software and license.

4. Other Nonfunctional Requirements

Appendix A: Glossary Animation: Falls under the general label media General file type: SWF May or may not be interactive Usually has associated xml files, in cases where there is translated text Icenter Content: standard demonstrations delivered over the web by expert pre-sales resources. Image: a still graphic or photo to be displayed in the media wrapper. General file types GIF, JPG, PNG, etc… Home Page Media Wrapper: Exists only on the ptc.com homepage Media: Referring to any or all Video, Images, and Animation Media Type: Kind or category of media. It could be Video, Image, or Animation Modifiers: Under navigator categories used to filter results on site search results pages and video library pages. Determined by wcms categorization and fast search Navigators: Categories which have modifiers used to filter results on site search results pages and video library pages. Determined by wcms categorization and fast search


Non - Home Page Media Wrapper: Any and all media wrappers except for the Home Page Media Wrapper Presentation Replays Content: Content that was formerly in the Presentation Replays content Group. For example: Demos, Tech Tips, and Web Casts Single Sign-On: IT Project replacing the current form process. User creates an account and answers questions one time, creating a profile instead of filling out forms each time to access secure or form protected content Splash Image: Still image usually at the beginning of a video. Sometimes displays a “play” icon. User clicks on it to play a video TBD: To Be Determined Thumbnail Image: Small image used for navigation or to select another Image, Video, or Animation to be displayed in non home page media wrappers only Video: Falls under the general label media General file type: FLV May have associated downloadable versions of a different file type such as MOV or WMV Video Types: A type of video there are 3 main types described in this SRS

• Marketing Videos: will be labeled Company

• Demos: full Demonstrations

• Tech Tips: shorter clips, not a full demonstration

• Support Videos: Tech Support videos fall under this heading

Appendix B: Future considerations A. Embed video in an email B. Social Media Features for video content when Jive is implemented or when there

is an existing definition of how Jive will work. Internally we can already do Rate this Page and Favorites

A. Comments will not display in a modal B. Number of views - “Views” may not make sense if a video is only viewed

3 times in 2 years. It may hurt us, not help. But it may also show us if a particular Demo or Video is not good content.


C. Ability to add to a Favorites list available to account users. Similar to PTConnector

D. Rating - For Internal and External video, from non-homepage Media Wrappers, Library pages and Unique URLs the ability to rate video is needed. Jive may be doing this but we cannot extract out a piece of technology from Jive, though we may follow similar standards for user experience, look and feel, etc…if they are known. Rating may be similar to star rating currently on the internal site (PTConnector). The user has the option to rate from 1 to 4 stars. The average rating is displayed along with how many users rated the item. Possibly reduce the number of stars from 5 to 4 to eliminate the middle which is a neutral rating. If rating is going to affect search results, associate video to search terms to ratings. External site (PTC.com) – all videos will need rating feature. Internal site (PTConnector) – only flv will have rating feature. (TBD)

C. Automated process for converting files A. Upload a file to WCMS and it would convert automatically to 3 formats

flv, wmv and mov. This process is currently manual B. Build a watch folder to be pulled from WCMS C. Use Final Cut Server in the future

D. Provide alternative access for video via RSS for mobile devices. Make format available for mobile devices to be put on iTunes store or available for download or on ptc.com would not be available for BlackBerry.

A. Providing access to a mobile friendly format delivered via rss B. creating H.264 files for the FLV videos C. Hosted on Akamai D. Accessible for both internal and external E. Audience: PTConnector (internal) users and partners

G. Transition period for moving from the current Presentation Replays content group to the External and Internal videos content group: REQ-1: Old Content from the presentation Replays Content Group: decision regarding what is expired and what is moved over: For example customer care newsletter, WF3 and below, Nancy P.’s Newsletter REQ-2: remaining marketing content in the presentation replays content group owners? REQ-3: other remaining video content besides presentation replays, (Demo Catalog temporary repository, all content is available here)

H. Image Creation: currently images such as thumbnail and splash images are created and uploaded manually and separately. In the future use ffmpg2 available for windows and Linux

I. Batch process for converting files from WMV to FLV A. Server side B. Manual conversion by the Web/Video team