Update main branch with the latest 6.1 release

.editorconfig

@@ -1,9 +1,28 @@
 root = true
 
+[**/*.py]
+file_header_template = SPDX-License-Identifier: Apache-2.0\nLicensed to the Ed-Fi Alliance under one or more agreements.\nThe Ed-Fi Alliance licenses this file to you under the Apache License, Version 2.0.\nSee the LICENSE and NOTICES files in the project root for more information.
+indent_style=space
+indent_size=4
+tab_width=2
+end_of_line = lf
+insert_final_newline = true
+charset = utf-8
+trim_trailing_whitespace = true
+max_line_length = 110
+
+[**/*.md]
+trim_trailing_whitespace = false
 [*.{js,json,yml}]
 charset = utf-8
 end_of_line = lf
 indent_size = 2
 indent_style = space
 insert_final_newline = true
-trim_trailing_whitespace = true
+trim_trailing_whitespace = true
+
+[*.xml]
+indent_style = tab
+charset = utf-8
+insert_final_newline = true
+trim_trailing_whitespace = true

.github/CODEOWNERS

@@ -0,0 +1 @@
+*    @Ed-Fi-Alliance-OSS/ed-fi-tech

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: 🏠 Ed-Fi Community Hub
+    url: https://community.ed-fi.org
+    about: For technical support, questions, and community discussions
+  - name: 📚 Ed-Fi Documentation
+    url: https://docs.ed-fi.org
+    about: Official Ed-Fi technical documentation and guides

.github/ISSUE_TEMPLATE/engineering-issue.yml

@@ -0,0 +1,46 @@
+# SPDX-License-Identifier: Apache-2.0
+# Licensed to the Ed-Fi Alliance under one or more agreements.
+# The Ed-Fi Alliance licenses this file to you under the Apache License, Version 2.0.
+# See the LICENSE and NOTICES files in the project root for more information.
+
+name: "🔧 Engineering Team Issue"
+description: "Internal issue for Ed-Fi engineering team members only"
+title: "Feature: [Brief Description of the Issue]"
+labels: []
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## ⚠️ Engineering Team Only
+
+        This template is for Ed-Fi engineering team members only.
+
+        If you're not part of the engineering team, please use the [Ed-Fi Community Hub](https://community.ed-fi.org) for support.
+
+  - type: textarea
+    id: description
+    attributes:
+      label: "Issue Description"
+      description: "Describe the issue or task"
+      placeholder: "Clear description of the issue..."
+    validations:
+      required: true
+
+  - type: textarea
+    id: acceptance-criteria
+    attributes:
+      label: "Acceptance Criteria"
+      description: "What needs to be done to resolve this issue?"
+      placeholder: "- [ ] Criteria 1\n- [ ] Criteria 2"
+    validations:
+      required: false
+
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: "Additional Context"
+      description: "Any additional information, screenshots, or context"
+      placeholder: "Additional details..."
+    validations:
+      required: false

.github/instructions/actions.instructions.md

@@ -0,0 +1,17 @@
+---
+applyTo: ".github/workflows/**/*"
+---
+
+# GitHub Actions Instructions
+
+- Name workflow files and jobs descriptively and consistently
+- Use environment variables for sensitive information (e.g., API keys, secrets)
+- Reference actions by their full SHA256 commit hash:
+   - BAD example: `actions/github-script@latest`
+   - BAD example: `actions/github-script@v7.0.1`
+   - GOOD example: `actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea`
+- Prefer official actions and marketplace actions with high usage and recent updates
+- Add comments to explain non-obvious steps or logic.
+- Use `if:` conditions to control step/job execution when needed.
+- Always validate YAML syntax before committing.
+- Use caching for dependencies to speed up workflows.

.github/instructions/python.instructions.md

@@ -0,0 +1,49 @@
+---
+applyTo: "**/*.py, **/pyproject.toml"
+---
+
+# GitHub Copilot Instructions for Python Files
+
+## Purpose
+
+This file provides guidance for GitHub Copilot to assist with editing, creating, and maintaining PYthon scripts in this repository, especially within the `eng` directory
+
+## General Guidelines
+
+- **Code Review:** Make only high confidence suggestions when reviewing code changes
+
+## Packaging
+
+- Use Poetry for dependency management
+- Use `poetry.lock` for locking dependencies
+
+## Style and Format
+
+- Apply code-formatting style defined in `.editorconfig`
+- Follow PEP 8 style guide for Python code
+- Use `black` for code formatting
+- Use quotation `"` marks for strings, not apostrophes `'`
+
+## Code
+
+- Include type hints for all function signatures
+- Use absolute imports within the repository
+- Group imports as: standard library, third-party, local application
+- Prefer explicit exception handling and logging for errors
+- Avoid bare `except:` clauses
+
+## Tools
+
+- Use `pytest` for testing
+  - Place all tests in a dedicated `tests/` directory
+  - Use descriptive test names nad group related tests in modules
+- Use `mypy` for type checking
+- Use `flake8` for linting
+
+## Change Management
+
+- Always run flake8 after making changes
+- Use clear commit messages describing the change (e.g., "Add new AcademicHonorCategoryDescriptor.xml")
+
+---
+This file is intended for use by GitHub Copilot and contributors to maintain high-quality Python files in the Ed-Fi-Standard repository.

.github/instructions/xml.instructions.md

@@ -0,0 +1,60 @@
+---
+applyTo: "**/*.xml, **/*.xsd"
+---
+
+# GitHub Copilot Instructions for XML Files
+
+## Purpose
+
+This file provides guidance for GitHub Copilot to assist with editing, creating, and maintaining XML files in this repository, especially within the `Descriptors` and `Samples/Sample XML` directories.
+
+## General Guidelines
+
+- **Format:** Always use proper XML syntax, including opening/closing tags, indentation, and encoding declarations if needed.
+- **Validation:** Ensure XML files are well-formed and, where possible, validate against the appropriate schema (XSD) if available in the `Schemas` directory.
+- **Comments:** Use XML comments (`<!-- ... -->`) to explain non-obvious sections or changes.
+- **Naming:** Use descriptive and consistent names for elements and attributes, following the conventions already present in the repository.
+- **Descriptor Files:** When creating or editing descriptor files, follow the structure and naming conventions of existing files in the `Descriptors` directory.
+- **Sample Files:** For files in `Samples/Sample XML`, provide realistic sample data that matches the schema and typical use cases.
+
+## Best Practices
+
+- **Indentation:** Use the tab character for indentation in XML files.
+- **Encoding:** Default to UTF-8 encoding unless otherwise specified.
+- **Schema Reference:** If a schema is available, include a reference to it at the top of the XML file (e.g., `xsi:schemaLocation`).
+- **Element Order:** Maintain the order of elements as defined in the schema or as commonly used in the repository.
+- **Reusability:** Use reusable elements and attributes where possible to maintain consistency.
+
+## Example Descriptor Structure
+
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<Descriptor xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+            xsi:noNamespaceSchemaLocation="../Schemas/Descriptor.xsd">
+	<CodeValue>Example</CodeValue>
+	<ShortDescription>Example description</ShortDescription>
+	<Description>Detailed example description.</Description>
+	<EffectiveBeginDate>2025-08-15</EffectiveBeginDate>
+	<EffectiveEndDate>2026-08-15</EffectiveEndDate>
+</Descriptor>
+```
+
+## Example XML Comment
+
+```xml
+<!-- This descriptor defines the example category for demonstration purposes. -->
+```
+
+## Directory-Specific Instructions
+
+- **Descriptors/**: Only create or edit files that define descriptor values. Do not add unrelated XML files.
+- **Samples/Sample XML/**: Only add sample data files that are valid according to the schemas in `Schemas/`.
+- **Schemas/**: Do not edit schema files unless specifically requested.
+
+## Change Management
+
+- Always validate XML files after editing.
+- Use clear commit messages describing the change (e.g., "Add new AcademicHonorCategoryDescriptor.xml").
+
+---
+This file is intended for use by GitHub Copilot and contributors to maintain high-quality XML files in the Ed-Fi-Standard repository.

.github/workflows/on-issue-opened.yml

@@ -0,0 +1,72 @@
+# SPDX-License-Identifier: Apache-2.0
+# Licensed to the Ed-Fi Alliance under one or more agreements.
+# The Ed-Fi Alliance licenses this file to you under the Apache License, Version 2.0.
+# See the LICENSE and NOTICES files in the project root for more information.
+
+name: "Issue Management"
+
+on:
+  issues:
+    types: [opened]
+
+permissions:
+  issues: write
+
+jobs:
+  manage-community-issues:
+    runs-on: ubuntu-latest
+    if: github.event.issue.user.type != 'Bot'
+    steps:
+      - name: Check if user has repository access
+        id: check-repo-access
+        uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8.0.0
+        with:
+          script: |
+            try {
+              // Check if user has repository access (collaborator, maintainer, admin, etc.)
+              const { data: permission } = await github.rest.repos.getCollaboratorPermissionLevel({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                username: context.payload.issue.user.login
+              });
+
+              console.log(`User ${context.payload.issue.user.login} repository permission: ${permission.permission}`);
+              return ['admin', 'maintain', 'write', 'triage'].includes(permission.permission);
+            } catch (error) {
+              console.log(`User ${context.payload.issue.user.login} does not have repository access: ${error.message}`);
+              return false;
+            }
+
+      - name: Close community issue with helpful message
+        if: steps.check-repo-access.outputs.result == 'false'
+        uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8.0.0
+        with:
+          script: |
+            const message = `Thank you for your interest in Ed-Fi!
+
+            This GitHub repository is maintained by the Ed-Fi engineering team for internal issue tracking and development coordination.
+
+            For technical support, questions, and community discussions, please visit the **[Ed-Fi Community Hub](https://community.ed-fi.org)** where our community and support team can better assist you.
+
+            The Ed-Fi Community Hub provides:
+            - Technical support and troubleshooting
+            - Community discussions and best practices
+            - Documentation and resources
+            - Direct access to Ed-Fi experts
+
+            We appreciate your understanding and look forward to helping you on the Community Hub!`;
+
+            await github.rest.issues.createComment({
+              issue_number: context.issue.number,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              body: message
+            });
+
+            await github.rest.issues.update({
+              issue_number: context.issue.number,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              state: 'closed',
+              state_reason: 'not_planned'
+            });

.github/workflows/scorecard.yml

@@ -30,12 +30,12 @@ jobs:
 
     steps:
       - name: Checkout code
-        uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
+        uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
         with:
           persist-credentials: false
 
       - name: Run analysis
-        uses: ossf/scorecard-action@0864cf19026789058feabb7e87baa5f140aac736 # v2.3.1
+        uses: ossf/scorecard-action@62b2cac7ed8198b15735ed49ab1e5cf35480ba46 # v2.4.0
         with:
           results_file: scorecard.sarif
           results_format: sarif
@@ -57,14 +57,14 @@ jobs:
       # Upload the results as artifacts (optional). Commenting out will disable uploads of run results in SARIF
       # format to the repository Actions tab.
       - name: Upload artifact
-        uses: actions/upload-artifact@26f96dfa697d77e81fd5907df203aa23a56210a8 # v4.3.0
+        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
         with:
           name: Scorecard SARIF file
           path: scorecard.sarif
           retention-days: 5
 
       # Upload the results to GitHub's code scanning dashboard.
       - name: Upload to code-scanning
-        uses: github/codeql-action/upload-sarif@cf7e9f23492505046de9a37830c3711dd0f25bb3 # codeql-bundle-v2.16.2
+        uses: github/codeql-action/upload-sarif@f443b600d91635bebf5b0d9ebc620189c0d6fba5 # v4.30.8
         with:
           sarif_file: scorecard.sarif