Koha-US SIG - Acquisitions Special Interest Group, 16 Jun 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Acquisitions Special Interest Group - 6/16/20

Description

Chat logs:
00:13:22 Margaret Hade: Blanket Po google group chat : https://groups.google.com/g/kohaacquser/c/zifFqwMb_QI/m/tqbYnjR3CQAJ
00:21:56 Laura (MCC): what did you download to do this
00:23:06 Margaret Hade: Could you be more specific Laura? are you talking about the document?
00:26:48 Margaret Hade: you’re right on track Rhonda!
00:36:36 Laura (MCC): Is there a place that discusses all the status values
00:39:22 Margaret Hade: Monday Minutes - Working with Bugzilla Part 1 https://youtu.be/uFsH9Fdy08s
00:39:50 Margaret Hade: Monday Minutes: Submitting a bug in Bugzilla https://youtu.be/BGdZxEjB2Cc
00:40:53 Jason Robb, SEKLS: this is helpful for understanding the dev cycle, roles and where those different statuses show up too https://wiki.koha-community.org/wiki/Development_workflow
00:59:10 Michelle Clarizio - Roseville Public Library: On Wednesday
00:59:13 Jennie Evans - Flower Mound: ours is tonight
00:59:30 Jennifer Marlatt: We upgraded on Saturday.
01:00:31 Stephanie: We're on the 19th
01:00:34 Margaret Hade: 25557
01:00:52 Margaret Hade: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25557
01:05:35 Margaret Hade: got to run, have a great day everyone!
01:05:42 Judy: We upgraded last night
01:06:28 Jennie Evans - Flower Mound: thanks, Rhonda!
01:06:35 Jennie Evans - Flower Mound: stay safe, everyone!
01:06:43 Jennifer Marlatt: Thank you!
01:06:44 Judy: Thank you, Rhonda.
01:06:45 Laura (MCC): thanks Rhonda
01:06:49 Stephanie: Thank you!

A

Okay, um welcome everyone. um This is our we're in june. Somehow we got to be in june already. um I hope everyone's doing well. um I know different libraries. We were chatting before we started about you know some libraries are still closed. Some are starting to open everybody's in different uh phases, um so I hope everybody's well and um we will just get started. I want I wanted to apologize for kind of.

A

Last month um I had my my father passed away and totally um yeah that took up most of my month of may so um sorry, I kind of dropped out of a communication there for a while, but um we're back and everybody's doing well. So thank you.

A

um Okay. What I wanted to do today was to spend a little bit of time. I know that we have started doing some talking about the blanket po process and laura had written up a word document that um kind of laid out. You know what it takes right now to do a po and, and maybe some ideas for um or for a blanket po. I should say we have stuff for regular, pos and and some ideas for um you know, changes that we could make.

A

We posted this on the list serve, and hopefully people got a chance to kind of look at that and kind of gather your thoughts. um I don't know if anybody has any thoughts about that. Have I I guess I'm really curious to to hear um other experiences. People have had with um other ilses what how that was implemented in some other ilses or or just you know what what it would be like. um I don't know if I can.

A

I don't really have a link to this document. If you don't have it, um if you go to the list or if you go to our group chat well,.

A

Yeah, I don't I'm not sure how to point to it. If you don't have it, um but.

A

I could I could um read some this description here for the blanket po um you know upgrades.

A

So the suggestion is basically to add a check box in the vendor record that contains the text, allows blanket po orders or something like that. You know like we've got some other things standing here and um in the contract details section and then in the invoice screen have a drop down menu for a new field called charge type and those values could be invoice. Credit blanket purchase, order, standard order, regular invoice.

A

If you were to click, blanket purchase, order or invoice credit. You would see something like invoice amount instead of shipping cost. Most of the rest of the procedure would be the same. um So does anybody have any feedback or thoughts or ideas about the blanket po process?.

B

Well, I was the one who who who really liked the idea. I guess um I we have. This is our third system or actually it's about our fifth system, but the uh the third. This is our third system, where I'm attempting to try to do something with blanket pose.

B

We we were able to do it in millennium and we're also able to do it in evergreen, which is the system that we just came from like a couple years ago, so um our staff has just been used to using the acquisition system to track our blanket pos, and someone did provide me with some um with a starting point, and I said oh well, that's good because it looks even if you add an invoice right now to the system.

B

It has to come through a basket in order to debit the the amounts from your um your funds, so it was just sort of so you have to sort of like receive, even though you're not really receiving or whatever. So it's it's sort of a kludgy back around way of dealing with it and it works pretty. Well. Actually, it's just. You know what the screen says and what it's actually doing are different. So that's why I just thought: well, you know it didn't seem like it would be.

B

You know terribly difficult to add like a charge type to the um the invoice, and I you know I just came up with some other ideas of things that I thought other libraries might use this for uh like a standing order which we don't have, but I know we other libraries have used that you know regularly or credit or whatever, although I guess, there's a new there's a way since I started doing this that credit. So now you can deal with them uh in the system, but anyways it just.

B

I was just trying to throw out some ideas and it didn't if we sort of just sort of modified slightly what we were doing now, I figured it would cost that much to try to implement. That was the idea. Anyways, okay,.

A

A

Oh yeah yeah, so margaret did um post a link to the group uh google group chat to so that you can go in there and see the document so um yeah. If you, if you want to look at that, I I think I think blanket pos are probably something that a lot of libraries use um for for different reasons.

A

um So I you know when I saw this, I thought. Oh, maybe that's something that I that again everybody that there's a lot of interest in that we can maybe start pushing kind of an aside.

A

I don't know how many of you peruse bugzilla, but I was in there yesterday and came across two bugs um from uh I don't know some some place. I think europe, you know one of the european uh support people um that referenced our 13325 about tracking funds for budgets and they have actually started working on the first step, which is logging um the um acquisitions transactions. You know when does when's the basket added. When is the basket uh deleted? When is an order added?

A

When is an order, canceled all those different things, um so you know that I think you know getting this stuff out there and getting other people across the world to actually see some.

C

Of these ideas.

A

That other people are interested in um that alone is helpful to get things moving.

C

A

We've got step one covered um in in the three-step process that bywater had laid out, so um that was that was really good to see. So I think you know the same thing if we can maybe get a um a bug out there with some of this blanket po stuff in um you know we just kind of have to decide how we want it to look.

A

You know put something out there that people can can get their hands around and understand, and then that will help things move along too, because I think you know we all agree. There's plenty of things we can do to improve the acquisitions part of of coha.

A

um Did anybody else? Have any ideas about um blanket pos? How? How have other people do? Other people use blank? You know that concept where you, you know, take a bunch out right at the beginning and then kind of charge against that um you know, that's basically what we do like for overdrive. You know.

C

Our electronic.

A

Our digital stuff is, we just do one big po and then buy against that for the next few months. um Does anybody else do anything like that.

B

Yeah we use ours, for we have some patron journey acquisition accounts. So you know if we like pre-select things, but they don't bill us until, like a patreon actually uses them. So um that's you know that in some streaming media we have pda for canopy and we all have it for ebsco ebooks.

B

So it's just a matter of encumbering the funds like ahead of time and then it allows us to keep track of how much we still have left in on.

D

A

A

A

Well, um I you know, if you have any other ideas about how to do this, um you know how this po process could be beneficial to you. um Definitely you know post in the google group. Well, you know we'll be watching that um just to get ideas and stuff if, if you've had experience on other ilses, that you know you think, oh that you know this. Is this worked really slick here or whatever um just workflow kinds of things? um I think that would be great.

A

So I think what we'll do now is move on to our next uh item, which we had talked about last time, um actually signing off on um a bug just to show everybody how that works. um So I did find. Oh no.

A

I found a bug. Yes, I thought I had messed up my papers. Okay, so I found a bug that was pretty simple. I actually signed off on it already, but um we can do it again, as margaret pointed out multiple times, um so I I this way. I know that what I'm going to do is is going to work. So what I will do first is close some of these crazy windows. I have here.

A

A

Okay, so I am going to share my screen.

A

A

Did that work? Oh there we go. Okay just took a long time to come up.

A

I think that's the whole thing, so can everybody see my screen and all the chaos that is my screen.

A

Okay, all right, so I want to do this step by step. So the very first thing that I do is find the bywater sandboxes. So what I'm going to show? You is how to sign off on something using the bywater sandboxes.

A

So this is how I find it. I just search on koha and.

A

A

And I think sometimes I throw a wiki in there too.

A

A

You can you'll get to this um page in the cohab wiki, that's um basically wiki and then sandboxes.

A

In the table of contents, here, there's um down here under five, it says available sandboxes. So there is, I click on buy water. That brings up this by water solution, and um these are self, they call them self provisioning, sandbox um stuff, and so this is the link that you need. So basically, if you can remember this link, you can just type that in I never remember the link, so there you go, um there's also a couple of video guides right here and both of those are good um refreshers.

A

You know like when you walk away from here and then you try this in a week or in two weeks or whatever, and you can't remember what certain fields are these two um demos, this one is done by kyle, I'm not sure who the other one is done by. I always watch this, the one done by kyle to refresh my memory of how this all works.

A

So um what we'll do is click on the sandboxes, so um you can see I've. I've got one out here, that's the one I tested yesterday. I just left it in case all heck broke loose. When I tried to do it today, we would still have this one to to test on.

A

But the first thing that you do is up here in the options we've got create and then there's a bunch of fields that you need to enter. So um what I should have done is bring up bugzilla and show you the bug.

A

uh Two we're gonna do two five, six one one! It's real! You know simple, straightforward kind of thing, so you can see it says, signed off here. That was me doing that the other day. So what this is is changing the vendor when creating the basket does not keep the new vendor. So when you're, when you open a basket, you know first, you search for the vendor and then you do create new basket and then once you've got the basket open, you're like oh, that was the wrong one. The wrong vendor I didn't want to.

A

You know, use amazon. I wanted to use you know ingram or whatever, there's a drop down that lets. You change the vendor and previous to this bug, you could change the vendor. All you wanted, but it would never save it. It would always just revert back to the of the original vendor. So this is this bug is supposed to change, uh fix that so that it actually saves it. So um what you do you know? You've got your bug here um and.

A

Okay, so what I'm just working through my mind and how this order should go? I think I've screwed it up already, but um okay. So um what each bug should have is a test plan.

A

So here we can see that jonathan created a test plan for us. So what we want to do is we'll just follow that test plan.

A

So back here at the sandboxes, um the first thing is enter your name, so what this is used for- and it tells you um underneath here- this will be used for signing off the patches.

A

So you want to do that and.

A

Enter a simple name for your sandbox lowercase, all letters and numbers, so what I usually do is just put in the bug number, um so I'm gonna say: uh oh okay, um I'm gonna say 2 at the er. Let's see, I'm gonna put two at the front just to make it not confusing so there's my sandbox name and then here I guess I'm not gonna put the two at the front.

A

um I'm just gonna call it b how about that? Okay, now it's happy, um and then here you actually. This is this is where you tell the system which fix to apply to the system, so um we will put in there that bug number um mark flavor. I just leave that alone.

A

um This is for, if you don't have the code in the bug and you have to use the git repository, I've never used that. So I would just ignore that the description and the notes are just optional, like it says here. um If you want to you, know, help yourself remember something or whatever you can do that so and then then this is the uh captcha just to make sure that it's not some robot. That's doing this.

B

um So how does it know what version of the system it's testing, or does it always you're doing this? It always tests the most current version of the system for the master. How do you know.

A

Yeah, um this is always going to use the most recent um version of the system, um so.

B

Even if it's not yet like we're, we're still working 1911- and you know, 2005 is sort of- I think it's sort of semi out. So this would be happening.

A

Yes, I think so um I'm not sure margaret do you know.

D

Yeah, so laura you are right when you said master so master is the latest most current thing that the developers are working on. It doesn't technically have a version number it's just called master. So when these sandboxes get built, it's using the latest pushed version of coha that whomever the version manager release manager is has approved.

D

So everything that's gone through reporting sign off, qa pushed to master, it's going to be working off of that, so things get fixed and master first and signed off there and then applied to a version and back ported to previous versions, if applicable,.

B

So whatever we work on, we wouldn't see, probably for several months, assuming we signed off on it because it hasn't hasn't made its.

D

Way through the food chain, yet exactly I like that made its way through the free chain. It does definitely go through a cycle um and the.

D

There isn't one web page. I can point you at at the moment that explains the whole cycle and timeline um since it's an open source community.

D

There are hard uh dates for when new versions are released and then whatever has been worked on and approved by qa and published push to master push to the release by the release manager. That's what comes out in a specific version, release or point updates in between essentially may and november each calendar year.

D

You can always potentially run master in your production environment. Some people do it it's a little bit on the wild side from our perspective, but it's doable and then you can always have the latest things um available to you in coho. Usually people do that in a demo site instead and see what they like.

B

A

Okay, thanks margaret, that makes a lot of sense.

A

Okay, you may have noticed that I kept refreshing this page and this status right here went from provisioning pending or provisioning pending yeah to provisioning to provisioned, and then once it was provisioned, these blue buttons showed up and those are how you access the staff side and the opac side of this new system that we've built with this bug.

A

Added to it um so, and I wanted to show you you know, if you go into bugzilla and just search on acquisitions, um you get you can see all of these new bugs that have shown up there's a lot of new things for acquisitions. These are all things that people could work on, as developers um then assigned it means somebody's grabbed. It basically um somebody's looking at it somebody's working on it.

A

So that way, you don't end up with two people trying to solve the same problem at the same time, um in d is in discussion, so there you know something about. The request needs further clarification, that's kind of the area we, if, if we can lay out exactly what we want, we can avoid that step. Maybe or make it a little bit shorter, that's that's a good thing.

A

These need are actually needs sign off, so those are the ones that you would look for to help move things along. That's where I came across these um that I'm looking at oh okay, the one that we have is is signed off. So it's not going to be in that list, um but the ones that.

A

Let's see here, if I can hear this one um add additional acquisition, logging and there's one that, oh, that one's signed off already too, so it's not going to be here um the problem I wanted to demonstrate this one I talked to margaret about it yesterday. This one actually has a dependency of you need to have another bug on your system. First, before you can test this one in the sand boxes or before you can test it period and in the sandboxes, that's just way too tricky.

A

So I don't even know if it's possible um to do a dependency with the sandboxes, so we just kept moving past that one these right here are. um These are ones that are signed off. So in this list, yeah right here we can see that this is the one that we're looking at. This is the one we're gonna sign off. um These fails um are failed, qa, so quality assurance um for whatever reason you know it could be something as simple as comments in the um picture.

A

You know the way the tech, the the code was written, you know, or it could be, that the function, it's just not working the way it's supposed to be functioning but forever it failed, qa and then um oh patch doesn't apply sometimes as you're working on something uh some.

A

You know the area that you're in somebody else might be making a change or whatever, and then your your patch doesn't fit any anymore, because somebody else has gone in and made it a change or something you know for whatever reason the patch doesn't apply, so the developer will go back and then these are push to master.

A

So all of these right here will be on the system that we are testing on and.

C

A

A bunch of those too- and I don't even know what blocked means.

D

That's it could be blocked by one of those, so you have some things that are dependent on others to be eventually pushed to master and blocked is just. This is not going to work with the current master setup of code. That's in cohab like just there is some significant roadblock and the developers can't proceed with it. Yet.

A

A

um Margaret could you watch the chat for me just to see if there's any anything coming in there.

D

Because I see uh laura is asking: is there a place that discusses all the status values so like a resource on bugzilla? That explains what the different values are and what they mean kind of glossary.

B

And what are these columns mean? And you know so that if I I might have a better sense as to what to work on, and you know myself, you know like later on.

D

uh I've got a couple of tutorial videos about bugzzilla itself. um Let me go fetch the links for those and I'll post them in chat. Does that work for now yeah. Thank.

B

A

Okay, all right, so let's go.

A

Let's go back to our sandbox, I keep there. We go okay, so here's our sandbox. So what we want to do. What what we need to do is follow our test plan. So our test plan- let's see I'll, just go back.

A

I will let's find our test plan back so here it is um so.

A

The test plan is to choose a vendor, create a basket and then assign a new vendor once you've created the basket and then without the patch. The new vendor doesn't change and with the patch um it does change and then go what how I interpreted this was to you, know, save it get out and then go back in and try and edit the basket and see if you can change the vendor.

A

That way too, so both at the creation and coming back later and editing trying to change the vendor both of those ways so we'll click on the staff, button, that'll, open a new window and it's always uh koha koha for um the passwords and stuff.

A

And then we go to acquisitions and in this system it took me a while to figure this out. But there's one vendor set set up and it's called my vendor. So we're going to just um search on that vendor.

A

And there is one basket here already, but we're going to add another one. So because that's what our test plan said to do, oops we gotta go this way, um choose a vendor and then create a basket. So we're gonna create a basket.

A

A

Vendor we'll call it and I think what our test plan said was assign a new vendor, so here's the vendor the little drop. Oh, that's right. I forgot something. Let's back out of here.

A

We need to create a new vendor, because this this is what typically happens. You figure out. Oh you know this system doesn't come with a lot of data, so you need to um we're just going to call it ingram and save it.

A

Okay. So now we've got two vendors that we can swap back and forth between. So let's go back to.

B

My just just for people's knowledge, if they just click on the the vendor search tab without putting any data and it'll give you all the all the values. So you know you could see what was there? Oh, okay.

A

Yeah, that must have been what I did to figure it out. I couldn't figure out: oh there, we go okay, so there's there's our vendor choices. At this point um we just always know who our vendors were. So I never had to try that um okay, so this one we're gonna pick my vent oops. No, that's not what I wanted to do. um We're gonna do a new basket for this vendor and we'll try it again. um Testing.

A

Okay and then um we're gonna switch the vendor and we'll leave everything else and we'll save it, and you can see that this is now an ingram order instead of my vendor order, so that looks good yay we successfully changed it. um So the other thing all right. So now we go back to boobs. You can do that every time we'll go back to our test plan.

A

Okay, and it says with the patch the vendor is changed, yay and then step. Four is edit the basket and change the vendor.

A

So we have a option here called edit basket and we decide oh yeah, we really did want my bender, and so we save it and now the basket is for my bender and that looks all super.

A

So um anybody have anything else. You want to test with this, because this is the time to do it. I used to work tests and it's like creativity is what pays off at this point. Sometimes the the advantage of people who use acquisitions testing acquisitions bugs is that you know the ins and outs of stuff. You know the the weird little, uh maybe not traditional uh workflows that you use um so so you can get in here and try things and make sure that it's really working the way you want it to so.

A

That's I I couldn't think of anything that you could do to this one. Besides the two uh cases where you're on creation and then on, you know editing it at a later point. um So if that's all good, then um let me think: okay yay, we can do this. This is good. So now we go back to our sandboxes and we're we're this first one here and under actions.

A

There is a option to sign off patches, so um you just click on that and you get another form to fill out.

A

It will take the name and the email that you put in when you created the sandbox, and it will replicate them here and the bug number now. This number of patches is pretty important.

A

So what you need and what they're asking there is, how many um units of code uh are are actually getting applied here. So back here, when you look at this, you can go to the logs and under get log.

A

You can see. We should have checked this earlier, but you can see that the very right here we see that this bug is the bug we were testing that it has applied. It's been applied to the system, so we're actually testing what we think we're testing. um You know you might mistype the number or something like that and and it won't apply, but we've applied it and we look at the next one. Okay, that's a different number, so we have just one patch.

A

But if you look at this one right here that katrine signed off on it's bug, one zero, nine one, zero and oh here's another one, one: zero, nine one: zero! So that one when she signs off on that one, she would have put two in the number of patches because there's actually two pieces of code. You know two sets of code that you know sometimes that you know they write code and then you know they go through tests and they realize oh there's a problem.

A

So they'll do a little a little follow-on piece of code to fix that error. You know. Maybe that happens once or twice you know. So that's that's what this stuff is all about. So back, are you sorted so that the things are together or do you have to look through the whole list?

A

They should be right next to each other because they will be applied one right after you know, they'll be applied at the same time, so they should be right next, you know right next to each other and at the top you know the one that you just applied um so okay, so we will just do one as the number of patches and then the captcha again.

A

A

So this is an important thing to note.

A

Oh, I guess I hit enter and what that note said was.

A

That I'll show you when we get basically what it says so now, if we go back to sorry, I hit the I hit the enter key, not thinking and then went on. So I'm going to refresh this. We can see there's two sign-offs here now, both of them being me- um and this looks all good. But what that comment that I scooted past before said is right now those sandboxes what it won't do is it won't update this status.

A

This one is already updated, but if, if it's, if it said need sign off before it will still say, need sign off after you signed it off in the co in the bywater sandboxes. So what you do is you click edit and then there's this little drop down and you change it to need sign off and then.

A

I'm not sure how to get out of here. I will save my changes since it's not a change, um so this.

D

And will advance you to like the next bug in the list once you save something, don't know why it does that, but don't worry about it just back button, your way to uh where you were at.

A

D

A

Remember that okay, so we have signed off a bug.

A

The the sandboxes are, you know, pretty simple to do it to sign off if you have a fairly straightforward bug to sign off things bugs that require command line um statements, or you know cron jobs and all that kind of stuff.

A

You really can't do through the sandboxes, because you don't have access to that stuff, but if you have something that's pretty user interface driven. um This is this is a way to sign things off um questions.

A

I know this can be pretty overwhelming the first time you see it, because this is, I I've gone to a number of conferences um and each time it's been, you know. How do I do this? How do I do this um so?

A

But the this is. This is much simpler. These sandboxes have made it much simpler to do uh sign offs than when we first got on on coho.

A

This has been helpful good, I'm glad you know it sounds pretty intimidating, but it really isn't and I think the developers really appreciate the input that librarians can give. You know the people that are actually using this code and you know I'm. I was real excited at first when I realized that there was a bug out there. That was actually going to do the um function that we had been talking or you know the beginning functions of actually um keeping a log of acquisitions stuff, but um yeah it.

A

It's not something that I we can do with um with this this particular tool because of the dependencies.

A

um If, if that other bug the first one that it depends on um ever gets pushed to master, then we could test this one, that's true right, okay, so um the other one has been signed off already. So you know we can wait. You know kind of wait and see, but um I'm guessing somebody will come in.

D

A

And test that one, because they're very closely they're they're related they're, real close to each other. It's just one has like four different functions that they're logging and then the other one adds another.

A

I don't know six or eight um acquisition functions that they're going to start logging, so um that that alone, you know just having that information captured in the system is going to be a real plus for us too, and it's kind of cool to know that there are other libraries across the world that are talking about the same things that we are functions that they want.

A

So, okay, um any other questions or um things that people are interested in related to the sandboxes.

B

Should we look at some other bugs that we think we want to sign off fire? We.

A

Could all right so I always go to home and margaret is there a best way to find um bugs that need to be signed off? I just kind of hunt.

D

um uh That'll work uh there's also using the browse feature. um So if you go to the top of the page and then under the green bar, it goes home new browse, okay and then coho the first one.

A

D

And then you can navigate to acquisitions and then sort the list by the status. It's in.

A

Oh okay, I see okay.

D

That's the way I usually do it that doesn't seem like too many clicks for me, but using the searching features, advanced search features you could just bookmark it setting up to just look at the module acquisitions and then the e-status needs sign-off and it doesn't hurt to check out maybe some other areas of coho. Once we've exhausted the list of sign-offable acquisitions bugs go, do a cataloging or circulation one and then chat with the person who's hanging out working on that bug that developer and say hey.

D

You know I just signed off on this other one, and you know when you have a moment. If you want to go qa that would be nice so spreading the love around bugs a little bit usually returns on that investment of time.

D

B

So before it gets to be signed, offable so to speak, happy assigned to someone and they have to do a plan for like how you would fit this and do the code is. Am I understanding this correctly.

D

I'd say: there's the two parts of the bug or enhancement needs to be reported and a developer needs to write a patch. So the code change itself and then an explanation of what this patch does the test plan, and then you can get into this need sign off, because the problem's been reported and a potential solution has also been reported.

B

So for the bugs that are at a new status and they haven't been assigned to anyone, um we can go in and we can comment on how we think this might be helpful, because that's another thing that we might be able to do with this group to try to get people to focus on those particular ideas. Is that true, that's true 100, sometimes it says, there's low interest. Well, it may be low interest, because no one knows that they're interested, not that there really is.

A

Yeah, and so like this one.

C

A

Here um well, yeah one once there's a fix for it. You probably don't need to promote it as much but um yeah for some of these other ones, um especially this list of new right.

A

You know it just goes on and.

D

On so, I will say more bugs um more problems with the code more potential enhancements, they all kind of sit in new status for a little bit um and there's a lot um and something of a backlog for it.

D

Some of these are a couple years old and it's kind of picking out the ones where you want to invest that time to make suggestions on how it should be fixed to talk to co-op developers around the world um at bywater at interleave, ptfs you'll see a lot of those names, bibli floating around um and encouraging the developers.

D

This is why this one's important, because sometimes it's just a lot and picking out which ones especially the ones that are like not immediately intuitive, to fix you kind of have to nudge them a little bit because developers believe it or not. Are human beings it'd be nice if we could clone them and just make them work all day, but they do have uh the same kind of ooh. That looks like it's fun or that's interesting or that looks simple.

D

Let me do the low hanging fruit first, so if you can make some of these new ones stand out as delicious ripe fruit that they just need to pluck off and write some pearl coat for it's more likely to get it uh moved through the community cycle through that food chain up and push to master and then into a cohort version.

A

A

All right, um we just have a couple minutes left um about seven um and I wanted to leave a little bit of time to discuss any questions or problems with uh 1911..

A

I'm going to stop sharing the screen now for a minute. um Has everyone migrated to 1911? I know this is kind of the week of migration. So there's probably some people that aren't on 1911. Yet, um okay, um we are on it. um It was.

A

Not that big of uh I mean we didn't run into that many problems with it. um Our catalogers, with the with the um advanced editor needed to do some setup of the the keystrokes. You know um copy, paste and stuff like that they needed to make a few adjustments there. That's all fine!

A

I think you didn't really notice too much difference.

A

Yeah yeah. um We noticed that in a basket the quantity column yeah, it doesn't display on default, which is kind of interesting, so holly put in a ticket for that, because that's kind of an important one when you're going through baskets to see that.

C

Hey rhonda, yeah, hey, this is marcy. um I just noticed that same issue because we upgraded a couple days ago and there's a bug out there right now bug two five: five, five seven. So apparently the order of the acquisition table doesn't match in the admin.

C

In the admin where you configure it, and so if you're telling it to hide column six, because six is what's displaying in your basket, that's actually a different column. So because I just started a a well, I didn't start a ticket. I emailed the upgrade the.

A

Okay, that's good information; okay,.

C

So yeah take a look at that bug and that'll. Tell you how to how the in the admin to hide the ones you don't need and make the ones that you do need like quantity appear. Okay,.

A

Okay, that's very good information, all right. Okay,.

D

And I'll piggyback on that to just illustrate the developers, are human beings and uh took I'd, say this simple route of just saying: we'll put it in this order, but not necessarily looking at the column name and that's how we ended up with this particular flavor of unintended feature in this version of cohab.

A

Okay, um I'm just going to put in a plug for one of the developments. One of our developments made it this release, um it's the it's an enhancement on the j to a um cron job. I guess it is um which allows you to do a whole lot more patron changes, um basically what we wanted it for and- and I'm I'm really curious to see how other library you know what creative things other libraries will be able to do with this thing, but we have always had a rule or a policy.

A

I guess is a better word to um our. When patrons came in for the first time to get a library card, we made them a category of new patron. You know new family new sing, you know individual all that kind of stuff, um and then we had a matching set of patron names that were not new, and so after they've been a new patron for 30 days and they had fines less than five dollars and um a valid uh driver's license number in their account.

A

um We would move them from new to regular, so the new patron only had like five checkouts, and I forget how many holds and then but then like the regular family card could get 45 checkouts or you know so um you know once they prove themselves for for a month um to be good citizens, then uh of the library. Then then we would upgrade their account, and that was all done automatically in the background with our old system, um so this new enhancement to uh used to be called j to a.

A

I think it's patron underscore update or something like that- there's more words in there, um but it will what it will allow us to do that thing automatically. You know run it once in.

B

A

Evening and and check for everybody that needs to be updated, so um just encourage people to explore that idea. If you've got some policies that you know, you're, not quite sure how to you know if you've got how how to implement or enforce them or you've got some. um You know staff person in the background with a report turning away um trying.

C

To get because that's what.

A

We've been doing for the last couple years, just have a report, but this will do it automatically. So.

A

um Any other thoughts about 1911, I think, we've.

A

A

Okay: well: okay, okay, so yeah we can. We can revisit this um uh next next meeting too, because it looks like a few of you are um well so flower mound goes tonight um and jennifer upgrading on saturday and 19th is friday right yeah. How could I forget that um and um okay see you margaret have a good day um yeah, so um and and if anybody has anything that they would like to bring up and discuss at one of our meetings, please send me an email and I'll get it on the agenda.

A

um The next meeting will be hang on one second.

A

Looks like july 21st is the third tuesday in july, so that will be our next meeting at same time and um we will see you all there. It's good to see everybody again and um yeah. That's you know, keep talking to each other and on the on the google group and we'll we'll get this going um soon. Yeah and yeah. Definitely everybody stay safe and we'll talk to you.

A