Podcasts - Support People / Groups #17

Open
opened 2022-07-05 23:39:07 +00:00 by danieljsummers · 1 comment
danieljsummers commented 2022-07-05 23:39:07 +00:00 (Migrated from github.com)

The podcast:person element allows name, role, group, image, and URL to be assigned to each person known to a podcast. It can be attached at the channel or item level. The podcast:valueRecipient element can be a person or a service and has several attributes; these will likely be the same for people across a podcast, but may need to vary for each episode.

For this issue, create the following (all at the web log level):

  • The ability to manage known persons, including the podcast:person attributes , as well as default customKey, customValue, type, and address values for this person (this will be part of a future "value recipient" issue). The person's name is the only required value.
  • For each podcast feed, allow the channel-level person list to be selected, optionally overriding the role and group attributes. (A future issue will add default value recipients.)
  • For each episode, copy the podcast-level defaults to the episode. Provide the ability to add persons at the episode level allow the default person entries to be overridden, and support changing the default persons' role or group for that episode. (A future issue will do the same for value recipients.)
  • Modify the feed generation logic to produce the podcast:person entries for both the <channel> and <item> elements.
The [`podcast:person`](https://github.com/Podcastindex-org/podcast-namespace/blob/main/docs/tags/person.md) element allows name, role, group, image, and URL to be assigned to each person known to a podcast. It can be attached at the channel or item level. The [`podcast:valueRecipient`](https://github.com/Podcastindex-org/podcast-namespace/blob/main/docs/tags/value-recipient.md) element can be a person or a service and has several attributes; these will likely be the same for people across a podcast, but may need to vary for each episode. For this issue, create the following (all at the web log level): - The ability to manage known persons, including the `podcast:person` attributes ~~, as well as default `customKey`, `customValue`, `type`, and `address` values for this person~~ _(this will be part of a future "value recipient" issue)_. The person's name is the only required value. - For each podcast feed, allow the channel-level person list to be selected, optionally overriding the `role` and `group` attributes. (A future issue will add default value recipients.) - For each episode, ~~copy the podcast-level defaults to the episode. Provide the ability to add persons at the episode level~~ allow the default person entries to be overridden, and support changing the default persons' role or group for that episode. (A future issue will do the same for value recipients.) - Modify the feed generation logic to produce the `podcast:person` entries for both the `<channel>` and `<item>` elements.
danieljsummers added this to the v3 milestone 2025-07-04 15:13:33 +00:00
danieljsummers self-assigned this 2026-07-25 14:26:38 +00:00

for dox: ImageUrl for podcast was a permalink (served from current web log); it is now a string, where non-absolute URLs will be interpreted as a permalink, but externally linked images can also be selected. This is how it already worked, but it was stored as a permalink.

~~for dox: `ImageUrl` for podcast was a permalink (served from current web log); it is now a string, where non-absolute URLs will be interpreted as a permalink, but externally linked images can also be selected.~~ This is how it already worked, but it was stored as a permalink.
Sign in to join this conversation.