Venue CSV columns#
To create SKG-IF venues, name each query result after a column listed below, as defined by the official Venue properties.
Column |
Description |
Example |
|---|---|---|
|
Primary key; groups all rows for one venue |
|
|
Venue name |
|
|
Venue type: |
|
|
Venue acronym or short name |
|
|
Name of the conference or book series |
|
|
Venue creation date or datetime in ISO 8601 format |
|
|
Identifier scheme for venues: |
|
|
The external identifier |
|
Both identifier fields must have a value for the pair to be used, so rows with an empty field are skipped.
Access rights#
A status is required to create the access rights object, so a description without a status is skipped.
Column |
Description |
Example |
|---|---|---|
|
Access status: |
|
|
Qualification of the access status |
|
Contributions#
RAMOSE groups rows for the same contributor through the internal key, while rows without that key or an agent name are skipped. A named contributor must have a local identifier; roles are collected without duplicates, and an external identifier is included only when both contribution_by_identifier_scheme and contribution_by_identifier_value have a value.
Column |
Description |
Example |
|---|---|---|
|
Contributor local identifier |
|
|
Groups rows that describe one contributor |
|
|
Contributor role: |
|
|
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 |
|
|
External identifier of the contributor |
|
The converter also accepts the declared-affiliation columns documented for Contributions.