feat: updated readme
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful

This commit is contained in:
Hazel 2024-05-07 10:37:02 +02:00
parent 3951394ede
commit 8abb89ea48

View File

@ -2,7 +2,7 @@
[![Woodpecker CI Status](https://ci.elara.ws/api/badges/59/status.svg)](https://ci.elara.ws/repos/59) [![Woodpecker CI Status](https://ci.elara.ws/api/badges/59/status.svg)](https://ci.elara.ws/repos/59)
<img src="assets/logo.svg" width=300 alt="music kraken logo"/> <img src="https://gitea.elara.ws/music-kraken/music-kraken-core/media/branch/experimental/assets/logo.svg" width=300 alt="music kraken logo"/>
- [Installation](#installation) - [Installation](#installation)
- [Quick-Guide](#quick-guide) - [Quick-Guide](#quick-guide)
@ -16,10 +16,10 @@
You can find and get this project from either [PyPI](https://pypi.org/project/music-kraken/) as a Python-Package, You can find and get this project from either [PyPI](https://pypi.org/project/music-kraken/) as a Python-Package,
or simply the source code from [Gitea](https://gitea.elara.ws/music-kraken/music-kraken-core). ** or simply the source code from [Gitea](https://gitea.elara.ws/music-kraken/music-kraken-core). **
> **NOTES** **NOTES**
>
> - Even though everything **SHOULD** work cross-platform, I have only tested it on Ubuntu. - Even though everything **SHOULD** work cross-platform, I have only tested it on Ubuntu.
If you enjoy this project, feel free to give it a star on GitHub. - If you enjoy this project, feel free to give it a star on GitHub.
### From source ### From source
@ -110,41 +110,6 @@ obj -> pg: add more detailed data from according page.
obj -> pg: if available download audio to target. obj -> pg: if available download audio to target.
``` ```
## Data Model
Music metadata can be easily abstracted to a few main Entities with some relations between them. This enables the easy scraping and aggregation of the correct metadata for each Song. Those Entities are `Song`, `Album`, `Artist` and `Label`.
<details>
This is convenient because then I can just use for example one Artist, which adds its metadata shared and consistently to each of its song. This exactly was the reason why piracy was such a mess in the past. Metadata has a lot of redundancy, but the relational databases of streaming services don't. THIS is the main reason for this program, and in my opinion also the reason for the widespread adoption of streaming services.
</details>
```mermaid
---
title: music kraken - data model
---
erDiagram
Song {}
Album {}
Artist {}
Label {}
Song ||--o{ Album : album_collection
Song ||--o{ Artist : main_artist_collection
Song ||--o{ Artist : feature_artist_collection
Album ||--o{ Song : song_collection
Album ||--o{ Artist : artist_collection
Album ||--o{ Label : label_collection
Artist ||--o{ Song : feature_song_collection
Artist ||--o{ Album : main_album_collection
Artist ||--o{ Label : label_collection
Label ||--o{ Album : album_collection
Label ||--o{ Artist : current_artist_collection
```
[i10]: https://github.com/HeIIow2/music-downloader/issues/10 [i10]: https://github.com/HeIIow2/music-downloader/issues/10
[i2]: https://github.com/HeIIow2/music-downloader/issues/2 [i2]: https://github.com/HeIIow2/music-downloader/issues/2