Performing Department
Family & Neighborhood Life Institute
Non Technical Summary
Clemson University's Youth Learning Institute (YLI) proposes to host and maintain web-NEERS v1.0 (WNEERS1) as well as begin work on web-NEERS v2.0 (WNEERS2) to be released in 5 years. YLI will provide, maintain and update servers to house the WNEERS1 project, and will provide support and training to NIFA staff. During the hosting and maintenance phase, YLI will be responsible for maintaining the code repositories, making changes as needed and ensuring that WNEERS1 is reasonably available for EFNEP reporting needs. This phase of the project will not involve creating any new features for WNEERS1, instead YLI will focus on keeping the reporting system online with as few outages in service as possible. During this time, YLI will be responsible for keeping various federal databases updated in the system. Development of WNEERS2 will begin simultaneously with the release and maintenance of WNEERS1. To begin development of WNEERS2 a work/advisory group with multi-state and federal members will guide and direct the YLI team during all project phases, helping to assure that the system will support current and future evaluation and reporting needs, and will synchronize with other data collection systems. Utilizing the work/advisory group recommendations, recommendations from previous work groups, and from system users, the development team will develop new features and redevelop old features to create an even more robust product.
Animal Health Component
(N/A)
Research Effort Categories
Basic
(N/A)
Applied
100%
Developmental
(N/A)
Goals / Objectives
Objectives and Procedures: The specific aim of this project is best divided into two distinct components: 1. Updating and Maintaining webNEERs version 1.0 (WNEERS1). 2. Designing, developing and testing webNEERS version 2.0 (WNEERS2). Year 1-5 Objectives WNEERS1 Support NIFA staff in operation and management of reporting system Maintain and update servers used to house and create EFNEP reports / data. Provide bug fixes and general maintenance of WNEERS1. Analyze WNEERS1 usage and provide load balancing on servers to ensure best possible user experience. Work to ensure servers and running and available for the maximum possible time. Update databases (excluding food or nutrition) and provide to EFNEP institution staff. Year 1 Objectives WNEERS2 Work with NIFA staff to determine direction, goals and scope of WNEERS2. Analyze system requirements and map content elements in cooperation with CSREES and the development/advisory committee Initiate development and testing, while maintaining program code and documenting all project development components and system maintenance procedures Year 2 Objectives Work with NIFA staff to continue to describe goals, taking into consideration user reports from WNEERS1. Begin development of WNEERS2 using the direction and guidance provided by NIFA staff. Continue to maintain program code and documentation of all project development components and system maintenance procedures Year 3 Objectives Continue development of WNEERS2, continue to document and store program code. Complete a functional beta test of system improvements. Begin in house beta testing, working to minimize bugs and other issues before being released to a group of beta testers. Year 4 Objectives Begin beta testing with EFNEP state staff, working to finalize WNEER2. Begin discussions related to securing additional funding and support Year 5 Objectives Develop User manuals and other documentation to be turned over to NIFA staff. Complete Beta testing, and WNEERS2. Release WNEERS2 to EFNEP staff. Begin work on WNEERS3
Project Methods
The CNE Logic Model depicts a broad continuum of intervention strategies at the individual/household, community/institution, and social structure/policy levels. The specific aim of the project was to design, develop, test, and implement a functional, secure, and user-friendly web-based EFNEP information system that will support local, university, state, territory and federal evaluation and reporting needs, align with the CNE Logic Model, and will synchronize with other agency and university data collection systems. We believe that, through a systematic and comprehensive process, we have developed a web-based evaluation system that will meet our current and future programmatic needs. It is important to document program performance that will provide essential assessment data that can inform the development of program policies and procedures, and provide needed information for intervention planning. We need to continually evaluate the web-NEERS to see if it meets programmatic needs. This project has involved a high level of interaction among EFNEP staff and information technology (IT) personnel at the federal, university, state, and territory level. The multi-state-federal partnership approach has enabled us to comprehensively address complex programmatic issues. We formed a multi-state development/advisory committee that served in numerous capacities, including: (1) determining system functionality and usefulness; (2) helping to ensure that the new NEERS system was not driven not by current needs, but by future needs of EFNEP and like organizations; (3) helping to better format data reports; (4) making recommendations on how to align the EFNEP reporting system with the indicators in the CNE logic model; (5) helping IT/Developers better understand the needs of any new NEERS system and its users; (6) Keeping development team informed on new research related to EFNEP-related evaluation methodologies and outcomes assessment, as well as national nutrition, physical activity recommendations and guidance systems; and, (7) Helping to develop a user-friendly graphical user interface that is similar in function and style to that of the NEERS5 system. Input from Coordinator (consultants), system users, and a "Behavior Checklist" work group and a "Youth Evaluation" work group have provided valuable contributions to the design, development, and testing processes. Evaluation of the web-NEERS system to ensure that the new system meets programmatic needs is a critical component of the development process. We will need to assess if the new system enables us to compile data and reports that will be useful, practical, and relevant. We will continue to work with the advisory committee, work groups, and other groups/individuals as we evaluate, refine, and maintain the system.