Tender DHP Agency Brief (DOC, 1.42Mb)

Click here to load reader

  • date post

    06-Sep-2014
  • Category

    Technology

  • view

    497
  • download

    3

Embed Size (px)

description

 

Transcript of Tender DHP Agency Brief (DOC, 1.42Mb)

  • 1 DIGITAL HERITAGE PROJECT AGENCY BRIEF ScreenEast SE/DHP agency brief 23.2.10
  • 2 1. Project outline 3 1.1 Background 3 1.2 Contacts 4 2. Functional specification 5 2.1 Functional overview 5 2.2 Site structure 6 2.3 Content management 7 2.4 User interactivity / comments / upload 8 2.5 Keyword search 9 2.6 Timeline functions 9 2.7 Mapping functions 10 2.8 Building larger articles 10 2.9 Language packs 10 2.10 User login and handling 11 2.11 Mobile, IPTV and GeoPoint applications 11 3. Technical specifications 12 3.1 Video specifications 12 3.2 Server / bandwidth specification 12 3.3 Compatibility 13 3.4 SEO specification 13 SE/DHP agency brief 23.2.10
  • 3 1. Project outline 1.1 Background Screen East (www.screeneast.co.uk) is the regional screen agency for the East of England, dedicated to promoting the film and TV industry in the region, and communicating the value of film and TV to the public. As part of this work, Screen East works extensively with screen heritage material for research, education and public interest / entertainment. Screen East financially supports the East Anglian Film Archive (owned by the University of East Anglia) where the film collections are held. Given the recent evolution of online video and a wider project to digitise more of the Archives material Screen East has recognised the need to make archive material more accessible to the public, through a video-enabled web site as part of the Digital Heritage Project. To facilitate the projects delivery and secure funding from the INTERREG IV A European pool, Screen East has teamed up with Ple Image Haute-Normandie (www.poleimagehn.fr), which supports all audiovisual activity around their region. They have been vital in offering technical guidance and will be working extensively with Screen East to achieve our common goals. While initially the idea of one site to serve both SE and PIHN was mooted, following discussions PIHN will continue to construct and provide their own site and functionality, as this will give them greater access to local government facilities at CRIHAN in France and allow them to create a site more specific to their needs. However, it is planned to co-ordinate some aspects. For example will run Flash video, for example, use a common screen resolution and ratio. Education programmes will be co-ordinated across the two regions. And it is planned to choose one video editing tool for use by the public (see 2.11 and separate video edit suite tender doc). SE and PIHN will also share common branding and styling for their two sites. A branding document, comprising logotypes (in English and French), typeface instructions, colours and basic styling guidelines, will be supplied at or about the date of commencement of full build. SE/DHP agency brief 23.2.10
  • 4 1.2 Contacts In the first instance please contact: Lance Paterson / l.paterson@screeneast.co.uk Technical consultant / ScreenEast Screen East, 2 Millennium Plain, Norwich NR2 1TF For ref: Jane Jarvis Screen East / j.jarvis@screeneast.co.uk Project manager, Digital Heritage / Screen East SE/DHP agency brief 23.2.10
  • 5 2. Functional specification 2.1 Functional overview Any candidate bid should fulfil all of the following functions: - be attractive, reasonably accessible, searchable, and easy/intuitive to use - deliver user-friendly video at good download speeds and reasonable quality - allow content management of the video and material surrounding the video, including but not limited to: o a full but simple and searchable tagging schema o allow text and pictures to be uploaded to sit beside video, turning it into a full article page o allow geo-tagging and mapping (via Google or Live) so that clips can be placed in geographical context (eg: jump to modern Street View), and nearby clips displayed o allow a for a time tag that will place the clip in a relevant historical timeline - allow moderated comments by users (login required) - provide a simple suite of social networking tools to allow users to share and link to video - allow users to form and join groups and forums based around content interests - allow access via mobile devices and IPTV The ability for users to upload, and possibly edit, their own clips on the server is currently still under discussion but should be discussed in any candidate bid. A separate bid document has been issued for an editing suite system that would allow users to edit together or sequence clips for educational purposes. This would be used by both SE and PIHN. Note that while SE are currently planning to use this feature as a site attractor, PIHNs version of this system will be orientated more as a structured educational tool. SE/DHP agency brief 23.2.10
  • 6 2.2 Site Structure As this is envisaged as a fully or partly CMS-driven site (see 2.3), the Topics section and menu could be fully or partly auto-generated. The page and menu based on keywords or keyword groups. If a drop down menu is used, the number of topics available will be limited to avoid visual overload, with a clear invitation to see more. Timelines could be broken down into decades or into relevant periods (eg: birth of film to WW1, 1840-1919, inter-war period 1920-1938, war and recovery 1939-1950) These could be placed on a CoverFlow timeline app, with videos signposted along the time axis. Places could bring up an interactive (Google?) map screen centred on the selected target area, with videos shown as pins or icons. Selecting one would bring up an info bubble with a link to the clip. Education would feature a link to the timeline editor / video compiler, historical education sections, and if possible a small film school section looking at the history of film making. Forums (or Groups) would give people a chance to interact with each other and discuss local history and film, ensuring the site is sticky and users have an additional reason to return. The About tree (and page-base links) would cover all other necessary items like Contact, legals, etc etc. SE/DHP agency brief 23.2.10
  • 7 2.3 Content Management System The CMS should allow for the upload of video and preferably its auto- encoding by staff, and possibly by users. Each video should then have its own SEO-friendly display page with the following: - Video title - Video - Notes and information - Author details if available - Timeline details - Keywords linked to relevant searches for that clip - Mapping function - User comments field and user comments - Tag cloud Each of these elements should feature on a single edit page for the clip and be as simple as possible to upload and edit. If possible, the video upload itself should also be conducted as part of clip creation. Ideally, the notes and information section should support TinyMCE or similar for basic formatting of text. Text should be limited to default font sizes and faces only, but bold, italic, linking, paragraphs, bullets, image insertion, and other simple tagging should be supported. Image upload should be available either on this screen or via a separate screen. If possible, auto-resizing (using WebMagick or similar) should be enabled to help staff and users keep to a standard template. Finally, if possible, the CMS should allow functional modules to be enabled/disabled/added/removed/moved via an AJAX type interface. This will allow one CMS to build a greater variety of pages via a modular system. It is suggested that clip information be held as XML, allowing easier transformation for functions such as mapping or timelining. SE/DHP agency brief 23.2.10
  • 8 2.4 User interactivity / comments / upload SE wish to encourage users to share and interact with the available content as much as possible. Therefore the site should support a reasonable range of Social Media functions, such as: - send to a friend - add to Facebook (see note below) - submit to Digg, del.icio.us, LinkedIn, Google Bookmarks, reddit and other social bookmarking services - submit to Twitter (using shortform link service if possible) Please note that a full Facebook Connect integration is not required for this project and should not be quoted for, as development timescales / costs are excessive for the relative needs of this project. Users should be able to enter comments about each clip. Registration and login would be required and comments would be post- moderated (ie: comments are not published immediately. Instead, a notification would be sent to a site moderator that a comment was waiting for publishing. Moderator can then decide whether or not to approve comment based on relevance.) If budget is available, users should be able and encoura