dashboard issueshttps://gitlab.servus.at/aura/dashboard/-/issues2024-03-29T10:23:04+01:00https://gitlab.servus.at/aura/dashboard/-/issues/241Show - General settings: improve layout, grouping, presentation of form fields2024-03-29T10:23:04+01:00David TrattnigShow - General settings: improve layout, grouping, presentation of form fieldso94 Feedback:
> Ev. könnten die Felder in ein paar Blöcke strukturiert werden, im Moment schwimmen sie je nach Länge der Feldbeschriftung und durch die unterschiedliche Größe je nach Inhalt recht unruhig und unübersichtlich.
Restructur...o94 Feedback:
> Ev. könnten die Felder in ein paar Blöcke strukturiert werden, im Moment schwimmen sie je nach Länge der Feldbeschriftung und durch die unterschiedliche Größe je nach Inhalt recht unruhig und unübersichtlich.
Restructure form to have more logical and visually balanced blocks.1.0-alpha3 — Playful Platypus ▶️🦦Konrad MohrfeldtKonrad Mohrfeldthttps://gitlab.servus.at/aura/dashboard/-/issues/65Provide selection for "Default Schedule Playlist" playlist2024-03-29T10:21:41+01:00David TrattnigProvide selection for "Default Schedule Playlist" playlistDiscussion needed where to put it.
This was previously known as "Schedule Fallback Playlist".Discussion needed where to put it.
This was previously known as "Schedule Fallback Playlist".Aura 0.9Richard BlechingerRichard Blechingerhttps://gitlab.servus.at/aura/dashboard/-/issues/266introduce comma separation for keyword entry in episode editor page2024-03-29T10:20:22+01:00Margarethe Maierhofer-Lischkaintroduce comma separation for keyword entry in episode editor pagewhen entering tags / keywords in the episode editor page, users have to push ’enter’ after each entry. entering several keywords with a comma in between saves the whole string (see screenshot). as a UX improvement, the dashboard could of...when entering tags / keywords in the episode editor page, users have to push ’enter’ after each entry. entering several keywords with a comma in between saves the whole string (see screenshot). as a UX improvement, the dashboard could offer comma separation for the keyword entry.
![Screenshot_from_2024-02-16_15-31-41](/uploads/2f421ee2e0068a5b82ddad33ce61addb/Screenshot_from_2024-02-16_15-31-41.png)https://gitlab.servus.at/aura/dashboard/-/issues/216State of new media management2024-03-21T18:19:33+01:00Konrad MohrfeldtState of new media managementThe dashboard main branch (deployed on dashboard.aura.radio) now contains the new playlist (media source) and file management feature.
The old media page is still there. I’ve refrained from removing it, so that it can serve as a referen...The dashboard main branch (deployed on dashboard.aura.radio) now contains the new playlist (media source) and file management feature.
The old media page is still there. I’ve refrained from removing it, so that it can serve as a reference to compare the behaviors of the existing and the new solution. If everything works out, I’ll remove it next week (or sooner, if everyone’s happy).
The only thing missing is the media source editor on the show level. The existing show playlist assignment dialog is now obsolete and arguably broken.
A few open questions:
1. Should the show description (note) editor and the media sources editor be on the same page or should we split them up into separate pages?
2. Are there any remarks or issues with the designation of the media source status in the timeslot overview?
3. In case a playlist contains exactly one entry of unknown duration: should we display the calculated duration instead of *Unknown duration*?
4. Are we happy with the expert mode? If not, what should be changed?1.0-alpha6Konrad MohrfeldtKonrad Mohrfeldthttps://gitlab.servus.at/aura/dashboard/-/issues/231When logging in with some unsupported browser, display notification on browse...2024-03-21T18:12:09+01:00David TrattnigWhen logging in with some unsupported browser, display notification on browser requirementsSince [Dashboard now has problems with certain browsers](https://gitlab.servus.at/aura/aura/-/issues/254), we added a [minimum browser requirements section](https://docs.aura.radio/en/latest/user/dashboard-overview.html#requirements) to ...Since [Dashboard now has problems with certain browsers](https://gitlab.servus.at/aura/aura/-/issues/254), we added a [minimum browser requirements section](https://docs.aura.radio/en/latest/user/dashboard-overview.html#requirements) to the docs.
Nonetheless, first reports from users start coming in, having issue with the login.
Therefore we should notify users when they are trying to access Dashboard with some unsupported browser (version). This should reduce individual support efforts.1.0-alpha7Konrad MohrfeldtKonrad Mohrfeldthttps://gitlab.servus.at/aura/dashboard/-/issues/280Update the `make help` screen2024-03-21T18:07:12+01:00David TrattnigUpdate the `make help` screenMany targets are not visible in the help dialog of the `Makefile`.Many targets are not visible in the help dialog of the `Makefile`.1.0-alpha6Konrad MohrfeldtKonrad Mohrfeldthttps://gitlab.servus.at/aura/dashboard/-/issues/244Collection of image uploader UX improvements2024-03-18T13:15:24+01:00David TrattnigCollection of image uploader UX improvementsParent: aura#214+
---
From the radio feedback:
> - Alternativtext: nicht Dateinamen als Default anzeigen → suggeriert, das wäre eine passende Bildbeschreibung, besser: leer lassen und Tooltipp
> - Lizenzen → CC Lizenzen mit richtigen B...Parent: aura#214+
---
From the radio feedback:
> - Alternativtext: nicht Dateinamen als Default anzeigen → suggeriert, das wäre eine passende Bildbeschreibung, besser: leer lassen und Tooltipp
> - Lizenzen → CC Lizenzen mit richtigen Bezeichnungen und Verlinkung?
> - kann beispielsweise bei der Überschrift “Lizenz” für weniger erfahrene Radiomacher*innen eine Erklärseite verlinkt werden, wie z.B.https://creativecommons.org/share-your-work/cclicenses/
> - Sollte Pflichtfeld sein! Dzt. Upload auch ohne Einwilligung möglich
> - Der Weg, um ein Bild zu ändern, ist nicht ganz intuitiv. Im Bilduploadfenster führt Abbrechen in einen neuen Dialog, bei dem nicht ganz klar ist, was passiert: Wird das bestehende Bild ersetzt? Oder muss ich das erst löschen?
Let's discuss what should be realized.1.0-alpha5Konrad MohrfeldtKonrad Mohrfeldthttps://gitlab.servus.at/aura/dashboard/-/issues/83development-installation: user not found in storage2024-03-14T19:12:23+01:00Ingo Randolfdevelopment-installation: user not found in storagei have seen 2 errors when trying to log in to the dashboard with a local development installation.
this error reported here occurred after removing all relevant docker images and a re-init of aura-web.
loading the page shows this in th...i have seen 2 errors when trying to log in to the dashboard with a local development installation.
this error reported here occurred after removing all relevant docker images and a re-init of aura-web.
loading the page shows this in the console:
```
UserManager.getUser: user not found in storage 2 oidc-client.min.js:1:2013
```
clicking "Anmelden" shows:
```
MetadataService.getMetadata: No authority or metadataUrl configured on settings oidc-client.min.js:1:2273
error oidc-client.min.js:1
getMetadata oidc-client.min.js:1
_getMetadataProperty oidc-client.min.js:1
getAuthorizationEndpoint oidc-client.min.js:1
createSigninRequest oidc-client.min.js:1
_signinStart oidc-client.min.js:47
(Async: promise callback)
_signinStart oidc-client.min.js:47
signinRedirect oidc-client.min.js:47
signinRedirect auth.js:196
D vuex.esm.js:847
dispatch vuex.esm.js:512
dispatch vuex.esm.js:402
signIn App.vue:122
VueJS 43
56d7 main.js:43
Webpack 6
```1.0-alpha4 — Raving Raccoon 🤪🦝https://gitlab.servus.at/aura/dashboard/-/issues/102[STORY] As a programme coordinator, I want to permanently delete a show, for ...2024-03-11T03:02:29+01:00David Trattnig[STORY] As a programme coordinator, I want to permanently delete a show, for undoing a created show by mistakeParent: #149+
---
The o94 legacy backend provides a "delete show" feature. This permanently deletes a show and all related data.
Similarly as the o94 backend, the delete button should asks for confirmation by outlining the consequences...Parent: #149+
---
The o94 legacy backend provides a "delete show" feature. This permanently deletes a show and all related data.
Similarly as the o94 backend, the delete button should asks for confirmation by outlining the consequences.
---
Side note: In most cases a show is deactivated, rather than deleted, in order to keep history data. Compare the [relevant documentation](https://docs.aura.radio/en/latest/user/station-administration.html#deactivating-and-deleting-users).1.0-alpha3 — Playful Platypus ▶️🦦Konrad MohrfeldtKonrad Mohrfeldthttps://gitlab.servus.at/aura/dashboard/-/issues/249rename fields in the Show Area2024-03-11T03:00:23+01:00Margarethe Maierhofer-Lischkarename fields in the Show AreaFor details see the spreadsheet on terms to update.For details see the spreadsheet on terms to update.1.0-alpha3 — Playful Platypus ▶️🦦Konrad MohrfeldtKonrad Mohrfeldthttps://gitlab.servus.at/aura/dashboard/-/issues/213Adding tooltips to fields and functions which are not obvious to users2024-02-20T15:41:32+01:00David TrattnigAdding tooltips to fields and functions which are not obvious to usersThis is a growing list of Dashboard aspects, which benefits from some tooltips or additional help. This list compiles from radio station requests.
- [ ] Episode Details: Explain use of "tags" input field
- [ ] `...`This is a growing list of Dashboard aspects, which benefits from some tooltips or additional help. This list compiles from radio station requests.
- [ ] Episode Details: Explain use of "tags" input field
- [ ] `...`1.0-beta1Konrad MohrfeldtKonrad Mohrfeldthttps://gitlab.servus.at/aura/dashboard/-/issues/234Bug: The dashboard version is not visible anymore, helping with bug reports2024-02-14T10:56:51+01:00David TrattnigBug: The dashboard version is not visible anymore, helping with bug reportsThe status bar with the current dashboard version is not available anymore.
While there is no need to display the version on every page, there should be at least some place we user can check the version.The status bar with the current dashboard version is not available anymore.
While there is no need to display the version on every page, there should be at least some place we user can check the version.1.0-alpha3 — Playful Platypus ▶️🦦https://gitlab.servus.at/aura/dashboard/-/issues/16use error modals instead of alerts?2024-02-08T13:17:27+01:00Andrea Ida Malkah Klaurause error modals instead of alerts?currently important errors are brought to the users attention via simple alerts and more details in the console.
from a UI perspective using a error modal or another form of error notification might be better.currently important errors are brought to the users attention via simple alerts and more details in the console.
from a UI perspective using a error modal or another form of error notification might be better.1.0-alpha3 — Playful Platypus ▶️🦦https://gitlab.servus.at/aura/dashboard/-/issues/250On a fresh Aura Web installation, Dashboard displays no calendar2024-01-25T17:20:56+01:00David TrattnigOn a fresh Aura Web installation, Dashboard displays no calendarPrerequisites: No fixtures imported, no show created.
![image](/uploads/e378c06df0068a4ac118fafe1399390a/image.png)Prerequisites: No fixtures imported, no show created.
![image](/uploads/e378c06df0068a4ac118fafe1399390a/image.png)1.0-alpha7Konrad MohrfeldtKonrad Mohrfeldthttps://gitlab.servus.at/aura/dashboard/-/issues/57Permission managment for adding playlist entries of type "Stream"2024-01-23T17:17:53+01:00David TrattnigPermission managment for adding playlist entries of type "Stream"Parent: https://gitlab.servus.at/aura/aura/-/issues/156+
---
To avoid the possible issue of constant licensing problems or RMs avoding to produce original content it could be helpful to implement following:
* By default only allow addi...Parent: https://gitlab.servus.at/aura/aura/-/issues/156+
---
To avoid the possible issue of constant licensing problems or RMs avoding to produce original content it could be helpful to implement following:
* By default only allow adding streams to playlists by Programme Coordinators
* Other users might be able to do that too, if they got the releveant permission assigned (via Steering)1.0-alpha3 — Playful Platypus ▶️🦦https://gitlab.servus.at/aura/dashboard/-/issues/230[STORY] As a programme coordinator, I want to list shows by category, allowin...2024-01-17T17:32:05+01:00David Trattnig[STORY] As a programme coordinator, I want to list shows by category, allowing quicker organization of content branchesClarify which of these requests we are going to implement:
- Add a *filter by category* option to the show list: Search not only title and sub title, but also the category.
- Display a column with the category in the show list.
- Allow ...Clarify which of these requests we are going to implement:
- Add a *filter by category* option to the show list: Search not only title and sub title, but also the category.
- Display a column with the category in the show list.
- Allow sorting the show list by the category.1.0-alpha5Konrad MohrfeldtKonrad Mohrfeldthttps://gitlab.servus.at/aura/dashboard/-/issues/245[STORY] as ProKo, I want a confirmation dialog when using the "re-activate" b...2024-01-17T16:58:47+01:00Margarethe Maierhofer-Lischka[STORY] as ProKo, I want a confirmation dialog when using the "re-activate" button, so I cannot reactivate a show by mistakeDe- and re-activating of a show is a critical action. Currently, only the deactivation function offers a confirmation dialog to prevent user mistakes. During the testing cycle 12/23-1/24, users from Freirad suggested to also add a confir...De- and re-activating of a show is a critical action. Currently, only the deactivation function offers a confirmation dialog to prevent user mistakes. During the testing cycle 12/23-1/24, users from Freirad suggested to also add a confirmation dialog for the re-activation, to have consistency in the UX and prevent ProKos from doing mistakes.1.0-alpha3 — Playful Platypus ▶️🦦Konrad MohrfeldtKonrad Mohrfeldthttps://gitlab.servus.at/aura/dashboard/-/issues/240Dashboard logs "awk: cmd. line:1: Unexpected token"2024-01-17T16:30:49+01:00Chris PastlDashboard logs "awk: cmd. line:1: Unexpected token"Running dashboard using the latest aura-web deployment (main branch) results in this log output (`docker compose logs`):
```bash
dashboard | awk: cmd. line:1: Unexpected token
```
Works as expected and no further errors - so jfy...Running dashboard using the latest aura-web deployment (main branch) results in this log output (`docker compose logs`):
```bash
dashboard | awk: cmd. line:1: Unexpected token
```
Works as expected and no further errors - so jfyi @kmohrf1.0-alpha5Konrad MohrfeldtKonrad Mohrfeldthttps://gitlab.servus.at/aura/dashboard/-/issues/55Refactor vuex store actions to use async/await2024-01-17T14:56:10+01:00Richard BlechingerRefactor vuex store actions to use async/awaitThe vuex store actions currently use a callback-based approach to deal with code that needs to execute after a certain action has handled. This can lead to strongly indented code that can be somewhat hard to follow.
Thankfully JavaScrip...The vuex store actions currently use a callback-based approach to deal with code that needs to execute after a certain action has handled. This can lead to strongly indented code that can be somewhat hard to follow.
Thankfully JavaScript introduced the :sparkles: magical :sparkles: feature of `async/await` as part of ES2017 which allows us to refactor these kinds of constructs into a more simple shape of:
```js
async function foo() {
try {
const result = await this.$store.dispatch("someAction")
// ... Do something with result
} catch (e) {
// ... Handle error
}
}
```
As the callback approach is spread pretty far across the codebase this will probably take a while to do and an incremental adoption might be advisable.1.1Richard BlechingerRichard Blechingerhttps://gitlab.servus.at/aura/dashboard/-/issues/18load meta infos only at startup/login or when showmanager is activated?2023-11-09T14:28:31+01:00Andrea Ida Malkah Klauraload meta infos only at startup/login or when showmanager is activated?currently we use a huge amount of separate requests to get all the info needed in the show manager (e.g. loading all categories every time we switch to a new show). this is quite fine for a local setup, but it might get laggy when workin...currently we use a huge amount of separate requests to get all the info needed in the show manager (e.g. loading all categories every time we switch to a new show). this is quite fine for a local setup, but it might get laggy when working a remote connection (e.g. via mobile).
should we use certain infos (like show types, and other meta categories) only once, when a user logs in, or only when we switch to the show manager, but not every time we switch to a new show?1.0-alpha3 — Playful Platypus ▶️🦦Konrad MohrfeldtKonrad Mohrfeldt