use-cases: improve Data Registry case

[Suor]

I took a look at the new Data Registry page. Congrats @jorgeorpinel on compiling it and please don't be angry if you'll get a bit more than you expected :)

Here go some considerations big and small as they occur in the text.

---

Furthermore, the version of the data file imported to B can be an older iteration than what's currently used in A.

• Time is somewhat non-linear when branches are involved, so it might not be correct to talk about "older iteration". Should we just say that B might refer to any version of an artifact from A.

Keeping this in mind, we could build a

could -> can

This way we would have a repository that has all the metadata and change history for the project's data.

• I don't understand this sentence. "we would ... change history", what does it mean? Why do we want to change any history? What does "history of projects data" mean?

Also, why do we push data-registry from the start? Can't one repo simply depend on the other repo? Registry is only one scenario. The majority of advantages listed do not require data registry. I understand that this use case is named "Data Registry", but maybe we can lay some trail to it?

features such as change history

• what does this mean "change history feature"?

Example

• This story about wget and the past brings confusion. May we just state the problem (the current state of it) and solve it? The whole story then starts from the middle, we present commands that do something else then expected and then say about that in some buble. I needed to reread it several times to get what is this about.

A dataset we use for several of our examples and tutorials is one containing

• ... tutorials contains ...

We partitioned the dataset in two ...

• We split the dataset into two ... (See use-cases: improve Data Registry case #795 (comment))

[jorgeorpinel]

Amazing @Suor! I'll start addressing or discussing all this ASAP.

[jorgeorpinel]

could -> can

I would agree if this was a tutorial or get started chapter with reproducible commands but here we are actually talking in a more hypothetical way.

[jorgeorpinel]

"we would ... change history", what does it mean? ... What does "history of projects data" mean?
what does this mean "change history feature"?

I meant the change history. The history of changes i.e. the commits in the Git repo. I can see how this sentence is strange though, I'll rephrase it. Thanks!

[jorgeorpinel]

why do we push data-registry from the start? Can't one repo simply depend on the other repo? Registry is only one scenario. The majority of advantages listed do not require data registry.

Actually, we first mention that "Instead of adding it it to both projects, B can simply import it from A." (implying simple project dependency). Like you noticed, this use case is about data registries so that's why we focus on them.

As for the list of advantages. I had the exact same concern with @shcheklein at first haha. Most of them are not specific to data registries. The reason we have them all listed there though, is that we hope use cases can serve as a bit of marketing, since we imagine they can be the landing pages for some users, linked to the use case directly from a search engine (first web page they ever see in our website). So, we are selling DVC as a whole in here.

[jorgeorpinel]

We split the dataset into two ...

What's wrong with "partitioned"? We then use the word "parts" several times.