One identity across datasets
A term, place, person or organization that a publisher aligns to an authority LOL covers is one document, shared by every dataset that references it, with that authority’s description. One that nobody aligned stays local to its dataset.
Where an authority’s description comes from
A document keyed on an authority’s URI – a GeoNames place, an RKDartists person, a Getty AAT concept – takes its description from that authority, read through the Network of Terms, NDE’s lookup service for terms by URI. authority names the vocabulary, and fetchedAt says when the description was read.
The indexer looks terms up when it builds the index, not when you query it, and stores what it gets. It fetches a stored description again after 30 days, and at most 1000 terms per run. So:
fetchedAtis usually older than the index, and an authority’s correction can take a month to reach LOL.- A new term may keep the publisher’s description for a run or two, and so may every term after a release that changes what the indexer keeps per term.
- An outage changes nothing you can see: the stored description is served. A term that was never fetched keeps the publisher’s.
A missing authority means the publisher did not align the term, the authority has no description of it, or the indexer has not fetched it yet. The response does not tell the last two apart. How the indexer limits its requests is in its README.
The same concept in two datasets
It depends on whether the term is aligned to a vocabulary LOL covers.
Where a publisher points a term at a covered vocabulary – both LDMax collections do, with a local node whose sameAs is http://vocab.getty.edu/aat/300028051 – the term is keyed on that URI. So is a term whose own id is the vocabulary URI. One concept is one document with one id, whichever datasets reference it, and it carries its authority’s description: language-tagged names, the alternate names that vocabulary knows it by, and authority and fetchedAt saying where they came from and when.
Where a term is aligned to nothing LOL covers – Discovery Museum points “keramiek” at AAT’s web page http://vocab.getty.edu/page/aat/300235507 instead of the term http://vocab.getty.edu/aat/300235507 – it stays local. Two datasets describing the same concept then give you two terms with two ids and two labels, and what they share is sameAs. That is what to compare on, not the term’s own id.
For an uncovered term, matching a concept across datasets is two queries. Find the terms first:
{
terms(
where: { sameAs: { in: ["http://vocab.getty.edu/page/aat/300235507"] } }
) {
items {
id
name {
value
}
}
}
} Run queryThen filter works by the ids you got back – all of them, since each dataset has its own:
{
creativeWorks(
perPage: 0
where: {
material: {
in: ["https://n2t.net/ark:/11978/ee7c7800add9423cad664d2d6765d325"]
}
}
) {
pagination {
total
}
}
} Run queryA term with no sameAs and no canonical id of its own cannot be matched at all, and deliberately so: nothing in the data says two similarly named local terms are the same concept, and the search API does not guess.
A term the authority could not describe keeps the publisher's. authority is absent on it, which is how you tell the two apart – and it happens for a reason worth knowing: a lookup by URI does not reach every term a vocabulary holds. Roughly a third of the Getty AAT references in the register resolve to nothing today, because the terms live in AAT sub-vocabularies that a URI lookup does not route to (netwerk-digitaal-erfgoed/network-of-terms#1943). Those keep an untagged publisher label until it is fixed upstream.
Places are the other case of the first shape, and the point of the next section: they are keyed on the term they align to whether the publisher used its URI as an id or stated it as sameAs, so one place is one document and one id.
Place references arrive through their own fields – locationCreated and contentLocation on a work, location on an organization, birthPlace and deathPlace on a person – and resolve against places, while about, material, genre and additionalType resolve against terms. A publisher may describe one place as either, so a location reference can be a Place, a DefinedTerm, or a node typed both.
additionalType also holds a work’s schema:artform. Limburgs Museum and Discovery Museum put their object types there (bord, gravure, munt), and a few genres such as ‘portret’ come along with them.
A place is one place
Where a publisher aligns a place to a term in GeoNames, GTAA or Wikidata – or names it by that term’s own URI – the place is keyed on that URI, and every dataset referencing it points at the same document. Drapo and Limburgs Museum both hold something about Venlo, and it is one place, one id, one facet bucket:
{
places(where: { id: { in: ["https://sws.geonames.org/2745641/"] } }) {
items {
id
name {
value
}
latitude
longitude
addressCountry
authority
fetchedAt
}
}
}name, latitude, longitude and addressCountry come from the authority that owns the identity – authority names it, fetchedAt says when it was read – and not from the publishers, whose descriptions of a term they merely referenced are dropped rather than merged. Neither selected dataset ships coordinates at all, so this is the only place a map gets them.
The name is the one the authority states for the place itself: “Venlo”, not “Venlo (NL)”. GeoNames answers a suffixed label to tell homonyms apart in a picker – “Bergen (NL)” against “Bergen (NO)” – which is a disambiguation, not a name. It reaches you as addressCountry instead, so you can render or filter on it rather than parse it back out of a string.
A place nobody aligned keeps the publisher’s id and the publisher’s description. LOL does no entity matching: “Kessel” appears in both datasets as a local place and stays two documents, because neither publisher said they are the same. Such a place carries no authority.
The facet and the filter differ, deliberately. Only canonical places get a facet bucket, so an unaligned place cannot be reached by faceting locationCreated – but a filter on its id matches, and asking places for it works. Facets are discovery over a result set; filters are exact retrieval, and narrowing the first leaves the second whole.
One artist, however many collections credit them
Persons work like places. Where a publisher aligns a person to an authority record – RKDartists, Wikidata, the KB thesauri or GTAA – or names them by that record's own URI, the person is keyed on it, and every dataset crediting them points at one document:
{
persons(where: { id: { in: ["https://data.rkd.nl/artists/80083"] } }) {
items {
id
name {
value
}
alternateName {
value
}
birthDate
deathDate
hasOccupation {
id
name {
value
language
}
}
authority
fetchedAt
}
}
}name, alternateName, birthDate, deathDate and hasOccupation come from the authority, through the Network of Terms, not from the publishers. Discovery Museum publishes Max Verboeket as his RKD record with a name and nothing else; RKDartists adds “Verboeket, Maximiliaan Leo Hubert Maria”, 1922-07-08, 2015-01-23 and fourteen occupations, glasontwerper and glass designer among them. The alternate names matter most: an authority records the variants a person or firm is also known by – “Céramique Maastricht, N.V. Keramische Industrie genaamd” beside “Société Céramique, N.V.” – and those are searchable, so a visitor typing the trading name finds the works.
A date is the period the authority states. RKD gives Rembrandt’s birth as 1606-07-15/1607, and birthDate serves exactly that, filtered by overlap like a work’s dateCreated. A birth the authority can only place in a decade is 162X.
A person nobody aligned keeps the publisher's id and description, and carries no authority – the same rule as for places and terms.
An authority only describes what it names. A publisher may align a person to something that is not a person; where that happens the person keeps the publisher’s own node and name rather than borrowing a place’s. So a missing authority is not always a missing alignment – sometimes it is the alignment being declined. The same holds where the node’s own id is a place a publisher also typed schema:Person: the person document carries the publisher’s name and no authority.
An occupation is an entry, and its id is usually null. The profile lets a publisher state an occupation as a term or, where none exists, as a resource with only a name, and RKD states every one of Verboeket’s fourteen the second way, once per language. Each is served as an entry with its name and no id, the same shape as a creator named inline on a work: displayed and searchable, filterable only where it has an id, and there is no facet over it. The reasoning is in the NDE alignment guide.
birthPlace and deathPlace are empty on a person the authority describes. The authority’s description replaces the publisher’s whole, and RKD names a birthplace by its own thesaurus, which no places document is keyed on, so nothing fills the field yet. A person nobody aligned keeps the publisher’s.
Organizations are keyed the same way, on an alignment to RKDartists, Wikidata or the KB thesauri. Limburgs Museum aligns Société Céramique to https://data.rkd.nl/artists/104628, so organizations serves the firm under that id with RKD’s name and alternateName – “Clermont en Chainaye, Aardewerkfabriek” among them – its location and its authority and fetchedAt.
An organization’s location carries its own name. RKD places Société Céramique in https://data.rkd.nl/thesaurus/46, “Maastricht (stad)”, a place from RKD’s own thesaurus that no places document is keyed on. So each entry carries the name the authority states beside its id, and where a places document does hold the id, its description replaces that name. An address an authority states only as text, as the KB does, is an entry with a name and an addressCountry and no id. The field filters on id; there is no facet over it. There are no dates: the NDE profile gives an organization none.
An institution appears twice
publishers and organizations are separate collections, and the same institution is routinely in both – under two different URIs, with one name.
- A publisher is an agent in a dataset's registration, identified by whatever URI the registrant used.
- An organization is an agent the object data relates to a work.
Neither URI resolves the other, so you cannot join them: to go from an institution to its works, start from publishers, get its datasets, and filter works by those – the two-query pattern under From one institution.
From one institution
There is no join across collections, so this is deliberately two queries: find the publisher’s datasets, then filter works by them.
{
datasets(where: { publisher: { in: ["https://www.tracelimburg.nl/"] } }) {
items {
id
name {
value
}
}
}
} Run queryFeed the returned ids into the second:
{
creativeWorks(
perPage: 10
where: { dataset: { in: ["https://id.drapo.nl/dataset/drapo-schemaorg"] } }
) {
pagination {
total
}
}
} Run queryFiltering datasets by publisher is the right direction: each dataset carries its own publisher, so the answer is complete. Going the other way – asking a publisher which datasets it has – is not currently reliable, because a document records only one dataset.