Change Log

Change Log



The Change Log provides insight into the developmental history of individual syllabi. It provides a chronological record for every current and historical Item. Log entries are produced any time an item is created, modified, reordered, or deleted, and these can be accessed through the course by individuals holding Domain level permissions, via the Analytics tab, and then the Change Log) at the top of each course. The most recent timestamp for each distinct item can be considered the last modified date for that item. The page in question also contains summary statistics and the last modified date for each item on the syllabus, which are arranged in hierarchical order for quick comparison against the syllabus content itself.

 

These records are presented in an on-screen log, and can also be downloaded through our extended .csv. 

 

On-Screen Change Log:

 

Value

Description

Timestamp

The date and time of the change, presented in your default timezone.

Item 

The type of item impacted as well as a unique ID assigned to that item. For example: Meeting Time [ID 0023], Meeting Time Entry [11409]. If an item is deleted and readded, it will receive a new number allowing you to distinguish iterations.


User

The email of the person completing the change or “Automation” if it is a scheduled feed.

Action

Actions are what was done to the item and consist of Add, Edit, Reorder up, Reorder Down and Delete. For file-only syllabi, Upload will be recorded as Add, and Replace will be recorded as Edit.

Method

The method describes how actions in the syllabus were completed. It is important to note that two-step processes, like running a Course Feed or clicking on an LTI which then subsequently Clones a course, will be listed as Feed or LTI respectively since these were the initiating methods. 

  1. Editor: Actions taken from within the UI.
  2. Cascade: Actions initiated from a template (parent syllabus) that impact the syllabus, after it was created. 
  3. Clone: Actions that happen because a syllabus was created from another syllabus using the interface. 
  4. Copy: Actions that happen because Copy (the interface version) was used.
  5. Feed: Actions that originate because of a Feed, including actions typical to another process like Clone, Copy, or Edit. This Method should be interpreted with the Feed Type and Action for full detail.
  6. LTI: Actions that originate because an LTI was launched. Courses Clone because of an LTI will be listed as LTI, not Clone.

Feed 

References the file name when Feed is used, for cross references with the Feed Log, or full Change Log.

Origin 

A hyperlinked title of the course where content originated, if clone or copy was applied.



Extended CSV:

 

Value

Description

Timestamp

The date and time of the change, presented in your default timezone.

Item Class

The type of item impacted. For example: Meeting Time, Meeting Time Entry.

Item ID

A unique number assigned to the item. If an item is deleted and readded, it will receive a new number allowing you to distinguish iterations. 


User

The person or process completing the action;  either the name of the user, or “Automation” if it is a scheduled feed.

Email

If an email is available it will be provided here.

Action

Actions are what was done to the item and consist of Add, Edit, Reorder up, Reorder Down and Delete. For file-only syllabi, Upload will be recorded as Add, and Replace will be recorded as Edit.

Method

The method describes how actions in the syllabus were completed. It is important to note that two-step processes, like running a Course Feed or clicking on an LTI which then subsequently Clones a course, will be listed as Feed or LTI respectively since these were the initiating methods. 

  1. Editor: Actions taken from within the UI.
  2. Cascade: Actions initiated from a template (parent syllabus) that impact the syllabus, after it was created. 
  3. Clone: Actions that happen because a syllabus was created from another syllabus using the interface. 
  4. Copy: Actions that happen because Copy (the interface version) was used.
  5. Feed: Actions that originate because of a Feed, including actions typical to another process like Clone, Copy, or Edit. This Method should be interpreted with the Feed Type and Action for full detail.
  6. LTI: Actions that originate because an LTI was launched. Courses Clone because of an LTI will be listed as LTI, not Clone.

Feed Type

When a Feed is used, this field will list what type of feed was used: Course, Copy, Delete Item, and Item.

Origin File

References the file name when Feed is used. 

Origin Internal ID

A unique number referencing the source syllabus if a source was used; this is relevant for Clone and Copy methods, as well as Feed methods result in Clone or Copy.

Origin External ID

The unique readable name of the source syllabus. 

Origin Course Title

The course title of the source syllabus is one that was used and it is available to display.



System wide aggregates are supplied through the Report Center, allowing System Administrators to see counts of modifications by action and method per course, and counts of action and method per day - system wide. This provides an overview of activity useful for high-level trending. The full log and its accompanying aggregates are also available through a .json output that can be accessed through the Change Log API.  Aggregates will be maintained indefinitely, while log entries will be retained for 180 days beyond the end date of the course, or until the course is purged from your system.


    • Related Articles

    • API - Syllabus Changes

      FYI: All lines within code blocks are numbered, regardless of whether there is more than one line of code provided. An API is available to retrieve statistics related to edits made to syllabi. This is helpful for integrating Concourse with other ...
    • Last Modified

      Concourse provides a modified date for every course, as well as a date and time for each individual syllabus item. The course-wide date is listed at the top of each Syllabus as “Modified.” Item last modified details are available in the Syllabus ...
    • API - General Usage

      FYI: All lines within code blocks are numbered, regardless of whether there is more than one line of code provided. An API is available to retrieve certain data stored by Concourse. This article covers documentation related to the initial version ...
    • Troubleshooting Feed Errors

      Feed processing involves populating and/or synchronizing data that is maintained by an external system. Feed processing can be used to migrate data from one system to another, such as populating syllabus item information like course descriptions or ...
    • API - Syllabus Access

      FYI: All lines within code blocks are numbered, regardless of whether there is more than one line of code provided. An API is available to retrieve statistics related to views of syllabi. This is helpful for integrating Concourse with other systems ...