A research community is a community of practice that gathers together researchers and practitioners
- with common research interests (e.g. a research discipline or a specific research topic) and,
- possibly, a decisional board. In some cases, a community builds and grows in the context of a research
- infrastructure that provides services and tools supporting the research activities of the members of a
- community. In other cases, a community builds and grows in the context of one or more research
- projects, forming what we call a “research initiative”.
A research community is a community of practice that gathers together researchers and practitioners
+ with common research interests (e.g. a research discipline or a specific research topic) and,
+ possibly, a decisional board. In some cases, a community builds and grows in the context of a research
+ infrastructure that provides services and tools supporting the research activities of the members of a
+ community. In other cases, a community builds and grows in the context of one or more research
+ projects, forming what we call a “research initiative”.
The RCD offers on demand Community Gateways that communities can customize to fit their sharing,
+ publishing and discovery needs. Through the RCD, gateway managers can configure the respective
+ Community Gateway by providing (i) the criteria identifying the subset of the OpenAIRE Research Graph
+ that pertains to the community, and (ii) the community statistics to be made public or private.
Once a Community Gateway has been created, several thematic service integration patterns are
+ possible:
+
+
+ Community-specific repository: OpenAIRE can guide your
+ repository managers on how to make the repository
+ “OpenAIRE-compliant”.
+ The gateway managers can configure the gateway so that all metadata records collected from the
+ repository are available in the gateway. If the repository manager wants to get the enrichments
+ OpenAIRE applies to the records, he/she can
+ activate the Broker service using the
+ Content
+ Provider Dashboard.
+
+
+ Continuous publishing: thematic services, once authorized by the
+ user, can publish their outputs (e.g. datasets, digital experiments) on behalf of the user. Thematic
+ services and digital experiment platforms can be easily enhanced with a publishing step by
+ integrating the Zenodo API. To know
+ more, check out
+ the pilot we have designed with the EPOS-IT infrastructure.
+
+ Community web site: you can use the
+ OpenAIRE Search API to show the
+ research products relevant to your community on your own website.
+
Discovery and reproducibility: Your community will have a single entry
+ point where all research products, of any type (literature, datasets, software, workflows, protocols),
+ are gathered together and linked with semantic relationships. Researchers can find a research product
+ in the gateway (e.g. a research dataset) and easily find out everything related to it and that is
+ needed to re-use it, but also to replicate and reproduce a research activity (e.g. software used to
+ process the dataset, the journal article where the research is described).
The RCD offers on demand Community Gateways that communities can customize to fit their sharing,
- publishing and discovery needs. Through the RCD, gateway managers can configure the respective
- Community Gateway by providing (i) the criteria identifying the subset of the OpenAIRE Research Graph
- that pertains to the community, and (ii) the community statistics to be made public or private.
+
Sharing:
+ scientific literature is only the tip of the iceberg. With a Community Gateway, you say to the members
+ of your community that everything they produce is relevant and that they should get credit for it.
Once a Community Gateway has been created, several thematic service integration patterns are
- possible:
-
-
- Community-specific repository: OpenAIRE can guide your
- repository managers on how to make the repository
- “OpenAIRE-compliant”.
- The gateway managers can configure the gateway so that all metadata records collected from the
- repository are available in the gateway. If the repository manager wants to get the enrichments
- OpenAIRE applies to the records, he/she can
- activate the Broker service using the
- Content
- Provider Dashboard.
-
-
- Continuous publishing: thematic services, once authorized by the
- user, can publish their outputs (e.g. datasets, digital experiments) on behalf of the user. Thematic
- services and digital experiment platforms can be easily enhanced with a publishing step by
- integrating the Zenodo API. To know
- more, check out
- the pilot we have designed with the EPOS-IT infrastructure.
-
- Community web site: you can use the
- OpenAIRE Search API to show the
- research products relevant to your community on your own website.
-
-
+
Credit for all: Making research data, software, methods and scientific
+ workflows available “as soon as possible” is one of the “mantra” of Open
+ Science. If your community has integrated Zenodo into a digital experiment platform, researchers no
+ longer bear the burden of manually publishing their research products, while it is also easier for
+ them to publish different versions, which reflect different stages of their activities.
Discovery and reproducibility: Your community will have a single entry
- point where all research products, of any type (literature, datasets, software, workflows, protocols),
- are gathered together and linked with semantic relationships. Researchers can find a research product
- in the gateway (e.g. a research dataset) and easily find out everything related to it and that is
- needed to re-use it, but also to replicate and reproduce a research activity (e.g. software used to
- process the dataset, the journal article where the research is described).
-
-
Sharing:
- scientific literature is only the tip of the iceberg. With a Community Gateway, you say to the members
- of your community that everything they produce is relevant and that they should get credit for it.
-
-
Credit for all: Making research data, software, methods and scientific
- workflows available “as soon as possible” is one of the “mantra” of Open
- Science. If your community has integrated Zenodo into a digital experiment platform, researchers no
- longer bear the burden of manually publishing their research products, while it is also easier for
- them to publish different versions, which reflect different stages of their activities.
-
-
Awareness:
- Thanks to dedicated pages of the Community Gateway you can suggest best practices to the researchers
- of the community. Open Science experts of OpenAIRE will be available to assist you.
-
+
Awareness:
+ Thanks to dedicated pages of the Community Gateway you can suggest best practices to the researchers
+ of the community. Open Science experts of OpenAIRE will be available to assist you.
OpenAIRE has onboarded in the EOSC Market Place both the RCD, as a service that offers on-demand
- Community Gateways, and the Gateways as services openly accessible by researchers to explore specific
- domains of interest.
-
OpenAIRE has onboarded in the EOSC Market Place both the RCD, as a service that offers on-demand
+ Community Gateways, and the Gateways as services openly accessible by researchers to explore specific
+ domains of interest.
+
The gateway is hosted on a virtual machine operated by OpenAIRE and hosted at the ICM data centre. The Gateway
+ is built with Angular and uses RESTful APIs, built with Java and the Spring Framework, to access the
+ OpenAIRE Research Graph. OpenAIRE is responsible to keep the back-end and front-end services
+ up-to-date and monitors the uptime and usage of the gateway, via the matomo web analytics platform.
+ Aggregated usage data is used by the OpenAIRE team for reporting purposes and does not include any
+ personal data.
+
Researchers of the community shall not pay to access the Community Gateway.
+
For the deployment and maintenance of a gateway, OpenAIRE may need support to cover part of the
+ costs (hardware, hardware management, application administration, software maintenance, and text
+ mining).
The gateway is hosted on a virtual machine operated by OpenAIRE and hosted at the ICM data centre. The Gateway
- is built with Angular and uses RESTful APIs, built with Java and the Spring Framework, to access the
- OpenAIRE Research Graph. OpenAIRE is responsible to keep the back-end and front-end services
- up-to-date and monitors the uptime and usage of the gateway, via the matomo web analytics platform.
- Aggregated usage data is used by the OpenAIRE team for reporting purposes and does not include any
- personal data.
-
Researchers of the community shall not pay to access the Community Gateway.
-
For the deployment and maintenance of a gateway, OpenAIRE may need support to cover part of the
- costs (hardware, hardware management, application administration, software maintenance, and text
- mining).
-
-
Please contact us to learn more about the service and the possible
- options.
-
- Spread the word about the OpenAIRE
- Open
- Innovation programme
- for SMEs, start-ups and research labs. The programme’s goal is to discover, support and fund
- innovative
- ideas and implementations of software in the Open Science domain.
-
+
+
Open Innovation Programme
+ Spread the word about the OpenAIRE
+ Open
+ Innovation programme
+ for SMEs, start-ups and research labs. The programme’s goal is to discover, support and fund
+ innovative
+ ideas and implementations of software in the Open Science domain.
- `
+ `,
+ styleUrls: ['learn-how.component.css']
})
export class LearnHowComponent implements OnInit {
public pageContents = null;
diff --git a/src/app/learn-how/learnInDepth/learn-in-depth-routing.module.ts b/src/app/learn-how/learnInDepth/learn-in-depth-routing.module.ts
deleted file mode 100644
index 2a5fe1e..0000000
--- a/src/app/learn-how/learnInDepth/learn-in-depth-routing.module.ts
+++ /dev/null
@@ -1,16 +0,0 @@
-import {NgModule} from '@angular/core';
-import {RouterModule} from '@angular/router';
-
-import {PreviousRouteRecorder} from '../../openaireLibrary/utils/piwik/previousRouteRecorder.guard';
-import {LearnInDepthComponent} from "./learn-in-depth.component";
-import {IsRouteEnabled} from "../../openaireLibrary/error/isRouteEnabled.guard";
-
-@NgModule({
- imports: [
- RouterModule.forChild([
- { path: '', component: LearnInDepthComponent, canActivate: [IsRouteEnabled], canDeactivate: [PreviousRouteRecorder] }
-
- ])
- ]
-})
-export class LearnInDepthRoutingModule { }
diff --git a/src/app/learn-how/learnInDepth/learn-in-depth.component.ts b/src/app/learn-how/learnInDepth/learn-in-depth.component.ts
deleted file mode 100644
index 6e017c2..0000000
--- a/src/app/learn-how/learnInDepth/learn-in-depth.component.ts
+++ /dev/null
@@ -1,257 +0,0 @@
-import {Component, OnInit} from '@angular/core';
-import {Breadcrumb} from "../../openaireLibrary/utils/breadcrumbs/breadcrumbs.component";
-import {EnvProperties} from "../../openaireLibrary/utils/properties/env-properties";
-import {ActivatedRoute, Router} from "@angular/router";
-import {Meta, Title} from "@angular/platform-browser";
-import {SEOService} from "../../openaireLibrary/sharedComponents/SEO/SEO.service";
-import {PiwikService} from "../../openaireLibrary/utils/piwik/piwik.service";
-import {HelperService} from "../../openaireLibrary/utils/helper/helper.service";
-import {Subscriber} from "rxjs";
-import {properties} from "../../../environments/environment";
-
-@Component({
- selector: 'learn-in-depth',
- template: `
-
-
-
-
-
-
-
-
-
-
-
-
-
Let’s set up a Gateway for your Community Together.
-
-
-
You don’t have to go alone.
-
-
We work with you in 4 collaborative steps to identify your needs, putting in
- practice our expertise on open science so you get the most out of OpenAIRE’s operational
- services.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
1. Analyse your needs
-
"Identify the scope and goals. Understand open science practices within EOSC
- and the OpenAIRE services."
-
-
In this stage, you get to talk to the OpenAIRE team. Share your expectations with us and let us give you
- all the details about the operational OpenAIRE services, which will be integrated into the Gateway for
- your community.
-
Here are the most important questions that the OpenAIRE team will ask you, in order to understand your
- scope and goals:
-
-
Do you want a gateway, where researchers can have access to all research products of a discipline? Do
- you want a gateway that gathers any research outcome, produced thanks to the funding and services of a
- given research infrastructure?
-
-
Is your community (in)formally organized in sub-communities? Would you like to browse research
- products and get statistics also for these sub-communities? For example, the European Grid
- Infrastructure (EGI) features “virtual organizations” that represent discipline-specific
- communities and/or specific research projects. The research infrastructure DARIAH, on the other hand, is
- organised in national nodes (e.g. DARIAH-IT, DARIAH-DE).
-
-
How can the OpenAIRE team identify the research products of your community, among all those available
- in the OpenAIRE Graph? Through a series of steps: set of keywords, acknowledgment statements, set of
- projects, set of repositories, etc. This can be partial and provisional information that will serve as a
- starting point to the OpenAIRE team. You will be able to refine and update this information, in the
- second phase “Develop a pilot”.
-
-
-
-
-
-
-
-
-
-
-
2. Develop a pilot
-
"We translate your needs into rules and processes and we configure
- operational OpenAIRE services."
-
-
Based on the information gathered in phase 1 “Analyse your needs”, the OpenAIRE team will set
- up a pilot Gateway. We will configure the OpenAIRE mining algorithms to identify research products of the
- OpenAIRE Graph that are relevant to your community. Those, together with some basic statistics, will be
- available in the pilot version of the Community Gateway that will be deployed on the OpenAIRE BETA
- infrastructure.
-
The OpenAIRE team will give you a demo of the Community Gateway, with details on how to refine and update
- the configuration of the Community Gateway, both in terms of criteria for including research products and
- in terms of logo and visible portal pages.
-
-
-
-
-
-
-
-
-
3. Test and Validate
-
"You validate and test your new Community Gateway (portal). If needed, we
- further refine and adapt to your needs."
-
-
Upon the completion of phase 2, take the time you need to test all its features, from search and browse
- for research products, to addition/removal of statistics from the portal. You can report any issue you
- might find and ask questions directly to the dedicated OpenAIRE team, via a specially designed
- collaboration tool.
-
Typically, this phase takes some months, as you will have to go through certain procedures. Change the
- configuration of the criteria to include research products, wait for the new configuration to be applied
- on the OpenAIRE graph and validate the results, before you actually decide that the coverage of research
- products for your community is adequate.
-
For some communities, the OpenAIRE team may also be able to implement dedicated mining algorithms (e.g.
- to find acknowledgement statements to your community/infrastructure in the full-texts of research
- articles) that may require several rounds of application, validation, and fine-tuning, before it reaches a
- high precision and recall. Your feedback is very important to minimize the effort and time needed for this
- process to complete.
-
-
-
-
-
-
-
-
-
-
-
4. Roll out the service
-
"We jointly roll out your new portal. You take over the business operations
- and start engaging your researchers."
-
-
Here we are: the coverage of research products is good, interesting statistics and charts have been
- selected, and the portal pages available for end-users are ready. We can roll out the Community Gateway
- and make it available to all the researchers of the community!
-
You, as a Community manager, become the main “promoter” of the Community Gateway. Engage the
- researchers of your community and, when applicable, inform the managers of the research infrastructure
- about the availability of tools for impact monitoring.
-
Remember that you will still be able to change the configuration of the Community Gateway in order to
- address any issue that may arise and to follow the evolution of the community (e.g. a new project or a new
- content provider that was not previously available in OpenAIRE).
-
Remember that you don’t have to go alone: the dedicated issue tracker you used in the “Test
- and Validate” phase is always available for you to contact the OpenAIRE team and ask for
- support.
-
-
-
-
-
-
-
-
-
-
-
-
-
Let us Help you develop a Collaborative Science
-
- Gateway.
-
- It is fast. It is reliable.