Planning Your iTunes U Site

Each iTunes U site, and its structure and content, is organized in an easy-to-use hierarchy of folders and files, or pages and items. As an administrator, you can use this structure as a starting point. Before you start populating your iTunes U site with content, you should take time to further plan your site’s organization, including its structure, user authorization, and access permissions.

To set up and apply user authorization and access permissions properly, you must organize your content into a structure based on the amount of content you will provide and the desired access for your users.

For example, to keep your site and user access simple, you can use the following structure.

Example of a simple, three-level, iTunes U site. Including a root Welcome Page, six Course pages, and three tabs within one of the Course pages.

In this example, you can control user access by providing access to the entire site or restricting access to specific Course pages, or down to individual groups in the English Course page.

If you have more content, or need more restrictive access, the following structure might be more appropriate.

Example of a complex, four-level, iTunes U site. Including a root Welcome Page, two descendant Welcome Pages, six Course pages, and three tabs within one of the Course pages.

In this example, you can control user access by providing access to the entire site or restricting access to a specific descendant Welcome page, specific Course page, or down to individual groups in the English Course page.

You can create pages within your iTunes U site for both private and public content. If your content is for public use, any user can access the page and view and download the information. If your content is for private use, you define a specific group of users who can access the page and how they can view, download, or edit the information. For these users, you must send user information to iTunes U that officially identifies the user’s role and confirms that the user is allowed to access the information. To do this, you create a credential definition identifying the user (for example, the user’s role, attributes, identifier) and assign that credential the page access you want (for example, download, edit, and so on).

Depending on how you want to control access to your site, you can use either:

For more information about user access, actions, and permissions, see “Controlling User Access.”



© 2009 Apple Inc. All Rights Reserved. (Last updated: 2009-11-04)