Developer:Meandre
From myExperiment
Contents |
Workflow Importer
Current Status
Basic meta data inference is completed as well as image preview generation.
Meandre File Structure
The .MAU file is a JAR/ZIP file containing a repository Turtle RDF file in the repository directory.
RDF Library
For the rdf library i am using the RDF bindings for the redland C library (librdf) http://librdf.org/docs/ruby.html.
Meandre Parser Design
The MeandreParser class does all the low level manipulation of the RDF store and returns data in a more usable format to the workflow processor.
Image Preview Style
The importer currently uses the rdf from the mau file to generate a dot file, this gives a significantly different layout to what is seen in the meandre workbench. Therefore it may be neccessary to use the facilities of dot to create a view more closely resembling the view in the Meandre workbench.
How meandre does it
Meandre appears to use the google web toolkit, this uses java and would therefore be unsuitable for myExperiment.
Audio Signal Repository
The Audio Signal repository is being developed in python using 4store as an RDF triple store and Web.py.
User Interface
The actual user interface for this system will be contained within myExperiment i.e: the user will not interact directly with the repository. The Use Cases for such an interface are:
Such a user interface will need another Rails controller but should not require any significant modifications otherwise.
Collections
MIR Meandre workflows typically work with Collections this could possibly be tied to the Packs functionality in myExperiment this would see the myExperiment site resposible for the metadata relating to the collections but the actual audio metadata would be served by the Audio Signal Repository.
Repository <-> myExperiment Interfacae
I intend to create a RESTful interface between the two systems. The URL structure should be split into two seperate sections. The metadata is for use by myExperiment where as the actual signals are used by Meandre:-
/metadata/... /signal/...
NEMA workflows use a Input Selector component that can either point to a single file or an xml list of files to be run against a workflow, therefore whatever mechanism we use for curated collections (probably packs) will have to be able to serve up data in this XML format. If the workflow is enacted on myExperiment there is the possibility of modifying the paramaters of workflows using the InputSelector components to automatically point to the correct collection selected using myExperiment.
Enactor
In theory the MAU file should be self contained and portable between meandre instances, however at present i cannot find a way to upload a MAU file directly into the Meandre infrastructure. The closest i can do at the moment is to extract the mau and upload its components using the web service interface at: http://localhost:1714/services/auxiliar/add_to_repository.html
