Design & discuss frontend component for Class Masking feature

[f-PLT]

Summary

Brief description of the issue (tl;dr).

Detailed Description

Detailed description of the issue and why it is important. You can also talk about proposed ways to solve the issue if
the path forward is not clear.

Don't forget to add the appropriate labels and link the issue to a milestone if applicable.

Implementation Details

If possible, break down the tasks or steps needed to complete the solution.

Consider including:

• Approximate timeline
• Specific files or areas in the codebase concerned
• Possible problems or complications

Related Issues

If applicable, list of related issues

Additional Context

Add any other context or screenshots here.

[f-PLT]

@f-PLT Right this as a user story and how it fits into the workflow of the parent issue

[mihow]

Some possible places to put this:

• Project level setting (default list to use for masking) - won't work for Joe
• Job level settings
• Meta pipelines created from Antenna ("Newfoundland moths" pipeline would run Quebec pipeline, plus a specific class mask)

[annavik]

This has been worked on in January and February!

Step 1 has been to make taxa lists configurable from UI (class masking requires taxa lists). This feature has been designed and implemented, currently in review. See PR: #1094

Step 2 has been to think about how to configure post processing from UI. My suggestion is we handle this as pipeline configuration, instead of individual job configuration. In this way, more post processing functions in future will not make it more complicated to process data, but we still make it possible for advanced users to do more specific pipeline configuration when needed and to save and reuse this configuration. I have discussed this approach with @mihow and we decided to move forward with it. See screenshots below.

Step 3 is to go ahead and implement this. This will involve both FE and BE. I think we can consider the design and discuss phase as completed and open a new ticket for the implementation.

Here are some sketches, showing the idea:

[annavik]

I will close this as completed, because we have a plan defined for how to present this in UI, which this task is about. See comments above.

To start implement this, we need class masking features available from API on the backend side. We have talked about we could start simple with a read-only pipeline that has class masking built in and focus on presenting the details and output in UI, based on the sketches. I don't think this is available in production yet though.

TBC! :)

[mihow]

Class masking (#999) has since shipped without the design this issue asked for ever happening. Replaced by #1406, filed now that there is a real feature to design a front end for. Closing this one to avoid two open tickets asking the same question.