Skip Headers

Oracle® Student Learning Implementation Guide Release 3.1.3 Part Number E21072-04 |
Home | Book List | Contents | Contact Us

Previous | Next
| PDF · Mobi · ePub

# 5 Default Content Integration

There are some different cases where students, teachers, and/or parents need to consume and/or interact with content through the OSL LT. The LT includes APIs that allow an implementation of OSL to build integration with a third-party Content Management System (CMS), to support these use cases. However, as content management is a significant part of LT functionality, OSL provides a default pre-integration with Oracle Universal Content Management (UCM).

## 5.1 OSL Content

"OSL Content" is content that is managed and controlled by OSL. This content is only accessible to OSL users through OSL. It is content that only has meaning in the context of OSL. OSL content includes files and in-line audio recording that are attached to:

- Learning Items (lessons and activities);

- Observations (comments about students); and

- Student Submissions (work completed by students).

The preconfiguration for OSL Content is a technical consideration that is outside the scope of this guide. For more information, see Chapter 6 of Oracle Student Learning Installation and Deployment Guide.

### 5.1.1 OSL Content Use Cases

The OSL Content Use Cases are summarized in the following table.

Table 5-1 OSL Content Use Cases

OSL Content Use Case | Description
--- | ---
Open file | This is where the student, parent, or teacher wishes to open a file that has been attached to an OSL objects listed above. In this case, the attachment behaves as a normal browser link and is handled by the browser on the client. So, for example, if the attachment is an MS Word document: a user on Windows XP using Internet Explorer, may find the document open directly in the browser; Whereas a user on Windows 7 using Google Chrome, may find that the document is automatically downloaded.
Open audio file | This is where the student, parent or teacher wishes to open an in-line audio recording that has been attached to an OSL objects listed above. In this case, the LT displays a Java applet that plays back the audio recording (JRE required).
Attach file | This is where the student, parent, or teacher wishes to attach a file to an OSL objects listed above. In this case, the user selects a local file using the standard operating system's file-browser dialog.
Record in-line audio | This is where the student, parent or teacher wishes to attach an in-line audio recording to an OSL objects listed above. In this case, the LT displays a Java applet that is used to record the audio (JRE required).
Remove Attachment | This is where the student, parent, or teacher wishes to remove a file or in-line recording from an OSL objects listed above.
Upload OSL Content | This is where the student, parent, or teacher wishes to upload a file to an OSL objects listed above. In this case, the user clicks the Upload tab in the RichDataEditor and selects a file using the file-browser dialog. A file is uploaded and displayed along with the rich data text.

## 5.2 General Content

"General Content" is content that is managed and controlled outside of the context of OSL. The interaction of OSL with General Content includes:

- References (hyperlinks) to and images embedded from General content within

  - Learning Items (lessons and activities);

  - Observations (comments about students); and

  - Student Submissions (work completed by students).

- Exporting (publishing) Learning Items (lessons and activities) from OSL into General Content

- Importing (retrieving) Learning Items (lessons and activities) from General Content into OSL

As OSL has no control over this content, it is very much the decision of the specific implementation as to how to configure their CMS for General Content usage.

### 5.2.1 General Content Use Cases

From an OSL perspective, the use cases listed in the following table must be supported.

Table 5-2 General Content Use Cases

General Content Use Case | Description
--- | ---
Open resource | This is where the student, parent, or teacher wishes to open a reference has been attached to an OSL Learning Item, Observation, or Submission. In this case, the reference behaves as a normal browser link and is handled by the browser on the client. So, for example, if the attachment is an MS Word document: a user on Windows XP using Internet Explorer, may find the document open directly in the browser; Whereas a user on Windows 7 using Google Chrome, may find that the document is automatically downloaded. A variation is where the reference is an image that the user chooses to display within the (html) text rather than as a hyperlink.
Find resource | Scenario 1 Where the student, parent, or teacher wishes to find: a resource to reference (hyperlink); or an image to display within the (html) text of an OSL Learning Item, Observation or Submission. Scenario 2 Where the teacher wishes to find a previously exported Learning Item to import into a lesson plan.
Upload resource | Where the teacher wishes to export a Learning Item from OSL into the CMS.
Associate context | This is invoked after the "Find resource" use case. In this case, the OSL context (which object in OSL is referencing the content item) is returned to the CMS.
Disassociate context | The reverse of the "Associate context" use case. This is where the user has removed a content reference in OSL.

### 5.2.2 Default Content Implementation (DCI)

The configuration of General Content is outside the scope of OSL. However, this release provides a default implementation of Oracle UCM 11g for General Content. DCI configurations have been designed to support generic requirements of K-12 education and may be easily and quickly applied. The configuration of the DCIs described in Appendix D.

#### 5.2.2.1 Overview

The DCI provides a simple and effective security and metadata model that makes it easy for administrators, teachers, students, and parents to use the content system. As the DCI is a configuration of Oracle UCM 11g (not a customization) it is possible to modify the DCI configurations (for example, extend the metadata attributes, introduce additional profiles, and so on) to meet specific requirements.From the administrator, teacher, student, and parent perspective, the DCI provides content in two "scopes", Public and School. Public content is accessible to all users of the system, whereas School content is only accessible to members of the school.Administrators can publish any content (files) as "Endorsed" meaning that when a person performs a general search for content he/she will find all endorsed content (Public and School) matching the search term.The DCI provides a simplified "check-in" screen that makes it very easy for administrators and teacher to add files into the content system. Teachers may add both Public and School content but are not able to "endorse" the content (the endorsement must be made by an administrator). Teachers can direct other users (students, parents, teachers, and administrators).

#### 5.2.2.2 Security Model

General content is stored in the default ("Public") security group. Access to documents is controlled through "Document Accounts".

All access to General content from within the OSL LT are performed as the logged-in user.

General content fits one "categories" specified in the following table.

Table 5-3 General Content Categories

Category | Description | Document Account | Metadata
--- | --- | --- | ---
Public | To enable sharing of documents across schools at the grass-roots level. Only teachers and administrators (school or department) can upload documents of this category. The documents are accessible to all users (students, teachers, and parents) but not searchable. Should a teacher wish to make a document searchable, s/he should ask an administrator to update the document Department (Endorsed). | PUBLIC | Scope=Public Visibility=All Endorsed=FALSE Searchable=FALSE
Department Endorsed | To enable the department to publish endorsed documents. Only department administrators can upload documents of this category. The documents are available to and searchable by all users. | ENDORSED/DEPARTMENT | Scope=Public Visibility=All Endorsed=TRUE Searchable=TRUE
School Endorsed | To enable schools to publish endorsed documents to all members of the school. Only school administrators can upload documents of this category. The documents are available to, and searchable by, all members of the school. | ENDORSED/SCHOOL/SchoolID | Scope=[School Name] Visibility=All Endorsed=TRUE Searchable=TRUE
School Unendorsed | To enable sharing of documents within a school at the grass-roots level. Only teachers and school administrators can upload documents of this category (to their own school). The documents are accessible to, and searchable by, all members of the school (students, teachers and parents). | UNENDORSED/SCHOOL/SchoolID | Scope=[School Name] Visibility=All Endorsed=FALSE Searchable=TRUE
School Teacher-only | Same as School (Unendorsed), except that the documents are only accessible to teachers and administrators of the school. | UNENDORSED/SCHOOL/SchoolID | Scope=[School Name] Visibility=Teachers Endorsed=FALSE Searchable=TRUE

#### 5.2.2.3 DCI Metadata Model

The following metadata attributes, in addition to mandatory system metadata elements, are associated with General content resources:

- Scope

- Visibility

- Endorsed

- Searchable

- Tags

- OSL Framework Item ID

- OSL Outcome ID

#### 5.2.2.4 DCI User Accounts

To ensure that students, parents, and teachers can access the correct content categories, they must be allocated with appropriate Document Accounts. The allocation is based on their role(s) as mapped to groups specified in the LDAP directory.

Since DCI security extends to schools, some additional configuration of Oracle Internet Directory (OID) is required for the DCI. This is described in Appendix E.