^^For the last few weeks, mythicalLibrarian will not delete data if the file is put into the --doover que. This means, if it was a low-confidence match, mythicalLibrarian will not delete the database, and you can doover the file.
You can hand-edit the dover.sh to remove previous data. If you are unsure, then delete ~/.mythicalLibrarian/doover.sh.
There will be a future modification for the --doover que which will ask you to manually identify files and remove them from the --doover que. User identified files will be treated as high confidence and therefore removed from the --doover que. I'm thinking it will be a dialog menu based system for use during --doover.
But, for now, your que will build up unless a high confidence match is made. You can type the following for more information on how to improve your confidence ratings.
Code:
mythicalLibrarian --confidence
ubuntite Wrote:Ok, I don't quite know what all this means. Do I need to add another user job to my mythtv setup to delete recordings, or will your script continue to delete my recordings from my mythtv database, just using a new method?
For now, you can continue using what you've been using. The depreciation is just a warning for the future. I will be removing the functionality from the core of mythicalLibrarian eventually. The reason is I don't want to try to maintain backwards compatability with a feature I don't use. It makes it simpler to just have it as a user job.
The user job is simple...
Code:
test "$RequiresDoover" != "1" && /usr/local/bin/MythDataDeleter "$InputFile" --writeFile --output="$MoveDir/$ShowFileName.info.txt" |tee -a "$mythicalLibrarian/output.log""
which basically says: If this file is not in the --doover que, then run MythDataDeleter on the file, write the database output file to $MoveDir/ShowFileName.info.txt, and put all terminal data into the mythicalLibrarian log.
I need to pretty much rewrite the enitre wiki.