# Review annotations error in prodigy V1.13.1

**URL:** <https://support.prodi.gy/t/review-annotations-error-in-prodigy-v1-13-1/6796>\
**Category:** Uncategorized\
**Tags:** review\
**Created:** [September 18, 2023, 11:29am UTC](https://support.prodi.gy/t/review-annotations-error-in-prodigy-v1-13-1/6796 "2023-09-18T11:29:33Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![foscraft](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/foscraft/32/4116_2.png) [@foscraft](https://support.prodi.gy/u/foscraft)\
**Post date:** [September 18, 2023, 11:29am UTC](https://support.prodi.gy/t/review-annotations-error-in-prodigy-v1-13-1/6796/1 "2023-09-18T11:29:33Z")

</div>

Am getting the following error when running the review property on prodigy.  
command:

```python
prodigy review newset myset --label OMS,OOT,METHODS

```

error:

```python
✘ Reviewing 'blocks' annotations isn't supported yet
You can vote for this feature on the forum: https://support.prodi.gy

```

---

<div class="post-metadata">

**Author:** ![koaning](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/koaning/32/230_2.png) [@koaning](https://support.prodi.gy/u/koaning)\
**Post date:** [September 19, 2023, 8:48am UTC](https://support.prodi.gy/t/review-annotations-error-in-prodigy-v1-13-1/6796/2 "2023-09-19T08:48:02Z")

</div>

Thanks for reaching out! The error is correct, the `review` recipe currently does not properly support the blocks view.

I would like to understand your use-case more though. Did you generate this dataset with a custom recipe or a built-in one? Also, do you have a screenshot of the interface you'd like to use?

---

<div class="post-metadata">

**Author:** ![foscraft](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/foscraft/32/4116_2.png) [@foscraft](https://support.prodi.gy/u/foscraft)\
**Post date:** [September 19, 2023, 8:51am UTC](https://support.prodi.gy/t/review-annotations-error-in-prodigy-v1-13-1/6796/3 "2023-09-19T08:51:07Z")

</div>

I am using the `python -m prodigy ner.llm.correct nannotated-text config.cfg yourdata.csv` to generate the dataset first, as demonstrated in your spacy llms video.

Once I hace the `annotated_text` now am trying to review and see how it performed with the prodigy interface.

---

<div class="post-metadata">

**Author:** ![koaning](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/koaning/32/230_2.png) [@koaning](https://support.prodi.gy/u/koaning)\
**Post date:** [September 19, 2023, 9:04am UTC](https://support.prodi.gy/t/review-annotations-error-in-prodigy-v1-13-1/6796/4 "2023-09-19T09:04:59Z")

</div>

Ah! That's indeed using a `blocks` interface under the hood. But it's also something that should work out of the box because it is an internal recipe. This is something that I'll explore today!

---

<div class="post-metadata">

**Author:** ![koaning](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/koaning/32/230_2.png) [@koaning](https://support.prodi.gy/u/koaning)\
**Post date:** [September 19, 2023, 9:54am UTC](https://support.prodi.gy/t/review-annotations-error-in-prodigy-v1-13-1/6796/5 "2023-09-19T09:54:26Z")

</div>

I investigated the issue and I think I have a proposal for a patch ready. We still won't be able to render everything that a blocks UI might generate, but we may want to allow a user like yourself to be able to pass `--view-id ner_manual` to the review recipe to make it clear that you're only interested in re-using that UI.

It's going through review now and I'll keep you posted on any changes.

Again, thanks for reporting, and sorry for the headache! I'll try to get this patched ASAP.

---

<div class="post-metadata">

**Author:** ![foscraft](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/foscraft/32/4116_2.png) [@foscraft](https://support.prodi.gy/u/foscraft)\
**Post date:** [September 19, 2023, 10:25am UTC](https://support.prodi.gy/t/review-annotations-error-in-prodigy-v1-13-1/6796/6 "2023-09-19T10:25:47Z")

</div>

Thank you, will be waiting on the developments.

---

<div class="post-metadata">

**Author:** ![koaning](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/koaning/32/230_2.png) [@koaning](https://support.prodi.gy/u/koaning)\
**Post date:** [September 20, 2023, 6:26pm UTC](https://support.prodi.gy/t/review-annotations-error-in-prodigy-v1-13-1/6796/7 "2023-09-20T18:26:09Z")

</div>

Reporting back. I think you should now be able to upgrade to version 1.13.3 that comes with a patch for this issue. You will need to pass `--view-id ner_manual` to the `review` call, but that should be it!

Let me know if there's still issues with this!

---

<div class="post-metadata">

**Author:** ![foscraft](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/foscraft/32/4116_2.png) [@foscraft](https://support.prodi.gy/u/foscraft)\
**Post date:** [September 21, 2023, 6:27am UTC](https://support.prodi.gy/t/review-annotations-error-in-prodigy-v1-13-1/6796/8 "2023-09-21T06:27:43Z")

</div>

Thank you. Will get back once I try it later today.

---

<div class="post-metadata">

**Author:** ![foscraft](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/foscraft/32/4116_2.png) [@foscraft](https://support.prodi.gy/u/foscraft)\
**Post date:** [September 22, 2023, 6:31am UTC](https://support.prodi.gy/t/review-annotations-error-in-prodigy-v1-13-1/6796/9 "2023-09-22T06:31:54Z")

</div>

Worked okay. Many thanks Vincent!

---

<div class="post-metadata">

**Author:** ![dansowter](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/dansowter/32/914_2.png) [@dansowter](https://support.prodi.gy/u/dansowter)\
**Post date:** [October 6, 2023, 2:40am UTC](https://support.prodi.gy/t/review-annotations-error-in-prodigy-v1-13-1/6796/10 "2023-10-06T02:40:11Z")

</div>

Thanks for this - ran into the same issue after annotating with custom recipes for textcat, based on the new ones for models-as-annotators and llm.correct (sorry, forget exact names). FYI there's another related issue with this workflow, where a task might allow multiple classes, but then the review UI is unaware that multiple were allowed. The workaround of putting "choice\_style": "multiple" into prodigy.json overcomes this issue, but it's likely to trip up lots of folks - and I don't believe there's currently a way to pass this config into a recipe without using the config file.

---

<div class="post-metadata">

**Author:** ![koaning](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/koaning/32/230_2.png) [@koaning](https://support.prodi.gy/u/koaning)\
**Post date:** [October 6, 2023, 11:42am UTC](https://support.prodi.gy/t/review-annotations-error-in-prodigy-v1-13-1/6796/11 "2023-10-06T11:42:20Z")

</div>

With regards to `choice_style`: that's correct. This information is stored in the `config.json` file and isn't stored on the annotated example in the database. So the `review` recipe needs this information in order to work.

Just to check @dansowter you're not stuck now? If you are I'll gladly see if I can help.

---

<div class="post-metadata">

**Author:** ![dansowter](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/dansowter/32/914_2.png) [@dansowter](https://support.prodi.gy/u/dansowter)\
**Post date:** [October 10, 2023, 2:56am UTC](https://support.prodi.gy/t/review-annotations-error-in-prodigy-v1-13-1/6796/12 "2023-10-10T02:56:11Z")

</div>

That's very kind of you. No, I'm not stuck, but I appreciate the offer.
