Some ideas of thing that could be shared on HEA for statistics purposes: - adding some statistics like "intranetuserjs yes/no" => yes if there's something, no if it's empty ? (intranetuserjs, opacuserjs, opac & intranet css, opacheader, opacnav, opacbottom). - For sysprefs *XSLT* => we could send "empty/default/local".
*** Bug 23897 has been marked as a duplicate of this bug. ***
Similar sysprefs to consider also. Maybe in a followup bug. AmazonAssocTag IntranetCirculationHomeHTML IntranetFavicon IntranetmainUserblock IntranetNav IntranetReportsHomeHTML IntranetSlipPrinterJS intranetstylesheet OpacCustomSearch OPACHoldsIfAvailableAtPickupExceptions OpacLoginInstructions OpacMainUserBlock OpacMoreSearches OPACResultsSidebar OPACSearchForTitleIn ProcessingFeeNote RestrictedPageContent RoutingListNote SpineLabelFormat XSLTDetailsDisplay
(In reply to Victor Grousset/tuxayo from comment #2) > Similar sysprefs to consider also. Maybe in a followup bug. > > AmazonAssocTag > IntranetCirculationHomeHTML > IntranetFavicon > IntranetmainUserblock > IntranetNav > IntranetReportsHomeHTML > IntranetSlipPrinterJS > intranetstylesheet > OpacCustomSearch > OPACHoldsIfAvailableAtPickupExceptions > OpacLoginInstructions > OpacMainUserBlock > OpacMoreSearches > OPACResultsSidebar > OPACSearchForTitleIn > ProcessingFeeNote > RestrictedPageContent > RoutingListNote > SpineLabelFormat > XSLTDetailsDisplay I don't think we will gain much from sharing these if anything at all and they are all likely to include very library specific information. I think we should not share them.
Empty or 'used' might work, but not sure about the information gain and it might scare people of thinking we share the actual content.
Victor, we don't want more sysprefs. The goal was to double-check, from the whitelist I provided, if they were all valid and relevant: we don't want personal data to be shared. A second pass could be done for the new prefs we added since I worked on this. Don't rethink/redo the whole process please.
(In reply to Katrin Fischer from comment #4) > Empty or 'used' might work, but not sure about the information gain and it > might scare people of thinking we share the actual content. +1