Metadata implementation spec
Contents |
Background information
Version 0.9 of the Transmission metadata standard is now available: here
Websites interested in implementing standard
Definitely interested
- Exequo
- Ifiwatch.tv
- Clearerchannel.org
- Engagemedia.org
- Transmission.cc
Video Platforms interested
- Plumi
Possible
- Filmforge project
- Show in a box - Word Press
What is involved in implementing the standard
If your project is being asked to implement the standard then the following information may help you decide how long it might take you and how much help you will need doing it.
Creating new / checking your metadata fields
While some feeds in the standard are optional, some are required. Part of the process will involve checking your database to make sure you have the relevant fields.
If not modifications will have to be make to your input forms, and database structure.
It is imagined that this is something groups will be able to do themselves.
Exporting a valid transmission feed
Modifications will have to be websites and systems to create the new Atom based Transmission Feed.
It is expected that some projects may need help with this aspect.
Importing valid transmission feeds
This is a vital part of the process. Some systems like Drupal have existing aggregation tool / modules , ie aggregator, and simple pie. It is not expected that these modules will work for the transmission feeds. So some customisation will be required to parse the feeds into the databases of different sites. Ekes is currently doing this as part of the ifiwatch.tv work.
This is expected to take some time depending on how familiar. It's hoped that assistance can be given to programmers wishing to make this work for this stage of the project.
Displaying the contents of imported feeds
It isn't expected that there is funding to cover this part of the process. However ifiwatch.tv uses a version of Drupal adapted to do so, at an initial level.
back to metadata_working_group
