ucdavis / ucdavis/ipa-client-angular
Pre-req checking
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
From Jeremy:
The was a DSS quarterly chair/director/CAO meeting today.
One item discussed was that the campus is in the process of implementing prerequisite checking through Banner.
Apparently, we have never before actually verified that students meet the prerequisites for the courses they take :-D
Anyway, the Academic Senate has decreed that individual instructors will have the choice on a course-by-course basis of whether or not they want students who do not meet prereqs will be denied registration.
So, it sounds like departments across campus will now need to determine instructor preferences for this purpose . . . which seems a lot like the IPA teaching call.
This probably doesn’t need immediate attention, but it’s something to bring up with the committee and users.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified. Start by consulting the committee and users about whether instructors need a course-by-course prerequisite preference in IPA and how Banner should provide it. Done is a documented, agreed requirement and implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angularjs, javascript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100