Echo360 - Introduction

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 groups

b. Sequence diagram

c. Links to the workflows

d. Workflow group notes

1.BACKGROUND

Echo360 is a platform used at NIDA to hold video content used to teach courses.

This content is then linked to from Canvas (aka ‘NIDA Learn’), which is NIDA’s learning management system.
Echo360 replaces Canvas' built-in video app called Studio.

Some advantages of using Echo360 over Studio are that it provides more features than Studio, allows video to be centrally viewed and managed, and has a much more active development path.

Echo360 is commonly referred to within NIDA as just ‘Echo’.

Apart from videos, Echo can also hold audio files, pdfs and PowerPoint files to help collect together teaching content on a given topic. However, since video is the main format for content in Echo, almost all references in the descriptions and workflows below will refer to this Echo content as ‘video’.

2. METHODS OF ADDING CONTENT TO ECHO

Echo provides three methods to allow content to be uploaded and made available:

1. A ‘Course->Section->Class’ method involves using a hierarchy that is set up in Echo. This hierarchy matches a similar structure in Canvas. The Echo hierarchy performs two main functions at NIDA:

• Migration: Content from Canvas' built-in Studio video application was migrated into this hierarchy as part of decommissioning Studio at the end of 2022. This content could not be migrated into Echo in any other way.

• Classroom capture: NIDA AV staff set up schedules for the recording of classroom sessions (and also livestreamed content if needed) and this content is then automatically added into folders in this structure. Instructors can then link to this captured content from the relevant course in Canvas if necessary.

The Course-Section-Class method is Echo’s older method of managing content.

2. A ‘Collection’ method allows each student and instructor to optionally share videos from their own personal Echo video space. If a user decides to share their content, they can do this by sharing an individual video, or collecting videos together into a Collection and then sharing the Collection with others.

Since a collection can thus contain videos from the Echo libraries of a number of users, content for a given Canvas course could be spread among multiple current or past instructors.

The Collection method can also be used to share Echo content informally. This can be for reasons not tied to the delivery of a specific course in Canvas.

The Collection method is Echo’s newest method of managing content.

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

Because of limitations in the ‘Course->Section->Class’ method, most instructor use of Echo will be using the 'Collection' method. However it should be remembered that content related to a given course in Canvas could be distributed among any or all of the above methods.

The following diagram summarises how content is added to Canvas via Echo for the three methods (click diagram to zoom):

3. OVERALL APPROACH TO USING ECHO WITH CANVAS

Given that there are multiple methods of adding content to Echo, there needs to be some standardisation of approach to ensure that Echo content can be found in a predictable way. The following guidelines have thus been developed to help guide use of Echo with Canvas.

1. Due to the limitations of the Course-Section-Class method, staff should use the ‘Collection’ method for any Echo content that needs to remain linked to the delivery of a particular NIDA course.

This applies to any new Echo content added to Canvas during and after 2023. This is because Echo content prior to January 2023 has been migrated from Studio into Echo, and any Studio links in Canvas have been replaced with Echo links for this time period.

(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.

This has the following benefits

• 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

• 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.

2. the ‘Course-Section-Class’ method is used as

• 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.
  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.

Apart from it being quicker and easier to link to these captures/livestreams from the staff member’s Echo library rather than from the course-section-class hierarchy, any link created in Canvas to the hierarchy is likely to break when the Canvas course the link is in is rolled over for the next delivery.

To help find content in the ‘Course-Section-Class’ hierarchy, the following diagram illustrates the levels in Echo’s ‘Course-Section-Class’ method and how they match equivalent levels in Canvas (click diagram to zoom):

3. The student submission method can be used whenever instructors would like students to upload assessment submissions in the form of video. Assessments can be set up to make video just one of the formats that the submission can be made in.

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.

4. MISCELLANEOUS NOTES

A NOTE ABOUT INTERACTION WITH ECHO CONTENT

Echo allows for more than just consuming content - staff and students can interact with this content to help learning and teaching. Interaction with Echo content can happen both in Canvas and in Echo. Here are a couple of examples of how interaction can happen in each platform:

• Students can contribute Echo content to a Canvas course which can then be used as a conversation starting point. This is possible in Canvas by uploading an Echo video within a Discussion post.

• Instructors can contribute Echo content to a Canvas course. Students then view this content and can interact with it in Echo, for example by typing in questions, comments or personal notes, answering prepared polls, or bookmarking sections they found problematic or would like to revisit.)

A NOTE ABOUT COLLECTING TOGETHER RELATED VIDEOS IN STUDIO AND ECHO

In Canvas, each user was able to create groups in his or her private Studio space to collect together related videos. If you would like these groups recreated as collections in Echo, please contact Andrew.

A NOTE FOR INSTRUCTORS ABOUT HOW ‘STUDENT VIEW’ WORKS WITH ECHO

Echo videos will not display properly when instructors turn on Student View in Canvas. Instead the following message is shown:
Invalid 'lis_person_contact_email_primary' in LTI request: Value was not provided or was empty
This happens because Echo needs have an account in its system for each person accessing its videos.
However when Student View is used, there’s no corresponding account in Echo to go with it.

FOR FURTHER INFORMATION ON ECHO

Information on Echo for instructors can be found at this Echo support landing page: https://learn.echo360.com/hc/en-us/

• General introductory videos for instructors can be found here: https://help.echo360.com/hc/en-us/articles/360039828532-Getting-Instructors-Started
  

Information on Echo for students can be found at this Echo support landing page: https://help.echo360.com/hc/en-us/articles/360039793831-Getting-Students-Started

5. STANDARD WORKFLOWS FOR USING ECHO WITH CANVAS

A number of standard workflows have been devised to ensure that video content at NIDA is stored and presented in a predictable way in both Echo and Canvas.

1. WORKFLOW GROUPS

These workflows fall into five Groups. The Groups holding the most used workflows are bolded:

More detail on the workflows in these Groups is provided in the sequence diagram and the four link tables below. Use the links in the tables to access the individual workflows.

• 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.

2. SEQUENCE DIAGRAM (click diagram to zoom)

3. LINK TABLES

4. WORKFLOW NOTES

The following notes should be read in conjunction with the workflows. Each workflow links to these notes where necessary.

Group A: Staff need to upload video content to Echo

General notes applying to all Group A workflows

• In addition to videos, you can upload presentation files (such as PowerPoint) and pdfs to Echo360. However uploading anything but video and audio files is currently not possible unless using the Course-Section-Class method. Thus, since video is the main type of content used in Echo and use of the Course-Section-Class method will be minimal, these workflows tend to refer to this content as just ‘video’

• Whenever you upload content to Echo, it’s added to your personal Echo library:

  • This library content is available off the ‘Library’ tab after clicking on the ‘My Echo360 Library’ link in the blue menu shown to the left of any Canvas course

  • You can use one of the three methods to share this content

    • as a student you can use the student submission method to upload your video content as part of an assessment submission

    • as an instructor, you can use either the course-section-class or collection method to allow others to access this content. Or you can simply keep your content to yourself in your library.

  • You can view and manage your Echo library from within Canvas.

  • Zoom recordings and classroom captures organized by the AV department should also appear in your Echo library.

• There are three places you can link to Echo videos from within a Canvas course page:

  • the text editor

  • the Modules screen, and

  • the course’s blue navigation menu.

    Of these, linking via the the text editor is recommended. Using the Modules screen or navigation menu is not preferred because both require using the Course-Section-Class method. Links created in Canvas to classes in the Course-Section-Class hierarchy are likely to break when the related Canvas course is rolled over.

Group B: Staff need to set up Canvas so that students can submit video to Echo for their assignments

General notes applying to all Group B workflows

• Video assignments follow the same three-step sequence as for any other assignment, ie setup, submission and grading.

• The Echo-preferred workflow uses the ‘Online + Website URL’ option in Canvas
  An alternative version using the ‘Online + File upload’ is also possible.

The above workflows are shown as Option A and Option B in these guides.

• Students should be able to create second submission attempts themselves unless instructors have chosen not to allow this as part of the assignment setup

• Video submissions and/or reattempts by students should not be altered by instructors unless students are unable to resubmit; NIDA’s Canvas and Echo admins can help if needed

Group C: Staff need to link to Echo video content from Canvas

General notes applying to all Group C workflows

• These workflows cover creating a simple link to an Echo video as well as embedding an Echo video in Canvas

• With these workflows you can link to both uploaded videos and videos recorded via Echo (ie webcam sessions) because once uploaded to Echo, Echo treats them the same.

• You can link in Canvas to a video that’s in your personal Echo360 library, either

  • as an individual video that you added or that someone shared with you, or

  • in a collection you created, or that another user made you a member of.

• However when linking to a video in Canvas, you can’t search for videos by the collection they’re in, since collections are not shown when linking.

  • So in order to link to a video in a collection, view the collection to find the video’s title. Then search for that title

  • Echo allows you to search for parts of a video title but will not search on punctuation and spaces

Group D: Managing content, and sharing videos individually or via collection

General notes applying to all Group D workflows

A. Introduction to collections
(This introduction is most applicable to workflow D.2. Adding a video to an Echo collection)

• Collections are a way to group videos together in Echo360

• Collections can have none, one or many videos

• Video management

  • Videos added to a collection are not copied into that collection. Instead they are added as a link. For this reason, if a user adds a video from their personal Echo360 library into a collection and then deletes that video from their library, the video also disappears from the collection. This also means that if this video is linked to from Canvas, access to the video via this Canvas link will no longer work

  • All the videos in a collection can be copied. This creates a separate softcopy file for each video in the collection: https://learn.echo360.com/hc/en-us/articles/360055448052

  • For the above two reasons, staff can request NIDA’s Echo admins to make a copy of collection media whenever desired as a precaution against loss

  • the formal collections related to each offering of a Canvas course will be duplicated before each new offering of a Canvas course. For example, the collection related to Canvas course ‘2021 ACT7101A’ will be duplicated and named ‘2022 ACT7101A'. If a video (link) in one of these collections is deleted, the link is not deleted in the other collection

B. Formal Canvas course collections

• One collection is created in Echo to match each Canvas course that may or will link to Echo video content. This formal collection has the same name as the Canvas course it belongs to.

  • The collection should never be deleted

  • The collection should also not be shared with students; to provide students with access to Echo content, link to that content from Canvas

  • if you have been assigned as the Manager for this formal collection, you will be responsible for sharing this collection with whoever is needed by adding and removing members of this collection

    • initially you will be the only member of this collection

    • An ‘Auto-Enroll Link’ option is available that adds whoever accesses the link as a Reviewer of the collection; this can be used to save time adding staff to the collection

    • the standard role in this collection for all staff (apart from the collection Manager should be Editor. This will help prevent accidental deletion of videos from the collection.

    • Students should not be invited to join this collection.

  • A copy of this collection will be created by NIDA’s Echo admins for each offering of a course in Canvas.

    • This copy will contain the same videos as for the previous offering

    • Members of the new collection can thus change content without affecting the content of the previous version. This ensures that

      • the collections continue to accurately reflect the Echo content for each delivery of a course

      • you can return to collections for previous years to access Echo content you may wish to reuse.

C. Introduction to video membership

(This introduction is most applicable to workflow D.3. Sharing your Echo collection)

• 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

• If you upload a video to Echo, you are automatically made the owner of that video and can thus manage it including copying, editing, downloading and deleting it.

• However the following actions on your video require the help of one of NIDA’s Echo admins (eg Josh, Ben, Andrew and some IT staff):

  • if you would like to give ownership of your video to someone else

  • if you would like to create a public link to your video, ie so it can be viewed outside NIDA. (You can still share your video with people inside NIDA.)

E. Sharing individual videos

• If you share an individual video with another user, this adds the video to their personal Echo library. Since you are still the video’s owner, your name appears under the video in their library.

• 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.

Group E: Deleting Echo content

General notes applying to all Group E workflows

• When using the course-section-class method, content should not be deleted from Echo sections or classes in Canvas courses that have already been delivered to students. Instead the link to this content can be deleted in Canvas for the next delivery of the Canvas course

• When using the collection method, content in a user’s personal Echo library can be deleted by the user as desired. However

  • it might not be possible for users to delete Echo content shared with others via collections depending on how the collections have been set up or shared; NIDA’s Echo admins can help in this case

  • if you delete a video in your personal library that has been added to a collection, it's also removed from that collection. This may affect others if you have shared this collection with them

If you no longer want a video but it is still needed, it’s thus worth considering making someone else co-manager of the video or adding videos to course collections using a non-personal Echo account,

• When using the student submission method, video submissions by students should not be deleted from Echo unless the student has uploaded the wrong submission prior to grading/instructor feedback. Students should be able to remove these submissions themselves; if not, NIDA’s Echo admins can help

ECHO ADMIN CONTACTS

For support, contact one of the NIDA Echo admins. Current NIDA admins as at January 2023 include:

For general support, please raise a help ticket by emailing IT at help.IT@nida.edu.au