Quoting TheMadMartian:

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

I am not even sure why this is an issue.  As has been said, many times, the CLT ignores capitalization.  Not only that, but the program does as well.  If you have Devito, and I upload DeVito, and it gets accepted, and you download it, you will still have Devito.

Using credited as, in these situation, has never made any sense...at least it hasn't to me.  It is unfortunate that those people who, in my opinion, went off the reservation might be inconvenienced.  Maybe Ken could run a filter, through the main db, that would remove all the credited as entries where the only difference is capitalization.

I understand that, Martian. The other ugly head this seems to raise to me is as follows, what will I update. Will I be updating De Banzie upon acceptance or the actually credited name of de Banzie. This may not be of import to you but it is to me, and all the more reason for documentation to be provided as to, in this case what is actual credit, so that when I get the update I can at least make the manual correction, since I want the data to reflect the credits accurately, if it is De Banzie, I want to know that, if it is de Banzie I need to know that too.

Skip

Quoting Prof. Kingsfield:

Quote:
I understand that, Martian. The other ugly head this seems to raise to me is as follows, what will I update. Will I be updating De Banzie upon acceptance or the actually credited name of de Banzie. This may not be of import to you but it is to me, and all the more reason for documentation to be provided as to, in this case what is actual credit, so that when I get the update I can at least make the manual correction, since I want the data to reflect the credits accurately, if it is De Banzie, I want to know that, if it is de Banzie I need to know that too.

Skip

I know that DeVito is correct.  If the credit was DEVITO, I would enter it as DeVito.  As I understand it, you would enter it as DeVito [Devito].  At this point, that becomes a local only issue.  As such, you are going to have to do that work yourself.  I know it sucks but, it is what it is. 

Quoting Varrus:

Quote:
What about spacing? ie. Danny DeVito vs. Danny De Vito?

I would think spaces would need credited as... since one of Ken's filters uses spaces for credited as it must be wanted.

His initials filter will give us something like..

J. T. Doe [J.T. Doe]

so it seems to me credited as needs to be used for spacing.

Quoting TheMadMartian:

Quote:
Quoting Prof. Kingsfield:

Quote:
I understand that, Martian. The other ugly head this seems to raise to me is as follows, what will I update. Will I be updating De Banzie upon acceptance or the actually credited name of de Banzie. This may not be of import to you but it is to me, and all the more reason for documentation to be provided as to, in this case what is actual credit, so that when I get the update I can at least make the manual correction, since I want the data to reflect the credits accurately, if it is De Banzie, I want to know that, if it is de Banzie I need to know that too.

Skip

I know that DeVito is correct.  If the credit was DEVITO, I would enter it as DeVito.  As I understand it, you would enter it as DeVito [Devito].  At this point, that becomes a local only issue.  As such, you are going to have to do that work yourself.  I know it sucks but, it is what it is. 

And if the CLT says Devito, Martian are you correct in just changing it, I don't think so. Not without communicating to other users, we all have different priorities and that is why Communication in the notes is so important. I understand that I can now deal with this locally, but in order to be able to do so I need to know how the updates are going and I need better communication from the Contributing user so that i know what i need to address locally, IF I need to address it locally. In this particular case all that is needed  is TWO words As Credited, that tells me what I need to know, his change  when it gets to the update comes down as De Banzie, in which case even with his notes I would be stuck, his notes would then be indicating that De Banzie was As Credited which was not what he was intending...this may be a can of worms, the more I dig.

Skip

Quoting Ken Cole:

Quote:
Bear in mind that version 3.6 will be out soon and will spawn a large number of contributions, so we'll be seeing submissions for many of these anyways.

Ken:

I hope you understand that I am seeing what appears to be a SNAFU. I want the data that I update to not screw up my data, I can do this with adequate notes and proper updates, but what will I see upon update De Banzie or Tim's intended de Banzie. In case 2 all he needs to tell me is As Credited, in case 1 how can I know that I am not corrupting my own data.

I am currently about 2-4 weeks behind on my updates because I get so many of them on a given day, ( I currently have about 120 in my qeue, that's about 6-8 hours work, so descriptive and useful notes are EXTREMELY important to me, including CLT results. I go through every update very carefully and if there is ANY doubt, i reject an update and I fear that sometimes I am rejecting good data that I cannot accept out of fear of corrupting my own and with most of stock in storage I am at the mercy of those notes. I recognize the importance which is why I do try to Communicate useful information to my fellow users.

Skip

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.

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

Quoting samuelrichardscott:

Quote:
So it's OK to vote on things if you don't own the disc yet you are against submitting things if you don't own the disc in your opinion?

I have said so and so has Ken repeatedly. If I am not comfortable in voting on something I don't own I don't vote and this happens all the time. I don't understand not using the wishlist, I know what is coming months in advance and it helps me in my budgetary planning.

Skip