Quoting mediadogg:

Quote:
CLTInfo gets 330

No, CLTinfo gets 366, same as you, only divided into two separate groups based on F/M/L.
If you feel that that's the wrong way to do it, take it up with AiAustria. I have no personal stake in how the data is presented.

Why would the correspondence be a coincidence? CLTinfo takes your output from CltBoss and formats it according to how AiAustria wanted it. If you get 366, I get 366.

There is no "search" in CLTinfo. It takes all of the info in your output and presents it in a structured way.

You certainly didn't offend me. I was just trying to clarify why my results corresponds to yours.

So basically, I am asking if you agree that it would be a good idea for me to include a "<Variants>" element in my export, to make it clear how the included credits were found. That way, CLTInfo (for example), would know up front how the data was gathered, then of course offer other ways to view it.

Does that make sense?

Quoting GSyren:

Quote:
Quoting mediadogg:

Quote:
So basically, I am asking if you agree that it would be a good idea for me to include a "<Variants>" element in my export, to make it clear how the included credits were found. That way, CLTInfo (for example), would know up front how the data was gathered, then of course offer other ways to view it.

Does that make sense?

Not sure what you mean by variants. Are those the (1), (2), (3) you mentioned before? Or are we talking about something else?

The whole point of the CLT and the notion of "common names" is that people are often known by different variants or aliases or variations in their names. It happens a lot with Asian names, as they are often reversed from what the actor uses in their native country. I apologize if "variant" is incorrect terminolgy.

In the contributions threads, it is often referred to as "name variant."

So, "ziyi zhang", "zhang ziyi", and "zhang zhi" are three variants of the credited name for the same "Crouching Tiger" actress.

But I know you knew all that, so maybe I misunderstood the question?

Quoting GSyren:

Quote:
Ok, I'm still not clear on how you intended to use the <Variants> field. Would it contain all name variants found, or just the variant(s) used in the search? Or something else? Would it be a single field for the entire export, or a field for every profile?

Well it is just an idea at this point, not implemented. The problem just became apparent, and once again it demonstrates the value of collaboration. It hadn't occurred to me that it was a problem.

It should reflect all the variants that were used to produce the XML credits collection in question. In the case we are just discussing, it would have "ziyi zhang". That would indicate that while other variations might be found in the profile XML (or even in the same credit because by definition creditedAs and F/M/L can coexist - its just that is inconsistently used). One entry for the entire collection.

So, you can see this by typing into the CLT tool:

"ziyi zhang", " ziyi zhang", "ziyi zhang " or " ziyi zhang "

all will yield 364 profiles (as of today).

Note that "ziyi  zhang" yields 0 profiles!!!!  (double space between the names)

This match can come  from either CreditedAs, or from any concatenation of F/M/L.

I have seen the credit completely contained in the firstname with middle and last and creditedas blank, or as first+last, or as middle+last. And in this case you have the possibility of getting double blanks, and is stuff like this that is driving me nuts. In order to be consistent with the CLT, I have to actually ignore a possible intended match that doesn't work just because somebody typed "ziyi  zhang" instead of "ziyi zhang" into the CreditedAs field.

I already have a "CLTName" class in my code, that I think I will map over into the XML. It will be something like:

<CLTSearchNames>    (or "<Variants>)
  <CLTSearchName firstname ="ziyi", middlename="", lastname="zhang", birthyear="", hashname="zhang_ziyi_">ziyi zhang</CLTSearchName>
</CLTSearchNames>

My instructions from AiAustria were to match "search name" first on CreditedAs if found in the credit entry, otherwise match on the concatenation of F/M/L, case insensitive and with leading and trailing blanks removed.

So, that's where I am. I appreciate your patience, and I am open to suggestions.

Quoting GSyren:

Quote:
Ok, so basically <Variants> would be the search arguments used. That sounds like it might be useful in some cases.

Thanks. I hope so. I will move along this path. So if somebody uses CLTBoss to scrape multiple variants (I can't tell whether they are really the same person in the code), then the resulting XML will always be an "OR" of the credits, with the combined set of profiles. My profile list grid actually contains the "hashname" version of the name, as part of my duplicates detection, so it makes me think ...

Your question about a variants per profile is now coming to mind, but I am still fuzzy. Do I need to reveal how each profile made it into the list? I think so, since my XML contains only the matched credits. If instead, one is looking at the "Invelos Export" output, you will of course get all credits, and all XML contents of each profile.

What should I do? I'm a bit confused. I hate to clutter up the XML, but how else to avoid the issue we hit earlier, by not knowing what filter was used to create the XML?

Ok, I am just discovering a fast and powerful Xpath tool inside CookTop XML editor.

Using this statement, "nodes: /CLTInfo/DVD/CLTCredits/CLTCredit[@CreditedAs!='' and @FirstName!='' ]",

I confirmed that the file in question had exactly 36 credits where F/M/L = "Zhang Ziyi", but CreditedAs was "Ziyi Zhang". That why we got the same "36" from the same profiles. There are 3 others returned by the same XPath query where the exact opposite is true!!! F/M/L is "Ziyi Zhang", but CreditedAs is "Zhang Ziyi".

This is just way too much for CLTBoss. I want to just spit out the results (in either CLTBoss or Invelos formats), consistent with CLT, and make it clear where the profiles came from, and then hopefully other tools will allow more sophisticated filters to be applied. Above my pay grade and intentions.