Frequently Asked Questions

We're always here to help you troubleshoot, but if you'd like to check for yourself, these are the most common reasons why you don't see the visualization on a degree plan:

• Is the file in .csv format?
• Did you use our example file so that the headings for the columns are matching to what our system needs to read it?
• Are you uploading a curriculum file to the curriculum page and a degree plan file to the degree plan page?

If you answered yes to these questions and are still experiencing issues, please email us at help@damoursystems.com and we will get back to you shortly.

A requisite cycle occurs when two courses both list the other course as a corequisite or strict-corequisite. Essentially, it creates an infinite loop, or "cycle", in the graph. This prevents us from calculating metrics and generating visualizations.

To fix a requisite cycle simply remove one of the corequisites. For example: Course A lists Course B as a corequisite, and Course B also lists Course A as a corequisite. This can be visualized as Course A <---> Course B.

To remove the cycle, only one course should list the other as a corequisite. This can be visualized as either of the following:
Course A ---> Course B
or,
Course A <--- Course B

A key error is most often followed by a number.

For example, you see the message: Key Error: key22 not found.
This means that in your CSV file, the course with an ID of 22 has an error associated with it. Usually it's a place where the course is referenced, such as in the list of prerequisites.

Let's say there is a course with ID 29, and it has a prerequisite of course ID 22. It's possible that after reviewing the file you notice there is no course with ID 22 listed (either it was omitted or the prerequisite was entered incorrectly). If you are still having issues understanding a key error, please reach out to us at help@damoursystems.com and we will get back to you shortly.

For the purpose of computing the complexity of a curriculum, OR relationships are usually irrelevant. All that matters is that you place one of the two courses belonging to the OR relationship into the curriculum so that the prerequisite structure is captured in the curriculum graph.

Caveat: If the two (or more) courses involved in the OR relationship have their own prerequisites, and these prerequisites differ, then there is the potential that the course you choose to include in the curriculum will slightly change the overall curricular complexity.

In this case, the complexity of the curriculum is actually a range, and not a single value. To determine the range, simply create a different curriculum for each of the possible selections of the OR’ed prerequisites that lead to differing curricular complexities; the minimum and maximum curricular complexity values obtained will give you the curricular complexity range for the curriculum.

An elective can be filled by some number of possible courses, so the complexity of the curriculum may vary depending on requisites of the chosen courses. For this reason, an elective can be treated as a normal course with no requisites, and each is often 3 hours. In this case we recommend creating “Business Elective 1”, “Business Elective 2”, etc until the total number of hours are filled.

Alternatively, you can choose the most common courses taken to satisfy the electives, and this will give you an idea of the pathway and complexity that “most” students are following.

Some core requirements, like humanities, may have long lists of available courses. In a case where a core requirement does not have a specific course required in the curriculum, you may use a general term like "Humanities Core Requirement 1", "Humanities Core Requirement 2", etc.

Other core requirements have a specific course to fulfill that requirement, for example every student may be required to take US History, HIST 101. If this is the case, please use the specific course that is required instead of a general name, such as "History Core Requirement".

Finally, core requirements under a specific curriculum may utilize one specific course of a list to complete the Core Requirement. For example, a social work curriculum may require Introduction to Social Work, SW 101, and that may complete the Social Science Core Requirement. In that case, list the course "SW 101" instead of something more generic like "Social Science Core Requirement".

Each complexity score is relative to the program and institution. If you are interested in how your Accounting program score compares to others, you can use the website to review other Accounting programs. Generally speaking, however, there is no "magic" number to achieve or scale to compare.

For more information regarding this topic and many others related to the project, this Youtube video is an excellent source of information: (https://www.youtube.com/watch?v=Ou5h0tg-5q4) Some of the questions during the video are helpful in the metrics and how they are calculated.

This is being done for a number of reasons, including:

1. After receiving favorable reviews from the APLU, The Association for Undergraduate Education at Research Universities, and others, a large number of users have uploaded their curricula to the site.  The simple navigation structure we initially provided does not allow one to easily organize, find, and view these curricula.  In addition, the underlying database technology does not support the level of usage the site is now receiving.  Thus, we have completely rebuilt the web application in order to address these issues, and to add enhancements.
2. We have learned a lot more about curricular analytics, and we have built a number of exciting new features into the new web application based on our evolving knowledge.

The primary improvements are in the areas of:

1. User Management. If there are multiple people from your organization using this application, you can now combine them within a single organizational structure that may contain sub-organizations.  Thus, you can now create and organize users within an organizational structure that matches your institution, e.g., university -> colleges -> departments.  You can also create an organization to house curricular studies involving other institutions, etc.
2. Support for Curricula and Degree Plans. A clearer distinction is now made between a curriculum, and the different degree plans that can be created to satisfy a curriculum.  Specifically, a curriculum is the set of courses in a degree program, along with the prerequisite arrangements between these courses.  A degree plan is a term-by-term arrangement of the courses in a curriculum.  Conceivably you can now create a different degree plan for every student pursing a particular degree.
3. Metrics. Additional metrics have been created that allow you to analyze both curricula and degree plans in order to support data-informed decisions.  These metrics are computed using a curricular analytics statistical toolbox, and to support transparency of our methods, the toolbox is available to institutional researchers as open source software.
4. Visualization. An improved user interface is now available for viewing and editing curricula and degree plans, and for viewing the metrics associated with curricular and degree plans.
5. Extensions. In the future we will be providing a number of extensions that will take advantage of new the infrastructure that now exists behind this web application. These will include:
   • The ability to more easily compare and contrast curricula and degree plans.
   • The ability to create degree plans optimized around particular requirements or student characteristics. Advisors will also be able to easily create degree plans by merging two curricula, e.g., a major and some minor, a double major, a 2-year to 4-year transfer plan, etc. (Note: because this feature will use a commercial optimization package, there will be a small fee associated with this service.)
   • The ability to perform what-if analyses, e.g., “What effect would improving the pass rate in this gateway course by 5% have on our 6-year graduate rate?” (Note: because these analyses require significant computational resources, there will be a small fee associated with this service.)

If you would like to serve as a beta-tester for any of these services, please send a request using the subject “Tester” to: help@damoursystems.com.

Simply log in using your old username and password, and you will be presented with a dashboard organized around these new features.  If you can’t remember your password, there are now “forgot my password” as well as “change my password” options.