WEBVTT 00:11:07.000 --> 00:11:11.000 the next, uh, JIRA ticket review. 00:11:11.000 --> 00:11:15.000 Um, will be the next cycle for that. 00:11:15.000 --> 00:11:17.000 Um… 00:11:17.000 --> 00:11:20.000 Any other calendaring… 00:11:20.000 --> 00:11:24.000 Announcements, thoughts? 00:11:24.000 --> 00:11:30.000 Tom, I said you were doing fee fines on Thursday, is that a lie? 00:11:30.000 --> 00:11:33.000 Awesome. Um… 00:11:33.000 --> 00:11:37.000 Great. Uh, let's see… 00:11:37.000 --> 00:11:46.000 You may have seen on Slack on Friday, Amelia Sutton sent out a UAT opportunity for testing how custom fields can be displayed on the checkout. 00:11:46.000 --> 00:11:52.000 screen. So, the info is… there's a little bit more info on the Slack post, but the link 00:11:52.000 --> 00:11:59.000 In the agenda is to the, um, page that has all the details. If you want to help out the deadline, 00:11:59.000 --> 00:12:04.000 For that, if I'm not mistaken, I just looked it up, and now I've forgotten it already. 00:12:04.000 --> 00:12:08.000 is April 1st, April Fool's Day, so… 00:12:08.000 --> 00:12:13.000 Um, jump on that if you'd like to help out and provide some feedback. 00:12:13.000 --> 00:12:17.000 And then, hot off the presses, Steph Buck is looking for 00:12:17.000 --> 00:12:24.000 Some folks to help out with, um, answering questions about SMS messaging, which she's having time to turn her attention to. 00:12:24.000 --> 00:12:32.000 Which I'm very excited about. There was several folks who said they were interested, so she suggested a little subgroup. 00:12:32.000 --> 00:12:38.000 Um, her estimate is just a couple of meetings to talk about workflows, and then… 00:12:38.000 --> 00:12:43.000 Another meeting after she has a chance to write things up to just give feedback on that. 00:12:43.000 --> 00:12:49.000 So, if anyone is interested in that, throw your name in the chat, and I will collect those names, and… 00:12:49.000 --> 00:12:55.000 let her, um, put something together. 00:12:55.000 --> 00:13:03.000 Anything else? Announcement-wise, administrivia-wise? 00:13:03.000 --> 00:13:08.000 Okay, then I will hand it over to Martina, who's joining us today. 00:13:08.000 --> 00:13:14.000 to talk about prioritization. This has been a long overdue invitation that we finally extended to her. 00:13:14.000 --> 00:13:17.000 Um, Martina, we have not been… 00:13:17.000 --> 00:13:19.000 doing nothing. I want you to know, we… 00:13:19.000 --> 00:13:24.000 We decided last January that we would start… by last January, I mean 2025. 00:13:24.000 --> 00:13:30.000 That we would start by going through all of our open JIRA tickets to try to get them into better shape, 00:13:30.000 --> 00:13:36.000 not really… really just to decide what to close and what to keep, what needed more refinement. 00:13:36.000 --> 00:13:39.000 before we prioritized, and now we're… 00:13:39.000 --> 00:13:44.000 coming to the close of that, and now we're ready to turn our attention to prioritization. 00:13:44.000 --> 00:13:45.000 So, welcome. 00:13:45.000 --> 00:13:50.000 Thank you. Thanks for inviting me, and I mean, that makes perfect sense to first 00:13:50.000 --> 00:13:55.000 look at the JIRA tickets and then start the prioritization process and vote. 00:13:55.000 --> 00:13:58.000 Um, I will speak… 00:13:58.000 --> 00:14:07.000 merely, um, about how we do it in ERM thick. Um, I'm the convener for, but I think the acquisition stake has a very similar process. 00:14:07.000 --> 00:14:09.000 to the one that URMSEC has. 00:14:09.000 --> 00:14:13.000 And I thought I would briefly… 00:14:13.000 --> 00:14:15.000 Um… 00:14:15.000 --> 00:14:19.000 Yeah, um, maybe show you 4 slides to… 00:14:19.000 --> 00:14:26.000 go through the process as an overview, and then maybe we can look at our individual pages and look at how we do it. 00:14:26.000 --> 00:14:34.000 And if, um, you already know specific things, um, or whatever, if you have questions, just let me know, and… 00:14:34.000 --> 00:14:36.000 say that. 00:14:36.000 --> 00:14:43.000 So, um, the four slides I wanted to present to describe the overall process. 00:14:43.000 --> 00:14:47.000 So in ERAMSIC, um, we have an implementer's Topics page. 00:14:47.000 --> 00:14:53.000 Uh, where everyone in the community can add topics to, and topics means 00:14:53.000 --> 00:15:00.000 requirements, wishes. They may be very small and tiny, just adding one further 00:15:00.000 --> 00:15:12.000 pick list value to a hard-coded list, for instance, or it may be something like, please add the checklist support that's available in open access app to the ERAM apps, for instance. So that's a larger package. 00:15:12.000 --> 00:15:17.000 Um, everyone, um, can add to, um, 00:15:17.000 --> 00:15:19.000 the ERM implementers list. 00:15:19.000 --> 00:15:30.000 That's valid for the ERAMSIG and some subgroups, and they're another subgroup has a specific one, so we work with, like, two implementers' topics lists. 00:15:30.000 --> 00:15:37.000 And, uh, these topics that I added to this list will be discussed in our SIG or subgroups. 00:15:37.000 --> 00:15:43.000 depends on where they belong to. So it's… if it's an e-usage topic, it will be discussed in the e-usage subgroup. 00:15:43.000 --> 00:15:48.000 But everything that's added will be discussed first. 00:15:48.000 --> 00:15:57.000 Um, and that means that people who have provided the topic can explain why they need it, give use cases, others can ask questions, agree or disagree, 00:15:57.000 --> 00:16:05.000 And especially the product owner learns about the requirement and can check as well whether he or she understands the issue. 00:16:05.000 --> 00:16:08.000 Um, and then, after this discussion, 00:16:08.000 --> 00:16:15.000 Um, either the product owner will create a Jira ticket for the implementer's topics, and the new requirement, 00:16:15.000 --> 00:16:21.000 Or we may have another meeting because the PO brings, like, some mock-ups. 00:16:21.000 --> 00:16:30.000 design proposals or, like, other, um, other input that needs discussion before we can add a JIRA ticket. 00:16:30.000 --> 00:16:41.000 And, um, then the product owner in our case creates the Jira tickets. This may vary from SIG to SIG. In our case, the product owner creates the JIRA tickets, 00:16:41.000 --> 00:16:51.000 And every Jira ticket that's created from this implementers list gets a specific label, and that's ERAMSICT topics. 00:16:51.000 --> 00:16:53.000 And so, um, because… 00:16:53.000 --> 00:17:03.000 We have this label, we can create a JIRA dashboard on ERAMSIC topics that are for ranking, or for voting. 00:17:03.000 --> 00:17:08.000 And this dashboard lists the different tickets by votes. 00:17:08.000 --> 00:17:12.000 Um, as you can see, like, here. 00:17:12.000 --> 00:17:24.000 Um, exactly. And so everyone who wants to help prioritizing ERM features can go to this dashboard and just walk themselves through the list, and 00:17:24.000 --> 00:17:29.000 at their votes to the different tickets, and how that goes, maybe we can look at… 00:17:29.000 --> 00:17:36.000 Afterwards. Um, and then, um, this prioritization is on one hand, done for the 00:17:36.000 --> 00:17:41.000 From unity priorities dashboard that's created by the Product Council. 00:17:41.000 --> 00:17:44.000 Um, and we have decided that 00:17:44.000 --> 00:17:52.000 Like, we will split our priorities across the different teams, because the subgroups represent different development teams. 00:17:52.000 --> 00:17:57.000 We are allowed to give five priorities, and we have 4 different areas. 00:17:57.000 --> 00:18:04.000 a focus, so we have said, okay, the priority one is the one that comes from the ERM SIG, 00:18:04.000 --> 00:18:16.000 The priority, too, comes from the e-holding subgroup, Priority 3 from the e-usage subgroup, and 4 from the Agreements Locer KB subgroup. That may be different, for instance, acquisitions has no re-subgroups. 00:18:16.000 --> 00:18:19.000 They just do, I think, one priority list. 00:18:19.000 --> 00:18:24.000 And the last one is a joint one across our groups, um, where we decide as a team 00:18:24.000 --> 00:18:27.000 what the priority 5 is. 00:18:27.000 --> 00:18:40.000 But, um, apart from that, we use the list for the different development teams' prioritization as well, so it has two goals. The one is the Community Priorities Dashboard by PC, 00:18:40.000 --> 00:18:43.000 But for the different development teams, it helps. 00:18:43.000 --> 00:18:47.000 to have this voting and prioritization 00:18:47.000 --> 00:18:55.000 So that they can pick tickets when they have spare time, they immediately know which one is the one that's the most needed by everyone. 00:18:55.000 --> 00:19:04.000 And, um, in this presentation is just… we have some JIRA dashboards and JIRA links, and we have some conference pages 00:19:04.000 --> 00:19:08.000 But I think I can go now, um, directly to… 00:19:08.000 --> 00:19:11.000 Maybe our implementers. 00:19:11.000 --> 00:19:20.000 page, and show you maybe some details, how we deal the statuses. I just want to pause briefly, if you have already some questions, or… 00:19:20.000 --> 00:19:29.000 Anything I should focus on? 00:19:29.000 --> 00:19:35.000 If that's not the case, then let's go directly to our implementers page. 00:19:35.000 --> 00:19:44.000 Um, I know that not all Sikhs have such an implementer's topics page, uh, Irem has, and the acquisition SIG has as well. 00:19:44.000 --> 00:19:49.000 Um, this is really a page where everyone can add their wishes. And in our ERM, 00:19:49.000 --> 00:19:56.000 case, we have, like, two tables on this page. There is one table. 00:19:56.000 --> 00:20:00.000 Where people can add their new topics that haven't been discussed yet. 00:20:00.000 --> 00:20:09.000 And the second table is, um, lists all the topics that have been discussed in our URAMSIC, or one of the subgroups. 00:20:09.000 --> 00:20:14.000 And what is given in this table is, like, the app's name, because, like, ERAM 00:20:14.000 --> 00:20:17.000 isn't represented only by one app. 00:20:17.000 --> 00:20:23.000 the brief topic, um, and then the description, or some use cases. 00:20:23.000 --> 00:20:26.000 We have a discussion status. 00:20:26.000 --> 00:20:32.000 Um, and I can show you in a second what different statuses we do have there. 00:20:32.000 --> 00:20:38.000 Uh, the date added, who provided the topic, interested parties can just list themselves as well. 00:20:38.000 --> 00:20:42.000 Then we have a link to the discussion, the meeting minutes, 00:20:42.000 --> 00:20:50.000 And in the last column, we have the JIRA ticket linked. So whenever the PO has created a JIRA ticket, it's listed here as well. 00:20:50.000 --> 00:20:56.000 And it's the status of the JIRA ticket, and that's important, is different from the discussion status. 00:20:56.000 --> 00:20:59.000 Because it can be, like, 00:20:59.000 --> 00:21:03.000 Through the SIC, and we are done with it, that means, for instance, for voting. 00:21:03.000 --> 00:21:07.000 we… the SIP itself will not do anything with this anymore. 00:21:07.000 --> 00:21:18.000 Um, but the status on the ticket says draft, because everything that now happens will happen in Jira, so people can now go into JIRA and vote for this ticket. 00:21:18.000 --> 00:21:25.000 What statuses do we have? Um, we have the one that says open all new items that haven't been discussed. 00:21:25.000 --> 00:21:29.000 have the status open, some, um, tickets or… 00:21:29.000 --> 00:21:34.000 topics may be blocked because we need more information. 00:21:34.000 --> 00:21:42.000 Before we can continue in progress means it's still in discussion, PO is doing mock-ups, and we need to decide on a specific 00:21:42.000 --> 00:21:45.000 like, mock-up or process. 00:21:45.000 --> 00:21:58.000 For voting means the SIGH has agreed, and it will be done, and there is a ticket for it that we can vote on. Enclosed can mean it's done, um, ticket is done, and development is done, or may even mean 00:21:58.000 --> 00:22:02.000 We have discussed, but we won't do, because it's not possible, or whatever. 00:22:02.000 --> 00:22:04.000 So these are the different, um… 00:22:04.000 --> 00:22:06.000 discussion started to cease. 00:22:06.000 --> 00:22:11.000 We have a brief description of how people can add their topics. 00:22:11.000 --> 00:22:14.000 And we have, as well, um, here, um, a… 00:22:14.000 --> 00:22:21.000 page where we tell how to prioritize ERM implementers' topics in Jira that you need in a… 00:22:21.000 --> 00:22:25.000 an Atlassian account, and so on and so forth. 00:22:25.000 --> 00:22:32.000 On the right side here, we have a glimpse at the list in Jira, and if we look at this ERAMSIC topics, 00:22:32.000 --> 00:22:43.000 Then we go to the page that I've already opened. That's our dashboard, where we list all the tickets that have been created out of these implementers topics. 00:22:43.000 --> 00:22:52.000 They all have this ERM-Sig-topics label, and they are, um, sorted by votes. So the highest votes 00:22:52.000 --> 00:22:59.000 appear highest in the list. And that's, for instance, in our case, the agreements export multiple agreements to CSV. 00:22:59.000 --> 00:23:02.000 Um, and if we now look at this ticket… 00:23:02.000 --> 00:23:08.000 everyone at this top right corner, um, should have this vote option. 00:23:08.000 --> 00:23:10.000 You can see this thump up. 00:23:10.000 --> 00:23:14.000 And if you click on that, you should be able to… 00:23:14.000 --> 00:23:18.000 Now, where is it? I don't see it here, because I have so many. 00:23:18.000 --> 00:23:22.000 Towards in my way. 00:23:22.000 --> 00:23:34.000 There we go. So, um, I have voted for this, I can remove my vote, and, um, if I want to vote on something, I can just add my vote for this new feature, and then, um, by that, 00:23:34.000 --> 00:23:41.000 I have done my job in JIRA, and I have voted for this ticket, for instance. And the more people vote for this in this top right corner, 00:23:41.000 --> 00:23:43.000 the higher it is in the list. 00:23:43.000 --> 00:23:50.000 That doesn't mean necessarily in ERM that this is done immediately after voting, so I'm not sure 00:23:50.000 --> 00:23:52.000 like, other 6 may go… 00:23:52.000 --> 00:23:58.000 go with this in a different way. Um, I know that it's the same in AcquisitionSig. 00:23:58.000 --> 00:24:02.000 Because the priorities list is usually something that's 00:24:02.000 --> 00:24:08.000 decided on… before a release, maybe a month ahead. 00:24:08.000 --> 00:24:19.000 Um, it's often decided by the funding institution and, um, the funding institution picks community priorities as well, but it's not necessarily that only this list 00:24:19.000 --> 00:24:24.000 like, decides on what will be done and what will be developed, but… 00:24:24.000 --> 00:24:29.000 I think we have more and more requirements, and the backlog of JIRA tickets grows. 00:24:29.000 --> 00:24:44.000 And grows and grows. And every time the development team has some spare time, it's important that they can immediately pick something that they can do, because in our case, they would need to wait, like, 2 weeks or even 4 weeks until the group meets next. 00:24:44.000 --> 00:24:50.000 And if they need to wait for that period, and then talk with us about what do you want to have 00:24:50.000 --> 00:24:59.000 done first, that would take too much time, and maybe then they even don't have any spare time anymore. So, that's why it's important for the development team that there's 00:24:59.000 --> 00:25:04.000 prioritization is there whenever they have time to pick something up. 00:25:04.000 --> 00:25:06.000 And that's, um, possible 00:25:06.000 --> 00:25:10.000 by doing this voting. 00:25:10.000 --> 00:25:18.000 So that's that. That's the Jira, and if we look back at how to prioritize… 00:25:18.000 --> 00:25:21.000 Um, yeah, what you need is an Atlassian account. 00:25:21.000 --> 00:25:28.000 So that you, um, yeah, and you can set up an account using this link. We have this how-to page in ERAM. 00:25:28.000 --> 00:25:39.000 And then you can navigate to the JIRA dashboard, or do a search by yourself on, like, the label that you decide should be the one that lists all votable tickets. 00:25:39.000 --> 00:25:42.000 In our case, it's ERM-Sick Topics. 00:25:42.000 --> 00:25:50.000 Then you can vote on the issues by, um, yeah, selecting the ticket you would like to prioritize and clicking this thumb-up button. 00:25:50.000 --> 00:25:53.000 Um, yeah. And then… 00:25:53.000 --> 00:26:00.000 um… sometimes, in our case, because we base our prioritization on this implementers list, 00:26:00.000 --> 00:26:12.000 Um, there may be tickets that don't have the label ERAMSIC topics, but that's something that people can bring back to the SIC, to the PO, or to me as a convener, and then we can discuss in the 00:26:12.000 --> 00:26:20.000 and the sake and, um, add the label to the ticket nevertheless, so that it is votable, for instance. 00:26:20.000 --> 00:26:24.000 And, um, this dashboard that comes out of it. 00:26:24.000 --> 00:26:38.000 And that we've just looked at is something, as mentioned, that's not all… or only something that will influence the PC priorities or the community priorities, I should say, that live under the PC. 00:26:38.000 --> 00:26:50.000 But that's something that really influencers the development for the different teams, because every team, and that's where the development team is listed here as well, can pick their highest priorities as well, and then 00:26:50.000 --> 00:26:54.000 do them. And everyone can follow 00:26:54.000 --> 00:27:01.000 what the status is of this ticket, and is we… everyone can be kept informed. 00:27:01.000 --> 00:27:04.000 Yeah, and I think that's our… 00:27:04.000 --> 00:27:10.000 prioritization process, um, the one thing that I have, um, 00:27:10.000 --> 00:27:21.000 that I could show, but you will know is the Community Priorities Dashboard, where you can see here our top 5 priorities that have been listed. 00:27:21.000 --> 00:27:29.000 based on this process that we have in our SIG. 00:27:29.000 --> 00:27:31.000 was that, um… 00:27:31.000 --> 00:27:39.000 Yeah, do you have any questions? Was that clear, how our process goes? 00:27:39.000 --> 00:27:40.000 I see you nodding. 00:27:40.000 --> 00:27:48.000 That was incredibly clear, and very impressive how organized that whole thing is. Thank you so much, Martina. 00:27:48.000 --> 00:27:51.000 That is stunning, how… 00:27:51.000 --> 00:27:56.000 not just clear it is, but how clear it is how others can vote, and… 00:27:56.000 --> 00:27:59.000 to your own people, and then explaining it to us. 00:27:59.000 --> 00:28:04.000 Um, I… it's interesting, I think there are some things we can definitely take away from this. 00:28:04.000 --> 00:28:09.000 I think one of the challenges for the RACIG 00:28:09.000 --> 00:28:11.000 is, um… 00:28:11.000 --> 00:28:13.000 that we have literally, like, 00:28:13.000 --> 00:28:22.000 500 open tickets. Like, we have so many tickets, so starting from, like, I have this idea, and then going… walking it all the way through. 00:28:22.000 --> 00:28:27.000 We sort of already have this huge corpus of ideas and JIRA tickets that… 00:28:27.000 --> 00:28:32.000 we need to figure out how to wrangle. But I do think there are definitely ways we can 00:28:32.000 --> 00:28:37.000 translate and adapt some of the processes you've used. 00:28:37.000 --> 00:28:41.000 Um, to our scenario. So I'll need to be talking to Katie, um, 00:28:41.000 --> 00:28:45.000 remind my co-convener, and we'll have to strategize how we're gonna… 00:28:45.000 --> 00:28:47.000 figure out how to roll this out. 00:28:47.000 --> 00:28:51.000 Um, and apply it to our own unique 00:28:51.000 --> 00:28:53.000 scenario here in RA. 00:28:53.000 --> 00:28:56.000 Um, one question I have that I think is… 00:28:56.000 --> 00:28:59.000 different than what our structure here. 00:28:59.000 --> 00:29:02.000 Um, we do… 00:29:02.000 --> 00:29:05.000 It's curious that you have an ERM implementer's 00:29:05.000 --> 00:29:09.000 group, and I want to hear a little bit about how those two… 00:29:09.000 --> 00:29:16.000 are differentiated in how they function. Like, is that a group that meets separately from the ERM-SIG? 00:29:16.000 --> 00:29:19.000 And… or is it just, uh, kind of… 00:29:19.000 --> 00:29:22.000 virtually, you are all the people who are implementing 00:29:22.000 --> 00:29:24.000 implemented who have ERM. 00:29:24.000 --> 00:29:34.000 Yeah, exactly, and I mean, maybe we could even rename that page, because it… I think it's called ERAM Implementers Page 00:29:34.000 --> 00:29:44.000 Because it has been created a very long time ago. Everyone really can add their topics and can discuss with us, even if they haven't yet implemented Folio. 00:29:44.000 --> 00:29:47.000 Um, it's just that we, from time to time, really 00:29:47.000 --> 00:29:57.000 um, spend time on these tickets. We have other meetings as well, where the product owner discusses other things with the group, where new development is shown, 00:29:57.000 --> 00:30:03.000 like, the… maybe UATs are described, but we really come back 00:30:03.000 --> 00:30:14.000 regularly to these topics, because otherwise they would add on and on and on. And I mean, you see on our implementers page already that we have a lot of open discussion topics. 00:30:14.000 --> 00:30:25.000 So, so that's really… when we see we have now a good bunch of new topics, then we would discuss those in the… in the usual ERAM SEC, or one of the subgroups, 00:30:25.000 --> 00:30:30.000 where they belong to. 00:30:30.000 --> 00:30:43.000 And, um, we have more tickets in Jira as well. We really reduced the number of votables by adding this Eremic Topics label. That could be different, but that's really our way to say this is the 00:30:43.000 --> 00:30:52.000 like, list of things that you can vote on, and if you want to add more from the rest of the ticket, then please contact us, and we can maybe add that label, too. 00:30:52.000 --> 00:30:57.000 Yeah. 00:30:57.000 --> 00:30:58.000 Yeah. 00:30:58.000 --> 00:30:59.000 Do you have ERM tickets that are in there that don't have that label? Like, that didn't come from the SIG? Okay. 00:30:59.000 --> 00:31:07.000 Yeah, yeah. 00:31:07.000 --> 00:31:18.000 other questions that folks have? 00:31:18.000 --> 00:31:21.000 And yeah. 00:31:21.000 --> 00:31:29.000 Um, how is the voting recorded in Jira? Is this a specific field or specific function that is used for that? 00:31:29.000 --> 00:31:35.000 Yes, that's… forgive me one second, I will share my screen again, and maybe… 00:31:35.000 --> 00:31:40.000 Let me find the e-holdings one, because… 00:31:40.000 --> 00:31:44.000 Uh, yeah, exactly. So you should see the ticket now. 00:31:44.000 --> 00:31:51.000 Um, yeah, you do. And in the top right corner, you really have this thumb-up option. 00:31:51.000 --> 00:31:57.000 And if you click on that, and why is it sometimes displaying correctly and sometimes not? Now it's better. 00:31:57.000 --> 00:32:03.000 Um, you see the list of people who have voted for this ticket, but that's something, I mean, 00:32:03.000 --> 00:32:11.000 Um, for me as now voting person, that's not maybe relevant. And I can vote by clicking on vote for this epic in this case. 00:32:11.000 --> 00:32:14.000 And then my vote is added. 00:32:14.000 --> 00:32:18.000 Um, yeah, and that's something that then can be… 00:32:18.000 --> 00:32:30.000 used for sorting the tickets in a list on a dashboard, for instance, or if you look on the NVIDIAL ticket, you can see the number of thumbs, and that's the number of votes. 00:32:30.000 --> 00:32:35.000 And it's not restricted, maybe that's something that is… 00:32:35.000 --> 00:32:37.000 good information as well. 00:32:37.000 --> 00:32:40.000 Um, it's not restricted. 00:32:40.000 --> 00:32:44.000 But in our SIG, and I know in acquisitions as well, it works. 00:32:44.000 --> 00:32:52.000 that not, like, 100 people from one organization vote on one ticket because they want to, like, push that. That works. 00:32:52.000 --> 00:32:58.000 And what the product owners always say is they can see, like, if you look at the list, you can see 00:32:58.000 --> 00:33:05.000 Um, who voted on it, and if there is a lot of people from my institution, for instance, they know, okay, VZG needs it, but 00:33:05.000 --> 00:33:10.000 do others need it as well? We thought about restricting that, 00:33:10.000 --> 00:33:18.000 Um, but that's not easy, uh, so… and we said everyone within Atlassian account is allowed to vote. 00:33:18.000 --> 00:33:21.000 And, um, people should be, yeah, 00:33:21.000 --> 00:33:28.000 should try not to, uh, trick out the system, but vote per institution. 00:33:28.000 --> 00:33:35.000 Does that explain your, um, answer your question, Anya? Oh, was that a different one? 00:33:35.000 --> 00:33:45.000 No, that actually was the question, so… but is that something that had to be activated specifically for you, or is that the standard functionality you simply employ for doing that? 00:33:45.000 --> 00:33:47.000 Yeah, it's… it should be there. 00:33:47.000 --> 00:33:48.000 For everyone, yeah. 00:33:48.000 --> 00:33:52.000 Mm-hmm. 00:33:52.000 --> 00:33:55.000 So it sounds like it's essentially… 00:33:55.000 --> 00:33:57.000 honor system… 00:33:57.000 --> 00:34:03.000 that one representative will vote for her institution. 00:34:03.000 --> 00:34:05.000 That seems like a reasonable… 00:34:05.000 --> 00:34:11.000 expectation. And because it's so transparent, it would be pretty obvious if somebody's really gaming the system. 00:34:11.000 --> 00:34:19.000 And some institutions even said, okay, we are such a large institution, and there may be different votes from, like, the journalist department and the 00:34:19.000 --> 00:34:24.000 Resource Access Department, whatever, so it may be okay if multiple people vote, but 00:34:24.000 --> 00:34:32.000 Um, like, no, that didn't really happen in our scenario, so that really worked out. 00:34:32.000 --> 00:34:37.000 And it should be lightweight, and not too complicated, and that really 00:34:37.000 --> 00:34:55.000 is doable via this voting process from my perspective. 00:34:55.000 --> 00:35:03.000 Other questions… 00:35:03.000 --> 00:35:08.000 For Martina, or thoughts about… 00:35:08.000 --> 00:35:12.000 thoughts… initial thoughts about, sort of, how 00:35:12.000 --> 00:35:14.000 this could… 00:35:14.000 --> 00:35:18.000 work in the resource access. 00:35:18.000 --> 00:35:26.000 Sig, knowing how many tickets we have. 00:35:26.000 --> 00:35:29.000 Yeah, Cornelia. 00:35:29.000 --> 00:35:44.000 Um, we should… we could maybe try to revert the process and vote… not vote for what is most… what the developers should pick up first, but for what we should start to refine first. 00:35:44.000 --> 00:35:54.000 Alright. I'm not sure, maybe… develop parallel structures for like. 00:35:54.000 --> 00:35:59.000 So, we don't have that many tickets that are ready for Dev. 00:35:59.000 --> 00:36:03.000 At this moment, so developers could choose from them. 00:36:03.000 --> 00:36:08.000 And start reflecting voting for what to refine, and the more we get refined. 00:36:08.000 --> 00:36:24.000 We could switch to… to what yeah, what? What should be developers priorities. 00:36:24.000 --> 00:36:40.000 I think my mind wrapped itself around exactly the same thing. We have to… we have to have a two-step process, but we don't want to have, like, two different ways of voting for it. So how can we use one and the same. 00:36:40.000 --> 00:36:50.000 For taking exactly the steps that Cornelia put there right away. We need to refine first and get things ready for development, prioritized in some way, and then. 00:36:50.000 --> 00:37:06.000 development needs an idea of the importance as well. And I was wondering exactly the same thing. Would it work if we use this really lightweight approach which I really, really like. It's very simple. It's very self-explanatory. 00:37:06.000 --> 00:37:07.000 I really like that. Would that work for us to go through this process of refining, adding new steps on an ongoing process? 00:37:07.000 --> 00:37:21.000 Anya? 00:37:21.000 --> 00:37:29.000 Yeah, well, I really like the way that Martina described, sort of, that not all tickets are available for voting at all times, right? 00:37:29.000 --> 00:37:35.000 So, even if we are looking at tickets that need refinement, 00:37:35.000 --> 00:37:43.000 We don't have to necessarily open all tickets for voting at the sale. Like, I don't think that would be successful. I think that telling… 00:37:43.000 --> 00:37:45.000 the community to vote for 500 tickets. 00:37:45.000 --> 00:37:49.000 is a non-starter. I mean, it throws me back to, like, 00:37:49.000 --> 00:37:54.000 What features do you need in MVP in order to go live? Like, 00:37:54.000 --> 00:37:57.000 those spreadsheets were mind-boggling. 00:37:57.000 --> 00:38:02.000 So, I don't think that's a viable… 00:38:02.000 --> 00:38:05.000 The question is how to get from… 00:38:05.000 --> 00:38:08.000 the number of tickets we have now in various states. 00:38:08.000 --> 00:38:12.000 to how does… how could we start? 00:38:12.000 --> 00:38:17.000 voting. Um, we could also have two dashboards, right? You could have a dashboard for… 00:38:17.000 --> 00:38:22.000 the prioritization of things that need refinement, and then the prioritization of things that are ready… dev-ready. 00:38:22.000 --> 00:38:29.000 Um, that are assigned to a dev team. 00:38:29.000 --> 00:38:56.000 I wonder if we could… have similarly to… The other 6, we have areas, right? Sort of, like… Um… fines and checkouts and, um… Um, noises and such. So maybe come up with a few of those areas that would divide. 00:38:56.000 --> 00:39:04.000 The tickets automatically, and then maybe concentrate on one. 00:39:04.000 --> 00:39:05.000 And, uh, area and. That might make it a bit easier, but still it's going to be like probably 50, 70 tickets. 00:39:05.000 --> 00:39:18.000 Olga? 00:39:18.000 --> 00:39:23.000 So I don't know after that. 00:39:23.000 --> 00:39:26.000 That's a good suggestion, Olga. The… 00:39:26.000 --> 00:39:31.000 If you remember the first, when we were looking through the Vega and the Valaris open tickets, 00:39:31.000 --> 00:39:34.000 We did that. We sort of… 00:39:34.000 --> 00:39:40.000 But, like, the 150 were too many to look at, and we sort of were like, let's look at requests today. 00:39:40.000 --> 00:39:41.000 Um, and that is another… that's definitely a way we can think about breaking it down. 00:39:41.000 --> 00:39:52.000 Hmm. 00:39:52.000 --> 00:40:08.000 Other thoughts? 00:40:08.000 --> 00:40:12.000 All right. Well, we will con… oh, Anya, you got another one. 00:40:12.000 --> 00:40:13.000 No mistake! Or you gotta… no, you got it. 00:40:13.000 --> 00:40:29.000 Yeah, no, not a mistake. I mean, we have been starting to discuss this when we looked at the old tickets as well, and I… I still really, really like this idea of kind of dividing it up by grouping the tickets to related. 00:40:29.000 --> 00:40:44.000 tickets and areas, because I feel that this will be helpful to also link separate tickets together, like how they relate to each other, because I feel that if we get a group of tickets that are related to each other. 00:40:44.000 --> 00:40:55.000 Development ready at the same time, the chances are higher that tickets are picked up together because a developer needs to look into a certain area anyway. 00:40:55.000 --> 00:41:21.000 So, I think that would be a good approach, given the huge number of tickets we have, so… We would have to discuss a way to kind of decide as a whole SIG on how to prioritize our areas of functionalities to start with. And I think there are very different pain points in different institutions. So I don't know how to. 00:41:21.000 --> 00:41:24.000 How to approach that. 00:41:24.000 --> 00:41:30.000 Yeah, for sure. I mean, I think our gap list is a good place to start, because the gap list is already a 00:41:30.000 --> 00:41:32.000 sort of a… 00:41:32.000 --> 00:41:37.000 a place where people have proactively said, these are things we want to have. 00:41:37.000 --> 00:41:40.000 And that is sort of a… one… 00:41:40.000 --> 00:41:43.000 way around, um, looking at 00:41:43.000 --> 00:41:45.000 the particular things that people have… 00:41:45.000 --> 00:41:49.000 identified as priorities already, in some respects. 00:41:49.000 --> 00:41:53.000 So that's one way. And I do think you're right, Anya, that 00:41:53.000 --> 00:41:55.000 spending some time… 00:41:55.000 --> 00:42:00.000 clustering these and making sure the relationships are together. 00:42:00.000 --> 00:42:04.000 in the ticket is helpful, um, because, you're right, there… 00:42:04.000 --> 00:42:07.000 it's much easier to develop within 00:42:07.000 --> 00:42:10.000 you know, 3 or 4 things that are related. 00:42:10.000 --> 00:42:12.000 Um, and sometimes it can… 00:42:12.000 --> 00:42:19.000 can reveal, sort of, better strategies when you know all of the problems in one place. 00:42:19.000 --> 00:42:31.000 That's a good idea. 00:42:31.000 --> 00:42:36.000 Martina, are you able to share the slides in the agenda? 00:42:36.000 --> 00:42:41.000 Thank you. If you can just link it to the agenda item, you can do that, or you can pop a link in the… 00:42:41.000 --> 00:42:44.000 Chad and I can do it either way. 00:42:44.000 --> 00:42:47.000 Thank you. 00:42:47.000 --> 00:42:50.000 other… 00:42:50.000 --> 00:43:02.000 thoughts about process. 00:43:02.000 --> 00:43:04.000 All right, well, I think this is a really good start, and I'm really excited. 00:43:04.000 --> 00:43:09.000 about how we can think about moving forward with some of these. 00:43:09.000 --> 00:43:10.000 Um… 00:43:10.000 --> 00:43:12.000 We do, yeah. 00:43:12.000 --> 00:43:17.000 Thank you, Martina, so much for coming. I know it's long overdue, but it was well worth it. Well worth the wait! 00:43:17.000 --> 00:43:20.000 Thanks for having me, thank you. 00:43:20.000 --> 00:43:23.000 Yeah, okay, thanks. 00:43:23.000 --> 00:43:27.000 Alright, well, we will turn our attention to… 00:43:27.000 --> 00:43:30.000 our draft, um… 00:43:30.000 --> 00:43:34.000 review of… I mean, reviewing our draft description. 00:43:34.000 --> 00:43:37.000 There's a link in the agenda… 00:43:37.000 --> 00:43:41.000 to the description, and… 00:43:41.000 --> 00:43:46.000 Let's see… need to go to it… 00:43:46.000 --> 00:43:51.000 So, if folks want to take a look… 00:43:51.000 --> 00:43:57.000 Um… 00:43:57.000 --> 00:44:03.000 So, full disclosure, I used AI to help draft this, because I ran out of time to do it myself. 00:44:03.000 --> 00:44:08.000 Um, and so I would love for folks to… 00:44:08.000 --> 00:44:11.000 Take a look… 00:44:11.000 --> 00:44:15.000 there's not… first of all, this is not like… 00:44:15.000 --> 00:44:23.000 high stakes. This is very, like, very low stakes. The reason we want to rewrite it is because the description that was on… 00:44:23.000 --> 00:44:25.000 that is currently on our website. 00:44:25.000 --> 00:44:28.000 Um, is… 00:44:28.000 --> 00:44:33.000 very much related to when we were building a system from whole cloth. 00:44:33.000 --> 00:44:36.000 So it talks about, you know, 00:44:36.000 --> 00:44:41.000 writing requirements and things like that that are about… 00:44:41.000 --> 00:44:46.000 A system that is not yet built, as opposed to a system that is built and is being maintained. 00:44:46.000 --> 00:44:49.000 enhanced, further developed. 00:44:49.000 --> 00:44:52.000 So that's why this, um… 00:44:52.000 --> 00:44:54.000 This list is… 00:44:54.000 --> 00:44:57.000 or the refinement is required, or… 00:44:57.000 --> 00:45:02.000 Seems necessary. To be able to signal to other 00:45:02.000 --> 00:45:04.000 folks who are maybe 00:45:04.000 --> 00:45:10.000 Considering joining the SIG, to know what it is that we do. 00:45:10.000 --> 00:45:13.000 So David suggested adding calendars, I think that… 00:45:13.000 --> 00:45:16.000 Makes sense. Um… 00:45:16.000 --> 00:45:18.000 Are there… 00:45:18.000 --> 00:45:20.000 Other thoughts? 00:45:20.000 --> 00:45:26.000 about this. I'll give folks a minute to read it. 00:45:26.000 --> 00:45:32.000 I was just maybe thinking when talking about cross-app functions, maybe user management, 00:45:32.000 --> 00:45:36.000 mentioning that, since there's a lot of crossover. 00:45:36.000 --> 00:45:45.000 Yeah. It was… I was considering adding some, you know, individual ones, and then I was like, well, then we gotta add this, and this, and this. 00:45:45.000 --> 00:45:46.000 Okay. 00:45:46.000 --> 00:45:47.000 But you're right, I do feel like the user management 00:45:47.000 --> 00:45:49.000 connection is much stronger than… 00:45:49.000 --> 00:45:53.000 I mean, it's sort of foundational to… 00:45:53.000 --> 00:45:56.000 what we do, I… I think. 00:45:56.000 --> 00:46:23.000 Um… 00:46:23.000 --> 00:46:29.000 You could put a catch all general circulation issues or, um. 00:46:29.000 --> 00:46:35.000 Developments. Did I catch anything we might be… might not have mentioned there? 00:46:35.000 --> 00:46:37.000 Which part do you mean, Scott? 00:46:37.000 --> 00:46:44.000 I was saying is at the end of the list, a kind of a catch-all statement saying for general circulation issues related to folio. 00:46:44.000 --> 00:46:47.000 It'd be kind of a catch-all for anything else not covered there. 00:46:47.000 --> 00:47:17.000 Gotcha. 00:47:33.000 --> 00:47:40.000 I'm looking back at the notes from February 9th, which I included… I… 00:47:40.000 --> 00:47:44.000 That's where we discussed this, so if anybody wants to see, sort of, what… 00:47:44.000 --> 00:47:48.000 We discussed at that meeting, I can… 00:47:48.000 --> 00:47:51.000 Throw that in here. 00:47:51.000 --> 00:47:57.000 Um, I actually did take notes at this one. 00:47:57.000 --> 00:48:01.000 These are real notes, not AI notes. 00:48:01.000 --> 00:48:05.000 Um, that's where the suggestion about making the bulleted list came up. 00:48:05.000 --> 00:48:08.000 Um… 00:48:08.000 --> 00:48:10.000 We had talked about adding 00:48:10.000 --> 00:48:15.000 multiple more things that were omitted, and then we'd also talked about, well, maybe we should… 00:48:15.000 --> 00:48:17.000 have… 00:48:17.000 --> 00:48:22.000 sort of a… not… rather than trying to make a laundry list of absolutely everything, 00:48:22.000 --> 00:48:25.000 sort of have larger catch-all 00:48:25.000 --> 00:48:29.000 um… thing, so it was… there was some sort of competing… 00:48:29.000 --> 00:48:56.000 ideas there. 00:48:56.000 --> 00:49:02.000 We could include… one of the things was, um… 00:49:02.000 --> 00:49:05.000 resource sharing and remote storage. 00:49:05.000 --> 00:49:07.000 Um… 00:49:07.000 --> 00:49:12.000 End user management sort of all fall into the category of… 00:49:12.000 --> 00:49:17.000 I mean, the problem is they don't all take the same form, so it's not… 00:49:17.000 --> 00:49:19.000 Um… 00:49:19.000 --> 00:49:22.000 it's not always collaborating with other… 00:49:22.000 --> 00:49:28.000 SIGS, it could be, you know, they could also be subgroups of our own SIG, so it's a little bit tricky to… 00:49:28.000 --> 00:49:32.000 Think about how to word that in a way that's accurate. 00:49:32.000 --> 00:49:47.000 Um… 00:49:47.000 --> 00:49:50.000 Well, if there are other, um… 00:49:50.000 --> 00:49:52.000 thoughts… 00:49:52.000 --> 00:49:57.000 Please add them as comments to the description, and I will… 00:49:57.000 --> 00:49:59.000 Um… 00:49:59.000 --> 00:50:02.000 take another pass at this, and then send it out. 00:50:02.000 --> 00:50:04.000 For final approval. 00:50:04.000 --> 00:50:07.000 Um… in the coming… 00:50:07.000 --> 00:50:10.000 days. I'll give it another week, we can look at it. 00:50:10.000 --> 00:50:16.000 um… oh, I guess we're not gonna meet for a couple weeks because of… 00:50:16.000 --> 00:50:19.000 Calming and holidaying. 00:50:19.000 --> 00:50:22.000 So, we will… when we next meet, we will… 00:50:22.000 --> 00:50:25.000 But the finishing touches on this, and then we can swap it out on the… 00:50:25.000 --> 00:50:33.000 On the wiki. There's not a formal approval process, I don't think, unless I'm missing something, Cornelia. 00:50:33.000 --> 00:50:39.000 I think this is just our description of ourselves. 00:50:39.000 --> 00:50:42.000 Alright. Any… 00:50:42.000 --> 00:50:51.000 thing else. 00:50:51.000 --> 00:50:58.000 Just a quick reminder, um… 00:50:58.000 --> 00:51:04.000 Implementer Sig has started the process of writing a survey. 00:51:04.000 --> 00:51:15.000 of that, it was the RA wanted to do the same thing, um, so it's possible they would like us to start looking at some of the questions we would like to have, if we wanted 00:51:15.000 --> 00:51:23.000 if it's general questions, have it as part of their survey, or if we want to have our own survey that goes out with theirs. 00:51:23.000 --> 00:51:27.000 I think we were hoping that we would… 00:51:27.000 --> 00:51:30.000 Um, be able to piggyback on the… 00:51:30.000 --> 00:51:33.000 that survey. So, um… 00:51:33.000 --> 00:51:39.000 I have seen that the implementers has… the meetings have been the survey subgroup. 00:51:39.000 --> 00:51:47.000 Um, would it be helpful, Tom, for one of us to go to a meeting, or do you… are you… obviously, are you going to those meetings? 00:51:47.000 --> 00:51:54.000 Yeah, I'm one of the conveners, but yeah, if somebody else wants to come, um, I think that would be helpful, too. 00:51:54.000 --> 00:51:55.000 Okay. 00:51:55.000 --> 00:51:59.000 As I said, they kind of want to know what direction we're going to. They don't want to try… they want to try to keep the… 00:51:59.000 --> 00:52:03.000 main survey from blowing up to this humongous thing. 00:52:03.000 --> 00:52:04.000 Mm-hmm. 00:52:04.000 --> 00:52:13.000 And I know before we said about that we wanted to get down to the nitty-gritty of, like, fine fees, like, are you using this functionality or this functionality, or this functionality? 00:52:13.000 --> 00:52:17.000 Um, so that might lean more towards a separate survey. 00:52:17.000 --> 00:52:20.000 But, um, yeah, I think having somebody come 00:52:20.000 --> 00:52:27.000 So that might help, uh, but it might also be something we want to talk about in this group as well, of what sort of questions you want. 00:52:27.000 --> 00:52:32.000 And what sort of detail we want to get down to. 00:52:32.000 --> 00:52:34.000 Um… 00:52:34.000 --> 00:52:39.000 What… do you know when the next meeting is, or is there a next meeting scheduled? 00:52:39.000 --> 00:52:52.000 I don't have to look, um… we've been using the, uh, planning board meeting for it, which would mean that it fall next Thursday, but I think that's off because of… 00:52:52.000 --> 00:52:53.000 calming. 00:52:53.000 --> 00:52:54.000 Calendar calming. 00:52:54.000 --> 00:53:00.000 Yeah, um, so I will look, and I can drop you a message in Slack. 00:53:00.000 --> 00:53:01.000 Sounds good. 00:53:01.000 --> 00:53:03.000 when it comes up, I'll drop you a message in Slack. 00:53:03.000 --> 00:53:08.000 Okay, if I'm able to come, I will try to come. I think, um… 00:53:08.000 --> 00:53:12.000 There are some pros and cons, I think, to… 00:53:12.000 --> 00:53:17.000 trying to, like… we have to figure out what is the actual goal of the survey. 00:53:17.000 --> 00:53:19.000 Um… 00:53:19.000 --> 00:53:24.000 I think the higher-level survey can get us a lot of information that we're trying to get, and… 00:53:24.000 --> 00:53:27.000 And then we need to think about the bang for the buck. 00:53:27.000 --> 00:53:30.000 of doing a separate survey, certainly. 00:53:30.000 --> 00:53:36.000 Um, and are there some higher level questions, higher level RA questions that we think we… 00:53:36.000 --> 00:53:38.000 would like to have in there. 00:53:38.000 --> 00:53:42.000 that could get us partway there. Um… 00:53:42.000 --> 00:53:46.000 or achieve some of the goals. So I want to circle back to what our initial… 00:53:46.000 --> 00:53:51.000 Goals were about that survey. This was the conversation that we primarily had at WolfCon. 00:53:51.000 --> 00:53:54.000 Um, if I remember correctly. 00:53:54.000 --> 00:53:55.000 Yes, yes. 00:53:55.000 --> 00:53:59.000 And so I can look back at that… those notes. Like, that was the topic of our WolfCon… 00:53:59.000 --> 00:54:02.000 Um, in-person, hybrid, whatever. 00:54:02.000 --> 00:54:05.000 Um, general RA SIG meeting. 00:54:05.000 --> 00:54:07.000 In September. So… 00:54:07.000 --> 00:54:09.000 I'll look back and see… 00:54:09.000 --> 00:54:16.000 that was where the idea of getting together with the implementer, SIG, and actually having a larger survey. 00:54:16.000 --> 00:54:18.000 Um, having one instead of… 00:54:18.000 --> 00:54:21.000 trying to survey all folio libraries simultaneously, twice. 00:54:21.000 --> 00:54:24.000 Right. 00:54:24.000 --> 00:54:31.000 Exactly. Um, and actually, as a plug for WolfCon, too, is the calls for proposals end on the 25th. 00:54:31.000 --> 00:54:32.000 So… 00:54:32.000 --> 00:54:40.000 Thank you. Thank you. Yes, so I was gonna say that I submitted a tick… I submitted one proposal for the general RAC. 00:54:40.000 --> 00:54:43.000 Meeting as a placeholder, so we will… 00:54:43.000 --> 00:54:46.000 do whatever topics, um, 00:54:46.000 --> 00:54:50.000 We have, at the time, but it's good to have a placeholder meeting. 00:54:50.000 --> 00:54:52.000 And then, um… 00:54:52.000 --> 00:54:57.000 I sent out the call on Slack, I'm not sure if anyone else has put anything out there. 00:54:57.000 --> 00:55:04.000 And then Katie and Cornelia were going to be looking into doing a workshop proposal. 00:55:04.000 --> 00:55:10.000 Can you give an update on that, either of you, about where you're at? 00:55:10.000 --> 00:55:18.000 Well, we… we did submit it. We went ahead and submitted it, and we started an outline and everything, so we're well on our way. 00:55:18.000 --> 00:55:20.000 to, um… 00:55:20.000 --> 00:55:21.000 Getting that done, so… 00:55:21.000 --> 00:55:24.000 Fantastic! Yay. 00:55:24.000 --> 00:55:27.000 Um, if there are any other… 00:55:27.000 --> 00:55:31.000 thoughts about if anybody is wanting to… 00:55:31.000 --> 00:55:35.000 submit a proposal for another… 00:55:35.000 --> 00:55:39.000 um, non-workshop, but just a session. 00:55:39.000 --> 00:55:41.000 Please feel free to do so, um… 00:55:41.000 --> 00:55:44.000 It would be great to have a little more… 00:55:44.000 --> 00:55:47.000 RA content, um, 00:55:47.000 --> 00:55:53.000 Tom, I know you are thinking about a couple that are still mulling about, milling about in your mind. 00:55:53.000 --> 00:55:55.000 Um, but if there are others, 00:55:55.000 --> 00:56:01.000 that are interested. It's a great… it's a very easy way to kind of get 00:56:01.000 --> 00:56:04.000 things on your CV, and um… 00:56:04.000 --> 00:56:09.000 It's a pretty easy group, it's a very low stakes. 00:56:09.000 --> 00:56:12.000 Um, I presented on e-reserves last year. It's… 00:56:12.000 --> 00:56:14.000 It's quite… 00:56:14.000 --> 00:56:19.000 Yeah, it's easy. It's not a… it's not a heavy lift, um… 00:56:19.000 --> 00:56:25.000 And if you have something that you're doing, and you're interested in sharing it with others, um… 00:56:25.000 --> 00:56:28.000 Please consider it. 00:56:28.000 --> 00:56:31.000 And you get to go to Prague, if you… 00:56:31.000 --> 00:56:34.000 If you want to, or you can also present 00:56:34.000 --> 00:56:38.000 Um, remotely. I'm not physically gonna be in Prague, but I will… 00:56:38.000 --> 00:56:41.000 be helping Katie run the… 00:56:41.000 --> 00:56:44.000 RA SIG meeting, so… 00:56:44.000 --> 00:56:46.000 It is possible to be… 00:56:46.000 --> 00:56:50.000 participating from home, and also, um… 00:56:50.000 --> 00:56:53.000 present. So give it some thought if you have any… 00:56:53.000 --> 00:56:56.000 ideas that you're interested in sharing. 00:56:56.000 --> 00:57:00.000 We would love to have some more content out there. 00:57:00.000 --> 00:57:05.000 Susan, I don't… I think I is the one that mentioned it. It's something on notices, maybe? 00:57:05.000 --> 00:57:07.000 I don't know if… 00:57:07.000 --> 00:57:08.000 I don't know, thank you. 00:57:08.000 --> 00:57:10.000 Yeah. And I don't know if anybody's able to actually… 00:57:10.000 --> 00:57:11.000 Okay, okay, yeah. 00:57:11.000 --> 00:57:14.000 Weigh in on notices, like… 00:57:14.000 --> 00:57:15.000 Um… 00:57:15.000 --> 00:57:19.000 Oh, so you didn't… didn't submit that then one? 00:57:19.000 --> 00:57:24.000 Because you're just suggested to do something on the notices. 00:57:24.000 --> 00:57:25.000 Oh, I… no. 00:57:25.000 --> 00:57:27.000 Did I, or did Katie did? 00:57:27.000 --> 00:57:28.000 Did I say I would do it? 00:57:28.000 --> 00:57:29.000 Or Katie did, and you… opted to run it? Yeah. 00:57:29.000 --> 00:57:33.000 I think so. 00:57:33.000 --> 00:57:34.000 I didn't want to call you out! 00:57:34.000 --> 00:57:39.000 I blocked… that didn't get into the… that did not get into the AI minutes that Susan offered, and we'll… 00:57:39.000 --> 00:57:40.000 Oh. Okay. 00:57:40.000 --> 00:57:44.000 action item would sign up for. Um, potentially I could. 00:57:44.000 --> 00:57:49.000 I mean, it would have to be remote, which is a little, um… I know is possible, but I don't know. 00:57:49.000 --> 00:57:52.000 Um, I certainly can. 00:57:52.000 --> 00:57:57.000 So, give me a little bit more, Katie, about what I said I would do now. 00:57:57.000 --> 00:58:01.000 Was it sort of a Notices 101? 00:58:01.000 --> 00:58:05.000 sort of from the beginning, how to set them up, because I certainly can do… 00:58:05.000 --> 00:58:10.000 That, or was I… were you thinking something more about… 00:58:10.000 --> 00:58:13.000 Optimizing your notices once they're… like, what's the target? 00:58:13.000 --> 00:58:16.000 audience, I guess, is what I'm thinking about. I want to… 00:58:16.000 --> 00:58:19.000 think about doing it in a way that makes the most sense. 00:58:19.000 --> 00:58:22.000 I think… I was thinking, like, a Notices 101. 00:58:22.000 --> 00:58:23.000 type thing. Just, I think… 00:58:23.000 --> 00:58:24.000 So, like, how notices. 00:58:24.000 --> 00:58:28.000 Yeah, because it's kind of daunting when you look at it. You have the 00:58:28.000 --> 00:58:34.000 templates, and then you, you know, have to create the policies and stuff. 00:58:34.000 --> 00:58:35.000 Okay, I can do that. 00:58:35.000 --> 00:58:38.000 Nothing complicated. 00:58:38.000 --> 00:58:42.000 I can do that. If anybody wants to help me with that, I'd be happy to have some help. 00:58:42.000 --> 00:58:46.000 Um, but I certainly can do it. 00:58:46.000 --> 00:58:52.000 I just wanted to add, uh, if you want to present virtually, please be aware of the time zone. 00:58:52.000 --> 00:58:58.000 Oh, grapes. 00:58:58.000 --> 00:58:59.000 Thank you. 00:58:59.000 --> 00:59:00.000 And Rick requested in your proposal. Do you want to be in the afternoon? 00:59:00.000 --> 00:59:03.000 Thank you. 00:59:03.000 --> 00:59:07.000 Um, if I do that, I will probably lean on 00:59:07.000 --> 00:59:10.000 you, Katie, or Cornelia to help me with in… 00:59:10.000 --> 00:59:19.000 person. I need somebody on the ground, right? Like, to help in the room. I think that's one thing that's really helpful, is if you're not 00:59:19.000 --> 00:59:24.000 physically there, it's very helpful to have a co-conspirator. 00:59:24.000 --> 00:59:33.000 physically there, um, to help to make sure. Even just, like, passing the mic around so people can ask questions of the speaker. 00:59:33.000 --> 00:59:37.000 Um, for local, and if there's any technical difficulties, 00:59:37.000 --> 00:59:39.000 If you're halfway around the world, it's kind of hard to… 00:59:39.000 --> 00:59:44.000 navigate those. You can't call on technical support if you're… 00:59:44.000 --> 00:59:48.000 somewhere else. 00:59:48.000 --> 00:59:53.000 Alright, thanks for that reminder. I will submit that request now, since the deadline is, like, Wednesday. 00:59:53.000 --> 00:59:59.000 Yeah, and Susan, if you need any help with that, I'm happy to help with that, since I did bring it up. 00:59:59.000 --> 01:00:05.000 Okay. Thank you. You're also doing a workshop, which is a much heavier lift, so… 01:00:05.000 --> 01:00:06.000 I will. 01:00:06.000 --> 01:00:07.000 Yeah, again, if I, like, don't want to pass the buck. 01:00:07.000 --> 01:00:10.000 Okay, I may… can I run my slide by you? 01:00:10.000 --> 01:00:12.000 Yeah, I'll get that'll work. 01:00:12.000 --> 01:00:15.000 Ah, so… All right. 01:00:15.000 --> 01:00:18.000 Any additional… 01:00:18.000 --> 01:00:19.000 suggestions. 01:00:19.000 --> 01:00:23.000 I mean, we will cover… we will cover notes on the workshop as well, so part of it, at least. 01:00:23.000 --> 01:00:27.000 Ooh, yeah. Maybe we can piggyback on that. 01:00:27.000 --> 01:00:31.000 That's good. 01:00:31.000 --> 01:00:32.000 All right. 01:00:32.000 --> 01:00:33.000 Yeah. 01:00:33.000 --> 01:00:35.000 Anything else before we… 01:00:35.000 --> 01:00:41.000 break. 01:00:41.000 --> 01:00:47.000 All right, thanks everyone. We will see some of you on Thursday at Fees and Fines. 01:00:47.000 --> 01:00:52.000 Otherwise, enjoy your calendar-calming week next week. 01:00:52.000 --> 01:00:54.000 And we will see you at the next… 01:00:54.000 --> 01:00:59.000 Meeting. Thanks, everyone! 01:00:59.000 --> 01:01:00.000 Bye. 01:01:00.000 --> 01:01:02.000 Okay, have aBye