[Koha-bugs] [Bug 23849] Update the list of sysprefs to share with Hea

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23849

--- Comment #21 from Katrin Fischer <katrin.fischer at bsz-bw.de> ---
> == Pretty sure they should be > No ==
> Or just share if it's empty/default or custom.
> AdlibrisCoversURL
> EmailAddressForSuggestions
> ILS-DI:AuthorizedIPs
> NewItemsDefaultLocation
> OpacHiddenItems
> OpacHiddenItemsExceptions
> ReplyToDefault
> RestrictedPageLocalIPs
> RestrictedPageTitle
> ReturnpathDefault
> SelfCheckAllowByIPRanges
> UpdateItemLocationOnCheckin

I'd go for not sharing whenever in doubt. I think they would not gain us much,
but have the potential to make people insecure about sharing when turning up on
Hea maybe?


> == Maybe false positive, could be yes (share) instead of no ==
> OverDrivePasswordRequired
> OverDriveUsername
> NovelistSelectStaffEnabled
> NovelistSelectView
> OAI-PMH:AutoUpdateSets
> OAI-PMH:MaxCount
> opaclanguages
> OpacLocationOnDetail
> OPACResultsLibrary
> RESTOAuth2ClientCredentials
> SyndeticsAuthorNotes
> SyndeticsCoverImages
> SyndeticsCoverImageSize
> SyndeticsEditions
> SyndeticsExcerpt
> SyndeticsReviews
> SyndeticsSeries
> SyndeticsSummary
> SyndeticsTOC

Everything that turns a feature on/off (boolean) is probably ok. Prefs set up
with strings might not be very helpful and more dangerous.

opaclanguages would be interesting to see, but would need some extra processing
as it's a string of language codes separated by pipe - as a string useless,
you'd want to list how often which language is installed.

> == We could just share if it's empty/default or custom ==
> This list will be copied to bug 23898
> AmazonAssocTag
> IntranetCirculationHomeHTML
> IntranetFavicon
> IntranetmainUserblock
> IntranetNav
> IntranetReportsHomeHTML
> IntranetSlipPrinterJS
> intranetstylesheet
> OpacCustomSearch
> OPACHoldsIfAvailableAtPickupExceptions
> OpacLoginInstructions
> OpacMainUserBlock
> OpacMoreSearches
> OPACResultsSidebar
> OPACSearchForTitleIn
> ProcessingFeeNote
> RestrictedPageContent
> RoutingListNote
> SpineLabelFormat
> XSLTDetailsDisplay
> 
> 
> == Not sure, does any know more about these sysprefs? ==
> Can field lists be an issue? They might just be useless actually.
> Or we could just want to know if it's empty/default or custom.
> Precedent: NotesBlacklist is currently marked as > No
> AuthoritySeparator
> BibtexExportAdditionalFields
> ExportRemoveFields
> ISBD
> MarcFieldsToOrder
> MarcItemFieldsToOrder
> MergeReportFields
> OPACISBD
> PatronQuickAddFields
> RisExportAdditionalFields
> StatisticsFields
> SubfieldsToAllowForRestrictedBatchmod
> SubfieldsToAllowForRestrictedEditing
> SubfieldsToUseWhenPrefill
> SubscriptionDuplicateDroppedInput
> 
> Similar doubts as previous paragraph:
> ItemsDeniedRenewal
> LinkerOptions
> MARCAuthorityControlField008
> UNIMARCAuthorityField100
> 
> Are backends lists an issue? Or is it actually very useful?
> ILLOpacbackends

These are not the installed ones, but what works in OPAC, so maybe not.

> Could the directory name be private and thus not sharable?
> intranet_includes
> 
> Could some codes be so rare that they are equivalent of sharing the library
> name?
> MARCOrgCode
> 
> That should be ok right?

The MARCOrgCode is the unique identifier of a library - so it IS equivalent to
sharing the library name. Official MARCOrgCodes can be looked up easily.


> borrowerRelationship
> BorrowersTitles
> 
> 
> == We might want to filter the content of these ==
> To only get Koha's official fields and not custom DB fields.
> They could be ignored now and be in a follow up bug.
> Or we could just want to know if it's empty/default or custom.
> BorrowerMandatoryField
> BorrowerUnwantedField
> DefaultPatronSearchFields
> UniqueItemFields
> 
> Filter to only have Koha's official statues:
> decreaseLoanHighHoldsIgnoreStatuses
> 
> 
> == prefs with > no ==
> They could be ignored now and in a follow up bug, we could share if it's
> empty/default or custom.
> 
> == Maybe a typo in the list ==
> ArticleRequestsMandatoryFieldsItemsOnly
> ↓
> ArticleRequestsMandatoryFieldsItemOnly
> 
> OpacSuppressionByIPRangeµ
> ↓
> OpacSuppressionByIPRange

Where is the typo?

> == Not in the UI (Administration › System preferences) what does it mean? ==
> ElasticsearchIndexStatus_authorities
> ElasticsearchIndexStatus_biblios
> INTRAdidyoumean
> OPACdidyoumean

These are set up on their own configuration pages, but systempreferences is
used for storage. That's why they are not showing in the regular GUI.

> OpacMainUserBlock
> opacheader

Both of those have been moved into News and should no longer be present, where
did you spot them as prefs?

> printcirculationslips

This one has its own bug somewhere I think.

-- 
You are receiving this mail because:
You are watching all bug changes.