Quote:
Quoting skipnet50:

Quote:
I daresay Unicus has it correct. His "name" for Profiler purposes would D/B/Woodside and then we would simply enter DB Woodside to indicate what the actual credit reads.

Are you saying that you would enter an on-screen "DB Woodside" credit as "D/B/Woodside [DB Woodside]"? I'm not saying that's right or wrong - I just would like to know EXACTLY where you, and others in this perpetual debate, stand. As I understand it, Unicus would simply enter D/B/Woodside and leave it at that, while you would use the "credited as" feature to indicate that the on-screen credit doesn't show a space between the initials. Feel free to correct me if I'm wrong - either one of you...

Quote:
To you it would be a waste of time, hal, accuracy is not your objective,. It is mine and that is why I do it,  the program inserts the space, which may not appear in the ACTUAL credit. I have no issue with how we have to enter it, but if the data says there is no space then I use the CA to reflect the accurate and actual data.

Skip

Quote:
Quoting hal9g:

Quote:
I'd rather see us enter him as 'DB//Woodside' than to enter him as 'D/B/Woodside [DB Woodside]'.

Well, as you've seen, there are plenty people that prefer the the other option as well. IMHO it's not so much about what either of us "rather sees" - the important thing is that we're all on the same page. As this thread, and countless similar ones before it, clearly shows, we won't achieve that by ourselves...

Quote:
This is just one more reason why the current linking system simply does not work and needs to be scrapped. 

It works wonders - locally, that is. Thanks to the "credited as" feature I have reached a level of accuracy in my local database that I don't think will ever be matched by any online database - ours included. So that part is great. For online purposes, though, the system is severely hampered by (a) the fact that a number of people refuse to use it, probably due to the extra work involved, (b) the fact that we're stuck with a CLT that almost invariably declares the IMDb-name the "winner", which gets pretty tiresome to fight against after a while, and (c) the lack of any guidance on issues like this (how to deal with this lack/presence of spaces, how to deal with the lack or presence of a comma in suffixed names, how to deal with parsing,...). IMHO, especially the latter is important: how can we be expected to work towards an accurate database if on each of these issues there are various groups of users handling this in entirely different ways. We HAVE to get users on the same page on these issues, or I'm afraid the "sharing the workload" part of the program will slowly die.

Quote:

And I repeat:
"D/B/Woodside" is 100% accurate data.  No space between "D" and "B" is entered in the database.

The space you see in DVDP in the cast list is a display issue, NOT a data issue.

What you are doing is manipulating the data to get it to display the way you want it to.  By doing so, you are screwing up the CLT by increasing the instances of "DB//Woodside" when you yourself stated that the correct way to enter it is 'D/B/Woodside'.

Keep it up and 'DB/Woodside' will become the most commonly credited form of his credit and we'll have to change his common name in every profile!

Quote:

[...] I'm perfectly willing to go either way, but as long as there's no general consensus and different people keep using their own method, the problem will remain. Ken really should step in and settle this, [...]