WEBVTT 00:06:22.000 --> 00:06:25.000 Hello! 00:06:25.000 --> 00:06:27.000 Someone actually rang my doorbell, and I was like, 00:06:27.000 --> 00:06:34.000 Like, what's going on? I live in an apartment, so that doesn't happen very often. I was very excited. 00:06:34.000 --> 00:06:36.000 The little things in life. 00:06:36.000 --> 00:06:50.000 Um, alright, let me get screen sharing set up here. 00:06:50.000 --> 00:06:53.000 Sweet. Alright. 00:06:53.000 --> 00:06:57.000 And do we have Joe? 00:06:57.000 --> 00:07:03.000 I do have to. 00:07:03.000 --> 00:07:06.000 Thank you, uh, disembodied voice of Joe. 00:07:06.000 --> 00:07:09.000 Okay, uh… 00:07:09.000 --> 00:07:16.000 Looks like people are piling in. Hopefully, I did not, again, send people to the wrong Zoom link, but uh, I guess we'll find out. 00:07:16.000 --> 00:07:18.000 on Slack, if I did. Um… 00:07:18.000 --> 00:07:27.000 Alright, uh, so, uh, to get us started off, uh, we have, um, just a little bit of housekeeping to take care of. Um, the first is upcoming sessions. 00:07:27.000 --> 00:07:31.000 We do not have anything scheduled for this coming Monday. 00:07:31.000 --> 00:07:36.000 I will check one more time on Slack if there are any topics, or feel free to shout it out. 00:07:36.000 --> 00:07:42.000 Um, but if there are no topics, I will go ahead and cancel that, the meeting on, uh, Wednesday, 00:07:42.000 --> 00:07:44.000 Uh, April 1st. 00:07:44.000 --> 00:07:49.000 is going to be canceled for calendar calming. I think that's the week of Easter, um, which might be 00:07:49.000 --> 00:07:52.000 Boy, that's a little bit different than normal? 00:07:52.000 --> 00:07:58.000 Um, so let me know if you have any topics for these, otherwise we'll go ahead and cancel. 00:07:58.000 --> 00:08:00.000 The next thing, um… 00:08:00.000 --> 00:08:05.000 We are, of course, still in search of a new co-convener. I know that Laura is very interested in being 00:08:05.000 --> 00:08:10.000 potentially a co-convener, uh, but we need at least two to make it a co, of course. 00:08:10.000 --> 00:08:14.000 Um, so we'll keep asking, um, if there's anyone who would like to step up. 00:08:14.000 --> 00:08:21.000 Um, I will, of course, stick around, uh, for March and April, and then we'll start figuring out if we have an actual problem on our hands. 00:08:21.000 --> 00:08:28.000 And then the last thing that I wanted to, uh, ask is I created a… 00:08:28.000 --> 00:08:32.000 draft of a cross-app stay working session. 00:08:32.000 --> 00:08:37.000 Um, but we need to find someone who will actually 00:08:37.000 --> 00:08:44.000 probably be at WolfCon, or at least virtually at WolfCon, to submit this, um, because I will be neither, and I've been told it's… 00:08:44.000 --> 00:08:49.000 challenging to change, uh, who the speaker is, like, the main speaker. 00:08:49.000 --> 00:08:54.000 Um, so if you'd like to volunteer, uh, let me know, and I'll post again on Slack. I think I already posted this one. 00:08:54.000 --> 00:09:04.000 That's all the housekeeping I have. Did anyone else have any other announcements they wanted to make? 00:09:04.000 --> 00:09:11.000 Okay, sounds good. Um, alright, so that is you, Joe. Did you want to share your screen, or do you want me to just… 00:09:11.000 --> 00:09:12.000 Keep sharing. 00:09:12.000 --> 00:09:13.000 No, I'm not here. 00:09:13.000 --> 00:09:17.000 It doesn't matter, because really all I've got is the page. 00:09:17.000 --> 00:09:18.000 I'll just pull it up then. 00:09:18.000 --> 00:09:22.000 Oh. Yeah. 00:09:22.000 --> 00:09:27.000 Um, but yeah, so this actually originated with… 00:09:27.000 --> 00:09:30.000 Uh, was it Zach Burke? 00:09:30.000 --> 00:09:35.000 The person responsible for the Stripes team? 00:09:35.000 --> 00:09:39.000 raised this with, uh, with me. 00:09:39.000 --> 00:09:49.000 Um, basically the court issue is that stuff that was developed very early on for acquisitions that was identified as an acquisitions requirement. 00:09:49.000 --> 00:09:53.000 um… behaves differently than… 00:09:53.000 --> 00:09:58.000 what is coded in Stripes as the default behavior. 00:09:58.000 --> 00:10:00.000 And… 00:10:00.000 --> 00:10:07.000 Behaviors should be in stripes wherever possible, because we want Folio to behave consistently. 00:10:07.000 --> 00:10:10.000 So, the issue that we're facing 00:10:10.000 --> 00:10:13.000 is, um… 00:10:13.000 --> 00:10:16.000 we've got business requirements. 00:10:16.000 --> 00:10:20.000 that exist in acquisitions, and this specifically pertains to… 00:10:20.000 --> 00:10:23.000 Um… 00:10:23.000 --> 00:10:26.000 facets and filters, like, pre-selected filters. 00:10:26.000 --> 00:10:30.000 in given, uh, applications. 00:10:30.000 --> 00:10:36.000 So, I believe the stripes default is when you enter an application, nothing is selected. 00:10:36.000 --> 00:10:38.000 But in acquisitions. 00:10:38.000 --> 00:10:41.000 Uh, the acquisitions module remembers 00:10:41.000 --> 00:10:43.000 what was last selected. 00:10:43.000 --> 00:10:47.000 And so, um… 00:10:47.000 --> 00:10:53.000 your pre-selected filters will carry on from session to session. 00:10:53.000 --> 00:11:00.000 The problem with that is if a user copies and pastes a URL, 00:11:00.000 --> 00:11:03.000 It's going to behave differently. 00:11:03.000 --> 00:11:06.000 Um, so this is where we… 00:11:06.000 --> 00:11:09.000 Um, I said, you know, 00:11:09.000 --> 00:11:15.000 the acquisition SIG, I think, is generally happy with the behavior. 00:11:15.000 --> 00:11:21.000 Um, but it's inconsistent with folio at large, so I wanted to come to… 00:11:21.000 --> 00:11:24.000 this broader group, this broader cross-app group. 00:11:24.000 --> 00:11:31.000 to discuss ways in which we might possibly find the best of both worlds. 00:11:31.000 --> 00:11:34.000 Or how do we resolve this conflict? Because… 00:11:34.000 --> 00:11:37.000 Um, having one app 00:11:37.000 --> 00:11:44.000 with separate behaviors. Again, inconsistency isn't good, but it's also challenging, uh, 00:11:44.000 --> 00:11:46.000 Just in terms of… 00:11:46.000 --> 00:11:54.000 testing and migration and translations, and all of those little under… other underlying things. 00:11:54.000 --> 00:11:57.000 that feed into, uh, stripes. 00:11:57.000 --> 00:12:03.000 So that's… that's really why I'm… I'm… I'm coming to you, because we do have a business need. 00:12:03.000 --> 00:12:06.000 for creating durable filters. 00:12:06.000 --> 00:12:10.000 But I also recognize that that's not necessarily universal. 00:12:10.000 --> 00:12:11.000 Laura, I see you have your hand up. 00:12:11.000 --> 00:12:15.000 Hello! 00:12:15.000 --> 00:12:25.000 Yeah, I was thinking about this when I read this and hearing you talk about it, thinking about it again, that I could see a lot of area… other places where 00:12:25.000 --> 00:12:30.000 Some users really might want and benefit from durable filters. 00:12:30.000 --> 00:12:38.000 Um, and so my ideal solution to this is probably a whole lot of work, but would be 00:12:38.000 --> 00:12:42.000 to… to make this personalizable across Folio. 00:12:42.000 --> 00:12:45.000 Across the app, so that in every app, 00:12:45.000 --> 00:12:47.000 The filters are not… 00:12:47.000 --> 00:12:51.000 By default, sticky, but… 00:12:51.000 --> 00:12:56.000 Um, each user or institution. 00:12:56.000 --> 00:13:00.000 could set… 00:13:00.000 --> 00:13:04.000 filters, and I'm thinking of something like in inventory. 00:13:04.000 --> 00:13:09.000 If something is staff-suppressed. Some institutions really want that always 00:13:09.000 --> 00:13:16.000 to be, um, not true for the default. Others want it to not be not true. 00:13:16.000 --> 00:13:21.000 Um, so I… I see some potential here to… 00:13:21.000 --> 00:13:30.000 to come up with a better experience for everyone if it's possible to prioritize that work for personalization. 00:13:30.000 --> 00:13:34.000 I'm not opposed to, uh, it might be a lot of work. 00:13:34.000 --> 00:13:37.000 Um, I know there's… 00:13:37.000 --> 00:13:42.000 a growing number of, of, uh… 00:13:42.000 --> 00:13:45.000 cases where we're starting to do personalization work. 00:13:45.000 --> 00:13:52.000 And this does seem like it would be a good candidate, which is why I wanted… one of the reasons I wanted to discuss it more thoroughly here. 00:13:52.000 --> 00:13:58.000 Um, especially if I can dump it onto stripes rather than keeping it in ThunderJek, that would make me ecstatic. 00:13:58.000 --> 00:14:01.000 But, um… 00:14:01.000 --> 00:14:04.000 Yeah, so, um, I definitely don't want to discount that. 00:14:04.000 --> 00:14:07.000 But I think… 00:14:07.000 --> 00:14:15.000 Um… yeah. 00:14:15.000 --> 00:14:22.000 Yeah, this is just a question, if this is part of why the behavior is different. So. 00:14:22.000 --> 00:14:30.000 in reg- like, if you're in orders right now, and you do… You do a search. 00:14:30.000 --> 00:14:40.000 Um, and you open up, say, like a PO line, let's just say, and you do another search. 00:14:40.000 --> 00:14:43.000 Um, it doesn't close the peel line that you're looking at, you know? 00:14:43.000 --> 00:14:50.000 But if you're in inventory, it closes like the record that you're… we're currently looking at. 00:14:50.000 --> 00:14:51.000 Is that also going to be part of this change, or is that, like, a separate, um, issue? 00:14:51.000 --> 00:15:01.000 Uh, Kristen, I see you've got your hand up as well. 00:15:01.000 --> 00:15:02.000 I think it… 00:15:02.000 --> 00:15:08.000 Because sometimes it throws people off. Like, you know, they… do you know what I'm saying? Like, if you do a search, especially, like, if you do, like, a general search. 00:15:08.000 --> 00:15:16.000 and then you're like, oh, you know what, I actually, I have this really specific number, and then you can do a search for that number. You'll see the results. 00:15:16.000 --> 00:15:21.000 in your details, but then what's actually open is not going to be related to your search anymore. 00:15:21.000 --> 00:15:23.000 Right. Um… 00:15:23.000 --> 00:15:27.000 that hadn't been factored in, but uh… I… 00:15:27.000 --> 00:15:30.000 definitely think it's something that could be added. 00:15:30.000 --> 00:15:33.000 to, uh, the page as… 00:15:33.000 --> 00:15:36.000 an additional aspect of the problem. 00:15:36.000 --> 00:15:42.000 So, I'm glad… I'm glad you… you mentioned that, um, because this is some… another thing that we probably should raise with Stripes. 00:15:42.000 --> 00:15:44.000 Because, again, this is about… this is about consistency across apps. 00:15:44.000 --> 00:15:48.000 Yeah. 00:15:48.000 --> 00:15:51.000 Um… 00:15:51.000 --> 00:15:54.000 And so related to that, what… 00:15:54.000 --> 00:15:58.000 should the behavior be? I would assume that in most cases, if you're… 00:15:58.000 --> 00:16:01.000 working, uh, in multiple… 00:16:01.000 --> 00:16:08.000 areas or tabs, and you have to switch back and forth, you would want some memory of where you were working. 00:16:08.000 --> 00:16:15.000 I know in acquisitions, it's particularly important, because so many various components of the system are… 00:16:15.000 --> 00:16:18.000 are impacted. 00:16:18.000 --> 00:16:22.000 I don't know enough about inventory to, uh… 00:16:22.000 --> 00:16:24.000 to say for certain… 00:16:24.000 --> 00:16:27.000 why that decision would have been made, but… 00:16:27.000 --> 00:16:29.000 Yeah, let's… 00:16:29.000 --> 00:16:36.000 Yeah, I think, you know, I like where Laura was going here, too, is just. 00:16:36.000 --> 00:16:43.000 Like, I know right now, if I'm working in acquisitions versus working in inventory, it just works different. 00:16:43.000 --> 00:17:13.000 Uh, and so I've gotten in the habit of, like, oh, if I'm doing a search in an orders, I better make sure there's no filters on that I don't want, because I had previously done a search that used these filters. Um, so I think the idea of maybe making a customizable. 00:17:17.000 --> 00:17:19.000 Yeah, so… 00:17:19.000 --> 00:17:21.000 First of all, though, I'd say 00:17:21.000 --> 00:17:24.000 Or this isn't the only app that has 00:17:24.000 --> 00:17:29.000 uh… maybe some… some different behaviour, 00:17:29.000 --> 00:17:34.000 around filters, and it's something that's been… 00:17:34.000 --> 00:17:38.000 Um, an issue in agreements, 00:17:38.000 --> 00:17:40.000 And… 00:17:40.000 --> 00:17:42.000 well, mainly agreements, I think. 00:17:42.000 --> 00:17:45.000 as well, which is that 00:17:45.000 --> 00:17:50.000 we've always had a default set of filters that are applied. 00:17:50.000 --> 00:17:53.000 Um, automatically. 00:17:53.000 --> 00:17:56.000 Um, on visiting the app. 00:17:56.000 --> 00:18:00.000 Which, um… 00:18:00.000 --> 00:18:05.000 Which is kind of partly because… I mean, essentially, 00:18:05.000 --> 00:18:09.000 the reasoning, I suppose, goes initially that 00:18:09.000 --> 00:18:12.000 if you've got a set of things where 00:18:12.000 --> 00:18:14.000 some things are shown and some things are not. 00:18:14.000 --> 00:18:16.000 Um, and you have… 00:18:16.000 --> 00:18:18.000 some, uh… 00:18:18.000 --> 00:18:21.000 like, orders or, like, agreements where… 00:18:21.000 --> 00:18:26.000 those things that are in the past and no longer active are really 00:18:26.000 --> 00:18:33.000 I'm rarely of interest to the current user. I mean, not never. Obviously, sometimes you want to find the specific thing. 00:18:33.000 --> 00:18:38.000 Um, but often you're dealing with, you know, what is currently 00:18:38.000 --> 00:18:41.000 active on the system, then 00:18:41.000 --> 00:18:45.000 having the user have to click that filter every time. 00:18:45.000 --> 00:18:48.000 feels like an imposition on the user. 00:18:48.000 --> 00:18:51.000 and not great usability. So… 00:18:51.000 --> 00:18:53.000 Um, so Agreements has… 00:18:53.000 --> 00:18:58.000 some default filters. They don't work in quite the same way as 00:18:58.000 --> 00:19:02.000 the orders ones, and that leads to some… 00:19:02.000 --> 00:19:05.000 different behaviour, so the exact 00:19:05.000 --> 00:19:09.000 issue, I think, that led to this being raised in the first place was that… 00:19:09.000 --> 00:19:12.000 If you paste a URL in orders, 00:19:12.000 --> 00:19:15.000 actually then the… 00:19:15.000 --> 00:19:19.000 filters are applied on top of the URL you have pasted, so… 00:19:19.000 --> 00:19:24.000 you… you kind of get a situation where the user's pasting a URL and then really not getting 00:19:24.000 --> 00:19:26.000 the results they're expecting. 00:19:26.000 --> 00:19:30.000 I'm in agreement, we always… 00:19:30.000 --> 00:19:32.000 defer to what has been 00:19:32.000 --> 00:19:35.000 put into the address bar. So the address bar is the lead 00:19:35.000 --> 00:19:37.000 thing, not the, um… 00:19:37.000 --> 00:19:41.000 Not the app never overrides what's been put into the address bar. 00:19:41.000 --> 00:19:44.000 Um, so there's some different behaviour there, but I think 00:19:44.000 --> 00:19:50.000 probably, like, the reasons at the heart of why agreements behave differently… 00:19:50.000 --> 00:19:56.000 you know, overlap, at least, or are the same for why orders behaves differently in terms of 00:19:56.000 --> 00:20:01.000 the desire for use from the desired behavior from a user perspective. 00:20:01.000 --> 00:20:04.000 And we have always kind of said, 00:20:04.000 --> 00:20:09.000 making it customisable per user is probably the ultimate 00:20:09.000 --> 00:20:15.000 like, behavior you'd want here, that they could define. 00:20:15.000 --> 00:20:17.000 Uh, the default filters that are used. 00:20:17.000 --> 00:20:19.000 And I guess that actually in… 00:20:19.000 --> 00:20:24.000 Um, inventory, there's kind of a bit of a… 00:20:24.000 --> 00:20:28.000 a cheat to this, which is there's the staff suppressed 00:20:28.000 --> 00:20:32.000 thing that I think just automatically applies unless you… 00:20:32.000 --> 00:20:34.000 kind of… 00:20:34.000 --> 00:20:37.000 It… that was changed, because so many of us 00:20:37.000 --> 00:20:39.000 Okay. 00:20:39.000 --> 00:20:40.000 had problems with it. 00:20:40.000 --> 00:20:42.000 So… so that… 00:20:42.000 --> 00:20:45.000 Yeah, so that was a behaviour, but it's just that this… 00:20:45.000 --> 00:20:49.000 This idea of automatically having some filters 00:20:49.000 --> 00:20:52.000 is a desirable behaviour, and I… I do think… 00:20:52.000 --> 00:20:55.000 that having customizable 00:20:55.000 --> 00:21:00.000 options is probably the right way to go here. I… I… 00:21:00.000 --> 00:21:02.000 I do think still… 00:21:02.000 --> 00:21:06.000 you… if somebody pastes something into the browser bar, 00:21:06.000 --> 00:21:13.000 I think overwriting that is dangerous. I think that that… that stops sharing… that stops users sharing links, and I think that that should be… 00:21:13.000 --> 00:21:19.000 something that we should not do. I think that we… I think whatever solution here has to avoid… 00:21:19.000 --> 00:21:23.000 a situation where you can't freely share a link with a colleague. 00:21:23.000 --> 00:21:25.000 And… and have the behaviour 00:21:25.000 --> 00:21:28.000 essentially have them see what you, you know, 00:21:28.000 --> 00:21:31.000 what you expect them to see. But, um… 00:21:31.000 --> 00:21:36.000 I think that having some ability to customize default filters, 00:21:36.000 --> 00:21:42.000 Um, maybe even having some way of applying a set of filters that you've previously saved. 00:21:42.000 --> 00:21:44.000 Um, uh… 00:21:44.000 --> 00:21:46.000 Rather than having to click through every 00:21:46.000 --> 00:21:53.000 Every filter that you want to apply to a particular scenario would be a really good idea. And to some extent, 00:21:53.000 --> 00:21:57.000 That is also something that we do in the… 00:21:57.000 --> 00:21:59.000 Um, dashboard app. 00:21:59.000 --> 00:22:05.000 is that actually what that allows the user to do is to save a fault… a set of filters. 00:22:05.000 --> 00:22:07.000 Which, uh… 00:22:07.000 --> 00:22:15.000 are used automatically. Um, it's a bit of a different scenario, but it… but it's… I think, ultimately, it's the same idea that 00:22:15.000 --> 00:22:19.000 Some searches are more useful than others, and you might want to do them 00:22:19.000 --> 00:22:21.000 on a regular basis, and therefore… 00:22:21.000 --> 00:22:25.000 being able to access those searches and filters very easily is a… 00:22:25.000 --> 00:22:29.000 a good behaviour. So, certainly very much in favor of… 00:22:29.000 --> 00:22:33.000 Having this customizable both at a tenant level, I think tenant level 00:22:33.000 --> 00:22:38.000 options are good, um, but I think ultimately you need it at a personal level, because… 00:22:38.000 --> 00:22:43.000 Um… staff… different members of staff will have different… 00:22:43.000 --> 00:22:46.000 purposes that they go to the search screen to… 00:22:46.000 --> 00:22:48.000 to fulfill, and I think that that's… 00:22:48.000 --> 00:22:50.000 really important, um… 00:22:50.000 --> 00:22:52.000 you know, if you're only dealing with 00:22:52.000 --> 00:22:58.000 monograph orders, why not have that as a filter that you've, you know, you're starting with? You don't need all the rest of the… 00:22:58.000 --> 00:23:00.000 the stuff in there, so… 00:23:00.000 --> 00:23:03.000 Yeah, uh, that's a long-winded way of saying 00:23:03.000 --> 00:23:06.000 I'm with you, Joe. Um, I do think there are some 00:23:06.000 --> 00:23:11.000 things we need to be careful about in terms of how pasting URLs work specifically, but in general. 00:23:11.000 --> 00:23:18.000 I think having some level of customizing both of the tenant and at the 00:23:18.000 --> 00:23:19.000 personal… the user level is… 00:23:19.000 --> 00:23:22.000 Oh, and I see you've got your hand up, and I saw, uh, Tara, you posted an important question in the chat as well, so go ahead, Owen. 00:23:22.000 --> 00:23:26.000 Yeah, the… where we do the custom… where we would do that… that setting of things. 00:23:26.000 --> 00:23:29.000 Um… 00:23:29.000 --> 00:23:32.000 I think it's safe to assume that most people 00:23:32.000 --> 00:23:38.000 given the option, would prefer that it be personal rather than tenant-wide. 00:23:38.000 --> 00:23:43.000 And I'm… I'm thinking a small library would probably be fine. 00:23:43.000 --> 00:23:45.000 with tenant-wide… 00:23:45.000 --> 00:23:50.000 Just based on their workflows, but when you get into larger institutions, 00:23:50.000 --> 00:23:55.000 Where you have specialized staff that work in specialized areas. 00:23:55.000 --> 00:24:00.000 that… that could actually be counterproductive, because then you'd have… 00:24:00.000 --> 00:24:04.000 Um, for instance, if you have 00:24:04.000 --> 00:24:06.000 acquisitions and serials acquisitions that are… 00:24:06.000 --> 00:24:11.000 separate, or e-resource acquisitions that are all separate. 00:24:11.000 --> 00:24:15.000 they're probably going to want separate 00:24:15.000 --> 00:24:17.000 defaults for different types of defaults, so… 00:24:17.000 --> 00:24:21.000 Um, in that case, having it durable… 00:24:21.000 --> 00:24:24.000 From session to session. 00:24:24.000 --> 00:24:26.000 or having a personalized per user. 00:24:26.000 --> 00:24:30.000 would make a lot more sense. So, um… 00:24:30.000 --> 00:24:36.000 I think in terms of doing it… I mean, I'm kind of of the opinion, even if it's more work, let's do it right the first time. 00:24:36.000 --> 00:24:39.000 Especially since we are now 00:24:39.000 --> 00:24:43.000 introducing awe. 00:24:43.000 --> 00:24:47.000 some level of personalization. 00:24:47.000 --> 00:24:50.000 Um, the other… the other question, then, 00:24:50.000 --> 00:24:56.000 would be with the personalization, because we don't want death by a thousand paper cuts. 00:24:56.000 --> 00:24:59.000 Um, would we want to, like, 00:24:59.000 --> 00:25:06.000 for me, portfolio, remember all my settings, or would we want to break it down, say, 00:25:06.000 --> 00:25:10.000 Uh, by… app. 00:25:10.000 --> 00:25:16.000 or by some other area, because I don't… I don't want it. 00:25:16.000 --> 00:25:22.000 like, um, I'm assuming if you wanted in orders, you'll probably also want it in invoices and receiving. 00:25:22.000 --> 00:25:25.000 I could be wrong. Um… 00:25:25.000 --> 00:25:31.000 But, like, does it make sense to do an app acquisitions, or do I have to do it for each… 00:25:31.000 --> 00:25:34.000 armed. Each little sub-component. 00:25:34.000 --> 00:25:37.000 Um… 00:25:37.000 --> 00:25:51.000 I guess. It's… yeah, the question is, what is… what is the sweet spot in terms of granularity? 00:25:51.000 --> 00:25:55.000 This personalization here remember the last thing I did, or set defaults? 00:25:55.000 --> 00:25:58.000 I was thinking, um… 00:25:58.000 --> 00:26:01.000 remember the last thing I did? 00:26:01.000 --> 00:26:04.000 would, like, either remember or don't remember. 00:26:04.000 --> 00:26:06.000 Um… 00:26:06.000 --> 00:26:09.000 But… we could certainly look… 00:26:09.000 --> 00:26:12.000 at setting defaults. 00:26:12.000 --> 00:26:16.000 Although, setting defaults 00:26:16.000 --> 00:26:19.000 would then require… the setting defaults would require a lot more work. 00:26:19.000 --> 00:26:22.000 Because then we'd need to figure out a place where to set defaults, 00:26:22.000 --> 00:26:29.000 or save what I've got as the default for this application. 00:26:29.000 --> 00:26:37.000 So, Joe, it sounds like you're saying that what you're proposing is app-by-app or folio-wide, you could set 00:26:37.000 --> 00:26:40.000 for the user to remember the last thing that they did. 00:26:40.000 --> 00:26:51.000 But I'm also hearing a lot of, like, there should be defaults and they should be different for different members of staff. 00:26:51.000 --> 00:26:52.000 But it sounds… yeah. 00:26:52.000 --> 00:26:54.000 And again, I'm not really, you know, I'm not… I'm not necessarily married to a certain… 00:26:54.000 --> 00:26:56.000 I'm more trying to get to 00:26:56.000 --> 00:27:04.000 what would the ideal case be here? We're gonna have to look at this. So, that's kind of why I'm coming to you as… 00:27:04.000 --> 00:27:06.000 you know, this was, uh… 00:27:06.000 --> 00:27:09.000 brought to me by Stripes, saying, 00:27:09.000 --> 00:27:13.000 This is inconsistent. So, if we're gonna make it consistent, I want to do it right. 00:27:13.000 --> 00:27:18.000 And I want to talk with… 00:27:18.000 --> 00:27:24.000 a group that is invested in folio at large and in multiple applications, because consistency is key. 00:27:24.000 --> 00:27:27.000 So, if we're going to do it consistently, and if we're going to put it into stripes, 00:27:27.000 --> 00:27:32.000 How would we want it to work? How can we make this really good? 00:27:32.000 --> 00:27:33.000 So I'm… 00:27:33.000 --> 00:27:41.000 I mean, I'm definitely on Team Default, but my job's different from a lot of library users, so… 00:27:41.000 --> 00:27:45.000 But it sounds like there are maybe others here who are also on Team Defaults. 00:27:45.000 --> 00:27:46.000 I'm… 00:27:46.000 --> 00:27:47.000 I'm… oh, sorry, go ahead. 00:27:47.000 --> 00:27:49.000 Go ahead. 00:27:49.000 --> 00:27:57.000 I was gonna say, I'm very much on team defaults, because I know I'm not always going to folio to do the same thing. 00:27:57.000 --> 00:28:02.000 And the apps that do remember what I did last time always throw me. 00:28:02.000 --> 00:28:08.000 Because they're showing me something that was relevant to me last week, maybe. 00:28:08.000 --> 00:28:10.000 Um, and I think… 00:28:10.000 --> 00:28:14.000 it's rare. There are cases, but I feel like it's rare where a 00:28:14.000 --> 00:28:23.000 a library staff person really only ever does one thing. 00:28:23.000 --> 00:28:25.000 And, like, the behavior in… 00:28:25.000 --> 00:28:28.000 orders right now, at least, seems like it's, like, 00:28:28.000 --> 00:28:31.000 remember that you searched for newspaper a week ago? Is that right? 00:28:31.000 --> 00:28:37.000 Yes, and it always makes me wonder what I did wrong, because I'm expecting 00:28:37.000 --> 00:28:50.000 something different than, you know, what I might have done literally because I don't look in orders very often. I… I don't remember that I did that search. So I think it's making stuff up. 00:28:50.000 --> 00:28:59.000 Yeah, like, here's an example. So, if you're looking here, for example, we at Chicago should not have any order lines that are in the pending. 00:28:59.000 --> 00:29:06.000 category. But I might search I might filter depending to find those out and be like, oh. 00:29:06.000 --> 00:29:20.000 These are a problem because, you know, something went wrong and somebody didn't finish them, or whatever, so let's figure out what's happening. Then, if I come back to orders later, and I have an actual, like, PO number. 00:29:20.000 --> 00:29:37.000 I don't want it to be limited to pending. Like, I was doing that search because I, you know, needed to find things that were pending, and it was great, it was easy to find them, I got the report, I exported it out, you know. But when I'm, you know, if I'm searching by a PO number, I don't… I have to just make sure I reset my limits. 00:29:37.000 --> 00:29:46.000 Um, so I think that that's a little different, like, I would not choose to have, I only want to look at pending order lines as a default. 00:29:46.000 --> 00:29:52.000 Um, but I like having that filter as an option to like check for it, you know. 00:29:52.000 --> 00:29:57.000 Maura, I see you have your hand up. 00:29:57.000 --> 00:30:08.000 Yeah, and this might be. you know, trying to, like… Come up with a technical solution before we've defined what we want. 00:30:08.000 --> 00:30:18.000 But what that sounds like to me is that, like, you've done this thing, your browser remembers it, at least for the duration of your browser session. 00:30:18.000 --> 00:30:27.000 and that, you know, it will forget it when you if you do it again, unless you have something specifically. 00:30:27.000 --> 00:30:37.000 set as a default. Um, but… you know, sort of… I'm thinking visually, if you have something where. 00:30:37.000 --> 00:30:54.000 Your browser session is going to remember. a filter that you put on, then maybe the thing to do is to have the… you know, like the indication of the filter being applied. 00:30:54.000 --> 00:31:08.000 being, like, put at the top of this, like, list on the, um… on the left side here in the left column where we have, you know, repeat receipt status and payment status and etc. And etc. If that one could sort of be… 00:31:08.000 --> 00:31:23.000 You know, listed up top to say, oh, by the way, right now, you're filtering for this for at least the duration of this browser session. Um, and if you want that to change, you can, you know, unfilter. 00:31:23.000 --> 00:31:36.000 So that's, you know, that might be getting ahead of, you know, what we're what we're talking about, but it seems like, you know, we're doing, you know. 00:31:36.000 --> 00:31:41.000 It seems like what we're looking for, you know, the I wish involved. 00:31:41.000 --> 00:31:53.000 Is that we'd like to be able to do things in the short term and have something remember, you know, in work that you're doing now, which we could call like. 00:31:53.000 --> 00:32:10.000 you know, the app remembers it for the duration of the browser session. And then forgets it tomorrow when you reopen the browser. As opposed to something you can set as a default thing, because it's something you do. 00:32:10.000 --> 00:32:23.000 Every time you're in that app. Um, do I do I have that right? 00:32:23.000 --> 00:32:24.000 But not with AI. 00:32:24.000 --> 00:32:29.000 Yes, Laura. Of course we want Folio to read our minds. But, uh, um… No, no. 00:32:29.000 --> 00:32:31.000 AI is just a dressed up Clippy. 00:32:31.000 --> 00:32:36.000 Yeah, um, so I agree with what Tara says about, um, 00:32:36.000 --> 00:32:38.000 If you paste the URL, 00:32:38.000 --> 00:32:42.000 the URL should be obeyed hard stop. 00:32:42.000 --> 00:32:49.000 And I think we agree with that. Um, and I think that's one of the stated outcomes that we need. So… 00:32:49.000 --> 00:32:57.000 Um, Tara, I'm gonna put your mind at rest. That is one of the acceptance criteria for doing this, because you URLs do need to behave consistently across the board. 00:32:57.000 --> 00:33:03.000 Um, what I was going to ask is… so we're on… this is actually a really good screen to be on. 00:33:03.000 --> 00:33:07.000 Um, where… 00:33:07.000 --> 00:33:11.000 How would… what would be the… 00:33:11.000 --> 00:33:15.000 process, workflow, uh, UX, whatever. 00:33:15.000 --> 00:33:19.000 that you would expect if you want to set 00:33:19.000 --> 00:33:22.000 a default search slash filter. 00:33:22.000 --> 00:33:26.000 like, how would you want to say, I'm here in orders, 00:33:26.000 --> 00:33:28.000 this is what I want as the default. 00:33:28.000 --> 00:33:33.000 Because if we try to go into settings… 00:33:33.000 --> 00:33:43.000 Um, and do that for every screen. It's going to be death by a thousand paper cuts. 00:33:43.000 --> 00:33:49.000 So you're picturing, like, like, kind of… I don't know if I can bring one of these up, uh… 00:33:49.000 --> 00:33:56.000 I'm sure someone knows what I'm about to say, but like, you know, like, these little buggers here? Like, you're picturing one of those up here. 00:33:56.000 --> 00:33:58.000 Where you could set defaults or something like that? 00:33:58.000 --> 00:34:03.000 It's just something somewhere. 00:34:03.000 --> 00:34:04.000 Yeah. 00:34:04.000 --> 00:34:05.000 Um, like, and I'll probably need… I'll need to talk with Kimmy about it, too. 00:34:05.000 --> 00:34:12.000 But, like, what would be quick, easy, painless, not take up too much real estate, and… and just… 00:34:12.000 --> 00:34:15.000 makes sense. Because, like, the… 00:34:15.000 --> 00:34:18.000 Or, like, something up here. 00:34:18.000 --> 00:34:19.000 Yeah. 00:34:19.000 --> 00:34:25.000 Yeah, I think being over on the search and filter side would make more sense than over on the actions. 00:34:25.000 --> 00:34:27.000 side. 00:34:27.000 --> 00:34:29.000 Yeah, I was picturing, like, little… 00:34:29.000 --> 00:34:34.000 little… whatever icon means default to all humans in existence. 00:34:34.000 --> 00:34:38.000 like, on this thing. Um, but this seems like… 00:34:38.000 --> 00:34:42.000 Mostly, I just want to know what Kimmy says, because… 00:34:42.000 --> 00:34:44.000 The last suggestion was great, and… 00:34:44.000 --> 00:34:46.000 I'm smarter than me. 00:34:46.000 --> 00:34:51.000 Yes. Kimmy is so good. 00:34:51.000 --> 00:34:54.000 Um, 00:34:54.000 --> 00:34:56.000 But yeah, if I walk in with… 00:34:56.000 --> 00:35:03.000 like, a bad idea, then she'll take it and make it way, way, way better, rather than if I walk in with no idea. 00:35:03.000 --> 00:35:04.000 But… yeah. 00:35:04.000 --> 00:35:06.000 We've had at least two medium-okay ideas, so… 00:35:06.000 --> 00:35:08.000 Yeah, yeah. So… 00:35:08.000 --> 00:35:15.000 Um, but I'm definitely getting loud and clear that having it in the search and filter bar somewhere, and maybe having a little icon. 00:35:15.000 --> 00:35:19.000 Or… or the orders drop-down. 00:35:19.000 --> 00:35:20.000 Yep. 00:35:20.000 --> 00:35:22.000 Or something like that. Just… 00:35:22.000 --> 00:35:25.000 set as, you know… 00:35:25.000 --> 00:35:31.000 Yeah, set default filter. 00:35:31.000 --> 00:35:34.000 Owen is asking… 00:35:34.000 --> 00:35:40.000 Do we need to collect user stories about when it's useful to preserve the last filter and when it's useful to have defaults? 00:35:40.000 --> 00:35:46.000 And when it's useful to have no fig… no, uh, filter set. 00:35:46.000 --> 00:35:47.000 I think it would be worth doing. 00:35:47.000 --> 00:35:51.000 Um, I think in the absence of that, it makes sense… 00:35:51.000 --> 00:35:56.000 to have memory within a folio session. 00:35:56.000 --> 00:36:04.000 And defaults on a clean login. 00:36:04.000 --> 00:36:07.000 But that's just me. 00:36:07.000 --> 00:36:14.000 Like, if I log out and log back in, I should expect everything to be clean. If I'm staying logged in, I'd want the memory, but… 00:36:14.000 --> 00:36:25.000 I'm a sample size of 1. 00:36:25.000 --> 00:36:35.000 Hard refresh also resets, yeah. 00:36:35.000 --> 00:36:43.000 In my work, I am more likely to be frustrated by a filter still being applied that I forgot I set. 00:36:43.000 --> 00:36:53.000 than I am by having to set the filter, but that's also sample size of 1. 00:36:53.000 --> 00:36:54.000 You know, 00:36:54.000 --> 00:36:55.000 Well… Oh, sorry. 00:36:55.000 --> 00:36:59.000 I'm just… go ahead. 00:36:59.000 --> 00:37:11.000 I was wondering to follow up on Laura's question and and the notion that you know, like, if you send a URL, and you want it to behave the way. 00:37:11.000 --> 00:37:19.000 the URL, you know, is set. and not sort of override anything. 00:37:19.000 --> 00:37:34.000 Do you want, um, does that mean that. Does that mean that the app contains the filter and continues to contain the filter that's included in the URL until like you close that tab. 00:37:34.000 --> 00:37:41.000 And open a new one. Or does that filter propagate for the remainder of your browser session? 00:37:41.000 --> 00:37:50.000 Um, in which case you can… someone can… inadvertently set filters for you. 00:37:50.000 --> 00:38:02.000 By sending you a URL and then you click on it, there's a filter being set to get you the data you're looking for. And then when you come back to do something else, that filter is still. 00:38:02.000 --> 00:38:09.000 is still working. 00:38:09.000 --> 00:38:10.000 No, it's clear, it's something to think about. 00:38:10.000 --> 00:38:18.000 and thus might confuse you. 00:38:18.000 --> 00:38:24.000 I see Charlotte's comment about, uh, an alternative to listing in the top of the search. 00:38:24.000 --> 00:38:28.000 of a colored icon next to the given filter being selected as default. 00:38:28.000 --> 00:38:31.000 I was thinking about, like, right under… 00:38:31.000 --> 00:38:34.000 and just spitballing here, right under the search and filter. 00:38:34.000 --> 00:38:41.000 as you check and uncheck, you have, like, a box that basically creates… shows you exactly 00:38:41.000 --> 00:38:45.000 what's in real time. So, orders right underneath… 00:38:45.000 --> 00:38:53.000 orders or above where, like, the little tabs have a box that… because right now, it's just pending. 00:38:53.000 --> 00:39:02.000 So the… just… it only has status appending, and then as you add additional things, the box up top just fills in automatically. 00:39:02.000 --> 00:39:08.000 And when you set anything, then there's a little button saying set default. 00:39:08.000 --> 00:39:14.000 could possibly be a weight, yeah. 00:39:14.000 --> 00:39:20.000 Because right now, yeah, we see status and order type are both selected, so I'm seeing, like, a little box right at the top. 00:39:20.000 --> 00:39:27.000 Um, either under… right underneath search and filter and above orders, or right below orders, something. 00:39:27.000 --> 00:39:31.000 Where it says… 00:39:31.000 --> 00:39:36.000 orders, status equals pending, and order type equals… 00:39:36.000 --> 00:39:40.000 whatever. 00:39:40.000 --> 00:39:44.000 Um, so that you know… you see right at the top. 00:39:44.000 --> 00:39:46.000 That is the active filter. 00:39:46.000 --> 00:39:49.000 Precisely. That is the precise filter. 00:39:49.000 --> 00:39:53.000 Um, my only hesitation on, like, color coding and stuff, 00:39:53.000 --> 00:40:02.000 is some apps have very, very long lists of filters, so you have to scroll through the whole list to see anything that's potentially filterable. 00:40:02.000 --> 00:40:09.000 Um, we're having a box at the top saying, 00:40:09.000 --> 00:40:10.000 Yeah. 00:40:10.000 --> 00:40:12.000 Yeah, reset all is… 00:40:12.000 --> 00:40:20.000 mostly… yeah, if you see reset all, that's usually correct, except I know for a fact we have an open bug for that in… 00:40:20.000 --> 00:40:24.000 one of our apps where it's coming up as reset all when it shouldn't. 00:40:24.000 --> 00:40:26.000 And… we are… 00:40:26.000 --> 00:40:30.000 planning to be able to get to that when we're able to. 00:40:30.000 --> 00:40:35.000 But… yeah, colors do add accessibility issues. 00:40:35.000 --> 00:40:46.000 The little X is a good indication that something in there is selected, but not exactly what. That's why I was thinking having a box up top, because I would just be very clear. 00:40:46.000 --> 00:40:58.000 And again, I'm sure Kimmy will have a thousand and one thoughts about the way we could handle this. 00:40:58.000 --> 00:41:06.000 But yeah, some sort of… we definitely need some sort of visual clue. 00:41:06.000 --> 00:41:09.000 So, on the assumption that, uh… 00:41:09.000 --> 00:41:12.000 An expert's going to come back with the best of all possible 00:41:12.000 --> 00:41:16.000 how to make it look nice options. Um… 00:41:16.000 --> 00:41:19.000 going back to, uh… 00:41:19.000 --> 00:41:28.000 Do we need to collect user stories about when it's useful to preserve the last filter? Is that something that the cross-app SIG will need to do? 00:41:28.000 --> 00:41:29.000 Yes, probably. 00:41:29.000 --> 00:41:32.000 I think it would be helpful. 00:41:32.000 --> 00:41:33.000 Yeah. 00:41:33.000 --> 00:41:35.000 Um, I can certainly bring it to the acquisition SIG. 00:41:35.000 --> 00:41:39.000 Um, and I think, you know, people who have… 00:41:39.000 --> 00:41:46.000 who are engaged with other SIGs, I think that would be very, very useful. 00:41:46.000 --> 00:41:48.000 Um… 00:41:48.000 --> 00:41:54.000 Just because, yeah, I mean, I think the various SIGs should, uh, 00:41:54.000 --> 00:41:58.000 should evaluate this, because… 00:41:58.000 --> 00:42:00.000 that those are where the real subject matters are, so… 00:42:00.000 --> 00:42:04.000 Um… 00:42:04.000 --> 00:42:09.000 Okay, so this seems like a case where, like, because it could potentially affect everyone, we have to make sure that we hit every single… 00:42:09.000 --> 00:42:11.000 Yeah. 00:42:11.000 --> 00:42:12.000 app that could be affected, right? 00:42:12.000 --> 00:42:14.000 Yeah. 00:42:14.000 --> 00:42:19.000 So, maybe, maybe we should do something… 00:42:19.000 --> 00:42:20.000 slightly more… 00:42:20.000 --> 00:42:22.000 I can… 00:42:22.000 --> 00:42:23.000 shop around to our favorite SIGs. 00:42:23.000 --> 00:42:25.000 Yeah, I'll reach out to… 00:42:25.000 --> 00:42:26.000 make a table or something. 00:42:26.000 --> 00:42:29.000 Is anybody here, uh, part of Resource Access? 00:42:29.000 --> 00:42:32.000 If not, I'll ask Anne or Steph to… 00:42:32.000 --> 00:42:37.000 raise the issue with them. 00:42:37.000 --> 00:42:40.000 Well, I think we need to form the question really specifically, because it's like, 00:42:40.000 --> 00:42:43.000 Yeah. 00:42:43.000 --> 00:42:45.000 It's… it's hard to say, like, uh… 00:42:45.000 --> 00:42:55.000 when it's useful to preserve the last filter, because, like, the example that I thought of immediately, it was, like, when you're checking stuff out, and, like, you've got your patron here, and then you pop over to look at the patron, 00:42:55.000 --> 00:43:00.000 And then it takes you right back to the checkout screen, and that sticks around, but also… 00:43:00.000 --> 00:43:06.000 I think while you're checking things out, the user sticks around, but that might be a function of actually what's in the URL. 00:43:06.000 --> 00:43:14.000 Laura might know, because I don't actually know how that's set, because I think if you go back to users after that, it will… 00:43:14.000 --> 00:43:17.000 after you end your checkout session, it'll be blank again, I think. 00:43:17.000 --> 00:43:19.000 Right. 00:43:19.000 --> 00:43:25.000 I think that's how we have it designed. So that, you know, privacy. 00:43:25.000 --> 00:43:32.000 Yeah, I mean, this is really easy to check. Uh, so it takes us straight to the user, you close out of that, and it's blank. 00:43:32.000 --> 00:43:37.000 Right? But then I go back to checkout, and it's still up because I didn't end the session. 00:43:37.000 --> 00:43:38.000 Right. 00:43:38.000 --> 00:43:45.000 So I don't know if that counts or not, right? Because, like, that's going straight to a record rather than remembering a search. 00:43:45.000 --> 00:43:47.000 No, but it's a pattern we need to be aware of. 00:43:47.000 --> 00:43:49.000 Because maybe that's a better pattern. 00:43:49.000 --> 00:43:50.000 Okay. 00:43:50.000 --> 00:43:56.000 Um… 00:43:56.000 --> 00:44:01.000 So, no, I do think it's relevant. 00:44:01.000 --> 00:44:06.000 Sweet. 00:44:06.000 --> 00:44:07.000 Any other discussion? Go ahead. 00:44:07.000 --> 00:44:13.000 Tara, I'm wondering if maybe our next meeting, we want to try to… 00:44:13.000 --> 00:44:19.000 craft, um, some sort of, you know, just a couple slides and some prompts. 00:44:19.000 --> 00:44:23.000 for us to take to SIGS, so we're all… 00:44:23.000 --> 00:44:26.000 asking the same questions. 00:44:26.000 --> 00:44:28.000 That's a great idea. I love that idea. 00:44:28.000 --> 00:44:31.000 Yeah, I think that's… I was going to say we could also consider doing a, uh… 00:44:31.000 --> 00:44:43.000 like a Google survey or something, but yeah, we do… we absolutely need to be clear and consistent on the, uh… 00:44:43.000 --> 00:44:47.000 messaging. What time… what time is the Monday meeting? 00:44:47.000 --> 00:44:49.000 Same as this one, just on Mondays. 00:44:49.000 --> 00:44:52.000 Okay, that one I have a conflict. 00:44:52.000 --> 00:44:54.000 Eh, okay. 00:44:54.000 --> 00:44:59.000 Um… 00:44:59.000 --> 00:45:00.000 Could we draft it and send it to you for feedback? 00:45:00.000 --> 00:45:03.000 Yeah. Yeah, that's absolutely fine. 00:45:03.000 --> 00:45:08.000 Um, and in fact, the page that I have set up, uh, 00:45:08.000 --> 00:45:12.000 that we were… yeah, where I'm outlining the problem. 00:45:12.000 --> 00:45:15.000 Um, please feel free to edit that. 00:45:15.000 --> 00:45:19.000 Um, and make additional, you know, feedback. 00:45:19.000 --> 00:45:21.000 changes and so forth. 00:45:21.000 --> 00:45:24.000 Um… 00:45:24.000 --> 00:45:27.000 there are a few things that are… that are written in stone. 00:45:27.000 --> 00:45:31.000 Um, like, the desired outcomes, I think, 00:45:31.000 --> 00:45:34.000 So that, at least what I've got there, 00:45:34.000 --> 00:45:38.000 is what Stripes is asking for. 00:45:38.000 --> 00:45:39.000 Okay. 00:45:39.000 --> 00:45:42.000 So we can clarify those, but um… 00:45:42.000 --> 00:45:44.000 that's, like… 00:45:44.000 --> 00:45:48.000 Yeah, if there are additional outcomes, please feel free to add. 00:45:48.000 --> 00:45:52.000 Um, but the 3 that I've added, those come from Stripes in terms of what they're expecting. 00:45:52.000 --> 00:45:57.000 Um… but yeah, this is great, and… 00:45:57.000 --> 00:46:01.000 like, I'm not claiming ownership over this page. 00:46:01.000 --> 00:46:03.000 Um, I… 00:46:03.000 --> 00:46:06.000 Yeah, I actually would, uh… 00:46:06.000 --> 00:46:14.000 Be very grateful if… if you would help answer some of these questions, because this is a community thing and not an acquisitions thing. It's just, we need to get 00:46:14.000 --> 00:46:18.000 everybody in alignment, and acquisitions is one of the, uh… 00:46:18.000 --> 00:46:23.000 problem children. 00:46:23.000 --> 00:46:25.000 Not a problem, child. 00:46:25.000 --> 00:46:26.000 Special flour. 00:46:26.000 --> 00:46:31.000 Now, we're a problem. 00:46:31.000 --> 00:46:37.000 Um, well, what a great opportunity to get some cool functionality added that could be useful across 00:46:37.000 --> 00:46:41.000 different apps. 00:46:41.000 --> 00:46:45.000 It's cool that a problem is becoming a feature. 00:46:45.000 --> 00:46:46.000 Okay, alright. 00:46:46.000 --> 00:46:52.000 Yeah, I think… I think… cool. Well, thank you so much for your time and for addressing this with me. 00:46:52.000 --> 00:47:00.000 Absolutely, thank you for coming to talk with us. Is there anything else that we should talk about on this subject, or should we, uh, just plan to pick this up on… 00:47:00.000 --> 00:47:02.000 Monday, while we're drafting those slides. 00:47:02.000 --> 00:47:08.000 Um, I think… I think I've… I've said everything that I need to said. 00:47:08.000 --> 00:47:10.000 everything that I need to say on this. 00:47:10.000 --> 00:47:17.000 And, uh, we've had a really good conversation, so I've got a lot of ideas and a lot more, um… 00:47:17.000 --> 00:47:18.000 I'm getting a lot more clarity. 00:47:18.000 --> 00:47:26.000 And raising a lot more questions, but we're getting closer to the point where we can actually define a feature. So, once we have the feedback from the SIGS, 00:47:26.000 --> 00:47:33.000 I think we can build out the feature, and then I'll coordinate with Stripes on where to go from there. 00:47:33.000 --> 00:47:37.000 So this is great, thank you. 00:47:37.000 --> 00:47:43.000 Amazing! Any more questions for Joe before we, uh… 00:47:43.000 --> 00:47:51.000 probably list the SIGs really feedback from. Yeah, we should list the SIGs we need feedback from, but I think we should actually list it app by app, because it's going to be different. 00:47:51.000 --> 00:47:53.000 per, um… 00:47:53.000 --> 00:47:56.000 Sorry, per section of folio. 00:47:56.000 --> 00:47:58.000 Um, I'm sure. Uh… 00:47:58.000 --> 00:48:03.000 And which… which SIG owns them. Does that make sense? 00:48:03.000 --> 00:48:05.000 Okay, awesome. Uh… 00:48:05.000 --> 00:48:07.000 Great. Okay. 00:48:07.000 --> 00:48:14.000 If we have nothing else to go over today, um, I will, uh, post what we need to do on Slack. 00:48:14.000 --> 00:48:17.000 And follow up on the Wolfgang, uh, question? 00:48:17.000 --> 00:48:18.000 But other than that, I think we are good for the day. So I will wish everyone a happy Wednesday, and we'll see you 00:48:18.000 --> 00:48:22.000 Yes. 00:48:22.000 --> 00:48:25.000 Next week. All right, bye! 00:48:25.000 --> 00:48:27.000 Thank you. 00:48:27.000 --> 00:48:31.000 Thank