Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/dataobservatory-eu/open-music-europe-user-stories
https://github.com/dataobservatory-eu/open-music-europe-user-stories
Last synced: 10 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/dataobservatory-eu/open-music-europe-user-stories
- Owner: dataobservatory-eu
- Created: 2023-11-20T10:39:22.000Z (about 1 year ago)
- Default Branch: main
- Last Pushed: 2023-12-06T12:44:00.000Z (about 1 year ago)
- Last Synced: 2024-12-08T04:42:52.725Z (15 days ago)
- Language: JavaScript
- Size: 430 KB
- Stars: 0
- Watchers: 1
- Forks: 2
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Open Music Europe User Stories
[](https://dataobservatory.eu/)
[](https://github.com/dataobservatory-eu/)
[](https://iotables.dataobservatory.eu)
[](https://iotables.dataobservatory.eu)
[](https://regions.dataobservatory.eu)
[](https://dataset.dataobservatory.eu)
[](https://www.rcharlie.com/spotifyr)
[](https://statcodelists.dataobservatory.eu)
[](https://dataobservatory.eu/)
## Welcome 👋
🙋♀️ Creating an ecosystem of open data and open knowledge sharing in R hugo, and open science repositories.
🌈 Contribution guidelines - you must abide by the [Contributor Covenant](https://www.contributor-covenant.org/version/2/1/code_of_conduct/) Code of Conduct.
## Metadata stories
Because `Open Music Europe` and the Digital Music Observatory will use the [Polifonia Ontology Network](https://polifonia-project.github.io/ontology-network/) to describe data and the meaning (semantics) of music data, we harmonise our user stories with Polifonia's. However, Polifonia's stories are aimed to design a knowledge model and formal ontologies, not data management or collection applications.
Polifonia stories: [github.com/polifonia-project/stories](https://github.com/polifonia-project/stories)
## Open Music Data stories
Our stories are aiming to support our internal and external music data users. We are not fully aligning with the Polifonia story outlines, because we mainly develop R code, or software that can place R code in applications (in Shiny or other.)
- Rebeca, intermediate R user, able to use the _eurostat_ package and _tidyverse_, wants to become FAIR compliant: [eurostat-user1](https://music.dataobservatory.eu/documents/open_music_europe/dataset-development/stories/eurostat-user1.html) -- source [stories/eurostat-user1.qmd](https://github.com/dataobservatory-eu/dataset-development/stories/)
- Ahmed, advanced R user, research data engineer wants to retain the data, add his new variables, and place them into a Data Catalogue:
[eurostat-user2](https://music.dataobservatory.eu/documents/open_music_europe/dataset-development/stories/eurostat-user2.html) -- source [stories/eurostat-user2.qmd](https://github.com/dataobservatory-eu/dataset-development/stories/)
- Michal, who have not used yet R, a junior assistant at a policy unit and does the work nobody wants to do. Recently, he had to reconcile dozens of PDF variable descriptions with poorly formatted CSV files and create clean Excel tables. Michal wanted to know if an R script could do this:
[eurostat-user2](https://music.dataobservatory.eu/documents/open_music_europe/dataset-development/stories/michal.html) -- source [stories/michal.qmd](https://github.com/dataobservatory-eu/dataset-development/stories/)
- Ivana is the chief analyst of a cultural policy unit. She uses the integrated microdata files created with retroharmonize to make utilisation and budget forecasts for concert halls based on panel data. She uses Excel, where time series projections could be more convenient to assemble. [ivana](https://music.dataobservatory.eu/documents/open_music_europe/dataset-development/stories/ivana.html) -- source [stories/ivana.qmd](https://github.com/dataobservatory-eu/dataset-development/stories/)
- Natália is a 45-years-old engineer working in a collective rights management organisation. She has extensive experience working with relational database management systems, but only vague familiarity with knowledge graphs. [natalia](https://music.dataobservatory.eu/documents/open_music_europe/dataset-development/stories/natalia.html) -- source [stories/natalia.qmd](https://github.com/dataobservatory-eu/dataset-development/stories/)
- Persona: Jana, a 42-years-old librarian working in a music information center. She is experienced in library metadata, such as Dublin Core, and working with relational database management systems, but not via queries or scripts, more using a graphical interface.
[jana](https://music.dataobservatory.eu/documents/open_music_europe/dataset-development/stories/jana.html) -- source [stories/jana.qmd](https://github.com/dataobservatory-eu/dataset-development/stories/)
- Persona: Georg, 40-year-old music curator, who mainly works with playlists on his computer. As a seasoned DJ, he is able to find music for every occasion, but due to GDPR constraints, making his playlist location-aware is becoming more and more difficult. [georg](https://music.dataobservatory.eu/documents/open_music_europe/dataset-development/stories/georg.html) -- source [stories/georg.qmd](https://github.com/dataobservatory-eu/dataset-development/stories/)
- Persona: Max, a 45-year old music curator at an In-Store Music company, who is a DJ in his spare time. Max is responsible for acquiring the music from different sources such as webshops or from record labels directly. [georg](https://music.dataobservatory.eu/documents/open_music_europe/dataset-development/stories/max.html) -- source [stories/max.qmd](https://github.com/dataobservatory-eu/dataset-development/stories/)
- Further developing stories in Google Docs: if needed, they should be made re-written in Quarto [here](https://docs.google.com/document/d/185IeCTRnjVv4lY3kYJQKJ1kD93V3ubfFwtNH3wWv_ak/) and [here](https://docs.google.com/document/d/15EC7pb2hVE9sTNwd4cSokgtKZxIvan6Jlh1PCJZAoVo/).