Provide a Relay Plugin for GoogleDocs as a Publish Destination

  • 1
  • Idea
  • Updated 8 years ago
  • Under Consideration
Archived and Closed

This conversation is no longer open for comments or replies and is no longer visible to community members. The community moderator provided the following reason for archiving: Inactive threads; archiving to prevent necroposing

We use GoogleApps and Docs. I'd like for a Realy user to be able to have a profile that uploads the recording into their GoogleDocs account. That way they can share it with a smaller team and manage the security, etc. The URL would need to be properly formed. Combine this with the YouTube MP4 format, and then GApps users could even automatically preview it in the emails. Google has a Docs upload API (http://code.google.com/apis/documents/) that is available. Can you add that soon?
Photo of Scott Lawson

Scott Lawson

  • 13 Posts
  • 0 Reply Likes
  • sad that I cannot save to GDocs

Posted 9 years ago

  • 1
Photo of Mike Curtis

Mike Curtis, Employee

  • 2204 Posts
  • 216 Reply Likes
I like the idea of working in some way with Google Docs. I once explored this a bit with Camtasia. One thing I ran into was a file size limitation. Not to say that there are not some options around it--or with the way things are going storage of today could be insignificant to storage of tomorrow.

Storage: http://docs.google.com/support/bin/an...

We would love to hear more ideas about ways we could work with Google docs. Thanks for sharing that link to the API!
Photo of Scott Lawson

Scott Lawson

  • 13 Posts
  • 0 Reply Likes
Google is now offering 20 Gigs for $5 per person per YEAR. We feel this is a trivial amount of $ for the value for employees and are looking at migrating all of our file storage for employees to Google. While MP4 is one option, we actually use WMV 95% of the time and that is a better compression ratio. And we typically want to record short screencasts, not hour-long "meetings" as some of the examples in your documentation reference. So, I think a Google Docs PlugIn would be useful and if Organizations are worried about storage, they can deal with that, but TechSmith can simply enable the users to upload where they want. Thanks for listening!
Photo of Rich Boys

Rich Boys

  • 3 Posts
  • 0 Reply Likes
This is an interesting idea for Camtasia Relay, but as Mike pointed out there may be limitations. A typical MP4 file output is often about 100 MB per hour. We have done some prototyping with cloud services and you may see us add one or more of these in a future version of Camtasia Relay. One thing to note is that while we might be able to send up an MP4 file to the cloud, not all services will take advantage of our Flash player and metadata for the rich media experience. Is this important to you?

I will be sure to add your suggestion to our research list. The team has time to try out these new services and see what works and what does not. If you would be interested in participating in these type of projects please feel free to contact me directly.

Rich
Photo of Scott Lawson

Scott Lawson

  • 13 Posts
  • 0 Reply Likes
Having the file and no metadata is fine. It would be better with the metadata, of course, but I am not picky. It is about giving the user an option to record a screencast and store in their GoogleDocs. I feel that if you could treat GDocs EXACTLY like a file share, that would be perfect. One use case it that we use the Mediasite plug in to FTP and Mediasite consumes the WMV and XML into a presentation. This works great! However, some presenters want to save the CAMREC for backup and in case they are asked to edit and re-publish. So, where do we store the CAMREC? Locally . . . not so good. In a shared drive . . . OK, but we do want to manage that. IN Google Docs . . . great! GDocs have search-a-bility, security, sharing, versioning, etc. I will contact you directly to participate. Thanks!
Photo of Scott Lawson

Scott Lawson

  • 13 Posts
  • 0 Reply Likes
Do you have an update on this topic?
Photo of Jess Knott

Jess Knott

  • 155 Posts
  • 2 Reply Likes
It's under consideration and on a backlog of ideas. It's not currently scheduled for production, but it IS something that's being thought about!
Photo of Scott Lawson

Scott Lawson

  • 13 Posts
  • 0 Reply Likes
I see the new feature coming in Version 4 to publish directly to YouTube. (http://www.techsmith.com/camtasia-rel...)

Will this work to a Google Apps YouTube account (Enterprise)? Also, any progress on pushing the other file types like CAMREC or WMV to Google Docs?

Thanks! Scott
Photo of Jim Dusseau

Jim Dusseau

  • 7 Posts
  • 0 Reply Likes
Scott: We'll be testing against YouTube EDU accounts and Apps for Domains, as well as standard accounts. The final release notes will list if we're not able to support those configurations for some reason.

From our research, it sounds like an Apps for Domains admin will need to enable logging into YouTube.

Regarding your request for publishing to Google Docs, we've logged your request. It would be helpful if you told us some more about what you'd use this capability for. Is this a means of sharing videos, or archiving videos?
Photo of Scott Lawson

Scott Lawson

  • 13 Posts
  • 0 Reply Likes
We are interested in publishing to Google Docs to both save a backup or in editable copy of the video (say in CAMREC format) and to have a file to share. Some people might just want to make a little screencast and not put it on a server or in an official repository but be able to have it as a file in order to share with some people or give to our customers in an informal way. Currently we are saving those files into our network shared drives but we are trying to get away from that and put all of our storage for employees in the cloud. For us at QAD that means Google Docs.
Photo of Jim Dusseau

Jim Dusseau

  • 7 Posts
  • 0 Reply Likes
Thanks, Scott. We'll add this information to our list of features under future consideration.
Photo of Scott Lawson

Scott Lawson

  • 13 Posts
  • 0 Reply Likes
I have another idea or development that you could pursue . . . Use the new Google Drive! I know it is not ready to use yet, but you could look at the API and I think tis is what QAD needs . . . and others would benefit, too:

https://developers.google.com/drive/

Are you getting any closer to committing to this idea? Thanks!
Photo of Walter Pelowski

Walter Pelowski, Customer Solutions Engineer

  • 226 Posts
  • 19 Reply Likes
Scott,

While we will continue to evaluate options like this, currently there is no timeline for creating an integration with Google Docs or Google Drive. To my knowledge you are the only person to ask of this thus far. Since your last message about this integration several months ago, you may have noticed that we now support YouTube publishing destinations in Camtasia Relay which was done to help customers that asked for video storage to Google.

Google Drive is yet another location that customers could store content. While we currently support MANY different publishing destinations, there will always be more on the horizon. What we have discussed more frequently since our last discussion is the option to give customers an API that would allow our tech-savvy customers, or these other media hosting companies to create their own integrations with Camtasia Relay. This would provide flexibility for enhancement and improvement to publishing destinations without relying on TechSmith expertise of the destination to make it happen.

We'll have to see what happens with Google Drive. Maybe it will take off, maybe it won't. Many are speculating that it's Google's response to Dropbox. On the Relay team here we're doing what we can to make features that really benefit our customers. Sadly, features like our publishing destinations don't have a broad impact in that they only help those customers that use that particular publishing destination. That is why it becomes very important for us to prioritize how many customers it might help, and as I've mentioned, so far you're the only person to my knowledge that has requested this feature. [I wholly encourage any other customers reading this post that feel they need this integration, to weigh-in.]

In the meantime, we're focusing more on those features that appeal to and can be used by a broader user-base like our webcam integration, server upgrade notifications, and more metadata within our output formats. I hope you can understand and appreciate the difficulty in balancing these feature requests. I can't say we're never going to do this, but it's not an idea that on which we're "any closer to committing" at this time.

If you'd like to brainstorm with me about alternative options to publishing content to your shared drives, I'd be happy to have this discussion with you. Between all of the publishing protocols and destinations we support, I'm confident we could find you an alternative solution that could fit your needs.

Sincerely,

Walter Mitchell Pelowski
w.pelowski@techsmith.com
Customer Solutions Engineer
http://www.techsmith.com
Photo of Scott Lawson

Scott Lawson

  • 13 Posts
  • 0 Reply Likes
Thanks for the detailed post, Walter. I'll stop asking . . . :-)

It makes sense especially since I am the lone ranger on this one . . . I just thought, hey they have a drop to Dupal of all things, [eyes roll], Google should have wider appeal than that!

Google Drive is just Google's new name for an upgraded and better Google Docs with syncing with better APIs and a way for applications like DocuSign to integrate with it. So, I think it will take off, and I would think that your customers like schools would be using it. Pushing to YouTube is good, I guess I'll have to break down and look at that . . . I just wanted a way to ingest the file into a file store, not a "publishing" and sharing system.

An API would be good so if we wanted to roll our own solution we would not have to use an intermediary FTP dropbox and pickup method. Anyway, I think you are right, I can come up with something and maybe I'll take you up on your brainstorming offer when I have thought a bit more about it.

Regards, Scott

This conversation is no longer open for comments or replies.