Highlighting PICO terms?#409

This might be a really dumb question, but is Nested Knowledge supposed to automatically highlight the PICO terms through AI? I don’t see anything highlighted.

Tiffany - this is not a dumb question! We have been struggling to “backfill” PICOs recently. Unfortunately, the models we use to highlight PICOs are slow (maybe .1-.5 seconds per abstract), so we opt to compute PICOs after search import is complete, not part of search import itself. Hence, “backfill”. It’s our intent that backfill occurs within 30 minues of import.

That said, I noticed the backfill has been failing with some frequency (upwards of 50% of abstracts, depending on time of day). We’re looking into it, thanks for the heads up!

Fixed in 1.38.1!

Great! I’ll be using that this week for the motocross project.

This is a slightly different but probably related question, I copied in an abstract that was not automatically imported and it’s not PICO highlighted, should I just wait and expect it to be processed, or is there a difference between abstracts imported in a search and abstracts that are manually entered? Thanks!

Now that is something I hadn’t considered in a while. No, we don’t update PICOs when you edit the abstract (they currently are all generated once, when you import the record originally).

It would probably make sense to re-run RoboPICO when you hit that save button on Edit Bibliographic data!

Thanks Karl! Is that something I can trigger in the nest? Normally I wouldn’t have even noticed that the highlighting was missing, but our client finds it useful to see when they’re viewing studies in synthesis.

There is not a way through the UI currently (is resource intensive & could be abused by unknowing users). We do have a backfill I can trigger - email me the nest you’re working on?

Thanks Karl! I sent you the nest and the specific study. You should have access but let me know if you need anything else from me!

Great, we’ll address the specific project shortly, and we’ll add RoboPICO on abstract addition as a feature in our next release. I’ll ping here when both of those happen!

Awesome, thanks!

The specific study you wanted is complete - let me know if there are more, and you can expect this to be automatically triggered in the next 1-2 releases (we’ve already completed the code as part of another feature that is still in development).

Perfect, thanks! I don’t think there are others but I’ll email you if any come up.

The “permanent” fix was made in release 1.57.0. Please note that PICOs are updated asynchronously, so they won’t appear immediately after you hit save; however, they should typically be updated quickly, so refreshing 1-2 seconds after should get the job done :) Thanks for bringing this up!

Awesome, thanks Karl!