#14 Extensible metadata support at import time

open
Jin
None
5
2010-04-06
2009-12-03
Anonymous
No

Allow user to run scripts to handle custom metadata extraction by adding extra config options to the import section of config.xml. For example:

[import hidden-files="no"]
[metadata-extractors]
[extract mimetype="audio/x-ms-wma" using-script=path/to/mediatomb/scripts/wma-extractor.py"/]
[/metadata-extractors]
[/import]

The patch allows users to specify arbitrary scripts or commands taking the file location as the single argument and printing lines "key:value" pairs to stdout. See wma-extractor.py for an example.

I plan on revising this patch as the current version is a bit of a hack. (e.g. metadata handling needs to be moved to a derived MetadataHandler class)

to test:
svn co https://mediatomb.svn.sourceforge.net/svnroot/mediatomb/trunk mediatomb-test
cd mediatomb-test
patch -p0 -i mediatomb_shell_based_extractor.patch
./configure --enable-metadata-extensions --prefix=/somewhere/useful
make
make install
/somewhere/useful/mediatomb

then try editing the config.xml adding relevant options

Discussion

  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2009-12-03
     
  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2010-02-16

    Two corrections:

    1.) Use version 2022 from SVN otherwise the patch might not work (especially with the current version 2069):

    svn -r 2022 co https://mediatomb.svn.sourceforge.net/svnroot/mediatomb/trunk

    2.) In config.xml, the section metadata-extractors has to be contained by mappings not directly in import.

     
  • Jin

    Jin - 2010-04-06

    Thanks, now that 0.12.0 is released, I will finally have some time to go through all patches.

     
  • Jin

    Jin - 2010-04-06
    • assigned_to: nobody --> jin_eld
     
  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2010-10-05

    Just a note of warning... this patch should not be accepted because it breaks other functionality of mediatomb (I'm hazy on the exact details because it has been so long). Good concept, bad execution.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks