Forum Discussion
Rise creating long file names
Hello,
When I export the rise file, rise 360 creates long names under the scormcontent > assets. Is there a way to control the number of characters? My LMS says there is an error in the filepath due to the number of characters.
Thank you
- NickStriegel-beCommunity Member
Adding to this conversation, as we're experiencing this issue as well.
Hi Nick!
Thanks for checking in on this!
I noticed you've also opened a support case and connected with my colleague Mark. Smart move! I see that Mark has included you in the feature report we are currently tracking. We'll be sure to update this discussion as soon as we have news to share.
For your reference, here's a deeper look at how we manage feature requests.
- DanaPercivalCommunity Member
Hi there,
I'm also interested in a solution as I've just experienced this issue for the first time today.
Thank you!
Hi Dana!
Thanks for checking in on this!
I've added your feedback to the feature report being tracked to allow the shortening of file names in published output. We'll be sure to update this discussion if it makes it onto our Feature Roadmap.
Have a great weekend!
- DanaPercivalCommunity Member
Thank you!
- StevenCroft-edbCommunity Member
May I add my voice to the request not to make huge long filenames in the zip SCORM export. I have also had failed uploads today but looking at the error code and reading this helped solve the issue. Can I reinforce it mostly seems to be with uploaded videos rather than linking or using embed code. It now uploads BUT there are still rather long filenames - why!?
- SteveWarren-304Community Member
Looking at Steven Benassi's last post, it's not even on the radar, so best to look for another solution - and Rise provides it!
Well, I think Rise is a brilliant product but there are always things you need to work around.
With long filenames, the only workaround that's both simple and consistent is, as in my last post, to embed a video hosted elsewhere.FWIW, the people I use are Streaming Video Provider (SVP). I have absolutely no connection with them, no affiliate relationship, and no friends or relatives working there. Just quite a few years of using their services, with absolutely brilliant support from them (real people responding within an hour or two, and who actually look into problems).
So now, I create the video as I want, upload it to SVP, copy the "share" code, and paste it into a Rise Multimedia > Embed block, where it will stay, unaffected by (say) the Rise "compression" process.
You can even create your own thumbnail!
Job done.Yes, it's a bit of work to set the process up to start with, but once you're under way, it's a breeze.
And the zipped up Rise export files, without the videos, are a whole lot smaller, too!- DavidArndt-507aCommunity Member
Hi Steve, you already posted that workaround above. I appreciate that this is a suitable solution for you. However, it is not a solution for many companies who need/want ownership of all their content in one place or simply can't use external video services for data protection reasons.
Dividing data locations for one product is also rarely a good idea in the long run in my experience. makes maintenance of the content more complex for one thing.It's great that Rise offers both solutions for video integration, but it's sad that one of them has a bug that Articulate fail to acknowledge as such.
Best Regards,David
- StevenCroft-edbCommunity Member
I still also find Sharepoint somewhat unreliable for hosting videos - you can at least use the embed code, but I find the permissions settings slightly unreliable/inconsistent with Sharepoint for selecting certain audiences.
- SteveWarren-304Community Member
Hi David
Yes, I already posted the workaround, but this time, after some experience of using it and transforming my experience with Rise, I thought I'd provide enough detail to point people in the right direction.
As I said, it also (unexpectedly) fixed another problem that's unresolved on this forum - that of providing your own thumbnail image.And I fully agree that it won't suit everyone, but my only intention here is to help maybe a few people who would appreciate it.
As I've also said in my posts, Articulate have very good reasons to obfuscate, encrypt, etc - with legions of people who would reverse engineer their product and "steal" it - but I, like you, wish they'd spend a bit more time on fixing bugs and problems, some of which have been around for many years.
With this particular problem, what's wrong with creating a 32-character md5 string to replace much of the garbage in the file name?Hey ho, crack on...