| Author |
Message |
| Registered: May 25, 2007 |  Posts: 453 |
| | Posted: | | | | I know some might say: Too many questions, but I simply don't understand!
I had a huge load of initial contributions (new Alt. Versions for "OC California"), correctly parsed Director of Photography "Buzz - Feitshans IV". But now I get all of them back as a so called 'update', wrongly parsed as "Buzz - Feitshans - IV".
Especially as this was the initial profile, I can't understand! No one has been able to "update" the profile since then. I only can presume that this was kind of an automatic correction as this guy is wrongly parsed in the main database? |
|
  | T!M | | Profiling since Dec. 2000 |
| Registered: March 13, 2007 | Reputation:  |  Posts: 8,736 |
| | Posted: | | | | We've talked about parsing before: DVD Profiler is set up, on purpose, to ignore parsing changes, to not force them on anyone. Accepting a profile update into your local database, will never change the parsing of an already existing cast or crew entry in your, or anyone's local database - however a name is parsed in the latest contribution will not overwrite the existing parsing of that name in anyone's local database. It'll stay exactly how it was - the contribution won't affect it. You don't see a difference in the contribution screen, the voters/screeners don't see it either, and any change won't actually reach anyone.
Once again: just parse names however you deem fit, and then never look back. It's really no more difficult than that. You are, of course, entirely correct that Buzz/Feitshans/IV is wrongly parsed. So you can fix that in your local database, but there's really no need to worry about it any more after that. There's no way you can "force" your correction onto other users. If you've got him correctly parsed in your database, then there's really nothing more that you can or even should do. | | | | Last edited: by T!M |
|
| Registered: May 25, 2007 | | Posts: 453 |
| | Posted: | | | | What do you think why I wrote this post: My contributions were INITIAL! What means: Nobody had done them before! No matter if the update changes anything: WHY does it even GIVE IT?
Why does a profile which has never been existing before suddenly change? As the database has other names with different parsings (right and wrong), why does THE DATABASE change data from right to wrong? |
|
| Registered: March 20, 2007 | Reputation:  |  Posts: 2,852 |
| | Posted: | | | | Quoting Magmadrag: Quote:
I had a huge load of initial contributions (new Alt. Versions for "OC California"), correctly parsed Director of Photography "Buzz - Feitshans IV". But now I get all of them back as a so called 'update', wrongly parsed as "Buzz - Feitshans - IV". If you'd lock your local data you wouldn't get that data "back" from the online database. --------------- |
|
| Registered: May 25, 2007 | | Posts: 453 |
| | Posted: | | | | scotthm: That's also not the question! I know how to lock & block. Let me explain it another way for hopefully a better understanding.
1. You buy a movie nobody around profiler owns so far, even has it in the wishlist
2. You create a brand new ("initial") profile, correctly parsed
3. You contribute, contribution is released
4. At once after release you check your updates and get back the profile - with a now wrong parsing
This contradict to all rules of logic I know! And so still the question is how this could happen!
My database, my profiles are my personal stuff, but how could MY correct data change in the database HERE change from right to wrong without anybody changing it? That is still the unanswered question |
|
| Registered: September 29, 2008 | | Reputation: | | Posts: 2,550 |
| | Posted: | | | | Is it possible that you have a profile with Buzz/Feitshans/IV in your local database somewhere? Profiler's updates might be thinking that "oh, he's made a mistake. He already this parsing of B/F/IV, so I'll correct this initial profile of B/F IV back to what he already has in his local database (B/F/IV)." Not sure this is the problem, but worth a try. Type Buzz Feitshans IV into the "click here to find a crew member" box and see if 2 variations come up. | | | My one wish for the DVD Profiler online database: Ban or remove the disc-level profiles of TV season sets. It completely screws up/inflates the CLT.
FACT: Imdb is WRONG 70% of the time! Misspelled cast, incomplete cast, wrong cast/crew roles. So for those who want DVD Profiler to be "as perfect as Imdb", good luck with that.
Stop adding UNIT crew! They're invalid credits. Stop it! | | | | Last edited: by huskersports |
|
| Registered: May 25, 2007 | | Posts: 453 |
| | Posted: | | | | I only got (his great-grandfather?) "Buzz Feitshans". And your though is nice but I can't follow it.
If updates would work that way, allready the checkout for them will need much more time as during the process the database here should compare every single cast and crew member in my database, if it has a different parsing to correct |
|
| Registered: March 20, 2007 | | Reputation: | | Posts: 2,852 |
| | Posted: | | | | Quoting Magmadrag: Quote:
4. At once after release you check your updates and get back the profile - with a now wrong parsing Why? You've got what you want in your local database, locked it, and contributed it. Done. No more to worry about. --------------- |
|
| Registered: May 25, 2007 | | Posts: 453 |
| | Posted: | | | | It's your thing not to worry. But if I send data do a database which has nothing else to do than to keep it and get back it changed/modified, I would like to know why.
Is this the first time? Or have there allready been updates I didn't control with other "changes" from right to wrong? |
|
| Registered: March 13, 2007 | Reputation:  |  Posts: 3,197 |
| | Posted: | | | | The name is likely already in the database, albeit entered with a different parsing. Thus the parsing you submit will not change it but you will see it as a "change" since it doesn't match what you have. Whether you choose to accept the change or not will not actually change anything in your local database since parsing is ignored when downloading existing names. | | | | First registered: February 15, 2002 | | | | Last edited: by Nexus the Sixth |
|
| Registered: March 20, 2007 | | Reputation: | | Posts: 2,852 |
| | Posted: | | | | Quoting Magmadrag: Quote:
But if I send data do a database which has nothing else to do than to keep it... That's quite an assumption. It's no secret that there are filters applied to some of the data and Ken has his own ideas about what the online database should store. That's why I say no need to worry, because it's something out of your control. --------------- |
|
| Registered: May 25, 2007 | | Posts: 453 |
| | Posted: | | | | I know that it is out of my control, but we had other threads to recognize that other names exist with at least two different parsings in the database on the server. And the "joke" I never mentioned before:
They are initial profiles but created as Alt. Versions of existing profiles. Before I make it an Alt. Version, I check for updates. And none of them had any! So one Disc ID has the correct parsing on the server but the Alt. Version is automatically changed to wrong? Hard to believe and impossible to understand |
|