Comment 1 for bug 1423344

I would strongly prefer this go into the database, obviating the opensrf.xml bits altogether. Your third example is very nearly there, but is bib-specific. That could certainly be generalized to support general more cases, though.

If you agree, and start down that road, I would recommend making your config.added_content_provider table a reusable primitive, and allow multiple owners to map settings to their chosen provider.