Greatest Tool ever. Building the bridge between the two is almost as great as the IMDB and the Profiler itself.

But I have no idea how to handle the crew if there are multiple movies on a disc.

It would be great if we'd have a checkbox in the first line with the movie's title to make the tool create an episode out of a movie like it does automatically with real series episodes.

Or are there any other solutions I'm not aware of? I've tried the series tab for movies but it wants me to select a season first.

I've just started to use your little but great tool.

Am I allowed to make a wish? Well here we go:

In case there is a cast/credit member who's name is two or more times in the DB I get a pop-up. That's great. But when I have more than one person with the same name AND no BY I start giving them fake BYs to get correct connections and note down which IMDb-ID is which BY in a textfile.

So - as I have to remove this fake BY before adding the new data - it would be really cool, if you could highlight the person which is actually in the film. Maybe a star behind the name or make it bold or something.

Well, but even then I have to know which (fake) BY I need to enter.
That's my request, for now I have to look it up on IMDb - of course I could also look it up in 'Cast/Crew Edit 2', but that's hell if you have a long list.

Edit:
Maybe it's possible to add the fake BYs into the 'CCE2'-Database, so they would stay until IMDb adds a BY? That would be even better!

And if 'CCE2' would recognize the need for a fake BY automatically, that would be the best I can think of!!!

That shouldn't be to hard for CCE2, because the persons are divided by their IMDb-ID already. So if CCE2 finds a new person with a known name but a new IMDb-ID, you get a notice like this:

nm1668238: <David> [Scott]
nm1881836: <David> [Scott]
nm0779036: <David> [Scott] (1976)
nm2259338: <David> [Scott]
nm0779031: <David> [Scott]

(Yes, I really have those five persons inside my DB )

And that's the moment for it to decide: Do all persons with that name have a BY?
- If yes, fine.
- If no, give all of them without a BY a fake one. (Just count them up. For example I start at 9001, so I could have up to 999 persons with the same name and no known BY. But you should not divide them between cast and crew, so their headshots would be connected correctly.)

And after that you could get the notice you have to get sure to have the needed persons in your DB. That would be something like:

nm1668238: <David> [Scott] (9001)
nm1881836: <David> [Scott] (9002)
nm0779036: <David> [Scott] (1976)
nm2259338: <David> [Scott] (9003)
nm0779031: <David> [Scott] (9004)

And as CCE2 already recognizes changes to the common name on IMDb and throws a message in those cases, why not do the same when recognizing a new BY? Which I believe CCE2 will already do, but I haven't ran into such a case by now, so I'm not sure.


Maybe this could be made optional, for those who don't like to have fake BYs in their database, although I guess that most people use this great tool to have correct connections inside their cast and crew.

I've just discovered that I got no warning for these two people:

http://www.imdb.com/name/nm2570301/ (VG crew, I'm adding them, too)
http://www.imdb.com/name/nm0913847/

(Had a good laugh when the crosslinks suggested that a japanese laywer is doing Nicole Kidmans makeup in his free time )

Is there only a warning if at least one person has a BY at imdb?

Quoting DJ Doena:

Quote:
I'll have to think about a possible solution for this one, because I'd also have to consider changing common names (and thus possible new fake BY clashes).

If I'm going to do this, I'll probably use the last for digits of the IMDb ID and have to alert the user if the fake BY has been replaced with an actual BY because then he'd have to adjust this in his DVDP database, too.

I don't see a problem with fake BY clashes. As the fake BY would be greater than at least 3000, it would be easy to recognize it when a common name is changed on IMDb.
So, if a person without real but with fake BY changes common name, you would erase the BY, check if there are other people with the new common name and in case give it a new one.
After this throw a message "John Doe (3003) changed the common name to John J. Doe (3002)". Done.

But I see a problem using the last for digits of the IMDb-ID. As this could easily clash with a real BY. I guess it would be better to just count up for each common name.

Quoting DJ Doena:

Quote:
Quoting Corma:

Quote:
Is there only a warning if at least one person has a BY at imdb?

Yes, because I figured it pointless to give a warning when there's nothing you can do about it (sans using fake BY )

I recognized this behavior yesterday when I got a warning for three people, where I never had one before. As I do use fake BY, I'd prefer to get a notice every time.
Also I'd like to get a warning if there's a cast- and a crew-member with the same common name and both without BY. (That's because of the headshots, which are not divided into two dirs and so would get the same filename in those cases.)

Quoting DJ Doena:

Quote:
Quoting StaNDarD:

Quote:
But I see a problem using the last for digits of the IMDb-ID. As this could easily clash with a real BY. I guess it would be better to just count up for each common name.

Still I'd go with the odds on this one, because the probability of that happening is still slim to none. And it's much less hassle than an additional fake BY managing system.

As of this moment, the last used IMDb ID is http://www.imdb.com/name/nm5300590/, http://www.imdb.com/name/nm5300591/ delivers a page not found.

That makes 5,300,590 different people and only IDs ending between 1890 and 2012 are roughly eligable to be mistaken for real BY. That makes 112 IDs out of every 10,000 or roughly 60,000 out of the whole of IMDb (= 1.12%) that even have a chance of colliding with real BYs. And then they have to have the same common name and BY. I'll take my chances with this one.

Well, lets take a rough guess. You have 5300590 people. Hundreds of first- and middlenames, hundreds of surnames. And of course you have round about 112 BYs. So there are at least (100*100*100*112) 112'000'000 different combinations. So what's the chance to get two actresses with the same common name and the same BY when you just have 5'300'590 people? But yeah it happens: <nm0001853> Vanessa Williams (1963) and <nm0004539> Vanessa Williams (1963)!

And what do you mean by fake BY managing system?

Once you've given a profile a fake BY you'll never need to touch it - except in two cases:

1. The profile gets a real BY on IMDb, then just replace the fake BY with the real BY (no need to touch any of the other persons with this common name, because the user will have to change all those data in his DVDP-DB, too. So keep it simple.)

2. A profile gets its common name changed. Then erase the fake BY for the actual profile. Check out if there's only one profile with the old common name and erase its BY too, if its a fake one (as its not needed anymore). At last check the new common name. If there's more than one with this new common name, they must already all have a BY (because it would have been needed before). But if there's only one other, you need to give it a fake BY (as long as it done have a real one).

So what could be the worst case? Worst case is that a changed common name could end up by the need to change three profiles in DVDP.

(OK, worst is the first run, where you need to add a lot of fake BYs at one time, but you have to do this either way. )

(Hmm, you have persons divided into cast and crew, don't you? So there could be a 'managing problem' to get the fake BYs unique, which would be needed to connect to headshots correctly.)

But of course I'd be happy either way, cause it would save me a lot of work anyway.

Quoting DJ Doena:

Quote:

Quote:

I recognized this behavior yesterday when I got a warning for three people, where I never had one before. As I do use fake BY, I'd prefer to get a notice every time.

I can add another option for the next version.

Quote:

Also I'd like to get a warning if there's a cast- and a crew-member with the same common name and both without BY. (That's because of the headshots, which are not divided into two dirs and so would get the same filename in those cases.)

That would not be impossible either.

That would be great!

PS: As I doubt that everyone will be happy to add a lot of fake BYs, you should make the fake BY system optional, too.

Quoting Corma:

Quote:
Quoting StaNDarD:

Quote:
Quoting StaNDarD:And what do you mean by fake BY managing system?

He wrote 'additional', too I guess that simply meant it's easier to realize by the ID than anything else like converting the roman numbers into a fake BY for example

But where's the managing part? As I see it, it's just a (more or less) simple add or erase in very few cases. The majority of the time you don't have to care about them.

By the way: the roman numbers would be a great idea, adding those to let's say 3'000 would be a perfect unique BY. As long as I can't imagine there will be more than 6'999 persons sharing the same common name.
But I guess, calculating roman numbers to arabic numbers may be hard.