Since this got no attention in the Support forum, I'm reposting it here:
-------------------------------------------------
Update: Another advantage of incorporating an optional "import control file" into the import scheme is that it provides a way to make the DB info *persistant* across DB deletes and re-imports. It's all well and good to have the ability to manually edit the imported data in the DB itself, but it's not much use if you have to re-edit in the case of a major change.
---------------------------------------------------
Is there any way (preferably *easy*) to allow xlobby to handle movies in a deeper and more complex directory structure than just X:/movietitle/movietitle.ext ????
I'd really like to be able to have these examples all work, and have "buttons" that have the directory names as the legend, which, when selected, will show all the movies under that leaf of the tree.
X:/Movies/The Jerk/The Jerk.ts
X:/Movies/The Notebook/The Notebook.ts
X:/Movies/XXX/Island Dreams/Island Dreams.ts
X:/Kids/Animation/Toy Story/Toy Story.ts
X:/Kids/Animation/Toy Story 2/Toy Story 2.ts
X:/Kids/Animation/Shrek/Shrek.vob
X:/Kids/Adventure/The Rocketeer/The Rocketeer.ts
X:/Nature & Science/Giants of San Benedicto/Giants of San Benedicto.ts
**Note that the number of directory levels is NOT always the same.**
I know that I need to add the .ts extention into the import setup, but the directory layout still seems to scew things up completely.
Is there any way this can be made to work???
------------------------------------------------------
Ok, I've gone back and read more of the various posts on the subject of video "movie" directory structures, and I can see that it is possible to add more levels, and "containers". But what I'm not sure about is this - is it possible to have a tree structure with branches of unequal length?
What I want, in essence, is this: any directory containing a file with a recognized video extension is a "Movie", and any directory that does NOT have a video file and has subdirectories is a "container".
A container may have a jpeg for display. It would also be a pefect place for a control file that could be entered into the DB for movie rating, password, being applied to everything below it.
Steve, if you could rewrite the import to do a recursive-descent parsing of each listed directory, you could easily get rid of all these import issues.
All that's needed is a list of video file extensions, and a list of directories. With this scheme, I doubt there'd be any need at all for the regular expressions, and at the same time it's far more flexible, and completely data driven without any need for the complex metadata.
Simplicity rules!