# Grouping images for PDF file annotation **URL:** \ **Category:** Uncategorized\ **Tags:** usage, image, front-end\ **Created:** [January 15, 2020, 8:39am UTC](https://support.prodi.gy/t/grouping-images-for-pdf-file-annotation/2424 "2020-01-15T08:39:31Z")\ **Posts on this page:** 1\ **Showing post:** 4
**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:** [January 17, 2020, 11:46am UTC](https://support.prodi.gy/t/grouping-images-for-pdf-file-annotation/2424/4 "2020-01-17T11:46:46Z")
> [@nocajar](#): > > and then start prodigy with multiple datasets? Datasets in Prodigy are what annotations are saved to – to load in data, you just stream it in from a directory, a file or a Python script. So you can set up your data like I described above and stream in page by page from multiple PDFs in order, however you like. That's a pretty standard use case. I'm not 100% sure I understand what the problem is or what's still missing. If you stream in your pages in order, the annotator can work on them and if they need to go back to a previous page, they can go back, check something or make a correction, and then move on. > [@nocajar](#): > > Is there a way to keep the history ordering on the left to the ordering of the jsonl stream? and keep more then 10 files in there? The history shows the most recently edited or created annotations, in chronological order. This is typically what's expected from the annotation history – if it wasn't showing you the annotations in "historical" order, it would be pretty confusing. The number of items kept in the history are examples that haven't yet been sent back to the server – so making the history longer would mean delaying sending examples back (see [my comment here](https://support.prodi.gy/t/history-size/2143/2) for details). --- _[View the full topic](https://support.prodi.gy/t/grouping-images-for-pdf-file-annotation/2424)._