Open gbilder opened 1 month ago
The issue is simply one of granularity—some dates (e.g., "published") can be partial, and the original metadata doesn't include a time component. However, it would be good if all dates (partial or otherwise) were represented consistently, even in string form. So, for example:
Published date parsing seems incocnistent across different Crossref content types:
For example, JournalArticles always return the Published date as a YYYY-MM-DD string.
However other contents seem to also include trailing time info. Here are examples:
In each case the published date seems to include trailing time info as well.
For example, with the last item in the above list:
results in:
What is very odd- is that the date in the JSON above ("2004-10-26T09:47:24Z") seem to be extracted from the :
Which is the date the record was createed, not the date the item was published.
http://api.crossref.org/works/10.1109/vlsic.2004.1346548/transform/application/vnd.crossref.unixsd+xml