-
Notifications
You must be signed in to change notification settings - Fork 391
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
Loom -> Cap importer chrome extension #363
Comments
/bounty $500 |
💎 $500 bounty • CapSteps to solve:
Thank you for contributing to CapSoftware/Cap! Add a bounty • Share on socials
|
/attempt #363
|
/attempt #363 Options |
Hi, |
Hello, |
How's that PR going? Can I take a look at it as well? |
💡 @neo773 submitted a pull request that claims the bounty. You can visit your bounty board to reward. |
Does the latest PR close the issue? |
I'm 99% sure this will need to be a Chrome Extension.
Requirements are:
User signs into Cap via Chrome extension (similar auth process as desktop app)
Chrome extension asks user to visit their Loom dashboard
We allow the user to import one space at a time, so they should select which space they want to import (spaces which they own, not only a member of).
We retrieve a list of all of the users members for that space
We retrieve a list of all videos belonging to that space
We ask the user which space they want to import into, or ask if they want to create a new one
We preview to the user what is going to be imported
We create the necessary imports, via a new /api/importer prefixed endpoint (from the web app).
When creating the video, we can use this url: https://www.loom.com/api/campaigns/sessions/LOOM_VIDEO_ID/transcoded-url, to grab the video .mp4 file. For now, we can leave the actual .mp4 upload to Cap for later. The Cap team will implement this part.
For imported videos, spaces, members etc, we should have a column on each that tracks their respective Loom id so know it was imported.
The text was updated successfully, but these errors were encountered: