The dataset viewer is not available for this subset.
Exception: SplitsNotFoundError
Message: The split names could not be parsed from the dataset config.
Traceback: Traceback (most recent call last):
File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 286, in get_dataset_config_info
for split_generator in builder._split_generators(
~~~~~~~~~~~~~~~~~~~~~~~~~^
StreamingDownloadManager(base_path=builder.base_path, download_config=download_config)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/webdataset/webdataset.py", line 81, in _split_generators
first_examples = list(islice(pipeline, self.NUM_EXAMPLES_FOR_FEATURES_INFERENCE))
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/webdataset/webdataset.py", line 32, in _get_pipeline_from_tar
fs: fsspec.AbstractFileSystem = fsspec.filesystem("memory")
~~~~~~~~~~~~~~~~~^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/fsspec/registry.py", line 302, in filesystem
cls = get_filesystem_class(protocol)
File "/usr/local/lib/python3.14/site-packages/fsspec/registry.py", line 239, in get_filesystem_class
raise ValueError(f"Protocol not known: {protocol}")
ValueError: Protocol not known: memory
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/src/services/worker/src/worker/job_runners/config/split_names.py", line 66, in compute_split_names_from_streaming_response
for split in get_dataset_split_names(
~~~~~~~~~~~~~~~~~~~~~~~^
path=dataset,
^^^^^^^^^^^^^
config_name=config,
^^^^^^^^^^^^^^^^^^^
token=hf_token,
^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 340, in get_dataset_split_names
info = get_dataset_config_info(
path,
...<6 lines>...
**config_kwargs,
)
File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 291, in get_dataset_config_info
raise SplitsNotFoundError("The split names could not be parsed from the dataset config.") from err
datasets.inspect.SplitsNotFoundError: The split names could not be parsed from the dataset config.Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.
Dataset Card for Lastfm-VADS
This dataset contains Valence, Arousal, Dominance and Sentiment Ratio values for over 800K tracks, with their respective artist, album and ranked tags.
Dataset Details
This dataset was curated to be used in a Bachelor Thesis, consisting in the integration of sentiment features into music recommendation along with inherent track features, such as artists, albums, interaction timestamps and (automatically assigned) ratings.
Track data was gathered with last.fm's API, and sentiment features were extracted from tags, with a sentiment analyzer that used generalized Wikipedia definitions.
Dataset Description
- Curated by: Javier Wang
- Language(s) (NLP): English
Dataset Sources
- Repository: https://huggingface.co/datasets/Acervans/Lastfm-VADS
- Demo: https://github.com/Acervans/lastfm_RS
Uses
Features may be integrated into any ML model, specifically RecSys models, to evaluate the model performance considering the included types (track-inherent or sentiment). These files are structured to be used directly within the RecBole framework, specifically for context-aware models if all features need be integrated.
Dataset Structure
This dataset has three atomic files, all of which use tabs as field separators:
lastfm_recbole.inter- Contains user-track interactions, organized in:- user_id: User ID.
- track_id: Track ID.
- rating: Rating assigned to the track based on the type of interaction of the user, keeping the highest if more than one.
- timestamp: Timestamp of the interaction.
lasftm_recbole.item- Contains item features, organized in:- track_id: Track ID.
- tags: Tags as sequential token, repeated by user assignment count, and separated by a space.
- artist_id: Artist ID.
- album_id: Album ID.
- v: Valence score for the track.
- a: Arousal score for the track.
- d: Dominance score for the track.
- stsc: Sentiment Ratio for the track.
lastfm_recbole.user- Contains users' IDs. This file was kept to have the same IDs assigned during processing.
File lastfm_data.tar.gz contains the raw files scraped with last.fm's API, distributed in several JSON and DAT files. Please check the Readme.txt inside for the structure of these files.
Source Data
The source data used for this dataset is Last.fm's API. The text source used to analyze sentiment (tag definitions) was obtained from Wikipedia's API.
Data Collection and Processing
This dataset was obtained through a simple web scraper. It retrieves the top 50 chart tags using Last.fm's API, representing the most listened tags at the time. For each tag, we obtained the top unique artists associated with them and the top-30 unique listeners. Then, we used the API to gather data from the top listeners, acquiring their top 20 tracks, recent tracks, and loved tracks, each with the corresponding timestamp, and artist and album information. Additionally, we collected the top 10 artists and albums for each listener. Finally, we fetched the top 10 tags assigned by users to each unique track, artist, and album, which were associated definitions according to the summaries retrieved from Wikipedia's API.
For processing, ratings in the .inter file were assigned based on listen count, type of interaction (love, recent, top) and ranking. All tags in the .item file were preprocessed to reduce ambiguities, removing spaces and dashes and converting to lowercase. These tags were then repeated based on user assignment count, to increase the weight given for each track. Finally, unique IDs were assigned for each track, user and album comply with Data Protection Principles.
- Downloads last month
- 499