Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »


Most documentation for using Media Collections Online is available on the Avalon Media System wiki. However, the Avalon documentation is generic, not institution-specific. This page contains IU-specific information. For general help with uploading and editing features of Avalon, see the Avalon Collections Guide.

Creating Collections

Before creating a collection, please contact Media Collections Online support with the proposed name of the new collection and a brief description of the collection.

Collection Staff

MCO provides several roles with differing levels of privilege: Manager, Editor, and Depositor. Managers can add people to the Editor and Eepositor roles from the collection page under "Manage Collections." To add new people to the manager role, please contact Media Collections Online support, providing the network IDs.

File Management Policy

When you add content to Media Collections Online, the master files are automatically saved to the IU Scholarly Data Archive (SDA). If you skip transcoding by ingesting pre-transcoded derivatives, those derivatives are also stored in SDA.

Once the ingest has successfully completed, the media files are moved to SDA and are no longer available in the dropbox. For batch ingest, the ingest manifest spreadsheets are left in place.

In moving the files to SDA, the files are renamed to include the MCO identifier in the file name. For example, if the ingested master file was named, and the identifier in MCO for the file (section, not the entire item) was 1234, the file would be renamed before being stored in SDA. Please contact Media Collections Online support to request retrieval of the master file or pre-transcoded derivatives.

Importing MARC Records from IUCAT

MARC records can be imported from IUCAT to MCO in two ways: 

  1. The Import function on the Resource Description Form for a single Avalon item can import a single IUCAT record into Avalon based on the Catalog Key in IUCAT
  2. A Batch Ingest Package can contain a spreadsheet of Catalog Keys from IUCAT to import several IUCAT records at the same time

To import from IUCAT into MCO, use the catalog key number at the end of the IUCAT URL for a record as the Bibliographic ID in MCO (for example, 6502911 is the MCO Bibliographic ID from This is equivalent to the 035$a Sirsi catalog key in the MARC record and is what is used for IUCAT permanent URLs. Paste that number into the Bibliographic ID column in a Batch Ingest Package spreadsheet or in the Bibliographic ID field in the Resource Description Form. The Bibliographic Label for this identifier is “Catalog Key,” which you would include in the Bibliographic Label column in the spreadsheet or select from the drop-down menu in the Resource Description Form.

MCO Drop Box Access

Please contact Media Collections Online support for information on how to access the Avalon drop box if you will be using batch ingest or need to upload files larger than can be handled by the browser (larger than 250 MB).

Batch Ingest Email Address

For Row 1, Column B of the ingest manifest use your network ID, not your full email address, for the submitter's email address.

Integration with Canvas

There is general documentation about Avalon/LMS integration here: Delivering Avalon Content Through a Learning Management System (LMS), however this is Avalon-general, not Media Collections Online/IU Canvas-specific. As of January 2016, MCO is not yet set up as a Canvas-wide tool. it is still possible to make this connection with some additional development work by the UITS Canvas support team.

  1. The MCO LTI tool needs to be added to the course site. Justin Zemlyak jazemlya@iu.eduis a Canvas administrator that has recently done this setup.
  2. The LTI tool gives MCO the Canvas course code (ex. SP16-BL-MUS-P110-30862), and this code MUST be used as the External Group's name on the item(s) in MCO.
  3. The user's browser must accept 3rd party cookies, or the user must add an exception to their browser for MCO.
  4. Other steps in the process are outlined in Delivering Avalon Content Through a Learning Management System (LMS)

Mixed Content

Sebastian Bisciglia,, has experience with mixed content in Canvas. He is using iframes to embed MCO items in Canvas simple pages. Since MCO purls are http and Canvas requires HTTPS, he is instead embedding master_files, although they are not permanent like purls. A hidden reference to the LTI tool needs to be added on each page to ensure students will be authorized to access MCO videos while in Canvas.



  • No labels