WEBVTT

1
00:06:18.050 --> 00:06:18.920
Tara Barnett (Index Data): Hey everyone!

2
00:06:20.310 --> 00:06:21.170
Laura Daniels: Hello!

3
00:06:22.560 --> 00:06:23.360
Kimberly Smith (MTSU): Hello?

4
00:06:24.320 --> 00:06:31.930
Tara Barnett (Index Data): Someone actually rang my doorbell, and I was like, like, what's going on? I live in an apartment, so that doesn't happen very often. I was very excited.

5
00:06:34.490 --> 00:06:36.170
Tara Barnett (Index Data): The little things in life.

6
00:06:36.760 --> 00:06:39.869
Tara Barnett (Index Data): Alright, let me get screen sharing set up here.

7
00:06:50.220 --> 00:06:51.030
Tara Barnett (Index Data): Sweet.

8
00:06:51.900 --> 00:06:52.880
Tara Barnett (Index Data): Alright.

9
00:06:53.390 --> 00:06:55.650
Tara Barnett (Index Data): And do we have Joe?

10
00:06:57.500 --> 00:06:58.470
Tara Barnett (Index Data): I do have to.

11
00:06:58.600 --> 00:06:59.870
Joe Reimers (EBSCO): No, I'm not here.

12
00:07:03.070 --> 00:07:06.800
Tara Barnett (Index Data): Thank you, disembodied voice of Joe.

13
00:07:07.430 --> 00:07:18.620
Tara Barnett (Index Data): Okay, looks like people are piling in. Hopefully, I did not, again, send people to the wrong Zoom link, but I guess we'll find out on Slack if I did.

14
00:07:18.710 --> 00:07:31.510
Tara Barnett (Index Data): All right, so, to get us started off, we have, just a little bit of housekeeping to take care of. The first is upcoming sessions. We do not have anything scheduled for this coming Monday,

15
00:07:31.610 --> 00:07:49.680
Tara Barnett (Index Data): I will check one more time on Slack if there are any topics, or feel free to shout it out, but if there are no topics, I will go ahead and cancel that. The meeting on Wednesday, April 1st, is going to be canceled for calendar calming. I think that's the week of Easter, which might be

16
00:07:49.740 --> 00:07:51.939
Tara Barnett (Index Data): Why, that's a little bit different than normal?

17
00:07:52.710 --> 00:07:57.610
Tara Barnett (Index Data): So let me know if you have any topics for these, otherwise we'll go ahead and cancel.

18
00:07:58.740 --> 00:08:00.850
Tara Barnett (Index Data): The next thing,

19
00:08:00.910 --> 00:08:14.600
Tara Barnett (Index Data): We are, of course, still in search of a new co-convener. I know that Laura's very interested in being potentially a co-convener, but we need at least two to make it a co-, of course. So we'll keep asking if there's anyone who would like to step up.

20
00:08:14.600 --> 00:08:21.589
Tara Barnett (Index Data): I will, of course, stick around for March and April, and then we'll start figuring out if we have an actual problem on our hands.

21
00:08:21.840 --> 00:08:37.249
Tara Barnett (Index Data): And then the last thing that I wanted to, ask is I created a draft of a cross-app stay working session, but we need to find someone who will actually

22
00:08:37.309 --> 00:08:54.619
Tara Barnett (Index Data): probably be at WolfCon, or at least virtually at WolfCon, to submit this, because I will be neither, and I've been told it's challenging to change, who the speaker is, like the main speaker. So if you'd like to volunteer, let me know, and I'll post again on Slack. I think I already posted this one.

23
00:08:54.940 --> 00:08:59.929
Tara Barnett (Index Data): That's all the housekeeping I have. Did anyone else have any other announcements they wanted to make?

24
00:09:04.550 --> 00:09:11.879
Tara Barnett (Index Data): Okay, sounds good. Alright, so that is you, Joe. Did you want to share your screen, or do you want me to just keep sharing?

25
00:09:13.800 --> 00:09:17.559
Joe Reimers (EBSCO): It doesn't matter, because really all I've got is the page.

26
00:09:18.320 --> 00:09:18.930
Tara Barnett (Index Data): Doctor.

27
00:09:19.350 --> 00:09:19.880
Joe Reimers (EBSCO): Yeah.

28
00:09:22.330 --> 00:09:30.799
Joe Reimers (EBSCO): But yeah, so this actually originated with… Was it Zach Burke?

29
00:09:31.180 --> 00:09:35.559
Joe Reimers (EBSCO): The person responsible for the Stripes team.

30
00:09:35.760 --> 00:09:39.070
Joe Reimers (EBSCO): Raised this with, with me.

31
00:09:39.370 --> 00:09:50.459
Joe Reimers (EBSCO): Basically the core issue is that stuff that was developed very early on for acquisitions that was identified as an acquisitions requirement.

32
00:09:50.880 --> 00:10:00.380
Joe Reimers (EBSCO): Behaves differently than… What is coded in stripes as the default behavior. And…

33
00:10:01.430 --> 00:10:07.609
Joe Reimers (EBSCO): behaviors should be in stripes wherever possible, because we want folio to behave consistently.

34
00:10:08.550 --> 00:10:17.230
Joe Reimers (EBSCO): So, the issue that we're facing is, we've got… business requirements.

35
00:10:17.540 --> 00:10:22.760
Joe Reimers (EBSCO): That exists in acquisitions, and this specifically pertains to… column.

36
00:10:24.520 --> 00:10:31.730
Joe Reimers (EBSCO): Facets and filters, like, pre-selected filters in given, applications.

37
00:10:31.780 --> 00:10:44.529
Joe Reimers (EBSCO): So, I believe the Stripes default is when you enter an application, nothing is selected. But in Acquisitions, the Acquisitions module remembers what was last selected.

38
00:10:44.860 --> 00:10:54.079
Joe Reimers (EBSCO): And so, your pre-selected filters will carry on from session to session.

39
00:10:55.010 --> 00:11:03.699
Joe Reimers (EBSCO): The problem with that is, if a user copies and pastes a URL, it's going to behave differently.

40
00:11:04.200 --> 00:11:09.230
Joe Reimers (EBSCO): So this is where we… I said, you know.

41
00:11:10.690 --> 00:11:16.080
Joe Reimers (EBSCO): The acquisition SIG, I think, is generally happy with the behavior.

42
00:11:16.400 --> 00:11:22.109
Joe Reimers (EBSCO): But it's inconsistent with folio at large. So I wanted to come to…

43
00:11:22.310 --> 00:11:36.219
Joe Reimers (EBSCO): this broader group, this broader cross-app group, to discuss ways in which we might possibly find the best of both worlds, or how do we resolve this conflict? Because,

44
00:11:36.550 --> 00:11:38.430
Joe Reimers (EBSCO): Having one app.

45
00:11:38.810 --> 00:11:46.869
Joe Reimers (EBSCO): with separate behaviors. Again, inconsistency isn't good, but it's also challenging, just in terms of

46
00:11:47.030 --> 00:11:57.339
Joe Reimers (EBSCO): Testing and migration and translations, and all of those little under… other underlying things that feed into, Stripes.

47
00:11:59.270 --> 00:12:04.709
Joe Reimers (EBSCO): So that's… that's really why I'm… I'm… I'm coming to you, because we do have a business need.

48
00:12:04.900 --> 00:12:07.120
Joe Reimers (EBSCO): For creating durable filters.

49
00:12:07.640 --> 00:12:10.900
Joe Reimers (EBSCO): But I also recognize that that's not necessarily universal.

50
00:12:11.880 --> 00:12:14.949
Joe Reimers (EBSCO): Laurel, Laura, I see you have your hand up.

51
00:12:15.880 --> 00:12:29.920
Laura Daniels: Yeah, I was thinking about this when I read this, and hearing you talk about it, thinking about it again, that I could see a lot of area… other places where some users really might want and benefit from durable filters.

52
00:12:30.070 --> 00:12:45.550
Laura Daniels: And so my ideal solution to this is probably a whole lot of work, but would be to… to make this personalizable across Folio… across the app, so that in every app.

53
00:12:45.810 --> 00:12:58.870
Laura Daniels: The filters are not… By default, sticky, but, each user or institution could set…

54
00:12:59.830 --> 00:13:09.690
Laura Daniels: filters, and I'm thinking of something like in inventory, if something is staff suppressed. Some institutions really want that always

55
00:13:10.000 --> 00:13:17.790
Laura Daniels: to be, not true for the default. Others want it to not be not true.

56
00:13:18.290 --> 00:13:21.730
Laura Daniels: So I, I see some potential here to…

57
00:13:21.990 --> 00:13:31.000
Laura Daniels: To come up with a better experience for everyone, if it's possible to prioritize that work for personalization.

58
00:13:32.160 --> 00:13:35.739
Joe Reimers (EBSCO): I'm not opposed to, it might be a lot of work.

59
00:13:35.870 --> 00:13:42.659
Joe Reimers (EBSCO): I know there's… A growing number of, of,

60
00:13:43.050 --> 00:13:46.329
Joe Reimers (EBSCO): Cases where we're starting to do personalization work.

61
00:13:46.520 --> 00:14:00.899
Joe Reimers (EBSCO): And this does seem like it would be a good candidate, which is why I wanted… one of the reasons I wanted to discuss it more thoroughly here. Especially if I can dump it onto Stripes rather than keeping it in ThunderJet. That would make me ecstatic. But,

62
00:14:02.210 --> 00:14:05.819
Joe Reimers (EBSCO): Yeah, so, I definitely don't want to discount that.

63
00:14:05.930 --> 00:14:10.770
Joe Reimers (EBSCO): But I think… Yeah.

64
00:14:11.350 --> 00:14:14.289
Joe Reimers (EBSCO): Kristen, I see you've got your hand up as well.

65
00:14:14.920 --> 00:14:21.499
Kristin Martin: Yeah, this is just a question, if this is part of why the behavior's different, so…

66
00:14:21.870 --> 00:14:31.010
Kristin Martin: In reg… like, if you're in orders right now, and you do… You do a search,

67
00:14:31.260 --> 00:14:38.239
Kristin Martin: and you open up, say, like, a PO line, let's just, say, and you do another search.

68
00:14:38.630 --> 00:14:42.699
Kristin Martin: It doesn't close the peel line that you're looking at, you know?

69
00:14:43.150 --> 00:14:49.940
Kristin Martin: But if you're in inventory, it closes, like, the record that you're… we're currently looking at.

70
00:14:50.200 --> 00:14:57.410
Kristin Martin: Is that also going to be part of this change, or is that, like, a separate, issue?

71
00:14:57.860 --> 00:15:00.090
Kristin Martin: Because sometimes it throws people off.

72
00:15:02.280 --> 00:15:07.940
Kristin Martin: Like, you know, they… do you know what I'm saying? Like, if you do a search, especially, like, if you do, like, a general search.

73
00:15:08.070 --> 00:15:15.900
Kristin Martin: for a… and then you're like, oh, you know what, I actually… I have this really specific number, and then you can do a search for that number. You'll see the results

74
00:15:16.110 --> 00:15:22.129
Kristin Martin: in… Your details, but then what's actually open is not going to be related to your search anymore.

75
00:15:22.400 --> 00:15:23.220
Kristin Martin: Right.

76
00:15:23.600 --> 00:15:28.380
Joe Reimers (EBSCO): That hadn't been factored in, but, I…

77
00:15:28.530 --> 00:15:37.360
Joe Reimers (EBSCO): Definitely think it's something that could be added to the page as an additional aspect of the problem.

78
00:15:37.690 --> 00:15:44.010
Joe Reimers (EBSCO): So, I'm glad… I'm glad you… you mentioned that, because this is some… another thing that we probably should raise with stripes.

79
00:15:44.010 --> 00:15:45.050
Kristin Martin: Because it got…

80
00:15:45.600 --> 00:15:49.490
Joe Reimers (EBSCO): This… this is about… this is about consistency across apps.

81
00:15:52.300 --> 00:15:59.109
Joe Reimers (EBSCO): And so, related to that, what should the behavior be? I would assume that in most cases, if you're

82
00:15:59.450 --> 00:16:18.180
Joe Reimers (EBSCO): working in multiple areas or tabs, and you have to switch back and forth, you would want some memory of where you were working. I know in acquisitions, it's particularly important because so many various components of the system are impacted.

83
00:16:18.330 --> 00:16:22.669
Joe Reimers (EBSCO): I don't know enough about inventory to,

84
00:16:23.800 --> 00:16:28.450
Joe Reimers (EBSCO): To… to say for certain why that decision would have been made, but…

85
00:16:29.070 --> 00:16:35.510
Kristin Martin: Yeah, I think, you know, I like where Laura was going here, too, is just,

86
00:16:35.830 --> 00:16:42.490
Kristin Martin: Like, I know right now, if I'm working in acquisitions versus working in inventory, it just works different.

87
00:16:42.820 --> 00:16:58.640
Kristin Martin: And so I've gotten in the habit of, like, oh, if I'm doing a search in orders, I better make sure there's no filters on that I don't want, because I had previously done a search that used these filters. So I think the idea of maybe making it customizable

88
00:16:58.890 --> 00:17:02.989
Kristin Martin: would be really helpful. Maybe some people really like that, maybe they don't, you know?

89
00:17:03.140 --> 00:17:05.620
Kristin Martin: So, I like that direction.

90
00:17:08.329 --> 00:17:14.649
Joe Reimers (EBSCO): Oh, and I see you've got your hand up, and I saw, Tara, you posted an important question in the chat as well, so go ahead, Owen.

91
00:17:17.640 --> 00:17:21.389
Owen Stephens: Yeah, so… First of all, though, I'd say

92
00:17:21.760 --> 00:17:29.590
Owen Stephens: Orders isn't the only app that has maybe some… some different behaviour.

93
00:17:29.790 --> 00:17:39.580
Owen Stephens: Around filters, and it's something that's been… An issue in agreements, And…

94
00:17:40.580 --> 00:17:44.639
Owen Stephens: Well, mainly agreements, I think, as well, which is that

95
00:17:46.040 --> 00:17:55.559
Owen Stephens: We've always had a default set of filters that are applied, automatically, on visiting the app.

96
00:17:56.540 --> 00:18:05.729
Owen Stephens: Which… Which is kind of partly because, I mean, essentially.

97
00:18:06.030 --> 00:18:08.940
Owen Stephens: the reasoning, I suppose, goes initially that

98
00:18:09.390 --> 00:18:14.759
Owen Stephens: If you've got a set of things where some things are shown and some things are not.

99
00:18:14.950 --> 00:18:18.840
Owen Stephens: And you have… some,

100
00:18:19.090 --> 00:18:26.639
Owen Stephens: Like, orders or, like, agreements where those things that are in the past and no longer active are really

101
00:18:26.900 --> 00:18:33.000
Owen Stephens: are rarely of interest to the current user. I mean, not never. Obviously, sometimes you want to find the specific thing.

102
00:18:33.410 --> 00:18:40.290
Owen Stephens: But often you're dealing with, you know, what is currently active on the system.

103
00:18:40.440 --> 00:18:45.370
Owen Stephens: then… Having the user have to click that filter every time.

104
00:18:45.540 --> 00:18:48.119
Owen Stephens: Feels like an imposition on the user.

105
00:18:48.890 --> 00:18:55.090
Owen Stephens: and not great usability. So, so Agreements has some default filters.

106
00:18:55.260 --> 00:18:58.900
Owen Stephens: They don't work in quite the same way as the…

107
00:18:59.150 --> 00:19:02.310
Owen Stephens: orders once, and that leads to some…

108
00:19:02.740 --> 00:19:12.229
Owen Stephens: different behavior, so the exact issue, I think, that led to this being raised in the first place was that if you paste a URL in orders.

109
00:19:12.450 --> 00:19:19.260
Owen Stephens: Actually, then the… filters are applied on top of the URL you have pasted, so…

110
00:19:19.570 --> 00:19:29.859
Owen Stephens: you kind of get a situation where the user's pasting a URL and then really not getting the results they're expecting. In agreements, we always…

111
00:19:30.400 --> 00:19:35.429
Owen Stephens: defer to what has been put into the address bar. So the address bar is the lead

112
00:19:35.590 --> 00:19:41.479
Owen Stephens: Thing, not the, not… the app never overrides what's been put into the address bar.

113
00:19:42.510 --> 00:19:56.500
Owen Stephens: So there's some different behavior there, but I think probably, like, the reasons at the heart of why agreements behave differently, you know, overlap at least, or are the same for why orders behaves differently in terms of

114
00:19:56.500 --> 00:20:04.139
Owen Stephens: the desire for use… from the desired behavior from a user perspective. And we have always kind of said.

115
00:20:05.200 --> 00:20:10.420
Owen Stephens: Making it customizable per user is probably the ultimate like…

116
00:20:11.050 --> 00:20:14.390
Owen Stephens: behavior you'd want here, that they could define

117
00:20:14.540 --> 00:20:20.990
Owen Stephens: the default filters that are used. And I guess that actually in…

118
00:20:21.250 --> 00:20:24.350
Owen Stephens: Inventory, there's kind of a bit of a…

119
00:20:24.630 --> 00:20:32.359
Owen Stephens: a cheat to this, which is there's the staff-suppressed thing that I think Just automatically applies unless you…

120
00:20:33.030 --> 00:20:34.570
Owen Stephens: kind of…

121
00:20:34.900 --> 00:20:38.060
Laura Daniels: It… that was changed, because so many of us.

122
00:20:38.060 --> 00:20:38.610
Owen Stephens: Okay.

123
00:20:38.610 --> 00:20:40.060
Laura Daniels: problems with it.

124
00:20:40.880 --> 00:20:52.349
Owen Stephens: So… so that… yeah, so that was a behavior, but it's just that this… this idea of automatically having some filters is a desirable behaviour, and I… I do think…

125
00:20:52.640 --> 00:20:53.550
Owen Stephens: that.

126
00:20:53.880 --> 00:21:03.790
Owen Stephens: having customizable options is probably the right way to go here. I do think, still, You shh…

127
00:21:04.180 --> 00:21:15.459
Owen Stephens: if somebody pastes something into the browser bar, I think overwriting that is dangerous. I think that that… that stops sharing… that stops users sharing links, and I think that that should be something that we should

128
00:21:15.630 --> 00:21:25.849
Owen Stephens: not do. I think that we… I think whatever solution here has to avoid a situation where you can't freely share a link with a colleague and… and have the behavior

129
00:21:26.110 --> 00:21:42.070
Owen Stephens: essentially have them see what you, you know, what you expect them to see. But, I think that having some ability to customize default filters, maybe even having some way of applying a set of filters that you've previously saved.

130
00:21:44.410 --> 00:21:57.420
Owen Stephens: rather than having to click through every… every filter that you want to apply to a particular scenario would be a really good idea. And… and to some extent, that is also something that we do in the…

131
00:21:57.600 --> 00:22:00.930
Owen Stephens: dashboard app is that actually

132
00:22:01.320 --> 00:22:06.900
Owen Stephens: What that allows the user to do is to save a set of filters, which,

133
00:22:08.010 --> 00:22:15.909
Owen Stephens: are used automatically. It's a bit of a different scenario, but it… but it's… I think, ultimately, it's the same idea, that

134
00:22:16.150 --> 00:22:29.629
Owen Stephens: some searches are more useful than others, and you might want to do them on a regular basis, and therefore, being able to access those searches and filters very easily is a good behavior. So, certainly very much in favor of

135
00:22:30.080 --> 00:22:39.620
Owen Stephens: having this customizable both at a tenant level, I think tenant level options are good, but I think ultimately you need it at a personal level, because,

136
00:22:40.360 --> 00:22:46.079
Owen Stephens: Staff… different members of staff will have different purposes that they go to the search screen to…

137
00:22:46.310 --> 00:22:58.519
Owen Stephens: to fulfill, and I think that that's really important. You know, if you're only dealing with monograph orders, why not have that as a filter that you've, you know, you're starting with? You don't need all the rest of the

138
00:22:58.660 --> 00:23:00.230
Owen Stephens: The stuff in there, so…

139
00:23:00.460 --> 00:23:16.679
Owen Stephens: Yeah, that's a long-winded way of saying, I'm with you, Joe. I do think there are some things we need to be careful about in terms of how pasting URLs work specifically, but in general, I think having some level of customizing both at the tenant and at the

140
00:23:17.850 --> 00:23:21.989
Owen Stephens: Personal user level is where we need to go, ultimately.

141
00:23:23.280 --> 00:23:27.610
Joe Reimers (EBSCO): Yeah, the… where we do the custom… where we would do that… that setting of things.

142
00:23:27.840 --> 00:23:33.430
Joe Reimers (EBSCO): I think it's safe to assume that most people

143
00:23:33.800 --> 00:23:38.549
Joe Reimers (EBSCO): Given the option, would prefer that it be personal rather than tenant-wide.

144
00:23:39.350 --> 00:23:44.050
Joe Reimers (EBSCO): And I'm… I'm thinking a small library would probably be fine.

145
00:23:44.260 --> 00:23:46.520
Joe Reimers (EBSCO): with tenant-wide.

146
00:23:46.920 --> 00:23:55.960
Joe Reimers (EBSCO): Just based on their workflows, but when you get into larger institutions, where you have specialized staff that work in specialized areas.

147
00:23:56.250 --> 00:24:02.140
Joe Reimers (EBSCO): that… That could actually be counterproductive, because then you'd have,

148
00:24:02.320 --> 00:24:11.349
Joe Reimers (EBSCO): For instance, if you have acquisitions and serials acquisitions that are separate, or e-resource acquisitions that are all separate.

149
00:24:12.220 --> 00:24:15.490
Joe Reimers (EBSCO): They're probably going to want separate

150
00:24:15.680 --> 00:24:19.510
Joe Reimers (EBSCO): Defaults, or different types of defaults, so…

151
00:24:19.760 --> 00:24:24.790
Joe Reimers (EBSCO): In that case, having it durable From session to session.

152
00:24:25.270 --> 00:24:30.489
Joe Reimers (EBSCO): or having a personalized per user would make a lot more sense. So,

153
00:24:31.270 --> 00:24:41.659
Joe Reimers (EBSCO): I think, in terms of doing it… I mean, I'm kind of of the opinion, even if it's more work, let's do it right the first time, especially since we are now introducing

154
00:24:41.970 --> 00:24:42.860
Joe Reimers (EBSCO): Aww.

155
00:24:43.690 --> 00:24:44.520
Joe Reimers (EBSCO): Oh.

156
00:24:45.140 --> 00:24:47.320
Joe Reimers (EBSCO): Some level of personalization.

157
00:24:47.700 --> 00:24:52.439
Joe Reimers (EBSCO): the other… the other question then would be…

158
00:24:52.940 --> 00:24:57.239
Joe Reimers (EBSCO): With the personalization, because we don't want death by a thousand paper cuts.

159
00:24:57.620 --> 00:25:02.310
Joe Reimers (EBSCO): Would we want it, like, for me?

160
00:25:02.570 --> 00:25:10.070
Joe Reimers (EBSCO): portfolio, remember all my settings, or would we want to break it down, say, by… app.

161
00:25:10.710 --> 00:25:15.309
Joe Reimers (EBSCO): or buy some other area, because I don't… I don't want it…

162
00:25:18.110 --> 00:25:23.770
Joe Reimers (EBSCO): I'm assuming if you want it in orders, you'll probably also want it in invoices and receiving.

163
00:25:24.100 --> 00:25:25.370
Joe Reimers (EBSCO): I could be wrong.

164
00:25:25.540 --> 00:25:31.930
Joe Reimers (EBSCO): But, like, does it make sense to do it in app acquisitions, or do I have to do it for each…

165
00:25:32.450 --> 00:25:33.320
Joe Reimers (EBSCO): Old.

166
00:25:33.950 --> 00:25:36.769
Joe Reimers (EBSCO): each little sub-component.

167
00:25:38.810 --> 00:25:44.180
Joe Reimers (EBSCO): I guess. It's… yeah, the question is, what is… what is the sweet spot in terms of granularity?

168
00:25:51.900 --> 00:25:56.380
Joe Reimers (EBSCO): Does personalization here remember the last thing I did, or set defaults?

169
00:25:56.540 --> 00:26:01.730
Joe Reimers (EBSCO): I was thinking remember the last thing I did.

170
00:26:02.210 --> 00:26:04.929
Joe Reimers (EBSCO): Would, like, either remember or don't remember.

171
00:26:05.840 --> 00:26:13.350
Joe Reimers (EBSCO): But… We could certainly look at setting defaults.

172
00:26:13.680 --> 00:26:27.879
Joe Reimers (EBSCO): although setting defaults would then require… the setting defaults would require a lot more work, because then we'd need to figure out a place where to set defaults, or save what I've got as the default for this application.

173
00:26:29.630 --> 00:26:36.770
Tara Barnett (Index Data): So, Joe, it sounds like you're saying that what you're proposing is app-by-app, or folio-wide, you could set

174
00:26:37.220 --> 00:26:46.769
Tara Barnett (Index Data): for the user to remember the last thing that they did. But I'm also hearing a lot of, like, there should be defaults, and they should be different for different members of staff.

175
00:26:51.680 --> 00:26:57.789
Joe Reimers (EBSCO): I'm not, you know, I'm not necessarily married to a certain… I'm more trying to get to…

176
00:26:58.000 --> 00:27:04.979
Joe Reimers (EBSCO): what would the ideal case be here? We're gonna have to look at this, so that's kind of why I'm coming to you, is…

177
00:27:05.390 --> 00:27:16.929
Joe Reimers (EBSCO): you know, this was, brought to me by Stripes, saying, this is inconsistent. So, if we're gonna make it consistent, I want to do it right, and I want to talk with

178
00:27:19.160 --> 00:27:31.689
Joe Reimers (EBSCO): a group that is invested in folio at large, and in multiple applications, because consistency is key. So if we're going to do it consistently, and if we're going to put it into stripes, how would we want it to work? How can we make this really good?

179
00:27:33.330 --> 00:27:40.160
Tara Barnett (Index Data): I mean, I'm definitely on team defaults, but my job's different from a lot of library users, so…

180
00:27:40.710 --> 00:27:44.360
Tara Barnett (Index Data): But it sounds like there are maybe others here who are also on Team Defaults.

181
00:27:46.420 --> 00:27:47.210
Joe Reimers (EBSCO): I'm…

182
00:27:47.210 --> 00:27:48.909
Laura Daniels: Oh, sorry, go ahead.

183
00:27:49.090 --> 00:27:49.670
Joe Reimers (EBSCO): Go ahead.

184
00:27:49.950 --> 00:27:57.480
Laura Daniels: I was gonna say, I'm very much on team defaults, because I know I'm not always going to Folio to do the same thing.

185
00:27:57.870 --> 00:28:09.830
Laura Daniels: And the apps that do remember what I did last time always throw me, because they're showing me something that was relevant to me last week, maybe. And I think

186
00:28:10.220 --> 00:28:18.610
Laura Daniels: it's rare. There are cases, but I feel like it's rare where a library staff person really only ever does one thing.

187
00:28:23.880 --> 00:28:32.029
Tara Barnett (Index Data): And, like, the behavior in orders right now, at least, seems like it's, like, remember that you searched for newspaper a week ago? Is that right?

188
00:28:32.030 --> 00:28:37.200
Laura Daniels: Yes, and it always makes me wonder what I did wrong, because I'm expecting

189
00:28:37.360 --> 00:28:48.630
Laura Daniels: something different than, you know, what I might have done, literally, because I don't look in orders very often. I don't remember that I did that search, so I think it's making stuff up.

190
00:28:48.820 --> 00:28:58.940
Kristin Martin: Yeah, like, here's an example. So, if you're looking here, for example, we at Chicago should not have any order lines that are in the pending.

191
00:28:59.160 --> 00:29:00.170
Kristin Martin: category.

192
00:29:00.300 --> 00:29:05.169
Kristin Martin: But I might search… I might filter depending to find those out, and be like, oh…

193
00:29:05.300 --> 00:29:18.139
Kristin Martin: these are a problem, because, you know, something went wrong, and somebody didn't finish them, or whatever, so let's figure out what's happening. Then, if I come back to orders later, and I have an actual, like, PO number.

194
00:29:18.650 --> 00:29:37.760
Kristin Martin: I don't want it to be limited to pending. Like, I was doing that search because I, you know, needed to find things that were pending, and it was great, it was easy to find them, I got the report, I exported it out, you know. But when I'm, you know, if I'm searching by a PO number, I don't… I have to just make sure I reset my limits.

195
00:29:37.870 --> 00:29:45.280
Kristin Martin: So, I think that that's a little different, like, I would not choose to have, I only want to look at pending order lines as a default.

196
00:29:45.410 --> 00:29:49.979
Kristin Martin: But I like having that filter as an option to, like, check for it, you know?

197
00:29:53.890 --> 00:29:55.619
Joe Reimers (EBSCO): Maura, I see you have your hand up.

198
00:29:56.770 --> 00:30:02.980
Maura Byrne: Yeah, and this might be, you know, trying to, like.

199
00:30:03.410 --> 00:30:07.150
Maura Byrne: Come up with a technical solution before we've defined what we want.

200
00:30:07.590 --> 00:30:16.920
Maura Byrne: But what that sounds like to me is that, like, you've done this thing, your browser remembers it, at least for the duration of your browser session.

201
00:30:18.750 --> 00:30:26.300
Maura Byrne: And that, you know, it will forget it when you, if you do it again, unless you have something specifically

202
00:30:26.600 --> 00:30:28.560
Maura Byrne: Set as a default.

203
00:30:28.920 --> 00:30:36.400
Maura Byrne: But… you know, sort of, I'm thinking visually, if you have something where

204
00:30:36.810 --> 00:30:39.569
Maura Byrne: Your browser session is going to remember

205
00:30:40.170 --> 00:30:47.559
Maura Byrne: a filter that you put on, then maybe the thing to do is to have the

206
00:30:47.990 --> 00:30:52.159
Maura Byrne: You know, like, the indication of the filter being applied.

207
00:30:52.540 --> 00:30:57.569
Maura Byrne: Being, like, put at the top of this, like, list on the,

208
00:30:57.860 --> 00:31:07.869
Maura Byrne: On the left side here, in the left column, where we have, you know, repeat receipt status, and payment status, and etc, and etc. If that one could sort of be…

209
00:31:08.050 --> 00:31:22.160
Maura Byrne: you know, listed up top to say, oh, by the way, right now, you're filtering for this for at least the duration of this browser session. And if you want that to change, you can, you know, unfilter.

210
00:31:24.250 --> 00:31:35.409
Maura Byrne: So, that's, you know, that might be getting ahead of, you know, what we're… what we're talking about, but it seems like, you know, we're doing, you know.

211
00:31:35.640 --> 00:31:44.090
Maura Byrne: it seems like what we're… what we're looking for, you know, the I-wish involved, is that,

212
00:31:44.220 --> 00:31:52.809
Maura Byrne: We'd like to be able to do things in the short term, and have something remember, you know, in work that you're doing now, which we could call, like.

213
00:31:53.210 --> 00:32:11.360
Maura Byrne: you know, the app remembers it for the duration of the browser session, and then forgets it tomorrow, when you reopen the browser. As opposed to something you can set as a default thing, because it's something you do every time you're in that app.

214
00:32:12.230 --> 00:32:15.369
Maura Byrne: Do I… do I have that right?

215
00:32:16.930 --> 00:32:19.710
Maura Byrne: Yes, Laura.

216
00:32:19.860 --> 00:32:23.380
Maura Byrne: Of course we want folio to read our minds.

217
00:32:23.860 --> 00:32:24.940
Maura Byrne: But.

218
00:32:25.310 --> 00:32:26.660
Joe Reimers (EBSCO): But not with AI.

219
00:32:27.210 --> 00:32:28.550
Maura Byrne: No, no.

220
00:32:28.970 --> 00:32:31.559
Maura Byrne: AI is just a dressed-up Clippy.

221
00:32:32.760 --> 00:32:39.599
Joe Reimers (EBSCO): Yeah, so I agree with what Tara… with what Tara says about, if you paste a URL,

222
00:32:39.960 --> 00:32:42.590
Joe Reimers (EBSCO): the URL should be obeyed hard stop.

223
00:32:42.790 --> 00:32:58.040
Joe Reimers (EBSCO): And I think we agree with that. And I think that's one of the stated outcomes that we need. So, Tara, I'm going to put your mind at rest. That is one of the acceptance criteria for doing this, because URLs do need to behave consistently across the board.

224
00:32:59.880 --> 00:33:05.840
Joe Reimers (EBSCO): what I was going to ask is… so we're on… this is actually a really good screen to be on.

225
00:33:06.290 --> 00:33:07.460
Joe Reimers (EBSCO): Where…

226
00:33:08.860 --> 00:33:22.330
Joe Reimers (EBSCO): how would… what would be the process, workflow, UX, whatever, that you would expect if you want to set a default search slash filter?

227
00:33:23.430 --> 00:33:27.209
Joe Reimers (EBSCO): Like, how would you want to say, I'm here in orders.

228
00:33:27.370 --> 00:33:29.390
Joe Reimers (EBSCO): this is what I want as the default.

229
00:33:29.680 --> 00:33:33.239
Joe Reimers (EBSCO): Because… If we try to go into Settings.

230
00:33:34.350 --> 00:33:39.169
Joe Reimers (EBSCO): And do that for every screen. It's gonna be death by a thousand paper cuts.

231
00:33:43.190 --> 00:33:48.209
Tara Barnett (Index Data): So you're picturing, like, like, kind of… I don't know if I can bring one of these up,

232
00:33:49.230 --> 00:33:56.609
Tara Barnett (Index Data): I'm sure someone knows what I'm about to say, but, like, you know, like, these little buggers here? Like, you're picturing one of those up here.

233
00:33:56.740 --> 00:33:59.139
Tara Barnett (Index Data): Where you could set defaults or something like that?

234
00:34:00.150 --> 00:34:02.650
Joe Reimers (EBSCO): It's just something somewhere.

235
00:34:03.390 --> 00:34:15.049
Joe Reimers (EBSCO): like, and I'll probably need… I'll need to talk with Kimmy about it too, but, like, what would be quick, easy, painless, not take up too much real estate, and… and just make sense?

236
00:34:15.270 --> 00:34:15.780
Joe Reimers (EBSCO): Because, like…

237
00:34:15.780 --> 00:34:16.920
Tara Barnett (Index Data): Like, something appear.

238
00:34:18.409 --> 00:34:18.919
Joe Reimers (EBSCO): Yeah.

239
00:34:18.920 --> 00:34:26.570
Laura Daniels: Yeah, I think being over on the search and filter side would make more sense than over on the actions side.

240
00:34:27.510 --> 00:34:41.839
Tara Barnett (Index Data): Yeah, I was picturing, like, little… little… whatever icon means default to all humans in existence, like, on this thing. But this seems like… mostly, I just want to know what… what Kimmy says, because…

241
00:34:42.440 --> 00:34:45.660
Tara Barnett (Index Data): The last suggestion was great, and even smarter than me.

242
00:34:49.820 --> 00:34:51.060
Joe Reimers (EBSCO): Kimmy is so good.

243
00:34:55.400 --> 00:35:04.240
Joe Reimers (EBSCO): But yeah, if I walk in with, like, a bad idea, then she'll take it and make it way, way, way better, rather than if I walk in with no idea.

244
00:35:05.200 --> 00:35:07.929
Tara Barnett (Index Data): We've got at least two medium… okay.

245
00:35:07.930 --> 00:35:16.739
Joe Reimers (EBSCO): Yeah, yeah, so, but I'm definitely getting loud and clear that having it in the search and filter bar somewhere, and maybe having a little icon.

246
00:35:17.070 --> 00:35:28.450
Joe Reimers (EBSCO): Or… or in the orders drop-down, or something like that. Just… Set his, you know, Yeah, set default filter.

247
00:35:32.930 --> 00:35:34.680
Joe Reimers (EBSCO): Owen is asking…

248
00:35:35.610 --> 00:35:46.050
Joe Reimers (EBSCO): Do we need to collect user stories about when it's useful to preserve the last filter, and when it's useful to have defaults, and when it's useful to have no filter set?

249
00:35:46.270 --> 00:35:48.269
Joe Reimers (EBSCO): I think it would be worth doing.

250
00:35:48.380 --> 00:35:52.540
Joe Reimers (EBSCO): I think in the absence of that, it makes sense

251
00:35:52.960 --> 00:35:56.869
Joe Reimers (EBSCO): To have memory within a folio session.

252
00:35:57.180 --> 00:36:01.400
Joe Reimers (EBSCO): And defaults on a clean login.

253
00:36:05.730 --> 00:36:07.549
Joe Reimers (EBSCO): But that's just me.

254
00:36:08.250 --> 00:36:14.999
Joe Reimers (EBSCO): like, if I log out and log back in, I should expect everything to be clean. If I'm staying logged in, I'd want the memory, but…

255
00:36:15.980 --> 00:36:17.649
Joe Reimers (EBSCO): On the sample size of 1.

256
00:36:26.870 --> 00:36:29.119
Joe Reimers (EBSCO): Hard refresh also resets, yeah.

257
00:36:35.420 --> 00:36:43.490
Laura Daniels: In my work, I am more likely to be frustrated by a filter still being applied that I forgot I set.

258
00:36:43.590 --> 00:36:48.590
Laura Daniels: than I am by having to set the filter, but that's also sample size of 1.

259
00:36:54.650 --> 00:36:55.540
Joe Reimers (EBSCO): you know.

260
00:36:56.400 --> 00:36:56.840
Maura Byrne: Oh, sorry.

261
00:36:56.840 --> 00:36:58.709
Joe Reimers (EBSCO): I'm just… go ahead.

262
00:36:59.170 --> 00:37:03.069
Maura Byrne: I was wondering, to follow up on Laura's,

263
00:37:03.840 --> 00:37:10.339
Maura Byrne: question, and the notion that, you know, like, if you send a URL and you want it to behave the way that

264
00:37:10.510 --> 00:37:14.410
Maura Byrne: the URL, you know, is set.

265
00:37:14.950 --> 00:37:17.439
Maura Byrne: And not, sort of, override anything.

266
00:37:18.570 --> 00:37:22.489
Maura Byrne: Do you want, does that mean that…

267
00:37:23.590 --> 00:37:33.470
Maura Byrne: Does that mean that the app contains the filter and continues to contain the filter that's included in the URL until, like, you close that tab.

268
00:37:33.740 --> 00:37:35.520
Maura Byrne: And open a new one.

269
00:37:35.760 --> 00:37:40.430
Maura Byrne: Or does that filter propagate for the remainder of your browser session?

270
00:37:40.790 --> 00:37:44.929
Maura Byrne: In which case, you can… someone can…

271
00:37:45.270 --> 00:37:49.920
Maura Byrne: Inadvertently, set filters for you.

272
00:37:50.080 --> 00:38:01.430
Maura Byrne: by sending you a URL, and then you click on it, there's a filter being sent to get you the data you're looking for, and then when you come back to do something else, that filter is still

273
00:38:01.950 --> 00:38:03.410
Maura Byrne: is still working.

274
00:38:08.040 --> 00:38:10.010
Maura Byrne: And thus might confuse you.

275
00:38:10.660 --> 00:38:13.389
Joe Reimers (EBSCO): No, it's clear, it's something to think about.

276
00:38:19.580 --> 00:38:29.009
Joe Reimers (EBSCO): I see Charlotte's comment about, an alternative to listing in the top of the search. Have a colored icon next to the given filter being selected as default.

277
00:38:29.270 --> 00:38:35.330
Joe Reimers (EBSCO): I was thinking about, like, right under… I'm just spitballing here, right under the search and filter.

278
00:38:35.960 --> 00:38:42.809
Joe Reimers (EBSCO): As you check and uncheck, you have, like, a box that basically creates… shows you exactly

279
00:38:42.920 --> 00:38:45.980
Joe Reimers (EBSCO): what's in real time. So, orders right underneath…

280
00:38:46.380 --> 00:38:53.120
Joe Reimers (EBSCO): Orders, or above where, like, the little tabs, have a box that… because right now, it's just pending.

281
00:38:54.780 --> 00:39:03.779
Joe Reimers (EBSCO): So the… just… it only has status appending, and then as you add additional things, the box up top just fills in automatically.

282
00:39:03.910 --> 00:39:07.829
Joe Reimers (EBSCO): And when you set anything, then there's a little button saying, set default.

283
00:39:08.400 --> 00:39:11.259
Joe Reimers (EBSCO): could possibly be a way, yeah.

284
00:39:14.610 --> 00:39:21.179
Joe Reimers (EBSCO): Because right now, yeah, we see status and order type are both selected, so I'm seeing, like, a little box right at the top.

285
00:39:21.690 --> 00:39:28.649
Joe Reimers (EBSCO): Either under… right underneath search and filter and above orders, or right below orders, something.

286
00:39:28.850 --> 00:39:38.930
Joe Reimers (EBSCO): Where it says… Orders, status equals pending, and order type equals… Whatever.

287
00:39:41.530 --> 00:39:45.299
Joe Reimers (EBSCO): So that you know… you see right at the top.

288
00:39:45.770 --> 00:40:01.919
Joe Reimers (EBSCO): that is the active filter. Precise… that is the precise filter. My only hesitation on, like, color coding and stuff is some apps have very, very long lists of filters, so you have to scroll through the whole list to see anything that's potentially filterable.

289
00:40:03.330 --> 00:40:10.160
Joe Reimers (EBSCO): We're having a box at the top saying, Yeah.

290
00:40:11.290 --> 00:40:13.570
Joe Reimers (EBSCO): Yeah, reset all is…

291
00:40:13.810 --> 00:40:20.599
Joe Reimers (EBSCO): mostly… yeah, if you see reset all, that's usually correct, except I know for a fact we have an open bug for that, and…

292
00:40:21.200 --> 00:40:26.039
Joe Reimers (EBSCO): one of our apps where it's coming up is Reset All when it shouldn't, and…

293
00:40:26.620 --> 00:40:30.360
Joe Reimers (EBSCO): We are planning to get to that when we're able to.

294
00:40:31.220 --> 00:40:31.970
Joe Reimers (EBSCO): Fucked.

295
00:40:32.330 --> 00:40:35.040
Joe Reimers (EBSCO): Yeah, colors do add accessibility issues.

296
00:40:36.890 --> 00:40:45.230
Joe Reimers (EBSCO): The little X is a good indication that something in there is selected, but not exactly what. That's why I was thinking having a box up top, because that would just be very clear.

297
00:40:46.710 --> 00:40:52.379
Joe Reimers (EBSCO): And again, I'm sure Kimmy will have a thousand and one thoughts about the way we could handle this.

298
00:40:59.330 --> 00:41:02.930
Joe Reimers (EBSCO): But yeah, some sort of… we definitely need some sort of visual clue.

299
00:41:06.890 --> 00:41:15.760
Tara Barnett (Index Data): So on the assumption that, an expert's going to come back with the best of all possible how-to-make-it-look-nice options,

300
00:41:16.530 --> 00:41:27.179
Tara Barnett (Index Data): going back to, do we need to collect user stories about when it's useful to preserve the last filter? Is that something that the cross-app SIG will need to do?

301
00:41:28.910 --> 00:41:30.260
Tara Barnett (Index Data): Yes, probably.

302
00:41:30.520 --> 00:41:39.960
Joe Reimers (EBSCO): I think it would be helpful. I can certainly bring it to the acquisition SIG, and I think, you know, people who have

303
00:41:40.830 --> 00:41:41.820
Joe Reimers (EBSCO): Aww.

304
00:41:42.320 --> 00:41:46.879
Joe Reimers (EBSCO): who are engaged with other SIGs, I think that would be very, very useful.

305
00:41:47.150 --> 00:41:57.530
Joe Reimers (EBSCO): Just because, yeah, I mean, I think the various SIGs should, Should evaluate this, because…

306
00:41:58.040 --> 00:42:02.690
Joe Reimers (EBSCO): that those are where the real subject matters are, so… .

307
00:42:04.580 --> 00:42:14.139
Tara Barnett (Index Data): Okay, so this seems like a case where, like, because it could potentially affect everyone, we have to make sure that we hit every single app that could be affected, right? Yeah.

308
00:42:14.470 --> 00:42:20.420
Tara Barnett (Index Data): So, maybe, maybe we should do something… Slightly more…

309
00:42:22.260 --> 00:42:24.420
Tara Barnett (Index Data): Shop around to our favorite sigs.

310
00:42:24.830 --> 00:42:26.110
Joe Reimers (EBSCO): Yeah, I'll reach out.

311
00:42:26.110 --> 00:42:26.970
Tara Barnett (Index Data): tables.

312
00:42:27.230 --> 00:42:33.549
Joe Reimers (EBSCO): Is anybody here, part of Resource Access? If not, I'll ask Ann or Steph to…

313
00:42:33.910 --> 00:42:35.430
Joe Reimers (EBSCO): Raise the issue with them.

314
00:42:37.700 --> 00:42:41.660
Tara Barnett (Index Data): Well, I think we need to form the question really specifically, because it's like.

315
00:42:41.940 --> 00:42:42.730
Joe Reimers (EBSCO): Yeah.

316
00:42:42.730 --> 00:42:45.330
Tara Barnett (Index Data): It's, it's hard to say, like,

317
00:42:45.650 --> 00:43:00.360
Tara Barnett (Index Data): when it's useful to preserve the last filter, because, like, the example that I thought of immediately was, like, when you're checking stuff out, and, like, you've got your patron here, and then you pop over to look at the patron, and then it takes you right back to the checkout screen, and that sticks around, but also…

318
00:43:00.470 --> 00:43:06.690
Tara Barnett (Index Data): I think while you're checking things out, the user sticks around, but that might be a function of actually what's in the URL.

319
00:43:06.950 --> 00:43:07.440
Joe Reimers (EBSCO): Mmm.

320
00:43:08.320 --> 00:43:12.829
Tara Barnett (Index Data): Because I don't actually know how that's set, because I think if you go back to users after that, it will…

321
00:43:13.440 --> 00:43:17.379
Tara Barnett (Index Data): If after you end your checkout session, it'll be blank again, I think.

322
00:43:18.650 --> 00:43:23.870
Maura Byrne: I think that's how we have it designed, so that, you know, privacy.

323
00:43:25.350 --> 00:43:30.620
Tara Barnett (Index Data): Yeah, I mean, this is really easy to check. So it takes us straight to the user, you close out of that, and it's blank.

324
00:43:31.320 --> 00:43:35.050
Tara Barnett (Index Data): Right? But then I go back to checkout, and it's still up because I didn't end the session.

325
00:43:36.720 --> 00:43:37.300
Maura Byrne: Right.

326
00:43:37.300 --> 00:43:42.920
Tara Barnett (Index Data): So I don't know if that counts or not, right? Because, like, that's going straight to a record rather than remembering a search.

327
00:43:46.790 --> 00:43:48.769
Joe Reimers (EBSCO): No, but it's a pattern we need to be aware of.

328
00:43:49.050 --> 00:43:50.889
Joe Reimers (EBSCO): Because maybe that's a better pattern.

329
00:43:57.100 --> 00:43:58.860
Joe Reimers (EBSCO): So, no, I do think it's relevant.

330
00:44:01.940 --> 00:44:02.650
Tara Barnett (Index Data): Sweet.

331
00:44:06.340 --> 00:44:07.880
Tara Barnett (Index Data): Any other discussion?

332
00:44:07.880 --> 00:44:13.419
Laura Daniels: I'm wondering if maybe our next meeting, we want to try to…

333
00:44:13.740 --> 00:44:22.819
Laura Daniels: craft, some sort of, you know, just a couple slides and some prompts for us to take to SIGS, so we're all…

334
00:44:23.330 --> 00:44:26.520
Laura Daniels: Asking the same questions.

335
00:44:27.000 --> 00:44:28.190
Tara Barnett (Index Data): That's a great idea.

336
00:44:28.580 --> 00:44:29.120
Tara Barnett (Index Data): Yeah.

337
00:44:29.120 --> 00:44:32.750
Joe Reimers (EBSCO): Yeah, I think that's… I was gonna say we could also consider doing a,

338
00:44:32.880 --> 00:44:40.520
Joe Reimers (EBSCO): like a… a Google survey or something, but yeah, we do… we absolutely need to be clear and consistent on the,

339
00:44:41.220 --> 00:44:47.259
Joe Reimers (EBSCO): Messaging. What time… what time is the Monday meeting?

340
00:44:47.840 --> 00:44:49.540
Tara Barnett (Index Data): Same as this one, just on Mondays.

341
00:44:50.370 --> 00:44:52.619
Joe Reimers (EBSCO): Okay, that one I have a conflict.

342
00:44:53.080 --> 00:44:54.090
Tara Barnett (Index Data): Okay.

343
00:44:59.930 --> 00:45:02.650
Tara Barnett (Index Data): Could we draft it and send it to you for feedback?

344
00:45:02.970 --> 00:45:09.410
Joe Reimers (EBSCO): Yeah, that's absolutely fine. And in fact, the page that I have set up,

345
00:45:09.590 --> 00:45:13.060
Joe Reimers (EBSCO): That we were… yeah, where I'm outlining the problem.

346
00:45:13.230 --> 00:45:22.589
Joe Reimers (EBSCO): Please feel free to edit that, and make additional, you know, feedback, Changes, and so forth.

347
00:45:25.080 --> 00:45:37.300
Joe Reimers (EBSCO): there are a few things that are… that are written in stone. Like the desired outcomes, I think that, at least what I've got there, is what Stripes is asking for.

348
00:45:37.670 --> 00:45:40.709
Joe Reimers (EBSCO): So we can clarify those, but,

349
00:45:43.890 --> 00:45:45.540
Joe Reimers (EBSCO): that's, like…

350
00:45:45.870 --> 00:45:53.450
Joe Reimers (EBSCO): Yeah, if there are additional outcomes, please feel free to add. But the three that I've added, those come from Stripes in terms of what they're expecting.

351
00:45:53.850 --> 00:45:58.130
Joe Reimers (EBSCO): But yeah, this is great, and…

352
00:45:58.360 --> 00:46:02.959
Joe Reimers (EBSCO): like, I'm not claiming ownership over this page.

353
00:46:03.670 --> 00:46:06.900
Joe Reimers (EBSCO): I… yeah, I… I actually would,

354
00:46:07.420 --> 00:46:15.370
Joe Reimers (EBSCO): be very grateful if you would help answer some of these questions, because this is a community thing and not an acquisitions thing. It's just, we need to get

355
00:46:16.020 --> 00:46:20.980
Joe Reimers (EBSCO): Everybody in alignment, and acquisitions is one of the, problem children.

356
00:46:23.930 --> 00:46:25.430
Tara Barnett (Index Data): Not a problem, child.

357
00:46:25.720 --> 00:46:27.060
Tara Barnett (Index Data): Special flower.

358
00:46:27.220 --> 00:46:29.549
Joe Reimers (EBSCO): We're a problem child, I think.

359
00:46:32.060 --> 00:46:39.509
Tara Barnett (Index Data): Well, what a great opportunity to get some cool functionality added that could be useful across different apps.

360
00:46:41.390 --> 00:46:44.049
Tara Barnett (Index Data): It's cool that a problem is becoming a feature.

361
00:46:45.860 --> 00:46:46.290
Joe Reimers (EBSCO): Okay.

362
00:46:46.290 --> 00:46:46.660
Tara Barnett (Index Data): Alright.

363
00:46:47.000 --> 00:46:50.979
Joe Reimers (EBSCO): Cool. Well, thank you so much for your time and for addressing this with me.

364
00:46:52.220 --> 00:47:03.219
Tara Barnett (Index Data): Absolutely, thank you for coming to talk with us. Is there anything else that we should talk about on this subject, or should we, just plan to pick this up on Monday while we're drafting those slides?

365
00:47:03.960 --> 00:47:16.819
Joe Reimers (EBSCO): I think… I think I have… I've said everything that I need to say, everything that I need to say on this, and we've had a really good conversation, so I've got a lot of ideas and a lot more,

366
00:47:17.260 --> 00:47:19.129
Joe Reimers (EBSCO): I'm getting a lot more clarity.

367
00:47:19.570 --> 00:47:27.390
Joe Reimers (EBSCO): And raising a lot more questions, but we're getting closer to the point where we can actually define a feature. So once we have the feedback from the SIGs.

368
00:47:27.530 --> 00:47:33.880
Joe Reimers (EBSCO): I think we can build out the feature, and then I'll coordinate with Stripes on where to go from there.

369
00:47:34.930 --> 00:47:36.610
Joe Reimers (EBSCO): So this is great, thank you.

370
00:47:37.710 --> 00:47:41.039
Tara Barnett (Index Data): Amazing! Any more questions for Joe before we,

371
00:47:42.830 --> 00:47:52.099
Tara Barnett (Index Data): Probably list the SIGs we'll need feedback from. Yeah, we should list the SIGs we need feedback from, but I think we should actually list it app by app, because it's going to be different, per…

372
00:47:52.530 --> 00:47:55.939
Tara Barnett (Index Data): Sorry, per section of folio.

373
00:47:56.140 --> 00:48:01.619
Tara Barnett (Index Data): I'm sure. And which… which SIG owns them. Does that make sense?

374
00:48:02.660 --> 00:48:03.350
Laura Daniels: Yes.

375
00:48:03.730 --> 00:48:23.619
Tara Barnett (Index Data): Okay, awesome. Great. Okay. If we have nothing else to go over today, I will, post what we need to do on Slack, and follow up on the WolfCon, question. But other than that, I think we are good for the day, so I will wish everyone a happy Wednesday, and we'll see you next week!

376
00:48:24.170 --> 00:48:25.130
Tara Barnett (Index Data): Alright, thanks.

377
00:48:25.760 --> 00:48:26.729
Laura Daniels: Thank you!

378
00:48:27.110 --> 00:48:27.890
Joe Reimers (EBSCO): Thanks.

