hydrusnetwork
Integration of file services into the duplicate filter and improvement of file moves
The current and recently overhauled file services are working great, at least for my purposes, but the way they are kept isolate from a duplicate filter adds an unnecessary workflow of keeping services tidy.
Take these three file systems, as an example of my IRL usage of Hydrus
- Everything, the main filesystem and the original one, where all files are initially dumped
- 2D where I move drawings that I have checked and ensured they meet my standards, both quality wise and tag wise
- 3D identical to (2) but with IRL pictures.
The duplicate filter recognizes services and allows you work under one, multiple or all, but does not allow to set a weight to each file services nor to move a file depending on it. For example, if (2) has a weight of 50 and (1) has a weight of 10 but the file on (1) is better, said file should be moved to (2) after finishing the batch of duplicates in order to keep a steady flow of curated files to such a service.
Similar to this steady flow of files concept, automated moving of files that the user has archived with a certain tag would also improve the usage of this. Allow me to explain.
The user sets a rule in which a file that is both
- Archived
- Has X tag or a combination of.
- Doesn't have dupes
Should always belong to (2).
A file in (1) is a drawn image of Samus Aran. The user dupe checks it and it has the certified tag of creator:taissart alongside character:samus aran. Upon archiving it, the file is automatically moved -be it during maintenance, shutdown, idle...- to (2), therefore creating a curated ecosystem of images, videofiles and whatnot. A file that is in (1), being a picture of a cosplay of Samus Aran, despite being archived would not meet the criterion to be moved to (2) since for example, the user has only set certain creator: tags as the need for it, keeping (2) strictly 2D.
