2½ Centésimos "Panama Pill" 1904/1905 [solved]

2 posts • viewed 59 times

This message aims at: requesting the modification of a coin in the catalogue

Status: Done
Upvotes: 0
Downvotes: 0

Hi. I searched for a bit before making this, so if it has come up previously I apologize in advance!

I see that while the coin may be minted as 1904, it was actually minted in 1905. I am fine with recording that kind of info as it is interesting and relevant.

However, I was attempting to use the API to add my example of this coin, and part of the logic care about the ‘minimum date’ and ‘maximum date’ fields, and my coin's listed year (in my spreadsheet, which is 1904 as minted).

The problem is that because of the way the date has been recorded “1904 (1905)” on Gregorian Calendar, it means the system sees the Gregorian year equivalent (1905) of the recorded date (1904), and the API returns the following for this type:

# This block is the ‘Type’ entry

   "id": 20590,
   "title": "2½ Centésimos ("Panama Pill")",
   "category": "coin",
   "issuer":
   {
       "code": "panama",
       "name": "Panama"
   },
   "min_year": 1905,
   "max_year": 1905
}

# And this is the ‘Issue’ entry
{
   "id": 109626,
   "is_dated": true,
   "year": 1904,
   "gregorian_year": 1905,
   "mintage": 400000,
   "comment": "Minted in 1905"
}

I suppose the question is, should Gregorian Date (min_year & max_year) represent the date physically minted, or the converted Gregorian equivalent of the ‘date’ field? How are other coin issues with similar situations? (literally minted in a different year than is minted on the coin itself)

I don't have an example handy, but im sure they aren't hard to find if I needed to.

I'm curious to hear thoughts on this. Not a big deal since i can just add the coin manually and move on. 😀

Hello,

 

I am closing this, just procedurally, because there is nothing for me to change.

 

This situation is caused by usage of forced “redating”. It is used mainly for calendars that do not start at 1st of January, thus do not correspond to Gregorian calendar and we sometimes have to manually amend date conversion. Here it is used as well, while producing “ok” result for ordinary users, API sees through it, and tells you exactly what happened. What it does not know is that both these lines:

 

"year": 1904,
   "gregorian_year": 1905,

 

are gregorian.

 

Best regards,

Jarek

Catalogue administrator
Status changed to Done (Jarcek, 2 Jun 2022, 08:35)

» Forum policy

Used time zone is UTC+2:00.
Current time is 14:41.