| | 1 | = UseCase012 - Associating Artist to Release |
| | 2 | |
| | 3 | **Initiating actor:** Logged-In Admin |
| | 4 | |
| | 5 | {{{#!div style="text-align: justify; width: 100%;" |
| | 6 | The goal of this use case is to link a musical release to its primary creator/s within the database. By establishing this relationship, the administrator ensures that the album or single is correctly attributed to the right artist/s, allowing the system to display the release on the artist's profile and enabling users to find the music through artist-based searches. |
| | 7 | }}} |
| | 8 | |
| | 9 | == Scenario |
| | 10 | |
| | 11 | {{{#!div style="text-align: justify; width: 100%;" |
| | 12 | |
| | 13 | 1. Admin selects a specific {{{Release}}} that currently lacks an assigned creator or requires a metadata update. |
| | 14 | |
| | 15 | 2. Admin searches for and selects the appropriate {{{Artist}}} from the existing database records. |
| | 16 | |
| | 17 | 3. System verifies the unique identifiers for both the {{{release_id}}} and the {{{artist_id}}}. |
| | 18 | |
| | 19 | 4. System creates or updates the "has" relationship, effectively linking the {{{Artist}}} to the {{{Release}}} in the database. |
| | 20 | |
| | 21 | 5. System validates the connection to ensure the release now appears under the artist's discography. |
| | 22 | |
| | 23 | 6. System confirms the successful association to the admin and updates the public-facing release page to display the {{{artist_name}}}. |
| | 24 | }}} |