Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Jira Story Card Description

MyUCDavis Quiz Builder users have associated various media, including graphics, .doc and .pdf files with their questions.

These media are displayed with the question, but they are not built into the question text. Once faculty have uploaded media, they can be deleted from the question, but the files remain on the server and cannot be accessed by faculty.

It is desirable that faculty have a method of retrieving these files for review and/or import into Resources as the first step in adding the media to assessments or question pool questions in Tests & Quizzes.In addition to just accessing the files there should be a way to identify

Successful outcome will be measured by these criteria:
1) Faculty are given a method of retrieving Quiz Builder media files on a per quiz, question pool and collection basis.
2) Identification information specifying which media file(s) are associated with each question that is being exported. If there is a way to bundle the media files together with an export of the questions that would also be desirable. A text file could be included in the zip file of the media that could document this relationship possibly including a
3) Identification includes question title, media file names and even question text all together.
If the image files could be 4) Image files renamed before zipping to their original names (as recorded in the myucdavis database) this would be highly desireable. This would not obviate the need for the text file because there could be name collisions and the text file could document how a filenname is overridden in this case.An expansion of this idea would be to implement a process that would do a MyUCDavis export and take a user to an assessment import and/or question pool import page on SmartSite. This would presumably build on something like Respondus's ability to use content information to relate media to questions. A down-the-road issue that we need to keep track of, if possible.
5) If image files are renamed, deal with name collisions in an intuitive, documented manner.