# data[].attributes.body
March & April: Dev Work

May 21: Audit Tool Demo (Audit Notes Linked)

July 14-18: Course Preferencing Ends

July 14-18: Prague Summit

July 21: Schedules Begin Running

July 28: SJM Audit Workbooks shared

Aug 8: Schedules Finalized

Aug 12: Schedules Released to Students

# data[].attributes.headline
ADAMs took vacations and relied on Ops Specialists to complete work while they were away

# data[].attributes.subject
ADAMs took vacations and relied on Ops Specialists to complete work while they were away

# data[].attributes.body
It was great to know what Chris was working on and provide him with feedback

# data[].attributes.body
Tool tailored to the needs of the process.

# data[].attributes.body
Active feedback in the Slack channel made it easy to capture notes and updates for future updates to the Schedule Audit Tool

# data[].attributes.body
For auditing, the spreadsheet with Preferences vs Enrollment was helpful in making sure students got most, if not all, of what they wanted

# data[].attributes.body
It was amazing to be able to learn how to play with the schedules. Also having your boss in vacation and not being able to ask for help was great at developing independence. The tool itself was perfect for making an idea on how the schedule would look like.

# data[].attributes.body
First set of schedules created by the system granted around 74% of primary selections If I am remember well).

# data[].attributes.body
It was great to see all the information about the specific student in one place (no more changing screens, looking for the registration guides, students' preferences, etc.). It was great to see the schedule graphically (goodbye printed timetable and buttons).

Adding and removing courses was supereasy and superfast.

# data[].attributes.body
Having a student summary with channel reqs and placement scores, plus the visual display of how each course transfers

# data[].attributes.headline
Split / not connected lec and lab sections (STEM)

# data[].attributes.subject
Split / not connected lec and lab sections (STEM)

# data[].attributes.body
It would have been better if lec and lab sections are paired (as we do not do inter-section enrollments)

# data[].attributes.body
It was great to have this as a backup - helped us check that we really audited all the students especially as some of the filters in the new tool were off.

# data[].attributes.body
As locations grow on course offerings and Faculty needed, it is extremely hard for ADAMS to be present during this process.

# data[].attributes.body
Still helped give a quick overview that students were meeting credit requirements and were correctly enrolled in correct courses

# data[].attributes.body
The new schedule building tool did not place students in two AAU courses which made our lives much easier than last year.

# data[].attributes.body
Clear templates for notes within the tool.

# data[].attributes.headline
The section and seat remaining be made visible

# data[].attributes.subject
The section and seat remaining be made visible

# data[].attributes.body
The system does not display the section and the seats remaining until after students are added into the class/es. It would be more helpful if the information is visible right away.

# data[].attributes.body
Previous notes were erased if made by the same user

# data[].attributes.body
the audit tool didn't took in consideration the minimum 15 minutes gap that is necessary to arrive from our center to AAU

# data[].attributes.body
he tool did not work with the 15 minute transfer time between AAU and study center, we had to check everything manually.

# data[].attributes.body
Some improvement to the visual display and basic information about course sections needs to be made: number of seats available and section number, as well as a color marker if a student's schedule has been completed or not in the left menu.

# data[].attributes.body
ex. Course enrollment going from 15 to 17 after adding only one student

# data[].attributes.body
When we tried to filter students from a partner, the list was not complete - we used the Audit Sheet to make sure everyone's schedule was checked

# data[].attributes.body
The tool was choosing to include an A2 over a P1 in some cases, it would have been easier if the tool would focus more on primaries.

# data[].attributes.headline
Sometimes the tool duplicated a class for a student

# data[].attributes.subject
Sometimes the tool duplicated a class for a student

# data[].attributes.body
Sometimes a student was automatically enrolled in the same course in two different sections

# data[].attributes.headline
Course ranking in order of interest should be more clear to students. 

# data[].attributes.subject
Course ranking in order of interest should be more clear to students. 

# data[].attributes.body
The tool created 15-credit schedules even when the university requirement is 12. Our sections are very full, we'll see what happens during Add/Drop.

# data[].attributes.headline
The notes section does not get refreshed

# data[].attributes.subject
The notes section does not get refreshed

# data[].attributes.body
Auditing a new student's schedule does not refresh the notes page - it still contains the same information from the last student audited

# data[].attributes.body
Some universities had a long list of electives, and some students still selected the courses that were elective as their option. It would have been easier if the students were informed that electives are not transferable most of the times.

# data[].attributes.body
As the section information are not displayed until students are already added to the class, there were times the sections were overenrolled. Undoing it consumes much needed time.

# data[].attributes.body
Not knowing if students should be enrolled in MATH 1117 or MATH 1118 without going deeper into individual eligibility records

# data[].attributes.body
There were a few students who did not select any AAU course (always mentioned in the Notes and in the Audit Sheet). We added them to an AAU course manually.

Maren suggested this is because they saved their course selection for later and when they never updated, the tool just showed their primaries and alternatives as they were.

# data[].attributes.headline
Revisit guidelines for how to build schedules

# data[].attributes.subject
Revisit guidelines for how to build schedules

# data[].attributes.body
Different approaches to selecting what courses needed to go into a schedule v. what did not. Norm on whether its ok to give a student a schedule of all electives if that is what they choose, etc.

# data[].attributes.body
make the tool be able to identify all the specific needs for a specific hub.

# data[].attributes.headline
Remove the 15-credit enrollment preference of the system

# data[].attributes.subject
Remove the 15-credit enrollment preference of the system

# data[].attributes.body
The system somehow auto-enrolls students in 15 credits, even if their channel req is just 12.

# data[].attributes.headline
Baskets of courses based on location/areas of interest

# data[].attributes.subject
Baskets of courses based on location/areas of interest

# data[].attributes.body
Re-iterating from Course Preferencing. If we can cut down on the options/have standard options across all locations (all students enrolled in ENGL 1112, enrolled in a math class, etc.) that may cut down on complexity

# data[].attributes.body
Add an option for students whose schedules were not checked yet so we can filter complete, preliminary complete, flagged, and something like "untouched". It was difficult to know whose schedule wasn't audited. We used the Audit Sheet to doublecheck

# data[].attributes.headline
Asking the tool to design the best schedule for a big group of students and not an average schedule for all of them that might not meet their preferences

# data[].attributes.subject
Asking the tool to design the best schedule for a big group of students and not an average schedule for all of them that might not meet their preferences

# data[].attributes.body
Would it be useful to make the tool design the best possible schedule only for a selection of students and do the rest manually according to students' preferences? I had the feeling that all students could have better schedules and that all were eventually edited. Maybe this would reduce the amount of work and still guarantee best schedules for everyone.

# data[].attributes.body
Two weeks seem too short for such a Herculean Task