Koha-US SIG - System Admin Special Interest Group, 9 Aug 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: System Administration Special Interest Group - 8/9/2022

Description

Agenda/Notes: https://docs.google.com/document/d/1zlznNa_q63woxTXBP1o1HU9xjQVbqOg30KengJupeSo/edit?usp=sharing

00:12:23 Jason (SEKLS): https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27841
00:12:28 Jason (SEKLS): https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25847
00:18:39 NEKLS Zoom 3 / George Williams: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27663
00:27:06 NEKLS Zoom 3 / George Williams: I already commented
00:27:39 Rebecca Coert (APL-VA): Thanks George!
00:32:16 NEKLS Zoom 3 / George Williams: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27663
00:32:34 Rebecca Coert (APL-VA): https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28863
00:35:51 Jason (SEKLS): https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30230
00:38:03 Rebecca Coert (APL-VA): https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29918
00:39:33 Jason (SEKLS): https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31216
00:42:22 Jason (SEKLS): https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31250
00:43:50 Daniel Gaghan: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31220
00:45:26 Barbara Johnson: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31179
00:59:02 Andrew FH (he/they): OPACResultsMaxItems OPACResultsMaxItemsUnavailable OPACResultsUnavailableGroupingBy
00:59:58 Daphne Hoolahan: Thanks

A

All right so welcome to the august 9th koha us system admin special interest group, as I was admitting to people before the recording started. I didn't do much preparation for this, because I've had a user's group and I visited the conference venue and I had an upgrade last night. So there's a very brief virginia agenda in the chat um the two bugs on there are from rebecca.

A

So hopefully she will show up here a little later, but we will just kind of do our usual sort of freeform thing where we will uh see if there's any reports that anybody has been working on anything cool, you want to share interesting, you've been doing with.

B

Well, I don't have a new report, but I learned that you can probably other people know this, but I learned that you can put comments in your report just like you would with css and it still runs, and that was helpful to me in a certain case. I looked it up and it's like. Yes, you can do this, so that was nice.

A

Yeah, I find that helpful when you like are testing things and you want to you.

C

Don't want to delete.

A

It out totally, but you can comment and then uncomment back and forth.

C

I always forget: what do you use to comment it out? Is it just two back flashes.

B

I used the slash and an asterisk and then reversed on the other side.

A

I should be taking notes. This is why I don't need to be. This is administrative chair.

A

All right uh anybody else, any cool reports you've been working on. I was gonna, pull up mine and see if there was anything in the recently added reports that I've done, that I've forgotten.

A

Oh yeah, my most recently added report is a list of self-registered patrons because someone deleted my self-registered patron report that I have linked up on the front page so not exactly new. um I did write a report to generate a pdf of our kits. I guess I can share that. One.

A

So I have this one called youth services kits list.

A

Because my youth services consultant wanted to be able to um our website's been up and down, so she wanted to be able to have a separate pdf. She could have stored and drive a drive somewhere that she could share with people. um Of course, there's different uses.

D

A

It's very slow, so we'll get there uh anything else exciting here: local circulation by shelf location and a date range not exactly exciting um I've. I haven't. I've been working on reports for logs because people want to access the logs, but I don't want them to access the logs because I'm afraid that they'll crash things. So um all right. So this report came so basically just an image of of the kit.

A

um Then I did a little formatting here with headers and um yeah, some html formatting in the title and then the call number and then she could just highlight this and print it as a pdf and then the hyperlinks are still maintained. So that was something sort of interesting I did. The sql is here and like the title field is just concatenating nh2 and then concatenating the um the description field, underneath so it gives it sort of a different, uh a summarized feel kind of.

A

So that's my most interesting report. I see george has joined us. Have you done anything fun with sql? Lately, george.

D

Maybe I don't know.

C

A

Right um making notes here, so I can add it to the notes later.

D

So that was george, maybe I don't know.

A

All right, so I guess we will move on to our next topic, then, which is bugs. um Let's see what these bugs are, that she sent me bug two seven, eight four one is add unique action. Types to action logs for holds it looks like andrew wrote this bug. So what do you know about it? Andrew.

C

Oh, that's a really good question, not much um that sounds nice.

A

D

What was that number again.

A

Oh, oh sorry, you came late um I'll, put the bug in the chat.

D

Yeah is there if there's an agenda, if you can throw that back in there too,.

A

The agenda is just those two bugs.

D

Oh okay got it.

C

So it sounds like right now in the action launch when you do something to a hold like when it goes to transit, or it goes to waiting. We just put modification, and so the idea I had a year ago- and then forgot was that if we could put like if the action was this hold went to transit or this hole went to waiting.

C

That would make writing a report to find all of the spots in the action logs where a whole winter transitor went to waiting or did a specific action, actually a lot more writable than what we've got now, because right now we just see something changed.

A

Yep- and it looks like rebecca commented on this, so I I think that's a great idea, so I should copy myself on this bug. Anybody else feels the same. Do the same.

D

I've already done it. I just made a comment on it.

A

All right and then the other bug that she shared with us is 25847, which is set the item to cart location when recording local use, with the statistical patron again andrew wrote this one too, like two years old, um so.

A

Yeah, we don't use this feature, but it sounds like it would be nice for, like local use recordings.

C

Yeah, it seems like it would need to be optional because, like I can think of the library where the fact that this got a local use doesn't necessarily mean it's gone into like the whole reshelving process.

A

Right, yeah, yeah, okay, that makes sense.

D

There's another there. I do use the card feature and I've already commented on that bug. um There's another one that I can't think of uh there's an issue with the cart feature where sometimes, uh when you check an item out and the location is cart, um cart gets recorded in the statistics table as the shelving location, and sometimes it doesn't, um and so that's what I have a bug out there somewhere.

D

That says, could we make sure that the permanent location is always recorded in the statistics table and I'll try and look for that and find the number, but it's a it's an enhancement that would be really useful in the in the statistics table because right now, if something does fall through those cracks and get recorded, it gets recorded as being checked out.

D

While it's at cart, then you have to rewrite your reports to to go back and find the data for from the items table or from in some cases the deleted items table in order to get accurate data about where those are searching. So if I find the bug for that I'll pop in the chat.

C

Are any of you using um pseudonymization.

C

I wonder if, if well first, I wonder if this pseudonymized actions table is recording those shelving locations in the same way, statistics is or it's getting it right when statistics is getting it wrong,.

C

I said I think there really wasn't a second.

D

I think when I asked about that specific problem, the issue is that some things don't always happen in the same order when you check an item in and so sometimes when you check the item out, the things also don't happen in the right order, and so sometimes when you do the checkout, it changes that location before it records the use, and sometimes it doesn't because it's not consistent how things happen. I'd like to use the pseudo the fake name.

D

I can't ever say that word. um I would.

E

Like to use that.

D

E

D

Investigated enough, yet to turn it all on so busy doing other things.

C

I told our koha to start recording the pseudonymized actions when I started and- and we are going to ask bywater to then start deleting the statistics table at 180 days once we've got 180 days of pseudonymized data in place.

A

Yeah we're we're kind of bad about data retention. We do a lot of it, so this isn't being recorded right.

C

Even after we've deleted that statistics table, the government can still find out who checked out a book if they want. So are we just complicating our own lives for not much protection.

D

You have you ever watched criminal minds. I mean they can find out your phone number that you had in 1960, with, like five taps of a keyboard.

C

Yeah, they just pull up koh and they keep saying enhance until they want us on the screen.

C

A

Yeah, that's that's something we're working on now um we're reviewing our policies and one of them is going to be patron. Privacy and confidentiality. So we're moving towards that. But at this point we're there's a lot of work to be done.

A

Well, we've um made it through the bulk of our agenda. Next, okay, george for the number uh yeah, that's.

D

The bug for um statistics table should have some way to include items permanent location.

A

Okay, get that in the notes, um are there other bugs that people want to talk about.

F

I'm not sure if there's an active bug, but we've been discussing amongst our team quite a bit about how confusing, because this happens a lot with our libraries. I get very confused by how lost works where things get checked in and that really you know, throws patrons and staff for a loop.

F

So I mean it would be quite a radical change, but we were just trying to wrap our heads around how we could make that. So, like an item didn't actually get checked in where it would just have like a lost status, something like that. Maybe that would work a little bit better than sort of moving something checking something in and moving it over to that lost table.

F

So just wanted some feedback on that.

D

I think it would be nice if you could say that when something you know you can tell it when something gets marked as lost, you can say what status it's going to be marked, as you know, which, which one of the loss statuses it's going to be. I think ours is number two um and it would be nice if you could say when something gets set to loss status. Number two.

D

It can't be checked in or you know, to have some flexibility there to say that this is what happens to different statuses, because we appreciate um you know. I've done several libraries we've, you know missing is one of the lost statuses we have, and so, when you can't find something else on the something on the shelf, your market is missing the way it gets checked in it's not missing anymore and that's super convenient.

D

um So it would be nice if there was a way we could say you know what happens when something is lost status. Number two: what happens when something is lost status? Number three. I think I have like eight lost statuses for various reasons.

E

D

Be nice if they were flexible about what we? What what happens when you you mark them that way,.

C

So you mean sort of the same choice that that you make in that system. Preference uh mark lost item has returned yeah.

D

It'd be nice if that could be controlled at a status by status level.

C

F

Yeah, that would be good. I think what I'm getting at is particularly the the confusion of when something hits that long overdue status, where it triggers and becomes lost that item back does get checked in off their account. Technically now, they're still in the account settings, you see a fee and so there's a record of it, but it, uh but because it's checked in it just uh creates a level of confusion.

F

So I would I I guess I haven't fully wrapped my head around what would be the best way to do it, but I feel like there's a way where it doesn't get checked in, but still retains that lost status. Just so you could see like if you ran a report of checked out items, you could still see that item there. You know, for example,.

C

And that is doable. That's the mark lost items, return system, preference- you could say, don't mark fast items as returned from the long overdue crime. Is that all there is.

C

Yes, but I mean well.

F

No, I we do want it to mark loss, we just don't want it to get checked in. I guess our marked.

C

Return is what you're saying yeah. So it's the system preference asks when I mark something as lost from via this method. Should it also get returned, and so it asks like on the item edit screen via the items tab. We have the long overdue crown and you for each one of those. You can say yes or no do or do not mark things as returned when they become lost, but- and I don't know how much this is going to wreck everything for you, that's a that's. A global behavior.

F

Actually, that wouldn't be a big deal, so the only consequences it would not be returned when it's marked lost.

A

Yeah, so that's how we're set up- and I will say that it creates a lot more um clutter and work for your libraries, because now they're dealing with all these long overdues that are still hanging out on people's accounts.

D

Yeah we do, we have it set so that when something is automatically marked lost, it does get checked in because we have another crown running that deletes those items that have had a lost status after a certain length of time and if they're still, if they're lost and still checked out, they can't be deleted automatically.

D

So we want to get them off people's cards so that, after the the time lapses, they're just automatically deleted and that and it does create problems because we do have people to go well how how come I'm being built for it. It says it's checked in and then we staff just say you know. Well it's because you never returned it. We marked it lost now, you're being billed for it return it, and we can do that.

D

The other issue we have is that so we have it uh so that you keep something overdue more than system-wide. You keep it overdue. More than 45 days it's going to get marked lost on day, 46 and then um 13 months later, it's automatically deleted anything with any loss status.

D

That's at the law status more than 13 months is automatically deleted, and so then the other thing that we have happen is somebody checks it out today, 46 days later, they're billed for it and then 13 months later it's deleted and then they return it and then that creates the hassle with staff where they have to go in and this and they go well.

D

You know now I've got a item that when we check in and says bark no barcode found, and so then they don't know what to do next, because that's confusing too, and invariably they will return these things, not at the library where they checked it out and never at the library where that actually owns the item, it'll be on the other end of the of the consortium.

D

So, ultimately, I think what you end up doing is you lost items, are just a pain, no matter what and you end up trading one set of problems for another. um The thing that we like about this is before we started doing this.

D

We had like 20 of the catalog, uh a 20 of the items in our catalog were marked as lost or missing, because the libraries, particularly the smaller libraries, never took the time to go through the steps to get those items out of the catalog, and so we had this big bloat in the catalog of all these things that were never coming back um and and they're just hanging out there, because the smaller libraries never have the time to do any maintenance on their catalog like that, so so you're.

D

I that's kind of the way I feel about. Is we traded that problem for a different problem when we switched to this method so.

F

What was that uh system preference again andrew.

C

I just messaged you an old blog about it, mark fast items as returned. Okay, great that.

F

Was great, thank you sure. Oh.

C

And if your long overdue behavior is set in the crown line rather than in the co-op system preferences, then this part of it, I think, also needs to get set in the ground line. Okay, because long overdue is like that.

A

I see rebecca you've joined us, we we talked about your bugs. Do you want to say anything about those.

G

uh No just please vote on them or comment or get some attraction to it, because they're just annoying they've been open for a long time, especially the um the cart one. That is one that we constantly run into we've had, I think, last year it was like 110 000 in-house use items, so those are all staff complaining. So it would be great if we could just figure out a way to. It seems like it's a simple thing, but I don't know so that's good to see everybody. Sorry, I'm late.

A

um So, as far as the agenda goes, it was those two bugs so we're just any other. Bugs people want to talk about um things we want to discuss uh on the topic of statuses. I know that there was discussion- I guess your several years back now about trying to come up with a way to make that more controllable and customizable, where you're like defining a status and then defining what it does instead of being constrained by the categories which they live in. um I don't know whatever happened that conversation, but I.

C

Know we had it there, we used your office to pull.

A

There may be a bug on it, but I'm not sure I couldn't find it just googling around uh real quick, but I think that would be a great improvement because, like not for loan statuses, do something and then not for one. If it's a negative, that's something else, and then law status do one thing withdrawn: do something else so um more clarity and like actually being able to manage what those things do would be nice.

G

I had a question for the group: does anyone use a display status? This came up in several of our in-house meetings and they want to determine some sort of display status.

F

I think we have one of our libraries that does that.

A

Use a shelf location in conjunction with the course reserves module which has been heavily modified to handle displays instead, of course, reserves which is going to be my presentation at quaho con. So everybody watch and a tank go hawk on and you can see what I'm doing there but yeah. Basically, it's just a shelf location that we temporarily apply with the course reserves module um it's it's.

C

Like if you want to do like a lighter weight version of a similar idea, you can set up a display, shelving location and then use the oh update item location on check-in system preference to make that shelving location of display go back to its permanent location at check-in. It's really like using the same mechanism as the shelving cart.

C

It requires you to make the permanent shelving location, an editable mark field. So then you can edit an item to make the current shelving location display and leave the temporary for the permanent location alone. Leave it as you know, fiction, so that when that thing gets checked back in it goes from display back to fiction.

C

um As far as I know, there is currently a bug around that editing process right now, if you make a permanent shelving location, an editable field, the koha wants to change it to match whatever you're setting the regular shelving location to, even though you're trying to only edit one field. So you end up having to edit that item twice.

C

That said, bywater should be patching that, because it's a thing, that's broken several times and has slapped various libraries in the face every time it's broken. So hopefully it's like kind of top of mind for them.

C

Thank you for that sure somewhere, I might have a 15-page like tango workload that tells how to set that all up. I could look around.

G

Yeah, I don't know if they want staff editing shelving locations. We were talking about, maybe like using a lost status, so it says display and then when they check it out, it goes to whatever it is and then when they check back in it just goes back to the shelf. But the question is: how do you track?

G

How would you track the stats on something like that? That was the other questions. They wouldn't see how many things are being checked out from their displays. If the displays are actually working and other than a shelving location, I really couldn't think of an option.

D

Shelving location is how several of our libraries do it so.

C

Yeah but then you're going to run smack into the bugs that george linked, where sometimes it records the wrong shelving location.

D

Yeah she wasn't here for that part.

C

A

um Other questions discussion, but I guess we're still on bugs on the agenda any other bugs anybody wants to bring up.

G

I put one in the chat: okay, um this is to cancel a pending notice in coho, uh something that we've asked about several times since we've had problems where things get trapped for a hold automatically generates that notice, and then we realize the item is broken or covered or whatever, for whatever reason that item can't fill the bold and now we take it out, get them another copy, but then they're getting that message. So we want some way to say: don't send this message like just it's pending, just cancel it.

G

um So that's been a request that we've had.

C

And you do one big flurry of messages every morning right september,.

B

So yeah you'd have more of.

C

A like window to actually hit that cancel button.

G

Yeah, we do all of our messages at eight in the morning for message me now so uh yeah we would have a little more time. I know most crown jobs are what 15 minutes or something.

C

But even then I can imagine be like oh dang. I really don't want this email to go out, I'm going to race the crowd job to go; click; the cancel button.

G

Yeah we've been doing this work around for claims, returned and lost items where we actually return the item and then check it back out to them and then place the claims return. But the problem is that generates a new checkout receipt and we don't want to tell them that we checked it back out. We just wanted to go through so sometimes I delete the email and then put it back the next day just make myself a note, but it would be nice. We could just say: don't generate that message and track it.

G

Of course you know so if some kind of log, if we needed to see who was canceling all the messages.

D

I think it's a great idea and it's for some reason another I got bumped out of bugzill and I can't log back in right now for some reason or another, but I'll comment on it as soon as I can. Thank you, the one that I brought up uh a little while ago um at a different meeting, and I'm not going to be able to find it here now, because I'm bumped out of bugzilla for some reason or another um is the.

D

In order to search for patrons in the new version in 211, you need to have modify patron permission.

D

And I can't find the bug for it, but this is a byproduct of here. We go.

D

No, that's not it um in quahog, there's always been two separate ways to search for a patron. You can search and check out or you can search in patrons uh and there were two different searches, and um somebody said: why do we have two different searches? Let's just make it one search which isn't a bad idea, but the thing is: is that if you have a staff member, like I have a bunch of staff members that don't have the, I think the name of the permission is modify patrons or edit borrowers.

D

If you don't have edited borrowers, you can't access the patron search. You can only do the checkout search and now, and so now, um with this next upcoming, uh upgrade in quahog that we have in a couple of weeks. It means that I have a whole bunch of people that aren't going to be able to search for patrons. They will have to have their card.

D

They'll have to have their card number in order to do a checkout search.

C

A

Think that bug that I put in is the one that george is talking about.

C

Great 3-0-2-3-0.

D

And it's another andrew bug.

D

Yeah this bug one five, eight one two made searching for patrons uh use the regular patron search. But if you have circulate but not edit borrowers, then you can't you can't do a patron search anymore.

D

So that's a problem.

D

So if a lot of people comment on that, that would be really useful.

C

So we have a another library in town that is also on koha and we have very limited access to their koha to occasionally check things out to their patrons. So on their system. I have view borrowers, but not edit borrowers and yeah. I could, if I type in a last name, if that gets me to just one patron, it will take me there, but if it tries to take me to a search results page, I get a permissions error.

D

Yeah it just uh it just bumps you out, and it says you don't have permission to do this. It doesn't say it. It's not a very helpful error message. It's just that you're just back at the login page, so.

A

All right, any other bugs you want to draw attention to.

G

I got one more cool, so this is something I noticed when we were doing pushing for expiration dates for covid, and I wanted to create a way that all the do all the expiration dates weren't on the same day, if that makes sense, so I'm asking to add a add a number of days to the expiration date, so you could say like 60 days and then everyone would just move out to their 60 days past their expiration date, which would sort of uh make it a little more workflow friendly, because we had some that had like a thousand or two thousand expiring.

G

On the same day, which I had to move out manually, um it took me two days to move out all of our patrons by hand. So if we could just add, you know some sort of like it's, I think it exists already in. Let me read my pick. It's been a while, since I've done this um with the batch extend due dates function, it already exists that you could add three extra days to your duty or whatever so seeing something like that on the patreon expiration date. Push would be really nice.

G

I have a lot of like just sitting there bugs so thanks for everybody for commenting.

A

I guess I have one I can plug too. um This is dealing with inventory the. So at this point, when I do inventory, I can only upload about a thousand barcodes at a time. um Otherwise it's a proxy error. So this is uh some improvements to making that work better.

A

It sort of invalidates the inventory rule at this point or tool, because um you can't do those comparisons.

A

You can't, if you're only doing a thousand at a time, then it's saying the other ten thousand barcodes are missing, um so you lose some of the value of using the inventory tool so that I've linked that bug out there as well.

A

um If there aren't any other bugs, we can move on to the issues portion of our agenda. um Does anybody have any outstanding issues things you want to talk through workflows.

A

Major problems, minor problems.

A

You want to talk about your co-workers right now and then well, they're, not in the room.

A

B

I'll point out that if you use the advanced cataloging editor- and this probably occurs in other places too, but there's and I'd have to look it up- there's some new um behavior. I guess that clears out cookies.

B

So we always use the advanced cataloging editor and we have that's the system preference set to enable and previous to the upgrade. Every time I would go into cataloging, it would take me to the advanced cataloging editor, but now there's some kind of clearing of cookies or something so now.

B

Every time I go into the advanced cataloging editor, I get the basic editor, even though I have the system preference enabled and then I have to you know, click on the settings and change to the advanced and then it'll stay that way throughout my session, but once I log out of coha and log back in and go into cataloging, it takes me to basic.

B

So um I'd have to look up the bug, but I worked with lucas and he did create some jquery to make it so that it would stick on the advanced.

B

But for that particular I I assume there was a reason that that behavior was created for other things, but in that instance to me, if I have a system preference enabled to do something, then I expect it to do it all the time and not take me somewhere that I really don't want to be um I'll see if I can find the bug.

A

I think it's the one I just put in there 31 cool 50.

E

So have you guys heard about the or ran into the bug for it's, uh you export one label to pdf and it it blows up the label export tool.

C

I think I read that, but don't remember the details of it.

E

Yeah lucas eventually gave us a a fix for it, but it's when you try and create a label in the batch, and you select only one label and you export it, and then you try and download it as a pdf. You get a 500 error and it's been fixed for 22.11, but it's just it's something. Our catalog was ran into and um brought to my attention and you know brought it to buy water and buy water fixed it. So if you, if you notice it, there's a fix for it just talk to them.

E

Actually I can, let's see if I can put it in the chat.

F

I think we had that issue um and related to it completely. We had something else that wasn't also contributing where our label creators were completely not working whatsoever. So but they applied a fix last night and it seems to be working this morning. So.

B

Another issue that we ran into is we were adding some donated copies of popular titles, so I would normally go into the item. Click on it to duplicate the item. You know bring forward some of the stuff quickly. Add my barcode, I'm I'm done so. I realized that I'd done a couple of them and I all of a sudden, looked and thought. How can the item that I just created have 47 checkouts and 77 renewals?

B

That's how does that work, and it was the same number from the base record I was using to duplicate from so apparently it is a bug and see.

B

I've got a ticket on, I'm not sure if we rep for yeah, I think it's um 31179.

B

And there's supposed to be a patch um coming, but that was really surprising um to me, so I stopped using that because I don't really want to want to see that something I just added has all those checkouts.

A

It sounds like a great way to increase your circulation statistics. I pad your numbers hard.

B

Yeah and confuse you when you're, trying to weed things and you're like how did this check out that many times.

A

E

Yeah I've got a question for folks. I remember a while ago um talking to might have been. Actually you andrew about the view, items, checkout history and the information on there not being very accurate. Is that still the case.

E

C

I mean you've still got two spots in very close proximity to each other, who are given two different versions of an item's checkout history, and I think that's probably what what what you and I may have talked about in the past, um because you get the one spot that gives the items.issues count that it's just that like incrementing lifetime, checkout count and then you've got another screen that counts the checkouts for that item in the old issues table and those numbers just don't tend to match.

C

In most cases like your items will have migrated in with account of checkouts from your previous ios and so that'll be in the items.issues number, whereas the old issues table is probably only ever checkout that actually happened in coho.

E

Okay, yeah, I was, I was telling my staff, the staff here to use the just the total checkouts and not go to that. That view item check out history page because one it's it's really confusing and too it's like the numbers are dramatically different, so yeah just want to make sure I was still on the same. The right page.

C

I think you are, and I think that the larger number is the more accurate number over the entirety of time.

A

Yeah, I generally discourage people from looking at that page at all. It confuses them about transfers too, because it'll say, like it's been in a different location and they'll. Think what that's going on here so yeah. um We don't rely on that. One.

A

All right, what else do we want to talk about other issues, bugs topics.

B

Well, I have another one that um in the opac.

B

It would use it used to say, like maybe I have um in the on the results page. I have two items checked out with one on hold that kind of thing, um but now it basically, if that's the case, it'll just say no items available and it it doesn't give the same kind of detail that it used to.

B

um So you can't tell let me see if I can find.

B

Maybe while I poke around somebody else, can talk about something else and I'll see. If I can show an example of what I'm talking about.

E

You know actually just occurred to me. um The news: is there a bug I can't remember, but the returns claims return. The little message that pops up when you check into claims returned and that message to resolve it, pops up, you click on it and then you resolve the claims return, but that message box still remains, and I was wondering: does anybody know if there was a bug that was submitted for that? Or is that something that that people want, because it just seems kind of uh it- should go away? That's basically what I'm saying.

A

I was looking for bugs, I don't know, there's one about automating, but I don't think it's the same thing. We don't use claims return. So I can't I can't comment on that.

G

Daniel, what version are you on.

E

We're on 21-11.

G

Okay, so it's not fixed in that one. I think.

E

G

Yeah we're behind everyone so.

E

It was added in this one and that's why I was like hey go away, so I thought it was a cool feature, but then it just doesn't appear.

E

Yeah 21, 11, 05.,.

A

G

A

Like a valid bug, if you want to file it sorry go out of rebecca.

G

Oh, no, I was gonna say we're still in 2105., so we're a little bit behind everyone.

A

We upgraded last night and I only had to fix fix.

A

I only had to fix one broken jquery and then I went um and hid barbara's cool new feature that lets us batch delete hold because I didn't want my libraries to do that and I had to hide the main contact information thing on the patron form, because I already have a patron attribute for that.

A

Oh, I had broken jquery in the news too, because I auto default that to the flip, because that's generally what we use it for and the home library so that they're not putting things on other people's slips, but the news page had a bunch of like html changes. So if you have custom code on that, make sure and check in that, um oh and then the course reserves module has the ability to add things to course, reserves by bib number now, which we don't need and that just confused people.

A

So I have to hide that too. So that's been my upgrade experience, hiding all the cool new things that we got.

E

Yeah, I was happy. I only had to fix one one finance report with the account line changes. Usually when that happens, it's like every port needs to be fixed, so it was just one so pretty easy fix.

A

That makes it that's a good indicator of a good upgrade.

F

A

Had all sorts of stuff.

F

Break but oh no at least the spine labels fixed. uh We have like auto renewal notices that stopped going out. We have everybody, has the ability to edit other people's items and I'm not sure why other people aren't reporting that I guess something about our setup is unique. That has caused that. So I don't know we have a few yeah a number.

A

Of ours has always been wide open on editing items. That's been on my to-do list forever to write some jquery for that, but it sounds like. Maybe you have that and it broke.

F

A

F

That previously- and it was beneficial because people will like look at somebody else's call number and like get angry at it, because they think it should be some something else and we don't actually want them to change it. Because the thing on the spine doesn't, you know, have their ideal. uh No.

A

Ideal for what that book anymore, as long as it looks right in the catalog.

F

So the other thing that happens is um when that exists is, if you just want to you, you can't, because you can't edit anybody else's item, your items go at the top, and so it's like, if there's we have some items that have like or some bibs that have over 60 items and so having that float to the top is super handy.

F

So uh there's a few things but yeah, I'm not sure exactly. We haven't got a lot of feedback as to why that was working and all of a sudden isn't, but I haven't seen a whole lot out there that that's happening to other libraries.

F

So some combination of our setup is, you know, ran afoul of this update in a few areas. That's different from others.

B

Well, I found um in my I was going to try and find a live example of what I'm talking about, but I did have some stuff in my ticket, so I'm gonna share my stream. Hopefully.

B

Can you see my screen.

B

Yep so the first two titles there are um an old pre 21 11 display, so it would show that there were no items available, but you knew that there were four items, so you can tell there are four items owned by the library but they're all checked out and this one you know two checked out one on hold at the time I looked at these in 2111. They had similar checks at checkouts and holds, but all it says is no items available, so I don't know how many items are owned by the library.

B

I just there's just no items available, um so I've got a ticket on it. I you know when I looked at this, I'm like it didn't used to be like that, and I that's why I had to go back and find this was from some other ticket a long time ago. I guess- and I was able to find this is how it used to display.

B

um But now you just don't get any more information without having to actually go into the um title.

A

Seems like an xslt thing, yeah.

B

Lucas is looking at it and I need to follow up um on it.

A

Yeah I'm looking at my oh back. I don't see those either, but I don't.

A

Yeah, I don't know how long it's been gone either, um but mine like I, have one that's on hold for sure. That just says no items available.

G

A

C

Barbara, have you looked at all at the system: preference opac results max items.

C

It's a system preference. I have not I've not ever looked at before. I was just looking to see if it was new or just something I have ignored, but it does have ss gives a number of show no more than blank unavailable, individual items, so maybe that's somehow getting enforced differently than it used to and showing unavailable items differently than it used to.

C

I don't see any bugs about it, though,.

A

What what was that? Scissor preference andrew.

C

The group of three- you know I'll put them in the chat.

A

Okay thanks, I was just gonna get them in the notes.

A

Awesome. Thank you.

A

So we've got about six minutes left. What else do we want to talk about anything.

A

System administration means everything koha, I think so nothing's off the table here.

A

Seems like crickets, I think that it's a good sign. That means we we got everything out we needed to so um we will go ahead and call this a wrap and see you guys next month. Thanks everybody.

G

Thanks everyone.

B

G

B

If you haven't registered for quahog con remember to register.

C

Thanks everybody.