Super Mark, thx for the effort.

Mithi,

I think the reason I left out fileds like slot and location is that it's a many to one relationship.  That is a single profile can have multiple slots and locations.  That's not to say it can't be done of course.  It's more a matter of finding the best way to do it.  Since I had no need for it, I thought I'd leave it out of version 1.

With that said, do you have any suggestions on how best to implement this?  Should duplicate rows be written for each slot/location?  Should it output some predefined amount similar to how it handles Directors (like 2.4, only the first two directors for a profile are listed)?  Not knowing the needs for this data, I can't really determine the best solution without additional input.

Quoting Mark Harrison:

Quote:
With that said, do you have any suggestions on how best to implement this?  Should duplicate rows be written for each slot/location?  Should it output some predefined amount similar to how it handles Directors (like 2.4, only the first two directors for a profile are listed)?  Not knowing the needs for this data, I can't really determine the best solution without additional input.

Good questions, but I don't really need it anyways, being Mr. XSLT
I would suggest "first entry only"
Anyone who needs that should/would/could work with childprofiles anyways, I think.

cya, Mithi

I tried running it a couple of times and I keep getting  The dotNet framework version 2.0 is not installed. Please install and try again
I tried that and I keep getting the same response...

Did you install .NET 2.0?  For the average user, this would be found here.

If you need a 64-bit version, you can find the links here under the ".NET Framework Version 2.0 Redistributable Package" section.

You can also run Windows Update if you're on XP or Vista and it should detect if you need to install 2.0.

Thanks. Works great. I can finally totally move over to the new version.

Quoting b00bie:

Quote:
I also would like a slot location on CSV, for my application I have a unique slot/location for each DVD so a single instance would be fine for me. Thanks.

I'm glad to hear that others are finding this useful.  But I do want to discuss the location/slot data a little more.

So let me use an example here.  I have The Lord of the Rings: Return of the King Extended Edition.  That's a single profile.  It has 4 discs.  Discs 1 & 2 are the movie, discs 3 & 4 are the bonus material.

At this point when I do a CSV export, I get one row for that profile.  The problem is that profile has 4 different location/slot values potentially since it has 4 discs associated with the profile.

So again I say, how do you handle that?

Option 1 would be to repeat each row for each unique location/slot.

So the CSV might look like:

Title,Location,Slot
Lord of the Rings, Location1, Slot1
Lord of the Rings, Location2, Slot2
Lord of the Rings, Location3, Slot3
Lord of the Rings, Location4, Slot4

Option 2 would be to handle this like it does with director.  It could either list the location/slot for the first disc in the profile and ignore the rest or list the first x number.  And then what should x be?  For TV sets, this could get much worse.  I have a TV set (Nowhere Man) that has 9 discs.  Should x = 9 then?  If I had a disc changer, I'd certainly load all 9 profiles, but where do you stop?  What if something has more than 9 discs associated with it?

Anyway, that CSV might look like:

Title,Location 1, Slot 1, Location 2, Slot 2, Location 3, Slot 3
Lord of the Rings, Location1, Slot1, Location2, Slot2, Location3, Slot3

What's the best solution here?  Since I have no need for that information, I honestly don't know.  I'm replying on those who need that data to tell me what they need.  Once we know the right direction to go, it should be an easy matter to make the change.  But I need to know which direction to go first.

Hi Mark,

thanks for that plugin. It is great and does everything I want and need (possibly at this time)
Maybe in the future will be a facility in DVDP that needs an extension.

Thanks again.