English > Scripts and Templates

Export template for J River Media Center

<< < (3/6) > >>

raldo:

--- Quote from: nostra on March 26, 2009, 06:36:35 pm ---To split files use this code in main template file:

--- Code: ---Files:
{%value=path template="pages\files.ptm"}
--- End code ---

And this in files.ptm

--- Code: ---{%value}


--- End code ---

P.S. You will need to use field number instead of "path" if you use 0.9.8.20

--- End quote ---

Nostra:

This is a step forward but consider this: In the resulting MPL file, I would like one <item> section per File. When I do what you suggest above, I get one item section where the filenames appear twice.

I tried moving the Item section into files.ptm, but then %value=xx didn't parse into the resulting mpl file.

Can a child template somehow inherit  the values from the parent template?

raldo:
I've found a solution which works better than before. See Edit above...

nostra:
You want to get only one (first?) file for arecord or what?
If so then define the template link like this:

--- Code: ---{%value=27 template="pages\files.ptm" maxvalues="1"}
--- End code ---

rick.ca:

--- Quote ---I assume you're talking about semi colon (after replace in output script) delimited fields?
--- End quote ---

Yes. I see you just replace all commas with semi colons. I used a separate export to do that only for list fields—so it wouldn't replace commas in fields like Description.


--- Quote ---It'll be interesting to see if for example "Director" (MC) will be changed to accommodate this.
--- End quote ---

I attempted to explain here some new field types that would be required to properly handle movie information, but there's no sign yet they "get it."


--- Quote ---I've found a solution which works...
--- End quote ---

Well done! So, does this achieve a level of integration you're satisfied with, or do you think there might be a better solution?

I hope the 0.9.9 export function is completed/fixed soon—I'd like to give this a try. Or at least be ready when MC gets around to providing the field types we need.

raldo:

--- Quote from: rick.ca on March 26, 2009, 08:23:26 pm ---[..]
Yes. I see you just replace all commas with semi colons. I used a separate export to do that only for list fields—so it wouldn't replace commas in fields like Description.
[...]

--- End quote ---
Yeah, I guess I can live with some extra semicolons.. Since the MPL file can be reimported, I guess I can do it all over again if those semicolons start bothering me!


--- Quote from: rick.ca on March 26, 2009, 08:23:26 pm ---[..]
I attempted to explain here some new field types that would be required to properly handle movie information, but there's no sign yet they "get it."
[...]

--- End quote ---
Notice how JRMC did the GUI design in cooperation with the users on the forum. I'm pretty sure they'll come around with a proper list of meta data for movies. As far as I understand, they're also working on theater view meta display view for movies.

It'd be interesting to know how the various online databases overlap and differ wrt. meta data. Has anyone done a survey?! The intersection between these services + some of the "Good differences" I guess should be the standard for what they end up with...


--- Quote ---So, does this achieve a level of integration you're satisfied with, or do you think there might be a better solution?
[...]

--- End quote ---
It looks like this is as far as we can get without code changes on either side. It's pretty good, I'd say...

The best solution, of course, would be a plugin on the JRMC side with direct communication to PVD.

Navigation

[0] Message Index

[#] Next page

[*] Previous page