Automatically back-propagate tags from data extraction#349

Can I automatically tag a study as a result of extracting data?

Good question! We received a similar request previously (https://nested-knowledge.nolt.io/86), and currently offer this as a bulk action, completed one tag at a time:

• Go to Inspector
• Add Filter - Data Element, and select the data element you want to ‘back-propogate’
• Select Bulk Actions
• Under Tagging, select the relevant tag.
• This will apply the relevant tag to all underlying studies, but without related tag-text.

If this workflow is too burdensome, we can consider an “Auto-back-propogate all Data Elements”; please let us know if that is of interest!

@Ranita Tarchand want to communicate the Bulk Action to clients who are interested in back-propagation?

This is duped with https://nested-knowledge.nolt.io/350 - should we move conversation over there?

NM, more traction here.

@Corey.jew tracking your request here!

While I mostly like tag propogation in extraction, there are several considerations:

1. Is this a configuration, or something we impose on everyone? I think it’s going to be very confusing if not all or nothing. e.g. getting very different tagging interactions when jumping between nests with different configs
2. When a DE is deleted, what happens to applied tags under that DE? This may get very confusing if the tags were manually created (not back-propogated)
3. Does this feature reduce the quality of applied tags? Propogated tags would lack both an excerpt and an annotation, which we know provide a lot of context/supporting info & make auditing work simpler.

Good questions–

1. I think it has to be an option/configuration. Otherwise, we are populating content without people’s plans.
2. Users may appreciate if deletions are also back-propagated, but I think our general approach is not to ‘link’ tags to DEs after creation. I think it’s simpler to make the new tags independent of the DEs.
3. Yes, I think back-propagation is a non-optimal solution to a case where optimal action is to manually apply tags. However, I think it’s an overall improvement in quality, since it’s actually a major task to ensure tag-DE matching. We have made ‘fixing’ DEs easier by showing tags in the extraction interface, but the reverse case is not yet addressed, and this would at least ensure that there is an opportunity to ‘fix’ tags.
   Last note– since we already have a workable method (Bulk Actions) for fixing this, I would like to explore using that function more to inform our approach here. Let’s manually back-propagate for now and explore the option of a configurable action for back-propagating all tags. Thanks!

Closing– we overlooked closing this when we launched the feature, which can be found in Bulk Actions on Inspector. We have another request for Back-propogating Interventions, but this is complete!