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

[Bug 13726] Koha::Acquisition::Bookseller should use Koha::Object
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '16

29 Nov '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13726 Josef Moravec <josef.moravec(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Signed Off -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13726] Koha::Acquisition::Bookseller should use Koha::Object
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '16

29 Nov '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13726 --- Comment #20 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- Created attachment 57803 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=57803&action=ed… Bug 13726: Fix for serials/acqui-search-result.pl -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13726] Koha::Acquisition::Bookseller should use Koha::Object
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '16

29 Nov '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13726 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13726] Koha::Acquisition::Bookseller should use Koha::Object
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '16

29 Nov '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13726 Josef Moravec <josef.moravec(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Failed QA --- Comment #19 from Josef Moravec <josef.moravec(a)gmail.com> --- Very close now I think. Just one issue I discovered now - when adding a serial subscription, I tried to search for a vendor: search is working, but no vendor name is shown in results table and vendor id is not transferred to new subscription form when clicking on Choose button. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13726] Koha::Acquisition::Bookseller should use Koha::Object
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '16

29 Nov '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13726 Josef Moravec <josef.moravec(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |17691 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17691 [Bug 17691] Add serial subscriptions info on vendor profile page -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13799] Add base for building RESTful API
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '16

29 Nov '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13799 --- Comment #246 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- (In reply to David Cook from comment #245) > (In reply to David Cook from comment #244) > > Is there going to be some documentation for using and developing the REST > > APIs? > > > > Still wondering about this... > > I see lots of blockers but no coherent documentation of the REST API for > Koha... /api/v1/spec will give you a json you can then copy/paste it to editor.swagger.io (file > paste json) See also bug 14458 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14224] patron notes about item shown at check in
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '16

29 Nov '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14224 --- Comment #17 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- (In reply to Aleisha Amohia from comment #16) > Hi Jonathan, > > I'm having issues using Koha::Issues->find($issue_id). > I'm receiving this error: > Can't locate object method "_new_from_dbic" via package "Koha::Issue" at > /home/vagrant/kohaclone/Koha/Objects.pm line 87 > Do you know what could be causing this? > > Aleisha Hi Aleisha, I have tried this small snippet: use Koha::Issues; my $issue = Koha::Issues->find(1); say $issue->branchcode; and it works as expected. Do you have a small part of code to recreate the error you got? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10662] Build OAI-PMH Harvesting Client
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '16

29 Nov '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10662 --- Comment #107 from David Cook <dcook(a)prosentient.com.au> --- I had hoped bug 17318 would fix the normalization problems with matching, but it looks like I might have to revive bug 15541 since the search query normalization mangles URLs. Since most OAI-PMH identifiers are URLs, it makes it impossible to match them. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10662] Build OAI-PMH Harvesting Client
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '16

29 Nov '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10662 --- Comment #106 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Galen Charlton from comment #1) > (In reply to David Cook from comment #0) > > Currently, Koha only acts as a OAI-PMH server, I propose to add a harvesting > > client as well (likely using the HTTP::OAI::Harvester module), so that Koha > > can ingest records from other data sources (such as digital repositories > > like Dspace). > > Interesting idea. > > > I've only started reading about it but despite initial reservations about > > resumption tokens, I think the hardest part will not be with the retrieval > > of records so much as the parsing of those records into MARC. > > This may be less of a problem in the long run with my plans to allow Koha to > support multiple metadata formats (although even once that's available, you > may still want the harvester to be able to convert the source metadata into > something else). > > One thing I'd suggest is that the harvester keep a copy of the original > metadata record in a database table; that would be more flexible than > immediately converting it to MARC and discarding the source data. Recently, I've been wondering if we really need an API just for OAI-PMH records, but that thought always brings me back to Galen's comment from 2013. I figure it's worthwhile having this API because it stores the entire OAI-PMH container record. If your metadata transform is bad, you won't get a MARCXML record in Koha, but you'll be able to re-try the transformation since the OAI-PMH container record is stored in the database. Plus, it shows an import history for records over time using the OAI-PMH identifier. I would like to link OAI-PMH identifiers more closely to MARCXML records, but it's a bit problematic. At the moment, I store it in the 024$a, but that's a fairly generic field. It would be nice to store it in the database, but then it might be lost during a record merge or a changing of biblionumbers in some other way. In the long-run, I'm planning to store the OAI-PMH identifier in RDF, but that's still in the future yet. Of course, OAI-PMH identifiers aren't foolproof either. In theory, they should be unique, but there's no guarantee. Anyway, I think it can't hurt to store OAI-PMH records in Koha. There's a cleanup_database script which will clear out old records, so the database table doesn't grow too large, so you could lose the original OAI-PMH record that way, but Koha should store data for a period long enough to let you fix transformation problems and things like that. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10662] Build OAI-PMH Harvesting Client
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '16

29 Nov '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10662 --- Comment #105 from David Cook <dcook(a)prosentient.com.au> --- I've added a new report for the Icarus task scheduler with bug #17690. At this point, I figure it's more efficient to test and push the OAI-PMH import API and then focus on the task scheduler. If the API is pushed to Koha, it also means that anyone could write a harvester and POST records to the API. You might write a cronjob which is run nightly. Or you might write a daemon that you control from the commandline. The idea with Icarus is that there will be a user interface in Koha that librarians can use to schedule OAI-PMH tasks to run. For performance, I've split the task into two parts. One task downloads records, while the other task uploads them. This lets you work in parallel, which means you upload records as they're downloaded rather than waiting for all the downloads to complete before uploading. (Another idea I had was to set up an import daemon for Koha, which could be used in lots of different ways... whether it's from the web or the command line.) -- You are receiving this mail because: You are watching all bug changes.

1 0