Building An Application To Simplify Software Inventory

3 min read

In an earlier blog post, we described a process that could be used by schools and districts to inventory the applications used to support teaching and learning. This inventory covered details of contracting, educational rationale for the application, and the privacy implications of the application. Much of this evaluation will be identical across schools, so it doesn't make sense for different schools to sink time into doing indentical work across the country.

Since we put that post out, we have talked a lot internally about what it would require to build that application. We have also talked with educators, administrators, privacy advocates, vendors, and parents about the idea, and have received enough feedback where we don't feel like we are missing anything obvious. To round out the application, we would want to include some information about the text of privacy policies.

Maintenance

  • Date policy reviewed
  • Date policy was updated
  • Date policy was archived
  • Policy copy - text
  • Policy copy - image

The information in this section would allow us to do a few things. First, it would allow people to see how current (or out of date) a review was. Second, if a policy had been updated after a review, that would be a flag that the review was out of date and needed a touchup. Third, the text archives would allow us to maintain a verifiable changelog of policies over time, as policies are often changed with no announcement or explanation. Fourth, maintaining a text version onsite would allow us to automatically check for changes in the policy, which would in turn alert us to the need to revisit or update a review.

When the application was done, schools or districts could pass the application a list of names, and would receive a complete dataset of reviews. As described in our earlier post, they could augment these reviews with the contracting and pedagogical rationale that was specific to their use. However, this application makes it possible for districts to research apps more quickly, and document their technology use more thoroughly.

The project would be built on the following assumptions:

  • Code that runs the site would be open source;
  • Data that is stored in the site would be openly licensed;
  • Compiling the reviews would be the largest initial hurdle. Based on conversations I have had with various schools and districts, though, there is no shortage of people who need this information, and are tackling it on their own. Ideally, we would work with interested partners to help facilitate the review process;
  • Over time, maintaining the reviews will require additional time from people reviewing updated terms and new apps, and people reviewing the reviews;
  • Over time, maintaining the software will require ongoing outreach to make sure that we are measuring things that answer questions people care about (or should care about);
  • Maintaining project infrastructure will also be an ongoing expense.

If you have any ideas/feedback on this, please, let us know.

, ,