| Time |
S |
Nick |
Message |
| 00:23 |
|
|
oleonard joined #koha |
| 00:36 |
|
|
AndrewFH joined #koha |
| 00:46 |
|
|
lisettelatah joined #koha |
| 01:01 |
|
|
AndrewFH joined #koha |
| 02:03 |
|
|
AndrewFH joined #koha |
| 02:12 |
|
|
morrism joined #koha |
| 04:08 |
|
tuxayo |
hi :) |
| 04:08 |
|
tuxayo |
mtj or dcook around? |
| 04:17 |
|
mtj |
hi tuxayo, whats up? |
| 04:24 |
|
tuxayo |
mtj: I'm wondering if there is additional work for packaging if I release 19.11.x one day after the other branches? I got a few patches where I got conflicts that I couldn't solve, and might get help tomorrow (release day) or the day after. |
| 04:24 |
|
tuxayo |
And the day of the release there are always patches being backported in stable and oldstable. As I am on oldoldstable, I might not get them soon enough to have the time to release before the end of the day. |
| 04:25 |
|
tuxayo |
On the other hand, they can wait next month. I'm wondering how release timing impacts packaging work. |
| 04:28 |
|
mtj |
hi tuxayo, i think its no problem :) |
| 04:30 |
|
mtj |
if no big security bugs are included for next release?, then no problem |
| 04:42 |
|
tuxayo |
mtj: Good, thanks! I might use that. How does that work for you? Is that one operation that packages all branches. Or is that one per branch and doesn't matter if done on a different day? |
| 04:42 |
|
tuxayo |
Nope, no security release so no tight coordination. |
| 04:47 |
|
mtj |
tuxayo: packages can be built in parallel.. but i like to test/push each separately :) |
| 04:48 |
|
mtj |
..you can send us an email when you are ready |
| 05:13 |
|
|
did joined #koha |
| 05:17 |
|
tuxayo |
mtj: ok, thanks for the info :) |
| 05:21 |
|
|
MarkHofstetter joined #koha |
| 06:48 |
|
koha-jenkins |
Project Koha_19.11_U18 build #303: ABORTED in 12 min: https://jenkins.koha-community[…]ha_19.11_U18/303/ |
| 06:59 |
|
koha-jenkins |
Project Koha_19.11_U20 build #201: SUCCESS in 23 min: https://jenkins.koha-community[…]ha_19.11_U20/201/ |
| 07:05 |
|
koha-jenkins |
Project Koha_19.11_D9 build #307: SUCCESS in 29 min: https://jenkins.koha-community[…]oha_19.11_D9/307/ |
| 07:08 |
|
koha-jenkins |
Project Koha_19.11_D8 build #376: SUCCESS in 32 min: https://jenkins.koha-community[…]oha_19.11_D8/376/ |
| 07:12 |
|
|
cait joined #koha |
| 07:15 |
|
|
reiveune joined #koha |
| 07:15 |
|
|
paul_p joined #koha |
| 07:15 |
|
reiveune |
hello |
| 07:15 |
|
wahanui |
que tal, reiveune |
| 07:16 |
|
|
paul_p_ joined #koha |
| 07:17 |
|
koha-jenkins |
Project Koha_19.11_D10 build #145: SUCCESS in 44 min: https://jenkins.koha-community[…]ha_19.11_D10/145/ |
| 07:23 |
|
|
fridolin joined #koha |
| 07:31 |
|
|
did joined #koha |
| 07:32 |
|
koha-jenkins |
Project Koha_19.11_U16 build #60: SUCCESS in 57 min: https://jenkins.koha-community[…]oha_19.11_U16/60/ |
| 07:32 |
|
|
alex_a joined #koha |
| 07:33 |
|
alex_a |
Bonjour |
| 07:33 |
|
wahanui |
hola, alex_a |
| 08:00 |
|
|
lds joined #koha |
| 08:01 |
|
|
cait1 joined #koha |
| 08:08 |
|
|
cait2 joined #koha |
| 08:10 |
|
|
cm joined #koha |
| 08:10 |
|
cm |
hi |
| 08:10 |
|
wahanui |
privet, cm |
| 08:10 |
|
cm |
i keep getting this error when i search the opac: Context.pm: could not find ParserDetails.ini in /usr/local/share/perl/5.28.1/XML/SAX |
| 08:14 |
|
domm |
Hey, I've got a MARC21-Framework question: the library does not want to show some MARC21 fields (eg 600-700) in the cataloguing interface, but we cannot figure out how to disable them. |
| 08:15 |
|
domm |
Or is the correct answer to "just" delete the tags/fields? |
| 08:23 |
|
magnuse |
domm: you should be able to hide them using the "visibility" setting on subfields, in the MARC frameworks editor: https://koha-community.org/man[…]lds-and-subfields |
| 08:25 |
|
cait2 |
domm: no |
| 08:25 |
|
cait2 |
if you delete them, you will be losing the data too |
| 08:25 |
|
cait2 |
unless that IS the intention |
| 08:26 |
|
cait2 |
What magnuse said - set editor to hidden |
| 08:31 |
|
ashimema |
bug 27730 |
| 08:31 |
|
huginn |
Bug https://bugs.koha-community.or[…]_bug.cgi?id=27730 enhancement, P3, ---, koha-bugs, NEW , Innocent changes to framework silently delete bibliographic data |
| 08:31 |
|
ashimema |
any chance you might weight in on that one cait2 ? |
| 08:31 |
|
ashimema |
I'm not at all close to the area of functionality or cataloguing practices to really understand what Ian is getting at |
| 08:38 |
|
cait2 |
I think the issue is that even I was not aware that ignore would lead to data loss as well |
| 08:38 |
|
cait2 |
so maybe we need to verify if that has changed between versions and document? |
| 08:42 |
|
cait2 |
commented |
| 08:53 |
|
cm |
hi cait2 :) |
| 08:57 |
|
|
fridolin joined #koha |
| 08:59 |
|
domm |
magnuse: None of the "visibility" checkboxes are ticked (tag 600, subfield 9), but when adding a record, I still see both (600, subfield 9) |
| 09:02 |
|
domm |
the visibilty checkboxes work with tag 500, but not for tags > 600, which seems very weird |
| 09:15 |
|
|
davidnind joined #koha |
| 09:31 |
|
domm |
hm, where is the visibility stored in the DB? I cannot find anything in table marc_subfield_structure? |
| 09:32 |
|
ashimema |
thanks cait2 |
| 09:32 |
|
ashimema |
:) |
| 09:32 |
|
cm |
i've upgraded from 3.10.x to the current version |
| 09:32 |
|
cm |
now i don't see any titles when i search the opac |
| 09:33 |
|
cm |
the number of titles is show correctly, but i see no title name |
| 09:33 |
|
|
severine_q joined #koha |
| 09:33 |
|
severine_q |
Hi #Koha ! |
| 09:35 |
|
domm |
ok, visibilty seems to be stored as a bitmask of some sort in marc_subfield_structure.hidden |
| 09:38 |
|
domm |
btw, I'm trying to disable the tagfield in the editor... |
| 09:38 |
|
domm |
(Add MARC record) |
| 09:43 |
|
cait2 |
domm: hidden |
| 09:44 |
|
cait2 |
it#s a numeric value, there is a list in the wiki what the values mean |
| 09:44 |
|
cait2 |
cm: make sure the biblionumber is not set to hidden in your frameworks |
| 09:44 |
|
cm |
ok ill check |
| 09:44 |
|
cait2 |
cm: in ealrier versions this didn't work (the visibility setting) but now it does |
| 09:44 |
|
cait2 |
which is nice... but might mismatch with some old configurations |
| 09:44 |
|
domm |
https://wiki.koha-community.or[…]iki/Hidden_values |
| 09:45 |
|
domm |
ok, that seems helpful |
| 09:45 |
|
cait2 |
domm: yep that exactly |
| 09:45 |
|
cm |
where can i find this setting? |
| 09:45 |
|
cait2 |
domm: the 4 checkboxes are translated to these numbers, the proof is in the code somewher too of course, but i always use this |
| 09:46 |
|
cait2 |
cm: go to administration > bibliographic frameworks (you might have to do this for all of them) > marc structure > 999 and see if the subfield for biblionumber has the checkbox for OPAC checked in visibility |
| 09:46 |
|
cait2 |
hm and also do this for 245 maybe? |
| 09:46 |
|
cait2 |
oooh and another thing to check: do you have anything in OpacHiddenItems system preference? |
| 09:48 |
|
cait2 |
hm and running the marc bilbiographic framework check probably doesn't hurt either, it's also under administration |
| 09:49 |
|
domm |
OpacHiddenItems* is empty, hidden set to 8 (all no), but I still see tagfield 600, subfield 9. |
| 09:49 |
|
domm |
I don't see any of the other subfields, though |
| 09:52 |
|
domm |
time to look at the code :-) |
| 09:53 |
|
domm |
I think this might be the cause: |
| 09:53 |
|
cm |
so for 999 all is visiblw |
| 09:53 |
|
domm |
elsif ($subfield eq "9" and |
| 09:53 |
|
domm |
exists($tagslib->{$tag}->{'a'}->{authtypecode}) and |
| 09:53 |
|
cm |
checking 245 now |
| 09:53 |
|
domm |
defined($tagslib->{$tag}->{'a'}->{authtypecode}) and |
| 09:53 |
|
domm |
$tagslib->{$tag}->{'a'}->{authtypecode} ne '') { |
| 09:56 |
|
cm |
cait2: :-( |
| 09:57 |
|
cm |
for 245 everything is visible as well |
| 09:57 |
|
cm |
and there no opachiddenitems set |
| 10:01 |
|
domm |
yeah, found it: 600.a has an authtypecode (PERSO_NAME), which triggers the special case in addbiblio.pl:346 (# it's a subfield $9 linking to an authority record - see bug 2206) |
| 10:01 |
|
huginn |
Bug https://bugs.koha-community.or[…]w_bug.cgi?id=2206 blocker, PATCH-Sent (DO NOT USE), ---, gmcharlt, CLOSED FIXED, Authorities not updating with the number of biblios |
| 10:01 |
|
domm |
when I remive the authtypecode from 600.a, the field is not shown in the editor |
| 10:10 |
|
cm |
also i see this in opac-error.log: opac-search.pl: Use of uninitialized value in scalar assignment at /usr/share/koha/lib/C4/Koha.pm line 550.: /usr/sh are/koha/opac/cgi-bin/opac/opac-search.pl |
| 10:10 |
|
cm |
dunno if its related |
| 10:22 |
|
oleonard |
Hi #koha |
| 10:27 |
|
magnuse |
kia ora oleonard |
| 10:27 |
|
* magnuse |
needs lunch |
| 10:31 |
|
cm |
cait2: sorry to bother you but do you have any further ideas? |
| 10:32 |
|
|
MarkHofstetter joined #koha |
| 10:32 |
|
|
davidnind left #koha |
| 10:32 |
|
ashimema |
eythian around? |
| 10:41 |
|
oleonard |
What is the question cm? |
| 10:42 |
|
cm |
i've upgraded from 3.10.x to the most recent version |
| 10:42 |
|
cm |
in the opac search the number of titles found is displayed correctly |
| 10:42 |
|
cm |
but i see no title names |
| 10:43 |
|
cm |
i see the numbers and can klick the select box but no title names |
| 10:44 |
|
oleonard |
cm: Only on the results page, not on the detail page? |
| 10:44 |
|
cm |
only on the results page |
| 10:44 |
|
cm |
the details page is correct |
| 10:44 |
|
oleonard |
Are all the XSL preferences set to "default," and are you using any custom XSLT? |
| 10:45 |
|
cm |
also when i hover over "place hold" i see the correct biblio numbers |
| 10:45 |
|
cm |
hm xsl preferences.. how can i check that? |
| 10:46 |
|
oleonard |
Search system preferences for "xsl." |
| 10:47 |
|
cm |
most are set to default |
| 10:47 |
|
cm |
some have a toogle display/dont show |
| 10:48 |
|
oleonard |
All the ones like " OPACXSLTDetailsDisplay " should be set to default |
| 10:49 |
|
cm |
they are |
| 10:50 |
|
oleonard |
I'm assuming that if OPACXSLTDetailsDisplay is set to default and the title displays correctly that there's no issue with the framework, but just in case did you open the "MARC Bibliographic framework test" from Administration? |
| 10:51 |
|
oleonard |
Hm, I guess that doesn't verify title stuff, so that's probably superfluous. |
| 10:51 |
|
cm |
i did and shows some issues, but these were also present in the old version |
| 10:51 |
|
cm |
nvalid authority typesNot all authority types referred to by the frameworks are defined. |
| 10:51 |
|
cm |
these kinds of warnings |
| 10:52 |
|
oleonard |
Search results in the staff interface look correct? |
| 10:52 |
|
cm |
oh |
| 10:52 |
|
cm |
i found something |
| 10:52 |
|
cm |
i changed OPACXSLTDetailsDisplay to empty |
| 10:52 |
|
cm |
and now i see everything correctly |
| 10:53 |
|
cm |
"default" was the default setting i changed it to empty |
| 10:53 |
|
oleonard |
Yes, with OPACXSLTDetailsDisplay set to empty it pulls the data from the database rather than the MARC data |
| 10:54 |
|
cm |
so what could be wrong with the marc data? |
| 10:54 |
|
oleonard |
If the detail page is correct when OPACXSLTDetailsDisplay is "default," then nothing is wrong with your data. |
| 10:54 |
|
oleonard |
it makes me wonder if there is a problem with the XSL file which controls your search results. |
| 10:55 |
|
oleonard |
Search results in the staff interface look correct? |
| 10:55 |
|
cm |
yes |
| 10:55 |
|
oleonard |
What Koha version are you on? |
| 10:56 |
|
cm |
20.11.02.000 |
| 10:57 |
|
cm |
i did some extensive marc cleanups, but only for authorities |
| 10:57 |
|
cm |
never for items |
| 10:57 |
|
oleonard |
You might compare the file you have on your server with https://git.koha-community.org[…]m2OPACResults.xsl |
| 10:57 |
|
cm |
ok ill have a look |
| 11:03 |
|
cm |
oleonard: they are identical |
| 11:03 |
|
oleonard |
:/ |
| 11:03 |
|
cm |
your suggestion worries me a bit: how could i check if something is wrong with my marc files? |
| 11:04 |
|
oleonard |
If the detail page works and the staff interface search results work, then I wouldn't think anything is wrong with your MARC files. |
| 11:04 |
|
oleonard |
If the cause were the MARC files then the same problem would be reflected in those other interfaces. |
| 11:06 |
|
cm |
ok |
| 11:06 |
|
cm |
seems reassuring :) |
| 11:06 |
|
cm |
i have another idea |
| 11:07 |
|
oleonard |
I don't :( |
| 11:07 |
|
cm |
i suspect that my perl env on the linux server is somehow not correct |
| 11:07 |
|
cm |
because i also got some xml:sax warning that it could not find a parserdetails.ini |
| 11:07 |
|
cm |
any idea how to double-check that? |
| 11:11 |
|
|
khall joined #koha |
| 11:13 |
|
oleonard |
cm: Are you on a non-Debian platform? |
| 11:14 |
|
cm |
no im on debian |
| 11:14 |
|
oleonard |
Package installation? |
| 11:14 |
|
cm |
i had the problem that sax_parser_test didnt work |
| 11:14 |
|
cm |
yes package |
| 11:14 |
|
oleonard |
I have a vague memory of our installation instructions telling what to do in that situation but now I can't find it. |
| 11:16 |
|
domm |
I've opend Bug 28022 regarding my subfield 9 question / problem from earlier. Not sure if it's actually a bug, or intended (but slightly confusing) behavior... |
| 11:16 |
|
huginn |
Bug https://bugs.koha-community.or[…]_bug.cgi?id=28022 enhancement, P5 - low, ---, koha-bugs, NEW , MARC subfield 9 not honoring visibility |
| 11:17 |
|
cm |
in any case: oleonard, could i get any problems in the future when i leave OPACXSLTDetailsDisplay empty? |
| 11:17 |
|
cm |
if not, i would now just leave it at that |
| 11:18 |
|
oleonard |
The "empty" option is deprecated so at some point in the future it will go away |
| 11:18 |
|
oleonard |
But for now it is a workaround. |
| 11:18 |
|
cm |
hm |
| 11:21 |
|
|
AndrewFH joined #koha |
| 11:26 |
|
cm |
how could i verify that it is not a perl/xml error? |
| 11:26 |
|
cm |
like validaing the stylesheet on the server |
| 11:28 |
|
|
alex_a joined #koha |
| 11:28 |
|
|
paul_p_ joined #koha |
| 11:28 |
|
|
reiveune joined #koha |
| 11:28 |
|
|
StefanBerndtsson[m]1 joined #koha |
| 11:28 |
|
oleonard |
Sorry cm I don't know |
| 11:31 |
|
cm |
ok |
| 11:31 |
|
cm |
thx alot oleonard! |
| 11:32 |
|
oleonard |
Other than waiting around here for smarter help, I suggest posting a message to the koha general mailing list |
| 11:41 |
|
|
Dyrcona joined #koha |
| 11:55 |
|
|
AndrewFH joined #koha |
| 11:59 |
|
|
khall_ joined #koha |
| 12:28 |
|
ashimema |
domm, I have a vague recollection of done really funky code around that area regarding subfield 9 and authorised linking field and display ignoring hidden |
| 12:31 |
|
cait2 |
cm: I would check the error logs |
| 12:31 |
|
cait2 |
ah too late |
| 12:50 |
|
koha-jenkins |
Yippee, build fixed! |
| 12:50 |
|
wahanui |
Congratulations! |
| 12:50 |
|
koha-jenkins |
Project Koha_20.05_U20 build #292: FIXED in 26 min: https://jenkins.koha-community[…]ha_20.05_U20/292/ |
| 12:54 |
|
|
marie-luce joined #koha |
| 12:57 |
|
koha-jenkins |
Project Koha_20.05_D11 build #618: SUCCESS in 34 min: https://jenkins.koha-community[…]ha_20.05_D11/618/ |
| 13:02 |
|
koha-jenkins |
Project Koha_20.05_U18 build #125: SUCCESS in 39 min: https://jenkins.koha-community[…]ha_20.05_U18/125/ |
| 13:05 |
|
|
khall joined #koha |
| 13:15 |
|
koha-jenkins |
Project Koha_20.05_U20 build #293: SUCCESS in 25 min: https://jenkins.koha-community[…]ha_20.05_U20/293/ |
| 13:15 |
|
koha-jenkins |
Project Koha_20.05_D10 build #258: SUCCESS in 50 min: https://jenkins.koha-community[…]ha_20.05_D10/258/ |
| 13:16 |
|
koha-jenkins |
Project Koha_20.05_U16 build #263: UNSTABLE in 53 min: https://jenkins.koha-community[…]ha_20.05_U16/263/ |
| 13:17 |
|
|
khall_ joined #koha |
| 13:19 |
|
koha-jenkins |
Project Koha_20.05_D9 build #257: SUCCESS in 52 min: https://jenkins.koha-community[…]oha_20.05_D9/257/ |
| 13:21 |
|
koha-jenkins |
Project Koha_20.05_U2010 build #154: SUCCESS in 56 min: https://jenkins.koha-community[…]_20.05_U2010/154/ |
| 13:22 |
|
|
erik_ joined #koha |
| 13:41 |
|
|
cait2 joined #koha |
| 13:41 |
|
|
ashimema joined #koha |
| 13:41 |
|
|
black23[m] joined #koha |
| 13:41 |
|
|
mtj[m] joined #koha |
| 13:41 |
|
|
matts joined #koha |
| 13:41 |
|
|
janPasi joined #koha |
| 13:41 |
|
|
jajm joined #koha |
| 13:41 |
|
|
koha-jenkins joined #koha |
| 13:42 |
|
koha-jenkins |
Project Koha_20.05_U18 build #126: SUCCESS in 39 min: https://jenkins.koha-community[…]ha_20.05_U18/126/ |
| 13:50 |
|
|
darkharmony9999[m] joined #koha |
| 13:50 |
|
koha-jenkins |
Project Koha_20.05_D9 build #258: SUCCESS in 28 min: https://jenkins.koha-community[…]oha_20.05_D9/258/ |
| 14:01 |
|
|
tuxayo joined #koha |
| 14:04 |
|
koha-jenkins |
Yippee, build fixed! |
| 14:04 |
|
wahanui |
Congratulations! |
| 14:04 |
|
koha-jenkins |
Project Koha_20.05_U16 build #264: FIXED in 47 min: https://jenkins.koha-community[…]ha_20.05_U16/264/ |
| 14:04 |
|
koha-jenkins |
Project Koha_20.05_D10 build #259: UNSTABLE in 48 min: https://jenkins.koha-community[…]ha_20.05_D10/259/ |
| 14:04 |
|
koha-jenkins |
Project Koha_20.05_D11 build #620: SUCCESS in 33 min: https://jenkins.koha-community[…]ha_20.05_D11/620/ |
| 14:18 |
|
koha-jenkins |
Project Koha_20.05_U2010 build #155: SUCCESS in 56 min: https://jenkins.koha-community[…]_20.05_U2010/155/ |
| 14:22 |
|
koha-jenkins |
Project Koha_20.05_U18 build #127: SUCCESS in 39 min: https://jenkins.koha-community[…]ha_20.05_U18/127/ |
| 14:26 |
|
|
khall joined #koha |
| 14:51 |
|
koha-jenkins |
Project Koha_20.05_U16 build #265: SUCCESS in 47 min: https://jenkins.koha-community[…]ha_20.05_U16/265/ |
| 14:52 |
|
koha-jenkins |
Yippee, build fixed! |
| 14:52 |
|
wahanui |
Congratulations! |
| 14:52 |
|
koha-jenkins |
Project Koha_20.05_D10 build #260: FIXED in 48 min: https://jenkins.koha-community[…]ha_20.05_D10/260/ |
| 14:58 |
|
koha-jenkins |
Project Koha_20.05_U20 build #294: SUCCESS in 1 hr 35 min: https://jenkins.koha-community[…]ha_20.05_U20/294/ |
| 15:11 |
|
koha-jenkins |
Project Koha_20.05_D9 build #259: SUCCESS in 29 min: https://jenkins.koha-community[…]oha_20.05_D9/259/ |
| 15:11 |
|
koha-jenkins |
Project Koha_20.05_D11 build #621: SUCCESS in 33 min: https://jenkins.koha-community[…]ha_20.05_D11/621/ |
| 15:14 |
|
|
tmcmahon joined #koha |
| 15:16 |
|
koha-jenkins |
Project Koha_20.05_U2010 build #156: SUCCESS in 57 min: https://jenkins.koha-community[…]_20.05_U2010/156/ |
| 15:17 |
|
koha-jenkins |
Project Koha_20.05_U18 build #128: SUCCESS in 39 min: https://jenkins.koha-community[…]ha_20.05_U18/128/ |
| 15:24 |
|
|
paul_p_ joined #koha |
| 15:35 |
|
|
paul_p__ joined #koha |
| 15:40 |
|
koha-jenkins |
Project Koha_20.05_D9 build #260: SUCCESS in 28 min: https://jenkins.koha-community[…]oha_20.05_D9/260/ |
| 15:41 |
|
|
reiveune joined #koha |
| 15:41 |
|
|
alex_a joined #koha |
| 15:43 |
|
koha-jenkins |
Project Koha_20.05_U16 build #266: UNSTABLE in 51 min: https://jenkins.koha-community[…]ha_20.05_U16/266/ |
| 15:43 |
|
koha-jenkins |
Project Koha_20.05_D10 build #261: UNSTABLE in 50 min: https://jenkins.koha-community[…]ha_20.05_D10/261/ |
| 15:45 |
|
koha-jenkins |
Project Koha_20.05_D11 build #622: UNSTABLE in 33 min: https://jenkins.koha-community[…]ha_20.05_D11/622/ |
| 15:45 |
|
koha-jenkins |
Project Koha_20.05_U20 build #295: SUCCESS in 46 min: https://jenkins.koha-community[…]ha_20.05_U20/295/ |
| 15:53 |
|
oleonard |
Amit++ |
| 15:57 |
|
koha-jenkins |
Project Koha_20.05_U18 build #129: SUCCESS in 39 min: https://jenkins.koha-community[…]ha_20.05_U18/129/ |
| 16:05 |
|
reiveune |
bye |
| 16:05 |
|
|
reiveune left #koha |
| 16:09 |
|
koha-jenkins |
Project Koha_20.05_D9 build #261: SUCCESS in 29 min: https://jenkins.koha-community[…]oha_20.05_D9/261/ |
| 16:13 |
|
koha-jenkins |
Project Koha_20.05_U2010 build #157: SUCCESS in 57 min: https://jenkins.koha-community[…]_20.05_U2010/157/ |
| 16:18 |
|
koha-jenkins |
Project Koha_20.05_D11 build #623: STILL UNSTABLE in 33 min: https://jenkins.koha-community[…]ha_20.05_D11/623/ |
| 16:29 |
|
|
joan joined #koha |
| 16:30 |
|
joan |
hello everybody, did anybody do it?and how? automatically incorporate the stocknumber in the form 1,2,3 for example? thank you very much. |
| 16:32 |
|
|
darkharmony9999[m] joined #koha |
| 16:33 |
|
cait2 |
joan: you can use a catalouging plugin / value builder |
| 16:33 |
|
cait2 |
you link them to 952$i via the blbiographic framework configuration |
| 16:33 |
|
cait2 |
look for those plugins that contain "stocknumber" in the name |
| 16:33 |
|
cait2 |
I don't have time to explain mroe, but hopefully that will give you an idea - it's possible |
| 16:34 |
|
|
cait2 left #koha |
| 16:35 |
|
|
fridolin left #koha |
| 16:41 |
|
|
cait joined #koha |
| 16:54 |
|
|
SlackIntegration[m] joined #koha |
| 17:22 |
|
|
severine_q left #koha |
| 18:24 |
|
|
rangi joined #koha |
| 18:53 |
|
|
black23[m] joined #koha |
| 18:55 |
|
|
ashimema joined #koha |
| 19:45 |
|
koha-jenkins |
Project Koha_20.05_U20 build #296: SUCCESS in 27 min: https://jenkins.koha-community[…]ha_20.05_U20/296/ |
| 19:58 |
|
koha-jenkins |
Project Koha_20.05_D11 build #624: STILL UNSTABLE in 40 min: https://jenkins.koha-community[…]ha_20.05_D11/624/ |
| 20:10 |
|
koha-jenkins |
Yippee, build fixed! |
| 20:10 |
|
wahanui |
Congratulations! |
| 20:10 |
|
koha-jenkins |
Project Koha_20.05_U16 build #267: FIXED in 52 min: https://jenkins.koha-community[…]ha_20.05_U16/267/ |
| 20:11 |
|
koha-jenkins |
Project Koha_20.05_U20 build #297: SUCCESS in 25 min: https://jenkins.koha-community[…]ha_20.05_U20/297/ |
| 20:12 |
|
koha-jenkins |
Yippee, build fixed! |
| 20:12 |
|
wahanui |
Congratulations! |
| 20:12 |
|
koha-jenkins |
Project Koha_20.05_D10 build #262: FIXED in 51 min: https://jenkins.koha-community[…]ha_20.05_D10/262/ |
| 20:12 |
|
koha-jenkins |
Project Koha_20.05_U2010 build #158: SUCCESS in 52 min: https://jenkins.koha-community[…]_20.05_U2010/158/ |
| 20:15 |
|
koha-jenkins |
Project Koha_20.05_D9 build #262: SUCCESS in 58 min: https://jenkins.koha-community[…]oha_20.05_D9/262/ |
| 20:16 |
|
koha-jenkins |
Project Koha_20.05_U18 build #130: SUCCESS in 58 min: https://jenkins.koha-community[…]ha_20.05_U18/130/ |
| 20:31 |
|
koha-jenkins |
Yippee, build fixed! |
| 20:31 |
|
wahanui |
Congratulations! |
| 20:31 |
|
koha-jenkins |
Project Koha_20.05_D11 build #625: FIXED in 32 min: https://jenkins.koha-community[…]ha_20.05_D11/625/ |
| 20:38 |
|
koha-jenkins |
Project Koha_20.05_U20 build #298: SUCCESS in 25 min: https://jenkins.koha-community[…]ha_20.05_U20/298/ |
| 20:43 |
|
|
tuxayo joined #koha |
| 20:52 |
|
|
StefanBerndtsson[m]1 joined #koha |
| 20:59 |
|
koha-jenkins |
Project Koha_20.05_U2010 build #159: SUCCESS in 46 min: https://jenkins.koha-community[…]_20.05_U2010/159/ |
| 20:59 |
|
koha-jenkins |
Project Koha_20.05_U16 build #268: SUCCESS in 48 min: https://jenkins.koha-community[…]ha_20.05_U16/268/ |
| 21:00 |
|
koha-jenkins |
Project Koha_20.05_D10 build #263: SUCCESS in 48 min: https://jenkins.koha-community[…]ha_20.05_D10/263/ |
| 21:04 |
|
koha-jenkins |
Project Koha_20.05_D11 build #626: SUCCESS in 33 min: https://jenkins.koha-community[…]ha_20.05_D11/626/ |
| 21:11 |
|
koha-jenkins |
Project Koha_20.05_U18 build #131: SUCCESS in 55 min: https://jenkins.koha-community[…]ha_20.05_U18/131/ |
| 21:13 |
|
koha-jenkins |
Project Koha_20.05_U20 build #299: SUCCESS in 25 min: https://jenkins.koha-community[…]ha_20.05_U20/299/ |
| 21:15 |
|
koha-jenkins |
Project Koha_20.05_D9 build #263: SUCCESS in 1 hr 0 min: https://jenkins.koha-community[…]oha_20.05_D9/263/ |
| 21:37 |
|
koha-jenkins |
Project Koha_20.05_D11 build #627: SUCCESS in 33 min: https://jenkins.koha-community[…]ha_20.05_D11/627/ |
| 21:46 |
|
koha-jenkins |
Project Koha_20.05_U2010 build #160: SUCCESS in 47 min: https://jenkins.koha-community[…]_20.05_U2010/160/ |
| 21:49 |
|
koha-jenkins |
Project Koha_20.05_U16 build #269: SUCCESS in 50 min: https://jenkins.koha-community[…]ha_20.05_U16/269/ |
| 21:51 |
|
koha-jenkins |
Project Koha_20.05_D10 build #264: UNSTABLE in 51 min: https://jenkins.koha-community[…]ha_20.05_D10/264/ |
| 22:07 |
|
koha-jenkins |
Project Koha_20.05_U18 build #132: SUCCESS in 55 min: https://jenkins.koha-community[…]ha_20.05_U18/132/ |
| 22:17 |
|
koha-jenkins |
Project Koha_20.05_D9 build #264: SUCCESS in 1 hr 1 min: https://jenkins.koha-community[…]oha_20.05_D9/264/ |
| 22:32 |
|
koha-jenkins |
Project Koha_20.05_U2010 build #161: UNSTABLE in 46 min: https://jenkins.koha-community[…]_20.05_U2010/161/ |
| 23:01 |
|
koha-jenkins |
Project Koha_20.05_U18 build #133: SUCCESS in 54 min: https://jenkins.koha-community[…]ha_20.05_U18/133/ |
| 23:11 |
|
aleisha |
hi dcook are you around? |
| 23:15 |
|
dcook |
aleisha: Ish! |
| 23:15 |
|
dcook |
What's up? |
| 23:30 |
|
aleisha |
hi sorry was just on a break! still there dcook ? |
| 23:30 |
|
dcook |
aleisha: Yep |
| 23:30 |
|
aleisha |
i have a question about zebra search queries |
| 23:30 |
|
dcook |
Ooh well you've got the right guy here then |
| 23:30 |
|
dcook |
Hit me |
| 23:30 |
|
aleisha |
i was hoping so! |
| 23:31 |
|
aleisha |
i want to search multiple terms in one marclist |
| 23:31 |
|
aleisha |
like heading-main starts with 'fish' or 'sea' |
| 23:31 |
|
dcook |
marclist? |
| 23:32 |
|
aleisha |
by marclist i mean 'search main heading $a only' or 'search main heading' or 'entire record' |
| 23:32 |
|
aleisha |
oh also i am searching authorities ! |
| 23:33 |
|
dcook |
Hmm I am less familiar with the authorities interface, so it might be less of a Zebra question and more of a Koha question but let's see.. |
| 23:33 |
|
dcook |
Koha does a lot of mangling of search queries.. |
| 23:33 |
|
aleisha |
yeah... |
| 23:34 |
|
aleisha |
searching one term looks like '@attr 1=Heading-Main @attr 3=2 @attr 4=1 @attr 5=1 @attr 6=3 "fish" ' |
| 23:34 |
|
aleisha |
i've tried putting @or at the start and my second search term at the end but produces an error |
| 23:34 |
|
dcook |
Looking at the interface, it might not be possible to search multiple terms |
| 23:35 |
|
dcook |
Oh wait how do you mean putting @or at the start? |
| 23:35 |
|
dcook |
Are you searching Zebra directly? |
| 23:35 |
|
dcook |
Run me through the steps a bit more heh |
| 23:36 |
|
aleisha |
yeah so basically my problem is we have a search filter to search a thesaurus as well as the other headings |
| 23:36 |
|
aleisha |
and if you don't specify a thesaurus then koha or zebra doesn't search 'all' thesaurus |
| 23:36 |
|
aleisha |
so i want to put something in the query |
| 23:36 |
|
aleisha |
like if theres no thesaurus specified in the query, then search for these two main thesauruses |
| 23:36 |
|
aleisha |
does that make sense? |
| 23:38 |
|
dcook |
Nope haha |
| 23:38 |
|
dcook |
Sorry |
| 23:39 |
|
dcook |
You're talking about custom code? |
| 23:39 |
|
aleisha |
yeah but it could apply to any of the other marclists too |
| 23:40 |
|
dcook |
Still not really sure what marclists means but OK. I think I am starting to understand better. |
| 23:40 |
|
dcook |
So we're talking PQF/RPN queries |
| 23:40 |
|
aleisha |
yes |
| 23:41 |
|
dcook |
Ok I think I know what you're talking about now |
| 23:41 |
|
dcook |
So '@attr 1=Heading-Main @attr 3=2 @attr 4=1 @attr 5=1 @attr 6=3 "fish"' works |
| 23:41 |
|
dcook |
But the following example wouldn't |
| 23:41 |
|
dcook |
@or @attr 1=Heading-Main @attr 3=2 @attr 4=1 @attr 5=1 @attr 6=3 "fish" "other term" |
| 23:41 |
|
huginn |
dcook: downloading the Perl source |
| 23:42 |
|
dcook |
Or are you forming it differently? |
| 23:43 |
|
aleisha |
yes i think youve got it |
| 23:43 |
|
aleisha |
i also tried like |
| 23:43 |
|
dcook |
Any time you use a boolean operator, you're really joining together two queries, so you need to flesh them out more |
| 23:43 |
|
dcook |
Example: @or @attr 1=Heading-Main @attr 3=2 @attr 4=1 @attr 5=1 @attr 6=3 "fish" @attr 1=Heading-Main "test" |
| 23:43 |
|
aleisha |
@or @attr 1=Heading-Main @attr 3=2 @attr 4=1 @attr 5=1 @attr 6=3 "fish" attr 1=Heading-Main @attr 3=2 @attr 4=1 @attr 5=1 @attr 6=3 "sea" |
| 23:43 |
|
huginn |
aleisha: I'll give you the answer as soon as RDA is ready |
| 23:43 |
|
wahanui |
i already had it that way, huginn. |
| 23:43 |
|
aleisha |
but that didnt work |
| 23:43 |
|
aleisha |
ohhh |
| 23:44 |
|
aleisha |
okay thanks dcook ill give that a go |
| 23:44 |
|
dcook |
Hmm that looks ok at a glance |
| 23:44 |
|
dcook |
Well there's a typo in that one |
| 23:44 |
|
dcook |
you've put attr 1=Heading-Main instead of @attr 1=Heading-Main |
| 23:44 |
|
dcook |
This works fine: @or @attr 1=Heading-Main @attr 3=2 @attr 4=1 @attr 5=1 @attr 6=3 "fish" @attr 1=Heading-Main @attr 3=2 @attr 4=1 @attr 5=1 @attr 6=3 "sea" |
| 23:46 |
|
aleisha |
hmm i cant even see the different in those |
| 23:46 |
|
aleisha |
difference* |
| 23:46 |
|
aleisha |
oh th e missing @ |
| 23:46 |
|
dcook |
Yep |
| 23:47 |
|
aleisha |
this is what my query looks like |
| 23:47 |
|
aleisha |
@attr 1=Heading-Main @attr 3=2 @attr 4=1 @attr 5=1 @attr 6=3 "glasses" @or @attr 1=Subject-heading-thesaurus @attr 3=2 @attr 4=1 @attr 5=1 @attr 6=3 "scisshl" @attr 1=Subject-heading-thesaurus "scot" |
| 23:47 |
|
huginn |
aleisha: I suck |
| 23:47 |
|
aleisha |
but it's not working |
| 23:47 |
|
aleisha |
it needs the whole thing again maybe |
| 23:47 |
|
|
mtj[m] joined #koha |
| 23:48 |
|
aleisha |
this doesn't work either @attr 1=Heading-Main @attr 5=1 @attr 4=6 "fish" @or @attr 1=Subject-heading-thesaurus @attr 3=2 @attr 4=1 @attr 5=1 @attr 6=3 "scisshl" @attr 1=Subject-heading-thesaurus @attr 3=2 @attr 4=1 @attr 5=1 @attr 6=3 "scot" |
| 23:48 |
|
dcook |
So the problem there is your @or placement |
| 23:48 |
|
dcook |
You're thinking too logically hehe |
| 23:49 |
|
aleisha |
heh sounds right |
| 23:49 |
|
aleisha |
oh it needs an and? |
| 23:49 |
|
dcook |
Actually you have a few issues here |
| 23:49 |
|
aleisha |
i am so glad you see them!! |
| 23:49 |
|
dcook |
So if we think about @attr 1 as starting a query, it looks like you have 3 queries |
| 23:50 |
|
dcook |
But you only have 1 boolean operator |
| 23:50 |
|
dcook |
How is it that you want to be joining these three queries together? |
| 23:50 |
|
aleisha |
so where the @attr 1 is the same, joined by or. the rest joined by and |
| 23:51 |
|
aleisha |
@attr 1=Heading-Main @attr 3=2 @attr 4=1 @attr 5=1 @attr 6=3 "glasses" @and ( @attr 1=Subject-heading-thesaurus @attr 3=2 @attr 4=1 @attr 5=1 @attr 6=3 "scisshl" @or @attr 1=Subject-heading-thesaurus "scot") |
| 23:51 |
|
huginn |
aleisha: I'll give you the answer just as soon as RDA is ready |
| 23:51 |
|
wahanui |
i already had it that way, huginn. |
| 23:51 |
|
dcook |
I don't think you can use brackets with PQF/RPN |
| 23:51 |
|
aleisha |
yeah i was just trying to demonstrate what i want |
| 23:51 |
|
dcook |
@and @attr 1=Heading-Main @attr 5=1 @attr 4=6 "fish" @or @attr 1=Subject-heading-thesaurus @attr 3=2 @attr 4=1 @attr 5=1 @attr 6=3 "scisshl" @attr 1=Subject-heading-thesaurus @attr 3=2 @attr 4=1 @attr 5=1 @attr 6=3 "scot" |
| 23:51 |
|
huginn |
dcook: downloading the Perl source |
| 23:52 |
|
dcook |
hmm |
| 23:52 |
|
dcook |
this serves me for not having my test env up heh |
| 23:53 |
|
aleisha |
@and @attr 1=Heading-Main @attr 5=1 @attr 4=6 "fish" @or @attr 1=Subject-heading-thesaurus @attr 3=2 @attr 4=1 @attr 5=1 @attr 6=3 "scisshl" @attr 1=Subject-heading-thesaurus @attr 3=2 @attr 4=1 @attr 5=1 @attr 6=3 "scot" |
| 23:53 |
|
huginn |
aleisha: I suck |
| 23:53 |
|
aleisha |
ah yup so i got it looking like yours and still doesnt work :( |
| 23:53 |
|
dcook |
When you say doesn't work, what do you mean? |
| 23:54 |
|
dcook |
Error or 0 results? |
| 23:55 |
|
dcook |
Because I'm not getting any errors |
| 23:55 |
|
aleisha |
internal server error |
| 23:55 |
|
wahanui |
internal server error is not good even if config is wrong |
| 23:55 |
|
dcook |
Well I have to change Subject-heading-thesaurus to Heading-Main as I don't have that |
| 23:55 |
|
dcook |
Ah, i'm just using yaz-client atm |
| 23:55 |
|
dcook |
So I can't speak to an internal server error |
| 23:55 |
|
dcook |
That could be a number of things |
| 23:56 |
|
aleisha |
maybe try swapping the thesaurus one out for @attr 1=See-from |
| 23:56 |
|
aleisha |
as thats another marclist |
| 23:56 |
|
dcook |
Nope no good on my system |
| 23:57 |
|
aleisha |
hmm thats not a custom one |
| 23:57 |
|
aleisha |
oh well |
| 23:57 |
|
dcook |
Hmm |
| 23:57 |
|
dcook |
Yeah I see that.. |
| 23:57 |
|
dcook |
I se See-from in the bib1.attr |
| 23:57 |
|
dcook |
I mean it is custom |
| 23:57 |
|
dcook |
But it's Koha custom |
| 23:57 |
|
aleisha |
haha yeah :) |
| 23:58 |
|
dcook |
Oh wait.. |
| 23:58 |
|
dcook |
It's one of those red herring messages |
| 23:58 |
|
dcook |
It just means that I don't have anything in that index |
| 23:59 |
|
dcook |
But in your case I'd say add some logging |
| 23:59 |
|
dcook |
As the query should be fine overall |
| 23:59 |
|
dcook |
Structure-wise |
