This also changes the choices field, as actual code references like the
one created by __members__.items() will break migrations in the future,
when the code changes.

Browser clients have limited power over the response, specifically the
name of the file in a response. The anchor (a) element had support for
the download attribute for quite some time but is only applied for
downloads from the same origin. As clients should be able to consume the
the lohrothek api from other origins, the filename should be
configurable through the request.

Without these headers media files like images can be loaded by the
browsers DOM but not be examined in JavaScript. This is usually not a
problem but frontends might want to analyze images or other dynamic
content. For instance thekno will look at the overall brightness of an
image to determine the impact of filter effects and will adapt it
accordingly.

we need this value to properly address tracks in the queue.

Revert "Merge branch '100-quick-create-reports'"

See merge request !3

This reverts commit 12b4d0b8

the view. finally at least something should work.

This might be a question of semantics but arguably a report is only
~available~ if there is any content to present.

In addition to the existing fields the recording api now returns

* tags
* publication times
* broadcasts

This is helpful when filtering by tags because we usually display these
recordings on a detail page of a single recording as part of a similar
content section. In this case we don’t want the recording from the
detail page to be in the result set.

This makes it easier to find recordings for a particular series.