Open a-tze opened 6 years ago
jjeising
commented
6 years ago I partially see where this is coming from, but I'm yet unsure how this would be related to automated actions.
What I can imagine here are ticket tags, maybe even in place of needs attention, that freely assignable and reusable. A project could use tags like repaired-audio or manual-recording and use the search to filter tickets to tags (and move states manually for special actions).
a-tze
commented
6 years ago Tags sound even better.
In any case they should be completely free definable, but I'm unsure if there should be a set of predefined tags. So that users can use them right away without having to think of a tagging scheme first.
jjeising
commented
6 years ago This could be solve with a simple input with autocomplete. Already used tags will be preferred for completion and supplemented with a predefined standard set (maybe slightly dimmed). This would allow simple usage for standard case and fast definition of new tags.
An additional tag administration page in the project preferences could allow renaming (and with this merging) of existing tags.
We could also add a pre filled color coding which could render 2px vertical bars for the tickets as added visual aid.
While fixing a bigger amount of material, it seems like there should be a separate boolean flag for tickets, that should be set (by a human) as soon as there is some fixing done outside the automated toolchain. Needs-attention and comments are very helpful, but difficult to evaluate in the automated parts of the toolchain.
However I'm not really sure how this should look like. In most cases it is desirable that encoding is not happening automatically for repaired material, but the following steps/states are, so it's probably a bad idea to exclude tickets with this flag from automation completely.