Source: oma
Section: unknown
Priority: optional
Maintainer: Thomax Goettlich <thomax@icf.de>
Build-Depends: debhelper (>= 4.0.0), make, apache2-common (>= 2.0.49), apache2-mpm-worker (>= 2.0.49), libapache2-mod-perl2 (>= 1.99.12), libdbi-perl (>= 1.41), libdbd-pg-perl (>= 1.32), libdbi-perl (>= 1.41), libmime-perl, libxml-parser-perl (>= 2.34)
Standards-Version: 3.6.0

Package: oma
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: Open Meta Archive
 First of all, the archive is a set of database tables which
 is used to describe digitized media data. The description
 of the media data is called meta data. Both, media and meta
 data are organized through the archive. The archive has
 several human-machine and machine-machine interfaces which
 let you import, find, change, list and export media and meta data.
 .
 The meta data concept we use is based on the
 http://dublincore.org standard. All data are arranged in an
 expandable and open tree. Content input for the archive are
 provided by the contributors and the playout system.
 The contributors can use two interfaces for upload new data
 to the archive, the playout system is a special kind of
 contributor. It provides the media data on a local disk
 storage and points to the scheduler as a meta data
 repository. This is useful for automated archiving. 
 .
 http://oma.sf.net/

