Drupal 9 Port of Station

Created on 21 June 2022, over 2 years ago
Updated 24 March 2023, over 1 year ago

My current goals and ideas for the Drupal 9.x release of the station project is as follows.

Provide a basic framework for managing content for Podcasting, Terrestrial Radio and/or Internet Only Stations.

All of these have Programs hosted by Programmers. All the Programs may have one or more episodes. The episodes may or may not have music playlists. The music playlists may or may not be tied to a music catalog.

Except for Podcasting the programs are usually scheduled to "air" on a regular basis.

Details:

Programmer:

  • Drupal user content type.
  • Possibly later abstracted to a contact type (i.e. Civicrm contact).
  • Station will not define this type but for now the Program type provided by station has a locked field requiring this relationship.

Program:

  • Currently just a title and locked entity_relationship field to the (DJ's).
  • But some shows have DJ's some Hosts, some Programmers. All the same thing.
  • Custom modules and distributions can tweak that as they see fit.
  • Custom module can extend for Groups permissioning so more then one "DJ" can manage a program.
  • Custom module can provide podcast rss feeds for this type.
  • Custom module can provide Podlove button to make it easier to subscribe.

Episode:

  • Tied to a Episode.
  • Title and Audiofield.
  • Custom modules and distributions can tweak that as they see fit.
  • Custom module can extend for Groups permissioning so more then one "DJ" can manage a episode.

Playlist:

  • Tied to a Episode.
  • Custom modules and distributions can tweak that as they see fit.
  • Custom module can extend for Groups permissioning so more then one "DJ" can manage.

Schedule:

  • Custom modules and distributions can tweak that as they see fit.

Station Catalog:

  • Not provided by Station.

Sub Modules:

I am planning on providing the following sub-modules:

Station Podcast:

  • Provide a Podcast RSS feed.
  • Provide Podlove button to make it easier to subscribe.

Station Rivendell:

  • Automatic ingest of recorded live shows into Station Episodes
  • Merging of Rivendell Logs with Station Playlist to generate NFCB/NPR soundexchange reporting logs.

Without getting further along I can't really say exactly what configuration would be baked into the main Project and what would be left up to custom modules and distributions. But having an agreed upon set of entities and fields to work off of make it much easier to share customization.

🌱 Plan
Status

Active

Component

Other

Created by

πŸ‡ΊπŸ‡ΈUnited States darrick

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΏπŸ‡²Zambia knight218

    Following issue. How much of what you have listed is already in the d8 version and working?

  • πŸ‡ΊπŸ‡ΈUnited States darrick

    If you just install 8.x-2.1 you'll get a program content type which you can add fields to and create views for. You can schedule those program on a schedule grid.

    There are limited options for customizing the look of the schedule and using the scheduled data in views. That is being fixed in the upcoming 3.x version.

    Creating the audio content type and views for that along with podcast views can be done. But the Station module currently doesn't provide in default configurations for those.

    There is no functionality for playlists.

    What I mentioned overall is still the goal. 8.x-2.1 is intended to be a direct replacement of 7.x-2.x. Then 3.x will include the required changes to the program and scheduling entities to make everything much more user configurable.

  • πŸ‡ΏπŸ‡²Zambia knight218

    So for a new project, do you recommend d8 verision or d9?

Production build 0.71.5 2024