Update help

[Carlo Didier]

Remembering a thread about versioning and propagation, I also remembered that metadata replication (including categories, etc) does not work if a new version of an existing image is added to iMatch.
Let me explain.

Case 1: A master and one or more versions exist already in the iMatch databbase. Metadata for the master is changed and this is replicated to the version(s) as specified by the users' propagation settings. Ok.

Case 2: Same as above, but a new image is added to iMatch and identified as a new version of a master. In this case, no propagation is done! Apart from the fact that this is not what I would expect, it is not clearly explained in the help topics about versioning propagation (unless I just haven't found it)

If case 2 is by design, then it should be clearly documented and I will post a feature request to change it.
If it's a bug, I'll post a bug report.

[Mario]

By design, IMatch propagates changes made to metadata in the master to all known versions. If you add a version afterwards, IMatch will not copy data from the master to the version automatically. We discussed this already several times, search for additional info. Many users would not want this to happen, for example.

If you add a version later from the outside, either change something in the master to trigger the propagation, or propagate manually once.

[Ferdinand]

I understand Carlo's concern, but I support the current behaviour.  I want to control when certain resource intensive things occur, and this is one of them.  Mario introduced some additional commands early on - like F4,T - which enable you to propagate to just the new versions.  With this command I don't see that there is a real issue.  You can bookmark new images or assign them to a collection or category, and then easily select them all for propagation.

There is an issue IMHO with this workflow, but it's a separate one, and so I'll post separately.  It's about when a new version is identified as a new version. 

[Carlo Didier]

I understand Carlo's concern, but I support the current behaviour.  I want to control when certain resource intensive things occur, and this is one of them.  Mario introduced some additional commands early on - like F4,T - which enable you to propagate to just the new versions.  With this command I don't see that there is a real issue.  You can bookmark new images or assign them to a collection or category, and then easily select them all for propagation.

There is an issue IMHO with this workflow, but it's a separate one, and so I'll post separately.  It's about when a new version is identified as a new version.

I don't know if my workflow is so unique, but by default I always want my categories to be propagated to new versions and right now, this is only possible with a script that re-inplements the rules otherwise defined in the file versioning rules, so to avoid double work, I don't define versioning rules and do it all by script (automatically!).