← Previous day | Today | Next day → | Search | Index
All times shown according to UTC.
| Time | Nick | Message |
|---|---|---|
| 01:18 | tuxayo | Hi :) Does anyone if there is a way with a .patch or a unified diff to view it with meld, kdiff3, vimdiff, etc or even git itself? Without having to apply the patch. |
| 01:21 | The diff viewer of bugzilla just highlights whole lines changed. It's much easier in other tools to see what changed inside the line. Makes it harder when browsing many tickets and looking at their changes. | |
| 01:42 | kivilahtio | tuxayo: Thanks for the tip. I never really used the diff-viewer in Bugzilla. It is quite more handy than the raw .patch-file :) |
| 01:44 | tuxayo | > Thanks for the tip... (full message at <https://matrix.org/_matrix/med[…]JRGEyRVltCrvJtLVM>) |
| 01:44 | kivilahtio | tuxayo: https://stackoverflow.com/ques[…]-part-in-the-line |
| 01:45 | tuxayo: if you have trouble applying some of the patches, you could try git apply --reject commit-file-name.patch | |
| 01:45 | then git diff --word-diff=color | |
| 01:45 | tuxayo: sorry, this is the best I can give | |
| 01:47 | tuxayo | kivilahtio: Apply is too long when browsing several tickets. Thanks for the tips, that's precisely stuff like --color-words, --word-diff that is missing in the BZ built in viewer |
| 01:47 | When looking for stuff that I understand enough to QA it. | |
| 01:51 | kivilahtio | tuxayo: https://www.bugzilla.org/docs/[…]/patchviewer.html |
| 01:51 | Maybe Koha-Community's Bugzilla doesnt have all the goodies enabled, Bonsai and LXR for example are additional features. | |
| 01:54 | Running Ansible playbook to upgrade our fleet of free and open source software and hardware self-service library access control devices. Takes a long time to fix system issues and rerun playbooks. | |
| 01:54 | https://github.com/Hypernova-Oy/emb-toveri | |
| 01:54 | Some of the more exciting stuff I have done, and still do. | |
| 01:55 | You can make your own library card reader access control devices from the instructions, but it is a bit chalenging to manage the assembly and acquisitions as stuff is coming from 4 different coutries. | |
| 01:56 | tuxayo | > Maybe Koha-Community's Bugzilla doesnt have all the goodies enabled |
| 01:56 | Thanks maybe there are nice improvements there! | |
| 01:59 | kivilahtio: interesting, what do libraries do with these access control devices? | |
| 01:59 | kivilahtio | tuxayo: keep bad library users away from the self-service libraries. |
| 02:00 | tuxayo: It is a bit like a smart lock, with a display and it plays old Nokia ringtones. | |
| 02:01 | https://raw.githubusercontent.[…]er/rtttl/songs.pl | |
| 02:01 | tuxayo | > keep bad library users away from the self-service libraries |
| 02:01 | oh, that can be quite a problem indeed. So there are people banned from using self checkout? Can't the ILS enforce this? | |
| 02:01 | kivilahtio | we can manufacture those if you have libraries that want to start a self-service library |
| 02:01 | tuxayo: with our Koha-plugin it can be enforced. | |
| 02:02 | tuxayo | > with a display and it plays old Nokia ringtones |
| 02:02 | lol | |
| 02:02 | kivilahtio | Abba and the Black Diamon |
| 02:59 | alohabot joined #koha | |
| 05:59 | ashimema | The core issue with bugzilla is that it's really not seen any active development in decades |
| 06:00 | And .. most of its development predates git | |
| 06:00 | Bonsia and LXR you mention are tools for integrating with other version control systems.. so they won't help us here | |
| 06:01 | Splinter is the best we've got for now | |
| 06:02 | And patches themselves lack context . So it's very difficult to display any more context in the client. | |
| 06:03 | I'd love to see us jump to gitlab or tea.. but theyre missing a lot of the QA features we've come to rely on and I've bit come across any projects using them with the vast numbers of bugs we deal with | |
| 06:03 | Anywho | |
| 06:54 | magnuse | if anyone knows anyone who needs a really simple bug to practice on: bug 34942 |
| 06:54 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=34942 trivial, P5 - low, ---, oleonard, NEW , Typo: brower |
| 07:02 | Joubu | yes, should be bowser |
| 07:05 | cait joined #koha | |
| 07:06 | cait | good morning :) |
| 07:21 | @later tell PedroAmorim[m] MatthewBlenkinsop[m] could you have a look at bug Bug 34552? might be too late, but was not sure if you saw | |
| 07:21 | huginn | cait: The operation succeeded. |
| 07:36 | fridolin joined #koha | |
| 07:36 | cait | hi fridolin |
| 07:36 | fridolin left #koha | |
| 08:15 | MatthewBlenkinsop[m] | cait: I'm looking at the release this morning, I've just added that bug in 👍️ |
| 08:22 | ashimema | bug 34552 |
| 08:22 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=34552 normal, P3, ---, nick, Pushed to stable , No Results when filtering "All payments to the library" or "payment" in Statistics wizards : Cash register |
| 08:30 | cait | MatthewBlenkinsop[m]: htank you! |
| 09:21 | paulderscheid[m] | Morning #koha |
| 09:21 | magnuse | \o/ |
| 09:21 | paulderscheid[m] | Koha is currently not able to act as an identity provider itself, is that right? |
| 09:23 | magnuse | paulderscheid[m]: bug 21577 |
| 09:23 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=21577 new feature, P5 - low, ---, koha-bugs, NEW , Enable Koha to act as Shibboleth identity provider |
| 09:24 | ashimema | dcook has had success with keycloak paulderscheid I believe |
| 09:24 | you can use koha as your datasource | |
| 09:24 | paulderscheid[m] | Yeah, there |
| 09:24 | wahanui | Yeah, there is, like, an older Selenium version number on the wiki page |
| 09:25 | magnuse | wahanui: forget yeah, there |
| 09:25 | wahanui | magnuse: I forgot yeah, there |
| 09:25 | paulderscheid[m] | So you just have keycloak running and register it as an identity provider? |
| 09:26 | Sorry for the dumb questions, just getting into that stuff. | |
| 09:26 | ashimema | pretty much |
| 09:26 | Keycloak is an authz system and supports lots of different protocols.. we use it for testing a lot.. | |
| 09:27 | but I know dcook uses it much more extensively.. it can certainly act as an identity provider.. and I believe it can use various databases or api's for it's data backend.. so it could use the Koha borrowers table I reckon | |
| 09:27 | paulderscheid[m] | That's very cool! |
| 09:27 | ashimema | afraid that's about as far as my knowledge goes though.. I just know it's the recommended 'go to' for IdP stuff these days in open source circles |
| 09:28 | paulderscheid[m] | Yeah, I heard about keycloak from some seniors at Daimler Benz when I was at a hackathon |
| 09:29 | They were rather ranting, though ^^ | |
| 09:33 | Thanks ashimema | |
| 09:33 | thanks magnuse as well | |
| 09:34 | ashimema | SimpleSAMLphp is the other option.. maintained.. but must admit I never really got on with it well |
| 09:35 | paulderscheid[m] | Thanks |
| 09:51 | Joubu | aude_c[m], caroline: https://gitlab.com/koha-commun[…]anual/-/issues/34 |
| 10:06 | khall joined #koha | |
| 10:16 | ITMLJS[m] joined #koha | |
| 10:17 | ITMLJS[m] | Hello! I am Liyakat, from Gujarat, India. I am part of an educational institution and public library |
| 10:18 | we are looking for implementation of KOHA in our library and wish to replace our current custom software. Looking for contact of implementation partners in india | |
| 10:18 | any help would be highly appreciated | |
| 10:23 | paulderscheid[m] | Maybe hit up Priyanshu Soni or Triveni Chandriki, IT MLJS |
| 10:24 | ashimema you still there? | |
| 10:24 | ITMLJS[m] | yes, i am here |
| 10:24 | how do i get connected to them | |
| 10:25 | if you could share their contact numbers or email id, it would help | |
| 10:25 | paulderscheid[m] | Ah, sorry I was searching for another person IT MLJS. |
| 10:25 | But you can just ping them here, they both use IRC | |
| 10:25 | Priyanshu Soni Triveni Chandriki | |
| 10:27 | ITMLJS[m] | Thanks for the connect, i have send them DM to both. Let me wait for their response |
| 10:32 | oleonard | Hi #koha |
| 10:40 | PedroAmorim[m] | o/ |
| 10:52 | kellym joined #koha | |
| 11:13 | magnuse | ITMLJS[m]: have you seen this list? https://koha-community.org/sup[…]port/country/#ind |
| 11:26 | paulderscheid[m] | Can anyone tell me how to use $builder->build_object correctly? Is it just class and then a hashref w/ values to fields? |
| 11:26 | db fields? | |
| 11:27 | ashimema | pretty much |
| 11:27 | you don't need to put all values in, just ones you want to be predictable | |
| 11:27 | paulderscheid[m] | Do I have to specify all fields or just NOT NULL fields? |
| 11:27 | Ah, that makes sense. | |
| 11:27 | ashimema | it'll go ahead and build related data and things for you. |
| 11:28 | you don't even need to do the not null.. it'll make data up for yu | |
| 11:28 | paulderscheid[m] | That's so awesome! |
| 11:28 | ashimema | so there's a few patterns |
| 11:28 | people add explicit data using the 'values' param to test against.. other times you use the object accessors and let the random data get autogenerated | |
| 11:29 | I do a mix.. often I prefer the latter as you get more change of introducing weird encoding and odd unexpected data's that may throw an unexpected test failure and highlight a bug. | |
| 11:29 | it's a pretty useful tool | |
| 11:30 | paulderscheid[m] | Thanks ashimema++ |
| 11:33 | TriveniChandriki[m] | IT MLJS: 8861012120 |
| 11:37 | paulderscheid[m] | ashimema: could it be that it doesn't work w/ Koha::Biblio? |
| 11:38 | Because in the ->build_sample_biblio method it doesn't use the build_object method but rather C4::Biblio::AddBiblio | |
| 11:39 | ashimema | yeah.. it's a special cse |
| 11:39 | because the data involved is a bit more funky and not just db related | |
| 11:40 | i.e. MARC fields and index triggers etc | |
| 11:40 | sorry.. I should have highlighted that one | |
| 11:41 | paulderscheid[m] | I just thought I was too stupid or smth 😅 |
| 11:41 | ashimema | the basics will work I think.. but you rapidly get to needing to refer to crazy marc stuff |
| 11:42 | at which point the special method comes into it's own 🙂 | |
| 11:42 | paulderscheid[m] | I need specific field values anyway so the way to go would be to just create a record, add it and delete it after I guess? |
| 11:42 | ashimema | same for Items.. I think there's a special method for that too |
| 11:42 | yeah, that's a good plan | |
| 11:42 | paulderscheid[m] | Alright |
| 11:43 | ashimema | I often start with build_sample_biblio and then use ModBiblioMarc or whatever it's called to adapt it a bit |
| 11:43 | paulderscheid[m] | I already use the ->build_sample_biblio but I also need to check specific string handling in 700, 710 and 711 |
| 11:43 | Alright, thanks for the clarification. | |
| 11:43 | ashimema | oh cool.. nice |
| 11:44 | I've done that a few times.. there should be some example in tests somewhere | |
| 11:44 | paulderscheid[m] | I'll grep |
| 11:45 | Reading the codebase got so much easier w/ the docker extension :D | |
| 11:45 | And perlnavigator of course | |
| 11:46 | ashimema | https://git.koha-community.org[…]iblio.t#L576-L616 |
| 11:46 | 🙂 | |
| 11:47 | paulderscheid[m] | Thanks, that's a great approach! |
| 11:47 | You'll need some more karma for that one ashimema++ | |
| 11:47 | ashimema | hehe |
| 12:24 | caroline joined #koha | |
| 12:37 | khall joined #koha | |
| 12:39 | khall_ joined #koha | |
| 12:57 | oleonard | I just got momentarily very confused about why we have both SelfCheckInModule and SCOAllowCheckin preferences XD |
| 12:59 | Dyrcona joined #koha | |
| 13:02 | aude_c[m] | <Joubu> "aude_c, caroline: https://gitlab..." <- Thanks Joubu! Saw that coming in; logging a bug about the other issue this afternoon. |
| 13:03 | Also do you not have the power to merge your own requests on the Manual? Or was it for us to spot MR 737 coming in? 😄 | |
| 13:04 | caroline | Joubu++ |
| 13:04 | aude_c[m] | joubu++ |
| 13:07 | Joubu | aude_c[m]: it's always good to have somebody else doing a review and merging :) |
| 13:08 | aude_c[m] | Hehe! Someone else who fully understands what you're doing will need to merge it then 😅 |
| 13:09 | Joubu | I've downloaded the PO from pootle (the manual 22.11 project) and added them to the koha-manual project, that's all |
| 13:09 | caroline | 737 seems to be only po files? |
| 13:10 | Joubu | yes |
| 13:10 | aude_c[m] | That's all I understand about it :D |
| 13:10 | Joubu | another pair of eyes to make sure I've downloaded the correct things and that it's the most up-to-date POs we have would be useful |
| 13:11 | aude_c[m] | Thanks for logging the other issues you found too. |
| 13:15 | caroline | So is it only a matter of downloading the files from Pootle and adding them to the koha-manual project? Like when we have to do it from 23.05, we do it manually? |
| 13:16 | Joubu | I had a script for that, from when I was RM (19.05). I adjusted it with the new PO files |
| 13:17 | maybe it can be done more manually, but always better with a script | |
| 13:17 | (yes I need to share it) | |
| 13:20 | caroline | and do you have one for the other way around, creating the strings in pootle |
| 13:20 | ? | |
| 13:21 | With the "one manual" I guess we'd have to update it regularly | |
| 13:21 | Joubu | to push a po file? |
| 13:21 | caroline | to create the po file I think? |
| 13:21 | Like in Koha when we do gulp po:create or gulp po:update | |
| 13:22 | Joubu | the po is supposed to be there |
| 13:22 | with weblate you can easily pull and push PO files | |
| 13:22 | but I am not sure how it works if some strings have been updated in the meantime | |
| 13:23 | caroline | https://translate.koha-community.org/fr_CA/ there is no project "Koha manual 23.05" is what I mean |
| 13:23 | btw this is the tool I was talking about yesterday that we used to use to create the pull requests https://translate.koha-community.org/tools/ | |
| 13:24 | Joubu | I would prefer to not create it, and move to the "one for all" soon |
| 13:24 | caroline | +1 ok! As long as we know where we're going I'm fine with any solution :) |
| 13:25 | davidnind | We had a go a while ago documenting the translation process for the manual https://wiki.koha-community.or[…]lating_the_manual |
| 13:26 | caroline | davidnind++ |
| 13:26 | davidnind | it probably needs some updates (there were a couple of unanswered questions about how the process should work).... |
| 13:27 | caroline | I think now that we'll be moving to weblate, we'll have a better understanding as a group how it works, i.e. more people to ask |
| 13:28 | davidnind | that will be great! |
| 13:28 | Joubu | weblate has a great (well documented) REST API, and a CLI tool. It will be quite easy to automated everything and have our own scripts on top of that |
| 13:28 | caroline | before it was a bit of a "black box" situation where we input something, ??? happens, and something else comes out |
| 13:28 | davidnind | excellent! |
| 13:28 | wahanui | darn tootin' it is. |
| 13:32 | aude_c[m] | sounds so much better :) |
| 13:32 | Bug 34947 | |
| 13:32 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=34947 enhancement, P5 - low, ---, koha-bugs, NEW , Koha Manual search does not bring user to the relevant place in the page |
| 13:33 | aude_c[m] | Also discussed with @Joubu @caroline and everyone in Docs meeting yesterday |
| 14:48 | cait | caroline: around? |
| 14:48 | caroline | yes |
| 14:50 | cait | I was going to add a kohacon24 entry to the website |
| 14:50 | do you have any page you'd like me to link to? | |
| 14:50 | caroline | So far this is the page https://inlibro.com/en/kohacon2024/ |
| 14:50 | cait | https://koha-community.org/kohacon/kohacon24/ |
| 14:50 | caroline | I will update it when I have more info |
| 14:51 | cait | ok, can you check? should be linked now |
| 14:52 | caroline | +1 thanks! |
| 14:52 | cait++ | |
| 14:53 | cait | :) |
| 14:55 | kidclamp joined #koha | |
| 14:55 | caroline | Should I feed you info for that page, on do people just usually go to the dedicated website |
| 14:56 | cait | I think easier to just have one place for people to check - but if you want anything to be added, I am happy to |
| 14:57 | i think we only had the link in recent years, more common now to have separate websties | |
| 14:58 | caroline | ok perfect |
| 14:58 | Joubu | just saying, rangi has the kohacon.org domain, the idea was to add the different kohacons there |
| 14:58 | https://2020.kohacon.org/ | |
| 14:59 | so you could have 2024.kohacon.org | |
| 14:59 | caroline | OK I'll email him |
| 14:59 | Joubu | I guess you can just ask him to redirect |
| 14:59 | caroline | That's what I was thinking |
| 15:01 | That's what I was thinking, otherwise they'd have to give me access and they probably don't want that... | |
| 15:06 | email sent *fingers crossed* | |
| 15:06 | It would definitely look nicer on promotion material | |
| 15:10 | Shane-NP[m] | Is there a check-in method to set status to a particular type for about 10-20 items? Not sure it is worth an import, I just have a pile of damaged items |
| 15:10 | oleonard | Shane-NP[m]: Sounds like you want batch item modification |
| 15:11 | caroline | there is a pref to change the status upon checkin, but like oleonard said, I think the batch modification would be better in this case |
| 15:11 | Shane-NP[m] | Not seeing that on admin or tools....koha logo maybe? |
| 15:11 | caroline | ah never mind about the pref, it's only for notforloan status I think |
| 15:11 | Cataloging | |
| 15:12 | Shane-NP[m] | yep...ty |
| 15:12 | will batch item modification modify last seen? | |
| 15:13 | caroline | probably |
| 15:13 | wahanui | probably is too hard. |
| 15:14 | caroline | this is the pref I was thinking of, but like I said it's only for notforloan UpdateNotForLoanStatusOnCheckin |
| 15:14 | There is also a new one for location UpdateItemLocationOnCheckin | |
| 15:14 | oleonard | Last seen date was not modified in my quick test |
| 15:15 | caroline | do we have a place to document lastseen? I think we were talking about it the other day no? |
| 15:15 | like no one knows exactly what affects it | |
| 15:16 | I could maybe add a section about it in the manual under FAQ | |
| 15:17 | Shane-NP[m] | I like last seen, it helps me know an item was scanned at somepoint |
| 15:19 | I am just curious what is your "removal" process, do you keep item in Koha forever with a removed status, or do you purge items you have to dispose/recycle? Do you keep a secondary record if you do remove something? | |
| 15:20 | oleonard | We delete. We can always dig through deleteditems or deletedbiblio if we have to, but it's extremely rare |
| 15:21 | Shane-NP[m] | I only ask as typically I remove items from Koha, and make a recycled spreadsheet, but I am thinking that is redundant, had I just left it in koha and done something like not-for-loan |
| 15:21 | caroline | it depends on each library, I've seen some that keep the item with "Withdrawn" status for a certain amount of time (usually 1 or 2 years) and then batch delete |
| 15:21 | oleonard | For some lost statuses we leave them lost for a fixed amount of time before deleting them. |
| 15:22 | Shane-NP[m] | hmm...didn't think about that...deleted items are still recorded...I forgot you have the deleted tables |
| 15:22 | caroline | so oleonard you don't use the withdrawn status at all then? |
| 15:23 | oleonard | Not at all |
| 15:23 | Shane-NP[m] | heads the schema |
| 15:23 | caroline | +1 |
| 15:23 | added bug 34948 btw | |
| 15:23 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=34948 enhancement, P5 - low, ---, koha-bugs, NEW , Document items.datelastseen and borrowers.lastseen |
| 15:23 | caroline | I don't have time right now, maybe later in the winter |
| 15:24 | oleonard | Shane-NP[m]: often if we are doing a batch delete of old lost items we will build a report for it first, save the result as a spreadsheet, and then do the delete. Then we can refer to the spreadsheet later if we want to |
| 15:25 | cait left #koha | |
| 15:25 | Shane-NP[m] | hmm...okay I might have to change my process then, looks like damaged notes stay in the deleteditems table correct? |
| 15:26 | ashimema | have you seen bug 15504 caroline |
| 15:26 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=15504 enhancement, P1 - high, ---, matt.blenkinsop, Signed Off , Track Patron's Last Activity |
| 15:26 | ashimema | we're very very keen to get that through.. |
| 15:26 | * ashimema | is bugged that it keeps getting blocked |
| 15:26 | caroline | ah yes, I think that's the one I remembered being discussed |
| 15:27 | thx for linking! It will help for later | |
| 15:28 | I feel you for being blocked... we have a couple like that too :/ | |
| 15:28 | *cough* autocomplete *cough* ;) | |
| 15:29 | ashimema | ? |
| 15:30 | caroline | bug 27113 |
| 15:30 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=27113 enhancement, P5 - low, ---, hammat.wele, In Discussion , Elasticsearch: Autocomplete in search |
| 15:34 | KevinFurst[m] | Checkouts not respecting loan period setting:: When checking out books, a checkout record is created with a due date 3 weeks into the future. The library is set with only a single rule for a 2 week checkout for all patron categories. There is a really bare bones setup for this library; there is only one patron category type and one item type (ie BOOKS). So I don't think it has anything to do with the nesting rules as stated in the |
| 15:34 | documentation. Yet it seems to to want to add an additional 7 days to every checkout. Can someone suggest areas I could look as to why koha doesn't seem to be following my default loan period settings? (Note that in the other library in this instance, all patrons are set to 7 days and it works without issue). Thanks. | |
| 15:35 | caroline | KevinFurst[m], maybe the calendar? Do you have closed days? |
| 15:38 | KevinFurst[m] | We are closed Saturdays and Sundays but we have not marked those days as closed. We just treat the loan period as 14 calendar days. (As a school library, an overdue is not fined so it's not a huge deal if it is late a day due to a Sunday). I've never put anything into the calendar at either library. It's just weird because I would expect the same behavior in both libraries which only have this single rule applied to all patrons. Works |
| 15:38 | fine in one and not in the other. | |
| 15:39 | caroline | maybe circcontrol pref? |
| 15:40 | also homeorholdingbranch if circcontrol is on the item | |
| 15:41 | KevinFurst[m] | Looks like I've got that set to use the library the item is from. So I read that as I probably should go back and look at the calendar of the library where this is a problem. |
| 15:43 | So in reviewing that calendar, I guess I do have holidays marked as unique holidays. However there are no holidays upcoming in the loan periods we're dealing with (ie 14 days). | |
| 15:44 | oh. I think I found it. Thanks for pointing that out! | |
| 15:45 | caroline | check useddaysmode also maybe |
| 15:45 | usedaysmode (one d) | |
| 15:46 | paulderscheid[m] | PSA: For anyone using a macBook: Wait a couple of days w/ the Sonoma update. It is NOT stable 😆 |
| 16:06 | h2 joined #koha | |
| 16:06 | h2 | hello! |
| 16:07 | caroline | hi h2! |
| 16:07 | h2 | Hi, caroline! |
| 16:21 | Shane-NP[m] | paulderscheid: ty, isn't there also a CVE for all version prior to 14 kinda making you think you have to update if you can? |
| 16:23 | https://cve.mitre.org/cgi-bin/[…]me=CVE-2023-41993 hmm...maybe it exists but only mentions exploits in iOS, but Sonoma is listed as fixed. | |
| 16:26 | ahh I found the article, it is iOS, but the issue is connecting to to MacOS leave it vulnerable if the iOS device is unpatched | |
| 16:31 | cait joined #koha | |
| 16:43 | tuxayo | Hi :) Does anyone know how to "have a serial record with issues from multiple years" |
| 16:43 | I can make a subscription for a serial that started a few years in the past but then I don't know what should be done. | |
| 16:44 | caroline | receive a bunch of issues |
| 16:44 | Or I think you can click "create next" (or something like that) a bunch of times | |
| 16:52 | oleonard | Haha sorry tuxayo :) |
| 16:52 | Our sample data needs better serials data! | |
| 17:24 | h2 | We only have subscription records for currently received serials; we create item records for all the older items, then we create a subscription record for the subscription from that moment on, going forward. But maybe that's just us!:) |
| 17:29 | bag joined #koha | |
| 19:19 | khall joined #koha | |
| 19:25 | tuxayo | caroline: «receive a bunch of issues» great we can receive stuff from before the subscription was added, thanks, I'll try that :) |
| 20:21 | khall joined #koha | |
| 20:52 | alohabot joined #koha | |
| 21:56 | khall joined #koha | |
| 22:54 | khall joined #koha |
← Previous day | Today | Next day → | Search | Index