NPGObjThesTerms2 should be mapped

[VladimirAlexiev]

NPGObjThesTerms2 includes very useful concepts that should be mapped:

count	ThesXrefType	map to	URL example
1974	Execution place	Creation Location	npg/place/tgn/World/continents/North_and_Central_America/nations/United_States/states/California/counties/Los_Angeles/inhabited_places/Los_Angeles/neighborhoods/Hollywood
19011	Medium	Object Materials	npg/thes/Medium/Ink
5338	Other Classification	Classification	npg/thes/Other_Classification/Abstract
60	Place depicted	Subject
29363	Portrait Objects	Subject
5456	Portrait Setting	???
52	Related place	Subject
1265	Shape	crm:P2_has_type	npg/thes/Shape/Oval
15130	Sitter Type	??? see below
13141	Support	Object Materials	npg/thes/Support/Paper

I think that Sitter Type should be mapped to crm:P2_has_type such as "individual portrait", "group portrait", "non-portrait"...

$ csvgrep -c 2 -m Sitter NPGObjThesTerms2.csv|csvcut -c 3|sort|uniq -c|sort -rn
    193 Individual
     13 Non-portrait
      8 Group
      7 Political
      4 Professional
      3 Unrelated
      3 Artistic
      2 Couple
      1 Term
      1 Parent(s) and Child(ren)

The last col (URL Example) applies only if NPG does not map the respective set of concepts to AAT & TGN. If they map the concepts, use AAT directly. For TGN, use tgn:nnnnn-place not just tgn:nnnnn

[bsnikhila]

I mapped everything except for the shape and the sitter type. I was not sure the Shape goes in as P2_has_type. I felt the object 'has shape' Oval rather than 'is of type' Oval. But if you want me to map it that way, I'll go ahead and do it.

[VladimirAlexiev]

@workergnome @azaroth42 what do you think?

[workergnome]

I don't think there's an easy way to explicitly model shape, so thinking of it as a classification rather than a description of geometry makes sense to me...it's not a great as it could be, but I don't know if there's a better middle ground within the CRM.

[azaroth42]

:+1: to P2. What we mean is "This object is an instance of the class of Oval things".