Quote:
Quoting Prof. Kingsfield:

Quote:
this may be a can of worms, the more I dig.

You didn't really think there was an easy, one-stop solution, did you? 

Anyway - I've made peace with the fact that weren't ever going to get the community on the same page with regards to capitalisation issues. Additionally, this filter works wonders: I can still track what I want to track, except now I don't have to keep debating the matter. As this is basically a form of "dumbing down" of the database, it'll definitely lead to some problems (one of which you've already encountered), but luckily none that will affect my database. 

Based on what I've read, I guess that much like the premise itself, even it's problems are virtually impossible to explain. So good luck with that.

Quote:
Quoting Prof. Kingsfield:

Quote:
Quoting hal9g:

Quote:
Quoting Prof. Kingsfield:

Quote:
Oh great so now instead of going with whatever the CLT name is, in one case De Banzie (de Banzie), we have a user making an undocumented change to de Banzie . How is this going to dealt with, Ken, more runaway undocumented changes. If the CLT name is De Banzie then so should it be, it should NOT be changed to de Banzie. In short the CA is now, without documentation) overriding what the CLT result is.

Skip

The CLT ignores capitalization.

I know that Hal, see my comment above.

Ken:

This also why I object so strenuously to Global changes which a user does not own. I see these things come in and I find discrepancies ALL THE TIME with my data. Since my stock is in storage and i can't verify the vast majority of these issues right now, I am forced to assume that my data is correct, when it may not be (but I doubt it), so I reject them and I make note of the discrepancies for future reference. But when I see these discrepancies I am not appreciative of the user trying to change my data based on his copy which is different from my copy. Sure I can reject the data, but it also tells me that at some point in the future I am going to have fix that data, because the global assumption is wrong. <shrugs>

Skip

Essentially, Ken is saying that if you wish to track capitalization differences in names, it is entirely a local issue.  You will not be able to rely on the on-line database to know whether capitalization is "as credited" or not because it is extremely unlikely that a contributor is going to change the cast entry in their local database to match "as credited" before they contribute.

Frankly, I don' believe that there are that many users who really care that much about capitalization differences.  They just want the names to link.

You have the ability to do this locally.....but your on your own.

Quote:
Which is why communication in user notes becomes vitally important, Hal. Some users don't care, some DO and those that DO need the communication, since we can't rely on the Online, we have to rrely on the Communication user to user in our notes.

Skip

Quote:
Quoting Prof. Kingsfield:

Quote:
Which is why communication in user notes becomes vitally important, Hal. Some users don't care, some DO and those that DO need the communication, since we can't rely on the Online, we have to rrely on the Communication user to user in our notes.

Skip

If capitalization is not relevant to what is stored in the main database, there's no need to discuss it in the notes.

Quote:
Some don't need a further excuse to inflate their Contributions that they can brag about.

Skip

Quote:
To YOU, James. Please don't try and force your standards upon me. that's why I summarily reject most of your updates. Thios is supposed to a cooperative process, a team effort, not just to benefit James or Tim or Skip, but ALL of us and we all have different priorities. You aren't going to know what mine are and i don't know or care what yours are. Simple clear and useful communication through our notes is all we have and is the key that each of us can use to maintain our local data as we want it to be. All you do is insult me, james when you tell me in effect, no I am not going to be part of the team, I am not going to communicate clearly and usefully with you, you have to guess whether my data is useful to YOU. I want to do it MY way (even if it is within the rules. My single big key is AS CREDITED, everything else I can work with and around as long as I have the notes to know what I am dealing with. Yet another example where I recognize the individualism of all of us as it pertains to our local data.

Skip

Quote:
Actually the online database can in fact retain the proper capitalization, if people take the time to match it in their local db before contributing.  I just don't believe people will go to that trouble, since only one version of the capitalization can exist in your local at any given time.