-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[wishlist] one or more url archive link fields per slot, for linking to archives of that performance #20
Comments
Sounds good! So it would be a single URL for each Stream, to be updated post-event, right? |
Multiple URLs |
Multiple urls, we're currently archiving each individual stream to YouTube.com and archive.org |
I like the idea of having archived video URLs to each slot. Maybe the EDIT button could be removed in the same time. |
* Define `StreamArchiveURL` model and create migration * Register `StreamArchiveURL` admin and add inline to Stream admin * Add stream archive URLs as nested serializer on `StreamSerializer` * Set fk related name to `archive_urls` * Make archive urls nested serializer writable on `StreamSerializer` * Make `archive_urls` not required on serializer * Test partial update (PATCH) on Stream, to update `archive_urls` of a Stream Closes #20
Sorry it took so long. I've added Archive URLs to the Stream model. These can be added either via admin or API. You can check out the API documentation at /docs to see how to update them, but basically you'd need to do a PATCH request to {
"archive_urls": [
{ "url": "https://archive.org/foobar", "name": "Archive.org" },
{ "url": "https://youtube.com/foobar", "name": "YouTube" },
]
} The |
So good! Thankyou! |
we're currently brainstorming some post-event display stuff in muxy-frontend, and thought it'd be handy to link to the archived performance (on youtube.com/archive.org) from the performer card on night.tidalcycles.org (for example)
The place to keep that info of course is here, and sfradkin can add/update the links via the api when doing the video processing/upload
The text was updated successfully, but these errors were encountered: