On this page, we will go into the various project elements, describe them and provide current status.
Please note that date estimates are subject to change and could likely be done sooner than what is shown.
Revised 10/05/2024 11:30 AM EDT
| Underlying build | Building the necessary software that will be needed for the operation of the system. |  |
|---|---|---|
| Drupal 10 install. | Install Drupal 10 core, determine theme and install necessary modules. | |
| Drupal 10 (RECnet.com) | Adding RECnet.com to Drupal 10 multisite. | |
| Interim database connection | Establish an interim database connection between System 40 and the legacy database. | |
| Drupal 10 (RECnet.com) repair | Determining aspects of Durpal 10 that did not properly import from Drupal 7 and facilitating fixes to implement as many features as possible from the previous Drupal 7 build. | |
| PHP8 database interaction | Construct functions that will be used by REC to interact with the database. | |
| Development Standards | Develop standards for re-coding all PHP scripts to be compatible with PHP8 | |
| Toybox application conversion | Modify the source code in Toybox applications (those that reside on the recnet.com Drupal 10 server) to work with PHP 8 and System 40 Development Standards. This also includes the import and creation of any required elements not previously moved over. | |
| GIS server | Move GIS services, DNS and certificates to Sys40. | |
| Icecast | Establish Icecast server and perform operational testing. | |
| Icecast transition | Transition authorized Icecast clients to the new server. (NOTE: REC does not provide streaming services to the general public. There are other choices out there such as Aiir and Cirrus Streaming.) | |
| Perl retirement - phase 1 | Identify all internal back-end applications that were written in perl for conversion to PHP 8. | |
| Lime Survey | Install Lime Survey in the System 40 environment. | Week of 10-6-24 |
| Prepare Drupal 10 | Conduct final testing on the recnet.com and prepare to cut over. | |
| Deploy Drupal 10 | Redefine recnet.com DNS and certificates to transition CMS traffic to System 40. | |
| Legacy Drupal 7 availability. | Establish new domain (legacy.recnet.com) to continue to point to the legacy. Until 100% | |
| Obsolete content | Identify web folders with obsolete content which will not be carried over to Sys40. | |
| Copy website content | Copy all website content from Legacy to Sys40 except for Drupal. | |
| Relay servers | Set relay servers to receive requests from Sys40. (Relay servers are how we talk to the FCC public systems.) | |
| Broadcast support applications | Identify, recode and deploy in System40, various programs that are used by REC to support the broadcast data operation. Does not include eLMS. | |
| J1/DMV/FMR support applications | Identify, recode and deploy in System 40, various programs that are used for website support, on air information and playlist generation for J1 Radio, Delmarva FM and FM Riverton. | |
| Legacy server audit | Review Apache configuration files on legacy to identify obsolete records and plan for overall site map for Sys40. | |
| Subdomain audit | Audit DNS records to identify subdomains no longer being used and remove from DNS. | |
| recnet.net recoding | Update the recnet.net apps (public apps include the spare call sign list) to be compatible with the PHP8 and the new database procedures. | |
| recnet.net cutover | Set DNS and certificates for recnet.net services to Sys40 | |
| International updaters | Data updaters for Canada, Australia, Mexico, UK and Ireland | |
| ULS updaters | Updater programs for the Universal License System to support broadcast auxiliary, ship and coast stations, travelers information stations, antenna structure registration and amateur radio. | |
| IBFS updaters | Updater programs to support the International Bureau Filing System. | |
| LMS Updaters | Updater programs that support the FCC License Management System. | |
| Morning updaters | Other programs that are used to support the morning database updates (except eLMS). | |
| LPFM.us | Transition LPFM.us to System40 | |
| FCC.today | Transition FCC.today to System40 | |
| CountyWar | Transition CountyWar to System40 | |
| FMTranslator.com | Transition fmtranslator.com (static content) to System40 | |
| eLMS directory structure | Establish eLMS directory structure in System40 | |
| eLMS Updaters | Recode and transition eLMS applications that are not involved in application parsing or use storage items not in the SQL database | In progress |
| Prepare eLMS parsers and bots | Pre-code the eLMS parsers and lmslist (bot) to prepare for transition. | In progress |
| Copy eLMS database | Freeze updates into eLMS, copy frozen database to System40 and then resume operations. | Planned for 10/12~13 |
| Finish eLMS parsers and bots | Finish up coding on eLMS parsers and bots and prepare to deploy them. | Planned for 10/12~13 |
| eLMS Dual Operation | Operate eLMS simultaneously from Legacy and System40. Frequency of updates for each system will be reduced to accommodate an overall increase in calls to the FCC. | Planned for 10/12~13 |
| myLPFM.com | Transition myLPFM to System40 | Late October |
| lpfm.ws | Transition lpfm.ws to System40 | Late October with myLPFM |
| lpfm.app | Transition lpfm.app to System40 (as a standalone application) | |
| WIDE-FM | Move searches to the recnet.com toybox and redirect URL to RECnet.com page on WIDE-FM | Week of 10-6-24 |
| Internal Application N01 | Transition Internal Application N01 to System40 | Needs Drupal theme |
| FCCdata.org | Transition FCCdata.org to System40 | Early November |
| Data quality verification | Validate that all dynamic data is properly being handled in Sys40 SQL. | Early November |
| Soft launch System40 database | Change all database source on migrated applications from Legacy to Sys40. | Early November |
| LPFM.wiki | Transition LPFM.wiki to System40 | |
| Restructure Relay Servers | Determine future need for use of Relay Servers in the REC environment and make any changes if necessary. | |
| RadioDNS | Migrate RadioDNS SI server to Sys40 | Late October with myLPFM |
| Migrate DNS | Migrate DNS records to a new provider. | On decision |
| Historical preservation of legacy content | Identify files on the Legacy server that, while not published, may have historical significance. Preserve them through copy to System 40 | Mid November |
| Hard cut of Legacy data | Shut down SQL services on Legacy | Early November with FCCdata |
| Final sweep for Legacy artifacts | Verify one last time that no historically valuable has been left behind. | Mid November |
| Final verification of System40 | Conduct additional final tests on Sys40. | Mid November |
| Shut down Legacy server | Retire Legacy. | Late November |
| Project complete. | Complete System40 project | Late November |
| ALL AGENDA ITEMS AND THE ORDER OF THE SUB-PROJECTS THEY MAY BE HANDLED IN MAY BE DIFFERENT THAT WHAT IS ABOVE. |