id summary reporter owner description type status priority milestone component version resolution keywords cc 1447 "Annotation importer should have ""crop"" option for the ""Too many values"" error handling option" Nicklas Nordborg Nicklas Nordborg "There are use cases were one of the batch importers is used together with the annotation importer on the same file. The batch importer requires that data for a single item is mapped on multiple lines because it has references to multiple parents (eg. a single hyb may have multiple labeled extracts). For administrative reasons it is easier to just copy the complete first line and just update the parent references. But this creates a problem when using the file with the annotation importer, which now sees the duplicated annotations as a list of several values, when in fact there is only one value. This ""error"" is catched (or ignored) by the ""Too many value"" error handling option, but none of the options allow the annotations to be set. A third option is needed that is similar to the ""crop"" option for handling string values that are too long. The new option would ignore values that makes the list longer than what is allowed by the annotation type. I don't know if ""crop"" is the best word for it though... The workaround is to clear the annotation columns in all but the first line. The batch importers will still work, since they will ignore those columns. " enhancement closed major BASE 2.14.2 coreplugins fixed