Duplicate versions sets??

[Bobbert]

I have no idea why this occurs. I have 3 files, same filename different extensions. I select all three and "right click" "version selected files". PSu does it's thing and I have one image with three versions embedded. THEN I move to a different folder, view some images and go back to the folder where I created the version set. NOW I see THREE copies of the version set, one with each of the different files as the "main version". Kind of defeats the purpose of version sets in the first place! If I "destroy version set" then all three files are properly displayed again.

Am I doing something wrong, or is this a bug??

Thanks.. Still learning - I have 21 days left on my trial but if this problem gets solved, I become a happy paying registered user

[Hert]

If version sets would be restricted to files within a single folder then you would have a point. But version sets don't have this restriction and you can add files from several folders to one version set. Eg. Consider this version set:
Folder A/Image A
Folder A/Image B
Folder B/Image C

If you visit folder A you will see what's there, and that are 2 image files: A and B. If you visit folder B then it gives you also what is there and that is one file: C. If the version set would be displayed as one set then PSU would be lying to you as there's not 3 files in Folder A, nor in Folder B.

Version sets are only displayed as a single set in the CATALOG-By Category....in other words, when you're cataloging. When you view FOLDERS then it shown you what is in that folder! despite if and how the files in that folder are versioned.

[Bobbert]

Thanks for the quick explanation. It works exactly as you say.

BUT... I actually disagree with the approach. I'd like version sets to reduce clutter in my folder view too. What is wrong with showing the version set in the folder, and have the "out of folder "images indicated by a placeholder?

[jstartin]

BUT... I actually disagree with the approach. I'd like version sets to reduce clutter in my folder view too.

I think many users, perhaps most users, when once they have got used to it do agree with the way in which versions/version sets are displayed. Personally I use Folder View quite rarely, and when I do it is for some "special purpose" and I very definitely want a separate thumbnail for every file in the folder.

What is wrong with showing the version set in the folder, and have the "out of folder "images indicated by a placeholder?

Perhaps I am misunderstanding you, but you seem to describe what does happen now. If you have a Version Set consisting of"file1" "file2" and "file3" and they are present in the following folders:
folder\file1
folder\subfolder\file2
folder\subfolder\file3
then Folder View of "folder" will show only "file1" as a thumbnail, with tabbed markers for the other versions. Folder View of "folder\subfolder" will give separate thumbnails for "file2" and "file3" but not "file1".

[Bobbert]

Yes, you misunderstand me... I keep all my derived images in the same folder as the original. In the folder where file2 and file3 are kept the folder view shows file2 and file3 but not file1 as you say. But it does not combine file2 and file3 into one "version" display. I see TWO images, file2 and file3 separately. both indicate that they are part of a version. What I would like is to collapse file2 and file3 in the folder view... perhaps this is called "stacking" in other software.

Were PSu to do that it could indicate that file1 is part of the version, but not in the selected folder. That way my folder view would be less cluttered with derived images too.

Maybe this is a new feature request?

[vlad]

I am of two minds here: on the one hand I understand the (legacy?) argument that the folder view is aimed to presenting all image files in a folder (rather than their "photographic" content); OTOH the distinction does seem somewhat arbitrary, especially now that the folder view has been seamlessly integrated in the Catalog->All view. (Btw, I applaud this implementation!) After all, a folder could be regarded in PSU simply as another collection criteria rather than as a container of physical image files, couldn't it? (An argument could be made that an operation such as Verify Folder must refer to all the physical image files, but this still doesn't require per se that versions are always expanded in the folder view, especially if the verification result is open in a different tab.)

As a new PSU user, I had initially been confused myself by when versions would show up and when not, especially when filters (which could refer to versions) were also involved. Perhaps it would be useful to have in any collection view an option indicating whether to collapse the image versions in the active collection? I'm thinking the checkmark could be placed next to the filter icon, for example, and thus be quite unobtrusive. The checkmark could be initially enabled by default in all views, except when viewing images by folder - this would be fully compatible with the current behaviour but would allow it to be overriden on demand. What do you think?

[Mike Buckley]

I keep all my derived images in the same folder as the original. In the folder where file2 and file3 are kept the folder view shows file2 and file3 but not file1 as you say. But it does not combine file2 and file3 into one "version" display. I see TWO images, file2 and file3 separately. both indicate that they are part of a version.

Either I'm misunderstanding you or you are perhaps using a filter that prevents file1 from being displayed. On my system, all three files would be displayed in the folder view. When I want to eliminate the clutter, I use a filter that displays only one of the versions, depending on the version that I decide to display.