[Bug 19635] New: OAI-PMH deleted records are now default and are listed first
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19635 Bug ID: 19635 Summary: OAI-PMH deleted records are now default and are listed first Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: koha-bugs@lists.koha-community.org Reporter: nick@bywatersolutions.com QA Contact: testopia@bugs.koha-community.org It seems bug 15108 made some changes to which records are served up first by the OAI server. When making a basic request with no token, i.e.: http://localhost:8080/cgi-bin/koha/oai.pl?verb=ListRecords&metadataPrefix=marcxml You get any deleted records first. When continuing if you have more than 50 deleted records the resumptionToken also includes deleted records We have services harvesting the entire catalog that don't expect deleted records first. I am not seeing a way to prevent them, and wonder if they should not be served first. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19635 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ere.maijala@helsinki.fi, | |olli-antti.kivilahti@jns.fi | |, tomascohen@gmail.com -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19635 --- Comment #1 from Ere Maijala <ere.maijala@helsinki.fi> --- As far as I know there's definitely nothing wrong in returning the deleted records first. Can you explain in a bit more detail why that is an issue? A harvester should just harvest until a resumptionToken is not returned, and there's no promise in the protocol that the records are returned in any particular order. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19635 --- Comment #2 from Nick Clemens <nick@bywatersolutions.com> --- (In reply to Ere Maijala from comment #1)
As far as I know there's definitely nothing wrong in returning the deleted records first. Can you explain in a bit more detail why that is an issue? A harvester should just harvest until a resumptionToken is not returned, and there's no promise in the protocol that the records are returned in any particular order.
I think this came up because we have a site with more deleted than existing records, this slowed the harvest and they thought something was wrong because all records were returning deleted. It may not be 'wrong' but I think it is a change - is there any benefit to returning deleted first? should/could it be a syspref? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19635 --- Comment #3 from Ere Maijala <ere.maijala@helsinki.fi> --- (In reply to Nick Clemens from comment #2)
I think this came up because we have a site with more deleted than existing records, this slowed the harvest and they thought something was wrong because all records were returning deleted.
It may not be 'wrong' but I think it is a change - is there any benefit to returning deleted first? should/could it be a syspref?
There's no real benefit but there's no downside either as far as I can see. Since the harvester needs to harvest everything, it doesn't matter if the deleted records come first or last or interleaved with non-deleted records. I'd be fine with it being a syspref, but I still can't see a real reason for that. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19635 Ere Maijala <ere.maijala@helsinki.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |BLOCKED Depends on| |20271 --- Comment #4 from Ere Maijala <ere.maijala@helsinki.fi> --- Note that this will change when normal and deleted records get merged into a single table. That's bug 20271. I'd like to close this one as Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20271 [Bug 20271] Merge deleted biblio, biblioitems, biblio_metadata, and items tables with their "alive" cousins -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19635 --- Comment #5 from Ere Maijala <ere.maijala@helsinki.fi> --- ... no changes are needed here, but we can also keep this blocked for now. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19635 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|BLOCKED |RESOLVED --- Comment #6 from Nick Clemens <nick@bywatersolutions.com> --- I am okay with closing, once service got used to the change things have been working fine. Cosmetic not functional issue -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org