when finished use the checkbox!!!

User Story #1: View Summary Table

As a member of the Learning Outcomes Committee (LOC), I can view a summary table/grid for the current year containing all of the project information, so that I can view details at a glance.

Acceptance Criteria #1 – Display Summary Table

• Given I am on the LOC Summary page
• When the page loads
• Then I should see a data grid with the following columns:
  • Division
  • Academic Program
  • Division Chair
  • Dean
  • LOC Rep
  • PEN Contact
  • Payee(s)
  • Has Been Paid (Yes/No)
  • Report Submitted (Yes/No)
  • Notes
• And I should be able to scroll horizontally and vertically through the table if the data exceeds the viewable area.

Acceptance Criteria #2 – Sorting

• Given I am on the summary table
• When I click on a column header
• Then the table should sort data ascending or descending by that column.
• And the active sort column and direction should be visually indicated (e.g., arrow icon).

Acceptance Criteria #3 – Search/Filter

• Given I am viewing the summary table
• When I enter a keyword (such as a Division, Program Name, or Payee) in the search bar
• Then the table should display only rows containing matching results.
• And clearing the search field should restore the full table.

Technical Tasks

• Create a new route or page component for “LOC Summary.”
• Build a responsive data table using a JavaScript framework or library (e.g., DataTables.js, React Table, or plain JS).
• Implement sorting and search functionality using client-side filtering.
• Ensure accessibility compliance (keyboard navigation, readable column headers).
• Validate and test across major browsers and devices.
• Commit changes to GitHub with clear messages referencing Sprint 2.

---

User Story #2: Update Program Information

As a member of the LOC, I can update program information (Academic Program, Payee(s), Has Been Paid, Report Submitted, and Notes), and assign a Division to each program so that I can keep information current.

Acceptance Criteria #1 – Edit Program Information

• Given I am viewing the summary table
• When I click on an “Edit” button for a program
• Then I should see an editable form or inline fields for:
  • Academic Program (cannot be blank)
  • Payee(s)
  • Has Been Paid
  • Report Submitted
  • Notes
  • Division (select dropdown)
• And the fields should be pre-populated with existing data.

Acceptance Criteria #2 – Input Validation

• Given I am editing a program record
• When I leave the Academic Program field blank
• Then I should see an inline validation message: “Academic Program cannot be blank.”
• And I cannot save until all required fields are filled.
• And validation messages disappear once corrected.

Acceptance Criteria #3 – Save and Cancel

• Given I have made changes to a program record
• When I click “Save”
• Then I will see a confirmation message, "Changes saved!"
• And a current timestamp will be captured
• And my data will be saved to an in-memory array
• And the array will be printed to the console
• When I click “Cancel”
• Then all unsaved changes are discarded and the summary reverts to its previous state.

Technical Tasks

• Make an editable table or form
• Add “Edit” and “Save” buttons
• Add input validation rules and messages
• Implement “Save” functionality (data is not actually saved at this point)
• Implement “Cancel” to close the form or editable fields
• Ensure data integrity (e.g., Academic Program cannot be null)
• Add loading or success indicators for save operations
• Test for usability, error handling, and data persistence
• Push all updates to GitHub with detailed commit notes

---

User Story #3: Navigation Between Forms

As a member of the LOC, I can link to the summary page from the Division form (created in Sprint 1), and from the Division form to the summary page.

Acceptance Criteria #1 – Navigation from Division Form to Summary Page

• Given I am on the Division management form (from Sprint 1)
• When I click a “View Summary” button or link
• Then I should be navigated to the LOC Summary page
• And I should see the summary table for the current year

Acceptance Criteria #2 – Navigation from Summary Page to Division Form

• Given I am viewing the LOC Summary page
• When I click on a Division name or an associated “Edit Division” link
• Then I should be navigated to the Division management form

Technical Tasks

• Add a “View Summary” link or button to the Division management form.
• Add a “Return to Division Form” or clickable Division link on the Summary page.
• Implement routing or navigation logic between pages.
• Test navigation in both directions for accuracy and user flow.

---

Definition of Done

• All code is well-formatted, commented, and validated.
• The web app is user-friendly, accessible, and responsive.
• Code is version-controlled on GitHub with regular, descriptive commits.
• Proper error handling and input validation are implemented.
• All pages use consistent styling and naming conventions.

---

Deliverables

• Submit the URL of your web app on Digital Ocean (one submission per team).
• Provide a link to your GitHub repository showing Sprint 2 updates.