WEBVTT 1 00:04:21.620 --> 00:04:23.790 Scott Peterson: I think we're just early this time. 2 00:04:33.060 --> 00:04:36.639 Steve Strohl | MOBIUS: Don't know how he can be early with 3 minutes to go, but I guess so. 3 00:04:37.210 --> 00:04:38.160 Scott Peterson: It happens. 4 00:05:29.380 --> 00:05:31.230 Katie Rahman: Hey, I know you guys. 5 00:05:33.100 --> 00:05:35.559 Steve Strohl | MOBIUS: These people never show up early for a meeting. 6 00:05:38.110 --> 00:05:40.920 Scott Peterson: Hi there, it took me a second to find my unmute button. 7 00:05:43.320 --> 00:05:46.459 Scott Peterson: Okay, so we agree to everything, it's all good, we can leap. 8 00:06:05.310 --> 00:06:08.509 Scott Peterson: And for once, I'm in the office, so you can see me on my webcam. 9 00:06:11.900 --> 00:06:13.030 Katie Rahman: Yeah! 10 00:06:13.600 --> 00:06:17.539 Katie Rahman: Oh, these glasses are horrible reflection. Let me go ahead and add on. 11 00:06:18.020 --> 00:06:19.760 Katie Rahman: Okay. 12 00:06:30.500 --> 00:06:31.470 Martina Schildt | VZG: Hello! 13 00:06:33.080 --> 00:06:36.769 Scott Peterson: Morning, or evening, as it may be, depending on time zone. 14 00:06:37.120 --> 00:06:39.519 Martina Schildt | VZG: Yeah, it's, it's rather afternoon here. 15 00:06:39.520 --> 00:06:40.210 Scott Peterson: Okay. 16 00:08:12.610 --> 00:08:15.610 Katie Rahman: Sorry, Steve, for all the confusing emails. 17 00:08:16.740 --> 00:08:19.040 Katie Rahman: So… 18 00:08:23.840 --> 00:08:24.880 Steve Strohl | MOBIUS: All good. 19 00:08:25.360 --> 00:08:28.720 Katie Rahman: Okay. Did you get Miley, this one? 20 00:08:35.919 --> 00:08:37.659 Susan Kimball: Hello, everyone. 21 00:08:38.270 --> 00:08:39.020 Scott Peterson: Morning! 22 00:08:39.870 --> 00:08:49.350 Susan Kimball: Sorry, I'm a little late. Does anybody else, like, have 10 minutes to go, and then start doing something, and then fail to look back at their clock until 11.01? 23 00:08:50.410 --> 00:08:54.830 Susan Kimball: That happens to me more than I'd like to admit. 24 00:08:58.040 --> 00:09:05.909 Susan Kimball: Welcome, everyone. We'll get started in just a moment. We'll see if anybody else comes in who had a similar problem to me this morning. 25 00:09:21.910 --> 00:09:26.670 Susan Kimball: I will throw the agenda in the chat for anybody that doesn't have it. 26 00:09:49.400 --> 00:10:08.710 Susan Kimball: All right, I think we'll get started, since we have a pretty big agenda today, and I want to try to get to as much as we can. Apologies for my voice, I'm still recovering from that head cold from last weekend, which is now through this weekend, and still today. So, I'll do my best to mute if I cough. 27 00:10:09.910 --> 00:10:20.909 Susan Kimball: So welcome! I want to… we have a couple of announcements, and then I will be handing it over to Martina, who's joining us to talk about prioritization, which I'm excited to hear about. 28 00:10:22.310 --> 00:10:34.399 Susan Kimball: Meeting-wise, we have a fee-find subgroup, I believe. Tom's not on the call, but we are supposed to have a fee-find subgroup on Thursday. That is our next, cycle, so… 29 00:10:34.770 --> 00:10:40.490 Susan Kimball: watch the Slack if that ends up getting canceled, but that is the plan as of right now. 30 00:10:40.740 --> 00:10:46.350 Susan Kimball: And then next week is calendar calming week, so no meetings on Monday and Thursday next week. 31 00:10:47.880 --> 00:10:53.819 Susan Kimball: We… and then, oh, no meeting on April 6th, because it's a German holiday. Perfect. 32 00:10:55.000 --> 00:10:57.970 Susan Kimball: Good to know. And then… 33 00:10:58.540 --> 00:11:07.219 Susan Kimball: We will be back in action on the 13th… not the 13th, that's a lie. Sorry, on the 9th. 34 00:11:07.400 --> 00:11:14.070 Susan Kimball: With, the next JIRA ticket review, will be the next cycle for that. 35 00:11:15.800 --> 00:11:22.730 Susan Kimball: Any other… Calendaring, announcements, thoughts? 36 00:11:24.790 --> 00:11:28.010 Susan Kimball: Tom, I said you were doing fee fines on Thursday, is that a lie? 37 00:11:30.890 --> 00:11:32.230 Susan Kimball: Awesome. Nope. 38 00:11:32.480 --> 00:11:34.329 Susan Kimball: Great. 39 00:11:35.100 --> 00:11:36.719 Susan Kimball: Let's see… 40 00:11:36.850 --> 00:11:46.810 Susan Kimball: 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. 41 00:11:46.840 --> 00:11:59.320 Susan Kimball: screen. So, the info is… there's a little bit more info on the Slack post, but the link in the agenda is to the, page that has all the details, if you want to help out. The deadline 42 00:11:59.760 --> 00:12:00.960 Susan Kimball: for that. 43 00:12:01.110 --> 00:12:11.729 Susan Kimball: if I'm not mistaken, I just looked it up, and now I've forgotten it already, is April 1st, April Fool's Day. So, jump on that if you'd like to help out and provide some feedback. 44 00:12:13.280 --> 00:12:32.059 Susan Kimball: And then, hot off the presses, Steph Buck is looking for some folks to help out with, answering questions about SMS messaging, which she's having time to turn her attention to, which I'm very excited about. There was several folks who said they were interested, so she suggested a little subgroup. 45 00:12:32.330 --> 00:12:43.260 Susan Kimball: Her estimate is just a couple of meetings to talk about workflows, and then another meeting after she has a chance to write things up to just give feedback on that. 46 00:12:43.870 --> 00:12:52.949 Susan Kimball: So, if anyone is interested in that, throw your name in the chat, and I will collect those names and let her, put something together. 47 00:12:56.000 --> 00:13:00.239 Susan Kimball: Anything else? Announcement-wise, administrivia-wise? 48 00:13:04.150 --> 00:13:19.879 Susan Kimball: Okay, then I will hand it over to Martina, who's joining us today, to talk about prioritization. This has been a long overdue invitation that we finally extended to her. Martina, we have not been doing nothing. I want you to know. 49 00:13:19.880 --> 00:13:31.910 Susan Kimball: We decided last January that we would start, by last January, I mean 2025, that we would start by going through all of our open JIRA tickets to try to get them into better shape, not really… 50 00:13:31.970 --> 00:13:36.390 Susan Kimball: Really just to decide what to close and what to keep, what needed more refinement. 51 00:13:36.960 --> 00:13:44.160 Susan Kimball: Before we prioritized, and now we're coming to the close of that, and now we're ready to turn our attention to prioritization. 52 00:13:44.400 --> 00:13:46.140 Susan Kimball: So, welcome. 53 00:13:46.780 --> 00:13:57.340 Martina Schildt | VZG: Thank you. Thanks for inviting me, and I mean, that makes perfect sense to first look at the JIRA tickets and then start the prioritization process and vote. 54 00:13:57.400 --> 00:14:08.860 Martina Schildt | VZG: I will speak merely, about how we do it in ERAM SIG. I'm the convener for, but I think the acquisition SIG has a very similar process. 55 00:14:09.000 --> 00:14:11.160 Martina Schildt | VZG: to the one that URMSEC has. 56 00:14:11.470 --> 00:14:15.960 Martina Schildt | VZG: And I thought I would briefly, 57 00:14:17.190 --> 00:14:36.739 Martina Schildt | VZG: yeah, maybe show you four slides to go through the process as an overview, and then maybe we can look at our individual pages and look at how we do it. And if you already know specific things, or whatever, if you have questions, just let me know and say that. 58 00:14:38.460 --> 00:14:48.940 Martina Schildt | VZG: So, the four slides I wanted to present to describe the overall process. So, in ERAMSIC, we have an Implementers Topics page. 59 00:14:49.340 --> 00:15:02.189 Martina Schildt | VZG: Where everyone in the community can add topics to, and topics means requirements, wishes. They may be very small and tiny, just adding one further 60 00:15:02.220 --> 00:15:18.740 Martina Schildt | VZG: 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. Everyone, can add to, 61 00:15:19.020 --> 00:15:31.419 Martina Schildt | VZG: the ERM implementers list, that's valid for the ERM SIG and some subgroups, and there, another subgroup has a specific one, so we work with, like, two implementers topics lists. 62 00:15:32.210 --> 00:15:44.870 Martina Schildt | VZG: And, these topics that are added to this list, will be discussed in our SIG or subgroups, 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. 63 00:15:44.960 --> 00:15:48.859 Martina Schildt | VZG: But everything that's added will be discussed first. 64 00:15:48.870 --> 00:16:07.070 Martina Schildt | VZG: 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, and especially the product owner learns about the requirement and can check as well whether he or she understands the issue. 65 00:16:07.240 --> 00:16:22.510 Martina Schildt | VZG: And then, after this discussion, either the product owner will create a JIRA ticket for the implementer's topics and the new requirement, or we may have another meeting because the PO brings, like, some mock-ups 66 00:16:22.510 --> 00:16:31.289 Martina Schildt | VZG: design proposals or, like, other, other, you know, input that needs discussion before we can add a JIRA ticket. 67 00:16:32.500 --> 00:16:43.540 Martina Schildt | VZG: And, 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. 68 00:16:43.540 --> 00:16:53.040 Martina Schildt | VZG: And every Jira ticket that's created from this implementer's list gets a specific label, and that's ERAMSICT topics. 69 00:16:53.330 --> 00:17:05.209 Martina Schildt | VZG: And so, because we have this label, we can create a JIRA dashboard on ERAMSIC topics that are for ranking or for voting. 70 00:17:05.470 --> 00:17:12.960 Martina Schildt | VZG: And this dashboard lists the different tickets by votes, as you can see, like, here. 71 00:17:13.740 --> 00:17:31.100 Martina Schildt | VZG: Exactly. And so everyone who wants to help prioritizing ERM features can go to this dashboard and just walk themselves through the list and add their votes to the different tickets. And how that goes, maybe we can look at. 72 00:17:31.160 --> 00:17:43.019 Martina Schildt | VZG: Afterwards. And then, this prioritization is, on one hand, done for the community priorities dashboard that's created by the Product Council. 73 00:17:43.280 --> 00:17:53.959 Martina Schildt | VZG: And we have decided that, like, we will split our priorities across the different teams, because the subgroups represent different development teams. 74 00:17:54.010 --> 00:18:00.310 Martina Schildt | VZG: We are allowed to give 5 priorities, and we have 4 different areas of focus. 75 00:18:00.350 --> 00:18:05.979 Martina Schildt | VZG: But so we have said, okay, the priority one is the one that comes from the ERM sick. 76 00:18:05.980 --> 00:18:20.640 Martina Schildt | VZG: The priority 2 comes from the e-holding subgroup, Priority 3 from the e-usage subgroup, and 4 from the agreements local KB subgroup. That may be different, for instance, Acquisitions has no resubgroups, they just do, I think, one priority list. 77 00:18:20.640 --> 00:18:25.919 Martina Schildt | VZG: And the last one is a joint one across our groups, where we decide as a team 78 00:18:26.090 --> 00:18:28.250 Martina Schildt | VZG: What the priority 5 is. 79 00:18:28.950 --> 00:18:45.919 Martina Schildt | VZG: But, 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, but for the different development teams, it helps to have this 80 00:18:45.920 --> 00:18:57.000 Martina Schildt | VZG: Voting and prioritization, 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. 81 00:18:57.460 --> 00:19:09.489 Martina Schildt | VZG: And, in this presentation is… is just… we have some Jira dashboards and Jira links, and we have some Confluence pages, but I think I can go now, directly to… 82 00:19:09.980 --> 00:19:12.409 Martina Schildt | VZG: Maybe our implementers… 83 00:19:12.890 --> 00:19:24.039 Martina Schildt | VZG: 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 yeah, anything I should focus on. 84 00:19:30.890 --> 00:19:36.810 Martina Schildt | VZG: If that's not the case, then let's go directly to our implementers page. 85 00:19:37.560 --> 00:19:51.690 Martina Schildt | VZG: I know that not all SIGs have such an implementer's topics page, EREM has, and the acquisition SIG has as well. This is really a page where everyone can add their wishes. And in our EREM 86 00:19:51.690 --> 00:20:01.659 Martina Schildt | VZG: case. We have, like, two tables on this page. There is one table where people can add their new topics that haven't been discussed yet. 87 00:20:02.030 --> 00:20:15.810 Martina Schildt | VZG: And the second table is… lists all the topics that have been discussed in our ERAMSIC, or one of the subgroups. And what is given in this table is, like, the app's name, because, like, ERAM 88 00:20:16.410 --> 00:20:27.270 Martina Schildt | VZG: is represented only by one app. The brief topic, and then the description, or some use cases. We have a discussion status. 89 00:20:27.710 --> 00:20:43.589 Martina Schildt | VZG: And I can show you in a second what different statuses we do have there. The date added, who provided the topic, interested parties can just list themselves as well. Then we have, a link to the discussion, the meeting minutes. 90 00:20:43.590 --> 00:20:57.719 Martina Schildt | VZG: 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. And it's… the status of the JIRA ticket, and that's important, is different from the discussion status. 91 00:20:57.830 --> 00:20:58.790 Martina Schildt | VZG: Because… 92 00:20:59.240 --> 00:21:18.740 Martina Schildt | VZG: it can be, like, through the SIG, and we are done with it. That means, for instance, for voting, we… the SIG itself will not do anything with this anymore, 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. 93 00:21:19.570 --> 00:21:34.880 Martina Schildt | VZG: What statuses do we have? We have the one that says open. All new items that haven't been discussed have a status open. Some, tickets or topics may be blocked because we need more information. 94 00:21:35.060 --> 00:21:44.529 Martina Schildt | VZG: 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, like. 95 00:21:44.800 --> 00:22:03.700 Martina Schildt | VZG: mock-up or process, but voting means the SIG has agreed, and it will be done, and there is a ticket for it that we can vote on. And closed can mean it's done, ticket is done, and development is done, or may even mean we have discussed, but we won't do, because it's not possible, or whatever. 96 00:22:03.930 --> 00:22:08.049 Martina Schildt | VZG: So these are the different, discussion statuses. 97 00:22:08.140 --> 00:22:26.029 Martina Schildt | VZG: We have a brief description of how people can add their topics, and we have as well here a page where we tell how to prioritize ERM implementer's topics in Jira, that you need an Atlassian account, and so on and so forth. 98 00:22:26.670 --> 00:22:44.410 Martina Schildt | VZG: On the right side here, we have a glimpse at the list in Jira, and if we look at this ERMSIC Topics, 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. 99 00:22:44.690 --> 00:23:00.740 Martina Schildt | VZG: They all have this ERM-6-topics label, and they are, sorted by votes, so the highest votes appear highest in the list. And that's, for instance, in our case, the agreements export multiple agreements to CSV, 100 00:23:01.260 --> 00:23:15.959 Martina Schildt | VZG: And if we now look at this ticket, everyone at this top right corner, should have this vote option. You can see this dump up, and if you click on that, you, should be able to 101 00:23:16.100 --> 00:23:19.479 Martina Schildt | VZG: Now, where is it? I don't see it here because I have so many. 102 00:23:20.090 --> 00:23:21.900 Martina Schildt | VZG: Towards in my way… 103 00:23:24.240 --> 00:23:36.970 Martina Schildt | VZG: There we go. So, I have voted for this, I can remove my vote, and, if I want to vote on something, I can just add my vote for this new feature, and then, by that, I have done 104 00:23:36.970 --> 00:23:45.160 Martina Schildt | VZG: 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, the higher it is in the list. 105 00:23:45.510 --> 00:24:04.199 Martina Schildt | VZG: That doesn't mean necessarily in ERM that this is done immediately after voting, so I'm not sure, like, other SIGs may go… go with this in a different way. I know that it's the same in Acquisition SIG, because the priorities list is usually something that's 106 00:24:04.210 --> 00:24:21.229 Martina Schildt | VZG: decided on before a release, maybe months ahead. It's often decided by the funding institution, and the funding institution picks community priorities as well, but it's not necessarily that only this list 107 00:24:21.360 --> 00:24:25.550 Martina Schildt | VZG: like, decides on what will be done and what will be developed, but… 108 00:24:25.790 --> 00:24:46.100 Martina Schildt | VZG: I think we have more and more requirements, and the backlog of Jira tickets grows 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. 109 00:24:46.100 --> 00:24:52.980 Martina Schildt | VZG: And if they need to wait for that period, and then talk with us about what do you want to have done first. 110 00:24:52.980 --> 00:25:05.610 Martina Schildt | VZG: 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 this prioritization is there whenever they have time to pick something up. 111 00:25:05.960 --> 00:25:10.009 Martina Schildt | VZG: And that's, possible by doing this voting. 112 00:25:11.720 --> 00:25:22.880 Martina Schildt | VZG: So that's that, that's the Jira, and, if we look back at how to prioritize, yeah, what you need is an Atlassian account. 113 00:25:23.140 --> 00:25:29.850 Martina Schildt | VZG: So that you, and you can set up an account using this link. We have this how-to page in ERM. 114 00:25:30.450 --> 00:25:40.929 Martina Schildt | VZG: 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. 115 00:25:40.970 --> 00:25:52.109 Martina Schildt | VZG: In our case, it's ERAM Sick Topics. Then you can vote on the issues by, yeah, selecting the ticket you would like to prioritize and clicking this thumb-up button. 116 00:25:52.310 --> 00:25:55.729 Martina Schildt | VZG: Yeah. And then, 117 00:25:56.330 --> 00:26:16.129 Martina Schildt | VZG: sometimes, in our case, because we base our prioritization on this implemented list, there may be tickets that don't have the label ERAM SIG topics, but that's something that people can bring back to the SIG, to the PO, or to me as a convener, and then we can discuss in the… in the SIG, and 118 00:26:16.130 --> 00:26:20.480 Martina Schildt | VZG: Add the label to the ticket, nevertheless, so that it is votable, for instance. 119 00:26:21.290 --> 00:26:39.680 Martina Schildt | VZG: And, this dashboard that comes out of it, 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. 120 00:26:39.800 --> 00:26:52.590 Martina Schildt | VZG: But that's something that really influences 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 do them. 121 00:26:53.160 --> 00:27:01.570 Martina Schildt | VZG: And everyone can follow What the status is of this ticket, and everyone can be kept informed. 122 00:27:03.160 --> 00:27:05.940 Martina Schildt | VZG: Yeah, and I think that's our… 123 00:27:06.440 --> 00:27:11.830 Martina Schildt | VZG: prioritization process, the one thing that I have, 124 00:27:12.340 --> 00:27:25.600 Martina Schildt | VZG: 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 based on this process that we have in our SICK. 125 00:27:30.080 --> 00:27:38.380 Martina Schildt | VZG: Was that, yeah, do you have any questions? Was that clear, how our process goes? 126 00:27:40.810 --> 00:27:51.599 Susan Kimball: That was incredibly clear, and very impressive, how organized that whole thing is. Thank you so much, Martina. That is stunning, how… 127 00:27:51.950 --> 00:28:11.080 Susan Kimball: not just clear it is, but how clear it is how others can vote, and to your own people, and then explaining it to us. I… it's interesting, I think there are some things we can definitely take away from this. I think one of the challenges for the RACIG is, 128 00:28:11.730 --> 00:28:27.629 Susan Kimball: there… we have literally, like, 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, we sort of already have this huge corpus of ideas and Jira tickets that… 129 00:28:27.930 --> 00:28:47.729 Susan Kimball: we need to figure out how to wrangle, but I do think there are definitely ways we can translate and adapt some of the processes you've used, to our scenario. So I'll need to be talking to Katie, Rahman, my co-convener, and we'll have to strategize how we're gonna figure out how to roll this out. 130 00:28:48.170 --> 00:28:56.659 Susan Kimball: And apply it to our own unique scenario here in RA. One question I have that I think is 131 00:28:57.240 --> 00:29:01.029 Susan Kimball: different than what our structure here. 132 00:29:01.550 --> 00:29:09.570 Susan Kimball: We do… it's curious that you have an ERM implementers group, and I want to hear a little bit about how those two… 133 00:29:10.100 --> 00:29:25.209 Susan Kimball: are differentiated in how they function. Like, is that a group that meets separately from the ERM SIG? And… or is it just, kind of, virtually, you are all the people who are implementing… implemented who have ERM? 134 00:29:26.310 --> 00:29:34.990 Martina Schildt | VZG: Yeah, exactly, and I mean, maybe we could even rename that page, because it… I think it's called ERAM Implementers Page. 135 00:29:35.240 --> 00:29:49.139 Martina Schildt | VZG: 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. It's just that we, from time to time, really 136 00:29:49.170 --> 00:30:04.689 Martina Schildt | VZG: 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, like the… maybe UATs are described, but we really come back 137 00:30:04.910 --> 00:30:17.230 Martina Schildt | VZG: 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, so… so that's really… 138 00:30:17.230 --> 00:30:27.219 Martina Schildt | VZG: when we see we have now a good bunch of new topics, then we would discuss those in the… in the SAG, in the usual ERAM SAG, or one of the subgroups where they belong to. 139 00:30:31.570 --> 00:30:45.299 Martina Schildt | VZG: And, we have more tickets in JIRA as well. We really reduced the number of votables by adding this ERAMSIC Topics label. That could be different, but that's really our way to say this is the 140 00:30:45.440 --> 00:30:53.849 Martina Schildt | VZG: 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. 141 00:30:54.130 --> 00:30:54.820 Martina Schildt | VZG: Yeah. 142 00:30:55.830 --> 00:31:01.569 Susan Kimball: Do you have ERM tickets that are in there that don't have that label? Like, that didn't come from the SIG? Okay. 143 00:31:01.570 --> 00:31:02.430 Martina Schildt | VZG: Yeah, yeah. 144 00:31:07.970 --> 00:31:09.800 Susan Kimball: Other questions that folks have? 145 00:31:19.760 --> 00:31:20.550 Martina Schildt | VZG: And yeah. 146 00:31:21.840 --> 00:31:30.189 Anja Kakau | VZG: How is the voting recorded in JIRA? Is this a specific field or specific function that is used for that? 147 00:31:31.480 --> 00:31:36.159 Martina Schildt | VZG: Yes, that's… forgive me one second, I will share my screen again, and maybe… 148 00:31:37.250 --> 00:31:41.160 Martina Schildt | VZG: Let me find the e-holdings one, because… 149 00:31:41.650 --> 00:31:46.320 Martina Schildt | VZG: Yeah, exactly. So, you should see the ticket now. 150 00:31:46.450 --> 00:31:52.850 Martina Schildt | VZG: Yeah, you do. And in the top right corner, you really have this thumb-up option. 151 00:31:53.060 --> 00:32:04.979 Martina Schildt | VZG: And if you click on that, and why is it sometimes displaying correctly and sometimes not? Now it's better. You see the list of people who have voted for this ticket, but that's something, I mean. 152 00:32:05.240 --> 00:32:15.709 Martina Schildt | VZG: 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, and then my vote is added. 153 00:32:16.330 --> 00:32:20.159 Martina Schildt | VZG: Yeah, and that's something that then can be… 154 00:32:20.400 --> 00:32:31.359 Martina Schildt | VZG: used for sorting the tickets in a list on a dashboard, for instance, or if you look on the NVIDIA ticket, you can see the number of thumbs, and that's the number of votes. 155 00:32:32.400 --> 00:32:41.510 Martina Schildt | VZG: And it's not restricted, maybe that's something that is good information as well. It's not restricted. 156 00:32:41.510 --> 00:33:00.349 Martina Schildt | VZG: But in our SIC, and I know in acquisitions as well, it works, that not, like, 100 people from one organization vote on one ticket because they want to, like, push that. That works, and what the product owners always say is they can see, like, if you look at the list, you can see 157 00:33:00.380 --> 00:33:11.910 Martina Schildt | VZG: Who voted on it, and if there is a lot of people from my institution, for instance, they know, okay, BZG needs it, but do others need it as well? We thought about restricting that. 158 00:33:12.070 --> 00:33:22.269 Martina Schildt | VZG: But that's not easy, so… and we said everyone with an Atlassian account is allowed to vote, and, people should be, yeah. 159 00:33:22.780 --> 00:33:28.729 Martina Schildt | VZG: Should try not to, trick out the system, but vote per institution. 160 00:33:30.350 --> 00:33:35.360 Martina Schildt | VZG: Does that explain your, answer your question, Anya? Or was that a different one? 161 00:33:35.680 --> 00:33:46.589 Anja Kakau | VZG: 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? 162 00:33:47.010 --> 00:33:50.379 Martina Schildt | VZG: Yeah, it's… it should be there for everyone, yeah. 163 00:33:53.260 --> 00:33:57.870 Susan Kimball: So it sounds like it's essentially honor system… 164 00:33:58.050 --> 00:34:03.320 Susan Kimball: That one representative will vote for per institution. 165 00:34:03.540 --> 00:34:10.980 Susan Kimball: That seems like a reasonable expectation. And because it's so transparent, it would be pretty obvious if somebody's really gaming the system. 166 00:34:12.090 --> 00:34:27.770 Martina Schildt | VZG: And some institutions even said, okay, we are such a large institution, and there may be different votes from, like, the Jonas Department and the resource access department, whatever, so it may be okay if multiple people vote, but, like. 167 00:34:27.770 --> 00:34:32.509 Martina Schildt | VZG: No, that didn't really happen in our scenario, so that really worked out. 168 00:34:33.679 --> 00:34:42.289 Martina Schildt | VZG: And it should be lightweight, and not too complicated, and that really is doable via this voting process, from my perspective. 169 00:34:56.150 --> 00:34:58.620 Susan Kimball: Other questions… 170 00:35:04.170 --> 00:35:17.290 Susan Kimball: for Martina, or thoughts about… Thoughts… initial thoughts about, sort of, how… this… could… Work in the resource access. 171 00:35:18.290 --> 00:35:21.210 Susan Kimball: SIG, knowing how many tickets we have. 172 00:35:27.130 --> 00:35:28.490 Susan Kimball: Yeah, Cornelia. 173 00:35:29.790 --> 00:35:43.329 Cornelia Awenius (UB Mainz): We should… we could maybe try to revert 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. 174 00:35:45.130 --> 00:35:53.090 Cornelia Awenius (UB Mainz): Or… I'm not sure, maybe… Develop parallel structures for, like. 175 00:35:53.870 --> 00:35:58.609 Cornelia Awenius (UB Mainz): So we don't have that many tickets that are ready for DEF. 176 00:35:58.880 --> 00:36:02.139 Cornelia Awenius (UB Mainz): At this moment, so developers could choose from them. 177 00:36:02.390 --> 00:36:10.280 Cornelia Awenius (UB Mainz): And start with, like, voting for what to refine, and the more we get refined, We could switch to… 178 00:36:11.520 --> 00:36:17.299 Cornelia Awenius (UB Mainz): To, what, yeah, what would… what should be developers' priorities? 179 00:36:21.140 --> 00:36:22.030 Susan Kimball: Anya? 180 00:36:23.850 --> 00:36:39.870 Anja Kakau | VZG: 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 181 00:36:40.320 --> 00:36:50.330 Anja Kakau | VZG: 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 182 00:36:52.170 --> 00:37:06.150 Anja Kakau | VZG: 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. 183 00:37:08.000 --> 00:37:16.790 Anja Kakau | VZG: I really like that. Would that work for us, to go through this process of refining, adding new steps on an ongoing process? 184 00:37:22.150 --> 00:37:34.649 Susan Kimball: Yeah, well, I really like the way that Martina described, sort of, that not all tickets are available for voting at all times, right? So, even if we are looking at tickets that need refinement. 185 00:37:35.760 --> 00:37:45.789 Susan Kimball: we don't have to necessarily open all tickets for voting at the same… like, I don't think that would be successful. I think that telling the community to vote for 500 tickets 186 00:37:46.200 --> 00:37:57.459 Susan Kimball: is a non-starter. I mean, it throws me back to, like, what features do you need in MVP in order to go live? Like, those spreadsheets were mind-boggling. 187 00:37:57.690 --> 00:38:00.910 Susan Kimball: So, I don't think that's a viable… 188 00:38:01.770 --> 00:38:05.020 Susan Kimball: path. The question is how to get from 189 00:38:05.340 --> 00:38:08.560 Susan Kimball: The number of tickets we have now in various states. 190 00:38:08.840 --> 00:38:12.290 Susan Kimball: To… how does… how could we start? 191 00:38:12.490 --> 00:38:26.049 Susan Kimball: voting. We could also have two dashboards, right? You could have a dashboard for the prioritization of things that need refinement, and then the prioritization of things that are ready… dev-ready, that are assigned to a dev team. 192 00:38:26.270 --> 00:38:27.250 Susan Kimball: Olga? 193 00:38:29.250 --> 00:38:34.680 Olga: I wonder if we could… similarly to… 194 00:38:35.010 --> 00:38:39.709 Olga: the other 6, we have areas, right? Sort of, like… 195 00:38:39.920 --> 00:38:45.030 Olga: Fines, and, checkouts, and, 196 00:38:45.480 --> 00:38:56.060 Olga: notices and, and such. So maybe come up with a few of those areas that would divide 197 00:38:56.250 --> 00:39:02.509 Olga: The tickets automatically, and then maybe concentrate on one. 198 00:39:04.220 --> 00:39:09.640 Olga: And, area, and, that… 199 00:39:10.170 --> 00:39:17.049 Olga: Might make it a bit easier, but still, it's gonna be, like… Probably 50, 70 tickets. 200 00:39:18.330 --> 00:39:21.539 Olga: So, I don't know after that. 201 00:39:23.670 --> 00:39:26.990 Susan Kimball: That's a good suggestion, Olga. The… 202 00:39:27.070 --> 00:39:46.639 Susan Kimball: if you remember the first… when we were looking through the Vega and the Valaris open tickets, we did that. We sort of… like, the 150 were too many to look at, and we sort of were like, let's look at requests today. And that is another… that's definitely a way we can think about breaking it down. 203 00:39:52.430 --> 00:39:54.480 Susan Kimball: Other thoughts? 204 00:40:08.610 --> 00:40:13.490 Susan Kimball: All right, well, we will con- oh, Anya, you got another one? Nope, mistake! 205 00:40:13.490 --> 00:40:31.230 Anja Kakau | VZG: Yeah, no, not a mistake. We have been starting to discuss this when we looked at the old tickets as well, and I still really, really like this idea of kind of dividing it up by grouping the tickets to related tickets and areas. 206 00:40:31.310 --> 00:40:40.639 Anja Kakau | VZG: Because I… I feel that this will be helpful to also link separate tickets together, like, how they relate to each other, because I feel that 207 00:40:40.640 --> 00:40:54.909 Anja Kakau | VZG: If we get a group of tickets that are related to each other, 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. 208 00:40:55.450 --> 00:41:01.419 Anja Kakau | VZG: So, I think that would be a good approach, given the huge number of tickets we have. So… 209 00:41:01.800 --> 00:41:06.749 Anja Kakau | VZG: we would have to discuss a way to kind of decide as a whole SICK on… 210 00:41:06.760 --> 00:41:22.720 Anja Kakau | VZG: 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… how to approach that. 211 00:41:24.860 --> 00:41:32.319 Susan Kimball: Yeah, for sure. I mean, I think our gap list is a good place to start, because a gap list is already a… sort of a… 212 00:41:33.070 --> 00:41:45.299 Susan Kimball: A place where people have proactively said, these are things we want to have, and that is sort of a… one way around, looking at the particular things that people have done 213 00:41:45.500 --> 00:41:55.450 Susan Kimball: identified as priorities already in some respects, so that's one way. And I do think you're right, Anya, that spending some time 214 00:41:55.930 --> 00:42:00.200 Susan Kimball: Clustering these and making sure the relationships are together. 215 00:42:00.560 --> 00:42:10.460 Susan Kimball: In the ticket is helpful, because you're right, there… it's much easier to develop within, you know, 3 or 4 things that are related. 216 00:42:10.700 --> 00:42:18.239 Susan Kimball: And sometimes it can reveal, sort of, better strategies when you know all of the problems in one place. 217 00:42:20.120 --> 00:42:21.480 Susan Kimball: That's a good idea. 218 00:42:31.660 --> 00:42:35.960 Susan Kimball: Martina, are you able to share the slides in the agenda? 219 00:42:36.420 --> 00:42:43.250 Susan Kimball: Thank you. If you can just link it to the agenda item, you can do that, or you can pop a link in the chat, and I can do it either way. 220 00:42:43.600 --> 00:42:44.769 Martina Schildt | VZG: Will do, yeah. 221 00:42:44.770 --> 00:42:45.780 Susan Kimball: Thank you. 222 00:42:48.040 --> 00:42:52.950 Susan Kimball: Other… thoughts about process. 223 00:43:01.310 --> 00:43:10.590 Susan Kimball: All right, well, I think this is a really good start, and I'm really excited about how we can think about moving forward with some of these. 224 00:43:12.330 --> 00:43:19.340 Susan Kimball: Thank you, Martina, so much for coming. I know it's long overdue, but it was well worth it. Well worth the wait! 225 00:43:19.340 --> 00:43:20.980 Martina Schildt | VZG: Thanks for having me, thank you. 226 00:43:20.980 --> 00:43:23.050 Susan Kimball: Yeah, okay, thanks. 227 00:43:23.820 --> 00:43:30.150 Susan Kimball: All right, well, we will turn our attention to our draft, 228 00:43:30.580 --> 00:43:33.830 Susan Kimball: review of… I mean, reviewing our draft description. 229 00:43:34.940 --> 00:43:44.119 Susan Kimball: There's a link in the agenda to the… Description, and… let's see… Go to it. 230 00:43:46.380 --> 00:43:53.180 Susan Kimball: So, if folks want to take a look… 231 00:43:57.420 --> 00:44:07.720 Susan Kimball: So, full disclosure, I used AI to help draft this, because I ran out of time to do it myself. And so, I would love for folks to… 232 00:44:08.390 --> 00:44:15.150 Susan Kimball: Take a look… there's not… first of all, this is not like… 233 00:44:15.950 --> 00:44:26.839 Susan Kimball: high stakes. This is very, like, very low stakes. The reason we want to rewrite it is because the description that was on… that is currently on our website, 234 00:44:27.060 --> 00:44:28.070 Susan Kimball: is… 235 00:44:29.160 --> 00:44:36.179 Susan Kimball: very much related to when we were building a system from whole cloth. So it talks about, you know. 236 00:44:36.300 --> 00:44:41.190 Susan Kimball: Writing requirements and things like that, that are about 237 00:44:41.410 --> 00:44:49.480 Susan Kimball: A system that is not yet built, as opposed to a system that is built and is being maintained, enhanced, further developed. 238 00:44:50.120 --> 00:45:01.870 Susan Kimball: So that's why this, this list is… or the refinement is required, or seems necessary, to be able to signal to other 239 00:45:02.580 --> 00:45:08.169 Susan Kimball: folks who are maybe considering joining the SIG to know what it is that we do. 240 00:45:10.340 --> 00:45:17.460 Susan Kimball: So David suggested adding calendars, I think that… Makes sense. Are there… 241 00:45:18.380 --> 00:45:23.000 Susan Kimball: Other thoughts about this? I'll give folks a minute to read it. 242 00:45:27.130 --> 00:45:36.140 Katie Rahman: I was just maybe thinking when talking about cross-app functions, maybe user management, mentioning that, since there's a lot of crossover. 243 00:45:36.820 --> 00:45:53.509 Susan Kimball: Yeah. It was… I was considering adding a list… some, you know, individual ones, and then I was like, well, then we gotta add this, and this, and this. But you're right, I do feel like the user management connection is much stronger than… I mean, it's sort of foundational to what we do. 244 00:45:53.960 --> 00:45:54.840 Susan Kimball: I think. 245 00:46:23.720 --> 00:46:28.649 Scott Peterson: You could put a catch-all of general circulation issues, or, 246 00:46:29.290 --> 00:46:33.570 Scott Peterson: developments? Did I catch anything we might be… might not have mentioned there? 247 00:46:34.950 --> 00:46:36.710 Susan Kimball: Which part do you mean, Scott? 248 00:46:37.240 --> 00:46:44.440 Scott Peterson: I was saying, at the end of the list, a kind of a catch-all statement saying, for general circulation issues related to folio. 249 00:46:44.730 --> 00:46:47.550 Scott Peterson: That'd be kind of a catch-all for anything else not covered there. 250 00:46:47.860 --> 00:46:48.770 Susan Kimball: Gotcha. 251 00:47:33.670 --> 00:47:38.359 Susan Kimball: I'm looking back at the notes from February 9th, which I included… I… 252 00:47:39.530 --> 00:47:45.539 Susan Kimball: That's where we discussed this, so if anybody wants to see, sort of, what we… 253 00:47:45.770 --> 00:47:49.680 Susan Kimball: discussed at that meeting. I can throw that in here. 254 00:47:51.840 --> 00:47:55.409 Susan Kimball: I actually did take notes at this one. 255 00:47:57.460 --> 00:48:00.559 Susan Kimball: These are real notes, not AI notes. 256 00:48:01.830 --> 00:48:05.359 Susan Kimball: That's where the suggestion about making the bulleted list came up. 257 00:48:08.740 --> 00:48:15.709 Susan Kimball: We had talked about adding multiple… more things that were omitted, and then we'd also talked about, well, maybe we should… 258 00:48:15.940 --> 00:48:16.850 Susan Kimball: have… 259 00:48:18.020 --> 00:48:26.119 Susan Kimball: Sort of a… not… rather than trying to make a laundry list of absolutely everything, sort of have larger catch-all, 260 00:48:26.500 --> 00:48:31.640 Susan Kimball: Things, so there were some sort of competing… ideas there. 261 00:48:57.040 --> 00:49:05.230 Susan Kimball: We could include… one of the things was, resource sharing and remote storage. 262 00:49:05.370 --> 00:49:13.420 Susan Kimball: End user management sort of all fall into the category of I mean… 263 00:49:14.410 --> 00:49:18.890 Susan Kimball: The problem is they don't all take the same form, so it's not, 264 00:49:19.980 --> 00:49:31.420 Susan Kimball: it's not always collaborating with other SIGs, it could be, you know, they could also be subgroups of our own SIGs, so it's a little bit tricky to think about how to word that in a way that's accurate. 265 00:49:47.470 --> 00:49:51.740 Susan Kimball: Well, if there are other, thoughts. 266 00:49:52.920 --> 00:49:58.369 Susan Kimball: Please add them as comments to the description, and I will, 267 00:49:59.360 --> 00:50:02.189 Susan Kimball: Take another pass at this, and then send it out. 268 00:50:02.430 --> 00:50:03.670 Susan Kimball: For final. 269 00:50:03.870 --> 00:50:08.059 Susan Kimball: approval, in the coming… 270 00:50:08.200 --> 00:50:15.499 Susan Kimball: days. I'll give it another week, we can look at it, oh, I guess we're not gonna meet for a couple weeks because of… 271 00:50:16.300 --> 00:50:26.739 Susan Kimball: calming and holidaying. So we will… when we next meet, we will put the finishing touches on this, and then we can swap it out on the… on the wiki. 272 00:50:26.980 --> 00:50:32.669 Susan Kimball: There's not a formal approval process, I don't think. Unless I'm missing something, Cornelia. 273 00:50:33.310 --> 00:50:36.579 Susan Kimball: I think this is just our description of ourselves. 274 00:50:39.450 --> 00:50:43.080 Susan Kimball: Alright, anything else? 275 00:50:51.410 --> 00:50:52.419 Thomas Trutt: Just a nug. 276 00:50:52.570 --> 00:50:54.900 Thomas Trutt: Quick reminder, 277 00:50:58.510 --> 00:51:03.780 Thomas Trutt: Implementer State has started the process of writing a survey. 278 00:51:04.650 --> 00:51:15.220 Thomas Trutt: I know that it was… the RA wanted to do the same thing, so if possible, they would like us to start looking at some of the questions we would like to have, if we wanted 279 00:51:15.790 --> 00:51:21.710 Thomas Trutt: Have… 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. 280 00:51:23.860 --> 00:51:28.670 Susan Kimball: I think we were hoping that we would… 281 00:51:28.880 --> 00:51:31.570 Susan Kimball: Be able to piggyback on the… that. 282 00:51:31.990 --> 00:51:39.480 Susan Kimball: So, I have seen that the implementers, as the meetings have been the survey subgroup. 283 00:51:39.600 --> 00:51:47.219 Susan Kimball: Would it be helpful, Tom, for one of us to go to a meeting, or do you… are you obvious… are you going to those meetings? 284 00:51:47.850 --> 00:51:59.380 Thomas Trutt: Yeah, I'm one of the conveners, but yeah, if somebody else wants to come, I think that'd be helpful, too. 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… 285 00:51:59.610 --> 00:52:03.890 Thomas Trutt: Main survey from blowing up to this humongous thing. 286 00:52:03.980 --> 00:52:17.229 Thomas Trutt: 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? So that might lean more towards a separate survey. 287 00:52:17.230 --> 00:52:30.530 Thomas Trutt: But, yeah, I think having somebody come to that meeting might help, but it might also be something we want to talk about in this group as well, of what sort of questions we want, and what sort of detail we want to get down to. 288 00:52:31.650 --> 00:52:32.250 Susan Kimball: Yeah. 289 00:52:32.760 --> 00:52:39.420 Susan Kimball: What… do you know when the next meeting is, or is there a next meeting scheduled? 290 00:52:40.070 --> 00:52:52.099 Thomas Trutt: I'll have to look, we've been using the, planning board meeting for it, which would mean that it fall next Thursday, but I think that's off because of… 291 00:52:53.020 --> 00:52:54.300 Susan Kimball: Calendar calming. 292 00:52:54.990 --> 00:53:00.360 Thomas Trutt: Yeah, so I will look and I can drop you a message in Slack. 293 00:53:00.990 --> 00:53:03.560 Thomas Trutt: When it comes up, I'll drop the message in Slack. 294 00:53:04.410 --> 00:53:08.619 Susan Kimball: Okay, if I'm able to come, I will try to come. I think, 295 00:53:08.860 --> 00:53:11.980 Susan Kimball: there are some pros and cons, I think, to… 296 00:53:12.890 --> 00:53:18.310 Susan Kimball: Trying to, like, we have to figure out what is the actual goal of the survey, 297 00:53:19.160 --> 00:53:28.260 Susan Kimball: I think the higher-level survey can get us a lot of information that we're trying to get, and… and then we need to think about the bang for the buck of… 298 00:53:28.510 --> 00:53:38.479 Susan Kimball: doing a separate survey, certainly. And are there some higher-level questions, higher-level RA questions that we think we would like to have in there? 299 00:53:38.670 --> 00:53:41.909 Susan Kimball: That could get us partway there. 300 00:53:42.530 --> 00:54:00.069 Susan Kimball: or achieve some of the goals. So I want to circle back to what our initial goals were about that survey. This was the conversation that we primarily had at WolfCon, if I remember correctly, and so I can look back at that, those notes. Like, that was the topic of our WolfCon, 301 00:54:00.420 --> 00:54:09.900 Susan Kimball: in-person, hybrid, whatever, general RACIG meeting in September. So, I'll look back and see… 302 00:54:10.090 --> 00:54:23.459 Susan Kimball: that was where the idea of getting together with the implementer SIG and actually having a larger survey, having one instead of trying to survey all folio libraries simultaneously, twice. 303 00:54:24.430 --> 00:54:31.289 Thomas Trutt: Exactly. And actually, as a plug for WolfCon, too, is the calls for proposals end on the 25th. 304 00:54:32.090 --> 00:54:32.819 Susan Kimball: Thank you. 305 00:54:32.980 --> 00:54:43.359 Susan Kimball: Thank you. Yes, so I was gonna say that. I submitted a tick… I submitted one proposal for the general RACIG meeting as a placeholder, so we will… 306 00:54:43.500 --> 00:54:52.319 Susan Kimball: do whatever topics, we have at the time, but it's good to have a placeholder meeting. And then, 307 00:54:53.150 --> 00:54:57.939 Susan Kimball: I sent out the call on Slack, I'm not sure if anyone else has put anything out there. 308 00:54:58.070 --> 00:55:08.020 Susan Kimball: And then Katie and Cornelia were going to be looking into doing a workshop proposal. Can you give an update on that, either of you, about where you're at? 309 00:55:11.380 --> 00:55:18.520 Katie Rahman: 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. 310 00:55:18.740 --> 00:55:21.940 Katie Rahman: to, getting that done, so… 311 00:55:21.940 --> 00:55:24.150 Susan Kimball: Fantastic! Yay. 312 00:55:24.530 --> 00:55:27.290 Susan Kimball: If there are any other… 313 00:55:27.900 --> 00:55:32.249 Susan Kimball: Thoughts about if anybody is wanting to submit 314 00:55:32.530 --> 00:55:42.080 Susan Kimball: a proposal for another, non-workshop, but just a session, please feel free to do so. 315 00:55:42.200 --> 00:55:47.769 Susan Kimball: It would be great to have a little more… RA content, 316 00:55:47.890 --> 00:55:55.940 Susan Kimball: Tom, I know you are thinking about a couple that are still mulling about, milling about in your mind, but if there are others 317 00:55:56.190 --> 00:55:57.570 Susan Kimball: that are interested. 318 00:55:57.960 --> 00:56:01.560 Susan Kimball: It's a great… it's a very easy way to kind of get 319 00:56:02.230 --> 00:56:13.770 Susan Kimball: things on your CV, and it's a pretty easy group. It's very low stakes. I presented on e-reserves last year. It's… it's quite… 320 00:56:14.460 --> 00:56:16.050 Susan Kimball: Yeah, it's easy. 321 00:56:16.370 --> 00:56:27.650 Susan Kimball: It's not a heavy lift, and if you have something that you're doing, and you're interested in sharing it with others, please consider it. 322 00:56:28.380 --> 00:56:31.560 Susan Kimball: And… you get to go to Prague, if you… 323 00:56:31.760 --> 00:56:39.639 Susan Kimball: If you want to. Or, you can also present, remotely. I'm not physically going to be in Prague, but I will be 324 00:56:39.790 --> 00:56:46.500 Susan Kimball: helping Katie run the RA-SIG meeting, so, it is possible to be 325 00:56:47.100 --> 00:56:51.110 Susan Kimball: Participating from home, and also, present. 326 00:56:51.280 --> 00:56:53.790 Susan Kimball: So give it some thought if you have any… 327 00:56:54.220 --> 00:57:00.230 Susan Kimball: ideas that you're interested in sharing. We would love to have some more content out there. 328 00:57:00.640 --> 00:57:05.409 Katie Rahman: Susan, I don't… I think I is the one that mentioned it. It's something on notices, maybe? 329 00:57:05.620 --> 00:57:07.519 Katie Rahman: I don't know if… 330 00:57:07.580 --> 00:57:10.870 Susan Kimball: And I don't know if anybody is able to actually… 331 00:57:11.740 --> 00:57:12.220 Katie Rahman: Okay. 332 00:57:12.220 --> 00:57:14.149 Susan Kimball: Weigh in on notices, like… 333 00:57:15.570 --> 00:57:18.340 Cornelia Awenius (UB Mainz): So you didn't… didn't submit that one? 334 00:57:19.310 --> 00:57:22.539 Cornelia Awenius (UB Mainz): Because you just suggested to do something on the notices. 335 00:57:24.130 --> 00:57:25.940 Susan Kimball: Did I, or did Katie did? 336 00:57:25.940 --> 00:57:27.770 Cornelia Awenius (UB Mainz): Or Katie did, and you… 337 00:57:28.490 --> 00:57:29.710 Susan Kimball: Did I say… it. 338 00:57:29.770 --> 00:57:30.700 Cornelia Awenius (UB Mainz): Yeah. 339 00:57:30.700 --> 00:57:33.069 Katie Rahman: I think so. 340 00:57:33.500 --> 00:57:39.479 Susan Kimball: I blog… that didn't get into the… that did not get into the AI minutes that Susan offered and will. 341 00:57:39.480 --> 00:57:39.870 Cornelia Awenius (UB Mainz): Oh. 342 00:57:39.870 --> 00:57:44.250 Susan Kimball: action item would sign up for. Potentially I could. 343 00:57:44.410 --> 00:57:52.060 Susan Kimball: I mean, it would have to be remote, which is a little, I know is possible, but I don't know. I certainly can. 344 00:57:52.480 --> 00:57:57.519 Susan Kimball: So, give me a little bit more, Katie, about what I said I would do. 345 00:57:57.730 --> 00:58:00.890 Susan Kimball: Was it sort of a Notices 101? 346 00:58:01.420 --> 00:58:09.470 Susan Kimball: like, sort of, from the beginning, how to set them up, because I certainly can do that, or was I… were you thinking something more about… 347 00:58:10.690 --> 00:58:18.999 Susan Kimball: optimizing your notices once they're… like, what's the target audience, I guess, is what I'm thinking about. I want to think about doing it in a way that makes the most sense. 348 00:58:19.750 --> 00:58:24.230 Katie Rahman: I think… I was thinking, like, a Notices 101 type thing. 349 00:58:24.230 --> 00:58:24.770 Susan Kimball: account. 350 00:58:25.090 --> 00:58:34.079 Katie Rahman: Yeah, because it's kind of daunting when you look at it. You have the templates, and then you, you know, have to create the policies and stuff. 351 00:58:35.350 --> 00:58:35.910 Susan Kimball: Okay. 352 00:58:36.390 --> 00:58:37.570 Katie Rahman: Nothing complicated. 353 00:58:38.440 --> 00:58:43.670 Susan Kimball: I can do that. If anybody wants to help me with that, I'd be happy to have some help. 354 00:58:44.080 --> 00:58:45.610 Susan Kimball: But I certainly can do it. 355 00:58:46.780 --> 00:58:52.840 Cornelia Awenius (UB Mainz): I just wanted to add, if you want to present virtually, please be aware of the time zone. 356 00:58:53.040 --> 00:58:58.170 Cornelia Awenius (UB Mainz): And request that in your proposal. 357 00:58:58.760 --> 00:58:59.120 Susan Kimball: Thank you. 358 00:58:59.120 --> 00:59:00.529 Cornelia Awenius (UB Mainz): Do you want to be in the afternoon? 359 00:59:01.080 --> 00:59:02.830 Susan Kimball: Thank you. 360 00:59:03.620 --> 00:59:07.679 Susan Kimball: If I do that, I will probably lean on… 361 00:59:07.940 --> 00:59:20.029 Susan Kimball: you, Katie, or Cornelia to help me with in-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… 362 00:59:20.190 --> 00:59:34.170 Susan Kimball: physically there, it's very helpful to have a co-conspirator physically there, to help to make sure. Even just, like, passing the mic around so people can ask questions of the speaker, 363 00:59:34.290 --> 00:59:45.339 Susan Kimball: for local, and if there's any technical difficulties, if you're halfway around the world, it's kind of hard to navigate those. You can't call on technical support if you're somewhere else. 364 00:59:48.820 --> 00:59:53.760 Susan Kimball: Alright, thanks for that reminder. I will submit that request now, since the deadline is, like, Wednesday. 365 00:59:54.120 --> 01:00:01.359 Katie Rahman: Yeah, and Susan, if you need any help with that, I am happy to help with that, since I did bring it up. 366 01:00:01.360 --> 01:00:04.479 Susan Kimball: Thank you. You're also doing a workshop, which is a much heavier lift. 367 01:00:04.480 --> 01:00:05.610 Katie Rahman: Yeah, again. 368 01:00:05.940 --> 01:00:08.910 Katie Rahman: Like, don't want to pass the buck. Okay, I may… 369 01:00:08.910 --> 01:00:10.950 Susan Kimball: Can I run my slides by you? 370 01:00:11.190 --> 01:00:12.829 Katie Rahman: Yeah, yeah, that'll work. 371 01:00:12.830 --> 01:00:14.190 Susan Kimball: Awesome. 372 01:00:14.450 --> 01:00:15.620 Susan Kimball: Alright. 373 01:00:16.040 --> 01:00:17.800 Susan Kimball: Any additional… 374 01:00:17.800 --> 01:00:23.549 Cornelia Awenius (UB Mainz): I mean, we will cover… we will cover notes on the workshop as well, so part of it, at least. 375 01:00:23.670 --> 01:00:24.809 Susan Kimball: Yeah. 376 01:00:25.300 --> 01:00:27.420 Susan Kimball: Maybe we can piggyback on that. 377 01:00:27.690 --> 01:00:28.040 Cornelia Awenius (UB Mainz): Yes. 378 01:00:28.040 --> 01:00:28.620 Susan Kimball: That's good. 379 01:00:30.780 --> 01:00:31.990 Susan Kimball: All right. 380 01:00:32.870 --> 01:00:37.070 Susan Kimball: Anything else before we… break. 381 01:00:41.820 --> 01:00:52.210 Susan Kimball: All right, thanks everyone. We will see some of you on Thursday at Fees and Fines. Otherwise, enjoy your calendar-calming week next week. 382 01:00:52.400 --> 01:00:55.810 Susan Kimball: And we will see you at the next meeting. 383 01:00:56.260 --> 01:00:57.649 Susan Kimball: Thanks, everyone! 384 01:00:57.900 --> 01:00:59.429 Scott Peterson: Have a good day. 385 01:00:59.470 --> 01:01:00.870 Anja Kakau | VZG: Bye!