Processed information management

This module, which is currently under development, focuses on managing and processing the information obtained from processed sales files. As explained in the Processed Information section , the processing workflow organizes the data into tracks, releases, and artists.

Based on this structured information, it becomes possible to perform advanced operations such as data merging, data separation, and artist mapping, allowing different royalty percentages to be assigned to multiple artists within a release. All of this information is grouped and managed by organization.

This approach ensures that data is carefully collected, cleaned, and analyzed in order to support informed decision-making and strategic planning.

At the moment, this module provides the following three main features:

Artist Merge: The artist information obtained from processed sales files, after passing through the catalog matching module, can be merged by combining the information from two artist entities into a single unified record.
Artist Split: This process performs the opposite action of artist merging by separating the information previously combined between two artist entities.
Artist Mapping: This action is intended for tracks that involve multiple artists, where it is necessary to define the role of each artist within the track. It also allows royalty percentages to be distributed individually among the participating artists.

However, this module also serves as a foundation for implementing many of the processes and practices commonly required in royalty calculation systems. Since the information is already organized by entities at this stage, it opens the possibility for performing royalty calculations based on percentage splits, as well as generating analytical insights for decision-making.

For example, the system can be used to identify the most-streamed and least-streamed releases, artists, and tracks, as well as to perform trend analysis. Additionally, because each entity contains extensive metadata, the platform can also generate analytics based on genres, country-based streams, and many other dimensions.

Merge artist

POST /api/artists/{id}/merge/

This function will serve to merge artists who have a typographical error in their name and therefore the Glider amount and the OAS attachment detect them as a different artist.

        sequenceDiagram
    actor User
    participant System

    User->>System: Log into the system
    User->>System: Go to artists section
    User->>System: Select artist through checkbox
    System->>User: Display "Merge artists" button
    User->>System: Select artists to merge through checkboxes
    User->>System: Click on "Merge artists" button
    System->>System: Add earnings of selected artists to main artist
    System->>System: Add names of selected artists to aliases field of main artist
    System->>System: Relate artist instances to main artist
    System->>System: Delete secondary artists
    System->>User: Show results

Example

curl -X GET "https://oas-beta.ottomate.me/api/artists/{id}/merge/" \
    -H "Authorization: Bearer YOUR_TOKEN" \
    -F "id=1234" \

<<copy-to-clipboard “””text quote “ here”””>>

Request body

Field	Type	Description
id*	integer	Unique ID to identify the artist

* required fields

Response

200 OK — Successful

Field	Type	Description
artist_ids	list	List of new merged artist

401 Unauthorized — Invalid credentials

{"detail": "Authentication credentials were not provided or are invalid."}

Split artist

POST /api/artists/{id}/split/

The split is designed so that artists who have been previously joined can be separated, perhaps due to a finger error or any other situation not contemplated.