Blackboard Course Merges: Process, Requirements, and Limitations

This article outlines the manual Blackboard course merge request process, required CRN information, and limitations of the Banner–Blackboard integration.

🔗 Blackboard Course Merges: Process, Requirements, and Limitations

---

⚡ KEY POINT

Course merges in Blackboard are NOT automated through Banner.
All merges must be requested manually every semester using a Course Merge Request ticket.
Blackboard merges are performed only by CRN, so accurate CRN information is required.

---

📌 Overview

Course merges (also referred to as cross-listings) in Blackboard are not created automatically through Banner. Due to technical limitations in the current Banner–Blackboard integration, all course merges must be requested manually each semester (e.g. ALP courses) using a Course Merge Request.

This article explains:

• Why merges are not automated

• What information is required for merge requests

• How to avoid delays or incorrect merges

---

⚙️ Are course merges handled automatically through Banner?

No.

At this time, IT Ops and the Records Department have confirmed that there is no mechanism within the current Banner–Blackboard integration to send the following to Blackboard:

• 🔗 Cross-listings

• 👥 Cohorts

• 🧩 Parent/child course merge instructions

These actions cannot be sent via Banner or CSV batch file feeds. As a result, Blackboard does not receive merge instructions automatically.

📎 This limitation was reviewed through institutional merge discussions, and no change was made to the existing process.

---

👩‍🏫 What does this mean for faculty and departments?

Because merges are not automated:

• 📝 All desired course merges must be requested every semester (request the merge as soon as you get access to the shells)

• 🎫 A Course Merge Request ticket is required for each merge

• ⏰ Requests should be submitted as early as possible, ideally before the semester begins

Early submission helps ensure courses are configured correctly and avoids mid-semester corrections that may impact students or instruction.

---

📋 Required information for Course Merge Requests

Blackboard allows merges to be completed only by CRN. The LMS Administrator must act strictly on the CRNs provided and cannot infer intent. CRNs can be found in Banner or in your course tile on your Blackboard dashboard under the course name or in the Content Collection. Alternatively you can find the CRN in Banner with your course assignment.

Each Course Merge Request must include:

• 🟢 Parent Course CRN
  (the course students will see and access)

• 🔵 Child Course CRN(s)
  (the course(s) that will be merged into the parent)

• 📆 Semester and year

⚠️ Important:
If incorrect or unintended CRNs are submitted, the merge will be completed exactly as requested. Correcting errors may require a separate unmerge request.

---

🔄 Making changes to an existing merge

If a merge needs to be modified after it has been completed (for example, separating a child course):

• 🎫 A new Course Merge Request ticket must be submitted

• ✏️ The request must clearly specify which CRN(s) should be unmerged

---

📚 Related Resources

• 🔗 CCRI Course Merge Policy
  https://www.ccri.edu/onlinefaculty/tech_corner/merge.html

---

✅ Key reminders

• 🚫 Course merges are not automated through Banner

• 🔁 Manual merge requests are required every semester

• 🔢 Accurate CRN information is essential

• ⏳ Submitting Merge requests early helps avoid delays and corrections