Key concepts

In alphabetical order, some key concepts to understand :


A collection represents a coherent and autonomous set of data: coins, table records, historical events, images, maps, etc. You can create as many collections as you want.

Imagine you have medieval coins and contemporary coins. Two possibilities :

  • Either you manage this data in a single collection, using for example a folder “Medieval coin” and another “Contemporary coin
  • Either you create two separate collections, which will not share any data

Note: When you select a collection, its name will always be displayed in the title of the software window.

How to structure your collection ?

There are probably as many methods of classification as there are collectors. To take account of this constraint, your coins will be stored in a tree structure, composed of folders, themselves composed of subfolders, etc. In an operation that is very similar to the one you already know with Windows Explorer. You are therefore free to define the tree that best suits your needs.
Note :

  • This tree structure is also adopted for historical events
  • You can drag and drop (or cut / paste) folders within the tree, which therefore remains scalable


The import/export functions are mainly intended for the exchange of data between collectors. They are available from the homepage. Simply select a collection, and target the data you want to export. For example, you can export only the table of monetary systems, or some historical events, or even your entire collection. The export result is a simple zip file.

You are free to include or not the images, knowing that the weight of the result file will of course be much more consistent with the images. Without images, the export file can easily be sent by mail. The recipient can then import this file into its collections.

Note :

  • Personal data are NOT exported (date of purchase, purchase price, etc.)
  • It is imperative not to modify the contents of the zip file, otherwise it will not be exploitable by NumismatPro
  • The import is also used to restore a backup file


The merge function is available from the home page. Suppose you have two distinct collections, A and B. Using this function, you can extract all (or part) of the data from A and merge it with the data in B (A-> B). In the same way as in the export function, it is possible to target the data of A which will be merged in B. For example, you have received the collection A from another collector, and the table of Issuing Authorities of A is particularly well informed. You can, thanks to this targeting, integrate in B only this table of Issuing Authorities A. Following this fusion, the collection A will remain unchanged.


You may already have many images of your coins and do not want a software to modify, or worse, delete these valuable images. To respect this constraint, NumismatPro systematically duplicates all images in its working environment. Therefore, your initial images will remain intact, whatever happens.

Note :

  • You can associate images with coins, as well as historical events. As many images as you want
  • The accepted image formats: jpeg and png. The compression of the jpeg is more important, which amounts to having files less voluminous. On the other hand, jpeg do not manage transparency, unlike the png format


Let us take an example: the coin of 1 franc Semeuse of 1975 and that of 1976 are identical in all respects, except for the Year.
We will create a model “1 Franc semeuse”, by providing in this model all the necessary zones: weight, historical events, diameter, composition, etc. Once the model is created, you will only have to create coins that inherit the model, and these currencies will inherit by default all the zones of the model. You will only have to enter the fields that differ for the coin in question. The year in the previous case (1975, 1976, etc.). In this way, you avoid having to enter for each coin always the same information. The notion of model makes it possible to accelerate and to make reliable the input.

This model management is particularly well suited to the capture of contemporary coins, which are often very similar and differ only in a few areas (often the year, mint marks or varieties).

Obviously, the search algorithm will take into account this notion of model.
To take the example above, imagine that you created a model with “Diameter = 20”, and 10 coins that inherit the model, knowing that they differ only by the year.
A coin search with “Diameter = 20” will display the 10 coins.
If now, in one of the inherited coins, you enter “Diameter = 21“, the same search will show only 9 coins.
In summary: if the field of an inherited coinis empty, the fieldof the model is retained. If the field of an inherited coin is entered, it is the one that takes precedence over the possible value present at the level of the model.

This notion of model will guarantee you a quick entry as well as a great coherence of the data.


The backup will save all the data of your collections, including images, and also personal fields in a single Zip file. It is recommended to make backups regularly. Never modify the contents of these Zip files, otherwise the restore may no longer work.

With the Import menu, you can restore all or part of your collection with one click.


There are fields whose number of values is not infinite. These values are stored in tables. For example, the different values in the “State of Conservation” field will be stored in the table of the same name.
This management has two advantages: reliability of the seizures on the one hand, and having to enter only once each value on the other hand.

Note that the majority of the tables have a “flat” structure, classic.
Some tables, however, have a tree structure, which has the advantage of being able to manage data of the “father / son” type, a little like the Russian dolls. For example, the issuing authority is in this case. An issuing authority may possibly contain other issuing authorities: an empire which would contain countries which themselves contained regions, and so on.

What does the lock on the records of some tables mean?
The tables already have pre-set values, indicated by a lock. This will make it possible to have a common repository for all users, which will facilitate the exchange of data between collectors. These values are locked, ie they can not be deleted. On the other hand, it is possible to make these values inactive if they do not concern your collection.
Obviously, the new values you create in the tables will never be locked.
Example: If you only manage European coins, it is enough to make the countries outside Europe inactive, which will never be offered in terms of seizure when creating a new coin.


A currency is described by a great deal of information. Each of these information is a field.
Example of field : Weight, Diameter, State of conservation, etc.

Field tile
NumismatPro offers a large number of fields as standard, which allows you to fine-tune your coins.
However, not all of the fields may be suitable for you. So you have the option of selecting the fields you want to exploit as part of your collection. This is the purpose of the Field tile available on the Home screen.
Example: a collector of contemporary currencies will have no interest in using the Globular field, rather adapted to the antique coins. Simply uncheck this area so that it no longer appears in NumismatPro.

Personal fields
You may want to have fields that are not provided in the software. Personal fields respond to this scenario.
A personal field is characterized by its type (character, Boolean, numeric or date) and its label.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s