# A separate data-registry for each dataset or combine them into one?

**URL:** https://discuss.dvc.org/t/a-separate-data-registry-for-each-dataset-or-combine-them-into-one/1262
**Category:** Questions
**Created:** [July 22, 2022, 5:43pm UTC](https://discuss.dvc.org/t/a-separate-data-registry-for-each-dataset-or-combine-them-into-one/1262 "2022-07-22T17:43:13Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![rmbzmb](https://avatars.discourse-cdn.com/v4/letter/r/ed8c4c/32.png) [@rmbzmb](https://discuss.dvc.org/u/rmbzmb)
#### Post date: [July 22, 2022, 5:43pm UTC](https://discuss.dvc.org/t/a-separate-data-registry-for-each-dataset-or-combine-them-into-one/1262/1 "2022-07-22T17:43:13Z")

</div>

I wonder if it is better to use the same data-registry for two or more separate projects? Or would it better to use a new one for each dataset? For example, what would happen if I have two folders `/data` in two different projects, then check them add them to a single data repository and then try to run `dvc checkout data` ?? Or `dvc pull`.

---

<div class="post-metadata">

### Author: ![dtrifiro](https://avatars.discourse-cdn.com/v4/letter/d/278dde/32.png) [@dtrifiro](https://discuss.dvc.org/u/dtrifiro)
#### Post date: [July 23, 2022, 3:26pm UTC](https://discuss.dvc.org/t/a-separate-data-registry-for-each-dataset-or-combine-them-into-one/1262/2 "2022-07-23T15:26:13Z")

</div>

Hi,

can elaborate on your usecase?

I guess a typical setup is to have all datasets in the same dvc repository and then use it in other projects using `dvc import` (docs: [import](https://dvc.org/doc/command-reference/import))
