Page Comparison

1. Background

2. Methods of adding content to Echo

3. Overall approach to using Echo

4. Notes

   1. Interacting with Echo content

   2. Collecting together related videos in Studio and Echo

   3. How ‘Student View’ works with Echo

   4. For further information about Echo

5. Standard workflows for using Echo with Canvas

a. Workflow groupsGroups

b. Sequence diagramDiagram

c. Links to the workflowsWorkflows

d. Workflow group Group notes

...

...

3. A ‘Student Submission’ method allows students to upload video videos to Echo as part of their assessment submissions for a given Canvas course. This video These videos can then be watched inside Canvas by instructors.

...

(Additionally, any videos that were in a user’s private Studio area in Canvas should now be in this user’s personal Echo library.)

A separate collection will be set up for each delivery of a Canvas course. This formal collection will have the same name as the related Canvas course (e.g. '2023 TSM7201A Studio'). Instructors should ensure that any video used in that delivery has been added to this specific collection and linked to from the relevant Canvas course.

...

• the collection is a predictable location for collecting together the Echo content related to a given Canvas course, regardless of the current status of the instructors teaching it; this content can be in active use in Canvas or not; this content can be in active use in Canvas or not

• when collections are duplicated for the next delivery of a Canvas course, the collections for previous years provide an archive of content that can be accessed if for example a video is accidentally deleted from the collection for the current delivery

• it’s easier to check if there are issues with students being able to access and interact with the relevant Echo content because links to this content from a given Canvas course should all point to this collection.

Other collections can be created that are different to this formal collection. These additional collections can be for casual sharing of content, and can be useful for example to collect together materials on a topic of interest, or as part of planning for a future course. These additional collections should only be used for content that if lost would not affect the delivery of the Canvas course.

...

• the means to access content migrated from Studio (ie prior to the start of 2023), including student video submissions

• a backup store of classroom capture and livestream content.
  The In contrast, the principal method of accessing these captures and livestreams is via the copy of each which will automatically be made available in the Echo library of one staff member involved with the delivery of the relevant Canvas course. This staff member can then create a link to these captures/livestreams in Canvas via the formal course collection if desired.

...

The student submission method allows video submissions to Echo to be tied to the Canvas course for which the submission was made, again allowing related video content to be kept together.

When a student submits a video as part of their assessment, Echo adds the submitted video to the student’s personal Echo library and links to this from the assessment screen.

...

...

• The workflows expected to be most used are highlighted in the diagram and shown in red in the link tables. Each workflow is given a code, e.g. A.2. is the second workflow in Group A.

...

...

...

• Ownership of video collections

  • Currently all users - including students - are allowed to create collections and each collection remains private to the user who created it until that user chooses to share the collection with others.

  • You are thus able to access Echo360 content in any collection that you have created or to which you have been made a member

  • As the owner (or ‘manager’) of a collection you control who has access to your collection and what they can do with it. You can make someone else a manager of your collection but once you do, you can’t undo this by yourself since managers can not remove or demote other managers. If you want to remove a collection manager, ask one of NIDA’s Echo360 admins for help

  • Collections have an option that allows whoever clicks on a link to be made a member of that collection

  • The following practice is recommended for managing course-based Echo collections: A single person is designated as the manager for all course-based Echo collections for a given degree/school. This person would likely be the course coordinator or similar. This person creates all course-based Echo collections for the degree/school so that by default they are given the role of Collection Manager.

    • All staff who are then added as members of this collection are added in an Editor role only in order to prevent them accidentally deleting videos from this collection. If a video really needs to be deleted from the collection, then staff ask the Collection Manager to do this for them. Or the Collection Manager does this as a standard part of managing these course-based collections.

    • the standard role for all students should be Reviewer.

D. Ownership of individual videos

...

• What they are then allowed to do depends on their role.

  • Note that for students, who have minimal rights over videos that have been shared with them, the actions they are able to take with the video are viewing it, downloading it and removing it from their library.

  • If you thus want to prevent students from downloading content you have shared with them, instead of sharing the video with them, create a collection, add the video to the collection then add students to this collection in the role of Reviewer.

• Equally, if someone owns a video and has shared it with you, you may not be able to share it with someone else.

...