I just mentioned tunings as one example. Of course there could be lots of different attributes of each record. And yes, it would be a relational database. In this example, the index is custom code, with the WordPress template wrapped around it for consistency with the other pages.
My offer is to build something comparable in scope to the OTSFM example, but with different attributes that this site's users would need. I think anyone could use an interface like that without difficulty. I can integrate it with the site if we can define "integrated." As with the wiki, it would be up to the site users to populate the tool with data over time.
I'll take a look at your diagram, but what I'm offering would not be hard to do ... maybe a day's work, which would be a reasonable contribution given all I've learned from this site.
