Koha-US 2023 Meetings, 12 May 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: koha-US May 2023 General Meeting

Description

00:13:00 Fred King: Lauren, we hardly ever bite.
00:13:23 Jennifer Marlatt: https://docs.google.com/document/d/1Gck0YOXJeZmzcTobPmmypYHlFslnfRVhKpxjrnjnciM/edit?usp=share_link
00:14:52 NEKLS Zoom 3 / George Williams: https://www.libraryjournal.com/story/christopher-brannon-and-george-williams-movers-shakers-2023-innovators
00:15:00 Rebecca Coert - APL-VA: Reacted to "https://www.libraryj..." with 🥳
00:15:11 Jason - SEKLS: Reacted to "https://www.libraryj..." with 🙌
00:15:12 Michelle - CLAMS Library Network: Reacted to "https://www.libraryj..." with 🥳
00:15:15 Barbara Johnson - Bedford: Reacted to "https://www.libraryj..." with 🎉
00:23:41 NEKLS Zoom 3 / George Williams: Robin is at a conference in Colorado this week
00:29:06 Fred King: webchat.oftc.net/?channels=koha
00:30:46 Michelle - CLAMS Library Network: Thanks Fred, I still haven't logged onto IRC yet
00:31:06 Michelle - CLAMS Library Network: Slack would be useful for newer people like me
00:39:38 Bob Bennhoff: https://forms.gle/LJvzhiGoQG4qb4mq8
00:39:41 NEKLS Zoom 3 / George Williams: IRC Logs https://irc.koha-community.org/koha/
00:42:08 Lauren Denny: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33353
00:44:24 Lauren Denny: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25439
00:46:59 NEKLS Zoom 3 / George Williams: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25669
00:50:47 Christopher Brannon: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32985
00:53:06 Fred King: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32386
01:01:13 NEKLS Zoom 3 / George Williams: https://bywatersolutions.com/education/monday-minutes-adding-web-pages-in-koha
01:02:07 Christopher Brannon: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33462

A

All right now we can get underway. Thank you for your patience, everyone ah all right! Well, we are officially going here this lovely May morning. uh I am Christopher Brannan with the Coeur d'alene public library and the Cooperative Information Network, and also the 2023 uh koha US president and I'm gonna go around the room and have people do quick introductions so Fred you're. First on my screen.

B

ah Fred King uh Medstar Washington Hospital Center in DC, I'm, unsupported user and I I'm, probably going to do yet another presentation on how to on being an unsupported user at least why to submit a proposal for it.

A

All right, Bob.

C

Oh Ben Hoff Aspen cat services manager, that is a consortia located in Colorado I'm, also the vice president of koha US.

A

Rhonda Help Me Rhonda.

D

Just for that no um um Rhonda, Kuiper, I'm, Technical, Services and collection development manager at Round, Rock, uh public library in Texas and uh past president and I lead the Acquisitions Sig. So if you have questions about active positions, join us every third Tuesday.

A

To learn more all right, Georgette.

E

Georgette Rogers Liberty life, Library uh part of the uh cin consortia and I am the treasurer for the Quahog.

A

F

I'm Barbara Johnson technical services manager at Bedford, public library in Texas and past president of profile, us.

A

Great George.

G

I'm George, Williams and I am currently muted. I am the next search catalog coordinator at Northeast, Kansas library system.

A

H

A

H

I am the secret Bank coordinator at the southeast Kansas library system,.

A

I

Hi I'm Michelle spinney from the clams Library Network and we just joined koha, uh February 27th, so we're new to koha and Aspen, so just trying to join as many uh meetings as possible to get to know everyone. Thank you welcome.

A

J

Just in time, um I work with um a international Consortium, timworks Library Consortium, all over the world. Doing a little bit of everything. uh I just took on the responsibility of chairing the kill, High U.S circulation meeting that's happening tomorrow. Please come because I know little to nothing again about circulation, so I'm keeping this meeting alive so that I can learn about circulation. So I need everyone to come and teach me.

A

Well done and thank you for sticking your neck out. There.

J

Rebecca I'm just praying nobody chops, It Off.

E

I'm Rebecca Court I am a co-ha person at Arlington, Public Library in Virginia.

F

A

Last but not least, Jennifer.

E

Hi I'm Jennifer, um but the corona public library and I am the koha U.S Secretary.

F

A

All right, we're gonna, get ourselves underway here, um secure checking.

A

G

Anyone put a link to the agenda and I was.

A

Just going to ask Jennifer to put the link on.

A

E

She'll get that out there. Thank you, Jennifer.

A

And um all right, so we're gonna open up with uh announcements. Does anybody have any announcements before we get into our agenda.

G

I think it's worth putting it pointing out that in the new edition of Library Journal, there is a really great book review on page 75 for a book called whale fall by Daniel Krauss I just wanted to mention that.

A

All right well, thank you.

G

There's a set the centerfold on page 28 isn't bad either it mentions Quahog 15 times.

A

All right anyone else.

A

All right so uh on to new business uh first thing, uh Lauren had already hinted at this uh circulation. Sig is going to be underway uh soon and Lauren. Can you tell us a little bit more because you're, not the only uh host of this sig.

J

um John is working with me to um co-chair this.

J

If no one brings anything we're gonna talk about how his Consortium has been using Patron templates and permissions, um and how all that ties in together, uh we may do a shout out for bywater's new video on what's coming in 2211 concerning that as well. So I'm not sure if his Consortium has moved up mine is not so I'm still waiting anxiously to hear. How is everyone handling 2211 what's coming, so that's what we will be talking about.

A

Great all right- and you are meeting uh remind us again- uh it is.

J

The second Thursday 11 A.M Eastern Standard.

A

Tomorrow, all right, fantastic and that's 11, A.M Pacific Central. He said Central, Eastern, Eastern, okay, 11, uh Eastern, all right.

J

It's the same time same as the cataloging group just a week later that 11 time slide is like the time for the majority of kohai us meetings.

J

So now you just keep the same time just to rotate the day.

A

All right, you did take a poll, so it appears to have been a popular time so.

J

That one won all.

A

Right well, um Speaking of meetings. um The education committee is going to get back underway, I am uh stepping in as chair for the education committee. We have several uh topics that we're going to be talking about now. uh This month's meeting is going to be held on its regular time on uh next Wednesday um and I. Had that information up um it is next Wednesday at oh.

A

I want to say, uh you know, I'm not going to say it I'm going to I'm going to look it up. uh I, don't have these things memorized.

H

A

H

Same time as this meeting, if that helps Christopher, oh well, thank you.

A

H

A

Do know it's before our Consortium meeting, which means nothing to anybody else, but uh yeah, so it is on the calendar, 10, 30 a.m and I think that's yeah central time so 10 30 Central, so um yeah. We have a lot of things on the agenda: we're going to um adjust or focus a little bit plus we're also going to send out a poll after that meeting uh for a new meeting time just to uh to make sure that that is the best time for everybody to meet.

A

um We've got a lot of people in the uh message group that uh we don't have a lot of those people coming to the meeting, and so um I am going to put out a poll to see if, if there's a better time so that we can get more of uh interested parties uh involved and attending um so yeah. Please come to the meeting if you're interested in the education committee, the education committee I I feel like is you know one of well, it is one of the key uh driving forces.

A

Our development is one of those key driving forces behind koha. Us education goes along that with that, because we are, we are driving education. We are driving development through koha us, and so the education committee is going to help steer some things. We're going to look at some of our focuses and see if we can't uh make some movements forward in what we're doing and be a little bit more active uh in uh koha overall. So uh please come to that meeting if you're interested in in uh being involved in any way.

A

um That's all I have to say about that, so there. um The next thing on my agenda is the.

A

I lost my agenda just a second here there it is, uh is koha US slack workspace, so I had put out some um some ticklers about this in slack and also uh in a list uh talking about the koha US slack space. We have a slack workspace just like why water has one for their partners.

A

um The koha US slack workspace does not get a lot of um uh use uh lately as of late um last year we had a lot of use out of it, but this year seems like it's just kind of off people's grids. I see a lot more activity going on in the the buy water by water. Partners workspace I wanted to open this up for discussion, because I'm wondering if we need to repurpose this or yeah um or kind of change gears uh I was kind of thinking. You know, I I want this.

A

I want to have a space where we can all come together and and talk. You know outside of uh email listsers. You know if there's something that you want. You know. If you want to see if somebody is available right away for discussion, you know, Splat slack is uh pretty good for that. I am not you know, I've used IRC, but IRC has just kind of hit and miss you can't I I, it's not as user friendly, as slack has been for me. I, don't know about any of you.

A

I like I, like slack I like being able to use it, but um I do want to have it a little bit more open to uh people in general, rather than just specifically Bywater Partners or just specifically us members, and so my idea was to you know, have something that is more cohort. Community Based.

A

um It was brought to my attention that there is a koha community workspace out there, but it is largely unused, but I did find out that Robin is actually um the one that that owns that workspace and um so.

G

Robin, as in Robin Hastings,.

F

G

A

So does she know that yes, she's, the one that told me that so so uh Robin owns that so um I I, you know I was thinking of re uh reworking the koha U.S workspace for something like this, but since there's one that already exists, I'm I'm kind of feeling like we need our workspace, really isn't accomplishing anything. I think it's just kind of dead space I think that we should just terminate it because I don't want to have a ton of workspaces out there.

A

That people aren't hanging out in uh I would rather breathe some life into the Quahog Community workspace and if Robin is willing, uh um let kohai us manage that, um but I want to have I was hoping she'd be here, but uh I want to have that conversation with her, but I also want to have that conversation with all of you and to see what your thoughts are on that because again, I don't want too many competing things and within you know, within those workspaces we can create channels of specific topics, uh different areas, and we could have a koha U.S uh channel in there.

A

If we want it, but uh really you know, I I just want to Foster communication within the community all together and so I want to see what uh you folks. Think of that. If we went that direction.

G

Well, I can tell you how we ended up with a koha U.S. Specific uh slack workspace is when I was the president of koha US in 2019, we joined uh techsoup and we got all of the tech soup stuff squared away, and we got all of our 501 3C documentation taken care of with them, and uh one of the offers that was made by techsoup was hey since you're 5013c you're eligible for a fully funded professional plan.

G

At uh slack, do you want that and I just said yes and it the fully funded slack for non-profits, um one of the fallback one of the drawbacks of it? Is it has a limit of 250 members after 250 members, you can get a discount price on their normal rate, which is eight dollars per member per month.

G

So it's not feasible for us to continue to open it up to the whole community at that price, but it is not difficult if we wanted to just continue using that space and open it up to the entire community.

G

um It's not that difficult to say, take us off of the um professional version and put us onto the free unpaid version.

G

We would lose a few um uh features features of the professional plan, but they're features that we're not using anyway, because right now, really it's only been an Avenue of communication for the people that are on the koha US board or who have been on the koi U.S board at some point or another, so we're really not using it to its full potential, um and now that we know that Robin owns, uh you know is the one that created um Community or community.com or whatever it is um I can't imagine that she wants to hold on to that and not open it up to anybody who wants it.

A

H

G

A conference in Colorado this week, so she that's why she's not here.

A

Any other comments or thoughts or suggestions.

H

I I've shared some of mine with you Christopher, but I I. Think that um if we're gonna do it I think using Co-op Community as the main one makes sense and dissolving the US wouldn't make sense.

H

um I know that there is a koha, not quadash Community, just koha um slack Channel out there, I I think the Swedish users group has that and I know that there's Co-op conversations that go on in there. So um I don't know. If there's going to be any sort of conflict there um and I know that the community at large at least the developers, aren't totally cool with using a paid product to develop an open source product.

H

So you may get pushed back, but um I think if you sell it as a place for people to get together and talk, not necessarily just not for the development portion, they can still use IRC for that. um But um I think that it would it it's a great idea, because I think that all the support companies out there have their own slacks and um people are getting left out of conversations and I.

H

Think if we have a central place that everybody can get together, we can still have those Silo tax blacks around but um like a main chat channel would be huge for people like us who don't hang out in in IRC all the time.

H

um I think there's a like a loud minority in the IRC that would be against it.

H

That's my two cents.

A

And nobody's forcing them to to join it, um but yeah I think you know I think it's important that we have something: that's user friendly, I! Don't think you know irc's okay, but it feels a little technical, a little bit more complicated than slacks. The slack is more user-friendly. In my opinion, um I I like being able to have it on in the background and things pop up and um Iris. You know I, guess I guess you can find.

A

If you can find a a good app uh to handle IRC, you might be able to find that but I I, just like the feel of slack and yeah, it is a paid product, but they also, you know, run it. You can uh do a free version like what we're looking at and do what you want. You know we we can't, we can't be completely open source. You know we want to push open source, but we can't be completely uh open. uh Source I mean we're doing a lot of Google stuff.

A

uh I haven't heard pushback on that. um So you know it's it's. You know you use what works uh you use what's available and you know you know if we can use slack, whether we're paying a little bit or enough. Nothing. So be it. You know, let's use what what's available out there and um I don't want to get my nose up about you know. uh You know this product is better because it's free or it's open source or you know you know we.

A

We need to use what works and slack has been popular and and uh works well, and so.

H

The other thing is you may like, if, even if you get the conversation rolling in the community, you may find that maybe someone out there is already working on this, because I know that they looked at an open source version of slack in the past um that could interface with IRC so like it would bring that IRC channel into the into the conversation as well. So if you I, don't think we should do this in in the darkness.

H

I guess is what I'm saying like if you're gonna snatch up that Coho Community slack Channel I, think you should put it out to the community and say Here's. What we're planning is that cool with y'all um before we just go and do it that's I, don't want to ruffle any feathers. I, don't I'm! I I lived through the um Americans are bad era of koha. When, when the trademark tried to get snatched up so I don't want to I, don't wanna um roster any bad.

G

Blood, that's what I was going to say as well, I think, um rather than just immediately abandoning and getting rid of koha us Slack um put it out there that we want to start using Quahog or community.com Slack whatever it is, that Robin has and if there's a huge pushback against it then say all right: we won't call it koha, Community, we'll just call it koha us and I'll be open to anybody, and um that way we won't get any pushback from the community about saying we're we're stealing the name of the community, even though some like 10 people in the community hate the idea.

A

But you know and I don't see it as stealing I mean, uh but.

G

But I I don't see it as stealing either, but there's some people that might Robin.

A

Started it and it is koha Dash Community is the workspace and you know if it's truly a community thing it doesn't. It means that no one person has ownership of it. You know koha us just wants to to help facilitate it. So you know I I, don't you know if people are going to get their uh feathers ruffled because of of something they're going to get their feathers ruffled because of something we can't please everybody in the community.

A

But our goal is to you know open things up within the community so that we can have discussions and uh pull more people in uh to those discussions and get more people involved, and you know so, yeah I think you know. Maybe some developers might you know, be ticked off about it. I don't know, but yeah I I will have that that conversation I will put that conversation out there I'll. What I'll do is I'll, throw it out into into the list serve uh the koha community, listserv and.

G

I'm just kind of thinking back to that time, when koha n a became koha us, because one person complained that we weren't we weren't allowed to speak for all of North America, so koha in a bad koha U.S, that's okay, because they weren't in the U.S yeah.

A

And you know we have not, you know, although we limit our, you know, conferences to the U.S region, we have not limited anything else to the U.S, so um you know yeah people, people get upset about things.

G

Well, I'd be willing to go to Saskatoon for a conference.

H

Yeah, if they put in a proposal, I mean we were always open to that. We just told them hey. You know. Most people aren't going to vote for that because they can't travel there, but yeah.

G

I go to Belize.

A

F

Think I I'm still waiting for.

A

Us to to have a a co-op conference in Hawaii, so.

G

I talked to some people from Alaska earlier this week that were interested in koha. So may we go to Anchorage like in December.

B

Yeah, that sounds good, there's also about KOA installation and none of us.

G

Yeah I know that would be so cool.

B

In many ways oh and I put the I can get to uh the IRC uh Toy channel from Firefox I put the address in it's in Firefox. It looks kind of like um chat, does in um Zoom I'm, just not quite as well. It's in Courier towns.

H

Well, I think part of the problem with IRC is everybody's, already kind of migrated to slack their own little slack holes, and not ever it's been diluted already so I think we need. The goal here would be to bring everybody back together like have a central place, that people go and I think that's a something that's missing and would be a great Boon to the community. If people use it yeah.

G

I I agree too I uh Jason mentioned the uh open source, slack alternative, it's called Rocket chat and the big difference between slack and Rocket chat is that we can. We could conceivably do rocket chats. It is very similar to slack, but um as an open source product we would need to put it on a server and host it.

G

That's the big drawback is somebody would need to take responsibility for setting it up for setting up a server somewhere virtual or real, uh putting it out there on the internet and maintaining it over time, so that.

H

G

Think is the biggest drawback of Rocket. You.

H

Say that the drawback, but to some people, that's a not a drawback, because then all the data is on a secure server, not on slack servers and I. Think people might like that more and I think you could possibly get buy-in from one of the support companies to host that. If, if we like help sponsor it or help administer it, that sort of thing right.

G

But uh I'm certainly not going to offer to hosting to host a server here and that's what I think for us in this group. That's a horrible.

E

G

Nobody wants to do that, except maybe Fred.

B

um Just thinking of ways that uh it could be done.

G

um But I don't think anybody here really wants to pay for another server, um but if somebody out there does want to do that. If, if this conversation starts that conversation, um then that's cool with me, too um I think the last time I remember, reading uh being in a discussion on the IRC about rocket chat.

G

um The conversation really was well. Why do we need that? We've already got IRC.

G

But honestly, the last time I went to the IRC there's nobody there anymore, really, except for a handful of people that are there all the time and never log out, and you don't really even know if they're there or not right, um the number of messages in the IRC has really really Fallen um and the amount of activity the the.

G

What used to be the monthly koha meetings are now really irregular and when they do have them, you know it used to be when you would go to an IRC meeting, a monthly meeting there'd be like five people there. Now um it's like quarterly and there's three people there. It's that there's just not a lot of activity going on in the iris.

B

All right, yeah I'm, looking at the list of who signed on to it or IRC. There are a lot of people, just not many people contributing.

B

Half a dozen because.

A

They're having a meeting today, the.

F

A

As to how we should proceed so I appreciate everyone's input, does anybody have anything else to add before we move on.

G

Right um I will um I'm giving it up now. I will put a link to the there's. uh All of the koha IRC chat is indexed and I'll put a link to that index. So you can see all the chat history from the IRC, so you can, if you want to take.

F

G

Wants to see what conversations have been taking place, I'll put a link in there for people to find that.

A

Thanks George um so before we open up the floor for General discussion, I just wanted to uh mention one thing uh that I didn't mention any announcements is that um our uh we have uh updated the the conference website. uh The graphic in the background is our theme explore the possibilities uh that conference again is September 20 through the 23rd in Portsmouth, uh New Hampshire, we're hoping to see a lot of people there and hopefully some new faces and um uh the Bob just opened up the uh the call for presentations.

A

So if you have some great ideas, something to help us explore the possibilities, please uh submit a proposal for a presentation. um We have some ideas uh in the form uh to help guide you. If, if you do not know what you would want to necessarily share, um uh we.

E

A

Steer away from uh uh migration stories try to help uh steer people towards you know what our theme is. You know what has what has uh koha inspired you yeah: uh where has it taken you and where do you see it going? uh Those are the you know, that's the direction that we are going with this year's conference so um check out the website.

A

If you haven't already uh there's a lot of information on the venue and Portsmouth uh the host just knocked themselves out in providing us information, a lot of travel information so start booking uh as soon as you can and we'd like to see as many people as possible participate in this presentations kind of Let's uh nudge, a buy water out a little bit, make them work to to get a spot for a presentation so um yeah. Please join us looking forward to that. I.

C

Did put the uh proposal form in the chat so thus far, which is not a surprise. We don't have any yet people weren't waiting to uh with a ready with their presentation. Quite yet, but hopefully we'll get some very soon.

A

And that uh the the presentation proposals are open until June 14th. Is that right? All right, that's correct! So you got a little bit of time all right. So with that said, we're gonna open up the floor to General discussion. Anybody have anything exciting going on or any uh thing with koha that you want to bring up talk about.

A

If not, I have plenty of things to throw at people.

B

Well, uh Lauren did I know we discuss the cataloging. um Remember, has anyone brought up the problem with elasticsearch in the general meeting.

J

Elasticsearch eight I put in a butt I put the bug number.

J

The elasticsearch I think six is what most people are on and it will become not supported by the Alaska search community.

J

um Our Consortium won't move to Alaska search until koha Works, its way to like the most current Alaska, search and I understand. Why add something that's going to be Obsolete and no longer supported in six months.

J

um So this is the bug that they're working on does. Anyone else know like: are you on more recent versions of Alaska search.

B

Yeah I'm using uh 2011 with elasticsearch sticks, but there's the also also the problem that it might not be open source.

F

B

Much longer which.

A

Really, yes, well, that sucks.

B

Yeah, it's still going to be free, just not open source that.

G

Might mean forking it.

E

A

Yeah I could see that happening.

B

I'm, just looking at the bug, we'll learn, posted um yeah, I think it's the one I saw were they uh someone's mentions yeah that it may not be open source.

B

It's very murky, I think with the term he used.

A

Yeah so we're in six point something in uh I'm surprised, they're, not even in seven yet.

J

F

Are you also supposed.

J

To debug for elasticsearch, seven.

H

um They do mention open search, which is already like a forked version of elasticsearch and I. Think that's what they're looking at now! Maybe.

A

Maybe that's why there's a hold off.

F

B

Anyone know that open search, I, really like elasticsearch it's made putting in well make it's made. Koa uh make sorry it's made. Making KOA do things that wasn't intended to do, which seems to be my specialty uh much easier.

A

I think the big thing is going to be. You know whether or not we have people in the community that we are that we are familiar with and can communicate with, that are involved in the open, um open source, uh inelastic search that would go over and continue in into that Arena because I mean, if, if you don't have people that are building on it and and uh people that are involved in the areas where we need people involved in then it might cause a stall I. Don't know.

A

F

A

So um version six is gonna die out and six months.

J

I, don't remember the dot the timeline, but it will no longer be supported. You can still use it right at your own risk right.

A

You know you don't want to stay in stuff that isn't being supported any longer, because there's always there are always things that need to be fixed up and tightened up.

A

A

F

A

uh Let's see here.

B

G

I was just gonna say that there I'm gonna, put another bug Link in here. um That is another elasticsearch bug that the reason we haven't upgraded to seven is because seven also removes uh features that kohas relying on currently.

A

G

Features: it's the it's where that issue with uh specifying types in mapping is depreciated in version seven elasticsearch! That's why we haven't upgraded to that's why the community has an upgraded to version. Seven is because version seven is causing problems in koha as well, so.

A

Koha is uh depending on some depreciated features.

A

F

What it looks like.

A

That's odd that they would do that.

B

Yeah, okay and I need to search for the bug but I put in um they're upvoted, one for matching. Creating matching rules for importing, doesn't work and a couple of people that they can't replicate it I just spun up 2011 at test site and I still can't have to follow up on that at some point. If.

G

You find that bug. Let me know, because I've been working with matching rules, as we add Authority control and so I've been figuring out a few issues with that myself.

G

I can specify there that the the issue that we're having um in our Authority control product project is that um not all of the when we update authorities, um Library Congress Authority record controlled well, the one of the issues with koha is that the um koha, you know the authority control number.

G

That's in an authority. Control record is in the zero zero one, but when you import an authority into koha, it overwrites the zero zero one with the koha uh ID number.

G

So that's: okay, because that um the library Congress number all of those numbers in the authority control records are duplicated in other places. In the mark record for the authority control, the you know, like the library Congress numbers also is automatically duplicated in the 010, um but others are duplicated in, like the 016 and the o24, and the issue with matching rules on those is that um they're, the 016 and the o24 aren't indexed by koha automatically.

G

You have to add those to the index if you're on elasticsearch, so that you can match on those and that's the issue we're having is trying to get those mapped before we do our final.

G

um Our final part of this Authority control project is to make sure that if we bring in updates to those records, we can match on them. It'd.

H

Be nice to be able to.

G

Do that you know instead of just creating duplicates so.

B

Adding a new field or a new indexed Field in with elasticsearch is really easy.

G

It's even easier for me, because I just have to tell by water what I want indexed I don't have to actually index it myself.

A

I threw another uh bug out there: uh three two nine eight five and this one has to do with uh an inconsistency. It's a if you do a patron, quick search done on a card number. um Here's the thing you have this field uh I think it's called in defaults, Patron, search Fields.

A

um If you do not include card number as one of the search criteria when you do a patron search by card number, it works, uh but if you're doing a search for a patron card number like as a patron uh guarantor, um it does not work which is really weird.

A

um I opened up this discussion and you know, and it's interesting how discussions go in the conversation, because you know people say well, it works if you put it in there, it'll it'll work and I'm like okay, great, but it you know nowhere. Does it explain to you?

A

Okay and you don't have to have it in there and it'll work for for General searching, but if you know, if you're doing guarantor searches by card number, it's not going to work, um there's nothing to to indicate that it's not documented anywhere and so I'm scratching my head, trying to figure this stuff out and so I.

A

You know I'm, basically saying okay, we just need some consistency either it works whether it's listed there or not- and it's mentioned that that it'll work, regardless of of it being listed in that field or it doesn't work it shouldn't work consistently. If you take it out, you shouldn't be able to search by that anywhere.

A

It just needs to work the same everywhere rather than it works in one place and not the other, which is the conversation I had and then I had somebody uh write back on that and you know I I'm not trying to be a troublemaker, but I do give a little bit of pushback uh in these conversations, because it's it's weird how you know some of these things are are brought up in these conversations. This is like. Why did you go there?

A

um Somebody somebody created a patch and they said this patch should fix the problem. You're describing, but not sure it's something we want this Behavior has been around for years. It's like okay, if you didn't, if you don't want it, why did you provide it? And you know, if that's you know I, you know I gave options as to you know, diff. You know two different directions. We could go with it. You know, if you don't like that, why did you give it?

A

It was just a little odd to me, but um you know I'm not I'm, not trying to complain about it. It's just like you know, provide the patch and you know you know: do you not see the the benefit of keeping something consistent, one way or the other within the product, rather than having it act differently in different places?

A

Let's so uh I apologize to everybody in the community if I seem a little snarky in my response to that, but uh yeah I'm just trying to understand people's mindsets uh in going forward, I'm, not trying to dictate in any way um how Koh should work, but it does seem to make sense that you know if, if you're gonna say you know this, this field works for searching. It should work everywhere or it shouldn't work at all, so that you know it's just kind of goofy to me.

A

I welcome people to to join in the conversation, but um we're trying to I'm trying to get us into place and he's got this patch so we'll see if it works and sign off on it. But it's just funny how some of these conversations can go on these topics.

A

A

A

Has anybody played with the new version of uh koha, yet we've got it on our test. Server I just started looking at it.

C

The thing I noticed immediately because they move all the different like options for checkout check in renew to the right side. I used to clicking below so I have to I have to uh adjust uh I I. Just can't I've been doing that for years, and my body doesn't want to look to the right side for that spot.

B

And the home page looks a lot different yeah.

G

Bob's problem, a little better Bob's problem was mentioned. Bob's problem was mentioned by everybody that I've shown the new interface to it's, like all of that stuff. That used to be here is over here and it's weird to.

C

We'll all adjust in a matter of weeks, probably days if not days, so it's just I, that was the first thing I noticed, is I kept on clicking on blank space.

A

Yeah it's it's kind of odd. You know, because everything has been made a little bit smaller on the page.

A

um It's good for fitting things in you know in tighter tighter screen spaces, but you know if you've got fat fingers if you're working on a device like a phone or whatever, and you got fat fingers that might make it a little bit more challenging. But um the the challenge for me is: you know: I want to go back to the home page man, it's a smaller place to click on, and it's like. Okay, uh where am I clicking at you, it makes me hesitate a lot now. I'm stuttering in my my workflow.

A

And you have to get used to the fact that the cataloging tools are now on the cataloging page, so uh yeah, that's that's! A huge shift for poha does.

B

Make more sense but like most things, it's going to take a while to get used to.

A

Well, it's interesting that they moved the cataloging tools, but they didn't move the circulation tools.

G

A

H

A

The the circulation page does have well, it has more going on on it um and we add quite a bit to our circulation page. So that's going to be an interesting shift when that does happen,.

G

uh I haven't used it yet, but uh um we've been using for years the the hacky version of using koha to add extra pages to the uh to the OPAC. You can create a page.

G

um You have to go into the back end of Cohan and set up some things, but then you can create a system preference where you can fill the the little system, preference box full of HTML, and it will create a separate new web page on the OPAC and that feature has been implemented fully into Cohan.

G

Now, where there's a system where there's a like the news features, you can go in and create whole pages, not just for the staff client, but not just for the OPAC, but also for the staff client now, and so that I can see as a way of you know, creating a page like right now. I have all my statistics on the home page in koha on a tab, and this way I can just create a page, that's just for the statistics stuff um and they can be isolated on a branch by Branch basis.

G

So I can have pages that you know are only visible to staff at one library or another, um and that I'm really excited about yeah.

B

That is the re. uh Pretty much only reason, I upgraded the authors catalog to 2011, so I could have the additional tab. It is really easy to create just come into news, click click there you are and it's on the OPEC page, a separate tab.

A

Yeah I am it would a natural progression for this. It would be great if sometime down the road, you could Define, who can edit what pages, because it would be nice to be able to say: okay, here's a page for this library, and they can, you know, put it whatever they want on it and maintain that page and update it as needed and you're kind. You know, because I can see in the future. You know if you have like a Consortium. We.

I

E

A

Separate Consortium web page, but it might be nice to just put all that together and have Pages for each of the um the branches um that you maintain there rather than on a completely different site. So you know: there's some possibility down the road uh if they, if they give that uh ability for individuals to or uh or groups to, edit.

A

Any other comments or thoughts about 2211.

H

Another like big feature: they added with the was curbside pickup USB plug-in it's a native feature. Now I haven't looked at it much, but we might might.

F

Get more use out of it now that it's built in and.

H

H

G

I just put a link to the MonDay minutes that Kelly and Jesse did about the web pages into the chat box.

A

Yeah that was well done. Some good information there.

A

F

A

Minutes anybody want to suck.

F

Up that last minute,.

A

I will throw one thing out: real, quick before we wrap up. Then, uh let's see here, I think this is the one and let's make.

F

F

A

Okay, something that I'm pushing for we've made a lot of progress with uh passwords. This is a next good step, with passwords um to be able to force a password change for new patrons right now. um uh You know if you know, when patrons sign up for an account online. If.

H

They do a self-registration.

A

They can create their password right off the bat if you do it in person, uh we're giving them a default password unless you have some mechanism in place for them to be able to type in their password you're doing it for them you're, giving them some sort of defaults or you or a staff. Member knows it.

A

If they're telling you what password to use or something not completely kosher, um it would be good if we could have those passwords expire right away and when they log in for the first time it asks them to update their password. Don't have that mechanism right now, I tried uh forcing this system to do that.

A

I was going to go in there and use some jQuery and say Well when you're creating a new account just make the expiration for the password defaulted today, but the password expiration date not available on an add new Patron form which is really God, so I can't even hack it right now. So uh if we were to try and do something like that, we'd have to create the patreon, then go back into the patreon and edit that date and set it to to today in order to have that functionality.

A

So it would be nice to have something like that. uh In my opinion, if you have opinions on that, please comment on the the bug.

B

All right, I just had to tell someone. No, this, isn't the usback embassy drop by one digit.

A

All right well, we've reached 9 31 and it is time to wrap up and uh I've got another meeting starting here for the the conference committee. So uh I want to thank everybody for joining us today. It's great to have you here and if you're sticking around for that committee, we'll be starting in just a few minutes. So thanks everyone for coming we'll see you next month.

E

See you later Christopher I'm jumping onto another computer and I'll, be there in a minute all right.