Clipper on the Road – CILIP Scotland Multimedia Group – The National Library of Scotland

I attended at meeting of the CILIPS Multimedia Information and Technology Group on the 27th May to hear a presentation from the National Library of Scotland to hear a presentation about plans to create a new moving image center at the Kelvin Hall. It was one of those chance things…my boss (Jennifer Louden, Librarian at Glasgow City College) told me about the meeting. The meeting was at the Mitchell Library in Glasgow  a grand example of a Carnegie Library.

The National Library of Scotland is creating a new moving image center at the Kelvin Hall site in Glasgow together with Glasgow University and other organisations as part of a multi-million pound development as I listened I though the Clipper toolkit could really help with helping to enhance the access to the large digital film collection that is going to be sited there. I got talking to the Presenter – Gill Hamilton the Digital Access Manager from NLS and was able to give a short demo of the online prototype. Long story short…there was a lot of potential for collaboration so I will be getting on touch with Gill shortly.

John

HTML5 Video

HTML5 Video or Flash?

The first iteration of Clipper a few years ago was written using Adobe Flex as an installable Adobe AIR based application controlling Flash video. At the time Flash was the obvious solution for delivering cross platform video to the plethora of browsers out there. But then along came the iPhone and as I’m sure you’re aware, things changed. Enter HTML5 video. For the better? Yes. But…

We have still had to deliberate over the most efficient way to deliver video as universally as possible. Questions which need to be answered before adopting HTML5 video as the method of delivery are:-

  • Do the users have access to a modern browser?
  • If they are in a restricted IE environment, do they have at least IE9?

If the answer is yes to both of the above then HTML5 video is definitely the way to go. If the users are situated in a larger institution with a lethargic IT department they might well be limited to IE7 or worse. In which case Flash would still be the appropriate solution.

We decided to follow the trends of the majority of web development teams globally and think to the future rather than be restricted by the fewer and fewer institutions tied to old technology. HTML5 video will be the delivery mechanism of video for all future versions of Clipper.

What is HTML5 Video?

Do you remember the cartoon Hong Kong Phooey? If you were old enough to watch television in the 80’s you probably will and you will maybe remember Hong Kong Phooey had a helper called Spot the Cat. Spot the Cat did all the work and solved all the cases. Hong Kong Phooey got all the credit. HTML5 plays the role of Hong Kong Phooey in this particular episode. Let me introduce HTML5 video..

<video>
<source src=”path/to/video”>
</video>

That’s it. Apart from a couple of optional attributes that we can include, HTML5 has done its job. Over to you Spot the Cat to get the job done..

Spot the Cat

If you just want your users to play the video the following will do..

<video controls>
<source src=”path/to/video”>
</video>

Users will be able to stop and start the video. And go full screen. But for a tool like clipper we need to be able to manipulate and read the current state of the video playing in the web page. We need to load videos to be edited based on user search results. Spot the Cat deals with all this extra complexity and in this particular episode is played by the web developers’ old friend Javascript.

Happily these days the modern browser allows us to natively control any supported video using Javascript. When I say any supported video by the browser we do have to be aware that at the time of writing we will be requiring H.264/MP4 format for all browsers except Firefox which requires the OGG/Theora format. OK I’m ignoring Opera here. Anybody using Opera? Please let us know. You’ll see the Ogg videos anyhow.

http://www.quirksmode.org/html5/tests/video.html

This will be an issue to consider when an institution is at the point of encoding an existing library of videos into a web ready video library. It is obviously an important factor for us to consider with the more advanced stages of Clipper’s development when we will be developing an encoding service into the application. Maybe by then Mozilla will have talked themselves out of the patent issues of the MP4 format. What patent issues? Well when Apple, Google and Mozilla were trying to release the majority of web video from the proprietary clutches of Adobe, they all had their preferred ‘open’ video format solution. They were the following:-

  • Google – WebM
  • Mozilla (Firefox) – Ogg
  • Apple – MP4

Oh didn’t Apple make it clear. H.264 patent roster includes Apple along with Panasonic, Sony, Dolby, Thomson, and Toshiba. Big names indeed. To be clear on the issue of royalties here is a more comprehensive article discussing where the term ‘open’ comes from..

http://www.engadget.com/2010/05/04/know-your-rights-h-264-patent-licensing-and-you/

In my next post I intend to record our experience of 3rd party javascript libraries. Time saving frameworks which relieve the developer of cross platform issues? Theoretically yes. Actually not quite so clear cut. I’ll go away and take a deep breath first as we’ve recently decided that it can be a short term gain but long term headache.

The Research Data Lifecycle

The Research Data  Lifecycle

Access to the Clipper toolset will help overcome some significant obstacles in the research data lifecycle for time-based media and provide exciting new opportunities for researchers and data managers. Below we map the functionality of the toolset to the main parts of the Jisc research data lifecycle:

The JISC Research Data Lifecycle
The JISC Research Data Lifecycle

You can find out more about the Research Data Lifecycle at this link to download a PDF (see page 11) that also describes the JISC Research Data Spring initiative that we are involved in

  • Data Creation and Deposit
    • Plan & Design: – Access to the toolset may prompt new ideas for the initial design of research.
    • Collect & Capture: – Clipper has the potential for use with live audio/video streams to mark clips on the fly – (i.e. insert time stamps) and for fieldwork ‘off the grid’. This could support critical incident identification and speed up post capture analysis. The Clipper documents that are created can become new content in an existing repository / archive collection with the potential of being a source of new material support research
  • Managing Active Data
    • Collaborate & Analyse: – Enables effective ways of collaboration with time based media – researchers can work on the same data without altering the original – supports remote access. Access is under the control of the originating provider and the only material that is shared via Clipper is the metadata not the original, i.e. Clipper users and collaborators only see what they are entitled to see.
  • Data Repositories and Archives
    • Clipper documents are stored as W3C compliant HTML code – good solution for long term preservation, access and human / machine analysis.
    • Share and Publish: – New collaborative opportunities for using and reusing data including integrating with the social web. New Clipper content can be shared and published. Enables crowdsourcing of metadata and folksonomies. Provides a platform for researcher innovation
  • Data Catalogues and Registries
    • Discover, reuse and cite: – Enables remote access, analysis and collaboration. Reuse and citation become easier by providing web links to take the user directly to the reosurces. Clipper content can enrich existing catalogues, registries, collections and archives by producing user generated metadata based on existing collection content, this in turn becomes a rich set of data for analysis. Good opportunities for citizen science and research engagement, and capturing evidence of impact.

John