[EPIC] UI extensions based on the new fields provided in AEP05

changed milestone to %1.0-alpha2 — Precise Pheasant

added P2 discuss + 1 deleted label

assigned to @kmohrf

mentioned in issue #89 (closed)

marked this issue as related to steering#150 (closed)

marked this issue as related to steering#151 (closed)

changed title from UI extensions based on the new fields provided in AEP05 to [EPIC] UI extensions based on the new fields provided in AEP05

added EPIC label

changed the description

added requires-refinement label

marked this issue as related to #152 (closed)

mentioned in issue #152 (closed)

changed the description

added 1 deleted label

added To Do label

marked the checklist item Update all links and link types as completed

marked the checklist item Update all links and link types as incomplete

marked the checklist item repetition_of (foreign-key to self): When creating a timeslot in calendar view, there should be the option to select any previous timeslot, in order to schedule it as a repetition of that timeslot. repeated timeslots do not have their own Playlist and Note data. They are rather referencing such data from the timeslot they are referring too. as completed

marked the checklist item repetition_of (foreign-key to self): When creating a timeslot in calendar view, there should be the option to select any previous timeslot, in order to schedule it as a repetition of that timeslot. repeated timeslots do not have their own Playlist and Note data. They are rather referencing such data from the timeslot they are referring too. as incomplete

mentioned in issue #101 (closed)

marked this issue as related to #161 (closed)

mentioned in issue #170 (moved)

marked this issue as related to #170 (moved)

changed the description

mentioned in commit 560d8dda

marked the checklist item tags (nullable TextField): enter tags with a popular delimiter approach (like blank or semicolon). Nice too have eye-candy: after entering a delimiter character, tag-text turns visually into a "tag" with rounded border etc. ;-) but no real requirement for that. as completed

Regarding contributors on the note @fm_margarethem: the steering admin interface does not currently offer the ability to add new hosts, nor does the dashboard. When editing the contributors list: should users be able to add new hosts or should they only be able to select from existing hosts?

The idea behind the contributors field is to allow owners of a show add hosts (of another show) that contributed to a specific episode of a show.

Therefore, it should only allow the owner(s) of a show to add or remove known hosts.

Known hosts sounds like contributors should be selected from a list of existing hosts. That’s fine for me.

But how and where are new hosts created and added to steering? Will the admin interface in steering be extended to support adding/removing hosts? I’m just confused how anyone (even admins) add new hosts to the steering database.

Actually, there is no front-end to do this.

But, there is an API for that, and this is how I do it:

$ http -a $TOKEN -A bearer POST aura.local/steering/api/v1/hosts/ name=Ernesto

We may need to move this to a pre-beta version: [EPIC] Extended radio station settings, replaci... (#162 - moved)

I think adding another steering admin interface just for hosts might be the better (or at least the fastest) way even if our long term goal is to move these into the dashboard. We had a discussion if we rather want the CRUD operations for basic data models or the permission management to land in 1.0 and decided on the latter.

That being said, if it’s only the hosts model, I can imagine doing the CRUD interface for that in the dashboard (though not as part of this release).

Thanks for your input and I agree on your opinion, @kmohrf. Having the option in the steering admin interface to change / add hosts would be sufficient for MVP scope.

We already discussed the implications of creating a "settings page" on dashboard for ProKo & admin users which would allow them to change settings which are currently only available via the steering backend interface, and we agreed to postpone this to 1.0 because it is doubling the functionality of the steering backend (so it is out of MVP scope).

When I talk to ProKos, often they mention they are very used to using backend interfaces and tools that have very basic list-based UIs. So as long as the functionality is concerned for ProKo features, we can also lower the priority of creating fancy frontends a bit and focus on how to acheive the basic availability of the functions.

@kmohrf @eigenwijsje @fm_margarethem I agree that bulk editing hosts for PCs can be covered by the Django Backend in 1.0.

But please note, hosts at least need self-service features to edit their profile within the 1.0 release. Check [EPIC] Host and User Profile Managment (aura#41 - closed). This is currently scheduled for alpha-4 and is not yet fully specified.

@kmohrf @fm_margarethem a small addition to @eigenwijsje explanation:

The idea behind the contributors field is to allow owners of a show add hosts (of another show) that contributed to a specific episode of a show.

Therefore, it should only allow the owner(s) of a show to add or remove known hosts.

There can also be varying hosts (of the same show) for episodes. For example a show is usually maintained by 5 hosts. So, when broadcasting a new episodes, these 5 hosts are pre-populated in the note. Now in some episodes only 3 of them are actually doing the show. In that scenario the other 2 hosts are removed when editing the episode details (note).

mentioned in commit aa707763

marked the checklist item contributorIds (many-to-many to Host): add ability to query and add individual hosts for the specific note: Episode contributors: Add ability to query and ... (#170 - moved) as completed

mentioned in commit db7dc49d

marked the checklist item subtitle (nullable TextField): Display the sub-title of a category, when it is assigned in the show view as completed

mentioned in commit 319cf540

marked the checklist item internalNote (nullable TextField): See [STORY] as a programme coordinator I need an ed... (#152 - closed) as completed

mentioned in issue aura#203 (closed)

marked this issue as related to aura#203 (closed)

mentioned in issue steering#159 (closed)

added 1 deleted label

changed milestone to %1.0-alpha3 — Playful Platypus

mentioned in issue #182 (closed)

marked this issue as related to #182 (closed)

changed the description

mentioned in issue #185 (closed)

mentioned in issue #186 (closed)

changed the description

regarding the repetition of a timeslot:

could the repetitionOfId be shown in a shorthand form (as a bold or coloured W/R for "Wiederholung/repetition") in the Calendar to make it visible at one glance for ProKos? The shorthand can be displayed next to timeslot & show title in the Calendar Day View, and it can be visible in the Calendar Week View in the tooltip of a timeslot.

This sounds like a fantastic idea.

ok, so since this was the last open topic from the list to be discussed, I guess no more need for input/refinement here.

[EPIC] UI extensions based on the new fields provided in AEP05

Common

`Category`

`Show`

`Host`

`Note`

`Timeslot`

`License` and `LicenseType`

`Link` and `LinkType`

Designs

Child items ...

Activity

[EPIC] UI extensions based on the new fields provided in AEP05

Common

Category

Show

Host

Note

Timeslot

License and LicenseType

Link and LinkType

Activity

`Category`

`Show`

`Host`

`Note`

`Timeslot`

`License` and `LicenseType`

`Link` and `LinkType`