Quoting Jimmy S:

Quote:
I know wich actor is wich in my database and the way to do it now is problematic, seriously you must invent a middle initial or make a volontary typo in the name.

I don't get this. If it's local only, why don't you just add invented birthyears like 0001, 0002, etc. instead of invent a middle initial or make a volontary typo in the name 

Quoting Jimmy S:

Quote:
Because I don't want to see Joe Whatever (1) in the credit of a film...

Then we propably use some sort of different layout since I don't see BYs listed on Cast/Crew lists. Only if I double click an actor to see all his credits.

Quote:
Don't see what is hard to understand in the fact of wanting a real solution for our online database with no effects whatsoever on the online database

Now I'm confused. You wan't a solution to our online database that doesn't have any effect to our online database

I am not sure how you would allow it for your local, without effecting the online (unless you chose to forgo any online activity for cast and crew).

I think that there would have to be an online component to cast and crew entries, to solve the issues that we have.


Charlie

Quoting Jimmy S:

Quote:
Quoting CharlieM:

Quote:
I am not sure how you would allow it for your local, without effecting the online

You know I hope that some fields aren't contribuable in a profile?

My only question is this.

Lets take a relatively unknown and common name , Joe Smith

There aren't any BY's to be found to differentiate between 2 different people. 

In the online, therefor, there is only 1 Joe Smith
Locally, you differentiate by some means (right now numbers inserted into BY's)

Considering, a big design component of the software is the Online, shared DB, how would you resolve

1.  downloading a new profile with Joe Smiith (1 Online, 2 Locally)
2. Uploading a profile

Now for you, that may not be a big deal, for you may very well choose not to use the online for cast and crew (not a big deal), but considering the actual base design of the program involves a shared DB, I really think that needs to be taken into consideration.

If implemented properly, considering a large criticism of the program involves name linking, would resolve your issues and would not need to be kept locally, and you would be able to share in the labor of others.

Just an opinion.

I don't understand what you need Jimmy. Since it's for your local database only, should anyone else do anything?

It seems to me that it might be really difficult to do because wouldn't everyone's local data be affected if invelos makes those changes?

I know you don't like to use a false BY but wouldn't it be better to just figure out a way to organize those people the way you want to?

From reading about this issues in the forums, the little bit I picked up is to fix or implement this type of thing would need a big change in the way the database works.

If so, then I would like that data to be done so that it is available online too so everyone could have access to it if they wanted it.

Quoting Kathy:

Quote:
I don't understand what you need Jimmy. Since it's for your local database only, should anyone else do anything?

You know that I can even confused myself sometimes

This is what I imagine visually :


The ID number would be just another possible way to use to make a distinction between two persons or more with the same name in our database. It doesn't need to be contribuable and, as I wrote already, I don't see what is the big deal with that at all. Yes it's an offline thing, but a non contribuable field doesn't affect the online database in any way.

Quoting Winston Smith:

Quote:
The by data could be used, you could assign your own by, but then your data would not be cintributable.

Not it doesn't... I have already wrote that I don't want fictional data in my database and a false birthdate is fictional.

I guess it sounds like it...

Except as I said the field wouldn't be contribuable and would be ignored in the contributing process.

So for the online database


would be the same person as the First Name, Last Name, Middle Name and Birthdate are the same.

The distinction would happen only in the user database when he/she set an ID Number for the name and this distinction would be local only.

I don't see the benefit, this database is a cooperative effort among thousandsd of users. I don't understand what benefit is derived if marilyn monroe is 000002 in jimmys db, 575 in mine,  34675 in charlies and. 8654  in kathys how does help us as a group.