@Chris_Hofer Thanks for speculating, but a couple of things. Firstly, I've had these image problems before and I've checked the html coding to verify addresses/paths are correct. I've worked with admin on these problems before, and I'm familiar with the syntax. But this brings up another issue. Why are image references getting corrupted in the first place? Why should exporting a course package or QTI and then importing it cause problems? We've had these issues before, and the image handling is shoddy at best.
In fact, copying an entire course seems to be the best option, i.e., we get images to show in the copied course. However, doing a quiz export/import gives problems- broken image links. It seems when a quiz export is performed, images stored in the file structure don't get copied, or their address references are corrupted in the imported file so that the images are not referencing correctly. And to be sure, images are either inserted from the file system, or uploaded into the problem question from an external source (not copied/pasted)--both of which are recommended and supported functions for including images.
There seems to be a similar issue here--images are not being copied (for some mysterious reason) when the quiz is migrated, or more appropriately, the reference address is getting corrupted. And the most frustrating point is that it happens sometimes and not others. And I probably know a lot more than most teachers, since I'm familiar with LMS systems (BB, Canvas, Moodle) and some coding. What are other teachers going to do when then experience these difficulties? I hope they flood their admin and Instructure with emails and comments!
So I reiterate. Canvas has a shoddy, temperamental coding for handling images. They shouldn't offer faculty the ability to include them in their questions, and offer them export/import options that don't function properly. Faculty shouldn't be expected to have to know details about coding, OSs, etc. In fact, if the program allows a teacher to copy and paste an image into a question, it should have a robust way of dealing with it! One of the most important rules of coding, or programming in general, is designing a "dummy" proof program. Either simplify and restrict the code and its abilities so that it always functions, or provide the functionality but ensure the code is robust enough to handle it.
This leads me to have to be in disagreement with your Honest Opinion about "good practices." No offense, but that's a bit elitist. Although personally I don't copy and paste images (although the program allows this), the teaching public should not have to have knowledge of what a program can and cannot do. It is the responsibility of the designers to ensure their program can deliver what it offers, what it allows. Which is part of my point here, because the program is not functioning properly, even with "best practices" employed, which is supposed to be within its own construct!
@hesspeI agree 100% that Canvas should keep employing the two formats.
Even if only 1% of teachers have significant migration difficulties, this still amounts to an unacceptable loss of time and wages (see above) for the people in this community. In addition, even if the current migration worked perfectly, it still represents a huge time investment, for something that a lot of us won't even care about! I can only hope that the community puts pressure on Canvas to either keep both formats, or at the least, offer reliable transitioning tools.
This discussion post is outdated and has been archived. Please use the Community question forums and official documentation for the most current and accurate information.