Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data Type of datetime values of claimed publications missing #4051

Closed
matthiasluehr opened this issue Feb 13, 2025 · 0 comments · Fixed by #4052
Closed

Data Type of datetime values of claimed publications missing #4051

matthiasluehr opened this issue Feb 13, 2025 · 0 comments · Fixed by #4052
Assignees
Milestone

Comments

@matthiasluehr
Copy link
Contributor

Description:

When importing a publication using the DOI claiming tool the publication's
DateTimeValue-Node is specified not as
http://www.w3.org/2001/XMLSchema#dateTime data type but rather as a plain
string:

http://vivoweb.org/ontology/core#dateTime "2015-01-01T00:00:00"

On the other hand, when crafting a publication manually using the UI it's
done properly:

http://vivoweb.org/ontology/core#dateTime "2015-01-01T00:00:00"^^http://www.w3.org/2001/XMLSchema#dateTime

Thus using SPARQL's aggregate date and time functions against the date time values generated by
the DOI claimer wont work.

To Reproduce
Claim a publication, edit the individual, find the DateTime Value and display raw statements of it:

Image

The date is stored as a string.

Expected behavior
Should be stored as http://www.w3.org/2001/XMLSchema#dateTime data type.

Additional context
Check for bogus date time values:

SELECT ?uri ?litval ?year
WHERE {
  ?uri a <http://vivoweb.org/ontology/core#DateTimeValue> .
  ?uri <http://vivoweb.org/ontology/core#dateTime> ?litval .
  BIND (YEAR(?litval) AS ?year)
  FILTER (!bound(?year))
}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

3 participants