Is a Organisation a Node or a Blank Node?

A Organisation is a Node. Nodes are the fundamental items which store data. They are identified using a unique @id field. Blank Nodes are stored within them. An example of a Node is a Site which might describe an area of cropland, or a Term which describes an item in the food system.

What are the internal properties of a Organisation?

The following properties are automatically set when data are uploaded to the HESTIA platform: @context, @id and @type. If they are included in an uploaded file, they will be overwritten.

Organisation | HESTIA

Organisation

Viewing version

Type:Node

View examples

The organisation which manages the Site(s).

Field	Type	Required	Definition
name	string	No	The name of the Organisation.
description	string	No	A description of the Organisation.
boundary	object	No	A nested GeoJSON object for the Organisation boundary of type 'FeatureCollection', 'Feature' or 'GeometryCollection' in the WGS84 datum.
area	number	No	The area of the Organisation in hectares.
latitude	number	No	The latitude of the Organisation (-90 to 90).
longitude	number	No	The longitude of the Organisation (-180 to 180).
streetAddress	string	No	The street address.
city	string	No	The city or town.
region	Term	No	The most specific geographical region from the Glossary. This field has additional validation rules when set: the `region.termType` must have one of the following values: `region`.
country	Term	Yes	The country from the Glossary. This field has additional validation rules when set: the `country.termType` must have one of the following values: `region`.
postOfficeBoxNumber	string	No	The post office box number.
postalCode	string	No	The postal code.
website	iri	No	A link to a website describing the Organisation.
glnNumber	string	No	The Global Location Number.
startDate	string	No	The start date of the Organisation in ISO 8601 format (YYYY-MM-DD, YYYY-MM, or YYYY).
endDate	string	No	The end date of the Organisation in ISO 8601 format (YYYY-MM-DD, YYYY-MM, or YYYY).
infrastructure	List[Infrastructure]	No	The Infrastructure on the Site. infrastructure cannot be duplicated. The following fields determine whether a Infrastructure is unique: `term.@id`
dataPrivate	boolean	Yes	If these data are private. Private means that HESTIA administrators can access these data and you can grant access to other platform users, but these data will not be made available to any other users of the platform or distributed to third parties.

Internal Properties

The following properties are automatically set when data are uploaded to the HESTIA platform. If they are included in a file which is uploaded, they will be overwritten.

Field	Type	Definition
@context		The location of the JSON-LD context file.
@id		The unique ID assigned to the Node by HESTIA.
@type		Organisation
boundaryArea	number	The area in km2 of the boundary. This field is automatically calculated when boundary is provided.
originalId	string	The identifier for these data in the source database.
uploadBy	Actor	The user who uploaded these data.
schemaVersion	string	The version of the schema when these data were created.
createdAt	date	Date created on HESTIA in ISO 8601 format (YYYY-MM-DD).
updatedAt	date	Last update date on HESTIA in ISO 8601 format (YYYY-MM-DD).

Example 1

JSON-LD
CSV
CSV (Compacted)

[object Object]

{
  "@context": "https://DOMAIN/schema/Organisation.jsonld",
  "@id": "orhaa1",
  "@type": "Organisation",
  "name": "La Ferme du Grand Roc",
  "latitude": 49.16472,
  "longitude": 6.901544,
  "city": "Œting",
  "region": {
    "@id": "GADM-FRA.6.9_1",
    "@type": "Term",
    "name": "Moselle",
    "termType": "region"
  },
  "country": {
    "@id": "GADM-FRA",
    "@type": "Term",
    "name": "France",
    "termType": "region"
  },
  "startDate": "1989-06-01",
  "uploadBy": {
    "@id": "actor-577",
    "@type": "Actor",
    "name": "J. Poore, University of Oxford"
  },
  "dataPrivate": false
}