How do we treat "s.l." / "s.s." after taxon names during digitization?

[RebekkaML]

Some folders at the Herbarium have s.l. / s.s. (sensu lato/ sensu stricto - in a broad / strict sense) added to the Taxon name. Should the digitizers add this when digitizing? Can the DigiApp and the GREL script handle this? Do we want this information in Specify, and if yes, do we have to implement this ourselves or is it already possible?

Example: "Angelica archangelica L. s.l."

Necessary steps:

• Discuss with @PipBrewer and collections managers if we want to add this into Specify.
• If we want to, talk to Fedor about how we should do this.

[PipBrewer]

I reckon that would be treated as a suffix to the taxon name in the specimen record (not the taxon record). But would want to check with Jens S. Need to also check how we have dealt with suffixes when importing in the past.

[PipBrewer]

@FedorSteeman @AstridBVW The ss/sl should be added to the specimen record (to the addendum) in Specify. Do you have any suggestions about how we would deal with this in the DigiApp?

[FedorSteeman]

Yes, I think it should be added to the determination instance that is linked to the collection objection record.

To have this information imported we would probably need to make changes to the digi app to take into account whenever someone adds the "s.l." or "s.s." string. Or perhaps we can turn it into a radio button list, which is probably the safest. The postprocessing GREL script will also have to be adapted.

I was considering whether we could solve it just with the postproc GREL script but the problem is that adding one of these strings will make the app assume this is a novel i.e. unknown name to it. So the app will have to adapted.

[RebekkaML]

Discussed this issue with Fedor Steemann and Zsuzsanna Papp at the Data Issue Meeting 13.06.2024. The GREL script for imports into Specify needs to be reviewed and we need to determine how exactly it handles these instances and if it needs to be adjusted.