4 years later, I still have the same issue with collections.
I have the same issue with other information too, like "modified date" for instance.
I see the modified date from the day the file was added to the collection, and when I look at the properties I see the correct date (today for instance).
How can you update the file info in a collection ? (f5 doesn't help).
I hope I'll get a bit more feedback than 4 years ago about the same question.
It should happen automatically, if Opus can see the change at all.
Does this happen even with a simple test collection? e.g. Create a new collection at the top-level (not nested), and add just one text file from your desktop to it, then edit the file. Does the size update after a second or two?
Under Preferences / Miscellaneous / Advanced, what are these set to? Is either set to a non-default value (it will be in bold if so)?
it is a simple collection of files located on the network, no nested collection.
collection_change_delay is default (5000)
no_external_change_notify is default (false)
I have something interesting to add to this description.
I have set up an highlight for files modified within the last hour (following one of your great videos you used to publish for each new Dopus version, speaking about them, I miss them !!) .
Guess what, once I check the file properties within Dopus, then the file is highlighted in the collection, but the modified date column doesn't show the change at all.
I did another test, added a file from a network location, then if I edit and save the file from the collection, then the date doesn't change.
If I do the same from the lister displaying the remote folder, then the collection is updated.
I also tried to add a local file in the same collection (the files I add in collection are usually located on Windows network share):
I set a created and modified date in 2014.
then I added the file to the collection.
I edited the file from a remote computer (through d$ share) and the date and size were correctly updated within 1-2 seconds.
Network folders explains it. Collections cache the details of network files and don't monitor them for changes, since it could be problematic to monitor every folder containing collection items over the network. (For local folders, we can monitor the whole system with a small overhead, but there's no provision in Windows to do that over a network.)
Updating the cached values is probably going to be a matter or removing & re-adding the items. That can be automated for a whole collection using DOpusRT: External Manipulation of File Collections, or could be done for just selected files via a script. (Of course, a script could also be written which does both, and refreshes the whole collection if nothing is selected.) Time permitting, I might be able to look at writing that, although I can't right at this minute.
I would have loved to find a condition to make this button available only if sourcepath is a collection.
I searched but couldn't find how to do it. Is it possible ?
Also, I would love to have way to do it without relying on an external file and risking to lose the collection if anything goes wrong (because of the /clear flag).
I know you can't add all user suggestions, but wouldn't it make sense to refresh the file properties if a user does a Refresh in a collection ? I would seem logical to me, after all this is the goal of a standard "Refresh", to get the current information.
many thanks, I spent my efforts with the modifier IF and I didn't see the hideifpath option.
Thanks to you, I have now found the disableifpath modifier too, which is perfect, until a real Refresh is added, without having to reconstruct the collection.