We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Integrated management of Project, Funding and Research Data

00:00

Formal Metadata

Title
Integrated management of Project, Funding and Research Data
Subtitle
the experience of BORIS Portal
Title of Series
Number of Parts
9
Author
Contributors
License
CC Attribution 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language
Production Year2022
Production PlaceBerlin

Content Metadata

Subject Area
Genre
Abstract
BORIS project, based on DSpace-CRIS, is about: -a customized workflow for projects, interoperability with internal project management, and link to project investigators and project results. -custom managing of Documents for Projects, Funding and Datasets Integrations: -Integrate UniBE HR application (PARIS) to synch Researchers and Organizations -Integration datasets with Publication portal
Keywords
Computer animation
Computer animation
Computer animation
Computer animation
Transcript: English(auto-generated)
We're coming to the next talk of the D-Space Braxstraf in 2022, the integrated management of project funding and research data, the experience of Boris Portal from University of Bern. With me, I have Zumi and Ricardo. Thanks for your presentation. The stage is yours.
Thank you. Hi, everyone. Welcome to our presentation. And thank you for giving us the opportunity to talk about our project, Boris Portal. My name, as already mentioned, is Zumi Sonteram. I work at the Open Science team at the University Library of Bern.
And today I'm going to present with Ricardo Fazio for science. He's a project manager there and our main point of contact for this project. I will be starting with some background information on what exactly Boris Portal is about.
And the second part, Ricardo will be talking about some implementation that has been customized for our repository.
Here you can see the services we provide for the University of Bern members. And I won't be getting into much details about all of them. But apart from the open access support and research data management support,
you can see that we have three items, the Boris publications, the Boris thesis and the Boris Portal icon, which seem to be very similar. Boris is shortened for Boris Bern Open Repository and Information System.
And in this next slide, it will clarify the reason for it. So Boris Portal, here in this graph, is the institutional repository which uses DSpace.
And at the moment, only contains research project funding and research data information. However, we do also have Boris publications and Boris thesis using e-prints.
In the near future, it is our goal to integrate Boris publications and Boris thesis into Boris Portal to then only have one main platform for all the research information. So we work with DSpace version 5 for Boris Portal and we went live September last year.
So it's not that far away. There are two applications for Boris Portal in our case.
For one, the publication of project and funding information was a requirement from the WISE Rectorate Research of the University of Bern. So they are one of our project partners, since they are interested in having a collection of those information to have an overview of the current projects at the University of Bern.
Another project partner is the clinical trial unit of the Inverspital Ben, which is the University Hospital of Bern. The clinical trial unit part was mostly interested in the research data repository part.
So now I won't be going into much details of the project and funding information, what we do have for the submission, all the metadata and so on, since this is probably something you already know a lot about.
But I would like to go into the research data item aspect of Boris Portal briefly. So it is our institutional research data repository of the University of Bern,
where you can publish research data and or metadata, as well as supplementary documents such as codebooks and so on. You can make the research data item citeable. We have a DOI and we also have the Creative Commons licenses.
And it meets the requirements of the most important funder, according to the FAIR data principles. And I think yesterday we also had a similar talk about managing the access of research data.
So this will be kind of similar. In our case, which is special, we do have this thing that we do not allow users to upload sensitive data.
However, it is possible to upload metadata and its associated documents and a data transfer agreement. Here you can see a little bit more about this managing the data access part.
We have four access types, open, embargoed, restricted and closed. And you can put this on every data file you upload into Boris Portal.
Before I hand over to Ricardo, who will be talking a little bit more in detail about those upload steps,
I would like to mention a few things we would like to tackle in the future. It is planned to work on the integration of Boris Portal into the credit opening process, which is like an internal process at the university that would make it easier for the researcher to not have to submit the same information
to the repository and for opening a credit. Then we would also like to build interfaces to the databases of the research funders, such like the Swiss National Science Foundation.
And of course, we would also like to improve on the overview of research activities, of faculties, institutes, centres and individuals. And as already mentioned before,
we are also working on the migration of Boris publications, so on from e-prints to D-Space. And of course, lastly, also working on and talking about the migration process to D-Space 7.
Now, please, Ricardo, you can... Okay, thank you. Thank you. Yeah, I would like to... We have a lot of work done with collaboration with the University of Bern staff. And I would like to present four issues,
four requests that we implemented in the repository. The first one is, as Sumi said, is about the upload step. Because we had the requirement to upload the...
Obviously, for the research data submission, we have to upload obviously the file for the data
from the datasets that more or less, you can say, the common files that is uploaded in every submission, then the data transfer agreement and other supplementary files. We decided to create, to implement and extend the upload step
with three forms that allows the researchers to upload each type of bitstream. And each type of bitstream is saved in a specific bundle.
Also, as you may see from the table, the availability of the uploading of each bundle is based on the value of the metadata access rights that is defined during the submission.
Okay, we can go... Please, can go. Okay, thank you. Also, we added the managing of Creative Commons,
Creative Commons license for each bitstream. The Creative Commons is saved as a specific metadata for each bitstream, instead of having only one Creative Commons license for the entire item.
Actually, in the submission, you have also the metadata to apply the Creative Commons license to the whole item. And this is also used as, let's say, a default value for the uploaded bitstreams that the submitter will upload.
And then obviously, you can go into the file list and change the license from there.
I think we can go over. Thank you. Also, we had another requirement to let the people easily upload documents about funding and projects.
As Sumi mentioned, Boris Portal is on this space five. So, in this space, Chris five. So, in this space, Chris five, there is still the item and the other entities are still different objects, different type of objects, in respect of the space seven.
So, we implemented the creation of funding and project as a submission style, let's say, to ease the submitter life easier.
And also, at the end of the submission of the funding of a project, a new entity, a new object is created, is increased. And from the page of the object, you can start the submission of a document.
This is, again, a new submission of a special item that is of type document. And they connect the relation between the item and the object is automatically done using the authority framework in this space, Chris.
And also during submission, the submitter can also pick from the researcher profiles, some person, in order to give them the permission to read and download those documents.
At the end of the submission of this special type, these special items, these items will be visible into the object page with a specific component on the object page.
Okay, we can go. Okay. Also, we had to synchronize and the information from the Human Resources database that is called PARIS.
I hope I pronounced it correctly. And from PARIS, we import the researcher's information and the faculty and department. In this space, Chris, they become researcher profiles and organization units.
This is done mainly using ETL transformation. This is done using Pentium Suite. And this ETL, take the data from PARIS and transform this data in the
Excel format that is used by a standard import framework of this space, Chris, file. And in this way, we import and update every day the information from the Human Resources database.
The interesting thing here is that we save the unique ID from the Human Resources database that is called GUID.
As the external ID of the researcher profile that in this space, Chris is the source ID. And also, we have configured the login that use Shibboleth to receive the GUID as the net ID of the person.
So, we have the profiles and as soon as the user logs in via Shibboleth, a post-login action that is triggered as soon as the login is successful.
Tries to connect the researcher profile and the person using the net ID and the source ID of the researcher profile.
In this way, every user is automatically connected to this researcher profile without the need to search and try to connect or disturbing too much the administrator of the repository.
Next. Thank you. And the last issue, the requirement that we had is to, as Sumi mentioned, there is still the Boris publication portal, and that is based on eprints.
So, we had to connect the research data and the project to the related publications in Boris publication. This was done using a lookup on eprints during the submission of the research data or the project.
And this lookup, again, the authority framework from this space, Chris, and queries the searching point of eprints.
And the eprints gives as a response a JSON that is called in citation
format. This means that the data that we receive are a citation of the publication and obviously the eprints ID. The eprints ID is saved as authority of this metadata and obviously the citation is saved as a value.
So, we use the eprints ID to create a rendering to create a link to the actual publication. But obviously, we are also preparing for the import, as Sumi mentioned, preparing for the import in order
to be able to recreate the connection easily between research data and its publication project and its publication.
And I think that it's all for me. I hope I will not be too long. And if you have any questions, please. Perfect. Thank you. We already have a question. The creative commons licenses for each bitstream, will this be made available for all DSPACE 5 users?
Not for now, because actually this requirement came from University of Bern for the first time for us.
And then we didn't have many requests of this kind, but it's possible it can be ordered to the community code, obviously.
Yes, I think there's interest, at least in the chat over here, to get this feature to DSPACE 5.
Okay, any other questions? You can open your mic if you want to be recorded, if you're okay with that and ask directly, or you can type your questions into the Zoom chat.
What's your approximate schedule for the DSPACE 7 migration? We are still in discussion about when exactly that would be.
At the moment we have planned to first do the migration of Boris publications like this from eprints to DSPACE first and then do the migration to DSPACE 7.
But everything is still in discussion, work in progress. So it could be. Yes, Ricardo, please. Yeah, sorry. Just to add that obviously we know that the migration will be done in the near future.
And we, University of Bern for Science are working on this Boris portal, looking forward for the DSPACE 7. So we will not, everything that we implemented, for example, the submission of the CRIS entities is
done looking for the DSPACE 7 submission that will, let's say, remove the difference between entities and items.
So this is our, we are not still scheduling the DSPACE 7, but we are working with this vision, let's say. Yeah, great. I don't see any other questions. Ricardo, thanks a lot for this great talk.
Thanks to you. I hope we meet each other at the DSPACE 7 CRIS workshop later this afternoon. Thank you. Bye bye. Thank you. Goodbye.