BioCollect Schema - AtlasOfLivingAustralia/ecodata GitHub Wiki

The illustration below is a logical view of the subset of the ecodata schema that is used by the BioCollect application. Entities exclusive to BioCollect are not illustrated here.

Entity	Description
Project	BioCollect Projects can be works based or survey based.
Site	Sites are usually related to a single project but can be associated with multiple. Activities take place at a site.
Activity	An activity represents work/events/surveys undertaken at a site during a period of time
Output	Outputs record data about activities
OutputMetaData	A JSON file that describes the data in an Output type and how it should be displayed in a form
ActivityMetaData	A JSON file that describes an Activity type, which Outputs are required and whether they are optional or mandatory.
ProjectActivity	A ProjectActivity (or survey definition) describes an activity that will be carried out multiple times during a project lifetime. For example, a survey. It provides a template for the creation of new Activities with pre-defined type, sites and species.
Organisation	Organisations relate to a collection of project. The relationship can be as a grantee, service provider or sponsor.
Hub	A Hub defines a view of a collection of projects. Hubs allow some theming and custom pages to be applied to BioCollect via a URL path that identifies the Hub.
Document	Documents are a mechanism to allow files to be attached to ecodata entities. They can be informational, photo's or logos.
UserPermission	The UserPermission entity is the mechanism ecodata uses to implement an access control list (ACL) for other entities. Most permissions relate to Projects but Program and Organisations also have separate permissions
Record	Records are optionally generated from Activity and Output data. They are the mechanism via which ALA occurance data is produced for import into the ALA BioCache.