Dataset should have a `.name` field
{'login': 'f4hy', 'id': 36440, 'node_id': 'MDQ6VXNlcjM2NDQw', 'avatar_url': 'https://avatars.githubusercontent.com/u/36440?v=4', 'gravatar_id': '', 'url': 'https://api.github.com/users/f4hy', 'html_url': 'https://github.com/f4hy', 'followers_url': 'https://api.github.com/users/f4hy/followers', 'following_url': 'https://api.github.com/users/f4hy/following{/other_user}', 'gists_url': 'https://api.github.com/users/f4hy/gists{/gist_id}', 'starred_url': 'https://api.github.com/users/f4hy/starred{/owner}{/repo}', 'subscriptions_url': 'https://api.github.com/users/f4hy/subscriptions', 'organizations_url': 'https://api.github.com/users/f4hy/orgs', 'repos_url': 'https://api.github.com/users/f4hy/repos', 'events_url': 'https://api.github.com/users/f4hy/events{/privacy}', 'received_events_url': 'https://api.github.com/users/f4hy/received_events', 'type': 'User', 'site_admin': False}
[{'id': 1935892871, 'node_id': 'MDU6TGFiZWwxOTM1ODkyODcx', 'url': 'https://api.github.com/repos/huggingface/datasets/labels/enhancement', 'name': 'enhancement', 'color': 'a2eeef', 'default': True, 'description': 'New feature or request'}]
[]
["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."]
**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.

{'url': 'https://api.github.com/repos/huggingface/datasets/issues/4404/reactions', 'total_count': 0, '+1': 0, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0}