The relevant columns for this dataset relating to publications for each sample are
- author = AUTHORS
- publication_year = year
- title = title
- journal = (no SEAD equivalent, but can be added to full_reference)
- place of publication = (no SEAD equivalent, but can be added to full_reference)
To make full_reference combine all of the above using the Extra Columns tab, and the expression{author} ({publication_year}) {title}, {journal}, {place_of_publication}
as of 2026-09-18 the above code to make full_reference gives a warning: "´full_reference´ conflicts with an existing or reserved result column."
Roger has been asked about this, and will look into it. Roger replied 2026-09-29:
Ok, I think this is a false positive error message i.e. it can be ignored. I will fix it though, I think the issue is caused by having an extra column used as a business key. The check tests if the name is used, and finds it in “business keys”. Having an extra column as a business key is perfectly legal.
YAML as of 2026-09-17
name: citation
type: entity
system_id: system_id
keys:
- full_reference
columns:
- author
- publication_year
- title
- journal
- place_of_publication
public_id: biblio_id
source: datasheet
drop_duplicates: true
check_functional_dependency: false
drop_empty_rows: true
extra_columns:
full_reference: '{author} ({publication_year}) {title}, {journal}, {place_of_publication}'
year: '{publication_year}'
