List of which settings are Per Database, Per User, or Per Computer?

[GrantRobertson]

Is there a comprehensive list of which settings are Per Database, Per User, or Per Computer?

When changing a setting from a default, it would be nice to know if I am going to have to re-set that setting each time I create a new database. Or, more importantly, it would be nice to know which settings I can set up differently for each database. Sometimes, I may want to do something one way in one database and another way in another database.

Personally, I think every description for every setting should mention this.

[Mario]

Is there a comprehensive list of which settings are Per Database, Per User, or Per Computer?

Or per user/database? Per machine/user? Per machine/database? Per machine/user/database?

No. IMatch maintains about 300 settings in the settings database.
I don't see any need to document this. Because as soon as the documentation would be finished, it would also be outdated.

I am going to have to re-set that setting each time I create a new database.

Did you know that 99% of all IMatch users get by with one database? (According to telemetry).
And, from what I understand, most of the remaining 1% use a second database for testing stuf

IMatch does not have the limits some other on-premise DAMS have, like limited number of assets per database, which forces the users to create multiple databases if they exceed that limitation.

I maintain about a half a dozen databases. My own and 6 databases for testing.
"My" database was created by IMatch 3, maybe 15 years ago. Since then, I used it and it grew and was updated seamlessly with each IMatch version. It manages about 900,000 files.

Except from maybe the thesaurus or some category setup, I never had to transfer anything from one database to another.

[rolandgifford]

Or per user/database? Per machine/user? Per machine/database? Per machine/user/database?

No. IMatch maintains about 300 settings in the settings database.
I don't see any need to document this. Because as soon as the documentation would be finished, it would also be outdated.

The settings help page mentions that there are settings at different levels. I don't need or want a comprehensive list of every setting but it would be useful (to me) to know which type of setting is at user level.

I have a single computer/database but two Windows users. Currently I'm the only one looking at IMatch but my wife will eventually get round to looking at her photos and she will also do updates, under a different user. Our needs and styles differ so it would be useful to know what sort of thing we can set at a user level. I expect these to primarily be layout differences but I don't know yet what they will be so a list of the sort of thing that I may want to consider will help.

[Mario]

For two users, you will need to licenses for IMatch. Just saying.

A settings database currently stores about 600 individual entries (aka settings) linked to a user id.
Adding workspaces grows this to about 25,000 entries (assuming a small number of workspaces).

You can always use an User Name Alias for your wife so she can share settings with you.

If you want me to document all this for your personal use, contact me via support email address and we can discuss terms, cost, contract, legals, deliveries and a time frame.
If you pay for it, I can justify to spend a week or two on documenting all these settings and when they are applied. This will take some effort and this will be costly.

But, I guess for the vast majority of IMatch users, all this is totally irrelevant.
Does Adobe give you a list of settings they store per user in their applications? Does Windows? C1? DxO?...
Really, who needs this?

I would really much prefer to spend my development time with something productive.
Improving IMatch. Create new features. Fixing bugs.
There is only so much time in a day.
But if I can earn some good money by documenting IMatch internals and which settings are linked to a user and when they are applied, why not?

[sinus]

...
Does Adobe give you a list of settings they store per user in their applications? Does Windows? C1? DxO?...
Really, who needs this?

...

Yep, that is the point for me.
If users from IMatch have problem or a proposal, Mario does look into it.
If he sees, ok, this is a bug, he will eliminate it.

If he sees, yep, that is a cool proposal, he will add it.
And Mario reads (I guess) every single post here on the forum from users, and mails and so on.

So, try this with Adobe. Photoshop. Or Microsoft. Or a camera-producer with some crappy software. Sometimes it works and they listen to you. But mostly they do not care, what you are writing.
 IMatch, means Mario, cares.

[rolandgifford]

For two users, you will need to licenses for IMatch. Just saying.

Surprising, thanks for pointing that out.

I had missed that particular point in the Licence where I can install the software on lots of PCs providing only I use it. I had expected that one software installation on one PC with one database would be one licence, it seems that I'm mistaken.

[Mario]

For two users, you will need to licenses for IMatch. Just saying.

Surprising, thanks for pointing that out.

I had missed that particular point in the Licence where I can install the software on lots of PCs providing only I use it. I had expected that one software installation on one PC with one database would be one licence, it seems that I'm mistaken.

IMatch is licensed per user.
The licensed user can use IMatch on any number of computers, provided that she/he is the only IMatch user on these computers. Many IMatch users have a desktop and notebook and I'm not greedy. But each user needs a  separate license.

[rolandgifford]

Many IMatch users have a desktop and notebook and I'm not greedy.

I have the reverse, I'm not in any way suggesting that you are being greedy.

It would be useful (but possibly not worth your effort) to install only for the logged in Windows user rather than available for every user of that PC. A warning/error message when an unlicenced user runs the software would probably help as well.

Neither makes any difference to me as I'm honest and now know the rules. I will either buy another licence for my wife or stop using IMatch. I don't know which, there is no current rush to decide. Both of us being able to maintain our own photos within the same database is an absolute requirement for us (when she gets round to it).