This is not as straight forward as the title of this issue might suggest.
The simple solution would be to allow only ancestries part of the schemes enum to be allowed, which would guarantee the pipeline to finish. But,
-
It is however interesting to add ancestries not part of the enum, in case we add such references in the future. It will generate an error right now, but that is likely due to my latest large update to the update_stats sub-workflow. It should be simple to fix. Regarding IBPs internal active inventory, we only use EUR, right now, so no projects are on hold due to this.
-
We should not allow free text, but instead guide the user to the Study_Notes: field. To decide what is free text and what is an actual pop-code could be debated, but as far as I am aware, it would be ok to only allow one word to be used as study_ancestry.
This is not as straight forward as the title of this issue might suggest.
The simple solution would be to allow only ancestries part of the schemes enum to be allowed, which would guarantee the pipeline to finish. But,
It is however interesting to add ancestries not part of the enum, in case we add such references in the future. It will generate an error right now, but that is likely due to my latest large update to the update_stats sub-workflow. It should be simple to fix. Regarding IBPs internal active inventory, we only use EUR, right now, so no projects are on hold due to this.
We should not allow free text, but instead guide the user to the Study_Notes: field. To decide what is free text and what is an actual pop-code could be debated, but as far as I am aware, it would be ok to only allow one word to be used as study_ancestry.