Issue 888: File > Import > Peptide Search with existing library reports the build settings in the Audit Log

issues
Status:resolved
Assigned To:Brendan MacLean
Type:Defect
Area:Skyline
Priority:2
Milestone:22.2
Opened:2022-05-09 14:36 by Brendan MacLean
Changed:2022-07-25 14:10 by Nick Shulman
Resolved:2022-07-25 14:10 by Nick Shulman
Resolution:Fixed
Closed:
2022-05-09 14:36 Brendan MacLean
Title»File > Import > Peptide Search with existing library reports the build settings in the Audit Log
Assigned To»Nick Shulman
Type»Defect
Area»Skyline
Priority»3
Milestone»22.1
The steps for the May Institute demo for the Selevsek data includes using the "Use existing" choice in File > Import > Peptide Search. This operation instead of simply listing the .blib file I used lists all of the values for the library build I didn't actually do. This needs to be fixed to list the library file path:

2022-05-09 14:25:42    Added spectral library "Bruderer2022-assay"
2022-05-09 14:25:42    Build Spectral Library > Cut-off score is "0.95"
2022-05-09 14:25:42    Build Spectral Library > Search files is Empty
2022-05-09 14:25:42    Build Spectral Library > iRT standard peptides is None
2022-05-09 14:25:42    Build Spectral Library > Include ambiguous matches is False
2022-05-09 14:25:42    Build Spectral Library > Filter for document peptides is False
2022-05-09 14:25:42    Build Spectral Library > Workflow is "DIA"
2022-05-09 14:25:42    Build Spectral Library > Input File Type is "Search results (build library directly)"

In may case, what I actually had was the path:

E:\test\2022-Selevsek2015\Selevsek90.blib

2022-07-15 13:24 Brendan MacLean
Priority3»2
Milestone22.1»22.2

2022-07-25 14:10 Nick Shulman
resolve as Fixed
Statusopen»resolved
Assigned ToNick Shulman»Brendan MacLean
Fixed in PR #2169