forked from D-Net/openaire-graph-docs
Minor (link) fixes
This commit is contained in:
parent
e21949a82c
commit
3d6d2f3523
|
@ -32,9 +32,9 @@ A vocabulary is a data structure that defines a list of terms, and for each term
|
||||||
[...]
|
[...]
|
||||||
```
|
```
|
||||||
|
|
||||||
Each vocabulary is typically used to control and harmonise the values available in a specific field characterising the bibliographic records. The example above provides a preview of the vocabulary used to clean the [result's instance typology](data-model/entities/other#instance).
|
Each vocabulary is typically used to control and harmonise the values available in a specific field characterising the bibliographic records. The example above provides a preview of the vocabulary used to clean the [result's instance typology](/data-model/entities/result#instance).
|
||||||
|
|
||||||
The content of the vocabularies can be accessed on [api.openaire.eu/vocabularies](https://api.openaire.eu/vocabularies/)
|
The content of the vocabularies can be accessed on [api.openaire.eu/vocabularies](https://api.openaire.eu/vocabularies/).
|
||||||
|
|
||||||
Given a value provided in the original records, the cleaning process looks for a synonym and, when found, resolves the corresponding term which is used in turn to build the cleaned record.
|
Given a value provided in the original records, the cleaning process looks for a synonym and, when found, resolves the corresponding term which is used in turn to build the cleaned record.
|
||||||
Each aggregation process applies vocabularies according to their definitions in a given moment of time, however, 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.
|
Each aggregation process applies vocabularies according to their definitions in a given moment of time, however, 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.
|
||||||
|
@ -47,7 +47,7 @@ Bibliographic records that do not meet minimal requirements for being part of th
|
||||||
Currently, the only criteria applied horizontally to the entire graph aims at excluding scientific results whose title is not meaningful for citation purposes.
|
Currently, the only criteria applied horizontally to the entire graph aims at excluding scientific results whose title is not meaningful for citation purposes.
|
||||||
Then, different criteria are applied in the pre-processing of specific sub-collections:
|
Then, different criteria are applied in the pre-processing of specific sub-collections:
|
||||||
|
|
||||||
* [Crossref filtering](data-provision/aggregation/doiboost#1-crossref-filtering)
|
* [Crossref filtering](/data-provision/aggregation/doiboost#crossref-filtering)
|
||||||
|
|
||||||
## Country cleaning
|
## Country cleaning
|
||||||
|
|
||||||
|
|
File diff suppressed because it is too large
Load Diff
|
@ -14,8 +14,8 @@
|
||||||
"write-heading-ids": "docusaurus write-heading-ids"
|
"write-heading-ids": "docusaurus write-heading-ids"
|
||||||
},
|
},
|
||||||
"dependencies": {
|
"dependencies": {
|
||||||
"@docusaurus/core": "2.0.1",
|
"@docusaurus/core": "^2.1.0",
|
||||||
"@docusaurus/preset-classic": "2.0.1",
|
"@docusaurus/preset-classic": "^2.1.0",
|
||||||
"@mdx-js/react": "^1.6.22",
|
"@mdx-js/react": "^1.6.22",
|
||||||
"clsx": "^1.2.1",
|
"clsx": "^1.2.1",
|
||||||
"hast-util-is-element": "^1.1.0",
|
"hast-util-is-element": "^1.1.0",
|
||||||
|
@ -26,7 +26,7 @@
|
||||||
"remark-math": "^3.0.1"
|
"remark-math": "^3.0.1"
|
||||||
},
|
},
|
||||||
"devDependencies": {
|
"devDependencies": {
|
||||||
"@docusaurus/module-type-aliases": "2.0.1"
|
"@docusaurus/module-type-aliases": "^2.1.0"
|
||||||
},
|
},
|
||||||
"browserslist": {
|
"browserslist": {
|
||||||
"production": [
|
"production": [
|
||||||
|
|
Loading…
Reference in New Issue