Mapping and LOs: A walkthrough the order of operations

The Course Outcomes Report might be able to provide you with the general information you need to review the CLO/PLO alignment.

 

The order of your next steps depends largely on if your LOs will be built on your CLOs or your Bundles. As a reminder, you can enter LOs on either layer of the course, and sort orphans on the opposite side. We do recommend, if possible, creating them on your CLOs, since those objects already exist. 

 

Step 1: Add your LOs to each CLO bucket using the "Add Multiple" panel:

 

 

Step 2: Review the result of adding LOs. The first LO in the list will take on all the mapping that was formerly attached to the empty CLO. 

 

 

 

Step 3: For easiest remapping, enter into grid view. Once your LOs have been added, the outcome will have a light gray background and a dark blue check: this indicates partial mapping. To map everything inside, click the box at the intersection of the CLO and the PLO, and it will automatically map everything inside. 

Before mapping everything in CLO1 to PLO1:

After mapping everything in CLO1 to PLO1:

From grid view, users can easily toggle between outcome sets and courses as needed.

 

 

Step 4: Create your Bundle layer objects and sort orphans on that layer.

 

 

 

If you are creating on the Bundle layer, the steps are very similar, with a shifted order of operations:

• Step 1: Create your Bundles
• Step 2: Add all LOs inside your Bundle objects
• Step 3: Sort orphans on the CLO layer. In this approach, the mapping would still migrate to the very first orphan LO that is sorted into the CLO. 
• Step 4: Map newly added LOs in grid view.

Please keep in mind that once your very first LO is added to an empty CLO, all mappings will move with the LO itself, so if you move or delete an LO out of a CLO, the mapping will go with it. One possible safety guard is to create a placeholder LO. Only if you think this is necessary, you could create a placeholder in each CLO (as the first LO in the object) with a reminder to not delete it until all the other LOs are sorted and mapped appropriately.