Last modified: 2014-05-13 11:40:41 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T66593, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 64593 - Allow "speaking" values to specify the precision of a time value.
Allow "speaking" values to specify the precision of a time value.
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
WikidataRepo (Other open bugs)
unspecified
All All
: High normal (vote)
: ---
Assigned To: Wikidata bugs
u=dev c=backend p=0
: need-volunteer
Depends on: 64558
Blocks: 64545
  Show dependency treegraph
 
Reported: 2014-04-29 10:34 UTC by Daniel Kinzler
Modified: 2014-05-13 11:40 UTC (History)
8 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Daniel Kinzler 2014-04-29 10:34:48 UTC
Currently, when calling the API, the precision ofa time value has to be specified using an obscure number, e.g. 8 for a decade or 0 for a gigayear. We should accept obvious string values for these, and map them to the internal numeric representation during deserialization of the JSON structure supplied to the API call. We'll want at least the following to work:

"gigayear" => 0,
"megayear" => 3,
"kiloyear => 6,
"century" => 7,
"decade" => 8,
"year" => 9,
"month" => 10,
"day" => 11,
"hour" => 12,
"minute" => 13,
"second" => 14,
Comment 1 Nemo 2014-04-29 11:38:36 UTC
I added your example on mailing list to <https://www.mediawiki.org/wiki/Wikibase/DataModel#Dates_and_times>
Commenting on that here: https://www.mediawiki.org/wiki/Thread:Talk:Wikibase/User_manual
Comment 2 Markus Krötzsch 2014-04-29 14:04:41 UTC
A "kiloyear" is usually called a "millennium".

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links