Multiple configurations of meetings between the Southeast Comprehensive Center (SECC), REL Southeast, and VirtualSC have taken place to flesh out details needed for VirtualSC database development. Those meetings yielded the following information: SECC/REL Southeast will be populating the database with some starter resources. The database will allow people to continually add resources with a submission form. VirtualSC users with login/password credentials will review and publish approved resources submissions. The following database tags have been suggested by VirtualSC: Grade-level (tag this as “elementary” “middle” or “high” rather than each grade level as previously discussed with SECC/REL Southeast); Course type (tag this as a subject category, such as English language arts [ELA], math, or other subject, no need to be more specific); Type of environment described in the resource (brick-and-mortar, virtual, or blended context); “Includes assessment practices” (yes or no tag); “Includes data from experimental studies” (yes or no tag). We also have learned through communication that the VirtualSC website is running WordPress, so it is a php server with Mysql database; however, they don’t have access to the server other than through WordPress. It may be possible to integrate the resource database into WordPress, use php and mysql, or to ask for permission to upload the data and page to the server, which is hosted by an external vendor, so VirtualSC does not have direct access. It might be possible to pull the resource database into Moodle and house it there, so that VirtualSC leadership staff and possibly teachers can access it, depending on the resources.
In March, SECC and REL Southeast will continue to meet virtually to discuss all of the aforementioned details in efforts to establish next steps for database development and will begin to submit resources as soon as the VirtualSC director approves our forward movement given all of these considerations.
Technological compatibility across SECC and VirtualSC platforms will impact database design, so both entities will continue to plan the design so as to best allow the full operation of the database on a VirtualSC technology platform of choice.