1,477,004
edits
Item talk:Q3: Difference between revisions
From geokb
→Caching raw data as schema.org documents
No edit summary |
|||
| Line 9: | Line 9: | ||
In the case of ORCID, we have native JSON-LD Person documents already and are shifting to storing those from older methods that used the full ORCID JSON structure. | In the case of ORCID, we have native JSON-LD Person documents already and are shifting to storing those from older methods that used the full ORCID JSON structure. | ||
Storing raw content, not all of which is processable into the knowledge graph, in wiki pages has the added benefit of immediately adding content to the overall search index in the Wikibase instance while we hash through additional reference data mapping. This can be accessed directly using the search form or Mediawiki API. While this is not as specific and transitive across the entire knowledgebase as a SPARQL approach, it does open up possibilities for additional use patterns to leverage larger chunks of text or data structures not yet fully digested into the knowledge representation. | Storing raw content, not all of which is processable into the knowledge graph, in wiki pages has the added benefit of immediately adding content to the overall search index in the Wikibase instance while we hash through additional reference data mapping. This can be accessed directly using the search form or Mediawiki API. While this is not as specific and transitive across the entire knowledgebase as a SPARQL approach, it does open up possibilities for additional use patterns to leverage larger chunks of text or data structures not yet fully digested into the knowledge representation. | ||
== Periodic Updates == | == Periodic Updates == | ||
The caching process is managed through the statements for a person recording their USGS profile URL (P145 "official website") and ORCID (P106). To aid in managing automated caching tasks, we record | The caching process is managed through the statements for a person recording their USGS profile URL (P145 "official website") and ORCID (P106). To aid in managing automated caching tasks, we record three details in qualifiers on the official website claims: | ||
* last update (P129) date indicating when we last ran an HTTP operation on the URL | * last update (P129) date indicating when we last ran an HTTP operation on the URL | ||
* status code (P151) indicating if the resource was available or not | * status code (P151) indicating if the resource was available or not on the last update date | ||
* retrieved (P139) date specifying when we last retrieved information from the | * retrieved (P139) date specifying when we last retrieved information from the official website source | ||
<sparql tryit="1"> | <sparql tryit="1"> | ||
PREFIX | PREFIX geokbe: <https://geokb.wikibase.cloud/entity/> | ||
PREFIX | PREFIX geokbp: <https://geokb.wikibase.cloud/prop/direct/> | ||
PREFIX p: <https://geokb.wikibase.cloud/prop/> | PREFIX p: <https://geokb.wikibase.cloud/prop/> | ||
PREFIX pq: <https://geokb.wikibase.cloud/prop/qualifier/> | PREFIX pq: <https://geokb.wikibase.cloud/prop/qualifier/> | ||
| Line 28: | Line 26: | ||
SELECT ?item ?url ?last_update ?retrieved ?status_code | SELECT ?item ?url ?last_update ?retrieved ?status_code | ||
WHERE { | WHERE { | ||
?item | ?item geokbp:P1 geokbe:Q3 ; | ||
geokbp:P145 ?url ; | |||
p:P145 ?url_statement . | p:P145 ?url_statement . | ||
OPTIONAL { | OPTIONAL { | ||
