View source for W:SLDB

{{WST}}
{{:W:ProjectsM}}

=!!! UNDER CONSTRUCTION  !!! =

* How do you let people know what stuff you have and where your stuff is?
* Suppose we're looking at a 'piece of stuff' that you wanted to syndicate content across institutions, then what sort of metadata would you need to exchange in order to be able to build a common repository? 

= A description of the ScienceLive Syndication and Federation tools =

The first question is discussed here [[resource discovery]]. For the 2nd question see [[Using media rss to syndicate and share media]].

== Multiple use ==
[[Image:portal use at institution.png|400px|thumb|Reusing the same portal software for a range of purposes. (Click image for larger version.)]]

We use the terms "portal" and "web front end" synonymously: This is a portal software, that is fed through 
* one or more video servers (such as PCP or replay)
* or from a metadata hub (such as Oxitems in Oxford, the mediaplayer architecture in Cambridge)
The same portal software is reused across an institution and elsewhere, for a number of purposes:
# To build an institutional portal ("All/Selected videos from Oxford University", "CamTV", etc.)
# To build departmental portals: Departments pay for having their own videos produced, and they should be able to have these in the context of their website, integrated with their content management system.
# To build special interest portals within an institution ("Cambridge Environmental Initiative" may want to collect videos related to the environment, again within their web content management system)
# The same portal software can also be used to build national / international / special interest portals, such as "UK HE national video portal", "National video portal for teachers", "Science Engineering Technology Medicine videos", "All videos from OpenCast partners" etc. 

As a practical example, we are using the same portal software to build
* CamTV/mediaplayer: An institutional portal for Cambridge University http://mediaplayer.group.cam.ac.uk
* A national portal http://podcast.steeple.org.uk, syndicating media from Oxford, Open University, UCL, and Cambridge
* A subject-based portal http://www.sciencelive.org .



= Why this is relevant =
[[Image:Portal_use_at_institution.png|Various uses for portal software|320px|thumb]]

The ideas described on this page are relevant, because we're using them for two projects:
* CamTV: http://mediaplayer.group.cam.ac.uk
* Steeple podcast portal: http://podcast.steeple.org.uk

The portals contain about 7500 data sets, and we need to have a good syndication standard to be able to share metadata efficiently.

More info about portal ideas: http://www.steeple.org.uk/wiki/Portal
* http://www.steeple.org.uk/wiki/Portal/Design_criteria_for_portal
* http://www.steeple.org.uk/wiki/Portal/Requirements_gathering

[[Image:EnsembleOverview.gif|320px|thumb|link=http://www.steeple.org.uk/wiki/Ensemble]]

= Links =

{{syndication}}

Dublin core, OAI, ORE:
* http://www.openarchives.org/
** http://www.openarchives.org/ore/1.0/atom
** http://www.openarchives.org/ore/1.0/toc.html
* http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects/LinkingOpenData
* http://gondolin.rutgers.edu/MIC/text/how/mpeg7_dc_map.pdf
* http://dublincore.org/documents/dcq-rdf-xml/
* http://www.intertwingly.net/wiki/pie/Rss20AndAtom10Compared

Feed history:
* http://www.ibm.com/developerworks/xml/library/x-extatom1/
* http://www.mnot.net/drafts/draft-nottingham-atompub-feed-history/draft-nottingham-atompub-feed-history-01.txt
* http://www.ietf.org/rfc/rfc5005.txt

{{portal}}

= Web front end ("portal") =


== Program ==

Programmatically this needs to be done:
* [[/metadata/|Agreement on metadata]]
** What information needs to be transferred between the 'encoding core' (such as pcp or replay) to the (institutional web portal)
** How should this be bundles in a feed format (RSS+media, Atom+media, ...)
* [[/Database design/|Database design]]
** How is the feed information stored in the database? A database may not be necessary for smaller numbers of items (< 50), but for larger amounts (institutional portal, 2000 items) buffering in a database is needed.
** [[/Choice of technology/]]
* [[/Web application/|Designing the web application]], that presents the videos to the user
** [[/Design criteria for portal/]]
** [[/Choice of technology/]]

== Examples of Educational Video and Audio portals ==

Also see -

** [[/Choice of technology/]]
* [[/Web application/|Designing the web application]], that presents the videos to the user
** [[/Design criteria for portal/]]
** [[/Choice of technology/]]

== Existing systems ==

* CamTv, ScienceLive, Steeple Portal all use the same technology
* Miro communities
* Inspired by the present work via Steeple, ... 

== Licensing ==

As a meta question: What license would the portal software need to have to achieve wide buy-in?