INCLUDES ALL PIECES OF INSTALLATION TEMPLATE, CROSSED OUT IF NOT USED
Tool Search: Federal/State Program Updater
Introduction
{LABELING THIS SECTION FEELS UNNECESSARY}
SAME INTRO TEXT FROM HOW-TO GUIDE SAMPLE ARTICLE
The Federal/State Program Updater (FSPU) allows State Edition and District Edition users to import federal or state program participation data using an import file. Users can also add, edit, or delete federal or state program participation data using an Ad hoc filter.
Records can also be imported for Attendance Recovery (AR) using the same file used when requesting new SSIDs, a current Ad hoc filter, or another file that includes the student's SSID.
Use this tool to:
- Create Attendance Recovery Program records.
- Add Attendance Recovery Program Services records for Days Used.
- Add Attendance Recovery Program Services records for Hours Earned.
The FSPU can be used to add and maintain Attendance Recovery records when using the manual process to manage records, particularly when program attendance for recovery programs is recorded outside of Campus.
The import can be run daily (consider creating a daily task using the Task Scheduler). Every time the import runs, the total hours earned for students are updated.
Installation types
This guide explains the steps and instructions required to install {product name} on supported operating systems. It also explains how to configure, start, and uninstall {product name}}.
{Include a table to capture the different installation types, such as:
Supported operating systemsThe type of product installed (if provided in different versions, such as Main and Lite version)Cloud providers, such as CodeSpaces, CodeSandBox, GitPod, etc.,) including a link to the right heading for all options.}
Overview
{This section is optional.}
{Add a list of the available project versions, link to the installation guide for that version, and highlight the latest, beta, or stable version as listed in the following table:}
{Explain the intended result of the installation, such as the commands, command aliases, major flags, available plugins, files downloaded, or application programs.}
{Add a sequential end-to-end summary of the installation process that can serve as a quick link or reference section for users as listed in the following table:}
System requirements
{Start by breaking this into sub-sections based on the number of installation types (product type, operating system, or cloud-especially for projects that require self-hosting to work). Based on your use case, you can use this section reversely by having the installation type as the heading and system requirements for that type as a sub-section.}
{Mention for all installation types.}
Before you begin
SAME AS BEFORE YOU START? CURRENT HTG TEMPLATE DOESN'T HAVE INTRO SENTENCE TO BEFORE YOU START, BUT CONCEPT IS THE SAME
Before installing {version number}, ensure you have:
- Review the Federal/State Program Updater article for a general understanding of the tool.
- See the Federal/State Program Updater Tool Rights article for details on available tool rights.
- Create a list of students who require Attendance Recovery Program records and/or have existing Attendance Recovery records. This can come from the Filter Designer, the SSID file, an existing Google Sheet, or an Excel file. Verify the list of students includes their SSID.
{Include prerequisites for all installation types.}
ABOUT INFO FROM INSTALLATION GUIDE TEMPLATE
ABOUT INFO FROM HOW-TO GUIDE TEMPLATE
Installation steps
The following procedure explains how to use the Federal/State Program Update to create Attendance Recovery Program records for students.
Every student can be assigned an Attendance Recovery Program record without that record affecting reporting. Attendance hours are not reported on the Program record; the hours are recorded on the Program Services record.
Step 1 - Select Program and Mode
- Select Attendance Recovery from the Select Federal Program dropdown list.
- Select Import File: Add/Edit Participation from the Select Mode list of radio buttons.
- Click Next.
Step 2 - Create a New Import Mapping
- Click New. An Import Options modal displays.
- Enter the Mapping Name that identifies what is included in the mapping, e.g., Student Attendance Recovery Program Records 011426.
- Select the correct file type in the What is the file type? Options are Comma Delimited or Tab Delimited.
- Select the correct identifier for the records in the What identifier(s) in the import file will be used to match to students? Options are State ID, Last Name/First Name/Birth Date, or Person ID. Best Practice is to match to the student's State ID when possible.
- Mark the remaining checkboxes when your file includes the following:
- Source File includes a header row
- Overwrite existing data
- Auto-end overlapping records
- Click Save. The import record is available in the Saved Import Mappings window.
Creation of a new import mapping Step 3 - Upload the Source File
- Click Browse to locate the source file to import on your device.
- Select the file from your device location and click Open on the File Upload window. The selected file is listed next to the Browse button.
- Click Next to map the fields in the source file to the saved import mappings.
Step 4 - Map the Import Mapping to the Source Fields
When you created the Import mapping, you chose how to map the data to the selected students. Now you are going to use that entry to test and eventually import the data in the source file to create Attendance Recovery Program records.
FSPU - Mapped File Data Column AssignmentThe columns from the source file are displayed in the Import Data File Sample (see image above), with each column from that file assigned a corresponding number.
- Enter the column header name from the import file that contains the student identifier. For the field name State ID, select SSID from the Column in Import File field. That field is then displayed in the Mapped Fields window.
- Enter the column header name from the import file that contains the student's Start Date. In this example, the start date is column 8.
- Date fields need to be mapped to a specific format. After selecting Start Date in the Column in Import File field, click Map Field. Select the Date Format in the Start Date Field Map modal. In this example, the date format is MMDDYYYY. Select that option from the dropdown field and click Save. That field is then displayed in the Mapped Fields window.
That's not the end, but we get it.
It's OWL great!
Verify installation
{Include test commands, intended outputs, or other steps to confirm the installation was successful.}
Post installation
{Provide an overview of options or link to other relevant documentation once installation has been completed. Also, account for anticipated problems during or after installation.}
{Optinal: include short introduction text.}
Configuration options
{Provide information regarding post-installation configuration options.}
{Describe the requirements for configuring the installed product.}
{Link to relevant documentation if needed.}
Upgrade options
{Provide information regarding upgrade options, also known as an update options.}
{Describe how to install updates from a range of possible options.}
{Provide a link to available updates with specific version numbers, release dates, and key features.}
Example: To begin the system updates:
- Choose the version number.
- Download the update at link.
- Double-click the update file.
- Additional steps as needed.
Downgrade options
{Provide information regarding downgrading the version installed.}
Uninstallation options
{Provide information regarding uninstalling the product, software, SDK, package, library, framework installed.}
Troubleshooting
THIS SECTION FEELS HELPFUL. WE MAY NOT ALWAYS HAVE INFO TO PUT HERE
{This section helps solve problems encountered during installation. Start with a problem statement, then indicate the cause(s) and provide a solution. Additional information can be added (e.g., restart the computer)}.
{Add a warning note and highlight in color if the action has the potential to affect security.
Communicating with the product engineers and programmers is essential to keep this section up-to-date.}
{Problem title: ...}
{Optional: More details about the problem.}
{Optional: More details about the cause(s) of the problem.}
Solution: {Solution to the problem...}
Contact: {Support/contact information for issue reports and feedback...}
{Problem title: ...}
...
Next steps What's next?
- Create Attendance Recovery Program Services records for Earned Hours and Days Used.
- .sdfsd
Product version history
{History section with major changes to the installation guide tabulated following the Major.Minor.Patch semantic versioning specification.}
Definition of terms
{Optional: Provide a glossary table describing the terms, acronyms, and abbreviations used in the installation guide.}