Store additional beatmap data #582
Labels
area:beatmaps
database:schema-change
Items that contain or propose schema changes to the database
epic
Feature that requires significant effort to implement
project:API
Items related to the API project
project:Database
Items related to the Database project
project:DataWorkerService
Items related to the DataWorkerService project
project:OsuApiClient
Items related to the OsuApiClient project
proposal
type:feature
Currently we do not store the osu! id of the beatmap set for each beatmap, which is relevant for certain use cases such as accessing the beatmap's image assets. In addition to this, the osu! API returns different objects for each beatmap when requesting
/beatmaps/{id}
and/beatmapsets/{id}
. When requesting/beatmapsets/{id}
, the API will include the proper user data for all collab members (see below). When a single beatmap is requested from/beatmaps/{id}
, the owner will always be set to the user who uploaded the beatmap set. Finally, we should support fetching and storing beatmap attributes (namely SR, as that cannot be calculated with a formula without having the beatmap file) so we can display that information properly on the website.Tasks
Beatmap
relationships #586OsuApiClient
OsuApiClient
classDataWorkerService.Services.OsuApiDataParserService
to handle parsing the new data structureosu! API example responses
Pastebin below contains example osu! API responses for each of the possible variations of the data concerned in this proposal
https://pastebin.com/bkC1ytwr
Entity Structures
The text was updated successfully, but these errors were encountered: