Data elements annotation not jumping to tag text#570

In the extraction interface, the data elements are not sorted by tagged status and the “annotation” option doesn’t jump to the tag text. Having the tagged data elements at the top is useful, and having the tag text annotation for reference is definitely key to the extraction workflow for us. This issue started for me yesterday evening and others on our team have also reported it, in multiple nests that were previously working normally. Let me know if there’s something we should try on our end or any other information that would be helpful!

Thanks for sharing Erin– we intentionally removed Tagging annotations in MA Extraction to make way for annotations that can be attached to a Data Element during MA Extraction, which in turn is a necessary feature for Smart (automatic) MA Extraction that’s in the works. We felt we could/should remove the Tagging annotation because it’s relatively confusable & duplicated with this new feature.

We were aware this wouldn’t be a backwards compatible change, but assumed it wasn’t such a critical aspect of workflows. It sounds like that was a misjudgement on our end, apologies for the interruption to your work.

We’re discussing how we might add this back in, I’ll get back here with plans.

Thanks for the context! Our current workflow uses form-based tagging to identify the data (both qualitative and quantitative), which really streamlines extraction, so it would be great to restore those existing connections (making the extraction annotations match the tag annotations), but we could adapt to the new system in the future. Thanks!

OK– we have a design in place to add this data back to the display while also not rolling back the existing DE annotation selector. We’re going to rush to complete this by early next week!

Sounds great, thanks Karl!

Status update, we’ll be restoring this functionality, within the current design / styling, in the next release (most likely tonight).

Awesome, thanks for the update!

This functionality should be restored as of release 1.95.3, please let us know if that’s not the case. Thanks!