Skip to content

Gate the session-page Meetecho recording link on a populated recording-nameΒ #9592

Description

@alexamirante

Description

A url for the Meetecho recording player is always displayed on the session's page for both past and upcoming sessions.

Drawbacks:

  • The link will be broken until the Meetecho recording is available;
  • The link will stay broken for past sessions that didn't use Meetecho, e.g., interim-2025-iesg-18.

Since there's already a /api/meeting/session/recording-name API that allows us to change the session recording url, I propose to rely on it and only show the button when it has been hit (like we do for YouTube urls).
Meetecho already hits the API above every time a new recording is available.

Code of Conduct


Aggregated with agent assistance on 2026-08-18

Activity

  1. rjsparks commented on Feb 12, 2026

    @rjsparks
    Member

    This hasn't been consistently captured for past meetings - even full IETF meetings:

    >>> Session.objects.count()
    14802
    >>> Session.objects.filter(meetecho_recording_name__isnull=True).count()
    0
    >>> Session.objects.filter(meetecho_recording_name="").count()
    13852
    
    >>> has_mrn = Session.objects.exclude(meetecho_recording_name="")
    >>> meetings_no_mrn = Meeting.objects.exclude(session__in=has_mrn).distinct()
    >>> [int(n) for n in meetings_no_mrn.filter(type_id="ietf").annotate(meetnum=Cast("number",output_field=IntegerField())).exclude(meetnum__gte="125").values_list("number",flat=True)]
    [120, 119, 118, 117, 116, 115, 114, 113, 112, 111, 110, 109, 108, 107, 97, 96, 95, 94, 93, 92, 91, 90, 89, 88, 87, 86, 85, 84, 83, 82, 81, 80, 79, 78, 77, 76, 75, 74, 73, 71, 70, 69, 68, 67, 66, 64, 63, 62, 61, 60, 59, 58, 57, 56, 55, 54, 53, 52, 51, 50, 49, 48, 47, 46, 45, 44, 43, 42, 41, 40, 39, 38, 37, 36, 35, 34, 33, 32, 31, 30, 29, 28, 27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1]
    

    I think we'd have to code a switch to the behavior at a date (circa 121) that we were very confident that having the name meant there was a recording. Otherwise, we have a task of identifying and reconditioning the older Session objects where there is a recording at the default name the datatracker produces.

  2. alexamirante commented on Feb 13, 2026

    @alexamirante
    CollaboratorAuthor

    I confirm I've been hitting the recording-name API since IETF-120.

  3. changed the title [-]Remove automatic url for Meetecho recordings[/-] [+]Gate the session-page Meetecho recording link on a populated recording-name[/+] on Aug 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions