Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Individualized Evidence Requirements (ERs) #618

Open
tgaffey opened this issue Oct 14, 2021 · 0 comments
Open

Individualized Evidence Requirements (ERs) #618

tgaffey opened this issue Oct 14, 2021 · 0 comments
Labels
C-feature Category: New functionality or behavior

Comments

@tgaffey
Copy link
Contributor

tgaffey commented Oct 14, 2021

Each portfolio has specific requirements that need to be fulfilled before the system will “flip” the portfolio. There are two places the evidence requirements are set. First is in the CBL Maps Connector which allows you to upload a google sheet and the system ingests the file. Despite the connector saying that you can update maps, you can only add new competency areas. The second area is a Manage interface called CBL Skills. This is a very rough interface that was always intended to be used to add or edit Area, Competencies, and Skills. Currently, you can only change the language of the skills and update the Evidence Requirements.

These (ERs) are stored in the database tab cbl_skills as a JSON object.

This means that once you change ERs, that is now applied to all students.

Our schools need the ability to customize ERs for certain students: Students with IEPs; Students with 504 plans; Transfer students that come in with credits from their previous school.

It would be great if we could create some kind of child table to store individual ERs for specific students. All students would default to the table above as long as they dont have a copy in this new table.

@holly-g holly-g added the C-feature Category: New functionality or behavior label Nov 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-feature Category: New functionality or behavior
Projects
None yet
Development

No branches or pull requests

2 participants