Magda
Thank you. The link to the recording is always the same. If you want to listen to their past meetings, this is the best place to find them (see link at top of page). A quick WOLFCON update. The demo Bulk Edit presentation took place and the presentation took place was well received. The recording is available, and the link is in the in the meeting notes. If you would like to add some comments, please feel free to do so if you didn't attend the meeting in person. It was nice to see some of you in person. Sometimes I could not recognize you. The camera. Sometimes it's misleading. But it was nice to have a real interaction. In the comments about the welcome from anyone who attended online or. Unknown Speaker 8:38
Still there back there. Did we lose you? Unknown Speaker 8:46
Did we lose back then? Unknown Speaker 8:48
I think so she looks frozen on my side. Unknown Speaker 8:51
Yeah, seeing her screen at all. Right. Time for a party. I can I can see her screen. But yeah, we can see your screen is Debbie go back or she dropped off. I think she's going to try and rejoin. We can jump a topic though. expected behavior for user status, its expiration date is set to the past. She was asking if the fact that if you're changing a user expiration date, and it's in the past that the status on the user record is set to inactive if that is an error, and that is not an error. That's designed behavior. So I commented and said no because I was feeling salty. Saying buddy disagree, Christine. Anybody have concerned about that? All right, well, we'll tell her that that's not an error. She'll be happy with that answer. Yes, sorry. This is Christina. Unknown Speaker 10:08
I'm zooming in from my phone. And so I was really familiar with all the controls and all that. But no, I Unknown Speaker 10:15
agree with you. I do not disagree with what you said. Yeah. Okay. I have to admit that I was pulling up the agenda and reading the agenda. So I did not hear the first of what you said, Aaron. So can you repeat it if we have. So it's, I was just jumping at topic, because it's the one topic I felt like I could talk about. So after development updates, the topic was expected behavior for the user status, if the expiration date is set to the past, so this is if you are bulk updating user records, and you change the expiration date to, you know, a month ago, it changes the status on the user record to inactive, and that is designed behavior, that is not an error. So we don't, that doesn't need to be captured or reported. I'm hacked, we just jumped a topic, while we were waiting for you to come back. Unknown Speaker 11:15
I appreciate that. And I heard the the end of the conversations I wanted to see and this is the behavior you want to do in the bulk edit as well. So if the user enters invalid data, the data should be accepted, because I see that you can set this way that value of expiration date to be empty, but it sets the user as inactive. Is this expected behavior? Correct? Unknown Speaker 11:51
Set? Wait, say that again, throughout the generation data is blank. Unknown Speaker 11:56
Yeah. So let me let me show it to you. It may be in the in the snapshot, can you still see your screen, my screen? And the font size is okay. Or would you want me to change it Unknown Speaker 12:13
looks okay to me. Unknown Speaker 12:17
So, here are the users. And if I select my test user did so nothing prevents me here from typing here. In a valid invalid date, save it. So nothing happened. refresh, refresh. So what happened here, right now, you see that the expiration date was wiped out? Right? And the status remains active. Right? So Unknown Speaker 13:18
the question that is expected behavior, Unknown Speaker 13:21
if there is no expiration date, so if the user enters something that is invalid, and cannot be transformed into the date format, the data in the expiration date is left blank, but the user remains active. Unknown Speaker 13:40
So I happen to know that because I'm following another ticket that there is some some work going on about validating that field. I will send you the JIRA slack you the number so you can take a look at it. So I think there is some work happening right now that where there is no validation and right as you're seeing where they're trying to put it in. And so I would say that at that point, then you would get an error message back. And that would be reported because mod users would say, Hey, that's not a valid date. Right? So Unknown Speaker 14:13
the validation occurs on the UI, right? It does not occur on the back end, Unknown Speaker 14:19
though. There's no validation in either place. Okay. I'm talking right now without doing it in both places. Unknown Speaker 14:27
Still what in in both places that would be great in bulk edit right now, if you do the user barcode. Unknown Speaker 14:50
We have this lets the expiration date and We do the step back edit, you see, you have two options here, a sub bucket in CSV and the bucket is because I'm logged in as a decoy admin, both permissions, normally users will see one of those unless they have. So right now, if I do here, invalid what I'm going to show you, it's not the ideal behavior, I just want to show you what is happening. So I turned to the invalid date, we confirm the changes. This is not being populated. And commit the changes. And we are getting the three records have been changed, when in fact, nothing has changed. Unknown Speaker 16:02
So you would expect to, in this be Well, there are different paths we can take. One of the paths we were considering is on the screen. Unknown Speaker 16:16
Yeah, I don't want to, I don't want to stop you from going through it. But I really do think these two user JIRAs are relevant. And it's worth taking a look at them and then deciding about the best path. So I will I will tag you on all so you can take a look and then Unknown Speaker 16:35
having Can you send the links to me directly in the slack? Because right now 190 GS to review? I might. Yeah, please. And I will take a look, if I have a follow up questions. I will follow up with the group on Slack, or drink our next meeting. Unknown Speaker 16:55
Sure. Yeah, not a problem. Unknown Speaker 16:58
Great. Thank you very much. And the next part is the conversation about loan. Unknown Speaker 17:07
Well, I didn't talk about the bugs. We skipped that section. So I'm not sure if you want to go back to that or not. Unknown Speaker 17:14
Okay. So, as I said, this, one 150 is in in progress. And this will be a deployed probably tomorrow to the breakfast environment, and we will invalidate that. So this will for sure make the Morning Glory release. The non issues we talk about is the how the expected behavior for the record counts when the item bucket is triggered by holding. So did we talk about that during our last meeting, and it will be implemented in non Lana LaLana. But it will be marked as a non issue for morning glory. The same with multi data export worker, two or three. This happens intermittently, not every time and by the large amount of user barcodes is approximately 10,000. We have addressed this issue it is already fixed, but it did not make our morning cooler release. And the performance test results. I don't think they have changed since our last conversation. Are they any questions? Comments? No. Okay, great. I would like to move to the features that I would like to address in in our our kit next release, after Alana. And I admit, entering the territory that I'm not really familiar. This is the circulation. I want us to go into this territory because I would like us to start looking into cross app queries, building the queries across app that we can address in the release following arcade, which is Poppy, I believe, why we need the circulation because if we have a user data, and if we have item data, the record that is linking them are either loans or requests. And I would like to start with those two loan due dates and request how dates updates because they seem to be, they were pretty high on the list of use cases. But also, we already have some experience with the due dates. So hopefully we could address that quickly if there are no issues that we should consider. So, I don't know if you had the chance to take a look at the at the JIRA did JIRA does does have just very high level information. So, what we will be updating we will be updating on the loan due date and the other date are out of scope unless you indicate otherwise. And the query the query string of the of the records this will be covered by a separate story in future. The questions are basically the same that are listed on the agenda. So, I would like to ask you for the most common use case, for changing long due dates, the use case because mensen on bulk edits use cases, where was the pandemic and closures to the weather inclement weather, I hope the pandemic we are done with pandemic for a while, and we will not have to deal with this. But what are the other use cases that the library would like to update that you loan due dates. Unknown Speaker 21:59
I mean, it's more broadly than the pandemic but it's anytime anytime that a building needs to close. And that can be for all sorts of reasons. Right? Jeanette is mentioning in the chat that they close the building for two weeks and over winter break. And they if there's due dates during that timeframe, they would want to change that. You can control some of that with circulation calendars. But you know, being able to go back in and do a bulk change due date, which would be applicable in any of those scenarios. I don't know Bob Thomas, anything else you want to add there? Not that I can think of Unknown Speaker 22:50
I know David has mentioned this before and era sake about rolling things over for the next semester for people. That's more of a renewal instead of a due date change. I mean, I guess they could kind of be used in. Unknown Speaker 23:04
Right, it's important to note that those are different functions changing to date versus renewing an item. Because changing a due date, you're modifying an existing loan, but renewing an item you are checking. You're checking against rules and things like that when you're changing a due date, you're not really checking against any rules. Unknown Speaker 23:25
Yeah. So this is actually confirms my ad that this is kind of simplest update for the for the lungs, because if we start venturing into Unknown Speaker 23:41
well, it's not as simple as you would hope. Okay, I'm going through the questions, but there are definitely dependencies here. Unknown Speaker 23:51
So please go ahead. Unknown Speaker 23:54
So the major dependency that I can think of is with fees and fines if you change the due date for something that is overdue Unknown Speaker 24:06
or is age to last? Yeah, we'll get we can get to that in a second. Jennifer? That's a good question. Unknown Speaker 24:17
And if an item is recalled, you can change the due date on that item already. But you may that may have influences on Yeah, I'm just thinking out loud that may have dependencies or implications for if the item had been recalled what happens to the recall request. And then if the Unknown Speaker 24:50
if if it's like in the if there's a request queue behind it, does anything change there? So Unknown Speaker 25:00
Yeah. So would you like to change the due date? If the item is recalled? Unknown Speaker 25:13
In this case, there are definitely use cases for doing that. Unknown Speaker 25:16
So yeah, because the library's close, so even you guys did you date? Okay? Unknown Speaker 25:21
They're absolutely use cases for doing that. And that check it in the checkout or the user loans. The user record loan view does not stop you from doing that if an item has been recalled. Unknown Speaker 25:35
And what would be the expected behavior? If the if the item is a marked as h2 last? Unknown Speaker 25:45
That's a good question. And I might have to go try it. Because less Thomas or anybody else who's lived knows what happens, I would have maybe have to go try it. Because if I change a due date, I might reopen a loan, but I don't know if the loan would then change that. That would then change the item status, right? Because you can change a loan due date. But if the item status is ah to last, I don't think that changing the due date changes the item status. Unknown Speaker 26:21
I don't think it does either. I think renewable changed the item status, if you can we know through last? I don't I think you're correct. I think if you just change the due date, you just change the due date. Unknown Speaker 26:35
And no changes in the industry item status. Unknown Speaker 26:41
Yeah, I don't think it does. So you do have the potential there, then to screw some things up? I think the question is more like, how would you what's the expected behavior? And then how do you work with that? Right? Do you expect the bulk edit app to do things? Or do you just document it and say, Hey, if you do this, you then have to go run an item, bulk edit and change the item status or something like that. Unknown Speaker 27:21
This is where it gets really tricky when you get outside of circle logic. Unknown Speaker 27:24
Right? And Thomas, I don't I can't recall if we have discussed this might be honestly, this might be something needs to go there are a segue. Because I don't I don't know. I don't know what they would expect. I also have this memory. And I'll have to check with Burks. Travis, I have this memory, that there's an API for change due date, but that the UI doesn't use it for some reason. The UI just doesn't put to loan records. Go ahead, Thomas. Unknown Speaker 27:59
I was gonna say I'm in our test system right now. And I pulled up something that was aged to last. And in the UI, the change due date function is disabled. So my guess is that it was disabled. Because if you try to change the due date, it's gonna mess up a bunch of business logic, somewhere down the line. Unknown Speaker 28:17
Way, and I'm sorry, say that again. So if it's H and H to last item, you can't change the due date? Unknown Speaker 28:23
No, it's completely Unknown Speaker 28:24
grayed out. Okay. And that's not a permissions issue, because you have full permissions. Unknown Speaker 28:30
Yeah, I follow you, I have full permissions, right. Unknown Speaker 28:33
So then maybe that transfer Mac does that if it's H to last we would not change. And there may be other statuses, well, if an item is loaned, it should be checked out. Or the other one, the other one you would not change then the other item status that we need to be treated the same way we'd be declared lost, because declared lost also has an associated fine record. So Unknown Speaker 29:03
what about claimed return? Because that kind of throws in a weird limbo, Unknown Speaker 29:09
right. But if it's claimed return the loan is open. Can you claim an item return and change the due date? Do you have an example? You could try that on? Okay, well, that Tom, let's try that. Right. That may be another one where you wouldn't want to do that either. Because if it's clean return, there should be no return date on the record. But there is a due date on the record. I'm sure all the tech services people love listening to me proud along. Yeah. To answer your second question there. It should not include loan and return dates. Those are those are on the record and you You should not change those. There is a feature to back data return. But I would not back data. I would want to look at that separately. Unknown Speaker 0:00
All right, but if it's claim returned and the loan is open can you claim an item return and change the due date? Do you have an example? You could try that on? Okay, well, that Thomas, try that. Right? That may be another one where you wouldn't want to do that either. Because if it's clean return, there should be no return date on the record. But there is a due date on the record. I'm sure all the tech services people love listening to me prattle on. Yeah. To answer your second question there. It should not include loan and return dates. Those are those are on the record, and you should not change those. There is a feature to back data return, but I would not back data. I would want to look at that separately. Unknown Speaker 1:04
I agree, because I think it will increase even in you will increase the complexity if we start looking into renewal, because we need to check the policies about the allowed number of renewal and all this things. So that's good. And that question to the third question specify as what should be specified as a loan action? I saw that. I saw that. Currently, when you update in the user record in the loan records, if you change the manually change the due date, the action is due date change. I was wondering if we need to include a new a new action that would be bulk? They bio bulk due date change? Or is? Unknown Speaker 2:16
That's a good question. So where those actions often show up, there's not just in the loan record, but in the circulation log. I can't remember if the circulation log has a due date change as an action when we look and see. Unknown Speaker 2:37
So Unknown Speaker 2:42
it does. So if I bulk edited, you know, 100 loans and change their due date, I would want them to show up in that circle log. And that's probably where that that loan action is, is important. And so we could add a loan action that would then have, but that would then have a dependency on work in the search log to make sure that it showed up there. I'm not entirely sure everywhere that that is used. And I'm not sure how that might be used in reporting. Because I should be able to do a record and be able to look at or change due date and be able to see the user who did it. Unknown Speaker 3:26
But this, this will be recorded anyway. Sure. The metadata, Unknown Speaker 3:33
I think I would like to ask. That's another good questions, maybe for the arrows, or the RA SIG. Maybe also maybe to see if there are other cases where we've had something like this, and how we've treated it in terms of the circle log. The Pio for the circle log is still Stephanie buck. Unknown Speaker 3:53
Yes, I can reach out to her and the same development team that I'm working with was working on circulation long. Unknown Speaker 4:03
Without any other here, is there any reason we can think of to add another loan action? Yeah, absolutely. Unknown Speaker 4:11
I mean, the other possibility is you could change the source, instead of having a username, you could have a username and balk at it. So that kind of falls on the pattern. It uses the same filters everything else. Unknown Speaker 4:25
I think so what is happening right now, if the user if the bulk edits, the bulk edit is triggered by the user. So the bulk edit the record modified by the bulk edit has the user Unknown Speaker 4:42
right, versus just pulling from the metadata object? It wouldn't have anything extra in there. Yeah. Unknown Speaker 4:50
So I did go in and set up a test case and try things returned once you hit clients return renewal and change due date is not an option. So it looks like the only time you can change a due date is if the item record is open, or the sorry, the cert record is open. Unknown Speaker 5:07
The loan is open. And yes, it's checked out. Correct? Correct. Okay, so there's the answer, Magda. Unknown Speaker 5:15
Thank you. So for all other statuses, Unknown Speaker 5:22
you would deny Unknown Speaker 5:23
it would deny that and report it. Right? Yeah, I Unknown Speaker 5:27
would, that would definitely be something you would want recorded back. Yeah. Unknown Speaker 5:32
So the question number five, the record should Unknown Speaker 5:37
know, you would not be able account because this isn't a renewal. Unknown Speaker 5:42
Exactly. And then how the record should be identified? The loan records? I know, what would make sense, it's definitely a bill that the creditor has shown me the the, the loans for a specific user. But in our case, we will probably not have this option. But we can still submit the identifiers. Unknown Speaker 6:08
So yeah, there's no HR ID for a loan. Unknown Speaker 6:12
Okay, this simplifies, Unknown Speaker 6:15
there's just a UU ID on the loan record. I would not do it by location. Because that's, I don't know what you would mean by location. Unknown Speaker 6:27
I think that was one of the use case that they said that they would like to change. And I think this also fall into the case that some part of the library is being closed. So then you would identify this part of the library by locations, so then you submit the list of your locations, locations, you would Unknown Speaker 6:57
rate but I could, there could be scenarios where a particular library is closed, but the locations of the items that you want to change the due dates on could be all over. Because it could be like the main, you know, the service point for this particular remote campus is closing. And so we don't want the users to have to return things there. But we're going to, but they may have books from other multiple branches, right? So is this a thing where we can say please do it by more than one identifier? Like we've done in other cases? Or do we need to like really specify it down? Unknown Speaker 7:44
So that makes sense. Can you repeat, because I think I miss Unknown Speaker 7:50
Sure. Yeah. I guess I'm saying like, how many? How many? identifiers? Can we ask for, like alone you your ideas obvious to me, because especially if you have access to a reporting tool, because you can, not every library does, obviously, but you can use a reporting tool, and you can get a list of loan UU IDs, and then you can just feed it in a bulk edit tool. I think item IDs probably also make sense item barcodes. Because I could see scenarios to and that is that you can extrapolate to a location right? You can say show me all the barcodes in this particular location. I will say that I do think this needs to be able to report, I would say that it might be common if I have a list of barcodes to set it into Bulk Edit. And to say that at least some of those maybe aren't actually on loan. Right? Like let's say that this location that has 1000 books, I want to extend all the loans and all I have is a list of orders. So I'm just going to send 1000 barcodes into here. So if this process to change the due date, and I give it a list items, and it doesn't find a loan on the item, that should be reported back, right. But I do think item barcodes and item UU IDs and make sense to me. User UU IDs also makes sense. Because you could for example, say, you know, this group of 1000. You know, this group of 50 users was on a trip to South America and they're stuck there for a month. And I just want to renew all their books or change the due date on all their books. So that would also be something that I would think people would want to be able to do. Unknown Speaker 9:45
Even with users I Unknown Speaker 9:46
would say if possible user our patron type Unknown Speaker 9:52
okay Unknown Speaker 9:55
yeah, I couldn't see that. I could see that or patron group back then. Yeah. This is just that could lead to a scenario with performance issues. You know, you could do because if you're submitting like a list of if you're saying Please do this for all the patrons and group faculty. I could be a lot. And there are definitely use cases to do that. But yeah, I don't Yeah. Unknown Speaker 10:25
The other one, too, since we're dealing with cert records. I don't know what you want to also filter by Unknown Speaker 10:34
loan policy. Unknown Speaker 10:39
If you had a bad loan policy that you need to clean up, Unknown Speaker 10:44
but then would you if you have a bad policy? Will you be using it to identify the records that need to have the due date? It's Unknown Speaker 10:56
stored on the loan? Yeah. So So what Thomas's imagining is, like, you know, we loaned books for a month, and then we were like, Oh, crap, these all got the wrong due date. And we went in and fix the loan policy, but those existing loans don't get updated when you do that. So I, I would not make that as higher priority, but I do think that would probably be pretty simple to do in the context of the work they're doing, because it is the you UID for the loan policies stored on the loan. Right. So yeah, that's an interesting idea. Yeah. Yeah. And I saw Bob, nodding his head. So yeah, Unknown Speaker 11:37
yeah. I mean, we've changed long rules. And that's always an issue. Yeah. Unknown Speaker 11:45
So the question I have is, I'm sorry, I'm going back to this. Are you sure we don't need location? Unknown Speaker 11:57
I agree. I'm not sure how you would. So I'm looking, I'm actually looking at the ramp at the loan record. Unknown Speaker 12:06
Because I'm trying to see what what's actually stored on it. So there's actually what I'm trying to see is there's actually not a location on the loan. Unknown Speaker 12:20
What you see in the UU ID is stuff that's extrapolated from the item record. But there's actually not Yeah, well, okay. So there's an effective location at checkout of the item loan to the patron. Um, I mean, I'm sure there are libraries that would use that would do that. And so, you know, if it's, if it's something that can be done. Sure. I guess I just I think Unknown Speaker 12:48
it's not the highest priority, I would Unknown Speaker 12:51
not consider it the highest priority. Unknown Speaker 12:54
I would say even what might be higher than that is service point. What service point was checked out from going back to the loan type is you have a service point as a bad calendar, you need to fix something. Unknown Speaker 13:05
Yeah, yeah. There's also a checkout service point idea that's on the record. Yeah. Yeah, I agree with Thomas. Unknown Speaker 13:15
Yeah. But I also agree with what Aaron was saying before with location is patrons could have things checked out from different service points, different locations all over the place. So trying to narrow down a specific group of things that need to have their due dates changed by that criteria. Unknown Speaker 13:32
Yeah, right. So Christina is saying in the chat that she thinks Michigan State when you use location if it was available, Unknown Speaker 13:38
okay. So, yeah. Unknown Speaker 13:43
And that can definitely, I can imagine that being something that smaller libraries would probably use more than bigger libraries, even though Michigan State is obviously very. I know that for libraries that are similar, a lot of times their locations are smaller. And so that may be something that extrapolates a lot more sensitively for them. I also know that the Center for Research Libraries is using their location tree to like extrapolate to their membership, and so I could see them really wanting that. So yeah. Yeah, and Jen is pointing out that reserves sometimes are, are location based, and you could want to do it there. Yeah, that that makes a lot of sense. I don't know how often you would change a due date for short term loans, but there's definitely scenarios where Unknown Speaker 14:41
this was a great discussion. Is there anything else that you think I should keep in mind while gathering the requirements? For this? Request? Hold the sorry, not request the alone due dates. Unknown Speaker 15:02
Well, I will let the Scorpios know that we talked about this today. You know, Unknown Speaker 15:08
I will schedule in a time with the essay to discuss and review it. I'm not sure what they do the who is the convener of the Unknown Speaker 15:20
conveners. Jana? I think that somebody I think she's on vacation right now and somebody else is covering for her. It's Cornelia Arrhenius. Okay. Okay. It's covering for her right now. So you could try both Cornelia and Jana. And and the group meets Mondays and Thursdays, Unknown Speaker 15:44
okay. We'll probably not be able to meet this Thursday, but maybe Monday. Thank you. Thank you very much. Unknown Speaker 15:55
And they would also for request, hold shelf expiration dates, they will also be the group to talk to about that. So we can, okay, I need to drop off of that. 1055. Just FYI. Unknown Speaker 16:06
So you're saying that for the request called updates, I shouldn't Unknown Speaker 16:12
shelf expiration date, you have the whole thing in the sentence. And then you have just request hold date in the column on the left. So just to be clear, we're talking about the whole shelf expiration date? Yes, Unknown Speaker 16:23
we are talking about hold shelf expiration date, we are not talking about request expiration date, unless you think it would make sense to combine them. Unknown Speaker 16:35
So right now, the request expiration date is not set by anything. There's nothing that puts that on by default. You can put a date in there if you want, but it's optional. So I think there are scenarios where you would want to be able to do that. And so, but I don't know that it needs to be part of this feature. Unless it's simple to do. If that makes sense. I think the need the use cases for the hold shelf expiration date are much more common. And they're going to be very similar, have similar use cases to the loan, due date change, it's going to be the building is inaccessible for some period of time it's going to be it might be things like, you know, our our van is broken down. And we kept making deliveries for two days, that has happened to do more than I would like to care to admit. And so you want to just give a little bit more time for hold for requests to be manageable. Unknown Speaker 17:39
Okay. Oh, should the should the request status, which request status just shouldn't be impacted? Unknown Speaker 17:48
So there's only one it's going to be? Let me pull up the request app, it's going to be awaiting open a waiting for pickup. Unknown Speaker 18:01
And this is the only one. Unknown Speaker 18:04
Because what am Thomas please correct me if I'm wrong, open awaiting delivery doesn't get a whole shelf expiration date, because it's not going on a hold shelf? Unknown Speaker 18:12
We've asked correct, but we don't use delivery. So Unknown Speaker 18:16
yeah. So it's really just open, awaiting pickup. And then the request types that should be impacted would be all of them. Because all request types end up on a whole shelf eventually. Unknown Speaker 18:36
Or those that aren't being delivered, right? Unknown Speaker 18:41
Well, but you can have a hold that's delivered a page that's delivered every call that's delivered. Okay. So, but go ahead, sir. Yeah. But you're also gonna have all three of those end up as open awaiting pickup. So. Unknown Speaker 18:58
Yeah. And this similar question about the how the request should be identified. Unknown Speaker 19:06
Definitely pick up service point. And definitely a request ID there is no request, HR. You can all right, you could also do it by user ID. Or I can't imagine why you would do patron group, but user ID for sure. Unknown Speaker 19:32
The only thing I could think of for Patreon group would something with like, when we first enter COVID where all the undergrads got kicked off campus. That's the only thing I could think of that scenario. But Unknown Speaker 19:45
sure, yeah. Unknown Speaker 19:49
Yeah, yeah. Unknown Speaker 19:51
In that case, I feel that we would just extend everything so right Unknown Speaker 20:03
Okay, so I think I got a lot of information for those two and I will follow up with to circulation peer, and we are a singer. Hopefully next week and come I will come back to this group if I have more questions. And the next one is about the permission, removing or adding permission to the existing to the users. And I am nervous when it comes to permission, and I'm glad that we have Aaron here. But what would be the most common use case for removing or adding permission? Someone is leaving the university or joining the University? Student began university it's employment. Yeah. Okay. Unknown Speaker 21:05
It's your you're joining library employment, you're leaving library employment. Amanda is also pointing out in the chat that you're changing job duties. So maybe you're a staff member, but you're moving to a different role. Jennifer is saying the most common is student employees. And that's absolutely true. That's the that's the case, though of you're joining the library, you're leaving the library? Unknown Speaker 21:30
I think that'd be our biggest use case would be just an employment, individual users, we probably just changed the UI. Unknown Speaker 21:37
Okay, so you would identify that the permissions by user barcodes and user groups Unknown Speaker 21:46
are not just barcodes, any identifier? Yes, user identity UID, external system, barcode and username. I personally wouldn't do it by user group. Because when you're hiring a student, you're not usually changing their user group. But I don't know if other libraries would have that use case. Because it's also not. There's also I think, use cases that are like, right, because because you're really talking about employment groups, and they don't employment groups don't translate to patron group at most libraries. Okay. Unknown Speaker 22:34
This is to identify the records. So wouldn't you want to identify a group called students as a group to take away their search? Permissions? Unknown Speaker 22:47
Not unless I'm firing every single student worker? Well, I Unknown Speaker 22:51
mean, not really like in our case, we're small. So we have, you know, a handful of students. And if we were going to use their user record for their permissions, you know, at the desk, and then every semester we change staff, but in that case, we probably just do them one at a time. Are many Unknown Speaker 23:11
is also saying that most libraries don't, don't have that kind of all or nothing turnover. Right? Right. I might have 40 students leave and students remain. So Unknown Speaker 23:23
you're right. Yep. Yeah. Unknown Speaker 23:25
Is there anything in the permissions with that? Non library staff would need to use something like self checkout? Are I just, I'm just trying to think of any weird permissions that might have to be added to our large group of people because of an external service? Unknown Speaker 23:49
No, because you should have an edge module in most cases, and the edge module, does it. Okay, um, Christine is mentioning that being able to search by an assigned permission set would be useful. Okay, when assigned permission, I could definitely see that scenario. So I have no permission set called student desk workers. And please show me every user that has this permission set, and please take it away from them, that we Unknown Speaker 24:15
assign permission. Yes, this is. Unknown Speaker 24:18
But there's also I think there's a technical piece to this that's worth keeping in mind, it might be worth talking to, I think core platform about whether you edit the existing user permission record or whether you just delete the permission record, it's worth talking to core platform about the right way to do that. But that's a little a little rabbit holy, sorry. Unknown Speaker 24:45
I know this be very niche, but what about a silencer service point? Now Unknown Speaker 24:53
because you know well, I mean, But yeah, I guess you're talking about the assigned service point on the user record. Unknown Speaker 25:08
I guess. Yeah. I was I was thinking about the request record. But yeah, yeah, you could see that. So, you know, I want to see all the, I want to take permissions away from all the people who were assigned to XYZ permitted Service Desk, Unknown Speaker 25:24
or bumped them up to a different permission or changed your permissions, or change Unknown Speaker 25:28
their permissions. Yeah, that's, that's probably more likely, you know, although in that case, you should be using permission sets and just changing permission set. Unknown Speaker 25:38
True, true. I just trying to think of other clients, and that one, I would put as definitely a lower priority, because it would definitely be focused more on circulation. Sure, and there'll be other ways to get that data. But sure. Unknown Speaker 25:53 |