Previous Taxon recorded on identification from upload page is the same as the identification taxon (instead of null/undefined)

This is probably not a problem most people will notice, since this is revealed only by looking at the API response for a get request that includes observation details.

If you add an observation in the web upload page and include an identification at the time of upload, it looks like the previous taxon recorded for that identification is the same as that initial identification taxon (ex.

If you add an observation with no identification and then later go back and add an identification, it looks like there is no previous taxon recorded for that identification (ex.

It seems like the behavior should be consistent, and there should not be a previous taxon recorded on the first identification, regardless of whether it was loaded with the observation or if it was added after upload.

Unless maybe the intent of “previous taxon” is to preserve the observation ID present when the record was initially created?

the previous observation taxon is recorded on each identification. (i think there is a separate previous observation taxon that can be recorded with the observation, but that’s not what i’m talking about.) as far as i can tell, in every case except for when the identification is created at upload, the previous taxon is the observation taxon that existed just before the creation of the identification.

1 Like