Issue 804: Implement simple filtering for MSP file import

issues
Status:open
Assigned To:Brian Pratt
Type:Todo
Area:Skyline
Priority:3
Milestone: 
Opened:2021-05-10 by Brian Pratt
Changed:2021-05-10 by Brian Pratt
Resolved:
Resolution:
Closed:
2021-05-10 Brian Pratt
Title»Implement simple filtering for MSP file import
Assigned To»Brian Pratt
Type»Todo
Area»Skyline
Priority»3
There's an ongoing problem with reading .MSP format spectral library files into Skyline: they tend to be mixed bags of spectra from different machines, different CE values, any number of things we don't track in our internal library format. We advise users to filter before import but it seems that in many cases there isn't any ready way to do this.

If we implemented even a simple filter where users could create a lists of criteria that didn't involve any parsing, just straight string checks:
Entry must (not) contain phrase
(repeat as needed)

it would be really useful, I think. It could pop up instead of our current "conflicts found, you should filter" message and give the user to run the import over again as needed.