MoveApps Attribute Dictionary

The following are definitions of terms for properties used in describing MoveApps workflows published in the Movebank Data Repository. The properties are divided into different collections and describe the workflow itself, administrative and technical information about the apps used within the workflow, and the configuration of the apps in all workflow instances that are part of the publication. This set of information is called metadata as it is additional information about other data. It is useful in helping to understand the workflows and enable reusability.

The schema follows a hierarchical structure. This means that certain properties serve as container elements to group underlying properties, which in turn contain the descriptive information itself.

Each property is defined by a name, a definition, an example, how often it can be repeated, whether it is mandatory, a unit, the entity described, and the way the information is submitted to the metadata (automatically or submitted by the user).

  • Name: The name of the metadata property. This describes how the property is labelled in the metadata file.
  • Definition: A description of the information that is meant to be stored in the metadata property. If the property is contained within a container element, this is also defined.
  • Example: An example of how the metadata property can be filled out. Exception: Container elements do not have contents themselves but are used to structure other metadata properties. Therefore, container metadata elements do not include examples.
  • Occurrence: • Occurrence: This describes how many times a metadata property can be repeated. If a property does for example have an occurrence of ‘1’ it can only be available one time. An occurence of ‚n‘ means, that a property can exist an indefinite amount of times. An ‘1-n’ occuence means, that a property can exist an indefinite amount of times but at least one time.
  • Obligation: The obligation describes whether or not a property is required for a metadata record. This information is connected to the occurrence. A metadata property with an occurrence of ‘1’ will in turn also be mandatory. The obligation and occurrence of a property are described relative to the property above it in the hierarchy. This means a property with a mandatory obligation will only be mandatory, if the container above it, which might be optional itself, is available.
  • Unit: The unit describes what type of information is stored in a metadata property. Possible Units are:
      Container: A container metadata property is used as a structuring element. It doesn’t contain any information itself but is an empty element. All respective subproperties are structured a layer below it and can be container elements themselves.
      Controlled Vocabulary: If the content of a property comes from a finite list of possible options, the unit is marked as ‘controlled vocabulary’.
      ID: If the information is a unique identifier for a resource, the Unit is marked as ‘ID’.
      String: If a metadata property contains text or other more free-form information, it is marked as ‘string’.
      URI: If a metadata property contains a link to another resource, the unit of this property is marked as ‘URI’ (for ‘Uniform Resource Identifier’).
      xsd:date: o xsd:date: For date information on workflows/apps the xsd:date type, used in the XML schema context, is used.
  • Described entity: This describes what kind of entity is described with each specific metadata property. Available options are workflow and app.
  • Submission: The submission describes who entered the information into the system during submission. If the user itself entered it via a form it is marked as ‘user’. If the metadata is generated automatically or by a repository curator, it is marked as ‘system’.
  • Workflow properties

    Workflow administrative properties



































    Workflow instance and configuration properties











    App properties

    App administrative properties







































    App technical properties












    App programming language specific properties










    Submission