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
Created attachment 176577 [details] [review] Bug 23898: Share more data to HEA : test plan It would be nice to get more data about which functionnality are used or not. This could be achieved with sharing some systempreferences. However some of the systempreferences may hold some private information. This patch propose a way to share some syspref usage without sharing their values. Test plan : - apply test patch - prove t/db_dependent/UsageStats.t -> fail - apply code patch - prove t/db_dependent/UsageStats.t -> green Once this patch is applied to a production environment with HEA enabled, more systempreferences will be shared but those which values are meant to be private will only send "Empty" or "Used" value instead of the actual value. This will help the community find out about unused or rarely used functionnality and debug some specific systempreference combinations which may cause an issue. (this commit holds the tests)
Created attachment 176578 [details] [review] Bug 23898: Share new data to HEA Test plan : Apply test patch prove t/db_dependent/UsageStats.t -> fail apply patch prove t/db_dependent/UsageStats.t -> green After patch is applied to a production environment with HEA sharing enabled, more data will be shared to the community. Those data will help us clean some unused functionnality or debug some rare case where systempreferences configuration might be broken.
OpacMainUserBlock is not a system preference anymore