On Nov 2, 2018, at 12:29, David Klann <dkl...@linux.com> wrote:
> You would likely need to export the CSV data and use an app to coerce it
> into the acceptable XML format used in Rivendell. Not hard, but would
> require attention to the details.
You can also pass many of those fields in through the use of --set-string-*
switches —e.g. --set-string-title=, --set-string-artist=, etc. See the
rdimport(1) man page for the full list. This is the technique that many of the
scripts in that Git repo use.
> Speaking of which, Fred do you have a formal schema (DTD) for the XML
> used in the export data? I recently had a partially broken Rivendell
> installation (my "lab" system) and wanted to preserve the library, so I
> made my own "exporter" and created the XML with a script (attached for
> reference).
Alas, no. I have been gradually extending my knowledge of XML/XSL theology over
the past year or so, to the point where I can now more-or-less write DocBook
markup reasonably well, and even hack a stylesheet or two. One of these days
I’ll get around to DTDs.
Cheers!
|----------------------------------------------------------------------|
| Frederick F. Gleason, Jr. | Chief Developer |
| | Paravel Systems |
|----------------------------------------------------------------------|
| "No, `Eureka!' is Greek for `This bath is too hot!'" |
| -- Dr. Who |
|----------------------------------------------------------------------|
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
