Bug 9015

Summary: BiblioAddsAuthorities should probably be set to "allow" by default
Product: Koha Reporter: normalina <normalina>
Component: CatalogingAssignee: Galen Charlton <gmcharlt>
Status: RESOLVED MOVED QA Contact:
Severity: enhancement    
Priority: P5 - low CC: katrin.fischer, m.de.rooy, mkstephens
Version: Main   
Hardware: All   
OS: All   
See Also: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30025
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:

Description normalina 2012-11-07 06:22:16 UTC

    
Comment 1 Jared Camins-Esakov 2012-11-07 11:17:12 UTC
If you set the system preference "BiblioAddsAuthorities" in the Authorities tab to "allow" you will be able to edit the 100 fields.

Since this is a common point of confusion for new Koha users, I suggest it might be a good idea to change the default.
Comment 2 Myka Kennedy Stephens 2024-03-08 14:44:17 UTC
I'm doing some research on authority bugs and ran across this old one. There isn't a syspref called "BiblioAddsAuthorities" anymore. Based on the description in this bug, I'm guessing this syspref was rendered unnecessary by AutoCreateAuthorities and RequireChoosingExistingAuthority. 

Marking as "In Discussion," but I'm wondering if this bug could actually be marked "Resolved"? What does the community do with old bugs that are obsolete or no longer relevant?
Comment 3 Katrin Fischer 2024-03-17 21:54:14 UTC
I found:

Bug 30025 - Split BiblioAddsAuthorities into 2 preferences

This patch splits the system preference BiblioAddsAuthorities into two new system preferences that more clearly define what the settings do:
1- RequireChoosingExistingAuthority: this preference indicates whether a cataloger must choose from existing authorities, or if they can enter free text into controlled fields
2- AutoLinkBiblios: this preference determines whether Koha will attempt to link a new record to existing authorities upon saving. In conjunction with the existing preference, AutoCreateAuthorities, unmatched headings will either be linked to a new authority, or remain uncontrolled

And it looks like RequireChoosingExistingAuthority is already set to "don't require" by default.

I am closing - please re-open if there is still something that needs to be done here!