Dataset should have a `.name` field
COLLABORATOR
Hi! You can already use `dset.builder_name` and `dset.config_name` for that purpose. And when it comes to versioning, it's better to use `dset._fingerprint` than the `version` attribute as the former represents a deterministic hash that encodes all the mutable ops executed on a dataset, and the latter stays the same unless it's manually updated after each op.
2022-05-26T13:10:01Z
https://github.com/huggingface/datasets/issues/4404#issuecomment-1138559564
https://api.github.com/repos/huggingface/datasets/issues/4404
IC_kwDODunzps5D3QpM
https://api.github.com/repos/huggingface/datasets/issues/comments/1138559564/reactions
2022-05-26T13:10:01Z
https://api.github.com/repos/huggingface/datasets/issues/comments/1138559564
https://avatars.githubusercontent.com/u/47462742?v=4
https://api.github.com/users/mariosasko/events{/privacy}
https://api.github.com/users/mariosasko/followers
https://api.github.com/users/mariosasko/following{/other_user}
https://api.github.com/users/mariosasko/gists{/gist_id}
https://github.com/mariosasko
mariosasko
MDQ6VXNlcjQ3NDYyNzQy
https://api.github.com/users/mariosasko/orgs
https://api.github.com/users/mariosasko/received_events
https://api.github.com/users/mariosasko/repos
https://api.github.com/users/mariosasko/starred{/owner}{/repo}
https://api.github.com/users/mariosasko/subscriptions
User
https://api.github.com/users/mariosasko
public
NONE
@mariosasko  Can we make ._fingerprint not private? seems a critical component for tracking how a model was generated to ensure reproducibility.
2022-09-13T15:09:30Z
https://github.com/huggingface/datasets/issues/4404#issuecomment-1245555268
https://api.github.com/repos/huggingface/datasets/issues/4404
IC_kwDODunzps5KPapE
https://api.github.com/repos/huggingface/datasets/issues/comments/1245555268/reactions
2022-09-13T15:09:30Z
https://api.github.com/repos/huggingface/datasets/issues/comments/1245555268
https://avatars.githubusercontent.com/u/36440?v=4
https://api.github.com/users/f4hy/events{/privacy}
https://api.github.com/users/f4hy/followers
https://api.github.com/users/f4hy/following{/other_user}
https://api.github.com/users/f4hy/gists{/gist_id}
https://github.com/f4hy
f4hy
MDQ6VXNlcjM2NDQw
https://api.github.com/users/f4hy/orgs
https://api.github.com/users/f4hy/received_events
https://api.github.com/users/f4hy/repos
https://api.github.com/users/f4hy/starred{/owner}{/repo}
https://api.github.com/users/f4hy/subscriptions
User
https://api.github.com/users/f4hy
public
**Is your feature request related to a problem? Please describe.**
If building pipelines that can evaluate on more than one dataset, it would be nice to be able to log results of things like `Evaluating on {dataset.name}` or `results for {dataset.name} are: {results}`

Without some way of concisely identifying a dataset from the dataset object, tools which might run on more than one dataset must be passed the dataset object _and_ the name/id of the dataset being used. 

**Describe the solution you'd like**
The DatasetInfo class should have a `name` field which is the name of a dataset. then for a given dataset if it evolves in time the `version` can be updated but its different versions of the same dataset with a unique `name`. The name could then all be accessed by `dataset.name`

**Describe alternatives you've considered**
For my own purposes I am considering making `NamedDataset[Dataset]` where the subclass just has a .name field. 

**Additional context**
My guess is that most usecases are not working with more than one dataset in a given pipeline so a name is not really needed. This has surprised me though as one of the advantages of a standard dataset interface is to be able to build pipelines which can be passed in a dataset and separate responsibilities of the dataset loading from the train or eval pipeline.
