Extension of this editable table task
Story
In some cases, a Spectronaut report will have the column R.Run Date. This date can be used to extract the run order for anomaly scores. However, the date can be formatted in multiple different ways and it's up to the user to decide if the column exists (a user has to specify for spectronaut to include it). But if R.Run Date is a column in the report, users should see a table that's filled out with run order when they enable use of anomaly scores. The table should also be editable in case a user needs to make corrections.
Subtasks
- If a user clicks to enable anomaly scores:
- If the
R.Run Date column exists, create a table with the three columns: Run (not-editable), R.Run Date (not-editable), Parsed Date (not-editable), and Order (editable).
- If the
R.Run Date column doesn't exist, then create a table with only Run (not-editable) and Order (editable).
- Note: Users should still have the option to upload a CSV file for cases where there's hundreds of runs and Excel's copying and pasting would work best. Tooltip would need to provide clear instructions on how the CSV upload works, but the table columns displayed in Shiny should provide users a good idea of what's required of the CSV file.
- Note:
Run corresponds to the R.FileName column of the Spectronaut report.
- Add code to parse through the
R.Run Date and determine the run order - see here for example code
- My recommendation is to have a function that applies the 5-10 most standard ways of parsing dates. I recommend using a Chatbot here.
Acceptance Criteria
R.Run Date can be used to get the run order.
Extension of this editable table task
Story
In some cases, a Spectronaut report will have the column
R.Run Date. This date can be used to extract the run order for anomaly scores. However, the date can be formatted in multiple different ways and it's up to the user to decide if the column exists (a user has to specify for spectronaut to include it). But ifR.Run Dateis a column in the report, users should see a table that's filled out with run order when they enable use of anomaly scores. The table should also be editable in case a user needs to make corrections.Subtasks
R.Run Datecolumn exists, create a table with the three columns:Run(not-editable),R.Run Date(not-editable),Parsed Date(not-editable), andOrder(editable).R.Run Datecolumn doesn't exist, then create a table with onlyRun(not-editable) andOrder(editable).Runcorresponds to theR.FileNamecolumn of the Spectronaut report.R.Run Dateand determine the run order - see here for example codeAcceptance Criteria
R.Run Datecan be used to get the run order.