Verifier and resources handling

Anything and everything to do with DCP-o-matic.
IoannisSyrogiannis
Posts: 249
Joined: Mon Nov 13, 2017 8:40 pm

Verifier and resources handling

Post by IoannisSyrogiannis »

There is one aspect of the verifier that I am trying to manage, and I would like some input from anyone using it, or from Carl, or whomever may have some insight on best ways to go about it. Another perspective should be helpful.
Once in a while, I come upon a storage device (drive, NAS, etc. etc.) that has a good number of DCPs. Occasionally, VFs inside OVs, for the love of any supreme being. But, either way, with a lot of dealing with file structure.

The recent updates of the verifier were a huge help and a time saver. Honestly great, to not have to run "find" commands to look for asset map files and try to correct all those characters to escape and compile strings (series) of CLI commands, in order to do what I now do in a few seconds, a couple of minutes, most.

Yet, since I need to somehow moderate the extend of use of the storage, or to prepare as much when I am absent to be able to work when in place, and then the rest, etc. etc. I came up with (eventually) two ways.
1) To ask for a feature that would either schedule the initiation of the verification, or that it would be able to be posed and postponed, or stopped after the running verification and be saved. Hence the Mantis entry 2991 and a relevant one linked there.
2) To remove from (or, scarcely, add to) the list of the jobs that appear after scanning a storage, in order to make an estimation (based on intuition, mostly) on the time necessary to run the verification I chose (with „extras“ or not).

Going the second way, I have to deal with the fact that I can not extend the list pane vertically, so to have a wider view of it. Also, I can not multi-select, by Shift or Ctrl/Cmd. That is relevant to not being able to Ctrl/Cmd + A either, resolving to close the application, in order to remove a number of entries fast, before scanning the next storage.
Also, while the list populates itself with the folder names (and that is not a bad thing), when a DCP can be under a folder named by the CPL's UUID, or the folder could have a duplicate, it's hard to distinguish and filter. Believe it or not, there are DCPs that are hosted in folders by the name DCP.

So, I was trying to add another feature request, that would have to do with the sorting of a mess that -I suppose- could have to do with more than me. The problem is, that I don't know what the simplest solution would be to those... devilish entanglements I come upon every now and then (again). It seems to me that the naïveté of people and the random actions that build up entropy constitute an unsurpassable masterpiece of collective work! :lol:

So, here I am, appealing to the collective of you, us, for ideas of what would make things more manageable in a simple way.
Any ideas? Something one uses on another field and could easily apply here? Some distinction or sorting, or depiction that would enlighten the situation?