Specification of metadata sections¶
Each section in the amorphys metadata file(s) must have a certain specific format.
section¶
-
class
section Each section of
amorphyshas different properties of its own. But it can have an optional property,descriptionto describe itself.-
description¶ a human-readable
stringdescription of the section. It is recommended to include this property for every section, for increased understandability.
-
project¶
-
class
project The
projectsection ofamorphysis a subclass ofsection, and describes the organization of the project group.A typical
projectwould look like below:in: “project.json”¶{ "$schema": "https://raw.githubusercontent.com/gwappa/amorphys/master/schema/sections/project.json", "description": "the project organization for foraging experiment", "dataset": { "name": "HumanForagingBehavior_PostdocRoom", ... }, "people": { "Keisuke": { "name": "Keisuke S.K. Sehara", ... }, "Julien": { "name": "Julien Colomb", ... }, ... }, "affiliations": { "ChaosSoftware": { "name": "Chaos Software", ... }, ... }, "fundings": { "DFG": { "name": "Deutliche Forschungsgesellschaft", ... }, ... }, "data_published_by": [ { "$ref": "../people/Keisuke" }, { "$ref": "../people/Julien" } ] }
It consists of several fields:
-
description¶ a recommended field that is equivalent to that in
section.
-
people¶ a mapping to
contributorinstances representing the people involved in this project.
-
affiliations¶ a mapping to
institutioninstances representing the affiliations of the people involved.
-
funded_by¶ a mapping to
fundinginstances representing the funding sources for this project.
-