Mapping Residency

[philbarker]

I don't see much in CEDS we can use, the closest is residency type which just gives a US-centric view of in/out of state/district for tuition [fees] purposes.

The current model has

(Person) --residency--> (Residency)

(Residency) --pesc:countyCode
                    --pesc:stateProvince
                    --pesc:county
                    --pesc:country
                    --pesc:stateProvinceCode: [defined code]
                    --pesc:countryCode [text]
                    --pesc:residencyStatusCode [text]

Possible solution is to

• keep pesc:residency and pesc:Residency property and class
• use the ceds residency type for pesc:residencyStatusCode
• use locality, region, country terms from CTDL for location properties, i.e.:

use ceterms:addressLocality for both pesc:countyCode & pesc:county use ceterms:addressRegion for both pesc:stateProvince & pesc:stateProvinceCode use ceterms:addressCountry for both pesc:country & pesc:countryCode

This merges text and coded values, which may be a problem, if so we could specify that the properties should have structured values that comprise both, e.g.

    "ceterms:addressRegion": {
       "notation": "CA",
       "prefLabel": "California"

Though this kind of breaks CTDL.

BTW ideal solution is to have a URI for the place at, say, "county" level and everything else comes as linked data via that, e.g. "residencyLocation": "https://www.wikidata.org/entity/Q507957", but who has that data to hand.

[philbarker]

Decided on today's call to keep the current properties, maybe merging to use notation and prefLabel as shown above, but with pesc: property not CTDL. Need to write tests.

[philbarker]

• [x] Change property name pesc:residency to pesc:hasResidency for consistency / clarity of property Vs class name
• [x] Shape target objects of hasProperty
• [x] Write test cases: include in maximal passing and create failing tests.