tl/scenes/urls.py

from django.urls import path

from . import views

urlpatterns = [
    path("projects/", views.projects),
    path("projects/<int:pk>/scene/", views.scene),
    path("projects/<int:pk>/otio/", views.otio),
    path("projects/<int:pk>/revisions/", views.revisions),
]
Add Django backend: users, admin, OTIO + scene persistence A Project (owner, OTIO file, fps, scene JSON) persists the timeline. Session API: list projects, GET/PUT scene, serve OTIO. Admin manages users/projects; seed_demo creates a project from the bundled one_two_three.otio. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> 2026-06-28 23:45:49 -04:00			`from django.urls import path`

			`from . import views`

			`urlpatterns = [`
			`path("projects/", views.projects),`
			`path("projects/<int:pk>/scene/", views.scene),`
			`path("projects/<int:pk>/otio/", views.otio),`
Attribute annotations and scene saves to users Server-authoritative attribution: on each scene PUT the server diffs incoming annotation groups and stamps createdBy/editedBy (+ timestamps) from request.user, ignoring client-sent stamps so authorship can't be forged. Each save also writes a Revision (user, time, +N ~N −N summary, snapshot of the annotation layer), visible in the admin and via /revisions/. Projects gain collaborators so several users can edit one project and get distinct attribution. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> 2026-06-29 00:12:13 -04:00			`path("projects/<int:pk>/revisions/", views.revisions),`
Add Django backend: users, admin, OTIO + scene persistence A Project (owner, OTIO file, fps, scene JSON) persists the timeline. Session API: list projects, GET/PUT scene, serve OTIO. Admin manages users/projects; seed_demo creates a project from the bundled one_two_three.otio. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> 2026-06-28 23:45:49 -04:00			`]`