# How do we inspect dataset sessions?

**URL:** <https://support.prodi.gy/t/how-do-we-inspect-dataset-sessions/736>\
**Category:** Uncategorized\
**Tags:** usage, database, solved\
**Created:** [August 9, 2018, 2:28pm UTC](https://support.prodi.gy/t/how-do-we-inspect-dataset-sessions/736 "2018-08-09T14:28:33Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [August 9, 2018, 2:35pm UTC](https://support.prodi.gy/t/how-do-we-inspect-dataset-sessions/736/2 "2018-08-09T14:35:27Z")

</div>

A session is really just a “special” dataset and its name is the session ID – so you can use Prodigy’s regular database commands to export or output the annotations. For example:

```bash
prodigy db-out SESSION_ID | less
prodigy db-out SESSION_ID > session.jsonl

```

You can also use the print recipes to get nicely formatted command line output:

```bash
prodigy ner.print-dataset SESSION_ID | less -R
prodigy textcat.print-dataset SESSION_ID | less -R

```

(We’re hoping to improve some of the dataset and session handling as part of the [corpus management update](https://support.prodi.gy/t/prodigy-roadmap/32). I’ve also been thinking about writing a little recipe that makes it easier to navigate the individual sessions. They’re all timestamped, so it won’t be difficult to group them together by year, month, week, day etc.)

---

_[View the full topic](https://support.prodi.gy/t/how-do-we-inspect-dataset-sessions/736)._