Spacialist Documentation
Home
User
Developer
GitHub
Home
User
Developer
GitHub
  • User

    • Overview
    • Getting Started
    • Dictionary (Thesaurus)
    • User And Role Management
    • Data Model
      • Entity Type
      • Attribute
      • Attribute Types
    • Entity
    • Collaboration
    • Bibliography
    • Spatial Data
    • Data Importer
    • Data Analysis Tool
  • Developer

    • Developer
    • Environment
    • Coding Structure
    • Plugin
    • Classes

      • Entity Type
    • Commands

      • Export Entity Types (Data Model)
      • Refresh Testing
    • Framework

      • Authentication
    • Common Issues

Data Model

The program does not yet know, how your data is structured and gives you complete freedom on how to structure your data. While also restricting the data to an appropriate data type. This structure is defined in the Data Model.

The Data Model contains all the blueprints (in Spacialist: Entity Types) for the data you want to collect. Your actual data is then collected using Entitites, which is an object created from one of those "blueprints". And each Entity Type is a composition of different Attributes, which are defined by an Attrbiute Type and a label (as defined in the Thesaurex). Those attributes can then be used on multiple different entities and make it possible to have comparable data independent of Entity Type.

For Beginners, the concept is often a bit confusing and hard to understand, we'll illustrate the described relations using the following graphics:

Graphic illustrating the data model relations.

Designing an Entity Type

When creating an Entity Type you should should sketch out, what values are connected to your Entities and which Attribute Types do reflect those values most appropriately, e.g. is it a text, an item from a set of values or a number. If it's a number, is a Unit connected to that value, is it an integer or is it an floating point value? Take some time to think and design a good model, as it's hard to change it later in the process.

When you have a proper prototype of your Entity, the easiest way is to start is to go into the ThesauRex and create all required attribute labels and items you want to have as a Dropdown*.

If your entity used dropdowns, please check the Dropdown Lists section first.

Dropdown Lists

Dropdowns provide a way to select data from a predefined list of options which prevents errors and keeps the data consitent. There are two different types of dropdowns single or multi dropdowns. When you wonder which one to use, then you must ask yourself, if there will be always a single item selected or is there in any case there will be a scenario when you need multiple values in this input:

SingleThe entity has a field "Medal", which will always be either "Gold", "Silver", "Bronze" or "None".
MultipleThe entity is a metal object which can have a mixture of materials, then you may want to add "Silver" and "Gold" on the same Entity.

ThesauRex- vs. Entity Dropdown

Spacialist provides two ways to create dropdown fields.

| Type | When |Pro | Cons | |---|---|---| | ThesauRex | More static and simple Data with a text label only. Managed inside ThesauRex. | | | Entity | More dynamic and complex data with indefinite decree of complexity. Managed as Entities directly inside Spacialist. | |

Edit this page
Last Updated: 10/15/25, 3:31 PM
Contributors: Severino
Prev
User And Role Management
Next
Entity