Coin Sets Buying Value Incorrect [solved]

6 posts • viewed 59 times

This message aims at: reporting a bug

Status: Solved
Upvotes: 2
Downvotes: 0

I posted this is the recent coin set post but seems to have been overlooked.

 

I entered $40.25 as the set's Buying value (US 2025 Proof Set). Instead of dividing the value over each of the 10 coins ($4.025) the value is listed for each coin so my collection increased by $402.50. 

 

I don't think it makes sense to divide the price by the number of coins in the segt.

Yes, the only value should be the entered one influencing a set value estimate depicted on the set page at some point in the future.

I'm not understanding. Shouldn't enter what you bought the set for?

On second read my sentence is quite a mess and was more an addendum than a comment on your post.
I meant you enter the price you bought it for (40.25$) and this goes into a Numista value estimate (that should be depicted on the set site some time in the future (there are no values now) which then should end up 1:1 (+40.25$) on your ‘My values’). So the item count should be irrelevant and not be used for Numista values of the individual objects (because of their often heterogenic nature splitting of value is non trivial anyway).

Yes, quite a mess.  😁

 

The problem is if I enter what I paid for the set when I enter the set that value is applied to all coins in the set.

 

So I enter $40.25 for the set:

Every coin in the set now has a Buying value of $40.25. The penny coin:

 

I'm not concerned with the Numista generated values. That will eventually work. I'm worried that for every set I enter my collection value will increase by the whole set value times the number of coins in the set.

 

I have one set in my new collection called ProofSets. I entered a value of $40.25 for the entire Set. The value of my ProofSets collection is now 10X that value.

 

Hello,

We made a fix. The value of the set is now counted only once, instead of erroneously multiplied by the number of items in the set.

Status changed to Solved (Xavier, 5 Jun 2025, 15:35)

» Forum policy

Used time zone is UTC+2:00.
Current time is 00:08.