# Annotated jsonl as source

**URL:** <https://support.prodi.gy/t/annotated-jsonl-as-source/819>\
**Category:** Uncategorized\
**Tags:** usage, ner, solved\
**Created:** [September 17, 2018, 3:12pm UTC](https://support.prodi.gy/t/annotated-jsonl-as-source/819 "2018-09-17T15:12:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cristiano74](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/cristiano74/32/439_2.png) [@Cristiano74](https://support.prodi.gy/u/Cristiano74)\
**Post date:** [September 17, 2018, 3:12pm UTC](https://support.prodi.gy/t/annotated-jsonl-as-source/819/1 "2018-09-17T15:12:22Z")

</div>

Dear support,  
I’m trying to use the annoted jsonl as source for manuale NER, but I’m not sure the follow the right flow. For example I used:

```
prodigy dataset my_it9
prodigy ner.manual my_it9 it_core_news_sm covered_warrant.txt -l FIN
prodigy db-out my_it9 export2 -a accept

```

Then I review the annotations and change them partially:

`prodigy ner.manual my_it9 it_core_news_sm ./export2/my_it9.jsonl -l FIN`

Now I want to review again the annotations:

```
prodigy db-out my_it9 export2 -a accept
prodigy ner.manual my_it9 it_core_news_sm ./export2/my_it9.jsonl -l FIN

```

But at this step I’m not able to re-use the annotated jsonl as source, I mean I don’t see the last marked entities.

Maybe this flow is wrong?

Thanks in advance for any suggestions.

C.

---

<div class="post-metadata">

**Author:** ![Cristiano74](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/cristiano74/32/439_2.png) [@Cristiano74](https://support.prodi.gy/u/Cristiano74)\
**Post date:** [September 17, 2018, 4:11pm UTC](https://support.prodi.gy/t/annotated-jsonl-as-source/819/2 "2018-09-17T16:11:50Z")

</div>

I’ve seen a solution here [overwriting annotations](https://support.prodi.gy/t/overwriting-annotations/563/2) but I’m wondering if there is any good flow to accomplish this task as well?

Thanks

---

<div class="post-metadata">

**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\
**Post date:** [September 17, 2018, 7:19pm UTC](https://support.prodi.gy/t/annotated-jsonl-as-source/819/3 "2018-09-17T19:19:22Z")

</div>

Yes, I think what's going on here is that you're adding your new, reviewed annotations to the same dataset. So your dataset now contains the old annotations, as well as the new ones. By default, Prodigy is designed to always keep a record of each individual annotation decision so you can always reproduce it – that’s also why it doesn’t just silently overwrite existing records in your dataset.

You might find this thread interesting, which discusses a very similar workflow. I've also posted a more advanced recipe to automate the reviewing process and take random samples.

> [@Edit Saved NER Manual Annotations](https://support.prodi.gy/t/edit-saved-ner-manual-annotations/813):
>
> Hi there! I found this post here, which would be similar to what I’m facing, but my situation is not the same: I was using ner.manual annotating from a stream from stdin, but I can’t seem to understand how it would be possible for me to edit saved annotations instead of re-annotating them. If I dump the annotations to a jsonl file using db-out, to try to edit them, prodigy ends up creating a new record in the dataset with the updated annotations instead of updating the existing ones. Why is…