Uploaded image for project: 'Picard'
  1. Picard
  2. PICARD-193

Make remove tags logic in MetaDataBox more intuitive/flexible

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Normal Normal
    • 1.0
    • 1.0
    • Tags & Metadata
    • None

      Loving the new metadatabox, but think the logic here could be a little bit smarter and more flexible. I understand that with current Picard implementation that if you don't have clear_existing_tags selected then this means it can't remove an existing tag from one of your files. This makes sense.

      However this logic makes the behaviour a bit inconsistent between situations when you do and do not have files matched/linked to MB metadata. Currently if you don't have any files linked, since everything is considered "Added" you can click "Remove tag" which appears to cause it to be removed from the MB/"new" metadata. When you later link a file, the "new" tag is gone, which is exactly what one would expect.

      However once you've already matched/linked 1+ files, there's no easy way to achieve this that I can see. It'd be nice if there was an easy way to essentially say "Reset to original value" even once it's linked that behaves essentially the same as when you click "Remove tag" without linking anything.

      I'd actually quite like to make it consistent in naming between the two approaches but can't quite think of a good description that makes sense in both cases, and also makes sense when removing "newly added" tags. Would it make sense for "Reset to original value" to cause complete removal of a tag if you didn't already have it in your file; or if the file is not already linked? Maybe?

      Assigning you for comment Michael, not to require you to do anything nor agree

            bitmap Michael Wiencek
            voiceinsideyou voiceinsideyou
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:

                Version Package
                1.0