WEBVTT 1 00:01:51.240 --> 00:01:52.350 Stefan Dombek: Hello. 2 00:01:53.810 --> 00:01:54.700 Julia Eschbach: Bye! 3 00:02:01.500 --> 00:02:02.810 Bernd Oberknapp: Hi, I'm promoting it. 4 00:02:05.590 --> 00:02:06.340 Stefan Dombek: Soon. 5 00:02:07.250 --> 00:02:09.110 Stefan Dombek: I'll share the screen. 6 00:02:11.470 --> 00:02:14.159 Stefan Dombek: So… and this is the right. 7 00:02:15.050 --> 00:02:17.779 Stefan Dombek: So, you should my browser. 8 00:02:28.350 --> 00:02:37.809 Stefan Dombek: the, and this is the agenda for today, and, as we don't have new members, 9 00:02:38.120 --> 00:02:42.070 Stefan Dombek: So we can start with these points, 10 00:02:43.240 --> 00:02:46.850 Stefan Dombek: Are there any other points for today? 11 00:02:53.710 --> 00:03:00.680 Stefan Dombek: Okay, then I can give you some updates from the… development, 12 00:03:01.110 --> 00:03:05.340 Stefan Dombek: In our last meeting, there was a requirement to 13 00:03:05.580 --> 00:03:10.179 Stefan Dombek: Add an additional column for the report releases. 14 00:03:10.640 --> 00:03:13.860 Stefan Dombek: In the provider list, and so… 15 00:03:14.080 --> 00:03:23.530 Stefan Dombek: This is done, so you can see this in snapshot, so… Let's see… snapshot here… 16 00:03:28.630 --> 00:03:29.290 Stefan Dombek: Huh? 17 00:03:35.630 --> 00:03:36.860 Stefan Dombek: East. 18 00:03:37.100 --> 00:03:38.020 Stefan Dombek: Beautiful. 19 00:03:38.570 --> 00:03:40.889 Stefan Dombek: So, here is the additional column. 20 00:03:41.700 --> 00:03:53.100 Stefan Dombek: And you can find the report releases as a list, and so if you only use one report release, you just see 21 00:03:53.200 --> 00:04:03.060 Stefan Dombek: One report release, and if you have, multiple report releases, then it's separated with a comma. 22 00:04:03.460 --> 00:04:07.340 Stefan Dombek: And you can also, sort the column 23 00:04:08.110 --> 00:04:13.700 Stefan Dombek: And it is a string, so it sorts with the beginning of the string. 24 00:04:14.680 --> 00:04:25.179 Bernd Oberknapp: Yeah, it shows the releases of loaded reports, not the configured report, the report configuration, so there's… Yes. 25 00:04:25.340 --> 00:04:30.470 Bernd Oberknapp: Yeah, I've came already across that in our test system, so… 26 00:04:31.850 --> 00:04:46.520 Stefan Dombek: So, that is the requirement if… and the use case, when you have multiple, usage data provider records, for the same, provider, with different, 27 00:04:46.800 --> 00:04:49.610 Stefan Dombek: Releases in the harvester configuration. 28 00:04:51.680 --> 00:05:06.439 Bernd Oberknapp: when I suggested this feature, I actually had in mind to have the configured release listed, but this makes more sense, because when you filter this, you get exactly what you see. 29 00:05:06.890 --> 00:05:18.590 Bernd Oberknapp: Otherwise, there might be differences from what you see and when you filter, what you actually get, so this makes perfectly sense to me in this way. 30 00:05:19.980 --> 00:05:25.129 Stefan Dombek: And of course, you can also filter here in the search and filter bar. 31 00:05:25.530 --> 00:05:26.660 Stefan Dombek: priorities. 32 00:05:27.090 --> 00:05:31.250 Stefan Dombek: So… And you get the same. 33 00:05:31.760 --> 00:05:35.290 Stefan Dombek: result. Okay. 34 00:05:35.630 --> 00:05:37.759 Stefan Dombek: That's the, 35 00:05:37.860 --> 00:05:47.790 Stefan Dombek: A little feature that we implemented. And, we also, have implemented, the new icons, 36 00:05:49.640 --> 00:05:59.480 Stefan Dombek: s… Zero reports, that are reports that have no usage, If, 37 00:05:59.600 --> 00:06:05.790 Stefan Dombek: the icon, with a null here. It's like this. 38 00:06:08.450 --> 00:06:20.390 Stefan Dombek: I think we… I showed you in one of the last meetings, so… but here you can see it on snapshot. And here's also the other icon with the calendar. 39 00:06:20.870 --> 00:06:23.130 Stefan Dombek: 3031. 40 00:06:26.640 --> 00:06:30.430 Stefan Dombek: A yellow icon with a calendar symbol. 41 00:06:31.250 --> 00:06:37.330 Stefan Dombek: So… And the other one for 3032. 42 00:06:37.730 --> 00:06:48.949 Stefan Dombek: is, in, review, but it's not available in Snapshot today, but I think tomorrow you can see it. 43 00:06:53.870 --> 00:06:59.940 Stefan Dombek: Con… look into this issue here. It's an… 44 00:07:00.330 --> 00:07:08.780 Stefan Dombek: It's also a calendar icon with Red background, so… Okay. 45 00:07:12.830 --> 00:07:22.150 Stefan Dombek: and… these COP error codes with, 30, and tricks are… 46 00:07:22.830 --> 00:07:35.230 Stefan Dombek: handled by the UI, and it's not handled by the back-end module, so that means we just change the icon via the UI. 47 00:07:35.480 --> 00:07:46.579 Stefan Dombek: And, if you have, other requirements for other icons that we need, we can change this in, with… 48 00:07:46.700 --> 00:07:47.680 Stefan Dombek: Yo. 49 00:07:49.460 --> 00:07:54.510 Stefan Dombek: in one day, if we want. So, it's… 50 00:07:54.750 --> 00:07:57.469 Stefan Dombek: It's not hard for us, to do this. 51 00:07:59.210 --> 00:08:06.430 Bernd Oberknapp: Yeah, I like these new icons. I was wondering about the 3040 exception. 52 00:08:06.700 --> 00:08:25.499 Bernd Oberknapp: do you already have a plan how to actually show that? Because I just came across a problem where we have a 3040 exception, where the logging has gone wrong for a provider, and they deliver, for example, a 53 00:08:26.000 --> 00:08:30.250 Bernd Oberknapp: Either a report with usage, with a 3040 exception. 54 00:08:30.250 --> 00:08:36.150 Stefan Dombek: Which then has to be used, because you won't get any additional information, because they cannot. 55 00:08:36.150 --> 00:08:38.989 Bernd Oberknapp: Reconstruct the missing usage. 56 00:08:39.210 --> 00:08:51.259 Bernd Oberknapp: And you also might get a 30-30 and 30-40 combination, because there was no usage, but some of the usage might have been lost. 57 00:08:51.610 --> 00:08:54.259 Bernd Oberknapp: And, I'm still… 58 00:08:54.590 --> 00:09:02.940 Bernd Oberknapp: trying to figure out how to display this in our own system, and I'm not sure how to do that in folio either. 59 00:09:03.150 --> 00:09:07.620 Bernd Oberknapp: So, if you have an idea how to do that, I would be interested. 60 00:09:08.200 --> 00:09:13.409 Stefan Dombek: Okay, it's not discussed yet in this group, so… 61 00:09:13.710 --> 00:09:20.909 Stefan Dombek: I'm open for all solutions, and if we need a new icon, we can implement this, and… 62 00:09:21.350 --> 00:09:26.739 Stefan Dombek: We can talk about an icon in the next meeting. 63 00:09:29.660 --> 00:09:43.179 Stefan Dombek: Or if you have an icon, then we can also reuse this, but we have to use the icon set from Folio, and there is an set of icons for… 64 00:09:45.070 --> 00:09:48.920 Stefan Dombek: the UI from Folio? 65 00:09:49.020 --> 00:09:50.310 Stefan Dombek: stripes. 66 00:09:50.550 --> 00:09:59.669 Stefan Dombek: Is it? And, it's recommended to use this icon set in folio. 67 00:10:00.390 --> 00:10:06.740 Bernd Oberknapp: The color is independent from the icon itself, or is it… Oh. 68 00:10:06.860 --> 00:10:08.479 Bernd Oberknapp: part of the icon set. 69 00:10:08.830 --> 00:10:12.380 Stefan Dombek: It's part of the icon set, but we changed the color. 70 00:10:14.710 --> 00:10:20.550 Bernd Oberknapp: Okay, so you could use a similar icon, but in a different color, that would work. 71 00:10:20.990 --> 00:10:21.820 Bernd Oberknapp: Focus. 72 00:10:23.090 --> 00:10:30.330 Stefan Dombek: So, and, yeah, we can use any of these icons. 73 00:10:35.620 --> 00:10:36.430 Stefan Dombek: So… 74 00:10:36.430 --> 00:10:45.269 Bernd Oberknapp: Yeah, what came to my mind is maybe using the actual icon, so the one with the zero or the, 75 00:10:45.410 --> 00:10:51.380 Bernd Oberknapp: the checkmark on it, but maybe in a different color, but I'm not sure what the color. 76 00:10:51.860 --> 00:10:55.340 Bernd Oberknapp: Hmm. I have to think about that. 77 00:10:56.550 --> 00:10:57.340 Stefan Dombek: Okay. 78 00:11:00.470 --> 00:11:06.310 Stefan Dombek: Yeah, and then… let's… Let me see… Yeah, pee… 79 00:11:06.800 --> 00:11:13.669 Stefan Dombek: Would like, to start with, remove the harvester function for count of 4. 80 00:11:13.970 --> 00:11:25.790 Stefan Dombek: for the photo release umbrella leave, so I asked in the Slack channel, about this topic, what we… is there someone that needs this, 81 00:11:25.940 --> 00:11:30.490 Stefan Dombek: functionality for the harvester, and, 82 00:11:31.750 --> 00:11:43.500 Stefan Dombek: I got the response that, we can remove this function from the harvester, but you can still use, count of 4 reports, for, 83 00:11:43.720 --> 00:11:47.160 Stefan Dombek: Within the manual upload feature. 84 00:11:47.760 --> 00:11:49.190 Stefan Dombek: from usage. 85 00:11:49.800 --> 00:11:59.939 Stefan Dombek: So, that means if you have count of 4 reports, you can upload these reports via the upload form. 86 00:12:02.510 --> 00:12:05.749 Stefan Dombek: So… That's the first step. 87 00:12:05.990 --> 00:12:14.050 Bernd Oberknapp: You mentioned umbrella Leaf, so, what's the status of Trillium? I'm not sure about that. 88 00:12:14.400 --> 00:12:22.470 Stefan Dombek: The, Trillium comes in May, I think? 89 00:12:22.890 --> 00:12:26.600 Bernd Oberknapp: So, the feature freeze all had already, 90 00:12:26.600 --> 00:12:40.539 Stefan Dombek: Yeah. We stopped development for Trillium in January, and all features, that we now implement are for Umbrella Leave, so… 91 00:12:41.800 --> 00:12:47.269 Bernd Oberknapp: Okay, so these icon changes and these changes all are for Umbrella Leaf already. 92 00:12:47.270 --> 00:12:54.099 Stefan Dombek: Yeah, let me double-check this with the developers, but I think it is so, so… and… 93 00:12:55.260 --> 00:13:06.090 Stefan Dombek: Thing is, with each release, we get, some platform requirements, from the release manager. 94 00:13:06.360 --> 00:13:09.469 Stefan Dombek: And so, we need an, 95 00:13:09.650 --> 00:13:13.250 Stefan Dombek: A time frame, between, 96 00:13:13.840 --> 00:13:22.189 Stefan Dombek: our feature freeze and official feature freeze from, the folio community. So… 97 00:13:22.780 --> 00:13:28.380 Stefan Dombek: And in this time frame, we implement all platform requirements for Onfolio. 98 00:13:28.520 --> 00:13:29.520 Stefan Dombek: for usage. 99 00:13:34.420 --> 00:13:45.540 Stefan Dombek: So… After we remove the harvester function for count of 4… And we would like to… 100 00:13:46.280 --> 00:13:59.510 Stefan Dombek: implement two features, that, would, like, solve the problems with COP error codes starting with 1 and 2. 101 00:14:01.430 --> 00:14:05.599 Stefan Dombek: And it's a proposal from our team. 102 00:14:06.010 --> 00:14:13.040 Stefan Dombek: To handle these codes, and so we should discuss this here in the group, if it's, 103 00:14:13.990 --> 00:14:17.459 Stefan Dombek: Yeah, fits the requirement, so… 104 00:14:17.870 --> 00:14:24.389 Stefan Dombek: Let's see, the first one is to handle these COP codes here, starting with 1. 105 00:14:27.230 --> 00:14:36.430 Stefan Dombek: And our proposal is that we… Add optional harvester properties. 106 00:14:36.890 --> 00:14:39.299 Stefan Dombek: For the usage data provider. 107 00:14:40.850 --> 00:14:45.620 Stefan Dombek: That means, you get an… 108 00:14:46.510 --> 00:14:51.149 Stefan Dombek: Additional, section in the harvester configuration. 109 00:14:53.220 --> 00:14:58.779 Stefan Dombek: Where you can configure some Optional harvester properties. 110 00:15:02.340 --> 00:15:11.879 Stefan Dombek: The first option is, that you override, the number of failed attempts from the global settings from eUsage. 111 00:15:13.650 --> 00:15:19.039 Stefan Dombek: I think it, it, it was a requirement from, Treason more. 112 00:15:19.630 --> 00:15:24.559 Stefan Dombek: That you… Set an individual 113 00:15:25.020 --> 00:15:28.450 Stefan Dombek: Number for the usage data provider. 114 00:15:32.170 --> 00:15:38.549 Stefan Dombek: And… The second option is, 115 00:15:39.670 --> 00:15:49.289 Stefan Dombek: If the server response is 1000, service is not available, you can set up the minutes for a new attempt. 116 00:15:51.020 --> 00:15:56.579 Stefan Dombek: At the moment, you have only, a new attempt after… 117 00:15:56.790 --> 00:16:00.350 Stefan Dombek: I think, do most of you use 24 hours? 118 00:16:01.030 --> 00:16:02.599 Stefan Dombek: Into Settings. 119 00:16:02.990 --> 00:16:06.660 Stefan Dombek: And here you can set up the minutes for each provider. 120 00:16:08.380 --> 00:16:09.490 Stefan Dombek: Then… 121 00:16:09.650 --> 00:16:21.040 Stefan Dombek: The other option, 1010, servicey, is the same, also 10LF, report queued for processing. I think that's the most important one. 122 00:16:22.710 --> 00:16:33.119 Stefan Dombek: And if the provider says, okay, I need time to get all informations together for one report, and it's skewed. 123 00:16:33.530 --> 00:16:36.990 Stefan Dombek: Then you can say, okay, in… 124 00:16:38.540 --> 00:16:42.100 Stefan Dombek: In one hour, I, try it again. 125 00:16:42.680 --> 00:16:44.680 Stefan Dombek: To download the report. 126 00:16:46.320 --> 00:16:47.810 Stefan Dombek: Or 15 minutes. 127 00:16:48.230 --> 00:16:52.020 Stefan Dombek: So, it's very individual for each provider. 128 00:16:52.780 --> 00:17:00.310 Bernd Oberknapp: So, there would be a similar configuration in the e-usage settings, where you can set the defaults. 129 00:17:07.790 --> 00:17:13.869 Bernd Oberknapp: Because you mentioned we are overriding the default, so you have to set the defaults somewhere, and they… 130 00:17:14.470 --> 00:17:18.109 Bernd Oberknapp: Would they be hard-coded, or would they be configurable? 131 00:17:18.950 --> 00:17:24.620 Stefan Dombek: At the moment, we only use N1… one? 132 00:17:24.790 --> 00:17:26.099 Stefan Dombek: Setting… 133 00:17:37.520 --> 00:17:38.320 Stefan Dombek: Here. 134 00:17:38.770 --> 00:17:41.269 Stefan Dombek: This periodic harvesting. 135 00:17:43.330 --> 00:17:47.400 Stefan Dombek: So… And it's just one… 136 00:17:50.280 --> 00:17:57.250 Stefan Dombek: Option that you can choose, but if we need it, we can also adhere, and… 137 00:17:57.530 --> 00:18:04.350 Stefan Dombek: options where you can set global settings, and then re, override 138 00:18:05.600 --> 00:18:12.880 Stefan Dombek: these settings with, individual… if it's set at, for the provider. 139 00:18:13.420 --> 00:18:21.139 Bernd Oberknapp: Yeah, I think it would make sense to have the same settings as global settings. Regarding the, 140 00:18:22.030 --> 00:18:28.419 Bernd Oberknapp: the time frame in minutes, I was wondering if that's for… 141 00:18:29.160 --> 00:18:36.049 Bernd Oberknapp: 10… 1020, client has made too many requests, this is… 142 00:18:36.520 --> 00:18:44.970 Bernd Oberknapp: How would that be interpreted? Would I enter, for example, I can make 60 requests per minute? 143 00:18:45.140 --> 00:18:50.000 Bernd Oberknapp: Or is that something… when it's… 144 00:18:50.480 --> 00:18:55.320 Bernd Oberknapp: When the limit is reached, it will wait as many minutes as specified. 145 00:18:57.430 --> 00:19:00.839 Bernd Oberknapp: So would I configure the actual limit? 146 00:19:01.330 --> 00:19:15.250 Bernd Oberknapp: And the system would interpret that, and then make a decision based on that, or would I say, well, if that happens, if I run into that limit, then wait as long as specified? 147 00:19:15.640 --> 00:19:29.359 Stefan Dombek: That's, it's a good question, if… The harester detects these, error code. 148 00:19:29.650 --> 00:19:37.230 Stefan Dombek: Then, the horror still waits, and… didn't… 149 00:19:37.440 --> 00:19:55.059 Stefan Dombek: the harvester tries only the number of requests that you set up here in the time frame, in minutes that you enter. So, if you say, okay, I only… the harvester only allows you to 150 00:19:56.700 --> 00:19:59.820 Stefan Dombek: Yeah, to reach… to fetch 10. 151 00:20:01.500 --> 00:20:08.009 Stefan Dombek: Reports, or you can only make 10 requests in one hour. 152 00:20:08.160 --> 00:20:10.960 Stefan Dombek: Then you can say, okay, 10? 153 00:20:11.170 --> 00:20:12.750 Stefan Dombek: And 16 minutes. 154 00:20:13.510 --> 00:20:23.470 Bernd Oberknapp: Okay, then we probably need seconds instead of minutes in this case, because we have cases like Scholarity IQ, where you can make one request per second. 155 00:20:26.570 --> 00:20:30.739 Bernd Oberknapp: I think minutes made sense for the other ones, 156 00:20:31.040 --> 00:20:33.260 Bernd Oberknapp: You don't have to go below that. 157 00:20:34.750 --> 00:20:38.910 Bernd Oberknapp: But, for that, 1020, we need seconds. 158 00:20:39.580 --> 00:20:42.249 Bernd Oberknapp: Otherwise, you would have to wait way too long. 159 00:20:44.530 --> 00:20:45.220 Stefan Dombek: Yo. 160 00:20:45.590 --> 00:20:51.320 Bernd Oberknapp: And you still could run into problems if you specify, for example, 60 per minute. 161 00:20:51.450 --> 00:21:00.819 Bernd Oberknapp: Because it's 1 per second, then you could still run into that limit, because if you, request more than one per second, that would still exceed the limit. 162 00:21:03.380 --> 00:21:04.290 Stefan Dombek: Okay. 163 00:21:07.240 --> 00:21:08.240 Stefan Dombek: And… 164 00:21:09.490 --> 00:21:17.279 Bernd Oberknapp: So, so the question would be if that is changed to seconds, if the other ones also should be changed to seconds. I'm not sure about that. 165 00:21:17.990 --> 00:21:20.860 Bernd Oberknapp: Whether that makes sense. 166 00:21:21.060 --> 00:21:22.540 Bernd Oberknapp: for consistency. 167 00:21:27.010 --> 00:21:34.900 Stefan Dombek: Yeah, we can use minutes or seconds, it's, can use both options. 168 00:21:41.220 --> 00:21:46.569 Bernd Oberknapp: Yeah, for the other ones, you probably shouldn't go below a minute, that's so that minutes would be fine for them. 169 00:21:46.860 --> 00:21:49.760 Bernd Oberknapp: But the 1020 is another case. 170 00:21:50.780 --> 00:21:54.030 Stefan Dombek: Okay, then we use seconds for 1020. 171 00:21:57.150 --> 00:22:05.249 Bernd Oberknapp: Yeah, then you could specify for Scholarly IQ maybe 1 request every 2 seconds, and then you wouldn't exceed the limit, 172 00:22:07.070 --> 00:22:10.839 Bernd Oberknapp: And… You shouldn't get any of the 1020 exceptions, yeah. 173 00:22:13.710 --> 00:22:16.730 Bernd Oberknapp: But it should be clear that this is… 174 00:22:17.240 --> 00:22:20.120 Bernd Oberknapp: Really different from the other ones. 175 00:22:20.530 --> 00:22:21.360 Bernd Oberknapp: So… 176 00:22:22.570 --> 00:22:23.540 Stefan Dombek: Bye. 177 00:22:25.270 --> 00:22:29.450 Stefan Dombek: Yeah, and behind every options, you have info. 178 00:22:29.950 --> 00:22:31.130 Bernd Oberknapp: Icon. 179 00:22:31.130 --> 00:22:36.659 Stefan Dombek: And if you go over this icon, you get an explanation what it means. 180 00:22:36.790 --> 00:22:38.330 Stefan Dombek: So… 181 00:22:39.080 --> 00:22:51.169 Stefan Dombek: In our group, we understand what each COP error code means, but for other users, you get an explanation what they have to do with this option. 182 00:22:53.150 --> 00:22:58.909 Bernd Oberknapp: Yeah, the other thing I was wondering about is, these are… seem to be required 183 00:22:59.420 --> 00:23:02.139 Bernd Oberknapp: Fields that you have to fill in. 184 00:23:02.140 --> 00:23:12.690 Stefan Dombek: No, no, that's all optional properties, and if you activate an, option, then it is, required. 185 00:23:12.920 --> 00:23:18.499 Bernd Oberknapp: Okay, and if you don't activate it, you would see the default value, or… 186 00:23:18.980 --> 00:23:20.310 Stefan Dombek: No. 187 00:23:21.740 --> 00:23:24.699 Bernd Oberknapp: That would be helpful if I could see the default value. 188 00:23:26.220 --> 00:23:29.930 Bernd Oberknapp: So maybe in somewhat gray color? 189 00:23:30.420 --> 00:23:36.649 Bernd Oberknapp: I'm not sure if that's… Yeah, maybe as the other ones where you can select something… 190 00:23:40.220 --> 00:23:42.699 Stefan Dombek: Makes sense that. 191 00:23:43.010 --> 00:23:48.039 Bernd Oberknapp: Yeah, or like, for the custom ID, where you have the explanation, what you have to put in. 192 00:23:48.500 --> 00:23:59.900 Bernd Oberknapp: And if the… if that would be possible to show the default value in the same way, then you would know why you would have to override something, because you can immediately see what the current setting is. 193 00:24:01.840 --> 00:24:05.350 Stefan Dombek: Yeah, I think that it's… we can do this. 194 00:24:06.240 --> 00:24:07.909 Stefan Dombek: Just a placeholder. 195 00:24:08.790 --> 00:24:11.019 Stefan Dombek: Or this, input field. 196 00:24:16.520 --> 00:24:23.160 Stefan Dombek: Okay… Jen, let me see… Did I forget something? 197 00:24:23.450 --> 00:24:26.359 Stefan Dombek: Aya, here in the detail view… 198 00:24:27.220 --> 00:24:30.830 Stefan Dombek: Then you get also a new section, 199 00:24:31.590 --> 00:24:37.520 Stefan Dombek: After the harvesting configuration for these properties, so that you can check this every time. 200 00:24:41.070 --> 00:24:47.560 Stefan Dombek: So, because sometimes you don't have the permissions to edit the record, and then you can see… 201 00:24:47.560 --> 00:24:48.030 Bernd Oberknapp: Mhmes. 202 00:24:48.030 --> 00:24:48.959 Stefan Dombek: What's going on? 203 00:24:54.000 --> 00:24:55.840 Bernd Oberknapp: Yeah, the question is how you would… 204 00:24:55.980 --> 00:25:04.940 Bernd Oberknapp: would you also show the default in this case? Because the example shows, for 1010, service busy. 205 00:25:05.870 --> 00:25:07.210 Bernd Oberknapp: Nothing here. 206 00:25:20.110 --> 00:25:20.940 Stefan Dombek: Okay. 207 00:25:23.760 --> 00:25:33.870 Stefan Dombek: That's right, that makes sense. So… Let's see… Yeah. 208 00:25:34.540 --> 00:25:42.339 Stefan Dombek: And if you have time, you can, read the info text here, and the ticket. 209 00:25:42.850 --> 00:25:47.480 Stefan Dombek: So, and… what we can do this now. 210 00:25:48.200 --> 00:25:54.489 Stefan Dombek: The number of failed attempts, is the info text. How many attempts can the harvester make? 211 00:25:54.980 --> 00:26:05.690 Stefan Dombek: there is a default value in the global settings, you can override this with this option. So, and we can add this part also for the other options, 212 00:26:05.890 --> 00:26:10.790 Stefan Dombek: When we would like to implement the global settings. 213 00:26:11.020 --> 00:26:12.100 Stefan Dombek: And… 214 00:26:12.680 --> 00:26:31.239 Stefan Dombek: But I think, it's another, ticket, to add the global settings for these, different codes, but let us start with this feature, and then we can add also the global settings later. 215 00:26:33.610 --> 00:26:38.090 Bernd Oberknapp: What would be the default for 1020? 216 00:26:44.860 --> 00:26:46.610 Bernd Oberknapp: That's a tricky one. 217 00:26:46.610 --> 00:26:52.280 Stefan Dombek: Yeah. So, I have to ask, Dottino. 218 00:26:54.400 --> 00:26:59.390 Bernd Oberknapp: So maybe something like not more than one request per second, or something like that? 219 00:27:00.570 --> 00:27:05.979 Bernd Oberknapp: Because there has to be some, some, low, lower limit, oil, or… 220 00:27:06.550 --> 00:27:11.460 Bernd Oberknapp: Yeah, some… some limits, because you can't… simply say. 221 00:27:11.810 --> 00:27:15.669 Bernd Oberknapp: As quickly as the system is able to make requests. 222 00:27:16.090 --> 00:27:18.240 Bernd Oberknapp: Well, you could do that, but. 223 00:27:23.920 --> 00:27:27.739 Stefan Dombek: Yeah, I have to ask him. So, what's the default value? 224 00:27:31.950 --> 00:27:35.040 Stefan Dombek: I know there are some problems with, 225 00:27:35.610 --> 00:27:39.730 Stefan Dombek: Providers, with this, code. 226 00:27:42.790 --> 00:27:49.049 Stefan Dombek: And, there are some tickets in Jira also that I linked to, 227 00:27:49.370 --> 00:27:55.810 Stefan Dombek: this, issue for 10-20th, and… Yeah, and… 228 00:27:56.960 --> 00:28:05.369 Stefan Dombek: I meet him, I think in the next days, and we talk about these features, but we, 229 00:28:05.890 --> 00:28:15.870 Stefan Dombek: Yeah, in our last meeting, we also, in our refinement, we talked about these, proposals, and, 230 00:28:16.720 --> 00:28:20.830 Stefan Dombek: Our conclusion was that we need your, 231 00:28:20.990 --> 00:28:31.159 Stefan Dombek: Yeah, your feedback from the community, is this enough to solve these problems, or do we need additional solutions? 232 00:28:31.180 --> 00:28:42.240 Stefan Dombek: So, and it's good to hear that you need the default values, and also that we have to check what's the default value for 1020, so… 233 00:28:42.270 --> 00:28:48.100 Stefan Dombek: And maybe we have to adjust also the default value for 1020. 234 00:28:52.220 --> 00:29:00.700 Bernd Oberknapp: Yeah, the one I know that's, is called ERQ, that's one request per second per customer. 235 00:29:01.140 --> 00:29:03.590 Bernd Oberknapp: The… 236 00:29:04.820 --> 00:29:23.450 Bernd Oberknapp: Other one where this could occur is JSTOR. You get a 1011 exception, report is queued, and you ask too often for the final report. If you do that, you at some point, get a 1020 exception. That's different, but 237 00:29:24.420 --> 00:29:32.499 Bernd Oberknapp: Yeah, I think if you have something like one request per second as a default, that could work. 238 00:29:32.960 --> 00:29:41.940 Bernd Oberknapp: And you would have to… only would have to override that in a few cases, so… I think that's important to… to not, 239 00:29:42.210 --> 00:29:53.659 Bernd Oberknapp: set either A2, too high limits, so to really trigger too many requests that these exception 1020 occurs. 240 00:29:53.760 --> 00:30:10.800 Bernd Oberknapp: And also not to, set the limit too low, so that you really need a long time to harvest reports. So we have to find a compromise for… between those two, and maybe one request per second would be a… 241 00:30:10.990 --> 00:30:12.809 Bernd Oberknapp: Good starting point. 242 00:30:14.330 --> 00:30:16.829 Stefan Dombek: Okay, then, 243 00:30:17.450 --> 00:30:25.680 Stefan Dombek: I noticed this, so… and, I asked him, and when we addressed, 1020, then, 244 00:30:25.790 --> 00:30:27.560 Stefan Dombek: We can set one second. 245 00:30:28.260 --> 00:30:28.990 Stefan Dombek: Cool. 246 00:30:29.490 --> 00:30:30.790 Stefan Dombek: One request per… 247 00:30:30.790 --> 00:30:35.970 Bernd Oberknapp: Yeah, I would be interested what the current value is. I think the system will… 248 00:30:36.660 --> 00:30:40.320 Bernd Oberknapp: Create as many, requests as you can. 249 00:30:41.390 --> 00:30:46.939 Bernd Oberknapp: So you might run into that limit, but I haven't actually tried that with ColoriaQ. 250 00:30:48.270 --> 00:30:49.040 Stefan Dombek: Yep. 251 00:30:50.250 --> 00:30:57.460 Stefan Dombek: Okay, that's… that's the feature for… these, tickets, and… 252 00:30:57.610 --> 00:31:16.370 Stefan Dombek: You can find the links also from the ZUP error codes here, and they're marked as blocked, because we don't implement this feature yet. So, and it's also blocked by the modification of the harvester, so… and our backend developer 253 00:31:16.980 --> 00:31:29.500 Stefan Dombek: It's waiting for the requirements that we need in the community, and now we have a solution, and he can start with the modification. 254 00:31:29.940 --> 00:31:31.629 Stefan Dombek: from the harvester. 255 00:31:31.760 --> 00:31:46.160 Stefan Dombek: And, yeah, the other ones are just related to this ticket. So, because we need an additional, UI ticket, for this UX prod and, and for the documentation. 256 00:31:47.500 --> 00:31:51.320 Stefan Dombek: So… Okay, great. 257 00:31:53.510 --> 00:32:00.059 Stefan Dombek: And… We talked also about a test environment. 258 00:32:01.060 --> 00:32:06.609 Stefan Dombek: And, we think we can do this with Snapshot? 259 00:32:07.770 --> 00:32:16.630 Stefan Dombek: So, when we… When we implement this feature, you can test it on Snapshot. 260 00:32:17.610 --> 00:32:24.829 Stefan Dombek: And… Or you, you install the latest version of e-usage on your test system. 261 00:32:25.680 --> 00:32:34.939 Stefan Dombek: There are many ways, so… but we cannot, give you a test installation from Leipzig. 262 00:32:36.440 --> 00:32:37.500 Stefan Dombek: Unfortunately. 263 00:32:41.220 --> 00:32:48.059 Bernd Oberknapp: Yeah, that's fine with me. We have our own Eureka test installation, where we always run the latest version. 264 00:32:48.460 --> 00:32:53.050 Bernd Oberknapp: So, once the feature becomes available, we could test it. 265 00:32:58.850 --> 00:33:04.490 Stefan Dombek: So, the next one… It's very tricky. 266 00:33:04.720 --> 00:33:05.520 Stefan Dombek: -Oh. 267 00:33:05.930 --> 00:33:07.659 Stefan Dombek: And we split. 268 00:33:08.000 --> 00:33:13.510 Stefan Dombek: this feature in… 2… features, 269 00:33:15.910 --> 00:33:22.640 Stefan Dombek: It's about, verifying, credentials, and… 270 00:33:23.900 --> 00:33:34.359 Stefan Dombek: It's a solution that I have to explain for you. The first feature is that we're checking the login credentials when you're configuring the harvester. 271 00:33:35.160 --> 00:33:45.329 Stefan Dombek: Zoom… And… When the harvester starts, the credentials are… 272 00:33:46.320 --> 00:33:56.940 Stefan Dombek: can be correct or not. So, let me explain you later, and… Then, in the ongoing, 273 00:33:57.830 --> 00:34:04.299 Stefan Dombek: Harvesting, we need a separate solution for the harvester itself. 274 00:34:04.920 --> 00:34:10.110 Stefan Dombek: to detect the COP records during the harvesting process. So… 275 00:34:10.380 --> 00:34:14.439 Stefan Dombek: Okay, and let's see the first feature. 276 00:34:19.070 --> 00:34:22.560 Stefan Dombek: And… Yeah. 277 00:34:24.280 --> 00:34:25.340 Stefan Dombek: after you… 278 00:34:25.489 --> 00:34:32.280 Stefan Dombek: configure the harvester, you can… you click Save and Close, and all required fields are checked by usage. 279 00:34:32.580 --> 00:34:38.840 Stefan Dombek: So… If there are required fields, then user checks this, so that's… 280 00:34:39.130 --> 00:34:45.540 Stefan Dombek: There are no changes, so… and after you click on… Save and close. 281 00:34:46.320 --> 00:34:52.739 Stefan Dombek: 10… Usage checks the status of the harvesting status? 282 00:34:53.000 --> 00:35:00.909 Stefan Dombek: If it's active, and the harvesting vial is counter sushi, A background process starts. 283 00:35:03.790 --> 00:35:12.270 Stefan Dombek: And… Then… It… it's… it's more questions here. The loading spinner appears. 284 00:35:12.780 --> 00:35:14.739 Stefan Dombek: For the background process? 285 00:35:16.570 --> 00:35:20.020 Stefan Dombek: And then… the result? 286 00:35:20.710 --> 00:35:24.360 Stefan Dombek: Cames from the back… back-end system. 287 00:35:24.560 --> 00:35:28.220 Stefan Dombek: And if the connection is possible with the credentials. 288 00:35:28.520 --> 00:35:32.850 Stefan Dombek: Use it to save the data record and close the edit mode. 289 00:35:33.610 --> 00:35:37.679 Stefan Dombek: But if… is it not possible to connect to the server? 290 00:35:37.800 --> 00:35:39.800 Stefan Dombek: Then a window appears. 291 00:35:40.950 --> 00:35:45.689 Stefan Dombek: Yeah? And you get information what was going wrong. 292 00:35:47.720 --> 00:35:53.470 Stefan Dombek: And here we need some informations in… 293 00:35:54.870 --> 00:35:58.850 Stefan Dombek: Let me see what I had to… to ask you. 294 00:35:59.770 --> 00:36:04.680 Stefan Dombek: Yeah. 295 00:36:04.960 --> 00:36:11.670 Stefan Dombek: So, the first is, step 2. 296 00:36:13.070 --> 00:36:22.380 Stefan Dombek: then you only edit the record, but you don't change the credentials. Do we need also a check? 297 00:36:22.600 --> 00:36:23.960 Stefan Dombek: In the background. 298 00:36:24.340 --> 00:36:25.930 Stefan Dombek: That's the first question? 299 00:36:28.140 --> 00:36:29.490 Stefan Dombek: We can divide it. 300 00:36:29.880 --> 00:36:35.480 Stefan Dombek: It's possible And in step 3… 301 00:36:37.170 --> 00:36:40.950 Stefan Dombek: How long can the verification take? 302 00:36:41.250 --> 00:36:42.340 Stefan Dombek: At most. 303 00:36:42.910 --> 00:36:46.690 Stefan Dombek: Do we need a timeout, or an option for cancelling? 304 00:36:49.150 --> 00:36:53.140 Stefan Dombek: And… 10? 305 00:36:54.040 --> 00:37:04.439 Stefan Dombek: From the backend side, we should categorize, what should be displayed here in this, 306 00:37:04.910 --> 00:37:08.420 Stefan Dombek: Window, when there is no connection. 307 00:37:09.030 --> 00:37:10.170 Stefan Dombek: possible. 308 00:37:12.580 --> 00:37:15.890 Stefan Dombek: So let's start with the first one here. 309 00:37:16.030 --> 00:37:22.149 Bernd Oberknapp: This is strictly for release 5.1, or would you also do this in Release 5? 310 00:37:25.170 --> 00:37:26.360 Stefan Dombek: For both of them. 311 00:37:26.680 --> 00:37:30.740 Bernd Oberknapp: Because that might make a difference, because you cannot check the… 312 00:37:31.100 --> 00:37:38.359 Bernd Oberknapp: For release 5.1, you can use the status endpoint to check if the base URL is even correct. 313 00:37:38.590 --> 00:37:41.140 Bernd Oberknapp: You can't do that for release 5. 314 00:37:42.960 --> 00:37:48.569 Bernd Oberknapp: So, this might… make a difference. 315 00:37:53.920 --> 00:37:56.090 Bernd Oberknapp: Yeah, I'm not sure… 316 00:37:57.500 --> 00:38:12.319 Bernd Oberknapp: you need a timeout, and if the timeout occurs, you should display that there was a timeout. Same if you don't get a connection, that's another kind of timeout. So you can have the connect timeout or the response timeout. 317 00:38:12.520 --> 00:38:20.469 Bernd Oberknapp: And you should simply get… the user should get the information that something timed out, that the credentials couldn't be checked. 318 00:38:20.680 --> 00:38:21.340 Stefan Dombek: Hmm. 319 00:38:21.940 --> 00:38:26.300 Bernd Oberknapp: But they still could save them, if I understand this correctly. 320 00:38:26.680 --> 00:38:29.229 Stefan Dombek: Yes, that's… that's right. 321 00:38:29.230 --> 00:38:39.449 Bernd Oberknapp: That's important because, for… for some reason, the content API server might not be available at the moment, or it might, for example, return exception 1000. 322 00:38:39.560 --> 00:38:42.320 Bernd Oberknapp: That could also happen, so. 323 00:38:42.880 --> 00:38:49.719 Stefan Dombek: Yeah, you have always the option to save the record, also if there is an error. 324 00:38:50.970 --> 00:38:51.580 Bernd Oberknapp: Yeah. 325 00:38:52.970 --> 00:38:55.150 Stefan Dombek: And, yeah, so… 326 00:38:55.610 --> 00:39:06.339 Stefan Dombek: And you said it is only possible to verify the service URL with 5.1 and not with 5. 327 00:39:06.810 --> 00:39:13.629 Bernd Oberknapp: Yeah, the problem is you don't have an endpoint without authentication in release 5. 328 00:39:13.990 --> 00:39:22.630 Bernd Oberknapp: This changed in release 5.1, the status endpoint has no authentication, so you can simply test the base URL by using the status endpoint. 329 00:39:23.090 --> 00:39:41.629 Bernd Oberknapp: And you cannot do that in… separately in Release 5, so the issue actually might be that somebody enters the wrong URL, and then the correct credentials, but it still doesn't work. And you cannot… cannot really detect that in… in, release 5. 330 00:39:42.080 --> 00:39:44.300 Stefan Dombek: And, our approach. 331 00:39:44.300 --> 00:39:49.260 Bernd Oberknapp: Yeah, the member list, that's another thing I've… I was thinking about, 332 00:39:50.380 --> 00:39:56.260 Bernd Oberknapp: Basically, that's… should be fine, but the problem is that this is the… 333 00:39:56.610 --> 00:40:01.540 Bernd Oberknapp: The endpoint that has actually the worst implementation rate. 334 00:40:02.340 --> 00:40:05.709 Bernd Oberknapp: Or the most errors in the implementations. 335 00:40:06.300 --> 00:40:19.669 Bernd Oberknapp: So I'm not really sure if that's a good idea. It seems to be in the first place, because that's the endpoint where it makes sense to check the credentials. 336 00:40:19.840 --> 00:40:24.020 Bernd Oberknapp: But, yeah, I'm not so sure about that. 337 00:40:26.220 --> 00:40:29.670 Bernd Oberknapp: Maybe reports would be the better choice. 338 00:40:30.020 --> 00:40:42.050 Bernd Oberknapp: The advantage of members is that you get back the, if it's implemented correctly, you get back the, actually information about the institution and the credentials. 339 00:40:42.560 --> 00:40:53.729 Bernd Oberknapp: So you could, for example, display the institution name, or something like that, that was returned. If you use another endpoint like reports, that doesn't work. 340 00:40:54.520 --> 00:40:56.400 Stefan Dombek: It's this one here. 341 00:40:56.400 --> 00:41:00.610 Bernd Oberknapp: Yeah, and we actually have a… 342 00:41:01.810 --> 00:41:19.139 Bernd Oberknapp: feature in our National Statistics Server platform, not in the web interface, but on the command line, where we can check the credentials, and we provide… actually have a parameter where you can choose the endpoint. You could also say, I'm using PR. 343 00:41:22.760 --> 00:41:24.080 Stefan Dombek: Oh yeah, you are muted. 344 00:41:26.260 --> 00:41:27.830 Stefan Dombek: Mary cannot hear you. 345 00:41:29.770 --> 00:41:31.110 Bernd Oberknapp: Actually, I should be… 346 00:41:31.250 --> 00:41:32.710 Stefan Dombek: That's… no. 347 00:41:32.710 --> 00:41:37.640 Bernd Oberknapp: That's interesting, because my microphone was actually not muted. 348 00:41:37.980 --> 00:41:43.919 Bernd Oberknapp: the… The problem is that, reports should work. 349 00:41:44.330 --> 00:41:50.099 Bernd Oberknapp: The chance that it works is much better than for members. 350 00:41:50.960 --> 00:42:00.619 Bernd Oberknapp: And, but the alternative might be to actually use a report. But creating a report, even if it's just a PR or a PRP1. 351 00:42:00.700 --> 00:42:08.530 Stefan Dombek: Might, might take some time. So, usually the, the response from, from, reports is much faster. 352 00:42:08.940 --> 00:42:09.610 Stefan Dombek: Yeah. 353 00:42:10.130 --> 00:42:16.419 Stefan Dombek: Okay, then we change to the report list, the API endpoint. 354 00:42:16.560 --> 00:42:19.809 Stefan Dombek: And not use the member list. 355 00:42:20.290 --> 00:42:28.019 Stefan Dombek: It makes sense, because we would like to also add a feature for the report types. 356 00:42:28.020 --> 00:42:28.620 Bernd Oberknapp: Yeah. 357 00:42:28.620 --> 00:42:33.240 Stefan Dombek: And so we can check this together in one way. 358 00:42:33.600 --> 00:42:35.190 Stefan Dombek: So… and… 359 00:42:35.190 --> 00:42:42.630 Bernd Oberknapp: Yeah, and that would be another question. You… you said you would… only… 360 00:42:43.620 --> 00:42:48.020 Bernd Oberknapp: Make that check when you, save the form. 361 00:42:48.450 --> 00:42:55.539 Bernd Oberknapp: But it would make sense to actually fetch the report information once the credentials have been entered. 362 00:42:55.540 --> 00:43:00.629 Stefan Dombek: Yeah, yeah, that's the reason why we split it, and 363 00:43:01.270 --> 00:43:10.609 Stefan Dombek: This is just when you're configuring the harvest, but if it's, our approach is that, you… 364 00:43:12.010 --> 00:43:23.489 Stefan Dombek: Then, if it's detected, then the harvesting status is set to inactive, and you have to go through the process again. 365 00:43:25.160 --> 00:43:33.740 Bernd Oberknapp: No, I think that was a misunderstanding. I was talking about the actual report configuration in the harvester configuration. 366 00:43:34.760 --> 00:43:38.010 Bernd Oberknapp: If you go back to the… configuration. 367 00:43:38.290 --> 00:43:43.150 Bernd Oberknapp: The first thing you should enter is the base URL. 368 00:43:43.390 --> 00:43:48.710 Bernd Oberknapp: If… if it's release 5.1, you could check if that's actually… that actually works. 369 00:43:48.960 --> 00:43:52.519 Bernd Oberknapp: The next step is that you usually enter the credentials. 370 00:43:52.640 --> 00:44:05.529 Bernd Oberknapp: And once you have both, you could use the reports endpoint to actually fetch the information about the available reports, and populate them, the report information with that. 371 00:44:06.780 --> 00:44:09.020 Bernd Oberknapp: So the… and, 372 00:44:10.180 --> 00:44:18.199 Bernd Oberknapp: You could get that information from the registry, but that information may rely on the customer… based on the customer. 373 00:44:20.260 --> 00:44:32.359 Bernd Oberknapp: For example, if there's a database report, but I don't have any database products for that provider, the provider might not offer the database report for me. 374 00:44:33.710 --> 00:44:46.529 Bernd Oberknapp: But you could see that when you use the reports endpoint, and you should only get the reports that are available for you, including the information about the, 375 00:44:47.030 --> 00:44:53.649 Bernd Oberknapp: Beginning and end time. The starting time is the most informational starting date. 376 00:44:53.790 --> 00:44:56.429 Bernd Oberknapp: From where you can fetch the reports. 377 00:44:57.180 --> 00:44:57.820 Bernd Oberknapp: So… 378 00:44:57.820 --> 00:45:01.120 Stefan Dombek: Yeah, let me think… we need an… 379 00:45:01.120 --> 00:45:01.570 Bernd Oberknapp: Er… 380 00:45:01.570 --> 00:45:08.209 Stefan Dombek: another, concept here, maybe… And, another button? 381 00:45:08.430 --> 00:45:10.950 Stefan Dombek: Or an, a check. 382 00:45:11.280 --> 00:45:13.570 Stefan Dombek: After you enter something. 383 00:45:13.570 --> 00:45:23.909 Bernd Oberknapp: Yeah, it makes the whole thing more complex, so I'm not sure if that's a really good idea, but this is what would be possible with the API endpoints. 384 00:45:23.910 --> 00:45:25.190 Stefan Dombek: Yep. 385 00:45:25.470 --> 00:45:43.040 Stefan Dombek: But what we can do is that we gray out the sections here, and you have to check the credentials, and after that, is it possible to get the report types for the provider? 386 00:45:43.100 --> 00:45:48.289 Stefan Dombek: Because we… with the request, we get the report types, so… 387 00:45:48.290 --> 00:45:48.970 Bernd Oberknapp: Yep. 388 00:45:49.350 --> 00:45:59.829 Bernd Oberknapp: Yeah, and you can pre-populate those fields, or either if the report request fails, offer this to be edited manually. 389 00:46:01.700 --> 00:46:02.290 Stefan Dombek: Something… 390 00:46:02.290 --> 00:46:03.670 Bernd Oberknapp: like that, yeah. 391 00:46:03.670 --> 00:46:07.910 Stefan Dombek: But it would make the whole form more interactive, so that's… 392 00:46:09.250 --> 00:46:14.630 Stefan Dombek: Yeah, let me check this with our UI developer. 393 00:46:14.780 --> 00:46:18.010 Stefan Dombek: Maybe we can add sliders here? 394 00:46:18.640 --> 00:46:25.649 Stefan Dombek: Yeah, and the advantage would be that you already have checked the credentials, so you wouldn't have to do that when saving the form. 395 00:46:27.860 --> 00:46:28.680 Stefan Dombek: Okay. 396 00:46:29.150 --> 00:46:35.010 Bernd Oberknapp: Andrew, maybe you could use that, because the, 397 00:46:37.190 --> 00:46:43.339 Bernd Oberknapp: The date from where you can request the reports might change over time. 398 00:46:43.780 --> 00:46:47.879 Bernd Oberknapp: So you also might use that for updating that information. 399 00:46:48.080 --> 00:46:50.889 Stefan Dombek: Yeah, that's… that's true. 400 00:46:51.220 --> 00:47:00.310 Stefan Dombek: we can detect the CUP error codes later with the barista, and then if it's detected, you… 401 00:47:00.610 --> 00:47:03.110 Stefan Dombek: The, the, 402 00:47:04.210 --> 00:47:15.830 Stefan Dombek: the option for harvesting status is inactive, and you have to edit the UTP record again, and then you have the same procedure. 403 00:47:16.910 --> 00:47:25.659 Stefan Dombek: And… We can also do this for report types. It was a question how we can do this. 404 00:47:25.800 --> 00:47:28.029 Stefan Dombek: So… and… 405 00:47:28.810 --> 00:47:44.130 Stefan Dombek: So we can do this in, in, with one request to the server. So, and it is… we can merge, these two requirements in one feature. So, we… so we did… 406 00:47:44.250 --> 00:47:51.509 Stefan Dombek: We not only checked the credentials, we also checked the report types at this moment. 407 00:47:51.990 --> 00:47:59.759 Stefan Dombek: and you're configuring the harvester. So that makes also sense for me, and we have, 408 00:47:59.980 --> 00:48:08.649 Stefan Dombek: One feature that fits these two requirements. And, then we have also to… 409 00:48:10.460 --> 00:48:16.599 Stefan Dombek: at this requirement for detection for the COP error codes, not only for the 410 00:48:16.760 --> 00:48:26.860 Stefan Dombek: Credentials, also for report types. And… we can… 411 00:48:27.990 --> 00:48:39.939 Stefan Dombek: It makes sense to stop the harvesting process, because you get errors if you set up wrong report types. 412 00:48:45.120 --> 00:48:54.199 Stefan Dombek: So, what I heard from Martina, that there are some providers that only offer standard views, and 413 00:48:54.630 --> 00:49:04.219 Stefan Dombek: if you try to load the counter reports, an error message appears. So it's not the standard, but you get the error code. 414 00:49:04.550 --> 00:49:17.159 Bernd Oberknapp: Yeah, actually, you get really strange error codes in that case, or even not an error code, but something like a 400 or 500 exception from the web server, an HTTP status code test. 415 00:49:17.350 --> 00:49:21.120 Bernd Oberknapp: And some HTML page, or something like that. 416 00:49:21.120 --> 00:49:23.550 Stefan Dombek: Yeah. That can happen. 417 00:49:25.540 --> 00:49:34.419 Bernd Oberknapp: But I'm wondering if you actually want to support that, or if you would say, in that case, you have to upload the reports manually? 418 00:49:37.000 --> 00:49:41.090 Stefan Dombek: HTTP codes are not a… Problem. 419 00:49:45.330 --> 00:49:56.659 Stefan Dombek: the… we can only interpret the CUP error codes, because it's a structured, JSON format, and HTTP, codes 420 00:49:57.390 --> 00:50:04.629 Stefan Dombek: It's very difficult to filter out what is the reason why it's not possible to download. 421 00:50:05.970 --> 00:50:07.840 Bernd Oberknapp: So, 422 00:50:08.330 --> 00:50:23.819 Bernd Oberknapp: I actually asked that in the counter code team recently. Was dropping the 3000 exception in release 5.1 in favor of just a 404 HTTP code a mistake? 423 00:50:26.340 --> 00:50:38.359 Bernd Oberknapp: Because if you try to request a non-supported report, you just get a 404 HTTP code back, and any kind of content in that page. 424 00:50:39.760 --> 00:50:43.710 Bernd Oberknapp: There's no exception to 3000 in UBS 5.1. 425 00:50:45.790 --> 00:50:51.150 Bernd Oberknapp: So, you have to actually interpret the HTTP code. 426 00:50:51.420 --> 00:50:54.869 Bernd Oberknapp: If, if only just the 404. 427 00:50:55.720 --> 00:51:09.690 Bernd Oberknapp: You could ignore the other ones, because all the other ones are related to a specific exception, but the 404, that's just a REST API. You try a non-supported endpoint, so you get 404. 428 00:51:10.240 --> 00:51:10.980 Stefan Dombek: Okay. 429 00:51:21.150 --> 00:51:23.969 Stefan Dombek: This is a great feature. 430 00:51:24.180 --> 00:51:31.930 Bernd Oberknapp: Yeah, and regarding the, report providers that don't support, 431 00:51:32.750 --> 00:51:36.409 Bernd Oberknapp: the hotel reports, just some standard views. 432 00:51:36.520 --> 00:51:38.960 Bernd Oberknapp: You cannot expect anything. 433 00:51:39.270 --> 00:51:41.249 Stefan Dombek: Everything could happen. 434 00:51:41.630 --> 00:51:46.640 Bernd Oberknapp: If you try to request a counter report. 435 00:51:46.850 --> 00:51:47.520 Stefan Dombek: Yeah. 436 00:51:47.650 --> 00:51:54.100 Stefan Dombek: in… Yeah, we checked the standard, and they must offer counter reports. 437 00:51:54.720 --> 00:51:55.320 Stefan Dombek: At last. 438 00:51:55.320 --> 00:51:57.850 Bernd Oberknapp: Yeah, but some don't do that. 439 00:51:57.970 --> 00:52:03.479 Bernd Oberknapp: The most prominent example probably is, Gibi Guinos. 440 00:52:04.030 --> 00:52:06.860 Stefan Dombek: Which caused the most problems. 441 00:52:07.020 --> 00:52:11.330 Bernd Oberknapp: Which also, same as EffortZet, is on the same platform. 442 00:52:11.690 --> 00:52:15.369 Bernd Oberknapp: And we have really trouble with harvesting their reports. 443 00:52:15.520 --> 00:52:16.130 Stefan Dombek: Hmm. 444 00:52:17.990 --> 00:52:24.389 Bernd Oberknapp: And there's a number of smaller journal publishers who only have implemented 445 00:52:25.150 --> 00:52:28.229 Bernd Oberknapp: Perfume standard fuse, or just a single one. 446 00:52:28.660 --> 00:52:30.610 Stefan Dombek: Is it a misunderstanding? 447 00:52:30.830 --> 00:52:33.759 Stefan Dombek: No, it's… Can't count the reports? 448 00:52:33.910 --> 00:52:37.650 Bernd Oberknapp: They simply implemented what was easy for them. 449 00:52:37.860 --> 00:52:44.330 Stefan Dombek: Yeah, but I'm not sure if it's a misunderstanding counter-reports because it's renamed? 450 00:52:45.160 --> 00:53:01.249 Bernd Oberknapp: In some cases, I know that it wasn't a misunderstanding, it was the deliberate decision not to implement what was called the Kotamuso Reports, or now the Cotter Reports. They deliberately just implemented some of the strategies. 451 00:53:08.200 --> 00:53:09.080 Stefan Dombek: Yeah. 452 00:53:10.210 --> 00:53:11.340 Stefan Dombek: Okay. 453 00:53:11.930 --> 00:53:17.490 Stefan Dombek: Then… are you… up, like, 454 00:53:18.660 --> 00:53:23.690 Stefan Dombek: I edit these tickets in the next days, and. 455 00:53:23.690 --> 00:53:35.839 Bernd Oberknapp: Yeah, regarding just these report providers that only have some standard views, the question remains whether you actually want to support harvesting their reports. 456 00:53:36.410 --> 00:53:40.600 Bernd Oberknapp: Because that would be a… significant… 457 00:53:41.450 --> 00:53:50.909 Bernd Oberknapp: difference to the usual reports that would have to be taken into account when you, for example, then have the e-usage reports plugin. 458 00:53:51.720 --> 00:53:58.430 Bernd Oberknapp: Which just has some of the standard views available, but maybe not the data you want to use for evaluations. 459 00:53:58.640 --> 00:53:59.230 Stefan Dombek: Yep. 460 00:54:03.460 --> 00:54:10.259 Stefan Dombek: Okay, our privatization is, this list here, and, 461 00:54:10.520 --> 00:54:19.609 Stefan Dombek: We have time with, this feature for the credentials and the report types, so we can… I can, 462 00:54:20.170 --> 00:54:28.230 Stefan Dombek: Make the updates on these tickets, and then we can talk about, again, this, new feature. 463 00:54:29.600 --> 00:54:33.460 Stefan Dombek: That it's merged with the repo types, and… 464 00:54:33.580 --> 00:54:41.570 Stefan Dombek: if we say that that's our feature that we want to, then, I can… we can start with the implementation, but… 465 00:54:41.790 --> 00:54:46.770 Stefan Dombek: I think we start with this one here, and 466 00:54:47.780 --> 00:54:53.009 Stefan Dombek: I think dates are done, so… and removing the harvester function account for. 467 00:54:54.740 --> 00:55:06.709 Stefan Dombek: Okay, and, I think we should skip this part here for today, but for your information. 468 00:55:07.310 --> 00:55:14.060 Stefan Dombek: It's a feature, to add, templates in usage. 469 00:55:14.610 --> 00:55:20.069 Stefan Dombek: I think it's… We should talk about this in the next meeting. 470 00:55:20.370 --> 00:55:23.519 Stefan Dombek: to have more time for this. 471 00:55:24.610 --> 00:55:27.419 Stefan Dombek: No, that's not the right one. 472 00:55:29.230 --> 00:55:31.200 Stefan Dombek: Yeah, integrated providers. 473 00:55:31.430 --> 00:55:37.970 Stefan Dombek: It should be… and, and, 474 00:55:39.470 --> 00:55:49.729 Stefan Dombek: A helpful feature that you can automatically fill out, the input fields from the counter registry information, so… 475 00:55:50.050 --> 00:55:55.870 Stefan Dombek: You can select a provider from calendar registry and usage, 476 00:55:56.150 --> 00:56:01.770 Stefan Dombek: Fetch the data from counter registry and fill out all the fields automatically. 477 00:56:01.960 --> 00:56:02.680 Stefan Dombek: So… 478 00:56:03.240 --> 00:56:10.009 Stefan Dombek: It's planned, and I think it's better when we talk about this in the next meeting, when we have more time for this. 479 00:56:12.140 --> 00:56:22.420 Bernd Oberknapp: Yeah, that… if you add a check of the reports endpoint, you might have the information about the reports from two sources. 480 00:56:23.500 --> 00:56:38.319 Bernd Oberknapp: ones from the registry and ones from the reports endpoint, and I would suggest to actually use the one from the reports endpoint, if you have that information available, and use the registry information as a fallback. 481 00:56:41.340 --> 00:56:47.680 Bernd Oberknapp: Because the report's endpoint might be more precise than what you find in the registry. 482 00:56:47.890 --> 00:56:54.640 Bernd Oberknapp: And, this would also work for, providers that are not in the registry, so… 483 00:56:55.080 --> 00:56:57.710 Bernd Oberknapp: But would be the, the better choice. 484 00:57:00.140 --> 00:57:09.370 Stefan Dombek: Yeah, so, you can read the ticket, and we should talk about this in the next meeting, so… 485 00:57:09.590 --> 00:57:15.820 Stefan Dombek: To see if this is a good feature for you, or should we add more? 486 00:57:16.060 --> 00:57:20.269 Stefan Dombek: We would like to try… 487 00:57:20.960 --> 00:57:30.610 Stefan Dombek: Without caching the data, so… but if it's necessary, we add… 488 00:57:30.820 --> 00:57:34.530 Stefan Dombek: We add data to the database. 489 00:57:34.750 --> 00:57:50.480 Stefan Dombek: If it's needed, so… but we would like to try it on Snapshot if it's possible to load the data when you're configuring the usage data provider. But we have to see how well it works. 490 00:57:50.900 --> 00:57:56.489 Stefan Dombek: And if it's not worked, then we should add a caching process. 491 00:57:57.820 --> 00:58:03.210 Bernd Oberknapp: Yeah, caching what makes sense in the… 492 00:58:03.610 --> 00:58:20.360 Bernd Oberknapp: In the sense that you don't have to request that information multiple times when configuring multiple identity providers… multiple usage data providers in a short time, but not storing that information for a longer time, because it might change. 493 00:58:21.180 --> 00:58:21.730 Stefan Dombek: Hmm. 494 00:58:22.520 --> 00:58:30.489 Bernd Oberknapp: So if… if it's not… If the response isn't fast enough, you could, 495 00:58:31.180 --> 00:58:33.599 Bernd Oberknapp: Tommy, and I will talk to the… 496 00:58:33.950 --> 00:58:37.530 Bernd Oberknapp: Colleagues who are running that service. 497 00:58:38.280 --> 00:58:42.910 Stefan Dombek: Yeah, or there is an way to, to, 498 00:58:44.130 --> 00:58:47.689 Stefan Dombek: Make a whitelist for different institutions. 499 00:58:48.040 --> 00:58:48.730 Stefan Dombek: Oh. 500 00:58:49.140 --> 00:58:50.180 Stefan Dombek: Good to you. 501 00:58:50.830 --> 00:58:54.270 Stefan Dombek: Can make more requests. 502 00:58:55.290 --> 00:59:06.049 Bernd Oberknapp: Yeah, that would be another issue if you run into some limit where the requests are refused, but I don't think that that's a reconcern here. 503 00:59:09.860 --> 00:59:11.570 Stefan Dombek: Okay, yeah. 504 00:59:13.180 --> 00:59:19.499 Stefan Dombek: So… The question is when we meet again. So… 505 00:59:20.870 --> 00:59:26.340 Stefan Dombek: I think we need time to implement these features here, and… 506 00:59:27.910 --> 00:59:34.550 Stefan Dombek: So, if it makes sense to meet… 507 00:59:38.050 --> 00:59:39.260 Stefan Dombek: I think… 508 00:59:42.680 --> 00:59:49.710 Stefan Dombek: I'm on vacation. I think… At the end of April. 509 00:59:50.670 --> 00:59:53.350 Stefan Dombek: But there's also Eastern Time. 510 00:59:54.660 --> 01:00:06.450 Stefan Dombek: Trin… these meetings, so… When… when we have Easter, right? Eastern time is… 511 01:00:06.750 --> 01:00:09.340 Bernd Oberknapp: April 6th is Easter Monday. 512 01:00:09.990 --> 01:00:11.079 Stefan Dombek: Hmm, okay, then… 513 01:00:11.080 --> 01:00:17.349 Bernd Oberknapp: So, I think there's a rule we shouldn't have a meeting in the last week of the month? 514 01:00:19.550 --> 01:00:23.590 Bernd Oberknapp: That was a suggestion from the… one of the councils. 515 01:00:24.500 --> 01:00:27.500 Stefan Dombek: In, 4 weeks. 516 01:00:30.840 --> 01:00:34.659 Bernd Oberknapp: You mean on, on… that would be March 30th? 517 01:00:34.660 --> 01:00:35.340 Stefan Dombek: Yes. 518 01:00:37.110 --> 01:00:42.019 Bernd Oberknapp: That's the week before Easter, I'm not sure, but I could make it. 519 01:00:42.250 --> 01:00:44.549 Bernd Oberknapp: I'm not sure if everybody else would be able. 520 01:00:49.880 --> 01:00:52.870 Stefan Dombek: It's okay for the other members? 521 01:00:54.750 --> 01:00:55.969 Stefan Dombek: March 30? 522 01:00:57.680 --> 01:01:02.159 Stefan Dombek: Okay, then I'll create the invitation for you. 523 01:01:02.980 --> 01:01:08.820 Stefan Dombek: And then we meet in… In 4 weeks ago. 524 01:01:11.670 --> 01:01:18.319 Stefan Dombek: So, and then, I think it makes sense to talk about This feature here, and… 525 01:01:18.630 --> 01:01:19.950 Stefan Dombek: So let me go. 526 01:01:20.320 --> 01:01:28.050 Stefan Dombek: make sure that it fits the requirements. So, okay. 527 01:01:29.070 --> 01:01:34.619 Stefan Dombek: Then, have a nice sunny day, and, see you all. 528 01:01:36.450 --> 01:01:37.240 Bernd Oberknapp: Bye. 529 01:01:37.450 --> 01:01:38.010 Stefan Dombek: Fine. 530 01:01:38.010 --> 01:01:38.940 Heiko Schorde: Ciao ciao.