Source Files

Welcome to the community, Nancy! You came to the right place for help. 🙂

Can you tell me a bit more about what you're looking to do? Do you want to download a back-up copy of your Rise course for storage purposes? Are you trying to send a copy of a course to another Rise author? 

With a few more details, I can point you in the right direction. 

Hi Alyssa,

I would like to download a back-up copy.

Thanks!

Thanks for confirming that, Nancy! Because Rise is a web-authoring tool, all of the editable content will stay online. But as long as the course is owned by an active subscription holder, it will always be available to be updated! 

You do have the option to download an offline copy of your course, but keep in mind you won't be able to re-upload that copy back into Rise at a later date. My teammate Ashley created a video demo here to show you how it's done. 

Follow up question here on a similar topic - as the admin/team leader, would I have access to the source files that my team creates?  It would be part of my job to manage the source files, and make assignments of developers, but would need to have one location where all source files are managed. Is that possible with Rise?

Hi Peggy,

Each of your teammates would need to invite you to be a Collaborator on a course, or send you a Copy of the course. You can read here about the differences between those two options.

I know a few folks have asked about more options for teams and specifically admin access, so I'll keep you posted on that here! 

For professional content development it seems that with your current model, Rise is not an option that can be used in most enterprise or even academic scenarios.

Apart from obvious legal or regulatory reasons that may require keeping source files offline, there is also the issue of the ability to edit something that you have “archived” at a later time.

Example: a client requests development of courses. Courses are created and delivered in the desired published format. In most scenarios the client requests-expects the source files to archive. The developer also keeps a backup for any future updates – changes (educational content is not a static thing...).

Then a year later the need arises to edit one of the courses. Unless there exists somehow the option to “upload” these source files to the editing environment in order to work with them, any “archiving option” is useless.

It seems that now, Rise “source files” are required to exist only within the active subscription.  Even assuming that the developer maintains an active subscription every year (regardless of actual demand for work) it is not realistic to expect the client to also keep an active subscription just for storing the “source files” for a project.

In reality, this has stopped us dead for proposing Rise as a development option in a lot of cases that it would otherwise really make sense.

Hi Justin, Thanks for chiming in. I've passed along your feedback! 

Say I create a RISE output with "No LMS-Web Only" option and send the zip file to a client who currently doesn't have  a subscription, can the client save the file, in the future subscribe and reopen the file for editing?  Is there a time limit for doing so, and does it rely on me (the course creator) keeping my subscription alive?

Thanks. 

Thanks.  Then if I stop my subscription, does it mean I will lose all Rise courses on my account? How long will Articulate keep courses not linked to an active subscription?

Is there a solution that a Rise course can be saved somewhere without an active subscription, and reopen for update later with a new subscription?

If there is no solution for the above simple request, I don't see how to propose Rise tool to clients.  There is no way my clients will keep, year after year, a subscription just to avoid the source files from being deleted.

I think a good compromise would be to enable users to download a Rise package of some description. 

I would see this package as something that could be stored offline, with the understanding that it is only editible online with an active subscription. I'm speculating completely here but where this might result in a drop off in people subscribing on an indefinite basis there's an argument that any lost revenue could be made up by those who are currently unable to subscribe due to the issue we're discussing being resolved.

I'm not sure whether this could work for anyone but maybe for developers who don't have a need to subscribe to 360 (perhaps they're working exclusively in another tool at a client's request or are a freelancer who's taken up a permanent role), Articulate could offer Storage 360. For a monthly/annual fee developers could extend the 6 month period that courses will exist on Articulate servers post-subscription expiry.