Product CSV columns#
To convert SPARQL results into SKG-IF research products, write the operation’s query so that its result variables match the column names listed below.
Multiple rows per product are expected because identifiers, contributors, manifestations, citations, topics, as well as titles and abstracts in different languages, may produce different combinations. The converter groups and deduplicates their values.
Optional fields with no data are omitted from the output.
Only local_identifier and product_type are required at the product level.
Core metadata#
Official reference: Research product properties.
Column |
Description |
Example |
|---|---|---|
|
Primary key; groups all rows for one product |
|
|
SKG-IF product type: |
|
|
Product title |
|
|
ISO 639-1 language code for the title. Falls back to |
|
|
Product abstract |
|
|
ISO 639-1 language code for the abstract. Falls back to |
|
Product identifiers#
Official reference: identifiers.
Both identifier_scheme and identifier_value must be non-empty for an identifier to be included; rows where either is empty are skipped.
Column |
Description |
Example |
|---|---|---|
|
Identifier scheme for research products: |
|
|
The external identifier |
|
Contributions#
Official reference: contributions.
A contributor row is processed only when both contribution_role and _contribution_key are non-empty. The agent needs at least a family name, given name, or full name. Identifier scheme/value pairs and declared affiliation scheme/value pairs are co-dependent: both must be non-empty to be included.
Column |
Description |
Example |
|---|---|---|
|
Contributor local identifier |
|
|
The role of the contributing agent: |
|
|
CRediT contribution type: |
|
|
Family name. Its presence marks the contributor as a person |
|
|
Given name |
|
|
Full name (for organisations or agents without split names) |
|
|
Identifier scheme for the contributor: |
|
|
The external identifier of the contributor |
|
|
Affiliation local identifier |
|
|
Name of the declared affiliation organisation |
|
|
Short name or acronym of the affiliation |
|
|
ISO 3166-1 alpha-2 country code of the affiliation (e.g., IT) |
|
|
Identifier scheme for the affiliation |
|
|
The external identifier of the affiliation |
|
|
Organisation type: |
|
|
Website URL of the affiliation |
|
|
Alternative name of the affiliation |
|
See also Internal columns for contributor deduplication and ordering.
Internal#
These columns are consumed by the converter for deduplication and ordering. They do not appear in the JSON-LD output.
Column |
Description |
Example |
|---|---|---|
|
Deduplication key for contributors; also serves as the node identifier in the linked list that determines ordering within each role |
|
|
Points to the |
|
Contributors are ordered by role (author, then editor, then publisher) and within each role by the linked list formed by _contribution_key / _contribution_next_key.
Topics#
Official reference: topics.
topic_term anchors each topic entry; rows without it are skipped. Identifier and provenance fields are pairwise co-dependent: topic_identifier_scheme/topic_identifier_value and topic_provenance_associated_with/topic_provenance_trust must both be non-empty.
Column |
Description |
Example |
|---|---|---|
|
|
|
|
Identifier scheme for the topic: |
|
|
The external identifier of the topic |
|
|
Label describing the topic |
|
|
ISO 639-1 language code for the topic label. Falls back to |
|
|
|
|
|
Trust value for the relation, normalized to [0,1]. Provenance entries without trust are skipped |
|
Manifestations#
Official reference: manifestations.
The converter creates a manifestation only when at least one complete value can be mapped to the output. The following pairs must be populated together when used: manifestation_identifier_scheme/manifestation_identifier_value, manifestation_dates_type/manifestation_dates_value, manifestation_biblio_pages_first/manifestation_biblio_pages_last, manifestation_biblio_in_name/manifestation_biblio_in_local_identifier, manifestation_biblio_in_identifier_scheme/manifestation_biblio_in_identifier_value, and manifestation_biblio_hosting_data_source_identifier_scheme/manifestation_biblio_hosting_data_source_identifier_value.
Use _manifestation_key to group rows belonging to the same manifestation. Distinct keys create distinct objects in the manifestations list. When the column is empty, all manifestation values for the product belong to one object.
Column |
Description |
Example |
|---|---|---|
|
The URL of the class identifying the manifestation type (e.g. |
|
|
Label describing the manifestation type (e.g. |
|
|
ISO 639-1 language code for the type label. Falls back to |
|
|
URL of the schema that defines the manifestation type |
|
|
Internal key used to group and deduplicate manifestation rows; omitted from the JSON-LD output |
|
|
Identifier scheme for the manifestation (distinct from product-level identifiers): |
|
|
The external identifier of the manifestation |
|
|
The type of date: |
|
|
ISO 8601 date string; partial values like |
|
|
Peer review status: |
|
|
Peer review type: |
|
|
Access status: |
|
|
Qualification of the access status |
|
|
The URL of the licence for the manifestation |
|
|
Version identifier (for software or research data manifestations) |
|
|
Volume number |
|
|
Issue number |
|
|
The edition (for journals and books) |
|
|
Manifestation number within the venue (e.g., chapter number) |
|
|
The starting page. Both |
|
|
The ending page |
|
|
Venue local identifier |
|
|
Venue name. Both this field and |
|
|
Identifier scheme for the venue: |
|
|
Venue identifier value |
|
|
Venue acronym or short name |
|
|
Local identifier of the data source hosting the manifestation. Its presence triggers the hosting data source sub-object |
|
|
Name of the hosting data source |
|
|
Identifier scheme for the hosting data source |
|
|
Identifier value for the hosting data source |
|
Funding#
Official reference: funding.
funding_local_identifier anchors each grant entry; rows without it are skipped. Both funding_agency_name and funding_agency_local_identifier must be non-empty for the agency sub-object to be built. Identifier pairs (funding_identifier_scheme/funding_identifier_value and funding_agency_identifier_scheme/funding_agency_identifier_value) are co-dependent.
Column |
Description |
Example |
|---|---|---|
|
Grant local identifier |
|
|
Grant number |
|
|
Grant title |
|
|
ISO 639-1 language code for the grant title. Falls back to |
|
|
Grant abstract |
|
|
ISO 639-1 language code for the grant abstract. Falls back to |
|
|
Grant acronym |
|
|
Identifier scheme for the grant |
|
|
The external identifier of the grant |
|
|
Funding stream (e.g. “Horizon Europe”) |
|
|
Funding agency local identifier |
|
|
Name of the funding agency |
|
|
Short name of the funding agency |
|
|
ISO 3166-1 alpha-2 country code of the funding agency |
|
|
Identifier scheme for the funding agency |
|
|
The external identifier of the funding agency |
|
|
Organisation type of the funding agency: |
|
|
Website URL of the funding agency |
|
Relevant organisations#
Official reference: relevant_organisations.
A row is included only when relevant_organisation_local_identifier has a value. The name is optional, while identifier scheme/value pairs are co-dependent.
Column |
Description |
Example |
|---|---|---|
|
Organisation local identifier |
|
|
Organisation name |
|
|
Short name or acronym |
|
|
ISO 3166-1 alpha-2 country code |
|
|
Identifier scheme for the organisation |
|
|
The external identifier of the organisation |
|
|
Organisation type: |
|
|
Website URL of the organisation |
|
|
Alternative name of the organisation |
|