Interoperability in Action
This is a modal window.
Das Video konnte nicht geladen werden, da entweder ein Server- oder Netzwerkfehler auftrat oder das Format nicht unterstützt wird.
Formale Metadaten
| Titel |
| |
| Untertitel |
| |
| Serientitel | ||
| Anzahl der Teile | 39 | |
| Autor | ||
| Mitwirkende | ||
| Lizenz | CC-Namensnennung 3.0 Unported: Sie dürfen das Werk bzw. den Inhalt zu jedem legalen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen. | |
| Identifikatoren | 10.5446/51375 (DOI) | |
| Herausgeber | ||
| Erscheinungsjahr | ||
| Sprache | ||
| Produzent |
Inhaltliche Metadaten
| Fachgebiet | ||
| Genre | ||
| Abstract |
|
2
3
9
10
14
17
22
23
26
39
00:00
Diagramm
07:07
Computeranimation
14:14
ComputeranimationFlussdiagramm
16:28
Computeranimation
16:47
Computeranimation
18:33
ComputeranimationVorlesung/Konferenz
20:25
Computeranimation
21:01
Computeranimation
22:18
Flussdiagramm
24:40
Computeranimation
Transkript: Englisch(automatisch erzeugt)
00:10
Hi everyone, I hope you can hear me fine. Welcome to this session, take your seats. The idea is that by the end we should all be able to do a tower like this.
00:25
Hope you are ready and we do a lot of energy. I'm Gabriela Mejias, I'm the engagement lead for Orchid. I work with organizations increasing the adoption and awareness of Orchid in Europe.
00:41
Julie, my colleague from the Heidelberg University Library, who is a software developer and has contributed to the plugin. Before I continue, I would like to know how many of you know what Orchid is? Okay, so most of you, great.
01:01
I don't need to give you much of an introduction then, but the goal of Orchid is to solve the name ambiguity issue that's actually one of the goals and I'll continue later on. So Orchid is a not-for-profit organization.
01:23
It's very important for me to tell you this, we have an open governance and we are registered as a non-profit organization in the US, that means our bylaws prohibit the organization to be sold. I just want to make sure that you know that.
01:42
And we provide open tools, so the Orchid ID that most of you know, to identify researchers. We also offer APIs and that's what makes the plugin, the OJS Orchid plugin possible. And a registry that you can use, organizations can use,
02:03
to synchronize research data. And today we've talked a lot and heard a lot about open science and also about inclusion. For us these are also core values and we express this a little bit
02:27
on this diagram and for us openness means also interoperability. So as you can see here, the idea is that the researchers
02:40
with their Orchid ID can use their ID, can connect their ID through our system, like when submitting an article, when applying for a grant or connecting the ID into their repository, into their system at their institution,
03:04
and to be able to achieve this, we work with all organizations in the research landscape. And actually the plugin that we're going to present today is a joint effort from PKP, the Heidelberg University Library,
03:23
which is part of our German consortium, and we collaborated as well. And yes, this fits on the publisher sector. So I wanted to also tell you something about our community.
03:46
We have more than 7 million IDs registered and as I said before, we are a non-profit organization, we finance ourselves through membership fees, institutional membership fees. Currently we have more than 1,100 members in more than 40 countries
04:03
and these members are building these integrations with Orchid, meaning implementing Orchid IDs in their workflows and integrating our APIs into their systems to make this interoperability possible
04:20
so that data flows from one system to another, across organizations, across countries, to save the researcher's time, and to make data reusable as well. And I mentioned our APIs before, so I'm going to go into more detail now.
04:43
We are an open organization and therefore we have a public API that's open for everyone to use, it's free to use. With the public API, organizations can obtain an ID and read data that is marked as public on Orchid records.
05:06
Does everybody know what API means? Yes, okay. So it means application programming interface, so it's basically a tool that allows you to exchange data between your systems and the Orchid registry.
05:24
The public API is free to use, everybody can use it for free and it allows you to obtain an ID and read data on Orchid records that's public. Our member organizations have the benefit of using the member API.
05:42
This allows the same functionalities as the public API plus the functionality to add data to Orchid records or update the data that you add and also read trusted parties' information. So on the Orchid record there are three levels of privacy
06:02
controlled by each user or each researcher. Public means the data is available to everyone through the registry and through the API. Trusted parties is the second level, that means that the researcher needs to authorize this organization to read this information
06:25
and the last level is private, that means only the researcher or the user can access this information. Most of the data on the Orchid registry is public but most of the email addresses are marked as private.
06:41
And again we're an open organization, what we do every year is for the open access week we release our public data file, which is an XML file that contains all data that's public on the Orchid records and this is published under a CCO license.
07:04
So the member API allows you to read public and trusted parties' data, add or update information and we have another API for our consortium members or premium members that also allows
07:22
to synchronize information by sending a notification every time something changes on an Orchid record you can register a call back URL, you will receive a pin on that URL and then you'll know something changed on that record and you can update or synchronize that data
07:42
on your systems. And some information, some statistics for you to know the volume of data flowing in our registry. Currently we have more than 45 million of works.
08:01
We call it works and not publications because we consider many times of contributions, not only publications but also preprints, software, data sets, patents, conference posters and many more. You can see that there are more than 17 million unique DOIs
08:24
and most of this data is being added to our registry by member organizations. Actually the plug-in that we will see today allows more of this data to be able to get to the Orchid records
08:46
and as I'm going to show you now, this is an example of this interoperability using the APIs between systems. This is an example of an Orchid record and this is an example of a publication
09:02
being added to an Orchid record by the plug-in and this is an example from a researcher that has authored an article on a journal published by the Heidelberg University Library and as you can see here,
09:23
the source of the information is not the author herself but instead the journals. So for us, this is also a way of adding trust and transparency to the research process
09:40
and as you can see there as well, there's a DOI on the article that's been pushed by the plug-in and we integrate many different types of persistence, identifiers since this also contributes
10:00
to more interoperability and reusability and visibility of the research data. Yes, we've put together some resources, some links about the plug-in, some video tutorials and the plug-in guide
10:25
that was developed together with PKP in a virtual sprint as Caitlin mentioned today and now I'm going to hand over to Dulip who will explain you more
10:40
about the technical details of the plug-in. Thank you. Is only this mic is enough or I would like to later go to the computer
11:01
then I mean I would need that also. Hi, this is working like this. Okay, as Gabriela mentioned, I work for the University Library of Heidelberg and I will go through now how we did this OJS plug-in.
11:23
First, if everybody is clear about OJS, I think now I would not go to that detail and I will show you the plug-in and as we are always developing in a community, I also want to show you
11:42
who has contributed from beginning to this plug-in and then after that we will go to the questions. So this is OJS and it is standard and the development history specification and I'm having some demos from videos how the integration is done.
12:02
This is an image of settings from the OJS plug-in OJS Oki plug-in is a generic plug-in. It is generic means it is a plug-in which directly interacts a lot with OJS system and currently we support Oki API version 2.1
12:24
and the plug-in can be configured to use both the member API and the public API. Also as Gabriela mentioned, we are having this sandbox API and you can also configure that and we also allow that you can log all the communication
12:44
with the API or only the errors that you can configure through the plug-in. So some historical facts. The first development of this Oki plug-in was done by the University Library of Pittsburgh
13:00
and then later it was taken into public knowledge project PKP official plug-in and the Heidelberg University Library what we did was practically adding the support for the member API and a lot of community members helped and as we had here in this conference also we had some software sprints.
13:22
A lot of people contributed their ideas. Actually developing this kind of a plug-in is not the challenge, it's not the technology. It is the people contributing and you're getting the ideas and we have communicated everything how the plug-in communication went in the GitHub issue then if you are interested later you can see
13:41
and we also invite you to contribute or give you ideas or if you have also errors you can write there. So this is a formal specification what we are supporting. You can choose any kind of the four possibilities what you are having.
14:01
So now I have some videos. I have to go there and hopefully
14:21
so it is working. This is how you would set up the plug-in in OJS. First you go to the settings and you have your website settings then you go to the plug-ins
14:42
and you can find this plug-in in the plug-in gallery. You can just choose the plug-in and here I have already installed therefore it says I can update but generally it would ask you to install and you just click there.
15:02
And that's it for the installation. Then we can go to the installed plug-ins and you will see it under the section generic plug-ins. Here under the settings now you can configure if you are using the sandbox API
15:22
or the production API but what we would recommend and also first you test with the sandbox API and when everything is finished you can apply for the public API credentials and I have to also mention if you are using the sandbox API
15:41
Oki allows only to use Mailinator accounts. Mailinator is a service where you can have free email addresses if you are also considered with your privacy and do not want to give your email address to third part is you can use MailNets for other things also. Then you configure it here.
16:05
So choose the API settings and give your credentials and you can decide if you want to send emails and you set the error logging level
16:21
and then that's it. The configuration is simple. So the next thing next video where I am going to show is this plug-in allows authorizing Oki accounts for users who are insider
16:42
or others who are users of the OJS system that is the first example that I am going to show. Sorry. To do that when you have logged into your profile
17:04
you have to go to your public profile settings then if you have enabled the OJS plug-in then you will see this button to connect to your Oki ID and you will also see first that there is a small introduction
17:21
that you can read before going into the connecting with the Oki.
17:41
So after that I will also go again back to the Oki. Then we are connecting to the Oki profile. Here you have to log in with your Oki account because this is configuring with the Sandbox API I am using the Melanator account.
18:11
So that's it. Then what is happening in the background is the OJS system connects to the API and authorizes and gets a token
18:21
and it saves in the OJS and this green button is always a sign that it is verified by Oki. So now I am doing a submission
18:49
using this authenticated user.
19:06
That's my test profile.
19:32
Oh, I am sorry. I have to wait. It is the external author submission not the one, the other video I will show you
19:41
from the authorized user. I have mixed the videos. Here what I am doing is I am inviting an external author to the system using the Oki plugin.
20:11
So here we can configure that Do I want to send an authorization request to the external author?
20:26
And at this moment it sends an email to the author.
20:45
So the user can now authorize that OJS system here. What is happening in the behind is that the external author gives access for the OJS system that it can retrieve this token from Oki. Then you are redirected to OJS.
21:06
Now when you see the profile of this external author, you will see that his or her Oki ID is there.
21:24
Then we are done with the editing of the article and now we are going to publish. Exactly at this moment when you are publishing it, it sends the metadata from OJS system to the Oki.
21:46
So when I go back to the Oki page and when I refresh this webpage you will see that the article metadata is in the Oki page.
22:07
So here you see the article title and the article links and the metadata that this is the Oki ID membership from the University of Heidelberg
22:20
and also it is shown as the source. So now I am going to show you the other video where you think that is the internal author. So because I am already authenticated,
22:50
I can just publish. So when I am refreshing it now,
23:12
I will also have, it is the same process.
23:28
So now we have added the author and we are going to go to the OJS reader interface. In the reader interface, now you are seeing that this green button,
23:41
this is verified Oki ID. Earlier, some historical background in OJS, two versions. You could add Oki IDs without verification. We see with a lot of consultation with Oki organization
24:01
and also with discussion with infrastructure providers, we have decided that we do not want Oki IDs that are not authenticated and we are also thinking for older systems what we are going to, actually I want to answer some of the questions which can come.
24:22
We are also thinking of how we would ask the authors who are not authorized to send emails and get their permission that we get. Our systems have always verified Oki IDs.
24:41
So I think that was it. Let me see. Yes. As we always do, the next steps, what we are going to do,
25:02
we are discussing in this GitHub issue. You can have a look there. And, yeah, this is, again, some of the resources directly connected here. Yeah. Thank you very much for listening. And if you have questions, now... Thank you.