sources

This table contains all the sources for our datasets. The description column contains JSON encoded as text that contains useful additional fields like a longer descriptive text "additionalInfo".

Data license: CC-BY

1 row where datasetId = 695 sorted by id descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: createdAt (date), updatedAt (date)

id ▲ name description createdAt updatedAt datasetId additionalInfo link dataPublishedBy
2855 Meat conversion efficiencies - Alexander et al. (2016) 
{
    "link": null,
    "retrievedDate": null,
    "additionalInfo": "Livestock conversion efficiencies are given as reported in Alexander et al. (2016). Alexander, P., Brown, C., Arneth, A., Finnigan, J., & Rounsevell, M. D. (2016). Human appropriation of land for food: the role of diet. Global Environmental Change, 41, 88-98. Available at: http://www.sciencedirect.com/science/article/pii/S0959378016302370?via%3Dihub#bib0330 [accessed 24th August 2017].\n\n'Feed conversion ratio' is defined as the quantity of feed inputs required to produce one kilogram of edible product. This is measured in kilograms of dry-matter feed per kilogram of edible weight product.\n\nProtein and energy efficiency are both measured as the percentage of protein or energy converted from feed to animal product.\n\nOriginal data sources as used in this paper are as follows:\n\nSmil (2013).Should We Eat Meat? Evolution and Consequences of Modern Carnivory Wiley, New York, USA (2013).\n\nOpio et al. (2013). Greenhouse Gas Emissions from Ruminant Supply Chains\u2013A Global Life Cycle Assessment Food and Agriculture Organization of the United Nations (FAO), Rome, Italy (2013).\n\nMacleod et al. Greenhouse Gas Emissions from Pig and Chicken Supply Chains \u2013 A Global Life Cycle Assessment Food and Agriculture Organization of the United Nations (FAO), Rome, Italy (2013).",
    "dataPublishedBy": "Meat conversion efficiencies - Alexander et al. (2016)",
    "dataPublisherSource": null
}
 2017-08-24 18:38:10 2018-03-14 14:58:31 Meat conversion efficiencies - Alexander et al. (2016) 695 Livestock conversion efficiencies are given as reported in Alexander et al. (2016). Alexander, P., Brown, C., Arneth, A., Finnigan, J., & Rounsevell, M. D. (2016). Human appropriation of land for food: the role of diet. Global Environmental Change, 41, 88-98. Available at: http://www.sciencedirect.com/science/article/pii/S0959378016302370?via%3Dihub#bib0330 [accessed 24th August 2017]. 'Feed conversion ratio' is defined as the quantity of feed inputs required to produce one kilogram of edible product. This is measured in kilograms of dry-matter feed per kilogram of edible weight product. Protein and energy efficiency are both measured as the percentage of protein or energy converted from feed to animal product. Original data sources as used in this paper are as follows: Smil (2013).Should We Eat Meat? Evolution and Consequences of Modern Carnivory Wiley, New York, USA (2013). Opio et al. (2013). Greenhouse Gas Emissions from Ruminant Supply Chains–A Global Life Cycle Assessment Food and Agriculture Organization of the United Nations (FAO), Rome, Italy (2013). Macleod et al. Greenhouse Gas Emissions from Pig and Chicken Supply Chains – A Global Life Cycle Assessment Food and Agriculture Organization of the United Nations (FAO), Rome, Italy (2013).   Meat conversion efficiencies - Alexander et al. (2016)

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE "sources" (
	"id" INTEGER PRIMARY KEY AUTOINCREMENT,
	"name" VARCHAR(512) NULL  ,
	"description" TEXT NOT NULL  ,
	"createdAt" DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP ,
	"updatedAt" DATETIME NULL  ,
	"datasetId" INTEGER NULL, additionalInfo TEXT GENERATED ALWAYS as (JSON_EXTRACT(description, '$.additionalInfo')) VIRTUAL, link TEXT GENERATED ALWAYS as (JSON_EXTRACT(description, '$.link')) VIRTUAL, dataPublishedBy TEXT GENERATED ALWAYS as (JSON_EXTRACT(description, '$.dataPublishedBy')) VIRTUAL,
	FOREIGN KEY("datasetId") REFERENCES "datasets" ("id") ON UPDATE RESTRICT ON DELETE RESTRICT
);
CREATE INDEX "sources_datasetId" ON "sources" ("datasetId");