| Message |
Details |
Just a thought:
When you download a profile and it has a person w/o birth year, and your local database has the same name with a birthyear, the person in the downloaded profile will get that birthyear. This is the problem that Magmadrag wants to avoid.
But ... what's to say that the exact same thing doesn't happen if you add a profile (without a birthyear) through the API? It might be a good idea to test this - if not already done - before investing a lot of time and effort. | Posted: Topic Replies: 168, Topic Views: 10502 |
 |
Quoting mediadogg:
Quote:
Quoting GSyren:
Quote:
Quoting Magmadrag:
Quote:
I would need to export my (whole) collection to xml and export doesn't work anymore. It runs and runs... and at about 99 % the Error-Popup comes...
DVD Profiler can be a bit unstable. So if I had that problem, I wouldn't want to mess up my database further by trying to add stuff via the API. But that's just me. At least not without first finding a way to fix that export problem.
I assume that you have tried a database repair? I realize it's really slow with a database of that size, but it should be done.
That's hilarious. Adding stuff with the API is the Invelos provided, and sanctioned way to do things programmatically. In general, you don't "mess up" the database any more than the main program does when it has a bug. That's why we test and make backups. People should not fear plugins.
What I mean is that if the database is already compromised (export crashes) then I wouldn't try to add data en masse. Not through the API or otherwise. Not meant to disparage plugins in any way. | Posted: Topic Replies: 168, Topic Views: 10502 |
|
Quoting Magmadrag:
Quote:
I would need to export my (whole) collection to xml and export doesn't work anymore. It runs and runs... and at about 99 % the Error-Popup comes...
DVD Profiler can be a bit unstable. So if I had that problem, I wouldn't want to mess up my database further by trying to add stuff via the API. But that's just me. At least not without first finding a way to fix that export problem.
I assume that you have tried a database repair? I realize it's really slow with a database of that size, but it should be done. | Posted: Topic Replies: 168, Topic Views: 10502 |
|
Like I said:
Quote:
For each such name, create a cast (or crew) entry without a birthyear. This I don't know if it is possible to do through the API.
So yeah, it's just a listing. If it's no help at all, then sorry! | Posted: Topic Replies: 168, Topic Views: 10502 |
|
I whipped up a little program to see if this is something useful to you.
It lists all cast in your collection that does have a birth year, but has no matching non-BY entry.
To keep it simple I just used cast, but if you think it's useful I can add crew too.
BySpecial 1.0 | Posted: Topic Replies: 168, Topic Views: 10502 |
|
I was asked by mediadogg if I could write a graphical user interface for CommandOnEvent, so I did:
CommandOnEventGUI 1.0 | Posted: Topic Replies: 7, Topic Views: 4924 |
|
@Magmadrag:
What you suggest would entail two steps:
1) Create a list of names that have birthyear, but does not have a corresponding non-birthyear entry. A tool that does that is fairly easy to develop.
2) For each such name, create a cast (or crew) entry without a birthyear. This I don't know if it is possible to do through the API.
Even if it could be done, creating a cast/crew entry that is not connected to a profile has its problems. If you do a full database repair, the name will be gone. I think it will survive a basic database repair, but I'm not sure.
However, I believe there is an even bigger problem with your suggestion. Let's take David Brown as an example since you used that name. Presumably the Non-BY actor occurs in fewer movies than the BY actors. So if an update comes down without a BY for an actor that should have a BY, then it will accepted without a BY since there is such a cast entry in your database. Thus you get an incorrect linkage to the Non-BY actor.
Basically this is a design flaw in DVD Profiler itself. There is no way to distinguish between "birthyear known but not (yet) entered" and "birthyear unknown", and I don't see how this can be reliable fixed by a tool at the local level. | Posted: Topic Replies: 168, Topic Views: 10502 |
|
There might be a way to do that, depending on how you intend to use the text file.
1) Create a report. Select "Microsoft Print to PDF" as printer. Printing creates a PDF file.
2) Use ProfilerQuery. Create a query with the fields you want. Run the query. Select "File / Save result to file". This saves the result as a .CSV file, semi-colon separated.
Would either of those do? | Posted: Topic Replies: 2, Topic Views: 2380 |
|
| Ditto | Posted: Topic Replies: 8, Topic Views: 6126 |
|
| I have been binge watching good old ”24” with Kiefer Sutherland. | Posted: Topic Replies: 99, Topic Views: 21315 |
|