November 2013 - Koha-bugs - lists.koha-community.org

[Bug 10308] New: Authorities linker should handle the "local subject added entry" fields.
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '14

01 Sep '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10308 Bug ID: 10308 Summary: Authorities linker should handle the "local subject added entry" fields. Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: robin(a)catalyst.net.nz CC: m.de.rooy(a)rijksmuseum.nl In MARC21, 690-699 are for locally defined subjects. These should be linked up to their appropriate authorities by the linker too. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 10066] New: updating biblio return undefined error if linked authority does not exist in db
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '14

01 Sep '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10066 Bug ID: 10066 Summary: updating biblio return undefined error if linked authority does not exist in db Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: MARC Authority data support Assignee: gmcharlt(a)gmail.com Reporter: siewyee2(a)yahoo.com descrption of problem: updating biblio return undefined error if previouly linked authority does not exist in db steps to recreate: 1. link an authority to biblio 2. manually delete authority from db 3. either a. run link_bibs_to_authorities.pl or b. update the biblio from staff client 4. will return undefined error for field we wanted to clear all linked authorities subfield $9 from biblios. run into this error. fixed the code, but dont really know if it is the best approach. attaching code fix for reference. ######################################################################### AuthoritiesMarc.pm line 1194 added one line: return unless defined($record); } else { #fix undefined error if authorized heading does not exist in db return unless defined($record); # foreach my $field ($record->field('1..')) { ########################################################################## Biblio.pm line 669 added one line: return unless defined($authorized_heading); my $authorized_heading = C4::AuthoritiesMarc::GetAuthorizedHeading( { 'authid' => $authid } ); #fix undefined error if authorized heading does not exist in db return unless defined($authorized_heading); # return ($field->as_string('abcdefghijklmnopqrstuvwxyz') eq $authorized_heading); -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 9110] New: GetAuthorizedHeading Can't call method "field" on an undefined
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '14

01 Sep '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9110 Bug ID: 9110 Summary: GetAuthorizedHeading Can't call method "field" on an undefined Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: MARC Authority data support Assignee: gmcharlt(a)gmail.com Reporter: matted-34813(a)mypacks.net I deleted my auth_header records; When runnong misc/link_bibs_to_authorities.pl With LinkerRelink = Do I get: GetAuthorizedheading Can't call method "field" on an undefined value at /home/koha/kohaclone/C4/AuthoritiesMarc.pm line 1191 In my case, I deleted the auth_header records, since I wanted to regenerate them. They had lots of dups since I was upgrading from a 3.0 version to (master pre-3.10). I reindexed the bibs and auths, but since I shouldn't find any auths, and though my bibs might have dangling $9 links, there might need to be a check that $record->field is viable. other settings: CatalogModuleRelink Do LinkerKeepStale = do not LinkerModule - default AutoCreateAuthorities - either setting BiblioAddsAuthorities - allow UseAuthoritiesForTracings -either setting Fuzzy not enabled. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 5706] New: Search, create lists and Export authorities from staff interface
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '14

01 Sep '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5706 Summary: Search, create lists and Export authorities from staff interface Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: MARC Authority data support AssignedTo: gmcharlt(a)gmail.com ReportedBy: eb(a)efdss.org QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com Estimated Hours: 0.0 It would be useful to be able to perform certain operations on authority records in the staff interface. Specifically 1) Search by creation date 2) Search by control number 3) add to a list or create a list from a search results page 4) export MARC 5) batch edit authorities -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

1 5

[Bug 6839] New: placement of subfield 9 in 6XX and 7XX headings changes staff view
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '14

01 Sep '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6839 Bug #: 6839 Summary: placement of subfield 9 in 6XX and 7XX headings changes staff view Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: MARC Authority data support AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com We've noticed that where the subfield 9 in the 6XX and 7XX fields is first in the list of subheadings causes there to be dashes in the staff "Normal" view of the record. That subfield seems to be used to hold the link to the authority record, When a new heading is added and the record saved, making a link to the authorities, sometimes the 9 is first and sometimes second and sometimes last. But if it is first (before the a) there are dashes in front as if the subfield a were a subheading rather than a heading. The problem is that if the subfield 9 is first, while it's not pushed to the subfields loop in the GetMarc<whatever> subroutines of C4/Biblio.pm, it's still counted, and the next subfield is viewed as "second" even though it's actually first. This means a separator is put in front of it. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 2

[Bug 5347] New: late order management
by bugzilla-daemon＠bugs.koha-community.org 29 Aug '14

29 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5347 Summary: late order management Change sponsored?: Sponsored Product: Koha Version: rel_3_4 Platform: All URL: http://wiki.koha-community.org/wiki/Late_orders_acq_RF C OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: paul.poulain(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 For lateorders, we will add fields for date and comment coming from the library. For claims, we will add * a claim counter, to know how many times an order has been claimed * a claim table, containing all the claims an order has, with the date of the claim and the content of the claim -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

1 99

[Bug 5576] New: Access Koha via SSL
by bugzilla-daemon＠bugs.koha-community.org 29 Aug '14

29 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5576 Summary: Access Koha via SSL Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: ASSIGNED Severity: enhancement Priority: P5 Component: System Administration AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 Some libraries want to access Koha over SSL. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

1 12

[Bug 10542] New: QueryParser + OpacSuppression doesn't allow search in 'all libraries'
by bugzilla-daemon＠bugs.koha-community.org 29 Aug '14

29 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10542 Bug ID: 10542 Summary: QueryParser + OpacSuppression doesn't allow search in 'all libraries' Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de CC: jcamins(a)cpbibliography.com When QueryParser is activated and OpacSuppression is used, you don't find any results for "All libraries" (pull down next to simple search in OPAC). -- You are receiving this mail because: You are watching all bug changes.

1 56

[Bug 10060] New: Self Checkout module does not honour circ control
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '14

28 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10060 Bug ID: 10060 Summary: Self Checkout module does not honour circ control Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: liz(a)catalyst.net.nz With Syspref settings of: CircControl - Use the checkout and fines rules of >> the library you are logged in at. HomeOrHoldingBranch - Use the checkout and fines rules of >> the library the item was checked out from. The web self check module isn't obeying these rules - it is using the library of the borrower doing the circulating, not the library assigned to the staff user required to log in to use the self check. To replicate: Ensure web self check is enabled Set CircControl to >> the library you are logged in at Set HomeOrHoldingBranch to >> the library the item was checked out from Create a staff user with "Circulate - remaining permissions," with homebranch as Library A (your choice which of your branches is library A) Set that user as the auto login user for self check Hit the self check interface at cgi-bin/koha/sco/sco-main.pl log in or use the card number for a borrower from Library B, circulate an item. View the item's circulation history, it will be from Library B instead of Library A -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 8148] New: ldap authentication should FAIL if ldap contains NEW password, and user types the PREVIOUS password
by bugzilla-daemon＠bugs.koha-community.org 27 Aug '14

27 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8148 Priority: P5 - low Change sponsored?: --- Bug ID: 8148 CC: dpavlin(a)rot13.org Assignee: gmcharlt(a)gmail.com Summary: ldap authentication should FAIL if ldap contains NEW password, and user types the PREVIOUS password Severity: enhancement Classification: Unclassified OS: All Reporter: heupink(a)gmail.com Hardware: All Status: NEW Version: rel_3_8 Component: Authentication Product: Koha The way ldap authentication works now is that the patron password is both in ldap and in mysql, usually the primary location being ldap. If sys admins change the userpassword, it's changed directly in ldap, and koha still has the old password stored in mysql. If the user then tries to logon with the OLD password, he should get 'access denied'. But instead he/she gets in, using the old, no longer valid, password. Various possible solutions: The best one: - an option not to store the password in mysql AT ALL (passwords are very sensitive info, I would like to store them in as few places as possible) Two other solutions: - a 'flush authentication cache' button in the staff interface? - a syspref to select the order of precedence when authenticating a user? -- You are receiving this mail because: You are watching all bug changes.

1 54