English > Scripts and Templates
Export plugins for J River Media Center
raldo:
--- Quote from: rick.ca on April 07, 2009, 06:56:06 pm ---
--- Quote from: nostra on April 07, 2009, 01:53:00 pm ---If I would need existing data from PVD I would just query the PVD database directly using SQL and then put data into MC using it's API. This seems like most powerful and universal way to me.
--- End quote ---
Raldo, I don't understand your apparent reluctance to consider this may be the best solution.
--- End quote ---
Well, data retrieval is really not the issue at this point. As I've said before, I'm interested in a system where the entire operation of metadata import can be done from MC.
This also involves triggering a search for new data and resolving ambiguities in the results.
--------------
Btw, as I explained above, one issue with going directly at queries, is that one somehow has to translate a user configuration into queries via code. This mechanism already exists within Nostra's parsing language. Thus my apparent reluctance.
rick.ca:
--- Quote ---I'm interested in a system where the entire operation of metadata import can be done from MC.
--- End quote ---
I don't think the benefits that might be had using this approach would come close to outweighing the data integrity issues I raised above. I wouldn't risk messing-up my database using it, even if it worked. And I'm sure it won't. It's already enough of a challenge controlling "the entire operation of metadata import" directly from PVD.
--- Quote ---one somehow has to translate a user configuration into queries via code
--- End quote ---
I don't understand. Surely the database can be queried to determine the field names and types. And then all the data for records with a pathname can be extracted. I'm sure there may be complications I can't imagine for a process of querying the database one record at a time and updating the corresponding MC record. But if this is impossible, couldn't the plugin still extract all the data temporarily to XML and import that? It's been a while since I've done such an import to MC, but it seems to me you don't even have to worry about whether or not the media files or fields exist in MC—if they don't, they'll simply be ignored.
raldo:
--- Quote from: rick.ca on April 07, 2009, 10:44:43 pm ---
--- Quote ---I'm interested in a system where the entire operation of metadata import can be done from MC.
--- End quote ---
I don't think the benefits that might be had using this approach would come close to outweighing the data integrity issues I raised above. I wouldn't risk messing-up my database using it, even if it worked. And I'm sure it won't. It's already enough of a challenge controlling "the entire operation of metadata import" directly from PVD.
--- End quote ---
Yes, but one could still handle data integrity issues with a seamless system. You mentioned a new MC field "DateImportedFromPVD" which could be used to block import. Or some other mechanisms could be used.
It's not just that, though: Some users may have "lesser criteria" on data. For example, some of my friends use MC but complain about the lack of metadata possibilties for movies. Or my sister imports some movies into MC and her husband has no idea what the movies are about. A description, year, director might be nice for them.
But none of them are ready for PVD in its current state.
--- Quote from: rick.ca on April 07, 2009, 10:44:43 pm ---couldn't the plugin still extract all the data temporarily to XML and import that?
--- End quote ---
Yes, that's exactly what I am saying in the above posts. Use the mechanisms that are already there. (but pass the data through UDP instead)
rick.ca:
--- Quote ---But none of them are ready for PVD in its current state.
--- End quote ---
If that's the design premise, it's hard to imagine how your plugin will further the development of PVD. It would make more sense for nostra to give you his code so you can incorporate the acceptable parts of it into your MC plugin.
raldo:
--- Quote from: rick.ca on April 08, 2009, 12:32:39 am ---If that's the design premise, it's hard to imagine how your plugin will further the development of PVD.
--- End quote ---
Why? You could still use PVD in the way you've always used it and prune the data. And then use an MC plugin for import.
The difference would be that more people would use PVD.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version