You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In cases where multiple sheets are present on a data load (e.g. Biocode Team) and for which the data is FIRST loaded using events and samples, and then SECOND reloaded with the "Replace Expedition data" box checked-- with some parent identifiers removed, the invalidParentIdentifier Rule check does not work as expected...
For example: load EventID = 1 and EventID =2 (with associated samples)
Then remove EventID = 2 -- any materialSamples referencing that EventID will be silently dropped.
A workaround for now, is to first check the box "only validate data" BEFORE replacing expedition data.. This will catch the error. (also, i have added a message about this in the data validation and loading page on the UI)
The issue here is that when replacing the expedition data it also references existing parent/child entities in the database during the validation step that may not be present in the workbook-- this is very important in cases where we link photos/fastq data, for example, that we do not want to drop. In the current case, the Events tab IS in the loaded file and we need to write an exception to NOT look in the database for entities that are present in the workbook itself. I think we need to look in the DatasetController class to fix this.
The text was updated successfully, but these errors were encountered:
In cases where multiple sheets are present on a data load (e.g. Biocode Team) and for which the data is FIRST loaded using events and samples, and then SECOND reloaded with the "Replace Expedition data" box checked-- with some parent identifiers removed, the invalidParentIdentifier Rule check does not work as expected...
For example: load EventID = 1 and EventID =2 (with associated samples)
Then remove EventID = 2 -- any materialSamples referencing that EventID will be silently dropped.
A workaround for now, is to first check the box "only validate data" BEFORE replacing expedition data.. This will catch the error. (also, i have added a message about this in the data validation and loading page on the UI)
The issue here is that when replacing the expedition data it also references existing parent/child entities in the database during the validation step that may not be present in the workbook-- this is very important in cases where we link photos/fastq data, for example, that we do not want to drop. In the current case, the Events tab IS in the loaded file and we need to write an exception to NOT look in the database for entities that are present in the workbook itself. I think we need to look in the DatasetController class to fix this.
The text was updated successfully, but these errors were encountered: