Reports
The Reports source contains metadata records describing Technical Reports.
This section provides information about the Reports source ,
listing each field available for Reports, with details
about the field value type, including whether it may be used as a facet
and whether it is a multi-value field. The table also contains information about whether
the field may be used in the where
section and whether the
field the field may be used in the entity fields filter.
The page also lists the fields included in each fieldset available
for Reports, and each aggregation indicator available.
Reports Fields
Fields are used to perform searches on the source they belong to.
Field |
Type |
Multi? |
Filter? |
Facet? |
Description |
---|---|---|---|---|---|
|
Literal: string |
The abstract of the report. |
|||
|
Literal: json |
✓ |
Ordered list of authors names and their affiliations, as they appear in the source. The list can include researcher and organization identifiers, when available. |
||
|
Entity: categories |
✓ |
✓ |
✓ |
|
|
Entity: categories |
✓ |
✓ |
✓ |
|
|
Entity: categories |
✓ |
✓ |
✓ |
|
|
Entity: categories |
✓ |
✓ |
✓ |
|
|
Entity: categories |
✓ |
✓ |
✓ |
|
|
Entity: categories |
✓ |
✓ |
✓ |
|
|
Entity: categories |
✓ |
✓ |
✓ |
|
|
Entity: categories |
✓ |
✓ |
✓ |
|
|
Entity: categories |
✓ |
✓ |
✓ |
SDG - Sustainable Development Goals |
|
Entity: categories |
✓ |
✓ |
✓ |
|
|
Literal: json |
✓ |
Concepts describing the main topics of the report (note: automatically derived from the text using machine learning). |
||
|
Literal: json |
✓ |
Relevancy scores for concepts. 1 |
||
|
Literal: date |
✓ |
Date when the report was published, in the format ‘YYYY-MM-DD’. |
||
|
Literal: date |
✓ |
Date when the record was inserted into Dimensions (note: this field does not support exact match on the data, only range filters e.g. <= or `>=’). |
||
|
Literal: string |
✓ |
Digital object identifier. |
||
|
Literal: json |
✓ |
External identifiers available from the report publisher (e.g. OSTI ID). |
||
|
Literal: json |
✓ |
Sponsors/funders of the research/report, as they appear in the source. |
||
|
Entity: organizations |
✓ |
✓ |
✓ |
GRID organizations funding the report (only disambiguated). |
|
Entity: countries |
✓ |
✓ |
✓ |
Countries of the organizations funding the report. |
|
Literal: string |
✓ |
Dimensions report ID. |
||
|
Literal: string |
✓ |
Keywords, as provided by the source. |
||
|
Literal: string |
Original URL for the report. |
|||
|
Literal: json |
✓ |
Organizations publishing the report, as they appear in the source. |
||
|
Entity: organizations |
✓ |
✓ |
✓ |
GRID organizations publishing the report (only disambiguated). |
|
Entity: countries |
✓ |
✓ |
✓ |
Countries of the organizations publishing the report. |
|
Entity: cities |
✓ |
✓ |
✓ |
Cities of the organisations associated with the report, expressed as GeoNames ID and name. |
|
Entity: countries |
✓ |
✓ |
✓ |
Countries of the organisations associated with the report, expressed as GeoNames code and name. |
|
Entity: states |
✓ |
✓ |
✓ |
States of the organisations associated with the report, expressed as GeoNames codes (ISO-3166-2). |
|
Entity: organizations |
✓ |
✓ |
✓ |
Combined list of GRID organisations associated with the report, because the source marks them as responsible for it, or because they appear as authors affiliations. |
|
Entity: organizations |
✓ |
✓ |
✓ |
GRID organizations responsible for the report. Note: this can be different from the author affiliations. |
|
Entity: cities |
✓ |
✓ |
✓ |
Cities of the organisations responsible for the report, expressed as GeoNames ID and name. |
|
Entity: countries |
✓ |
✓ |
✓ |
Countries of the organisations responsible for the report, expressed as GeoNames code and name. |
|
Literal: json |
✓ |
Organizations responsible for the report, as they appear in the source. Note: this can be different from the author affiliations. |
||
|
Entity: states |
✓ |
✓ |
✓ |
States of the organisations responsible for the report, expressed as GeoNames codes (ISO-3166-2). |
|
Literal: string |
Title of a report. |
|||
|
Literal: integer |
✓ |
✓ |
Year when the report was published (note: when the date field is available, this is equal to the year part of the full date). |
- 1
Returned objects contain:
concept
,relevance
.For example:
{ "concepts_scores": [ { "concept": "professional relations", "relevance": 0.088 }, { "concept": "relation", "relevance": 0.062 }, { "concept": "representation", "relevance": 0.025 }, { "concept": "skald", "relevance": 6.984 }, { "concept": "Representations of Skalds", "relevance": 0.0 }, { "concept": "Sagas 1", "relevance": 0.0 } ] }
Reports Links
The diagram below provides an overview of the outgoing links from Reports to other sources.
Reports Fieldsets
Fieldsets are used to specify fields groups in the context of a return statement.
Fieldset |
Fields |
---|---|
|
|
|
|
Reports Indicators
Indicators are used to aggregate results in the context of a facet query.
Indicator |
Description |
---|---|
|
Total count |
Reports Search Indexes
Search indexes are used to perform full-text searches on the source they belong to. The default search index, which is used if none other is specified, is full_data
.
Search index |
Supports multi-index search |
Description |
---|---|---|
|
✓ |
The keyword will be searched in titles and abstracts of reports. |
|
✓ |
The keyword will be searched in all of the reports data. |
Reports Deprecations
This section lists fields and search fields that have been deprecated and should not be used.
Warning
This fields will be supported in versions 1.x and removed in the next major release. To ensure full compatibility with the upcoming major release, it is recommend to stop using deprecated fields as soon as possible.
Deprecated Fields
Reports source has no deprecated fields.
Partially Deprecated Fields
Reports source has no partially deprecated fields.
Deprecated Search Indexes
Reports source has no deprecated search indexes.