WEBVTT 00:37:43.000 --> 00:37:54.000 So this might. Make a difference. 00:37:54.000 --> 00:37:58.000 Yeah, I'm I'm not sure. 00:37:58.000 --> 00:38:06.000 You need a timeout, and if the timeout occurs you should should display that there was a timeout same if you if you don't get it. 00:38:06.000 --> 00:38:09.000 Connection. That's another kind of timeout. 00:38:09.000 --> 00:38:13.000 So you can have the connect timeout or the the response. Timeout. 00:38:13.000 --> 00:38:22.000 And you should simply get the user should get the information that something timed out that the credentials couldn't be checked. 00:38:22.000 --> 00:38:26.000 But they still could save them. If I understand this correctly. 00:38:26.000 --> 00:38:28.000 Yes, that's that's right. Um. 00:38:28.000 --> 00:38:39.000 Yeah, yeah, that's that's important. Because for for some reason the the content Api server might not available at the moment, or might, for example, return exception, 1,000. 00:38:39.000 --> 00:38:40.000 Yeah? 00:38:40.000 --> 00:38:42.000 That could also happen. So Our service is busy. Yeah. 00:38:42.000 --> 00:38:47.000 Yeah, you have always always the option to to save the record. 00:38:47.000 --> 00:38:48.000 Also, if there is an error. 00:38:48.000 --> 00:38:52.000 Yeah. Yeah. Okay? 00:38:52.000 --> 00:38:53.000 And yeah. So. 00:38:53.000 --> 00:38:55.000 Yeah. 00:38:55.000 --> 00:39:04.000 And you said it's uh only possible to verify the service. Url, with. 00:39:04.000 --> 00:39:07.000 Five, one, and not a five. 00:39:07.000 --> 00:39:14.000 Yeah, the problem is, you don't have an endpoint without authentication, and for in release, file. 00:39:14.000 --> 00:39:23.000 This change in release 5.1. But the status Endpoint has no authentication, so you can simply test the base URL by using the status Endpoint. 00:39:23.000 --> 00:39:28.000 And you cannot do that in separately, in release. 5. So. 00:39:28.000 --> 00:39:35.000 The issue actually might be that somebody enters the wrong URL, and then the correct credentials. But it still doesn't work. 00:39:35.000 --> 00:39:36.000 Uh. 00:39:36.000 --> 00:39:41.000 And you cannot cannot read. Detect that in in Release. 5. 00:39:41.000 --> 00:39:45.000 And our approach is to. 00:39:45.000 --> 00:39:51.000 Yeah, the Member List. That's another thing I've I was thinking about. 00:39:51.000 --> 00:39:57.000 Basically that's should be fine. But the problem is that this is the. 00:39:57.000 --> 00:40:00.000 The endpoint that has actually. 00:40:00.000 --> 00:40:07.000 The worst implementation rate. Or the most errors in the implementations. 00:40:07.000 --> 00:40:11.000 So I'm not really sure if that's a good idea. 00:40:11.000 --> 00:40:18.000 It. It seems to be, in the 1st place, because that's the end point where it makes sense to to. 00:40:18.000 --> 00:40:27.000 Check the credentials. But Yeah, I'm not so sure about that. 00:40:27.000 --> 00:40:43.000 Maybe reports would be the better choice. The 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. 00:40:43.000 --> 00:40:47.000 So you could, for example, display the institution name. 00:40:47.000 --> 00:40:54.000 Or something like that that was returned. If you use another. 00:40:54.000 --> 00:40:55.000 Uh, it's this one here. 00:40:55.000 --> 00:40:57.000 Endpoint like reports that doesn't work. 00:40:57.000 --> 00:41:09.000 Yeah, and we actually have a. Feature in our national statistics server platform, not in the Web interface, but on the command line. 00:41:09.000 --> 00:41:17.000 Where we can check the credentials, and we provide actually have an a parameter way. You can choose the endpoint. 00:41:17.000 --> 00:41:22.000 You could also say I'm using Pr or. 00:41:22.000 --> 00:41:26.000 Or as you're muted. 00:41:26.000 --> 00:41:29.000 We cannot hear you. 00:41:29.000 --> 00:41:30.000 Can you see so? Yes? Yes, no. 00:41:30.000 --> 00:41:33.000 Actually, I should be. 00:41:33.000 --> 00:41:38.000 That's interesting, because my my microphone was actually not muted. 00:41:38.000 --> 00:41:43.000 The the problem is that um. 00:41:43.000 --> 00:41:45.000 Repost should work. 00:41:45.000 --> 00:41:47.000 Um. 00:41:47.000 --> 00:41:51.000 The the chance that it works is much better than for members. 00:41:51.000 --> 00:41:56.000 And but the alternative might be to actually use a report. 00:41:56.000 --> 00:42:01.000 But creating report, even if it's just a pr or Prp. One. 00:42:01.000 --> 00:42:08.000 Might might take some time. So usually the the response from from reports is much faster. 00:42:08.000 --> 00:42:14.000 Yeah. Okay. Then we change to the report list. 00:42:14.000 --> 00:42:18.000 Der Api. Endpoint and not use the member. 00:42:18.000 --> 00:42:21.000 List um. 00:42:21.000 --> 00:42:28.000 It makes sense, because we would like to also add a feature for the report types. 00:42:28.000 --> 00:42:33.000 And so we can check this together in one way. 00:42:33.000 --> 00:42:35.000 So, and. 00:42:35.000 --> 00:42:42.000 Yeah, and that that would be another question. You you said you would. 00:42:42.000 --> 00:42:49.000 Only. Make that check when you save the form. 00:42:49.000 --> 00:42:55.000 But it would make sense to actually fetch the report information, once the credentials have been entered. 00:42:55.000 --> 00:42:58.000 Yeah, yeah, that's that's the reason why we split it. 00:42:58.000 --> 00:43:01.000 And. 00:43:01.000 --> 00:43:04.000 This is just when you're configuring the arrest. 00:43:04.000 --> 00:43:11.000 But if it's our approach is that you. 00:43:11.000 --> 00:43:20.000 Then, if it's detected, then the harvesting status is set to inactive, and you have. 00:43:20.000 --> 00:43:25.000 To go through the process again. 00:43:25.000 --> 00:43:35.000 No, I I think that was a misunderstanding. I was talking about the actually report configuration in in the Harvester Configuration. 00:43:35.000 --> 00:43:37.000 If you go back to the. 00:43:37.000 --> 00:43:40.000 Configuration. Um. 00:43:40.000 --> 00:43:44.000 The 1st thing you should enter is the base URL. 00:43:44.000 --> 00:43:49.000 If if it's released, 5.1 you could check if that's actually that actually works. 00:43:49.000 --> 00:43:53.000 The next step is that you usually enter the credentials. 00:43:53.000 --> 00:44:02.000 And once you have both, you could use the reports endpoint to actually fetch the information about the available reports. 00:44:02.000 --> 00:44:07.000 And populate them. The report information with that. 00:44:07.000 --> 00:44:11.000 So that and um. 00:44:11.000 --> 00:44:21.000 You could get that information from the registry, but that information may rely on the custom based on the customer. 00:44:21.000 --> 00:44:28.000 For example, if there's a database report, but I don't have any database products on for for that provider. 00:44:28.000 --> 00:44:34.000 The provider might not offer the database. Report for me. 00:44:34.000 --> 00:44:54.000 But you could see that when you, when you use the the reports endpoint, and you should only get the reports that are available for you, including the information about the Beginning and end time. The starting time is the most informational starting date. 00:44:54.000 --> 00:44:57.000 From where you can fetch the reports. 00:44:57.000 --> 00:44:58.000 Yeah, let me see, we need an. 00:44:58.000 --> 00:45:01.000 So. 00:45:01.000 --> 00:45:03.000 Another uh. 00:45:03.000 --> 00:45:08.000 Konzept. Here maybe another button. 00:45:08.000 --> 00:45:09.000 Or and check. 00:45:09.000 --> 00:45:11.000 Yeah, it. 00:45:11.000 --> 00:45:14.000 After you enter something. 00:45:14.000 --> 00:45:23.000 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. 00:45:23.000 --> 00:45:30.000 Yeah. But what we can do is that we gray out these sections here. 00:45:30.000 --> 00:45:36.000 And you have to check the credentials. And after that. 00:45:36.000 --> 00:45:41.000 Is it possible to get the report types for the. 00:45:41.000 --> 00:45:44.000 Provider, because we. 00:45:44.000 --> 00:45:48.000 With the request we get to report types. So. 00:45:48.000 --> 00:46:02.000 Yeah, yeah. And you can could pre populate those fields, or either. If if the report request fails, offer this to to be edited manually. 00:46:02.000 --> 00:46:09.000 Something like that. Yeah. But it would make the the whole form more interactive. So that's. 00:46:09.000 --> 00:46:10.000 Um. 00:46:10.000 --> 00:46:14.000 Yeah, let me check this with our Ui Developer. 00:46:14.000 --> 00:46:19.000 Maybe we can add sliders here. 00:46:19.000 --> 00:46:27.000 Yeah, and the advantage would be that you already have checked the credentials. So you wouldn't have to do that by saving the form. 00:46:27.000 --> 00:46:30.000 Okay? Yeah. 00:46:30.000 --> 00:46:38.000 Thank you. Maybe you. Could use that, that because the 00:46:38.000 --> 00:46:44.000 The date from where you can. Request the reports might change over time. 00:46:44.000 --> 00:46:47.000 So you also might use that for updating that information. 00:46:47.000 --> 00:46:51.000 Yeah, that's that's true. Um. 00:46:51.000 --> 00:46:54.000 We can detect the cop error codes. 00:46:54.000 --> 00:46:58.000 Later with the harrister, and then. 00:46:58.000 --> 00:47:01.000 If it's detected you. 00:47:01.000 --> 00:47:04.000 Die. 00:47:04.000 --> 00:47:16.000 Die Option. For harvesting status is inactive, and you have to edit the Utp record again, and then you have the same procedure. 00:47:16.000 --> 00:47:25.000 And we can also do this for report types. It was a question how we can do this. 00:47:25.000 --> 00:47:28.000 So, and. 00:47:28.000 --> 00:47:33.000 So we can do this in in uh. With one request. 00:47:33.000 --> 00:47:35.000 To the server so and. 00:47:35.000 --> 00:47:40.000 We can merge these two requirements in one feature. 00:47:40.000 --> 00:47:44.000 So we, so we did. 00:47:44.000 --> 00:47:50.000 We not only check the the um credentials, we also check the report types. 00:47:50.000 --> 00:47:53.000 At this moment, when you're configuring the Harvester. 00:47:53.000 --> 00:47:58.000 So that makes also sense for me. And we have. 00:47:58.000 --> 00:48:03.000 Um. One feature that fits these two requirements. 00:48:03.000 --> 00:48:07.000 And then we have also. 00:48:07.000 --> 00:48:09.000 To. 00:48:09.000 --> 00:48:16.000 At this requirement for detection, for the cop arrow calls not only for the. 00:48:16.000 --> 00:48:24.000 Credentials also for report types. 00:48:24.000 --> 00:48:27.000 And we can. 00:48:27.000 --> 00:48:33.000 It makes sense to stop the harvesting process, because you get. 00:48:33.000 --> 00:48:36.000 Faith errors. If you. 00:48:36.000 --> 00:48:44.000 Set up from report types. 00:48:44.000 --> 00:48:46.000 So what I heard from Martina. 00:48:46.000 --> 00:48:49.000 Yeah. 00:48:49.000 --> 00:48:55.000 That there are some providers that only offers standard views and. 00:48:55.000 --> 00:49:05.000 If you try to load the counter reports an error message appears so it's not the standard, but you get the error code. 00:49:05.000 --> 00:49:18.000 Yeah, actually, you get really strange error codes in that case, or even not an error code, but something like a for 400 or 500 exception from from the Web server in Http status code test. 00:49:18.000 --> 00:49:22.000 And some HTML page, or something like that. 00:49:22.000 --> 00:49:24.000 That can happen. 00:49:24.000 --> 00:49:26.000 Um. 00:49:26.000 --> 00:49:36.000 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. 00:49:36.000 --> 00:49:39.000 Http. Codes are another. 00:49:39.000 --> 00:49:42.000 Problem. 00:49:42.000 --> 00:49:45.000 Just um. 00:49:45.000 --> 00:49:52.000 Die. We can only interpret the cop error codes because it's a structured Json. 00:49:52.000 --> 00:49:55.000 Format and Http. 00:49:55.000 --> 00:50:01.000 Codes. It's very difficult to filter out. What's what is the. 00:50:01.000 --> 00:50:05.000 The reason why it's not possible to download. 00:50:05.000 --> 00:50:06.000 Um. 00:50:06.000 --> 00:50:09.000 So um. 00:50:09.000 --> 00:50:13.000 I actually asked that in the counter cow team recently. 00:50:13.000 --> 00:50:20.000 Was dropping the 3,000 exception, and released 5.1 in favor of just F. 4 or 4. 00:50:20.000 --> 00:50:27.000 Http code a Mistake. 00:50:27.000 --> 00:50:33.000 Because if you try to request a non-supported report. 00:50:33.000 --> 00:50:40.000 You just get a 404 Http code back, and any kind of content in that page. 00:50:40.000 --> 00:50:46.000 There's no exception. 3,000 in in these 5.1. 00:50:46.000 --> 00:50:52.000 So you have to actually interpret the Http code. 00:50:52.000 --> 00:51:04.000 If if only just the 4 0. 4. You could ignore the other ones, because all the other ones are related to a specific exception. But the 404. 00:51:04.000 --> 00:51:09.000 It. That's just a rest. Api. You try a non-supported endpoint. So you get 4. 00:51:09.000 --> 00:51:21.000 Okay. 00:51:21.000 --> 00:51:25.000 This is a great feature team. 00:51:25.000 --> 00:51:34.000 Yeah, and and regarding the Report providers that don't support. 00:51:34.000 --> 00:51:40.000 The auto reports. Just some standard views. You cannot expect anything. 00:51:40.000 --> 00:51:46.000 Everything could happen. 00:51:46.000 --> 00:51:47.000 Yeah, in. 00:51:47.000 --> 00:51:48.000 If you try to request a counter report. 00:51:48.000 --> 00:51:54.000 Ja, ich. Check the standard, and they must offer counter reports. 00:51:54.000 --> 00:51:56.000 Die diese. 00:51:56.000 --> 00:51:58.000 Yeah, but but some don't. Don't do that. 00:51:58.000 --> 00:52:00.000 The most. 00:52:00.000 --> 00:52:04.000 Roman example, probably is Kimi quinos. 00:52:04.000 --> 00:52:12.000 Which caused the most problems. Which also, same as Faz, is on the same platform. 00:52:12.000 --> 00:52:18.000 And we have really troubled with harvesting their reports. 00:52:18.000 --> 00:52:26.000 There is a number of smaller journal publishers. Who only have implemented. 00:52:26.000 --> 00:52:28.000 A few standard views, or just a single one. 00:52:28.000 --> 00:52:30.000 Is it a misunderstanding. 00:52:30.000 --> 00:52:31.000 Count counter reports. 00:52:31.000 --> 00:52:37.000 No, it's. It's they. They simply implemented what what was easy for them. 00:52:37.000 --> 00:52:42.000 Yeah, but I'm not sure if it's a misunderstanding counter reports, because it's renamed. 00:52:42.000 --> 00:52:45.000 No. No, no. 00:52:45.000 --> 00:52:47.000 Hey. Nope. Okay. 00:52:47.000 --> 00:52:58.000 In some cases I know that it wasn't a misunderstanding. It was the deliberate decision not to implement what was called the condomaster reports or no. The counter reports. 00:52:58.000 --> 00:53:08.000 They deliberately just implemented some of the strategies. 00:53:08.000 --> 00:53:10.000 Yeah? 00:53:10.000 --> 00:53:12.000 Okay, dann. 00:53:12.000 --> 00:53:15.000 Are you. 00:53:15.000 --> 00:53:18.000 Up like uh. 00:53:18.000 --> 00:53:24.000 Edit these tickets in the next days, and um. 00:53:24.000 --> 00:53:37.000 Yeah, the regarding just these repod providers that only have some standard views. The question remains whether you actually want to support harvesting the reports. 00:53:37.000 --> 00:53:42.000 Because that would be a. Significant. 00:53:42.000 --> 00:53:52.000 Difference to the usual reports that would have to be taken into account. When you, for example, then have the e-user tree, or plugin. 00:53:52.000 --> 00:53:58.000 Which just has some of the standard use available. But not, maybe not the data you want to use for for evaluations. 00:53:58.000 --> 00:54:03.000 Yep. 00:54:03.000 --> 00:54:07.000 Okay, um. Our privatisation is. 00:54:07.000 --> 00:54:10.000 Just list here, and um. 00:54:10.000 --> 00:54:20.000 You have time with this feature for the credentials and the report types, so we can. I can. 00:54:20.000 --> 00:54:26.000 Make the updates on these tickets, and then we can talk about again. This. 00:54:26.000 --> 00:54:29.000 New feature. Um. 00:54:29.000 --> 00:54:32.000 That it's merged with the repop types and. 00:54:32.000 --> 00:54:37.000 If we say that that's our feature that we want to. 00:54:37.000 --> 00:54:41.000 Then I can. We can start with the implementation. But. 00:54:41.000 --> 00:54:47.000 I think we start with this one here, and um. 00:54:47.000 --> 00:54:54.000 I think dates are done so, and remove India harvester function, count for. 00:54:54.000 --> 00:54:58.000 Okay, und ähm. 00:54:58.000 --> 00:55:03.000 I think we should skip this part here for today. 00:55:03.000 --> 00:55:07.000 But for your information. 00:55:07.000 --> 00:55:10.000 It's a feature to. 00:55:10.000 --> 00:55:14.000 At Templates in usage. 00:55:14.000 --> 00:55:17.000 Um. I think it's. 00:55:17.000 --> 00:55:20.000 We should talk about this in the next meeting. 00:55:20.000 --> 00:55:22.000 To have more time for this. 00:55:22.000 --> 00:55:24.000 Um. 00:55:24.000 --> 00:55:29.000 Node. It's not the right one. 00:55:29.000 --> 00:55:31.000 Here integrated providers. 00:55:31.000 --> 00:55:34.000 Um. 00:55:34.000 --> 00:55:36.000 It should be. 00:55:36.000 --> 00:55:39.000 And uh. 00:55:39.000 --> 00:55:50.000 A helpful feature that you can automatically fill out the input fields from the counter. Registry informations. 00:55:50.000 --> 00:55:56.000 You can select a provider from counter registry and usage. 00:55:56.000 --> 00:56:01.000 Fetch the data from counter registry and fill out all the fields automatically. 00:56:01.000 --> 00:56:13.000 So it's planned, and I think it's it's better when we talk about this in the next meeting, when we Have More Time For This. 00:56:13.000 --> 00:56:24.000 Yeah. But if if you add a check of the reports endpoint, you might have the information about the reports from 2 sources. 00:56:24.000 --> 00:56:28.000 Once from from the registry, and once from the reports endpoint. 00:56:28.000 --> 00:56:42.000 And I would suggest to actually use the one from the reports endpoint. If you have that information available and use the register information as a fallback. 00:56:42.000 --> 00:56:48.000 Because the the reports endpoint might be more pro precise than what you find in the registry. 00:56:48.000 --> 00:56:57.000 And this would also work for providers that are not in the registry, so. 00:56:57.000 --> 00:56:59.000 Yeah? 00:56:59.000 --> 00:57:00.000 Yeah. So um. 00:57:00.000 --> 00:57:02.000 That would be the better choice. 00:57:02.000 --> 00:57:09.000 You. You can read the ticket, and we should talk about this in the next meeting. So. 00:57:09.000 --> 00:57:15.000 To see if this is a good feature for you, or should we add more. 00:57:15.000 --> 00:57:18.000 Um. 00:57:18.000 --> 00:57:20.000 We would like to try. 00:57:20.000 --> 00:57:24.000 Without caching the data. 00:57:24.000 --> 00:57:29.000 So, but if it's necessary, we at. 00:57:29.000 --> 00:57:34.000 Uh via the data to the database. 00:57:34.000 --> 00:57:37.000 If it's needed so. But we. 00:57:37.000 --> 00:57:42.000 Would like to try it on snapshot if it's possible to load the data. 00:57:42.000 --> 00:57:46.000 Menu configuring the the usage data provider. 00:57:46.000 --> 00:57:51.000 But we have to see how well it works. 00:57:51.000 --> 00:57:54.000 And if it's not work, then works, then. 00:57:54.000 --> 00:57:58.000 We should add a caching process. 00:57:58.000 --> 00:58:14.000 Yeah, caching. What makes sense in in the. In the sense that you don't have to request that information. Multiple times when configuring multiple identity multiple users, data providers in in. 00:58:14.000 --> 00:58:23.000 In a short time, but not storing that information for a longer time, because it might might change. 00:58:23.000 --> 00:58:34.000 So, if if it's not. If the the response isn't fast enough, you could, Tell me, and I will talk to the. 00:58:34.000 --> 00:58:37.000 Colleagues who are running that service. 00:58:37.000 --> 00:58:44.000 Yeah, or there is an a way to. 00:58:44.000 --> 00:58:49.000 Make a whitelist for different institutions. 00:58:49.000 --> 00:58:56.000 To do have can make more requests. 00:58:56.000 --> 00:59:05.000 Yeah, that would be another issue if you, if you run into some some limit where the the requests are refused. But, I don't think that that's. 00:59:05.000 --> 00:59:09.000 Every concern here. 00:59:09.000 --> 00:59:13.000 Ja. 00:59:13.000 --> 00:59:15.000 So. 00:59:15.000 --> 00:59:20.000 The question is, when we meet again. So. 00:59:20.000 --> 00:59:24.000 I think we need time to implement these features. 00:59:24.000 --> 00:59:30.000 Here, and. 00:59:30.000 --> 00:59:37.000 So if it makes sense to. 00:59:37.000 --> 00:59:42.000 I think. 00:59:42.000 --> 00:59:45.000 I'm on vacation, I think. 00:59:45.000 --> 00:59:50.000 At the end of April. 00:59:50.000 --> 00:59:56.000 But there's also Eastern time. 00:59:56.000 --> 01:00:01.000 These meetings, so. 01:00:01.000 --> 01:00:04.000 When when we have East. 01:00:04.000 --> 01:00:09.000 Ist und schreiben, was. 01:00:09.000 --> 01:00:10.000 Okay, dann ist. 01:00:10.000 --> 01:00:11.000 April 6.th This is the Monday. 01:00:11.000 --> 01:00:17.000 So I I think there's a rule we shouldn't have a meeting in the last. 01:00:17.000 --> 01:00:20.000 Week of the month. 01:00:20.000 --> 01:00:24.000 That was a suggestion from the one of the councils. 01:00:24.000 --> 01:00:26.000 In uh. 01:00:26.000 --> 01:00:31.000 Four weeks. 01:00:31.000 --> 01:00:34.000 You mean on on that would be much. Thirties. 01:00:34.000 --> 01:00:37.000 Yes. 01:00:37.000 --> 01:00:43.000 That's the week before Easter. I'm not sure I I could make it. 01:00:43.000 --> 01:00:49.000 I'm not sure if everybody else would be able. 01:00:49.000 --> 01:00:51.000 It's okay for the other. 01:00:51.000 --> 01:00:54.000 Members. 01:00:54.000 --> 01:00:57.000 March thirty. 01:00:57.000 --> 01:00:59.000 Okay. Then I'll. 01:00:59.000 --> 01:01:02.000 Create your invitation for you. 01:01:02.000 --> 01:01:05.000 And then we meet in. 01:01:05.000 --> 01:01:11.000 In four weeks ago. 01:01:11.000 --> 01:01:15.000 So, and then I think it makes sense to talk about. 01:01:15.000 --> 01:01:18.000 Dieses feature hier. And. 01:01:18.000 --> 01:01:26.000 So make make sure that it fits the requirements so, and. 01:01:26.000 --> 01:01:29.000 Okay. 01:01:29.000 --> 01:01:31.000 Done have a nice sunny day. 01:01:31.000 --> 01:01:37.000 And see you all. 01:01:37.000 --> 01:01:41.000 Bye.