Comment 7 for bug 1861239

If we were adding the data as a new feature I would agree that inclusion should be opt-in. In fact I wish that had been the case. However, when there is an existing feature with an existing behavior my opinion is that we should be as least disruptive as possible. The scenario of the data being required for state reports and funding being at risk when a library/libraries doesn't realize it's missing for an extended period of time after an upgrade is the kind of possibility that Anna is mentioning. I don't think we should ignore that.

All of that said I'll be glad to write something up for release notes that says in screaming caps "hey, if you don't need it turn this off" and we can provide recommended SQL for people to wipe what is there.