Menu

Suggestion: Add Gregorian date column to the Excel export

6 posts

This message aims at: suggesting an idea to improve Numista

Status: Implemented
Votes: 27
Author Message
January First-of-May
Joined: 10-Apr-2016
Posts: 702
A few weeks ago, I wanted to figure out which years I have the most coins from (and which years I didn't have any from), and it turned out that Excel export sucks at this - the only available "date" column is the one with the local dates, which has relatively useless numbers for Muslim, Japanese, Thai and Israeli coins (and a few other less common weird cases - Ethiopia is particularly insidious, because their dates are only a few years off).
So I had to do the counting by hand, which took me half a day.

As such - would it be possible to add the Gregorian date (or something equivalent) to the Excel export?
I'm pretty sure a lot of people would want to know which years they have coins from, and right now all the different-calendar stuff makes it impossible to figure out if you export to Excel (even though such an export would feel like the obvious way to figure out stuff like that... really I'm not even sure what it can possibly be used for in its current condition, since we don't do import, but that's another question entirely).

Sorry for the wall of text, incidentally.
(Also sorry if this particular suggestion had already came up - my cursory forum search only found it as a combination with lots of other stuff, and I wanted to mention it individually.)
Cyrillius Numista team
Joined: 5-Jun-2013
Posts: 1818
I support, I also need it.
tamarf
Joined: 13-Oct-2014
Posts: 2
Very good idea.
jelle
Joined: 18-Oct-2014
Posts: 605
Or select one ;)
Some want Arabic or Jewish
yinfeld
Joined: 8-Oct-2014
Posts: 1
I think it will be helpful.
Status changed to Accepted (Xavier, 12-Apr-2019, 11:46AM)
Status changed to Started (Xavier, 12-Apr-2019, 11:46AM)
Xavier Site admin
Joined: 16-Jan-2007
Posts: 4049
Hello,
The export is now configurable. You may add a column for the year in the Gregorian calendar.
Status changed to Implemented (Xavier, 12-Apr-2019, 10:10PM)

Used time zone is UTC+1:00.
Current time is 01:54PM.