← Previous day | Today | Next day → | Search | Index
All times shown according to UTC.
| Time | Nick | Message |
|---|---|---|
| 02:17 | koha-jenkins | Project Koha_19.11_U18 build #350: FAILURE in 2 min 22 sec: https://jenkins.koha-community[…]ha_19.11_U18/350/ |
| 02:38 | Project Koha_19.11_D8 build #428: SUCCESS in 22 min: https://jenkins.koha-community[…]oha_19.11_D8/428/ | |
| 02:47 | Project Koha_19.11_U_Stable build #51: SUCCESS in 31 min: https://jenkins.koha-community[…]9.11_U_Stable/51/ | |
| 02:57 | Project Koha_19.11_U20 build #251: SUCCESS in 41 min: https://jenkins.koha-community[…]ha_19.11_U20/251/ | |
| 03:01 | Project Koha_19.11_U16 build #107: SUCCESS in 43 min: https://jenkins.koha-community[…]ha_19.11_U16/107/ | |
| 03:05 | Project Koha_19.11_D9 build #366: SUCCESS in 27 min: https://jenkins.koha-community[…]oha_19.11_D9/366/ | |
| 03:16 | Project Koha_19.11_D11 build #16: SUCCESS in 29 min: https://jenkins.koha-community[…]oha_19.11_D11/16/ | |
| 03:30 | Project Koha_19.11_D8 build #429: SUCCESS in 32 min: https://jenkins.koha-community[…]oha_19.11_D8/429/ | |
| 03:31 | Yippee, build fixed! | |
| 03:31 | wahanui | Congratulations! |
| 03:31 | koha-jenkins | Project Koha_19.11_U18 build #351: FIXED in 26 min: https://jenkins.koha-community[…]ha_19.11_U18/351/ |
| 03:45 | Project Koha_19.11_U16 build #108: SUCCESS in 44 min: https://jenkins.koha-community[…]ha_19.11_U16/108/ | |
| 03:47 | Project Koha_19.11_U_Stable build #52: SUCCESS in 30 min: https://jenkins.koha-community[…]9.11_U_Stable/52/ | |
| 03:57 | Project Koha_19.11_D9 build #367: SUCCESS in 25 min: https://jenkins.koha-community[…]oha_19.11_D9/367/ | |
| 04:11 | Project Koha_19.11_U20 build #252: SUCCESS in 41 min: https://jenkins.koha-community[…]ha_19.11_U20/252/ | |
| 04:48 | Project Koha_19.11_U20 build #253: SUCCESS in 37 min: https://jenkins.koha-community[…]ha_19.11_U20/253/ | |
| 05:55 | lmstrand joined #koha | |
| 06:08 | cait joined #koha | |
| 06:35 | reiveune joined #koha | |
| 06:35 | reiveune | hello |
| 06:43 | magnuse | https://git.koha-community.org/ down? |
| 06:48 | Joubu | not down but a bit slow indeed |
| 06:48 | will have a look | |
| 06:53 | please don't try git fetch or web, it's getting slower and slower:) | |
| 06:55 | restarting gitea | |
| 06:56 | alex_a joined #koha | |
| 06:59 | cait joined #koha | |
| 07:00 | lds joined #koha | |
| 07:03 | cait1 joined #koha | |
| 07:08 | Joubu | back to normal |
| 07:32 | alex_a joined #koha | |
| 07:32 | alex_a joined #koha | |
| 07:46 | magnuse | Joubu++ |
| 08:17 | ashimema | mornin' koha |
| 08:29 | magnuse | kia ora ashimema |
| 08:30 | ashimema | wonder if there's a leak somewhere in the gittea code.. I found it was slowing down allot on Friday.. clearly it got worse over the weekend needing the restart this morning |
| 08:32 | Joubu | RAM and swap were full, gitea had been OOM killed 3 times in the last hour... |
| 08:42 | alex_a joined #koha | |
| 09:14 | ashimema | thanks for the patch on bug 29261 Joubu 🙂 |
| 09:14 | huginn` | Bug https://bugs.koha-community.or[…]_bug.cgi?id=29261 major, P5 - low, ---, jonathan.druart+koha, Needs Signoff , Translation script breaks members/tables/members_results.tt |
| 09:14 | ashimema | I obviously mis-understood one of your comments |
| 09:34 | huginn` | News from kohagit: Bug 28153: DBRev 21.06.00.035 <https://git.koha-community.org[…]38538b009c8b1b88a> |
| 09:34 | News from kohagit: Bug 28831: DBRev 21.06.00.034 <https://git.koha-community.org[…]ff480bf8e47f67511> | |
| 09:34 | News from kohagit: Bug 28445: (follow-up) Display count of modified items when too many to display <https://git.koha-community.org[…]eb87ab96a50dae23c> | |
| 09:34 | News from kohagit: Bug 28153: (follow-up) Add installer files and update atomicupdate <https://git.koha-community.org[…]a43ce23d812d46380> | |
| 09:34 | News from kohagit: Bug 28211: (QA follow-up) Add unit tests <https://git.koha-community.org[…]ca8088cb9847de7e6> | |
| 09:34 | News from kohagit: Bug 29243: Correct call when adding items from staged records <https://git.koha-community.org[…]c28c18f1ef358a6c4> | |
| 09:34 | News from kohagit: Bug 28445: Split and join on ' | ' instead of '|' for repeatable <https://git.koha-community.org[…]ad9eb729c9eb1df9a> | |
| 09:34 | News from kohagit: Bug 28211: (QA follow-up) POD changes <https://git.koha-community.org[…]4a86eff39d110f7e1> | |
| 09:35 | News from kohagit: Bug 28211: (QA follow-up) Remove test_call_recursive <https://git.koha-community.org[…]08abd8b1c635e7057> | |
| 09:35 | News from kohagit: Bug 27949: (QA follow-up) Remove TODO <https://git.koha-community.org[…]2a1ae57a26a9de138> | |
| 09:35 | News from kohagit: Bug 28831: Database revision, add new preference <https://git.koha-community.org[…]37224492ac539d44f> | |
| 09:35 | News from kohagit: Bug 28831: Add the new group by substatus-block <https://git.koha-community.org[…]5733ac511a90b039f> | |
| 09:35 | News from kohagit: Bug 28831: Add choose/when, and change indentation <https://git.koha-community.org[…]860572c474ed2d44f> | |
| 09:35 | News from kohagit: Bug 28785: Don't send SessionRestrictionByIP to template <https://git.koha-community.org[…]fabcd6c0dafec510c> | |
| 09:35 | News from kohagit: Bug 28785: Add skip_version_check for checkauth <https://git.koha-community.org[…]d98572015cc7c5a32> | |
| 09:35 | News from kohagit: Bug 28785: Adjust check_cookie_auth calls <https://git.koha-community.org[…]27de343a9c86d9564> | |
| 09:35 | News from kohagit: Bug 28785: Centralize cookie auth check in check_cookie_auth <https://git.koha-community.org[…]5aa57a00a8981fbae> | |
| 09:35 | News from kohagit: Bug 27949: Allow multiple article requests print slip <https://git.koha-community.org[…]b75d17a065706f545> | |
| 09:35 | News from kohagit: Bug 28211: Replace use of call_recursive() with call() <https://git.koha-community.org[…]17dd3d3c4f7e978d8> | |
| 09:35 | News from kohagit: Bug 28153: Add 'Hold reminder' messaging preference <https://git.koha-community.org[…]50e8223dad807138f> | |
| 10:10 | cait joined #koha | |
| 10:17 | Jeremyb joined #koha | |
| 10:25 | koha-jenkins | Project Koha_Master_D10_My8 build #665: UNSTABLE in 50 min: https://jenkins.koha-community[…]ster_D10_My8/665/ |
| 10:32 | Project Koha_Master_D11 build #414: UNSTABLE in 56 min: https://jenkins.koha-community[…]a_Master_D11/414/ | |
| 10:58 | Project Koha_Master_U_Stable build #279: UNSTABLE in 41 min: https://jenkins.koha-community[…]ter_U_Stable/279/ | |
| 11:15 | Project Koha_Master_D11_CPAN build #450: UNSTABLE in 50 min: https://jenkins.koha-community[…]ter_D11_CPAN/450/ | |
| 11:20 | oleonard | Hi #koha |
| 11:33 | koha-jenkins | Project Koha_Master_D9 build #1786: UNSTABLE in 1 hr 0 min: https://jenkins.koha-community[…]a_Master_D9/1786/ |
| 11:37 | Project Koha_Master_U20 build #208: UNSTABLE in 39 min: https://jenkins.koha-community[…]a_Master_U20/208/ | |
| 12:16 | Project Koha_Master_U20 build #209: STILL UNSTABLE in 39 min: https://jenkins.koha-community[…]a_Master_U20/209/ | |
| 12:31 | Project Koha_Master_D9 build #1787: STILL UNSTABLE in 1 hr 15 min: https://jenkins.koha-community[…]a_Master_D9/1787/ | |
| 12:33 | Project Koha_Master_U_Stable build #280: STILL UNSTABLE in 59 min: https://jenkins.koha-community[…]ter_U_Stable/280/ | |
| 12:54 | Dyrcona joined #koha | |
| 13:38 | awazez joined #koha | |
| 13:58 | tcohen joined #koha | |
| 14:22 | ashimema | cait around? |
| 14:22 | wahanui | hmmm... cait around is cait cait1 cait2 cait3 cait4 cait5 |
| 14:23 | cait1 | no? |
| 14:23 | *hides* | |
| 14:23 | ashimema | I'm getting myself confused |
| 14:24 | between 773 and 785 linking it seems | |
| 14:24 | cait1 | @marc 773 |
| 14:24 | huginn` | cait1: Information concerning the host item for the constituent unit described in the record (vertical relationship). In the case of host items that are serial or multi-volume in nature, information in subfields $g and $q is necessary to point to the exact location of the component part within the bibliographic item. (Repeatable) [b,d,g,h,i,k,m,n,o,p,q,r,s,t,u,w,x,y,z,3,6,7,8] |
| 14:24 | cait1 | @marc 785 |
| 14:24 | huginn` | cait1: Information concerning the immediate successor to the target item (chronological relationship). When a note is generated from this field, the introductory phrase may be generated based on the value in the second indicator position for display. (Repeatable) [b,c,d,g,h,i,k,m,n,o,r,s,t,u,w,x,y,z,6,7,8] |
| 14:24 | cait1 | @marc 780 |
| 14:24 | huginn` | cait1: Information concerning the immediate predecessor of the target item (chronological relationship). When a note is generated from this field, the introductory term or phrase may be generated based on the value in the second indicator position for display. (Repeatable) [b,c,d,g,h,i,k,m,n,o,r,s,t,u,w,x,y,z,6,7,8] |
| 14:24 | cait1 | they all really work in the same way |
| 14:24 | 780 and 785 are a couple | |
| 14:25 | a lot of them can be paired up | |
| 14:25 | not all | |
| 14:25 | ashimema | if UseControlNumber is disabled.. one uses Host-item search (on title only) whilst the other uses ti,phr |
| 14:25 | cait1 | so waht's the question? |
| 14:25 | ashimema | and then you split them with author stuff in bug 20277 |
| 14:25 | huginn` | Bug https://bugs.koha-community.or[…]_bug.cgi?id=20277 normal, P5 - low, ---, katrin.fischer, Signed Off , Link to host item doesn't work in analytical records if 773$a is present |
| 14:25 | cait1 | hm did you check what host item indexes? |
| 14:25 | i thought it was 773$t | |
| 14:26 | actually i hitnk i might be to blame in part for the confusion | |
| 14:26 | $a is main heading in the documentation | |
| 14:26 | and our first marc21 export put the title there when there was no author | |
| 14:26 | ashimema | wow.. |
| 14:26 | cait1 | instead of $t that was then empty |
| 14:27 | because it was a misunderstanding of the documentation I guess | |
| 14:27 | ashimema | now I'm wondering if the fallback search in bug 11175 was always wrong. |
| 14:27 | huginn` | Bug https://bugs.koha-community.or[…]_bug.cgi?id=11175 enhancement, P5 - low, ---, joonas.kylmala, Signed Off , Show the parent record's component parts in the detailed views |
| 14:27 | cait1 | I cannot tell about that right now |
| 14:27 | but nowadays we assume that $t is the title | |
| 14:27 | ashimema | ok |
| 14:27 | cait1 | and $a might or might not be filled with an author |
| 14:28 | so the at searches we have in some spots actually are not correct | |
| 14:28 | ashimema | 'show_analytics_link' does a different search to the 773 one |
| 14:28 | cait1 | they do soemtimes work as title contains 245$c that might have the author in the same spelling... but it also might have not |
| 14:28 | ashimema | so I think you're fix doesn't change enough lines.. shouldn't those searches match? |
| 14:28 | cait1 | we never ran into these cases because we use $w |
| 14:28 | ashimema | us too 😉 |
| 14:28 | cait1 | i thinik oleonard-away also worked on a fix for one a while ago |
| 14:29 | maybe we coud compromise on verifying the fix is ok and then change the others on a different bug? | |
| 14:29 | i think oleonard-away was working on one of those too a while ago, but not sure now if it's the same bug or not | |
| 14:38 | ashimema | I'm working through 11175 |
| 14:39 | marion joined #koha | |
| 14:45 | ashimema | hmm |
| 14:46 | right.. | |
| 14:46 | so the 773 is a specific reverse link | |
| 14:47 | the 'Show analytics' is the reverse right.. | |
| 14:47 | my brain hurts | |
| 14:53 | I 'think' Host-item contains title and author.. but distinctly. | |
| 14:53 | 995 <!--record.abs line 229: melm 773$a Host-item-->... (full message at https://matrix.org/_matrix/med[…]wgvPWAdinxygIfIL) | |
| 14:53 | 1003 <!--record.abs line 231: melm 773$t Host-item--> | |
| 14:53 | 1004 <index_subfields tag="773" subfields="t"> 1005 <target_index>Host-item:w</target_index> | |
| 14:53 | 1006 </index_subfields> | |
| 14:54 | or am I reading that wrong? | |
| 15:10 | Oak joined #koha | |
| 15:27 | reiveune | bye |
| 15:27 | reiveune left #koha | |
| 15:31 | domm | Quick question (hopefully): Can we use both LDAP and "internal"/Koha for auth? For example, patrons should use KOha-auth, but librarians LDAP? |
| 15:32 | ah, classic: after posting the question I find a link indicating that this is possible: | |
| 15:33 | https://bywatersolutions.com/n[…]-work-in-koha-3-4 | |
| 15:33 | (though that's a rather old link..) | |
| 15:37 | oleonard | cait1: That doesn't sound familiar... |
| 15:46 | cait1 | sorry, ashimema, phone calls and such, got distracted |
| 15:46 | domm: but ye | |
| 15:46 | s | |
| 15:46 | ashimema | no worries cait1 |
| 15:46 | cait1 | domm: if the user doesn't match on LDAP, it will use Koha's login |
| 15:46 | it's the same login form and in that a little unlike the other auth methods | |
| 15:47 | ashimema | I've changed 11175 to use ->subfield('245', "a") instead of ->title |
| 15:47 | so it now matches the XSLT | |
| 15:47 | so i think we're good now cait1 | |
| 15:48 | * ashimema | mistook ->title to mean 'a' only when it actually means 'all subfields' |
| 15:48 | domm | ok, I' also seen that in the code, now.. I was a bit unsure because modern SSO-Logins usually allow the user to choose the auth provider... |
| 15:48 | ashimema | ->title_proper doesn't even cover it.. as that concats a few but not all subfields and not just 'a' |
| 15:48 | domm | cait1: thanks, anyway |
| 15:52 | ashimema | cait1: could you ask your chaps to test bug 28729 for me? |
| 15:52 | huginn` | Bug https://bugs.koha-community.or[…]_bug.cgi?id=28729 major, P5 - low, ---, martin.renvoize, ASSIGNED , Return-path header not set in emails |
| 15:52 | ashimema | took some digging |
| 16:09 | cait1 | ashimema: title-cover |
| 16:09 | is just a | |
| 16:09 | ashimema | cover? |
| 16:09 | cait1 | ashimema: we actually have a patch in production for that (or almost production) - I will compare and check with you |
| 16:10 | a standard index in koha that is only 245a | |
| 16:10 | ashimema | oh.. cool |
| 16:10 | cait1 | on my todo list to post it :( |
| 16:10 | we will check | |
| 16:10 | just added to my todo | |
| 16:10 | ashimema | ah, interesting |
| 16:10 | cait1 | see you all tomorrow! |
| 16:11 | ashimema | host-item is 245at |
| 16:11 | have a good evening miss | |
| 16:11 | cait1 | also interesting actually |
| 16:11 | you too! | |
| 16:11 | although... t? | |
| 16:11 | your it's not 773? | |
| 16:11 | ashimema | oo |
| 16:11 | my bad.. misread | |
| 16:11 | 773at | |
| 16:11 | cait1 | ok, that let's me rest now :) |
| 16:12 | cait1 left #koha | |
| 16:18 | IGS joined #koha | |
| 16:19 | IGS | I'm a librarian. I don't speak SQL. Can someone help me with a report? |
| 16:20 | oleonard | You don't have to ask to ask IGS. Ask away, and if anyone can help they will. |
| 16:22 | IGS | We're not a circulating library, but I still need statistics about what things people are using. I was told to make a report using the following line of SQL. |
| 16:22 | select * statistics where type='localuse' | |
| 16:22 | It says I have a syntax error. | |
| 16:26 | oleonard | select * FROM statistics where type='localuse' |
| 16:26 | ashimema | oleonard++ |
| 16:29 | IGS | That did something. It showed me a list that looks kind of like this. |
| 16:29 | datetimebranchvaluetypeotheritemnumberitemtypelocationborrowernumberccode 2021-10-11 10:45:15MAIN0.0000localuse5362 | |
| 16:30 | How can I get it to show me the title of the item? | |
| 16:32 | cait joined #koha | |
| 16:51 | IGS | Is it possible to modify the SQL line " select * FROM statistics where type='localuse' " so that the report shows me the title of the item and maybe the call number? |
| 17:09 | tcohen | hola |
| 17:09 | wahanui | hi, tcohen |
| 17:39 | Awazez joined #koha |
← Previous day | Today | Next day → | Search | Index