+
-
-
-
-
- The aggregation processes are continuously running and apply vocabularies as they are in a given
- moment of time.
- It could be the case that a vocabulary changes after the aggregation of one data source has
- finished,
- thus the aggregated content does not reflect the current status of the controlled vocabularies.
-
- In addition, the integration of ScholeXplorer and DOIBooost and some enrichment processes
- applied
- on the raw
- and on the de-duplicated graph may introduce values that do not comply with the current status
- of
- the OpenAIRE controlled vocabularies.
- For these reasons, we included a final step of cleansing at the end of the workflow
- materialisation.
- The output of the final cleansing step is the final version of the OpenAIRE Research Graph.
-
-
-
- -
-
-
+
-
- The OpenAIRE Research Graph is enriched by links mined by OpenAIRE’s full-text mining
- algorithms
- that scan the plaintexts of publications for funding information, references to datasets,
- software URIs, accession numbers of bioetities, and EPO patent mentions.
- Custom mining modules also link research objects to specific research communities, initiatives
- and infrastructures.
- In addition, other inference modules provide content-based document classification, document
- similarity, citation matching, and author affiliation matching.
-
- Project mining
- in OpenAIRE text mines the full-texts of publications in order to extract matches to funding
- project codes/IDs.
- The mining algorithm works by utilising
- (i) the grant identifier, and
- (ii) the project acronym (if available) of each project.
- The mining algorithm:
- (1) Preprocesses/normalizes the full-texts using several functions, which depend on the
- characteristics of each funder (i.e., the format of the grant identifiers), such as stopword
- and/or punctuation removal, tokenization, stemming, converting to lowercase; then
- (2) String matching of grant identifiers against the normalized text is done using database
- techniques; and
- (3) The results are validated and cleaned using the context near the match by looking at the
- context around the matched ID for relevant metadata and positive or negative words/phrases, in
- order to calculate a confidence value for each publication-->project link.
- A confidence threshold is set to optimise high accuracy while minimising false positives, such
- as matches with page or report numbers, post/zip codes, parts of telephone numbers, DOIs or
- URLs, accession numbers.
- The algorithm also applies rules for disambiguating results, as different funders can share
- identical project IDs; for example, grant number 633172 could refer to H2020 project EuroMix
- but
- also to Australian-funded NHMRC project “Brain activity (EEG) analysis and brain imaging
- techniques to measure the neurobiological effects of sleep apnea”.
- Project mining works very well and was the first Text & Data Mining (TDM) service of OpenAIRE.
- Performance results vary from funder to funder but precision is higher than 98% for all
- funders
- and 99.5% for EC projects.
- Recall is higher than 95% (99% for EC projects), when projects are properly acknowledged using
- project/grant IDs.
-
- Dataset extraction
- runs on publications full-texts as described in “High pass text-filtering for Citation
- matching”, TPDL 2017[1].
- In particular, we search for citations to datasets using their DOIs, titles and other metadata
- (i.e., dates, creator names, publishers, etc.).
- We extract parts of the text which look like citations and search for datasets using database
- join and pattern matching techniques.
- Based on the experiments described in the paper, precision of the dataset extraction module is
- 98.5% and recall is 97.4% but it is also probably overestimated since it does not take into
- account corruptions that may take place during pdf to text extraction.
- It is calculated on the extracted full-texts of small samples from PubMed and arXiv.
-
- Software extraction
- runs also on parts of the text which look like citations.
- We search the citations for links to software in open software repositories, specifically
- github, sourceforge, bitbucket and the google code archive.
- After that, we search for links that are included in Software Heritage (SH,
- https://www.softwareheritage.org) and return the permanent URL that SH provides for each
- software project.
- We also enrich this content with user names, titles and descriptions of the software projects
- using web mining techniques.
- Since software mining is based on URL matching, our precision is 100% (we return a software
- link
- only if we find it in the text and there is no need to disambiguate).
- As for recall rate, this is not calculable for this mining task.
- Although we apply all the necessary normalizations to the URLs in order to overcome usual
- issues
- (e.g., http or https, existence of www or not, lower/upper case), we do not calculate cases
- where a software is mentioned using its name and not by a link from the supported software
- repositories.
-
- For the extraction of bio-entities, we focus on Protein Data
- Bank (PDB) entries.
- We have downloaded the database with PDB codes and we update it regularly.
- We search through the whole publication’s full-text for references to PDB codes.
- We apply disambiguation rules (e.g., there are PDB codes that are the same as antibody codes
- or
- other issues) so that we return valid results.
- Current precision is 98%.
- Although it's risky to mention recall rates since these are usually overestimated, we have
- calculated a recall rate of 98% using small samples from pubmed publications.
- Moreover, our technique is able to identify about 30% more links to proteins than the ones
- that
- are tagged in Pubmed xmls.
-
- Other text-mining modules include mining for links to EPO
- patents, or custom mining modules for linking research objects to specific research
- communities,
- initiatives and infrastructures, e.g. COVID-19 mining module.
- Apart from text-mining modules, OpenAIRE also provides a document classification service that
- employs analysis of free text stemming from the abstracts of the publications.
- The purpose of applying a document classification module is to assign a scientific text one or
- more predefined content classes.
- In OpenAIRE, the currently used taxonomies are arXiv, MeSH (Medical Subject Headings), ACM and
- DDC (Dewey Decimal Classification, or Dewey Decimal System).
-
-
- [1] Foufoulas, Y., Stamatogiannakis, L., Dimitropoulos, H., & Ioannidis, Y. (2017, September).
- High-Pass Text Filtering for Citation Matching.
- In International Conference on Theory and Practice of Digital Libraries (pp. 355-366).
- Springer,
- Cham.
-
+ The OpenAIRE Research Graph is enriched by links mined by OpenAIRE’s full-text mining
+ algorithms
+ that scan the plaintexts of publications for funding information, references to datasets,
+ software URIs, accession numbers of bioetities, and EPO patent mentions.
+ Custom mining modules also link research objects to specific research communities, initiatives
+ and infrastructures.
+ In addition, other inference modules provide content-based document classification, document
+ similarity, citation matching, and author affiliation matching.
+
+
Project mining
+ in OpenAIRE text mines the full-texts of publications in order to extract matches to funding
+ project codes/IDs.
+ The mining algorithm works by utilising
+ (i) the grant identifier, and
+ (ii) the project acronym (if available) of each project.
+ The mining algorithm:
+ (1) Preprocesses/normalizes the full-texts using several functions, which depend on the
+ characteristics of each funder (i.e., the format of the grant identifiers), such as stopword
+ and/or punctuation removal, tokenization, stemming, converting to lowercase; then
+ (2) String matching of grant identifiers against the normalized text is done using database
+ techniques; and
+ (3) The results are validated and cleaned using the context near the match by looking at the
+ context around the matched ID for relevant metadata and positive or negative words/phrases, in
+ order to calculate a confidence value for each publication-->project link.
+ A confidence threshold is set to optimise high accuracy while minimising false positives, such
+ as matches with page or report numbers, post/zip codes, parts of telephone numbers, DOIs or
+ URLs, accession numbers.
+ The algorithm also applies rules for disambiguating results, as different funders can share
+ identical project IDs; for example, grant number 633172 could refer to H2020 project EuroMix
+ but
+ also to Australian-funded NHMRC project “Brain activity (EEG) analysis and brain imaging
+ techniques to measure the neurobiological effects of sleep apnea”.
+ Project mining works very well and was the first Text & Data Mining (TDM) service of OpenAIRE.
+ Performance results vary from funder to funder but precision is higher than 98% for all
+ funders
+ and 99.5% for EC projects.
+ Recall is higher than 95% (99% for EC projects), when projects are properly acknowledged using
+ project/grant IDs.
+
+
Dataset extraction
+ runs on publications full-texts as described in “High pass text-filtering for Citation
+ matching”, TPDL 2017[1].
+ In particular, we search for citations to datasets using their DOIs, titles and other metadata
+ (i.e., dates, creator names, publishers, etc.).
+ We extract parts of the text which look like citations and search for datasets using database
+ join and pattern matching techniques.
+ Based on the experiments described in the paper, precision of the dataset extraction module is
+ 98.5% and recall is 97.4% but it is also probably overestimated since it does not take into
+ account corruptions that may take place during pdf to text extraction.
+ It is calculated on the extracted full-texts of small samples from PubMed and arXiv.
+
+
Software extraction
+ runs also on parts of the text which look like citations.
+ We search the citations for links to software in open software repositories, specifically
+ github, sourceforge, bitbucket and the google code archive.
+ After that, we search for links that are included in Software Heritage (SH,
+ https://www.softwareheritage.org) and return the permanent URL that SH provides for each
+ software project.
+ We also enrich this content with user names, titles and descriptions of the software projects
+ using web mining techniques.
+ Since software mining is based on URL matching, our precision is 100% (we return a software
+ link
+ only if we find it in the text and there is no need to disambiguate).
+ As for recall rate, this is not calculable for this mining task.
+ Although we apply all the necessary normalizations to the URLs in order to overcome usual
+ issues
+ (e.g., http or https, existence of www or not, lower/upper case), we do not calculate cases
+ where a software is mentioned using its name and not by a link from the supported software
+ repositories.
+
+
For the extraction of bio-entities, we focus on Protein Data
+ Bank (PDB) entries.
+ We have downloaded the database with PDB codes and we update it regularly.
+ We search through the whole publication’s full-text for references to PDB codes.
+ We apply disambiguation rules (e.g., there are PDB codes that are the same as antibody codes
+ or
+ other issues) so that we return valid results.
+ Current precision is 98%.
+ Although it's risky to mention recall rates since these are usually overestimated, we have
+ calculated a recall rate of 98% using small samples from pubmed publications.
+ Moreover, our technique is able to identify about 30% more links to proteins than the ones
+ that
+ are tagged in Pubmed xmls.
+
+
Other text-mining modules include mining for links to EPO
+ patents, or custom mining modules for linking research objects to specific research
+ communities,
+ initiatives and infrastructures, e.g. COVID-19 mining module.
+ Apart from text-mining modules, OpenAIRE also provides a document classification service that
+ employs analysis of free text stemming from the abstracts of the publications.
+ The purpose of applying a document classification module is to assign a scientific text one or
+ more predefined content classes.
+ In OpenAIRE, the currently used taxonomies are arXiv, MeSH (Medical Subject Headings), ACM and
+ DDC (Dewey Decimal Classification, or Dewey Decimal System).
+
+
+ [1] Foufoulas, Y., Stamatogiannakis, L., Dimitropoulos, H., & Ioannidis, Y. (2017, September).
+ High-Pass Text Filtering for Citation Matching.
+ In International Conference on Theory and Practice of Digital Libraries (pp. 355-366).
+ Springer,
+ Cham.
-
-
Read more
+
-
-
Read less
+
-
@@ -521,7 +483,8 @@
- Zenodo community (16K results tagged)
- the data source it comes from (250K results tagged)
- The list of subjects, Zenodo communities and data sources used to enrich the products are defined
+ The list of subjects, Zenodo communities and data sources used to enrich the products are
+ defined
by
the managers of the community gateway or infrastructure monitoring dashboard associated with the
RC/RI.
@@ -530,11 +493,11 @@
-
-
-
+
- This process “propagates” properties and links from one product to another if between the two
+ This process “propagates” properties and links from one product to another if between the
+ two
there is a “strong” semantic relationship.
As of September 2020, the following procedures are in place:
@@ -549,13 +512,16 @@
by”
a dataset D.
Dataset D will get the link to project P.
- The relationships considered for this procedure are “isSupplementedBy” and “supplements”.
+ The relationships considered for this procedure are “isSupplementedBy” and
+ “supplements”.
-
- Propagation of related community/infrastructure/initiative from organizations to products
+ Propagation of related community/infrastructure/initiative from organizations to
+ products
via affiliation relationships: e.g. a publication with an author affiliated with
organization O.
- The manager of the community gateway C declared that the outputs of O are all relevant for
+ The manager of the community gateway C declared that the outputs of O are all relevant
+ for
his/her community C.
The publication is tagged as relevant for C.
@@ -563,7 +529,8 @@
Propagation of related community/infrastructure/initiative to related products: e.g.
publication associated to community C is supplemented by a dataset D.
Dataset D will get the association to C.
- The relationships considered for this procedure are “isSupplementedBy” and “supplements”.
+ The relationships considered for this procedure are “isSupplementedBy” and
+ “supplements”.
-
Propagation of ORCID identifiers to related products, if the products have the same
@@ -573,53 +540,45 @@
the same authors as the publication. Authors of D are enriched with the ORCIDs available
in
the publication.
- The relationships considered for this procedure are “isSupplementedBy” and “supplements”.
+ The relationships considered for this procedure are “isSupplementedBy” and
+ “supplements”.
-
-
-
Read more
+
-
-
-
-
-
-
-
-
- The aggregation processes are continuously running and apply vocabularies as they are in a given moment of time.
- It could be the case that a vocabulary changes after the aggregation of one data source has finished, thus the aggregated content does not reflect the current status of the controlled vocabularies.
+ The aggregation processes are continuously running and apply vocabularies as they are in a given
+ moment of time.
+ It could be the case that a vocabulary changes after the aggregation of one data source has
+ finished, thus the aggregated content does not reflect the current status of the controlled
+ vocabularies.
- In addition, the integration of ScholeXplorer and DOIBoost and some enrichment processes applied on the raw and on the de-duplicated graph may introduce values that do not comply with the current status of the OpenAIRE controlled vocabularies.
+ In addition, the integration of ScholeXplorer and DOIBoost and some enrichment processes applied on
+ the raw and on the de-duplicated graph may introduce values that do not comply with the current
+ status of the OpenAIRE controlled vocabularies.
For these reasons, we included a final step of cleansing at the end of the workflow materialisation.
The output of the final cleansing step is the final version of the OpenAIRE Research Graph.
-
-
-
-
-
-
@@ -637,7 +596,8 @@
-
DSpace & EPrints
- repositories can install the OpenAIRE plugin to expose OpenAIRE compliant metadata records via their
+ repositories can install the OpenAIRE plugin to expose OpenAIRE compliant metadata records via
+ their
OAI-PMH endpoint and offer to researchers the possibility to link their depositions to the funding
project, by selecting it from the list of project provided by OpenAIRE
@@ -647,20 +607,16 @@
Sygma automatically fetches from the OpenAIRE Search API the list of publications and datasets in
the
OpenAIRE Research Graph that are linked to the project.
- The user can select the research products from the list and easily compile the continuous reporting
+ The user can select the research products from the list and easily compile the continuous
+ reporting
data of the project.
-
-
-
-
-
-
![Stats Analysis](assets/graph-assets/about/architecture/stats_analysis.svg)
@@ -670,7 +626,8 @@
producing
the charts for funders, research initiative, infrastructures, and policy makers that you can see on
MONITOR.
- Based on the information available on the graph, OpenAIRE provides a set of indicators for monitoring
+ Based on the information available on the graph, OpenAIRE provides a set of indicators for
+ monitoring
the funding and research impact and the uptake of Open Science publishing practices,
such as Open Access publishing of publications and datasets, availability of interlinks between
research
@@ -678,10 +635,6 @@
etc.
-
-
-
-
@@ -692,7 +645,7 @@
-
Microsoft Academic Graph
- which is made available under the ODC Attribution License.
+ which is made available under the ODC Attribution License.
For more information on Microsoft Academic Graph please also read
here.
@@ -700,21 +653,16 @@
https://www.openaire.eu/aggregation-and-content-provision-workflows
+
+ See all references
+
-
Data & Metrics
- Coming soon...
-
-
-
-
-
-
-
-
+ Data & Metrics
+
@@ -722,31 +670,35 @@
Infrastructure
-
-
- The OpenAIRE Research Graph is operated and maintained at the
+ The OpenAIRE Research Graph is operated and maintained at the ICM cutting-edge Technology centre
- with the facilities and staff guaranteeing robust operation of the whole system.
- Okeanos SuperComputer hosting the graph consists of 26016 cores in total providing 1082 Tflops/s.
- Whole setup is energy efficient with 1.554 Gflops/Watts Power Efficiency resulting in 160th place on the "Top500 by energy-eficiency" list (as of 2019).
-
-
![](assets/graph-assets/about/infrastructure.png)
-
- ICM supports the continuous operation of the infrastructure including data aggregation, deduplication, inference and provision ensuring seamless 24/7 system uptime and availability.
- System administration activities cover hardware maintenance and provisioning of the new computational resources, providing High Availability solutions to address resilience to failures by service-level redundancy and Load Balancing to distribute workloads uniformly across servers.
- The most crucial parts of the persisted graph are covered with backups along with well defined restore procedures.
- All the monitoring activities rely on an aggregated system-level monitoring accessible via various dashboards giving the better overview of system stability and potential requirements for system elements extension.
- System level monitoring is supplemented with monitoring availability of all the publicly accessible endpoints.
- Hence, the offer of the public API of OpenAIRE to third parties, is of high-standards.
-
-
- All the maintenance operations undertaken by experienced system administrators are founded on well established routines and emergency maintenance procedures.
-
-
-
-
-
-
+ with the facilities and staff guaranteeing robust operation of the whole system.
+ Okeanos SuperComputer hosting the graph consists of 26016 cores in total providing 1082 Tflops/s.
+ Whole setup is energy efficient with 1.554 Gflops/Watts Power Efficiency resulting in 160th place on the
+ "Top500 by energy-eficiency" list (as of 2019).
+
+
![](assets/graph-assets/about/infrastructure.png)
+
+ ICM supports the continuous operation of the infrastructure including data aggregation, deduplication,
+ inference and provision ensuring seamless 24/7 system uptime and availability.
+ System administration activities cover hardware maintenance and provisioning of the new computational
+ resources, providing High Availability solutions to address resilience to failures by service-level
+ redundancy and Load Balancing to distribute workloads uniformly across servers.
+ The most crucial parts of the persisted graph are covered with backups along with well defined restore
+ procedures.
+ All the monitoring activities rely on an aggregated system-level monitoring accessible via various
+ dashboards giving the better overview of system stability and potential requirements for system elements
+ extension.
+ System level monitoring is supplemented with monitoring availability of all the publicly accessible
+ endpoints.
+ Hence, the offer of the public API of OpenAIRE to third parties, is of high-standards.
+
+
+ All the maintenance operations undertaken by experienced system administrators are founded on well
+ established routines and emergency maintenance procedures.
+
@@ -756,11 +708,6 @@
Team
-
-
-
-
-
![Team](assets/graph-assets/about/team.svg)
@@ -768,14 +715,12 @@
Key team members contributing to the Research Graph
-
-
diff --git a/src/app/about/about.component.ts b/src/app/about/about.component.ts
index ddd6d3a..5b1fbad 100644
--- a/src/app/about/about.component.ts
+++ b/src/app/about/about.component.ts
@@ -55,15 +55,6 @@ export class AboutComponent implements OnInit {
this.subs.push(this._piwikService.trackView(this.properties, this.title).subscribe());
}
}
-
- goTo(id: string) {
- const yOffset = -100;
- const element = document.getElementById(id);
- if(element) {
- const y = element.getBoundingClientRect().top + window.pageYOffset + yOffset;
- window.scrollTo({top: y, behavior: 'smooth'});
- }
- }
changeTab(index: number) {
UIkit.switcher(this.tabs.nativeElement).show(index);
diff --git a/src/app/about/about.module.ts b/src/app/about/about.module.ts
index f8c8936..e0f9077 100644
--- a/src/app/about/about.module.ts
+++ b/src/app/about/about.module.ts
@@ -9,18 +9,22 @@ import {IconsModule} from "../openaireLibrary/utils/icons/icons.module";
import {IconsService} from "../openaireLibrary/utils/icons/icons.service";
import {arrow_right} from "../openaireLibrary/utils/icons/icons";
import {Schema2jsonldModule} from '../openaireLibrary/sharedComponents/schema2jsonld/schema2jsonld.module';
+import {NumbersModule} from '../openaireLibrary/sharedComponents/numbers/numbers.module';
+import {TeamComponent} from './team.component';
@NgModule({
imports: [
CommonModule,
- RouterModule.forChild([{
- path: '', component: AboutComponent
- }]),
+ RouterModule.forChild([
+ {path: '', component: AboutComponent},
+ {path: 'team', component: TeamComponent},
+ ]),
BreadcrumbsModule,
IconsModule,
- Schema2jsonldModule
+ Schema2jsonldModule,
+ NumbersModule
],
- declarations: [AboutComponent, ActionPointComponent],
+ declarations: [AboutComponent, ActionPointComponent, TeamComponent],
exports: [AboutComponent]
})
export class AboutModule {
diff --git a/src/app/about/action-point.component.ts b/src/app/about/action-point.component.ts
index bd73c90..1c992ac 100644
--- a/src/app/about/action-point.component.ts
+++ b/src/app/about/action-point.component.ts
@@ -7,12 +7,12 @@ import {animate, state, style, transition, trigger} from "@angular/animations";
diff --git a/src/app/about/faqs.ts b/src/app/about/faqs.ts
deleted file mode 100644
index b8bf5f8..0000000
--- a/src/app/about/faqs.ts
+++ /dev/null
@@ -1,6 +0,0 @@
-export const faqs = [
-/* {
- question: 'Test',
- answer: 'Test'
- }*/
-];
diff --git a/src/app/about/team.component.css b/src/app/about/team.component.css
new file mode 100644
index 0000000..a90064b
--- /dev/null
+++ b/src/app/about/team.component.css
@@ -0,0 +1,32 @@
+.uk-card .uk-card-flip-inner .front,
+.uk-card .uk-card-flip-inner .back {
+ border-radius: 5px;
+ box-shadow: 0 2px 5px #0000001a;
+ border: 1px solid #E0E0E0;
+ font-size: 14px;
+ font-family: "Roboto", sans-serif;
+ line-height: 19px;
+ color: rgba(26, 26, 26, 0.8);
+}
+
+.uk-card:hover .uk-card-flip-inner .front,
+.uk-card:hover .uk-card-flip-inner .back {
+ box-shadow: 0 6px 15px #0000001A;
+}
+
+.uk-card .front img,
+.uk-card .back img {
+ width: 150px;
+ height: 150px;
+ border-radius: 50%;
+ object-fit: cover;
+}
+
+.uk-card .back img {
+ width: 100px;
+ height: 100px;
+}
+
+.uk-card .uk-card-flip-inner .uk-text-muted {
+ color: rgba(26, 26, 26, 0.6);
+}
diff --git a/src/app/about/team.component.ts b/src/app/about/team.component.ts
new file mode 100644
index 0000000..ffed138
--- /dev/null
+++ b/src/app/about/team.component.ts
@@ -0,0 +1,85 @@
+import {Component} from '@angular/core';
+import {Breadcrumb} from '../openaireLibrary/utils/breadcrumbs/breadcrumbs.component';
+import {member, team} from './team';
+
+@Component({
+ selector: 'team',
+ template: `
+
+
+
+
+
+
+
Meet The Team
+
+
+
+
+
+
+
+
![]()
+
+
{{member.name}}
+
+ {{member.role}}
+
+
+
+
+
+
+
+
+
+
![]()
+
+
{{member.name}}
+
+
+
+ Role: {{member.role}}
+
+
+ Affiliation: {{member.affiliation}}
+
+
+ Country: {{member.country}}
+
+
+
+
+
+
+
+
+
+
+
+
+ `,
+ styleUrls: ['team.component.css']
+})
+export class TeamComponent {
+ public team: member[] = team;
+ public breadcrumbs: Breadcrumb[] = [
+ {
+ name: 'home',
+ route: '/'
+ },
+ {
+ name: 'about',
+ route: '/about'
+ },
+ {
+ name: 'Team'
+ }
+ ];
+}
diff --git a/src/app/about/team.ts b/src/app/about/team.ts
new file mode 100644
index 0000000..5c0d8d9
--- /dev/null
+++ b/src/app/about/team.ts
@@ -0,0 +1,135 @@
+export interface member {
+ name: string,
+ role: string,
+ affiliation: string,
+ country: string,
+ responsibilities: string,
+ photo: string,
+ active?: boolean
+}
+
+export const team: member[] = [
+ {
+ name: 'Alessia Bardi',
+ role: 'Researcher / Product Manager of the OpenAIRE Research Community Dashboard (CONNECT)',
+ affiliation: 'Institute of Information Science and Technologies, Italian National Research Council',
+ country: 'Italy',
+ responsibilities:
+ 'Responsible for the design and operation of the pipeline for the materialisation and data quality evaluation of the graph\n' +
+ 'Responsible for the integration of content for the communities using OpenAIRE CONNECT services.',
+ photo: 'alessia.jpg'
+ },
+ {
+ name: 'Amelie Bäcker',
+ role: 'Librarian',
+ affiliation: 'Bielefeld University Library',
+ country: 'Germany',
+ responsibilities: 'Metadata integration (standard cases), helpdesk support (OpenAIRE Guidelines, metadata integration).',
+ photo: 'amelie.jpg'
+ },
+ {
+ name: 'Andrea Dell Amico',
+ role: 'Τechnical Team - Systems Administrator',
+ affiliation: 'Institute of Information Science and Technologies, Italian National Research Council',
+ country: 'Italy',
+ responsibilities: 'Working on the computing and storage infrastructure on the CNR side, maintaining the Hadoop and ElasticSearch clusters.',
+ photo: 'dell_amico.jpg'
+ },
+ {
+ name: 'Andrea Mannocci',
+ role: 'Researcher/Data scientist',
+ affiliation: 'Institute of Information Science and Technologies, Italian National Research Council',
+ country: 'Italy',
+ responsibilities: 'Working on data analysis and quality of data.',
+ photo: 'mannocci.jpg'
+ },
+ {
+ name: 'Andreas Czerniak',
+ role: 'OpenAIRE Project Officer',
+ affiliation: 'Bielefeld University Library',
+ country: 'Germany',
+ responsibilities: 'Responsible with the UniBI team for the aggregation (collection and transformation) of metadata.',
+ photo: 'czerniak.jpg'
+ },
+ {
+ name: 'Claudio Atzori',
+ role: 'Software & Data Engineer / Data quality',
+ affiliation: 'Institute of Information Science and Technologies, Italian National Research Council',
+ country: 'Italy',
+ responsibilities:
+ 'Responsible for the design of graph processing pipeline, glueing the different stages together, from the content aggregation, to the end of the supply chain at the indexing stage.',
+ photo: 'claudio.jpg'
+ },
+ {
+ name: 'Eleni Zacharia-Lamprou',
+ role: 'Software Engineer - Postdoctoral Researcher',
+ affiliation: 'Athena Research Center (ARC)',
+ country: 'Greece',
+ responsibilities: 'Implementation of Text and Data Mining (TDM) modules, used in the graph Enrichment phase.',
+ photo: 'eleni.jpg'
+ },
+ {
+ name: 'Enrico Ottonello',
+ role: 'Technical Team',
+ affiliation: 'Institute of Information Science and Technologies, Italian National Research Council',
+ country: 'Italy',
+ responsibilities: 'Data engineering, aggregation, data curation along the graph enrichment steps.',
+ photo: 'enrico.jpg'
+ },
+ {
+ name: 'Harry Dimitropoulos',
+ role: 'Senior Scientific Associate',
+ affiliation: 'Athena Research Center (ARC)',
+ country: 'Greece',
+ responsibilities: 'Responsible for the Text and Data Mining (TDM) modules used in the graph Enrichment phase.',
+ photo: 'dimitropoulos.jpg'
+ },
+ {
+ name: 'Lampros Smyrnaios',
+ role: 'Software & Data Engineer / Research Assistant',
+ affiliation: 'Athena Research Center (ARC)',
+ country: 'Greece',
+ responsibilities: 'Development of a software to extract the full-texts from publications\' web-pages. These full-texts are used by the Text and Data Mining (TDM) modules. Implementation of Text and Data Mining (TDM) modules, used in the graph Enrichment phase.',
+ photo: 'lampros.jpg'
+ },
+ {
+ name: 'Michele De Bonis',
+ role: 'Technical Team',
+ affiliation: 'Institute of Information Science and Technologies, Italian National Research Council',
+ country: 'Italy',
+ responsibilities: 'Responsible for the deduplication phase and the creation of algorithms to identify groups of data into the graph.',
+ photo: 'de_bonis.jpg'
+ },
+ {
+ name: 'Miriam Baglioni',
+ role: 'Researcher / Software & Data Engineer / Data quality',
+ affiliation: 'Institute of Information Science and Technologies, Italian National Research Council',
+ country: 'Italy',
+ responsibilities: 'Responsible for the graph enrichment steps not related to mining, and to the production of the graph dumps.',
+ photo: 'miriam.jpeg'
+ },
+ {
+ name: 'Paolo Manghi',
+ role: 'Chief Technical Officer',
+ affiliation: 'Institute of Information Science and Technologies, Italian National Research Council',
+ country: 'Italy',
+ responsibilities: 'Responsible for the design and roadmapping of the OpenAIRE infrastructure services, their operation, evolution, and interaction with third-parties.',
+ photo: 'paolo.png'
+ },
+ {
+ name: 'Sandro La Bruzzo',
+ role: 'Technical Team',
+ affiliation: 'Institute of Information Science and Technologies, Italian National Research Council',
+ country: 'Italy',
+ responsibilities: 'Responsible for the graph enrichment steps including the generation of DOIBoost.',
+ photo: 'sandro.jpg'
+ },
+ {
+ name: 'Yannis Foufoulas',
+ role: 'Software Engineer / Researcher',
+ affiliation: 'Athena Research Center (ARC)',
+ country: 'Greece',
+ responsibilities: 'Implementation of Text and Data Mining (TDM) modules used in the graph Enrichment phase.',
+ photo: 'yiannis.jpg'
+ }
+]
diff --git a/src/app/app.component.ts b/src/app/app.component.ts
index 178b476..b64198d 100644
--- a/src/app/app.component.ts
+++ b/src/app/app.component.ts
@@ -64,18 +64,13 @@ export class AppComponent implements OnInit, OnDestroy {
{
rootItem: new MenuItem("resources", "Resources", "", "/resources", false, [], null, {}),
items: [
- // new MenuItem("api", "API", "", "/resources", false, [], null, {}),
- // new MenuItem("schema", "Metadata Schema", "", "/resources", false, [], null, {}, null, "schema"),
- // new MenuItem("sources", "Sources", "", "/resources", false, [], null, {}, null, "sources"),
+ new MenuItem("api", "API", "", "/resources", false, [], null, {}),
+ new MenuItem("references", "References", "", "/resources/references", false, [], null, {})
]
},
{
rootItem: new MenuItem("contact", "Support", "", "/support", false, [], null, {}),
- items: [
- // new MenuItem("contact", "Contact", "", "/support", false, [], null, {}),
- // new MenuItem("documentation", "Documentation", "", "/support", false, [], null, {}, null, "documentation"),
- // new MenuItem("faq", "FAQs", "", "/support", false, [], null, {}, null, "faq"),
- ]
+ items: []
}
];
if(!isHome) {
diff --git a/src/app/contact/contact.component.html b/src/app/contact/contact.component.html
index 5242c1f..a2be63f 100644
--- a/src/app/contact/contact.component.html
+++ b/src/app/contact/contact.component.html
@@ -83,9 +83,9 @@
diff --git a/src/app/home/home.component.css b/src/app/home/home.component.css
index 7adfcdb..25a19b3 100644
--- a/src/app/home/home.component.css
+++ b/src/app/home/home.component.css
@@ -51,10 +51,6 @@
animation-duration: 1.5s;
}
-.numbers-background {
- background: transparent url('assets/graph-assets/home/5.svg') repeat-x center bottom;
-}
-
.fade-out {
visibility: hidden;
opacity: 0;
diff --git a/src/app/home/home.component.html b/src/app/home/home.component.html
index 4a9373f..a8156d7 100644
--- a/src/app/home/home.component.html
+++ b/src/app/home/home.component.html
@@ -115,6 +115,24 @@