|
|
Welcome to the Invelos forums. Please read the forum
rules before posting.
Read access to our public forums is open to everyone. To post messages, a free
registration is required.
If you have an Invelos account, sign in to post.
|
|
|
|
Invelos Forums->General: Website Discussion |
Page:
1... 7 8 9 10 Previous Next
|
A New Forum? |
|
|
|
Author |
Message |
Registered: March 13, 2007 | Reputation: | Posts: 3,436 |
| Posted: | | | | So both of you have the issue that Audio is (almost) always reported as updates, even if it is not changed? (At least for Stereo, I believe.) | | | Achim [諾亞信; Ya-Shin//Nuo], a German in Taiwan. Registered: May 29, 2000 (at InterVocative) |
| Registered: March 13, 2007 | Reputation: | Posts: 3,480 |
| Posted: | | | | Quoting ya_shin: Quote: So both of you have the issue that Audio is (almost) always reported as updates, even if it is not changed? (At least for Stereo, I believe.) I do. | | | ...James
"People fake a lot of human interactions, but I feel like I fake them all, and I fake them very well. That’s my burden, I guess." ~ Dexter Morgan |
| | T!M | Profiling since Dec. 2000 |
Registered: March 13, 2007 | Reputation: | Posts: 8,739 |
| Posted: | | | | Quoting m.cellophane: Quote: Quoting surfeur51:
Quote: Quoting m.cellophane:
Quote:
I have a Kristin//Scott Thomas. I'm unable to add a Kristin/Scott/Thomas. I get an error that says "Unable to save changes. A duplicate record exists."
Very strange. Which version do you use ? I have the last one (built 1392) and get no error for the same action. I have the same. Would anyone else care to try this? I too (obviously also using build 1392) have no problem in creating both a Kristin//Scott Thomas and Kristin/Scott/Thomas, or any other couple of names parsed differently. I realise it's a silly question, but still, since you're getting a "A duplicate record exists" error, I have to ask: are you absolutely sure that you didn't already have a Kristin/Scott/Thomas entry in your database before you tried to add one...? So no, the program most certainly not "ignores parsing" - something which Ken has publicly confirmed when people questioned that earlier. Sure, the CLT ignores it, just like it ignores birth years, or doesn't distinguish between cast and crew. It's just a pretty rudimentary tool. Additionally, the contribution acceptance system is modified to protect your local value (if one exists). But unfortunately, in all other areas, parsing is still very much alive, and very much a nuisance. | | | Last edited: by T!M |
| Registered: March 29, 2007 | Reputation: | Posts: 4,479 |
| Posted: | | | | Quoting ya_shin: Quote: So both of you have the issue that Audio is (almost) always reported as updates, even if it is not changed? (At least for Stereo, I believe.) Well, I don't know. I never update my profiles from online, skip all changes and lock fields of all profiles. | | | Images from movies |
| Registered: March 29, 2007 | Reputation: | Posts: 4,479 |
| Posted: | | | | Quoting T!M: Quote: But unfortunately, in all other areas, parsing is still very much alive, and very much a nuisance. Parsing is a nuisance, but fortunately concerns very few names. First nuisance is by far accented names, second one is asian names, contributors' typos third one, parsing fourth... but this may depend on movies you own ("hollywood movies" collections seem less sensitive to accented or asian names). | | | Images from movies |
| Registered: March 13, 2007 | Reputation: | Posts: 3,480 |
| Posted: | | | | Quoting T!M: Quote: I too (obviously also using build 1392) have no problem in creating both a Kristin//Scott Thomas and Kristin/Scott/Thomas, or any other couple of names parsed differently. I realise it's a silly question, but still, since you're getting a "A duplicate record exists" error, I have to ask: are you absolutely sure that you didn't already have a Kristin/Scott/Thomas entry in your database before you tried to add one...?
So no, the program most certainly not "ignores parsing" - something which Ken has publicly confirmed when people questioned that earlier. Sure, the CLT ignores it, just like it ignores birth years, or doesn't distinguish between cast and crew. It's just a pretty rudimentary tool. Additionally, the contribution acceptance system is modified to protect your local value (if one exists). But unfortunately, in all other areas, parsing is still very much alive, and very much a nuisance. I thought that I might have a stray Kristin/Scott/Thomas still in my db and what I originally thought I'd try is to add that parsing to my English Patient profile so I could see what would happen when I clicked on either version of the name. I couldn't find that parsing variant, so I tried to create it...and that's when I encountered the error that I could not create a duplicate. I recently ran a repair to delete duplicate names, but right now I'm running a full repair to see how things are after that. | | | ...James
"People fake a lot of human interactions, but I feel like I fake them all, and I fake them very well. That’s my burden, I guess." ~ Dexter Morgan |
| Registered: January 1, 2009 | Reputation: | Posts: 3,087 |
| Posted: | | | | Quoting surfeur51: Quote: Quoting m.cellophane:
Quote: Wow. I have no idea. I used a dual installation during the beta and have since resumed using the non-beta path. Can anyone else duplicate my experience? I did exactly the same... Strange. I just started with the release candidate and if I remember correct, this installed in the normal path. | | | Last edited: by VirusPil |
| Registered: March 13, 2007 | Reputation: | Posts: 3,480 |
| Posted: | | | | Repair complete. I now have both parsings of Kristin Scott Thomas, and Kristin/Scott/Thomas is assigned to 2 profiles. I replaced both Kristin/Scott/Thomas with Kristin//Scott Thomas. I deleted Kristin/Scott/Thomas. Saved. I successfully re-added Kristin/Scott/Thomas even though I already had Kristin//Scott Thomas. | | | ...James
"People fake a lot of human interactions, but I feel like I fake them all, and I fake them very well. That’s my burden, I guess." ~ Dexter Morgan |
| Registered: March 29, 2007 | Reputation: | Posts: 4,479 |
| Posted: | | | | Thanks for this. So we are back to the problem : common names from CLT and program functions are not coherent.
What we need is a fixed system, not a way to make easier the propagation of wrong data to other users' databases. | | | Images from movies |
| | T!M | Profiling since Dec. 2000 |
Registered: March 13, 2007 | Reputation: | Posts: 8,739 |
| Posted: | | | | Quoting surfeur51: Quote: So we are back to the problem : common names from CLT and program functions are not coherent. Yes they are. You just need to understand how to "read" the CLT numbers, and to never ever take those numbers on face value. If anything, the "problem" you're perceiving warrants work on the CLT, but it still has absolutely nothing to do with in which subforum we talk about common names, birth years and parsing issues. Quote: What we need is a fixed system, not a way to make easier the propagation of wrong data to other users' databases. There are plenty of other opportunities on these forums to talk about "what we need" with regards to what is referred to as "the linking system". This, however, is not one of them. For the umpteenth time: this thread is only about where we talk about these things, not about the system itself. The bottom line seems to be: you don't like the rules, and so you'd prefer to make it as hard as possible for users to follow them... |
| | T!M | Profiling since Dec. 2000 |
Registered: March 13, 2007 | Reputation: | Posts: 8,739 |
| Posted: | | | | Quoting surfeur51: Quote: First nuisance is by far accented names I've never ever had a problem with accented names. Luckily, we have a very simple and very clear ruling by Ken (paraphrasing: enter É as é and E as e), and additionally, there's the simple fact that accents are, generally speaking, rarely used in film credits. Therefore, accented common names are pretty rare as well. There are a few left - Penélope Cruz springs to mind, but even there "Penelope" is quickly closing in - but generally, every time you see an accented common name, you know that it's worth checking up on - chances are that it's wrong. All in all, it's perfectly simple, and never poses any problems. Unless, of course, you choose not to follow the rules... |
| Registered: March 29, 2007 | Reputation: | Posts: 4,479 |
| Posted: | | | | Quoting surfeur51: Quote: @T!M As usual , you understood nothing to what I wrote. The opinion you suppose I have is exactly the contrary of what I really think. Instead of blocking me for Pms, you should block me on the forum and avoid to loose your time misreading what I write and answering on I don't know what. +1 Please don't repeat every two pages the same fantasies about what you think is my opinion | | | Images from movies | | | Last edited: by surfeur51 |
| | T!M | Profiling since Dec. 2000 |
Registered: March 13, 2007 | Reputation: | Posts: 8,739 |
| Posted: | | | | Quoting surfeur51: Quote: Please don't repeat every two pages the same fantasies about what you think is my opinion Here's an idea: why don't you try that yourself? So far, you've managed to get it wrong every single time... | | | Last edited: by T!M |
| Registered: March 13, 2007 | Posts: 2,759 |
| Posted: | | | | If I have understood Ken correctly, profiler ignores parsing only while updating profiles. If you have 1//2 3 in your database (but not 1/2/3) and you update or add some profile (not necessarily the one which already includes 1//2 3) which contains 1/2/3, this 1/2/3 will automatically be changed to 1//2 3. This does not prevent you from manually adding 1/2/3 to you database. For obvious reasons this can not work when you have 1//2 3 and 1/2/3 already in your database.
BTW I have NOT double checked this. But this is what I understand Ken has promised to us. |
| Registered: January 1, 2009 | Reputation: | Posts: 3,087 |
| Posted: | | | | Quoting RHo: Quote: If I have understood Ken correctly, profiler ignores parsing only while updating profiles. If you have 1//2 3 in your database (but not 1/2/3) and you update or add some profile (not necessarily the one which already includes 1//2 3) which contains 1/2/3, this 1/2/3 will automatically be changed to 1//2 3. This does not prevent you from manually adding 1/2/3 to you database. For obvious reasons this can not work when you have 1//2 3 and 1/2/3 already in your database.
BTW I have NOT double checked this. But this is what I understand Ken has promised to us. This would make sense. As I never look at the changes happen at an update I've never noticed this. Perhaps someone other did?! |
| | Muckl | That's my common name. |
Registered: April 9, 2009 | Reputation: | Posts: 858 |
| Posted: | | | | Quoting VirusPil: Quote: Quoting RHo:
Quote: If I have understood Ken correctly, profiler ignores parsing only while updating profiles. If you have 1//2 3 in your database (but not 1/2/3) and you update or add some profile (not necessarily the one which already includes 1//2 3) which contains 1/2/3, this 1/2/3 will automatically be changed to 1//2 3. This does not prevent you from manually adding 1/2/3 to you database. For obvious reasons this can not work when you have 1//2 3 and 1/2/3 already in your database.
BTW I have NOT double checked this. But this is what I understand Ken has promised to us.
This would make sense. As I never look at the changes happen at an update I've never noticed this. Perhaps someone other did?! Yes, that's how it works. | | | 1.0.1, iPhone 3GS, iOS 4.1.0
Trivia v0.3.1 My HSDB v5 additions, HTML windows and other stuff |
|
|
Invelos Forums->General: Website Discussion |
Page:
1... 7 8 9 10 Previous Next
|
|
|
|
|
|
|
|
|