Change data type for attribute taxonIdCH

[morelanneIF]

Current situation

The taxonIdCH attribute is currently defined as such in the following file

%{
dwc_field: "taxonIdCH",
dwc_link: nil,
dwca_file: nil,
attribute: %Attribute{name: :taxon_id_ch, type: :integer, allow_nil?: true}
}

Desired situation

Change the attribute:type from integer to string

Example of value: infofauna:100

Accepted if

[ ] taxonIdCH = infofauna:100 can be imported with the Validation Imports (validationResponse)

[morelanneIF]

@luchszebbra This is a blocking element for the validationResponse, because the data coming from the center will always be a string

[cloedu87]

type change is not possible because we need this field for referencing other tables.

what we do now is stripping away the center at the beginning (if present) and parse it to integer before we update the database.

[cloedu87]

shipped w/ release 1.5.6

[luchszebbra]

Question: What happens if a record is being validated and ingested via validation import and the taxonIdCH provides a different swissSpeciesCenter than the Encoding?
swiss_species Encoding: id = infoflora:12345 => swissSpeciesCenter = infoflora and taxonIdCH = 12345
Validation: taxonIdCH = infofauna:54321

a) Is this a real case?
b) What to do?

Before we were not able to ingest infofauna:54321 and now we're able to ingest it by splitting the string. We put 54321 into taxonIdCH (validationLayer) and as far as I can see we ignore infofauna and do not put it in swissSpeciesCenter (Validation Layer).

The record then looks like:

Layer	taxonIdCH	swissSpeciesCenter
Raw	-	-
Encoding	12345	infoflora
Validation	54321	-

Edit: This is only about whether to put the swissSpeciesCenter into the validationLayer as well. the taxonIdCH is an int - this is by design and mustn't be changed.

[morelanneIF]

@luchszebbra it is not a problem to put the text part of the taxonidch into the swissSpeciesCenter of the validated layer. The goal of this layer is to be exported back into the institution, so it is up to them to decide what they keep or not. Plus, a different data center on the validation layer has no impact whatsoever.

[luchszebbra]

Thank you for the response: What do yo think - shall we write the swissSpeciesCenter onto the validation Layer or not? Thank you!

[morelanneIF]

Yes, please. I can then inform the users on how to rebuild the taxonIdCH if they want to.

[luchszebbra]

@cloedu87 Please add 'swissSpeciesCenter' to the validationLayer.

[morelanneIF]

@luchszebbra Hello ! I read in this issue that the addition of swissSpeciesCenter should have been shipped with the 1.5.6 version ? Still it is the one we have on our test env but this is still not to validate and the swissSpeciesCenter is still empty..... Could you inform me on the current status of this issue ?

[luchszebbra]

@sidler92 Please quickly have a chat with @cloedu87 and probably just create a new release; I guess this has been missed.