WEBVTT 00:06:48.000 --> 00:06:56.000 Zoom changed its interface again. 00:06:56.000 --> 00:06:59.000 Hello, everyone! 00:06:59.000 --> 00:07:21.000 Hello. 00:07:21.000 --> 00:07:25.000 How's everyone faring? 00:07:25.000 --> 00:07:31.000 I'm doing okay. We went from 16 degrees on Monday, going to be almost 80 today. 00:07:31.000 --> 00:07:37.000 We're in the opposite direction, but yeah, similar. 00:07:37.000 --> 00:07:38.000 It feels like that, doesn't it? 00:07:38.000 --> 00:07:43.000 They set the weather by a roulette wheel. 00:07:43.000 --> 00:07:44.000 Ugh, do not feel better. Thank you, Cornelia. 00:07:44.000 --> 00:07:46.000 Do you feel better, Susan? Aww. 00:07:46.000 --> 00:07:48.000 I'm sorry. Yeah, I've been… 00:07:48.000 --> 00:07:51.000 I have been very… I mean, it's… 00:07:51.000 --> 00:07:58.000 Did people just say just a cold? It's just a head cold, but oh my god, yes, I'm really in the worst of it. 00:07:58.000 --> 00:08:04.000 But I'm here today, this is my first day back after I worked half a day remotely yesterday, but… 00:08:04.000 --> 00:08:09.000 I… I caught up on lots of TV shows on Monday and Tuesday. 00:08:09.000 --> 00:08:11.000 So that was good. 00:08:11.000 --> 00:08:14.000 I wish I felt better. I'm here, though. 00:08:14.000 --> 00:08:18.000 It's gonna be a short week, and I just gotta power through. 00:08:18.000 --> 00:08:25.000 Um, but you guys get to see my face. Everyone here gets to see my mask, so… 00:08:25.000 --> 00:08:28.000 All right, um… 00:08:28.000 --> 00:08:31.000 So, we are… 00:08:31.000 --> 00:08:34.000 Continuing our ticket review… 00:08:34.000 --> 00:08:36.000 Um, we are up… 00:08:36.000 --> 00:08:41.000 to… let me see… ticket number… 00:08:41.000 --> 00:08:43.000 What did I say? 2650… 00:08:43.000 --> 00:08:46.000 6. Um… 00:08:46.000 --> 00:08:51.000 So… I am going to… 00:08:51.000 --> 00:08:57.000 do what we usually do and share my screen. I'm trying to think if I have any announcements between… before… 00:08:57.000 --> 00:09:01.000 that. Um, I guess I will say that on… 00:09:01.000 --> 00:09:04.000 Um, Monday… 00:09:04.000 --> 00:09:09.000 Not this Monday, next Monday now, um, we will be doing… 00:09:09.000 --> 00:09:13.000 Um, we hopefully will have a little time to look at our description. 00:09:13.000 --> 00:09:18.000 But I was also able to get, um, Martina from… 00:09:18.000 --> 00:09:23.000 Which… which sick is she from, Cornelia? 00:09:23.000 --> 00:09:24.000 ERM? 00:09:24.000 --> 00:09:25.000 Acquisitions. Acquisitions, I think. 00:09:25.000 --> 00:09:28.000 acquisitions? Okay. Um… 00:09:28.000 --> 00:09:38.000 And she's gonna come, and we've been talking about getting her to come and talk to us about how they've done the prioritization process in the acquisition SIG. 00:09:38.000 --> 00:09:40.000 Which was now, like, a year… 00:09:40.000 --> 00:09:44.000 More than a year ago, year and a half ago. Um… 00:09:44.000 --> 00:09:49.000 Our plan was originally to do this ticket review, and then to have 00:09:49.000 --> 00:09:54.000 then to talk about prioritization. We didn't think it was going to take us a year and a half, but here we are. 00:09:54.000 --> 00:09:56.000 still doing ticket review, because we have so many tickets. 00:09:56.000 --> 00:10:01.000 Um, but I think it's now time to think about how… 00:10:01.000 --> 00:10:06.000 to start hearing about how others have done the prioritization of their features. 00:10:06.000 --> 00:10:10.000 And how we might learn from that, and maybe adapt it to how 00:10:10.000 --> 00:10:13.000 to our environment, what we… what we have. 00:10:13.000 --> 00:10:17.000 So, we're gonna hear from Martina on… 00:10:17.000 --> 00:10:22.000 Monday, and we'll be able to ask her questions about how that went, 00:10:22.000 --> 00:10:25.000 And then we'll be able to figure out 00:10:25.000 --> 00:10:27.000 as we approach the end of this process, 00:10:27.000 --> 00:10:31.000 what is… what is our prioritization gonna look like going forward? 00:10:31.000 --> 00:10:38.000 So that is the plan for Monday, and hopefully folks can make it there. 00:10:38.000 --> 00:10:42.000 But for now, let's look at our… 00:10:42.000 --> 00:10:44.000 tickets. So we have, um… 00:10:44.000 --> 00:10:50.000 For the folks that haven't been here before, um, Cornelia updates our spreadsheet, 00:10:50.000 --> 00:10:54.000 Which is linked, you can follow along at home, it's linked in the agenda. 00:10:54.000 --> 00:11:00.000 Um, and then the link to all remaining RA-related tickets is a JIRA search. 00:11:00.000 --> 00:11:02.000 Um, or filter that… 00:11:02.000 --> 00:11:06.000 Kalila made for us. 00:11:06.000 --> 00:11:08.000 And while… 00:11:08.000 --> 00:11:14.000 I don't know what Cornelia was doing, but she discovered a few others that didn't seem to be in this list, so… 00:11:14.000 --> 00:11:19.000 When we're done with this, we may have to do a little bit more trolling to find out if we've truly gotten all of our… 00:11:19.000 --> 00:11:24.000 all of our tickets that are related to RA. 00:11:24.000 --> 00:11:32.000 Alright, so, um, Cornelia's gonna update the spreadsheet, and she will also update the… 00:11:32.000 --> 00:11:36.000 Um, I can't get my… grab my thing here… 00:11:36.000 --> 00:11:39.000 She's also going to update… 00:11:39.000 --> 00:11:44.000 the, um, tickets themselves. 00:11:44.000 --> 00:11:49.000 And I will share my screen, which is where? 00:11:49.000 --> 00:11:55.000 Here it is. 00:11:55.000 --> 00:11:58.000 Alright, so do people see this? 00:11:58.000 --> 00:12:01.000 25… 2656… 00:12:01.000 --> 00:12:02.000 Yep. 00:12:02.000 --> 00:12:05.000 Configure whether comments are required on loan actions. 00:12:05.000 --> 00:12:12.000 So, let's take a look at this one. 00:12:12.000 --> 00:12:19.000 So, some actions in loans require comments, so when you do overrides for checkout or renew, 00:12:19.000 --> 00:12:23.000 Um, claimed, returned, or declared lost. 00:12:23.000 --> 00:12:25.000 those all require a comment. 00:12:25.000 --> 00:12:30.000 Um, this feature would allow that to be configurable, so that you could 00:12:30.000 --> 00:12:35.000 comment could be the required or not. 00:12:35.000 --> 00:12:44.000 That would be make it comparable to how it is within the fees and fines area. 00:12:44.000 --> 00:12:49.000 Any thoughts about whether or not this is still… 00:12:49.000 --> 00:12:51.000 necessary, needed. 00:12:51.000 --> 00:12:55.000 desired. 00:12:55.000 --> 00:13:12.000 institutions wanting it. However, it really substantially slowed thing operations down in a circulation desk. And how often people need to go back and verify the comments. But it'd be more of a local institutional issue. So I would say if it would continue, it'd be a low priority. 00:13:12.000 --> 00:13:14.000 Yeah. 00:13:14.000 --> 00:13:19.000 There's no way to turn them off right now, or to not require them right now. 00:13:19.000 --> 00:13:22.000 So, that could potentially… 00:13:22.000 --> 00:13:26.000 If it were optional at the tenant level, then potentially. 00:13:26.000 --> 00:13:33.000 It could speed things up. 00:13:33.000 --> 00:13:37.000 Okay, it looks like… hmm… 00:13:37.000 --> 00:13:40.000 probably needs more refi… oh, it's open! 00:13:40.000 --> 00:13:41.000 Does… I mean, it doesn't… 00:13:41.000 --> 00:13:46.000 Yeah, it doesn't need a lot more refinement, but I think where should the setting go, and stuff like that. 00:13:46.000 --> 00:13:49.000 Right, yeah. 00:13:49.000 --> 00:13:50.000 Okay. 00:13:50.000 --> 00:13:53.000 needs to be clarified. 00:13:53.000 --> 00:13:57.000 Alright, well, let's leave it for further refinement. 00:13:57.000 --> 00:14:02.000 Um, this one is blocked currently. 00:14:02.000 --> 00:14:17.000 request. Allow override of prevented pickup service point. 00:14:17.000 --> 00:14:18.000 Is it one of these? 00:14:18.000 --> 00:14:24.000 Yep, that's connected to the one I mentioned that isn't on the list, and I don't know why. It's, um, it's linked. It's… 2, 6… The… wait, it's 2649. 00:14:24.000 --> 00:14:28.000 Oh. Is it linked down here? 00:14:28.000 --> 00:14:29.000 Oh, yeah. Allow override of request policy. 00:14:29.000 --> 00:14:32.000 Yes? Yes. 00:14:32.000 --> 00:14:38.000 Oh, so that's… that's one we definitely have wanted. 00:14:38.000 --> 00:14:42.000 So this one is similar, except that it is… 00:14:42.000 --> 00:14:45.000 based on its… 00:14:45.000 --> 00:14:48.000 pickup service point is prevented. 00:14:48.000 --> 00:14:50.000 So this is more the… 00:14:50.000 --> 00:14:57.000 I mean, it's a similar override, but it's a very… it's a more detailed… 00:14:57.000 --> 00:15:06.000 Yeah, the other one overwrites the request if it's not allowed by policy, and this one overrides this pickup service point if it's not allowed by policy. Yeah. 00:15:06.000 --> 00:15:09.000 Right. So it seems… 00:15:09.000 --> 00:15:12.000 similar, but it's blocked because the other one isn't… that's what it's blocked by? 00:15:12.000 --> 00:15:18.000 Yeah. It's blocked by prevent local page requests. That's 2690. 00:15:18.000 --> 00:15:21.000 9-0, okay. 00:15:21.000 --> 00:15:34.000 Um… That's… yeah, that's similar. It might be if we have the evidence for 9, it might not be really needed. 00:15:34.000 --> 00:15:35.000 Alright. 00:15:35.000 --> 00:15:42.000 Or no, no, it's the other way around. It's similar to the one we already have to enable request policy. 00:15:42.000 --> 00:16:00.000 To determine a load pickup service points. It's like abbreviation of this one, so that you just… so you don't need to click all the service points you… you want, but just can say no, no locals. 00:16:00.000 --> 00:16:01.000 Yeah. Yes. 00:16:01.000 --> 00:16:05.000 Oh, I see. Local, as in, like, you can't page your own. I mean, like, you will not page for your own users. Gotcha. 00:16:05.000 --> 00:16:09.000 Yes, we… 00:16:09.000 --> 00:16:10.000 for your… right. 00:16:10.000 --> 00:16:12.000 For your… for your location, for your location. 00:16:12.000 --> 00:16:17.000 That makes sense. Okay, but that… that's interesting that… 00:16:17.000 --> 00:16:20.000 That's interesting that the local page request 00:16:20.000 --> 00:16:24.000 is a blocker for this one. 00:16:24.000 --> 00:16:25.000 It is not really. Yeah. 00:16:25.000 --> 00:16:29.000 I did, yeah, I don't understand why that would block that functionality would block… 00:16:29.000 --> 00:16:33.000 this, but who knows? I understand why 49… 00:16:33.000 --> 00:16:36.000 Or 8-9 would, but… 00:16:36.000 --> 00:16:37.000 The managers did that. 00:16:37.000 --> 00:16:38.000 But that would just get developed. 00:16:38.000 --> 00:16:44.000 Yeah, Kate might have just did that because she was thinking that she wanted to do this after. 00:16:44.000 --> 00:16:51.000 to prevent local page requests, thinking that that would be the reason why you would need to override it, was to allow a local page request. 00:16:51.000 --> 00:16:52.000 Gotcha. 00:16:52.000 --> 00:16:54.000 And that's why she set up as a blocker. 00:16:54.000 --> 00:16:58.000 Yeah, that makes sense. 00:16:58.000 --> 00:16:59.000 Alright. 00:16:59.000 --> 00:17:22.000 No. But it isn't really, because, I mean, the other one, like, uh… Determine allowed pickup service point. That was a blocker, but now that we have that, and we have been having that for, like, 3 years or, um… 00:17:22.000 --> 00:17:23.000 Yeah. 00:17:23.000 --> 00:17:26.000 This would be very much needed. And we talked about those two… With Anne, I think, 2 or 3 times, but uh… Nothing happened. 00:17:26.000 --> 00:17:46.000 It still needs more refinement, but we have… We were going forward, we had some ideas about this, and it's all somewhere in the notes, and I sent it to Anne. But yeah, as it's not assigned to a team, so… 00:17:46.000 --> 00:17:49.000 That's why it gets lost in the discussions probably. 00:17:49.000 --> 00:17:51.000 Right. Do you think it still needs refinement? 00:17:51.000 --> 00:17:54.000 So maybe. 00:17:54.000 --> 00:18:07.000 Would this be for requests that are done in the request app or through the locator webpack? I'm assuming it'd be done through the through Folio, where you'd have to just build place requests out of an override on it. 00:18:07.000 --> 00:18:22.000 Um… I'm wondering if it'd be simpler is to have a designated, um, like an office delivery service point. But again, would be like, if you have that available, how do you keep people who are not, uh, certain patron groups been using it? 00:18:22.000 --> 00:18:38.000 So I'm kind of like, I see used to it. I guess be more like the libraries feel they would have a need for it. I'm just thinking it is more complexity and how likely or often would this need to come up as an issue where someone normally would not need. 00:18:38.000 --> 00:18:44.000 A novice delivery would not require it. 00:18:44.000 --> 00:18:50.000 I think it would come up more the more that you utilize the restricting of service points by CERC rules. 00:18:50.000 --> 00:18:52.000 Or pickup locations by circles. 00:18:52.000 --> 00:18:59.000 So if you have open surface points where anyone can request anything to go to any service point, I don't think this will come up. 00:18:59.000 --> 00:19:07.000 But once you start adding those restrictions, like you were saying, like, you have a certain patron group that can only get office deliveries, 00:19:07.000 --> 00:19:10.000 we have ran into… 00:19:10.000 --> 00:19:16.000 situations kind of like this, and even then, we didn't use it that much. It was… we had people that… 00:19:16.000 --> 00:19:19.000 We're blocked from doing… 00:19:19.000 --> 00:19:25.000 We call it faculty office delivery. Uh, they were blocked from doing faculty office delivery, because in the system, they weren't marked as faculty. 00:19:25.000 --> 00:19:34.000 But they actually were, so staff could go in and place a request… had to go in and place a request for them, because they were able to do it through the OPAC. 00:19:34.000 --> 00:19:48.000 Um, in those cases that we would have needed this, but we no longer do that service, and even when we did, that was a very, like, edge case. 00:19:48.000 --> 00:19:52.000 All right, so it looks like this one needs a little more refinement. 00:19:52.000 --> 00:19:54.000 Cordelia, so let's put that on this one. 00:19:54.000 --> 00:20:02.000 Yes, should we? Would it be possible to assign this to a development team so it doesn't get forgotten again? 00:20:02.000 --> 00:20:12.000 It would, uh, this would probably be Vega. 00:20:12.000 --> 00:20:15.000 Okay. 00:20:15.000 --> 00:20:20.000 Thank you. 00:20:20.000 --> 00:20:26.000 Alright, bulk APIs for circulation storage module. This one is opened. 00:20:26.000 --> 00:20:37.000 Which, in theory, means it's ready to go. 00:20:37.000 --> 00:20:43.000 Oh, this is about migrations, right? 00:20:43.000 --> 00:20:45.000 It is, um… 00:20:45.000 --> 00:20:50.000 But this is potentially work that would have to… that could or should be done? 00:20:50.000 --> 00:20:52.000 for… 00:20:52.000 --> 00:20:54.000 Walk at it. 00:20:54.000 --> 00:20:58.000 Once it hits circulation. 00:20:58.000 --> 00:21:04.000 You think it would scale to my full migration? 00:21:04.000 --> 00:21:08.000 I mean, yeah, I mean, usually when you do the bulk API, you can send 00:21:08.000 --> 00:21:12.000 either 100 or a few hundred. 00:21:12.000 --> 00:21:13.000 Yeah. 00:21:13.000 --> 00:21:18.000 requests at a time. It'd be so faster than doing individual, but… 00:21:18.000 --> 00:21:20.000 Oh, there's a whole bunch of… 00:21:20.000 --> 00:21:23.000 Oh, these are all related. Those are all… 00:21:23.000 --> 00:21:27.000 build on this, okay. 00:21:27.000 --> 00:21:29.000 Alright. 00:21:29.000 --> 00:21:30.000 How will this take it? 00:21:30.000 --> 00:21:34.000 Ah, 2020, most of these are… 00:21:34.000 --> 00:21:35.000 Okay. 00:21:35.000 --> 00:21:36.000 Yeah, October 2020? 00:21:36.000 --> 00:21:43.000 I'm wondering if there's even really a pain point anymore. Um, for migrations. 00:21:43.000 --> 00:21:44.000 Yeah. 00:21:44.000 --> 00:21:47.000 Or if they've found other ways around it. 00:21:47.000 --> 00:21:54.000 I mean, in general, I think that a lot of the places in folio should have bulk APIs, it's just tricky. 00:21:54.000 --> 00:21:58.000 Because how you handle the responses. 00:21:58.000 --> 00:22:05.000 Or how you… how the response is generated, but… 00:22:05.000 --> 00:22:08.000 Do you think this one needs more refinement, or do you think it's… 00:22:08.000 --> 00:22:12.000 It looks like it's already been written up, including the… 00:22:12.000 --> 00:22:16.000 Cirque stores that are related. 00:22:16.000 --> 00:22:17.000 Okay. 00:22:17.000 --> 00:22:19.000 I don't think it does. It looks okay for me. 00:22:19.000 --> 00:22:22.000 Alright, let's put this as ready for dev. Again, 00:22:22.000 --> 00:22:24.000 It may not get prioritized, 00:22:24.000 --> 00:22:28.000 But I think all of us that have implemented are like, yeah, we don't need… 00:22:28.000 --> 00:22:32.000 It's already been done. Or a vendor does it, or whatever, but… 00:22:32.000 --> 00:22:33.000 Right. An evening. 00:22:33.000 --> 00:22:35.000 We're also supposed to be thinking about 00:22:35.000 --> 00:22:37.000 future libraries also. 00:22:37.000 --> 00:22:39.000 And Ian is a conquer vendor. They do my… 00:22:39.000 --> 00:22:41.000 Yeah, yeah. 00:22:41.000 --> 00:22:42.000 Yeah, exactly. 00:22:42.000 --> 00:22:44.000 it does migrations, so this is coming from Pose Vendor. 00:22:44.000 --> 00:22:45.000 My greeter. 00:22:45.000 --> 00:22:52.000 Exactly. 00:22:52.000 --> 00:22:53.000 Yeah. 00:22:53.000 --> 00:22:54.000 Alright, this one… the next one looks similar, maybe also from Ian, yeah. 00:22:54.000 --> 00:22:57.000 So this is about, can you migrate the fee fines? 00:22:57.000 --> 00:23:02.000 Um, oh, and ready for dev. Alright, so this one's in the same. 00:23:02.000 --> 00:23:04.000 basic boat. 00:23:04.000 --> 00:23:08.000 Cool. Alright. 00:23:08.000 --> 00:23:13.000 2747. This one is also open. 00:23:13.000 --> 00:23:16.000 Oh, this is part of the… this was part of the reserves review. 00:23:16.000 --> 00:23:18.000 So this one's already been… 00:23:18.000 --> 00:23:25.000 looked at, it looks like. 00:23:25.000 --> 00:23:31.000 Yeah, this one is a syncing of the data across. 00:23:31.000 --> 00:23:34.000 I don't know why it's on a roadmap, though. 00:23:34.000 --> 00:23:38.000 Reviewed… so it was reviewed and ranked. 00:23:38.000 --> 00:23:43.000 So I think this one's okay. We could either just leave it, or put it… 00:23:43.000 --> 00:23:46.000 Um… 00:23:46.000 --> 00:23:51.000 ready for dev, I guess? I don't… 00:23:51.000 --> 00:23:54.000 they already looked at it, so I don't know that we need to… 00:23:54.000 --> 00:23:58.000 But we want to tag it with something so we know we looked at it. 00:23:58.000 --> 00:24:03.000 Yeah. 00:24:03.000 --> 00:24:04.000 I know. It's weird that it's open, though. 00:24:04.000 --> 00:24:08.000 It's not exactly ready for Dev, but… 00:24:08.000 --> 00:24:17.000 It might have been created out of the working group, and the default state for new tickets is open. It's in a draft, which is kind of weird. 00:24:17.000 --> 00:24:20.000 It's not… draft is not the default? 00:24:20.000 --> 00:24:21.000 Open is usually the default. 00:24:21.000 --> 00:24:22.000 No, it… 00:24:22.000 --> 00:24:27.000 Which is stupid. 00:24:27.000 --> 00:24:28.000 Oh, it's older, yeah, that one's… 00:24:28.000 --> 00:24:29.000 The reporter Kelly Drake is listed as reporter, so it's old, really old. 00:24:29.000 --> 00:24:30.000 2020, yep. 00:24:30.000 --> 00:24:31.000 Oh, never mind that. 00:24:31.000 --> 00:24:39.000 I could be wrong, but I think syncing information was on top of the priorities. 00:24:39.000 --> 00:24:45.000 And maybe that's why it's, um… To open could be that. 00:24:45.000 --> 00:24:47.000 Yeah, or it just could have defaulted to open. 00:24:47.000 --> 00:24:52.000 Tom could be right about that. 00:24:52.000 --> 00:24:53.000 But it doesn't look like… like, we didn't look at. 00:24:53.000 --> 00:24:59.000 But it is… 00:24:59.000 --> 00:25:00.000 Yeah. 00:25:00.000 --> 00:25:02.000 Uh, how well the ticket is written, like, that part is… wasn't part of the review. 00:25:02.000 --> 00:25:04.000 Oh, okay. 00:25:04.000 --> 00:25:09.000 Yeah, so why don't we just put it in for, um, further refinement? 00:25:09.000 --> 00:25:19.000 Yeah, as I say, it could probably be devped the way it is, it's fairly straightforward, but I could see a few different scenarios that we might want to add there, like what happens if an instructor is deleted from Folio? 00:25:19.000 --> 00:25:22.000 Right. 00:25:22.000 --> 00:25:26.000 Yeah, there probably would be… need more. 00:25:26.000 --> 00:25:30.000 Because there's not… it doesn't even have all of the fields that are in most… 00:25:30.000 --> 00:25:36.000 Like, the use cases and things like that. I guess they're all part of the details field, but they don't… it's not the same structure. 00:25:36.000 --> 00:25:37.000 Right. 00:25:37.000 --> 00:25:41.000 So it probably needs more fleshing out. 00:25:41.000 --> 00:25:42.000 Alright. 00:25:42.000 --> 00:25:43.000 Okay. 00:25:43.000 --> 00:25:51.000 2771, ad created by user ID, username to the course listings display. 00:25:51.000 --> 00:25:57.000 This one, Olga, you guys also looked at. 00:25:57.000 --> 00:26:04.000 Yeah, I think we looked at all course resources, at least the ones we could find. 00:26:04.000 --> 00:26:07.000 So this is probably… 00:26:07.000 --> 00:26:14.000 still… this is probably the same, I would think. 00:26:14.000 --> 00:26:17.000 Although it's pretty… 00:26:17.000 --> 00:26:21.000 straightforward. Is it… does it need more refinement? It's really quite… 00:26:21.000 --> 00:26:28.000 To me, this is just their ask… it's… they… for that, uh, metadata field. 00:26:28.000 --> 00:26:29.000 on the courses. 00:26:29.000 --> 00:26:31.000 So that feels… 00:26:31.000 --> 00:26:32.000 horses. 00:26:32.000 --> 00:26:33.000 Yeah. 00:26:33.000 --> 00:26:35.000 Pretty straightforward. Like, maybe this one is ready for dev. 00:26:35.000 --> 00:26:39.000 quite straightforward. Yeah, a bunch of these look like they're from… 00:26:39.000 --> 00:26:42.000 courses, actually. 00:26:42.000 --> 00:26:47.000 So that one looks ready. 00:26:47.000 --> 00:26:54.000 This one is about just changing the structure of the name. 00:26:54.000 --> 00:26:57.000 For short. This also seems… 00:26:57.000 --> 00:26:59.000 pretty… 00:26:59.000 --> 00:27:02.000 ready, I would think. 00:27:02.000 --> 00:27:08.000 Yeah, a bunch of these do date back. These were Kelly's original ones. 00:27:08.000 --> 00:27:09.000 Yeah. 00:27:09.000 --> 00:27:24.000 I have a question. Would it help to, um… put courses in front of the… Ticket, uh… Name. Like, so we can see… 00:27:24.000 --> 00:27:26.000 See at a glance that it belongs to courses. 00:27:26.000 --> 00:27:28.000 If you wanted to, it helped them stand out by the other title. 00:27:28.000 --> 00:27:31.000 Do you mean here? 00:27:31.000 --> 00:27:33.000 Yeah. 00:27:33.000 --> 00:27:34.000 That could help. 00:27:34.000 --> 00:27:38.000 Yes. 00:27:38.000 --> 00:27:43.000 I don't see any reason why not to. 00:27:43.000 --> 00:27:50.000 I think the next several of these are coarse ones. 00:27:50.000 --> 00:27:59.000 So I think those last two are ready for dev. They pretty straightforward. They're more like just little tweaks, they don't really require a lot. 00:27:59.000 --> 00:28:01.000 Yeah. 00:28:01.000 --> 00:28:12.000 Uh, this one is allow users to add items to courses by using an item search rather than just a barcode. 00:28:12.000 --> 00:28:15.000 This one seems like it would need more refinement. 00:28:15.000 --> 00:28:19.000 Because there's a lot of different ways this could be implemented. 00:28:19.000 --> 00:28:24.000 So, wait, where the previous one? Last name, first name that was ready for Dev? 00:28:24.000 --> 00:28:28.000 Yeah, because it's similar to the prior one, it's very straightforward. 00:28:28.000 --> 00:28:29.000 I mean, I think… 00:28:29.000 --> 00:28:31.000 Okay. 00:28:31.000 --> 00:28:39.000 What it felt because the next one… I'm sorry, I'm… the ad items one, because when it just used the, um… 00:28:39.000 --> 00:28:41.000 general item search dialogue. 00:28:41.000 --> 00:28:43.000 the regular item search, I guess. 00:28:43.000 --> 00:28:44.000 Yeah. 00:28:44.000 --> 00:28:46.000 We could do it that way. 00:28:46.000 --> 00:28:48.000 Because that's… that's a standard modal throughout fully. 00:28:48.000 --> 00:28:55.000 Oh, it actually says that right here, search for the item on the courses page. 00:28:55.000 --> 00:28:56.000 Yeah. 00:28:56.000 --> 00:29:02.000 I mean, probably at this point in time, when this was thought of, that… actually, I can guarantee it, that model wasn't 00:29:02.000 --> 00:29:05.000 available, they would have had to build this from scratch. 00:29:05.000 --> 00:29:07.000 Right. 00:29:07.000 --> 00:29:16.000 Now, it should just be a matter of fact of literally just pointing to that moto and popping the information. 00:29:16.000 --> 00:29:19.000 Yeah. 00:29:19.000 --> 00:29:22.000 So you think this one's ready for dev, then? 00:29:22.000 --> 00:29:23.000 I think so. 00:29:23.000 --> 00:29:29.000 Okay. 00:29:29.000 --> 00:29:36.000 Alright. Oh, this is the one about the fake barcode. Boy, Olga, we've come across your whole slew of them right here. 00:29:36.000 --> 00:29:42.000 They're all right in a row. 00:29:42.000 --> 00:29:44.000 This one, I would say, needs for a little refinement. 00:29:44.000 --> 00:29:47.000 Yeah, we don't know how… what this looks like to add a… 00:29:47.000 --> 00:29:50.000 dummy record without a barcode. 00:29:50.000 --> 00:29:54.000 Or actually, it would… yeah. 00:29:54.000 --> 00:29:55.000 Exactly. 00:29:55.000 --> 00:29:58.000 The idea is to not add an item record, right? 00:29:58.000 --> 00:30:00.000 Or have a different type of item record. 00:30:00.000 --> 00:30:10.000 Yeah, this was one of the… one of the blockers with us for… I mean, we use Ares anyways, but this was one of the blockers why we just said no to courses, because… 00:30:10.000 --> 00:30:18.000 We do a lot of linking to electronic resources, and we don't want to create inventory records for… 00:30:18.000 --> 00:30:20.000 a link to National Geographic. 00:30:20.000 --> 00:30:21.000 Right, right. 00:30:21.000 --> 00:30:23.000 May page, or… yeah. 00:30:23.000 --> 00:30:28.000 Yeah, our e-reserves are totally separate from our print, so… 00:30:28.000 --> 00:30:29.000 Yeah. 00:30:29.000 --> 00:30:35.000 Yeah, I think this one needs further refinement. 00:30:35.000 --> 00:30:39.000 Alright, support for separate reserve tubes? 00:30:39.000 --> 00:30:49.000 Or libraries within a single tenant. 00:30:49.000 --> 00:30:52.000 So this is definitely… 00:30:52.000 --> 00:30:54.000 something we would use. 00:30:54.000 --> 00:30:57.000 Um… 00:30:57.000 --> 00:31:07.000 I would second that, too. We have a couple library institutions that have multiple branches in the same tenant, and still help them say, here is the reserves just for that one particular branch library. 00:31:07.000 --> 00:31:10.000 Yep. Right now, you can filter it by… 00:31:10.000 --> 00:31:15.000 location of the course, but it's not… 00:31:15.000 --> 00:31:19.000 actually separate. 00:31:19.000 --> 00:31:24.000 This probably, um… 00:31:24.000 --> 00:31:25.000 Yeah. 00:31:25.000 --> 00:31:27.000 This will need further refinement, though, because it's just a description of the problem, not… 00:31:27.000 --> 00:31:35.000 really a solution. 00:31:35.000 --> 00:31:40.000 This was added by an insane person. Ours is assigned to a sane person, so you can just get rid of it. 00:31:40.000 --> 00:31:44.000 This refuse check-in if item is not at primary service point. 00:31:44.000 --> 00:31:47.000 Refuse check-in. 00:31:47.000 --> 00:31:51.000 Yeah. 00:31:51.000 --> 00:31:54.000 This… I think one of the, um, there is a… 00:31:54.000 --> 00:31:56.000 I think down there is, like… 00:31:56.000 --> 00:32:01.000 Um, one of the things I could see this being used for is things like equipment. 00:32:01.000 --> 00:32:03.000 are reserve items. 00:32:03.000 --> 00:32:04.000 Where you don't want… 00:32:04.000 --> 00:32:06.000 Yeah. So, like, don't check it in. 00:32:06.000 --> 00:32:07.000 Yes, yes, exactly. 00:32:07.000 --> 00:32:12.000 Don't allow check-in if it's not at its home location. 00:32:12.000 --> 00:32:13.000 Correct. 00:32:13.000 --> 00:32:20.000 It's… 00:32:20.000 --> 00:32:21.000 Right. 00:32:21.000 --> 00:32:27.000 Yeah, we do that for both equipment and reserves. They must be returned at the correct location, though we still check them in, we just tell them there will be fines until it arrives to… the right location. 00:32:27.000 --> 00:32:28.000 Yeah. 00:32:28.000 --> 00:32:36.000 But it could be an indicator for staff to notice that it's wrong location. 00:32:36.000 --> 00:32:40.000 I think one of the things we'd have to do with this, too, is have an override as well. 00:32:40.000 --> 00:32:41.000 Yeah. 00:32:41.000 --> 00:32:42.000 writable. 00:32:42.000 --> 00:32:43.000 Yes. 00:32:43.000 --> 00:32:44.000 Mm-hmm. Yes. 00:32:44.000 --> 00:32:54.000 So this came from the German libraries. Originally, it came from my library, but because we didn't want to transport all. 00:32:54.000 --> 00:33:05.000 Stuff between, uh, multiple buildings and campuses. We don't need this anymore, but I know of German libraries who still want this, and maybe they will get developed. 00:33:05.000 --> 00:33:06.000 U.S. Libraries uniformly did not want this feature. That's funny. 00:33:06.000 --> 00:33:11.000 If they can get funding. Yes. 00:33:11.000 --> 00:33:16.000 But did not object to its development. 00:33:16.000 --> 00:33:19.000 Well, so if folks would… 00:33:19.000 --> 00:33:22.000 still like it, that we should leave it on there. 00:33:22.000 --> 00:33:23.000 Oh, no! Robert, like… 00:33:23.000 --> 00:33:26.000 Yes. 00:33:26.000 --> 00:33:32.000 I guess this is not as uniform across U.S. libraries as once thought. 00:33:32.000 --> 00:33:36.000 Alright, so let's… this one definitely would need more… 00:33:36.000 --> 00:33:38.000 refinement, because we… it's not really well written. 00:33:38.000 --> 00:33:41.000 I mean, not fully fleshed out here. 00:33:41.000 --> 00:33:43.000 So… 00:33:43.000 --> 00:33:45.000 we want to capture it, we would want to capture it. 00:33:45.000 --> 00:33:47.000 overrides, and… 00:33:47.000 --> 00:33:48.000 all the other fun stuff. 00:33:48.000 --> 00:33:50.000 Yeah, you'd have to know all the different… yeah. 00:33:50.000 --> 00:33:55.000 Alright, further refinement for that one. 00:33:55.000 --> 00:33:58.000 Alright, option to print all hold slips at the end 00:33:58.000 --> 00:34:02.000 of a check-in session. 00:34:02.000 --> 00:34:03.000 I don't like this. 00:34:03.000 --> 00:34:07.000 So instead of… so batching them for the end? 00:34:07.000 --> 00:34:08.000 Okay. 00:34:08.000 --> 00:34:14.000 Yeah… I… I don't like… I can see this being useful. I personally don't like this. 00:34:14.000 --> 00:34:18.000 I think it would cause more of a mess at check-in than… 00:34:18.000 --> 00:34:25.000 having them print individually. I can see it being a time saver, and I know that's something when we first went live was a 00:34:25.000 --> 00:34:31.000 big hassle with our major library, Olin, because they check in so many items at once. 00:34:31.000 --> 00:34:39.000 Um, the number of times they have to click on, okay, yes, print, okay, yes, print, they were slowing things down. 00:34:39.000 --> 00:34:47.000 But, at the same extent, I'm, like, looking at this and, like, you're checking 200 items, and then you… the system prints out 30 slips, you have to go through and figure out which slips. 00:34:47.000 --> 00:34:49.000 How are you going to connect them all? 00:34:49.000 --> 00:34:56.000 Yeah, exactly, exactly. That's… that's… that's the part I don't like about it. 00:34:56.000 --> 00:35:11.000 That's what I was wondering about, too. A lot of our bigger libraries had to batch check-ins. They have a system set up wherever they print the slips out and put them in the book each time, because otherwise you have a couple of carts of books have to go back again, find the book, find the right slip for it. 00:35:11.000 --> 00:35:14.000 And that would slow things down, actually, rather than save time. 00:35:14.000 --> 00:35:17.000 Yeah, I would agree. 00:35:17.000 --> 00:35:20.000 Um… 00:35:20.000 --> 00:35:22.000 Anyone interested in 00:35:22.000 --> 00:35:24.000 holding on to this one. 00:35:24.000 --> 00:35:30.000 Or see a use case where this could be helpful. 00:35:30.000 --> 00:35:39.000 I'd rather have, uh, somehow have direct print capabilities in folio, but I know that's also difficult, too. 00:35:39.000 --> 00:35:47.000 All right. Intend to close, Cornelia, we got one. 00:35:47.000 --> 00:35:49.000 All right, another courses one… 00:35:49.000 --> 00:35:53.000 Export courses info on the courses pane. 00:35:53.000 --> 00:35:59.000 So, being able to export… 00:35:59.000 --> 00:36:02.000 Oh. 00:36:02.000 --> 00:36:04.000 Export the list. 00:36:04.000 --> 00:36:08.000 of what's on reserve for a particular course. 00:36:08.000 --> 00:36:15.000 This should be super easy to do, because… It's happening in other places. 00:36:15.000 --> 00:36:22.000 And it's convenient to have that list in excel. But. 00:36:22.000 --> 00:36:23.000 Okay. Um, do we… 00:36:23.000 --> 00:36:24.000 Yeah, it's still not possible. 00:36:24.000 --> 00:36:27.000 This one may need more… 00:36:27.000 --> 00:36:36.000 I don't know, do we… does it look like it needs more refinement or not? I'm not sure how much has been done on it. It just has that one… 00:36:36.000 --> 00:36:37.000 Sure. 00:36:37.000 --> 00:36:40.000 Yeah, this is an Aaron. It looks like she originally wrote it, so there's a lot of information here, but… 00:36:40.000 --> 00:36:41.000 Yep. 00:36:41.000 --> 00:36:46.000 it's also older, so I would say do more refinement, just to ensure that it is how you want it. 00:36:46.000 --> 00:36:50.000 Yeah. 00:36:50.000 --> 00:36:57.000 All right. Uh, refinement for that one… 00:36:57.000 --> 00:37:00.000 And this looks like an addition of what the other one was. 00:37:00.000 --> 00:37:04.000 on the reserves paid. 00:37:04.000 --> 00:37:08.000 Okay, so this is when you're doing search results and you get either a list of courses or a list of… 00:37:08.000 --> 00:37:11.000 reserves that are attached to courses. 00:37:11.000 --> 00:37:15.000 So these, I would say both of these are further refinedment. 00:37:15.000 --> 00:37:17.000 Yeah. 00:37:17.000 --> 00:37:20.000 I think we did look at them at both of those tickets a year ago. 00:37:20.000 --> 00:37:31.000 Yep. Yeah, I think you're on… your tag is here. 00:37:31.000 --> 00:37:32.000 Yeah. 00:37:32.000 --> 00:37:33.000 Yeah, but we kind of we spend a bit more time on these 2 tickets like screenshots. 00:37:33.000 --> 00:37:36.000 Yeah. Yeah, the screenshots are good, that… 00:37:36.000 --> 00:37:39.000 It shows, sort of, like, where it would be. 00:37:39.000 --> 00:37:44.000 That makes sense. 00:37:44.000 --> 00:37:50.000 Alright. Add filter to courses pane to select search results by whether they are 00:37:50.000 --> 00:37:51.000 cross-listed. Oh, great. 00:37:51.000 --> 00:37:53.000 Yeah, so this one… 00:37:53.000 --> 00:37:58.000 Um, let's see… 00:37:58.000 --> 00:38:05.000 It might need more… I don't know. 00:38:05.000 --> 00:38:06.000 Oh, does it? Okay. 00:38:06.000 --> 00:38:08.000 Oh, it says in the description, needs additional requirements discussion. 00:38:08.000 --> 00:38:11.000 When the course group is able to resume and convener. 00:38:11.000 --> 00:38:14.000 Okay, well, there you go. 00:38:14.000 --> 00:38:15.000 All right. Further refinement! 00:38:15.000 --> 00:38:24.000 Well… 00:38:24.000 --> 00:38:34.000 When creating a cross-listed course, copy the course name and description. Oh, right, you have to write this every time, it's very annoying. 00:38:34.000 --> 00:38:38.000 When it's clear it's a cross list, it should just copy it over. 00:38:38.000 --> 00:38:39.000 That's odd. 00:38:39.000 --> 00:38:41.000 This probably doesn't need… 00:38:41.000 --> 00:38:48.000 Seems pretty straightforward. Oh, it's got a proposed solution and story already. 00:38:48.000 --> 00:38:51.000 This one's ready, I think. 00:38:51.000 --> 00:38:55.000 I don't use courses in Voyager when you process a course, you just literally added the… 00:38:55.000 --> 00:39:03.000 instructor, of course, not the department and the course number, and I was at. It was linked to the other course. 00:39:03.000 --> 00:39:05.000 Nice. 00:39:05.000 --> 00:39:12.000 Yeah, that makes sense. I mean, it should be carrying over. It really is just one course. 00:39:12.000 --> 00:39:13.000 Mm-hmm. 00:39:13.000 --> 00:39:20.000 It doesn't… it's weird in folio, because it doesn't look like one course, even though it is. 00:39:20.000 --> 00:39:21.000 Alright, tags for courses. 00:39:21.000 --> 00:39:24.000 rewrite the courses up? 00:39:24.000 --> 00:39:25.000 What? 00:39:25.000 --> 00:39:26.000 Completely rewrite the courses up. 00:39:26.000 --> 00:39:32.000 You stay in your fee fine lane. 00:39:32.000 --> 00:39:36.000 Alright, uh, tags for courses. 00:39:36.000 --> 00:39:40.000 This seems pretty straightforward. 00:39:40.000 --> 00:39:45.000 I don't know that it needs more refinement. 00:39:45.000 --> 00:39:49.000 The only thing it is mentioning is, uh, the discovery layer. 00:39:49.000 --> 00:39:53.000 I'm not sure if tags are exposed to discovery later now, so that would be new work. 00:39:53.000 --> 00:39:56.000 don't… 00:39:56.000 --> 00:39:59.000 Where does it say that, Tom? 00:39:59.000 --> 00:40:00.000 Oh, here? Okay. 00:40:00.000 --> 00:40:06.000 Uh, under use cases, yeah. 00:40:06.000 --> 00:40:11.000 Well, it says for extracting data, well… 00:40:11.000 --> 00:40:18.000 Yeah, that's not exactly a use case that could be. 00:40:18.000 --> 00:40:19.000 taken advantage of. 00:40:19.000 --> 00:40:22.000 I'm happy to turn her… yeah, I'm not even sure how a user… 00:40:22.000 --> 00:40:25.000 interaction be? 00:40:25.000 --> 00:40:28.000 how that would work, but yeah. 00:40:28.000 --> 00:40:30.000 Interesting idea, but I don't know if it's practical. 00:40:30.000 --> 00:40:33.000 Yeah. 00:40:33.000 --> 00:40:36.000 Olga, do you have any recollection about the… 00:40:36.000 --> 00:40:40.000 use cases for this? 00:40:40.000 --> 00:40:48.000 No, I don't think there was much interest in that ticket, though, again, I could be wrong. 00:40:48.000 --> 00:40:49.000 Yeah. 00:40:49.000 --> 00:40:52.000 But I don't think so. 00:40:52.000 --> 00:40:55.000 Well, it's… do we want to… 00:40:55.000 --> 00:40:59.000 keep it, or do we think it's something we could… 00:40:59.000 --> 00:41:03.000 Because we've got two of these, the next one is reserve items. 00:41:03.000 --> 00:41:06.000 So the… one of the use cases for that one… 00:41:06.000 --> 00:41:10.000 I'm curious. 00:41:10.000 --> 00:41:13.000 Oh, so more… these are more workflow. 00:41:13.000 --> 00:41:15.000 related. 00:41:15.000 --> 00:41:27.000 This one in particular feels to me like trying to fit a square peg into a round hole sort of thing. It's like… 00:41:27.000 --> 00:41:28.000 Right. 00:41:28.000 --> 00:41:30.000 We can't have queues like we do in Aries or other systems, so we're going to use tags to… 00:41:30.000 --> 00:41:33.000 gift statuses and track workflows. 00:41:33.000 --> 00:41:37.000 Right, this seems like an inelegant… 00:41:37.000 --> 00:41:43.000 way of getting around that, whereas you could use something like the dashboard, if that were… 00:41:43.000 --> 00:41:47.000 made available to track certain things in particular. 00:41:47.000 --> 00:41:52.000 Um, statuses or whatever. 00:41:52.000 --> 00:41:55.000 That might be a better… 00:41:55.000 --> 00:41:56.000 implementation of this. 00:41:56.000 --> 00:42:02.000 It does feel like a bit of a kludge. 00:42:02.000 --> 00:42:03.000 This is also tube. 00:42:03.000 --> 00:42:09.000 Um… I'm curious, what do other people think about this? 00:42:09.000 --> 00:42:28.000 I have kind of mixed feelings about it. I mean, it's one of those things, again, I can see a use for it, but how important would it be, um, you know, if you're searching in a catalog and not part of the course, these tags matching it, but you can't actually look at the records. Um, it might be useful for some institutions that have really huge course reserves. 00:42:28.000 --> 00:42:38.000 or they have a lot of different materials required searching, but as reservists have not been used that much in the past few years. I'm not sure how useful it'll continue to be. 00:42:38.000 --> 00:42:41.000 I think, honestly, too, is, um… 00:42:41.000 --> 00:42:46.000 the, um, adding process to items… to the item. 00:42:46.000 --> 00:42:51.000 that would probably take care of what this is trying… the need that this is trying to cover, because… 00:42:51.000 --> 00:42:55.000 If you can add a process to an item, 00:42:55.000 --> 00:43:01.000 You could add a process that needs to be reviewed by a manager that 00:43:01.000 --> 00:43:06.000 is linked directly to the item instead of being a tag on the item in the courses. 00:43:06.000 --> 00:43:10.000 list. 00:43:10.000 --> 00:43:15.000 Yeah, I think I would agree with that. I think this is a… 00:43:15.000 --> 00:43:19.000 like, for what we knew at the time, whenever this was, 2021, 00:43:19.000 --> 00:43:21.000 Um, 00:43:21.000 --> 00:43:24.000 Tags were sort of the only… 00:43:24.000 --> 00:43:29.000 thing, but if this is the only use case, is to work it around, to… 00:43:29.000 --> 00:43:35.000 pretend to be a workflow. My inclination is to close this one. 00:43:35.000 --> 00:43:37.000 It sounds like they really want a status. 00:43:37.000 --> 00:43:45.000 Um, you know, and this is a workaround, and I can imagine the mess of how many tags you kind of remove people. 00:43:45.000 --> 00:43:49.000 Don't forget to remove a tag, and you're… it's gonna get… 00:43:49.000 --> 00:43:51.000 messy… I think. 00:43:51.000 --> 00:43:52.000 Yeah. That's… 00:43:52.000 --> 00:43:59.000 Yeah. Right, and the Tags app, remember that the Tags app, like the Notes app, is across all apps. 00:43:59.000 --> 00:44:03.000 So you're going to have tags that might mean one thing, 00:44:03.000 --> 00:44:05.000 Yeah, I… 00:44:05.000 --> 00:44:08.000 I'm a little worried about keeping this in here as a… 00:44:08.000 --> 00:44:15.000 Exactly, and that's something that actually I'd like to see with the updates to the Tags app and the Notes app. 00:44:15.000 --> 00:44:17.000 that you can scope the 00:44:17.000 --> 00:44:23.000 types are tags to specific applications, because right now, when you add a tag, it's throughout the entire system. 00:44:23.000 --> 00:44:27.000 So, if… yeah, you could have a patron tag, 00:44:27.000 --> 00:44:31.000 that says one thing that someone could accidentally add it to an item. 00:44:31.000 --> 00:44:36.000 Right. And it might have a totally different meaning in that context, right? 00:44:36.000 --> 00:44:41.000 Exactly, exactly. 00:44:41.000 --> 00:44:44.000 Um, Olga, as the… 00:44:44.000 --> 00:44:47.000 former co-chair or chair of the… 00:44:47.000 --> 00:44:51.000 courses subgroup, what is your feeling based on what you were… 00:44:51.000 --> 00:44:55.000 Hearing in that group. 00:44:55.000 --> 00:45:10.000 I don't think… It's very it was very popular, or… Anyone even asked for it. 00:45:10.000 --> 00:45:11.000 Yeah. 00:45:11.000 --> 00:45:13.000 I… yeah, I don't think tax is… Useful. Thanks, I would be useful in this case. 00:45:13.000 --> 00:45:16.000 Okay, do you mind, um… 00:45:16.000 --> 00:45:24.000 Olga, if I have Cordia mark these as close, do you mind taking a quick look at your spreadsheet? 00:45:24.000 --> 00:45:33.000 that you linked in the comments of these, and just make sure that we didn't miss something. 00:45:33.000 --> 00:45:34.000 Yeah, there is down here. I was… 00:45:34.000 --> 00:45:35.000 Um, isn't there a link in my note? 00:45:35.000 --> 00:45:40.000 this link down here where it says this is where the rankings are. 00:45:40.000 --> 00:45:43.000 Um, do you mind taking a look at it for these two 00:45:43.000 --> 00:45:48.000 ticket, these two, um, tag tickets, one for courses and one for… 00:45:48.000 --> 00:45:54.000 reserve items. We'll mark it as intended to close, but if some… for some reason you see something in your 00:45:54.000 --> 00:45:57.000 your page that says… 00:45:57.000 --> 00:45:59.000 that somebody really wanted it. 00:45:59.000 --> 00:46:04.000 You can ask us to change it back. Does that sound okay? 00:46:04.000 --> 00:46:05.000 Awesome. Thank you. 00:46:05.000 --> 00:46:10.000 Sure. 00:46:10.000 --> 00:46:14.000 Alright, so Cornelia, for 06 and 07. 00:46:14.000 --> 00:46:18.000 Those are intended to close. 00:46:18.000 --> 00:46:34.000 Alright, use notice tokens in subject lines for patron notices. 00:46:34.000 --> 00:46:39.000 Um, I think this is something that people wanted, but, um… 00:46:39.000 --> 00:46:40.000 Yeah. 00:46:40.000 --> 00:46:43.000 The question is, is it… 00:46:43.000 --> 00:46:52.000 Um, yeah, it doesn't… is it… does it have enough detail to actually do it? 00:46:52.000 --> 00:46:55.000 I would say let's put it in refinement again, just because of the age. 00:46:55.000 --> 00:46:57.000 Yeah. 00:46:57.000 --> 00:47:02.000 That's probably true of most… a lot of these, unless it's very simple. 00:47:02.000 --> 00:47:07.000 Alright, further refinement for that one… 00:47:07.000 --> 00:47:10.000 Optimistic locking for Courses app? 00:47:10.000 --> 00:47:14.000 Boy, as one sentence. 00:47:14.000 --> 00:47:15.000 Um… 00:47:15.000 --> 00:47:18.000 Yeah, oddly enough, though, that means a lot. 00:47:18.000 --> 00:47:26.000 No, it does. So, I mean, that… all that means is just that when one person is editing it, it can't be edited by someone else, right? 00:47:26.000 --> 00:47:29.000 Yeah. 00:47:29.000 --> 00:47:32.000 So I assume that is… 00:47:32.000 --> 00:47:35.000 I mean… 00:47:35.000 --> 00:47:41.000 But does it need more refinement? It's literally one sentence. 00:47:41.000 --> 00:47:42.000 I would say he had more refinement, um… 00:47:42.000 --> 00:47:44.000 Okay. 00:47:44.000 --> 00:47:49.000 There is… because you… you probably should do lock… 00:47:49.000 --> 00:48:01.000 resolution. 00:48:01.000 --> 00:48:02.000 Yeah. 00:48:02.000 --> 00:48:06.000 So if two people open up the app at the same time, and they're working on the same course at the same time, one person saves it, how is the error handled? Is it possible to see the changes and overwrite the current changes? 00:48:06.000 --> 00:48:07.000 Except, Rob. 00:48:07.000 --> 00:48:10.000 Right. Gotcha. 00:48:10.000 --> 00:48:11.000 Also, what are… 00:48:11.000 --> 00:48:15.000 Where do you… do you know where Optimistic Locking is enabled now? 00:48:15.000 --> 00:48:17.000 Inventory has optimistic blocking. 00:48:17.000 --> 00:48:20.000 Okay. 00:48:20.000 --> 00:48:22.000 I believe that's… 00:48:22.000 --> 00:48:27.000 it. I don't think there's any… it might be being used in… 00:48:27.000 --> 00:48:30.000 less… I know there was a big push to put it pretty much everywhere. 00:48:30.000 --> 00:48:31.000 Yeah. 00:48:31.000 --> 00:48:39.000 Uh, but then as they were expanding out, they were running into workflow issues in some parts of the system. 00:48:39.000 --> 00:48:40.000 Yeah. 00:48:40.000 --> 00:48:41.000 Uh, because it can be a tricky little monster. Um, and even with this one, it's like, 00:48:41.000 --> 00:48:47.000 I think even saying where you wanted to have optimistic locking, i.e. 00:48:47.000 --> 00:49:00.000 I don't think we want to lock people adding items to a course, so if there's 3 people working in the system on the same course, and they're both adding items, 00:49:00.000 --> 00:49:01.000 Right. 00:49:01.000 --> 00:49:04.000 we don't want to block one person from adding items because another person is, but we want to block someone changing the course header information, 00:49:04.000 --> 00:49:05.000 Right. 00:49:05.000 --> 00:49:06.000 what someone else says. 00:49:06.000 --> 00:49:10.000 Right, if they're both editing the course itself. 00:49:10.000 --> 00:49:11.000 Exactly, yeah, yeah. 00:49:11.000 --> 00:49:13.000 Yeah. That makes sense. 00:49:13.000 --> 00:49:17.000 Alright. 00:49:17.000 --> 00:49:25.000 Allow configuration of items waiting pickup modal in checkout app by service point. 00:49:25.000 --> 00:49:26.000 Yeah, people want to get rid of it. 00:49:26.000 --> 00:49:27.000 So, uh… 00:49:27.000 --> 00:49:29.000 I want to get Reddit. 00:49:29.000 --> 00:49:31.000 rid of it. 00:49:31.000 --> 00:49:33.000 Why? 00:49:33.000 --> 00:49:34.000 Um… 00:49:34.000 --> 00:49:38.000 Oh, you mean the one when… when you look up a user and it says their items? 00:49:38.000 --> 00:49:39.000 awaiting pickup, I see. 00:49:39.000 --> 00:49:42.000 Yeah. 00:49:42.000 --> 00:49:46.000 Yes, that… 00:49:46.000 --> 00:49:52.000 This seems like a desired feature, because how many times have you checked out the thing, and you're like, 00:49:52.000 --> 00:49:58.000 It doesn't check out, because you just cleared the modal. 00:49:58.000 --> 00:50:03.000 Um… does it need further refinement? 00:50:03.000 --> 00:50:08.000 the question. 00:50:08.000 --> 00:50:09.000 Yeah. 00:50:09.000 --> 00:50:11.000 I would say it's probably… it's a fairly straightforward request. There seems to be a lot of detail here, so… 00:50:11.000 --> 00:50:13.000 Yeah, there's already stuff in here. 00:50:13.000 --> 00:50:15.000 Alright, yay! 00:50:15.000 --> 00:50:22.000 Ready for dev, although that one is not assigned to anyone. 00:50:22.000 --> 00:50:24.000 So far. 00:50:24.000 --> 00:50:25.000 That would be, uh, Vega. 00:50:25.000 --> 00:50:28.000 Well, is… are these… 00:50:28.000 --> 00:50:32.000 These are assigned, is that what that is? Sorry. 00:50:32.000 --> 00:50:35.000 Yeah, Vega, you say? 00:50:35.000 --> 00:50:37.000 Yeah, Vega does check out and check out. 00:50:37.000 --> 00:50:38.000 ModCirc store. 00:50:38.000 --> 00:50:41.000 Okay. 00:50:41.000 --> 00:50:44.000 Alright. 00:50:44.000 --> 00:50:48.000 So, should we assign it? 00:50:48.000 --> 00:50:52.000 Sure, you can throw it over. 00:50:52.000 --> 00:50:53.000 Yeah, exactly. 00:50:53.000 --> 00:50:56.000 Oh yeah, oh yeah, yeah, sure, the stories are… are assigned to Vega already. All right, yeah. 00:50:56.000 --> 00:50:57.000 It'll… and it'll fall off our list, but that's okay. 00:50:57.000 --> 00:51:00.000 Okay, so… 00:51:00.000 --> 00:51:05.000 Because our list is defined as not assigned to Vega or Valeris. 00:51:05.000 --> 00:51:09.000 That's alright, though. 00:51:09.000 --> 00:51:17.000 Uh, in CERC settings, do not allow deletion of loan policies that have already been used in open, closed, or anonymized loans. 00:51:17.000 --> 00:51:19.000 Oi. Okay. 00:51:19.000 --> 00:51:25.000 This would be, uh, Vega as well, and I would say, um… 00:51:25.000 --> 00:51:26.000 Yeah. 00:51:26.000 --> 00:51:30.000 further refinement, and this one probably should be kept, because this can cause issue… well, not really, but… 00:51:30.000 --> 00:51:34.000 why wouldn't you be able to allow deletions of… 00:51:34.000 --> 00:51:38.000 closed loans because of statistics? 00:51:38.000 --> 00:51:39.000 But I don't know why. 00:51:39.000 --> 00:51:54.000 I think so. statistics are maybe following up on lost items, build items that were closed over time. I can see the use of this. I'm just wondering how it's going to detect if it's been used with a loan already. 00:51:54.000 --> 00:52:00.000 from the circulation rules, that these seem really complex to set that up and verify it. 00:52:00.000 --> 00:52:07.000 Nah, as part of the… part of the data that's stored on the loan object is the, uh, different policies at checkout and renewal. 00:52:07.000 --> 00:52:13.000 So, there's, uh, the UUID for the loan policy, the notice policy, 00:52:13.000 --> 00:52:17.000 fine overdue policy and loss policy. 00:52:17.000 --> 00:52:23.000 are all written to a load record, so they would just have to scan all loan records to see if that UID was present on any of them. 00:52:23.000 --> 00:52:29.000 The other option you could do is a soft delete and not a hard delete, i.e., it's suppressed from the UI. 00:52:29.000 --> 00:52:30.000 Right. 00:52:30.000 --> 00:52:37.000 And no one can see it or assign it to anything, but it's still in the database. And to be perfectly honest, I'm more… 00:52:37.000 --> 00:52:41.000 I'm more apt to wanting to do a soft delete. 00:52:41.000 --> 00:52:43.000 and suppress it, then actually a hard delete and remove it from the system. 00:52:43.000 --> 00:52:48.000 Yeah. That makes sense. 00:52:48.000 --> 00:52:49.000 Yeah, well… 00:52:49.000 --> 00:52:54.000 Yeah, I want to soft delete, but I actually… it's for Mobius items. I look at the OpenRS 00:52:54.000 --> 00:53:01.000 loan policies, like the name, to kind of find those items, so we do use them for statistics. 00:53:01.000 --> 00:53:08.000 Okay. It's interesting, though, I guess I don't understand if this is to be… 00:53:08.000 --> 00:53:14.000 to say that you want it… that this is a choice, because otherwise, if it's… all these loan types… 00:53:14.000 --> 00:53:22.000 You would never be able to delete a loan policy, basically, if it had ever been used. But maybe it is an option, like… 00:53:22.000 --> 00:53:23.000 Well, 00:53:23.000 --> 00:53:25.000 it's asking for it to be optional. 00:53:25.000 --> 00:53:29.000 if you look at the situation, um, 00:53:29.000 --> 00:53:34.000 This is… this is an Aaron Duke issue. 00:53:34.000 --> 00:53:37.000 Yeah. 00:53:37.000 --> 00:53:38.000 Nah, that's okay. 00:53:38.000 --> 00:53:44.000 Sorry, I don't mean to be a brat, but it's just like, eh, the doctors are testing and adding loan policies that they're not ever gonna use. We need to be able to delete them. 00:53:44.000 --> 00:53:46.000 Right. 00:53:46.000 --> 00:53:48.000 Uh, yeah, yeah. 00:53:48.000 --> 00:53:51.000 So this one needs more refinement. 00:53:51.000 --> 00:53:59.000 Yeah, or a complete rewrite. 00:53:59.000 --> 00:54:07.000 Robert, I think there's a beacher in here, a ticket in here, about what you're describing. 00:54:07.000 --> 00:54:08.000 Yeah, they're… 00:54:08.000 --> 00:54:14.000 that the checks… I… we've looked at so many tickets. I think there is one that's, like, 00:54:14.000 --> 00:54:20.000 before you delete a loan policy, make sure it's not somewhere in the CERC rules. I think that is… 00:54:20.000 --> 00:54:21.000 Right, right. 00:54:21.000 --> 00:54:22.000 a feature written up already. 00:54:22.000 --> 00:54:26.000 Because if… because if it's assigned to a loan, it's not that big of an… 00:54:26.000 --> 00:54:33.000 issue, because all the data was already set there, it's just kind of a pointer. When you renew it, it's gonna check the CERC rules again, so… 00:54:33.000 --> 00:54:41.000 this shouldn't be a problem, but yeah. But again, that's why I'm a fan of a soft delete, because if there is some weird business logic somewhere, 00:54:41.000 --> 00:54:46.000 the information is still in the database, it's just frozen that no one can view it through the UI. 00:54:46.000 --> 00:54:49.000 Or edit it, yeah, exactly. 00:54:49.000 --> 00:54:50.000 Exactly, yeah. 00:54:50.000 --> 00:54:52.000 That makes sense. 00:54:52.000 --> 00:54:54.000 All right. 00:54:54.000 --> 00:55:01.000 subset of CERCLog data on user… 00:55:01.000 --> 00:55:04.000 This would be interesting, but… 00:55:04.000 --> 00:55:14.000 Boy, they would have to probably redo the SERP log. 00:55:14.000 --> 00:55:20.000 why wouldn't you just link to the CERC log from the user 00:55:20.000 --> 00:55:27.000 barcode. Like, you know, why wouldn't you just filter the CERC log by the user barcode? Wouldn't that give you the same thing? 00:55:27.000 --> 00:55:28.000 Yeah. 00:55:28.000 --> 00:55:29.000 So is this…? 00:55:29.000 --> 00:55:35.000 But this was… this was submitted by Darcy, so it might have came from some of our insanity. 00:55:35.000 --> 00:55:38.000 Do we think it's still needed? 00:55:38.000 --> 00:55:45.000 This is… 00:55:45.000 --> 00:55:46.000 Yeah. 00:55:46.000 --> 00:55:49.000 I wouldn't think so, because you can find it a couple different ways and just another option, a way of doing things, makes things more complex than they need to be. 00:55:49.000 --> 00:56:01.000 Yeah. 00:56:01.000 --> 00:56:04.000 Yeah, you can get this by just going to the… 00:56:04.000 --> 00:56:05.000 Circ log. 00:56:05.000 --> 00:56:06.000 Right. 00:56:06.000 --> 00:56:07.000 and filtering. Yeah. 00:56:07.000 --> 00:56:10.000 Yeah, that's what… that's what it says. It's too much work to go to the circl. 00:56:10.000 --> 00:56:13.000 I mean… 00:56:13.000 --> 00:56:14.000 Yeah, exactly. 00:56:14.000 --> 00:56:15.000 Maybe you could have a link from the user record directly to the, like… 00:56:15.000 --> 00:56:17.000 It… 00:56:17.000 --> 00:56:20.000 You know, it would be just a pre-filtered, 00:56:20.000 --> 00:56:24.000 by barcode, user barcode link, but… 00:56:24.000 --> 00:56:26.000 I don't know. 00:56:26.000 --> 00:56:27.000 Yeah, I would… 00:56:27.000 --> 00:56:29.000 I'm inclined to close this. 00:56:29.000 --> 00:56:30.000 So am I. 00:56:30.000 --> 00:56:33.000 That would be nice. Yeah. 00:56:33.000 --> 00:56:36.000 is a frivolous feature. 00:56:36.000 --> 00:56:40.000 We have plenty of real features. We don't need any frivolous ones. 00:56:40.000 --> 00:56:44.000 Alright. 00:56:44.000 --> 00:56:49.000 Renew item from checkout screen. 00:56:49.000 --> 00:56:54.000 This one, I would say, let's refine this one, because this is a pain in the butt. 00:56:54.000 --> 00:56:56.000 To try to renew from… 00:56:56.000 --> 00:56:58.000 Check out. 00:56:58.000 --> 00:57:04.000 Yeah, and this is something Voyager and a lot of other library management systems, you open up a Patreon account and 00:57:04.000 --> 00:57:12.000 check out an item that they already have checked out, it just renews it. 00:57:12.000 --> 00:57:17.000 So that's interesting. I have an additional ticket in my list. 00:57:17.000 --> 00:57:20.000 Oh, you do? Oh, on your spreadsheet? 00:57:20.000 --> 00:57:21.000 What… 00:57:21.000 --> 00:57:25.000 Yes. No, on on the filter I see on on Jira. 00:57:25.000 --> 00:57:26.000 Oh, I have not reload… I have not reloaded this recently, Cornelia, so it's possible… 00:57:26.000 --> 00:57:30.000 That's weird. Oh. 00:57:30.000 --> 00:57:35.000 Like, my window has been open for a long time, so what do you have? 00:57:35.000 --> 00:57:36.000 What's the number? 00:57:36.000 --> 00:57:40.000 Oh, okay. 3212. 00:57:40.000 --> 00:57:42.000 Alright, let me see if I… 00:57:42.000 --> 00:57:48.000 go back to… thank goodness, alright. 00:57:48.000 --> 00:57:49.000 It's also on the spreadsheet, so… Yeah. 00:57:49.000 --> 00:57:53.000 Oh, it is? Well, that's interesting. 00:57:53.000 --> 00:58:02.000 Oh, right, I forgot these… 00:58:02.000 --> 00:58:08.000 Sorry, I know I'm going fast here. 3212, here it is. 00:58:08.000 --> 00:58:13.000 Ability for folio to recognize a double barcode scan as an alternative 00:58:13.000 --> 00:58:19.000 Pressing close when a pop-up appears. 00:58:19.000 --> 00:58:30.000 I see I have a bad feeling about that one. 00:58:30.000 --> 00:58:36.000 Yeah, I said kill it. This is definitely from our insanity. It was submitted by my boss. 00:58:36.000 --> 00:58:38.000 Let's say we close it. 00:58:38.000 --> 00:58:44.000 So if something gets double scanned… okay, yeah, this seems like it's a… 00:58:44.000 --> 00:58:48.000 training issue, right? 00:58:48.000 --> 00:58:53.000 Well, it wasn't really a training issue, it was a barcode scanner issue. 00:58:53.000 --> 00:58:54.000 Oh, 00:58:54.000 --> 00:58:58.000 There was one barcode. Yeah, we had a batch of barcode scanners at one of the libraries. 00:58:58.000 --> 00:59:05.000 That was one of the smaller libraries that you scanned a barcode, and they were so sensitive that they would go beep, beep, 00:59:05.000 --> 00:59:08.000 And literally scan the barcode twice, and dump it into Folio. 00:59:08.000 --> 00:59:17.000 I see. 00:59:17.000 --> 00:59:18.000 Okay. 00:59:18.000 --> 00:59:20.000 And… Yeah, yeah, we… since then, we've changed the settings on those barcode scanners, so this is no longer an issue, but yeah, this was… this was a hardware issue. 00:59:20.000 --> 00:59:23.000 Okay. 00:59:23.000 --> 00:59:26.000 Any reason… 00:59:26.000 --> 00:59:32.000 not to close this? 00:59:32.000 --> 00:59:40.000 I don't understand it. Because some of those, like, you can close a modal with escape, that's already there. 00:59:40.000 --> 00:59:41.000 Yeah. 00:59:41.000 --> 00:59:42.000 Yeah. 00:59:42.000 --> 00:59:47.000 So what notes? I don't know what… What do you want? 00:59:47.000 --> 00:59:53.000 All right. Close it. 00:59:53.000 --> 00:59:57.000 Alright, the renew item from checkout screen, we're back to this one. Um… 00:59:57.000 --> 01:00:01.000 So, this is something Voyager could do, right, Tom? 01:00:01.000 --> 01:00:03.000 Yeah. 01:00:03.000 --> 01:00:06.000 So, it needs refinement, it looks like. 01:00:06.000 --> 01:00:13.000 We need to know, like, where it would go, how it would work… 01:00:13.000 --> 01:00:19.000 Or is it just… are you looking for a renewal, or is it only if… 01:00:19.000 --> 01:00:28.000 An item that's already checked out gets scanned again. It becomes renewed. 01:00:28.000 --> 01:00:31.000 That's what ours was, is if you… 01:00:31.000 --> 01:00:36.000 If somebody has something checked out on their account, and you scan it and check out, 01:00:36.000 --> 01:00:37.000 it just automatically renews the item. 01:00:37.000 --> 01:00:46.000 Gotcha. 01:00:46.000 --> 01:00:47.000 Well, there… 01:00:47.000 --> 01:00:48.000 Well, it's if you're in checkout. 01:00:48.000 --> 01:00:49.000 Do you have to check the patron barcode again, or… 01:00:49.000 --> 01:00:50.000 Yeah. Yeah. 01:00:50.000 --> 01:00:51.000 You're already in checkout, and you scan something that's already out to them. 01:00:51.000 --> 01:00:52.000 Which, I don't understand why that would happen in the first place, because why would they be coming to the desk with something they… I guess if they're coming to renew it. 01:00:52.000 --> 01:01:00.000 Yeah. But you… 01:01:00.000 --> 01:01:06.000 Yeah, but you would need to check to scan the patron barcode first, st wouldn't you? 01:01:06.000 --> 01:01:07.000 Yes, yes. And we, we have… 01:01:07.000 --> 01:01:10.000 Yes. It would be a regular checkout. 01:01:10.000 --> 01:01:11.000 Yes, and we did… oh, sorry, go ahead, Courtney. 01:01:11.000 --> 01:01:19.000 So… you just… Yeah, so you can search for the users as well, but yeah, whatever. I don't… I don't get it. 01:01:19.000 --> 01:01:27.000 Well, yeah, you would… it would be like a normal checkout. Like, so if I had… if… and, uh, the scenario I'm thinking of that used to happen all the time… 01:01:27.000 --> 01:01:29.000 Um, the portfolio, is we would… 01:01:29.000 --> 01:01:32.000 of patrons come in with a stack of books, 01:01:32.000 --> 01:01:43.000 And say to our student, I want to renew all these, and they would swipe their ID in checkout, bring up their account, and then just literally recheck the items back out to them, and they would renew them on the spot. 01:01:43.000 --> 01:01:47.000 Instead of having to go into their Patreon account and then renew them from there. 01:01:47.000 --> 01:01:50.000 It's 61 half a dozen, another, um… 01:01:50.000 --> 01:01:57.000 it just was a little bit easier sometimes for the students to do it that way than going into the user account. 01:01:57.000 --> 01:02:01.000 Yeah. 01:02:01.000 --> 01:02:02.000 Cordelia doesn't love it, I can tell. 01:02:02.000 --> 01:02:04.000 Oh, uh… 01:02:04.000 --> 01:02:05.000 And… 01:02:05.000 --> 01:02:13.000 I I wonder why would someone would do this? I mean, just people renew their… renew their loans on their own? 01:02:13.000 --> 01:02:14.000 Oh, yeah, we… 01:02:14.000 --> 01:02:15.000 Most of the time. 01:02:15.000 --> 01:02:24.000 We have lazy patrons. They would rather walk a stack of books to the library and ask us to renew them than log in, because we would even say to them, you know, you can do this online. Yeah, I know, I don't want to. 01:02:24.000 --> 01:02:28.000 I want… I'd rather you do it. I'm like, okay, why? 01:02:28.000 --> 01:02:30.000 And we're also talking about stu… 01:02:30.000 --> 01:02:31.000 Yeah, I said that. 01:02:31.000 --> 01:02:33.000 It would never… Would never happen here. 01:02:33.000 --> 01:02:34.000 Yeah. 01:02:34.000 --> 01:02:35.000 Yeah. You're also talking about students that were on, uh, wheelchairs. 01:02:35.000 --> 01:02:39.000 Crazy. 01:02:39.000 --> 01:02:46.000 that to get a laptop, instead of getting off the chair and walking 5 steps to get a laptop and walk 5 steps back, they would literally 01:02:46.000 --> 01:02:47.000 wheel. 01:02:47.000 --> 01:02:55.000 push themselves off of the desk, roll across the floor, grab a laptop, and push themselves off the laptop cart, and roll back to the desk. 01:02:55.000 --> 01:02:56.000 So… 01:02:56.000 --> 01:02:58.000 Oy. 01:02:58.000 --> 01:03:03.000 Alright, so Tom, is this something your folks still want? 01:03:03.000 --> 01:03:09.000 I would say very low priority, like, it works fine the way it is now. I think it would be useful. 01:03:09.000 --> 01:03:10.000 Yeah. 01:03:10.000 --> 01:03:14.000 But… I think it's also going to be a little bit complicated because of the way 01:03:14.000 --> 01:03:16.000 with folio, some of the blocks it has, so… 01:03:16.000 --> 01:03:18.000 Yeah. 01:03:18.000 --> 01:03:19.000 Yeah. 01:03:19.000 --> 01:03:21.000 I think it would need further refinement. 01:03:21.000 --> 01:03:24.000 In any case, about how this would work. 01:03:24.000 --> 01:03:28.000 Yeah, and Katie, are you saying close this one, or was it the other one? 01:03:28.000 --> 01:03:30.000 Oh, she was talking about a different one. 01:03:30.000 --> 01:03:31.000 Okay, sorry. 01:03:31.000 --> 01:03:33.000 spur of the back. Yeah. 01:03:33.000 --> 01:03:38.000 Alright, that is time, so we will stop there. 01:03:38.000 --> 01:03:42.000 I will add $3,400 as our next one to talk about next time. 01:03:42.000 --> 01:03:48.000 And that next time will probably be 3 weeks, cause… 01:03:48.000 --> 01:03:51.000 I think we have a calendar calming. 01:03:51.000 --> 01:03:58.000 in the middle of that, um, the last end of March, beginning of April. 01:03:58.000 --> 01:04:04.000 So, hopefully we'll see some of you on Monday to talk about prioritization with Martina. 01:04:04.000 --> 01:04:07.000 And, um, if we have time, look at our… 01:04:07.000 --> 01:04:09.000 description. 01:04:09.000 --> 01:04:16.000 Anything else before we go? 01:04:16.000 --> 01:04:20.000 I will be off in 3 weeks, so someone else has to fill in the spreadsheet. 01:04:20.000 --> 01:04:24.000 Okay. Appreciate that. Heads up. 01:04:24.000 --> 01:04:36.000 Thank you so much, Cornelia, for doing the note-taking on all of these decisions, and thanks, everyone, for participating. We'll see you all on Monday. 01:04:36.000 --> 01:04:37.000 Take care of them. 01:04:37.000 --> 01:04:38.000 Okay, have a good day, everyone. Okay. 01:04:38.000 --> 01:04:39.000 Thank you. I will try. Thank you. 01:04:39.000 --> 01:04:43.000 I will. Bye-bye. 01:04:43.000 --> 01:04:44.000 It's virus, exactly. That sounds much worse. 01:04:44.000 --> 01:04:54.000 And get better, Susan. Take care, have a lot of rest, because it's not just a cold, it's a virus. So… 01:04:54.000 --> 01:05:14.000 Okay.