Hi All,
We have recently discovered Mediamosa Project and we find it a wonderful component of the application we are developing now - the management system for videos of animals collected during our 'camera 'trap' study. Could somebody give us a brief description of the necessary steps to define our custom metadata definition for both mediamosa backend and frontend (e.g. site-builder). Is it possible to make it work with ftp batch uploading process? If so, how to do it? Do we need to rewrite a little bit the xlm-parser tool or it is enough to include new metadata definitions in 'qdc' file? When answering keep in mind that we are the ecologists rather than computer scientists but fortunately we know a little bit about computers ;)
Thanks in advance!
Jakub Bubnicki
Mammal Research Institute,
Polish Academy of Sciences
Białowieża, PL
Comments
.
Posted by Robert on August 10th, 2012 - 08:25Your question can be easily answered if you are a Drupal developer. But reading your message, you are not. So its kinda hard for me to come up with a workable answer. Also I completely missed this posting on the forum, so I'm sorry that I now responding.
Metadata definitions are simple, they are defined in the qdc / dc / czp modules. These module use Drupal hooks to describe the dc / qdc set and are basically nothing more than name and value pairs. Defining a new set should be easy; just copy one of the modules, rename and add / change the properties of the set its describing.
The FTP batch is a bit harder, as this was developed for one customer and been rewritten twice. I don't really know much about it, but what I do know; A script runs in the background and scans a directory (FTP) from time to time. If finds new files (xml and media), then it uses the XML to upload the media to mediamosa and processed the XML for metadata etc.
However, this process is straight forward and not very flexible. So I would suggest to write something yourself or hire someone who can alter / rewrite the FTP batch upload script.
Anyway, good luck, hope this info helps.
Thanks for your answer! I
Posted by kuba on May 7th, 2013 - 22:03Thanks for your answer! I missed it somehow. Actually we moved to the Django framework as we are more 'pythonists' than 'php-guys' ;) and we needed more flexibility in designing our app. Anyway, thanks again for your answer.
Cheers,
Kuba