Open valentinedwv opened 1 week ago
right now summary query just includes schema:datePublished.
OPTIONAL {?subj schema:datePublished ?date_p .} BIND ( IF ( BOUND(?date_p), ?date_p, "1900-01-01") as ?datep ) .
iris has no date published, but has a dateCreated and dateModified. something like this might work.
OPTIONAL {?subj schema:datePublished ?date_p .} OPTIONAL {?subj schema:dateCreated ?date_c .} OPTIONAL {?subj schema:dateModified ?date_m .} BIND ( IF ( BOUND(?date_p), ?date_p, if (BOUND(?date_c), ?date_c, if (BOUND(?date_m),?date_m, '') ) as ?datep ) .
We need to incorporate those, and prepare for a dateRange search over the temporal values generated by the (future) stacindexer.
also query the triplestore to see what exists.
prefix schema: <https://schema.org/> select (count(?s) as ?count) where { ?s schema:datePublished ?o }
prefix schema: <https://schema.org/> select ?s ?o where { ?s schema:datePublished ?o } limit 1000
This also needs to be checked... some distributions have datePublished.... that might make more than one record.
urn:gleaner.io:eco:geocodes_demo_datasets:data:e6243fdf074d088b1e1215547e77ac4431067f89
urn:gleaner.io:eco:geocodes_demo_datasets:data:d82062e44ed98aa19718b2461a2a15c7c6dd51a3
test with geocodes_dmeo_datasets, see if the date fields exist
if these exist, need to add those to summary
right now summary query just includes schema:datePublished.
iris has no date published, but has a dateCreated and dateModified. something like this might work.
We need to incorporate those, and prepare for a dateRange search over the temporal values generated by the (future) stacindexer.
also query the triplestore to see what exists.
This also needs to be checked... some distributions have datePublished.... that might make more than one record.
urn:gleaner.io:eco:geocodes_demo_datasets:data:e6243fdf074d088b1e1215547e77ac4431067f89
urn:gleaner.io:eco:geocodes_demo_datasets:data:d82062e44ed98aa19718b2461a2a15c7c6dd51a3