DatAscend terminology

A reference for key terms and concepts used throughout the DatAscend platform.

Aggregation: Aggregation is the process of summarizing or combining data to obtain more meaningful information. In DatAscend, aggregation is commonly used in reports to calculate totals, averages, counts, or other metrics from an entity's records. For example, a sales report could use aggregation to display total sales by region or the average sales per product. Aggregation allows users to obtain valuable insights from large data sets, facilitating informed decision-making within the DatAscend application.
API: An Application Programming Interface — a set of software functionalities that allows different software applications to communicate with each other. DatAscend offers a RESTful API to interact with platform data and configuration programmatically. Consult your administrator for details on how to access and use the DatAscend API.
boolean: A boolean value is a data type that can have only two possible values: true or false. In DatAscend, boolean fields are commonly used to represent states or conditions that can be active or inactive, accepted or rejected, among others. For example, a 'Users' entity could have a boolean field called 'active' to indicate whether a user is active or not. Boolean fields are useful for filtering and sorting data according to certain logical conditions within the DatAscend application.
breadcrumb: A breadcrumb is a navigation element that displays the path or hierarchy of pages or entities within an application. In DatAscend, breadcrumbs are used to help users understand where they are within the application structure and to facilitate backward navigation through related pages or entities. For example, if a user is viewing a specific record in an entity, the breadcrumb could display something like 'Customers > Customer XYZ > Details', indicating that the user is on the details page of customer XYZ within the Customers entity. Breadcrumbs improve usability and user experience by providing context and clear navigation options within your DatAscend application.
breadcrumbs: A breadcrumb is a navigation element that displays the path or hierarchy of pages or entities within an application. In DatAscend, breadcrumbs are used to help users understand where they are within the application structure and to facilitate backward navigation through related pages or entities. For example, if a user is viewing a specific record in an entity, the breadcrumb could display something like 'Customers > Customer XYZ > Details', indicating that the user is on the details page of customer XYZ within the Customers entity. Breadcrumbs improve usability and user experience by providing context and clear navigation options within your DatAscend application.
column headers: Column headers are the titles or labels displayed at the top of each column in a DatAscend table or report (also in data files for import). These headers indicate the type of information found in each column, facilitating comprehension and data analysis by users. For example, in a customer report, column headers could include 'Name', 'Email', 'Date of Birth', and 'Active'. Column headers are essential for organizing and presenting data clearly and accessibly within your DatAscend application.
columns: Columns, also known as fields or attributes, are defined in a DatAscend entity and represent the different properties or characteristics of records. For example, in a 'Customers' entity, columns could include 'name', 'email', 'date of birth', and 'active'. Columns define the structure of data stored in an entity and determine what type of information can be captured and managed for each record within your DatAscend application.
Dashboard: DatAscend's main summary page that displays key information, shortcuts, and widgets configured by Role. The Dashboard provides users with a personalized view of the most relevant information for their role and daily tasks. It can include reports, charts, task lists, quick links to entities or menus, and other components that facilitate access to important data and functionalities. Dashboards are configured in Studio and can be different for each role, ensuring that each user has an experience tailored to their needs within the DatAscend application.
database: A database is an organized system for storing, managing, and retrieving data efficiently. DatAscend can integrate with different database management systems (DBMS) such as PostgreSQL, MySQL, or SQL Server, depending on user needs and preferences. Databases allow users to access large volumes of information quickly and securely, facilitating data management and analysis within your DatAscend application.
date: A date field is a data type that stores information about a specific date, without including the time. In DatAscend, date fields are used to record events or important milestones that only require date information, such as birth dates, expiration dates, or registration dates. For example, a 'Customers' entity could have a date field called 'birth_date' to store each customer's date of birth. Date fields are useful for performing analyses based on specific periods, generating date-based reports, and automating time-related processes within your DatAscend application.
date and time: Date and time refers to a data type that stores information about specific moments in time and strictly contains both the date and the time. In DatAscend, you can use date and time fields in your entities to record events, schedule actions, or perform time-based analyses. For example, an 'Orders' entity could have a date and time field called 'creation_date' to record when each order was created. Date and time fields are essential for managing data temporality, allowing users to perform tracking, generate reports based on specific periods, and automate time-based processes within your DatAscend application.
Domain: A logical grouping or namespace for organizing Entities, Menus, and other resources within a DatAscend application. For example, you can have a 'Sales' domain containing entities such as 'Customers', 'Products', and 'Orders', and another 'Human Resources' domain with entities such as 'Employees' and 'Departments'. Domains help structure your application coherently, facilitating navigation and management of related resources. Domain use cases: Segregating information by country; domains can represent cattle farms of the same company, each with its own animal, employee, etc. information. Segregating information by departments or functional areas within a company, such as Sales, Human Resources, Finance, etc., to better organize related data and functionalities.
Entity: The main data structure in DatAscend, equivalent to a database table or collection. Entities contain records and can have properties, relationships, permissions, and configurations. An entity represents a concept or data type in your application, such as 'User', 'Product', or 'Order'. Entities are defined and managed through Studio, where you can configure their fields, relationships, and behaviors.
filter criteria: Filter criteria are conditions applied to entity data to display only records that meet certain requirements. In DatAscend, you can configure filter criteria in reports, dashboards, or entity views to limit the information displayed to users. For example, a filter criterion could be 'Status = Active' to show only active customer records, or 'Creation Date > 01/01/2024' to show only records created after January 1, 2024. Filter criteria are essential for customizing data visualization and ensuring that users see only the information relevant to their tasks and responsibilities within the DatAscend application.
foreign key: A foreign key is a field in an entity used to establish a relationship with another entity in DatAscend. For example, if you have an 'Orders' entity and a 'Customers' entity, the 'Orders' entity could have a foreign key field called 'customer_id' that references the customer's ID in the 'Customers' entity. Foreign keys allow linking records from different entities, facilitating the organization and access to related data. In DatAscend, relationships between entities are configured using foreign keys, which allows creating complex data structures and maintaining referential integrity within your application.
Import: The process of loading external data (e.g., from CSV or external sources) into the records of an Entity within DatAscend.
inner join: An inner join is a data combination operation in DatAscend that returns only records that have matches in both related entities. For example, if you have an 'Orders' entity and a 'Customers' entity, an inner join between these entities would return only orders that are associated with existing customers, excluding any order that does not have a linked customer. Inner joins are useful for filtering data and obtaining relevant information based on specific relationships within your DatAscend application.
joins: Joins are a technique used to combine data from two or more entities in DatAscend, based on a common relationship between them. For example, if you have an 'Orders' entity and a 'Customers' entity, you can perform a join to display customer information alongside each order in a report. Joins allow users to access related data efficiently, without the need to duplicate information across multiple entities. This is especially useful for creating complex reports that require data from multiple entities, as it allows combining information dynamically and flexibly within the DatAscend application.
left join: A left join is a data combination operation in DatAscend that returns all records from the left entity (the first entity mentioned) and the matching records from the right entity (the second entity mentioned). If there is no match in the right entity, the fields corresponding to that entity will be filled with null values. For example, if you have an 'Orders' entity as the left entity and a 'Customers' entity as the right entity, a left join would return all orders, including those that do not have an associated customer, showing null values for the customer fields in those cases. Left joins are useful for obtaining a complete view of an entity's data while including related details when available within your DatAscend application.
many to many: A many-to-many relationship in DatAscend is a type of association between two entities where multiple records of one entity can be linked to multiple records of the other entity. For example, if you have a 'Students' entity and a 'Courses' entity, a many-to-many relationship could link each student with several courses they are enrolled in, and each course could have several enrolled students. This type of relationship is useful for modeling situations where there is a flexible association between two data sets within your DatAscend application, allowing records to relate dynamically based on business needs.
many to one: A many-to-one relationship in DatAscend is a type of association between two entities where multiple records of one entity can be linked to a single record of the other entity. For example, if you have an 'Orders' entity and a 'Customers' entity, a many-to-one relationship could link multiple orders with a single customer, while each customer could have several associated orders. This type of relationship is common for modeling situations where several related objects point to a main object within your DatAscend application.
Menu: In DatAscend, a menu is a navigation element displayed in the sidebar or header of the application that links users to Entities, reports, or other views. Menus are configured in Studio and can be organized in domains to facilitate navigation. For example, a menu called 'Customers' could link to the customer entity, while a 'Sales Reports' menu could link to a report showing sales by region. Menus are essential for guiding users through the application and providing quick access to relevant functionalities and data based on their role and needs. Menus can be visible to all users or restricted to certain roles, allowing customization of the navigation experience based on the needs of each group of users within the DatAscend application.
Module: A functional area of the DatAscend platform (e.g., Users, Permissions, Workflows) that groups related functionalities and pages. Access to modules is controlled through roles and permissions, allowing customization of the user experience based on their needs and responsibilities within the application. For example, the 'Users' module could include pages for managing users, roles, and permissions, while the 'Workflows' module could contain tools for designing and managing the application's automated processes. Modules help organize the platform's functionalities logically, facilitating navigation and access to the tools needed to administer and use your DatAscend application effectively.
Multi-level relationships: Multi-level relationships in DatAscend refer to the ability to establish associations between entities that extend through several levels of relationship. For example, if you have a 'Customers' entity that is related to an 'Orders' entity, and the 'Orders' entity is related to a 'Products' entity, then the relationships between 'Customers' and 'Products' would be considered multi-level relationships. This type of relationship allows modeling complex and hierarchical data structures within your DatAscend application, facilitating access to related data through multiple levels of association.
MySql: MySQL is an open-source relational database management system widely used in web applications. DatAscend can integrate with MySQL to store and manage entity data, records, and other application-related information. MySQL offers high performance and easy configuration, making it a popular choice for developing applications that require efficient data storage.
Nested relationships: Nested relationships in DatAscend refer to the ability to establish associations between entities that are themselves related to other entities. For example, if you have a 'Customers' entity that is related to an 'Orders' entity, and the 'Orders' entity is related to a 'Products' entity, then the relationships between 'Customers' and 'Products' would be considered nested relationships. This type of relationship allows modeling complex and hierarchical data structures within your DatAscend application, facilitating access to related data through multiple levels of association.
number: A number is a data type that represents numeric values, whether integers or decimals. In DatAscend, numeric fields are used to store quantities, prices, scores, or other quantitative data. For example, a 'Products' entity could have a numeric field called 'price' to store the price of each product. Numeric fields are fundamental for performing calculations, analyses, and generating reports based on quantitative data within your DatAscend application.
one to many: A one-to-many relationship in DatAscend is a type of association between two entities where one record of one entity can be linked to multiple records of the other entity, but each record of the second entity can only be linked to one record of the first entity. For example, if you have a 'Customers' entity and an 'Orders' entity, a one-to-many relationship could link each customer with multiple orders they have placed, while each order would only be linked to one specific customer. This type of relationship is common for modeling situations where a main object has several related instances within your DatAscend application.
one to one: A one-to-one relationship in DatAscend is a type of association between two entities where each record of one entity is linked to a single record of the other entity, and vice versa. For example, if you have a 'Users' entity and a 'Profiles' entity, a one-to-one relationship could link each user with a unique profile that contains additional information about that user. This type of relationship is useful for organizing data that is closely related but that you want to keep in separate entities for reasons of clarity or data structure within your DatAscend application.
owner: The owner of a record in DatAscend is the user or entity responsible for that specific record. The owner may have certain permissions or responsibilities associated with the record, such as the ability to edit, share, or delete it. In some cases, the owner can also be used to control access to records, allowing only certain users to view or interact with records that belong to them. Owner management is an important part of data administration and security within your DatAscend application.
Permission: An access control rule that determines what operations (view, create, edit, delete) a Role can perform on an Entity or functionality.
PostgreSQL: PostgreSQL is an open-source relational database management system known for its robustness, scalability, and support for advanced features. DatAscend can integrate with PostgreSQL to store and manage entity data, records, and other application-related information. PostgreSQL is a popular choice for applications that require high performance, data integrity, and support for complex queries.
records: Records are individual entries in DatAscend that contain information about a specific object or entity. In DatAscend, records are stored in entities and represent concrete instances of those entities. For example, a record in the 'Customers' entity could represent a specific customer with their personal and contact information. Records are the basic unit of data storage and retrieval within your DatAscend application.
Relationships: A link between two Entities that represents a data association, similar to a foreign key in a relational database. Relationships allow connecting records from different entities, facilitating the organization and access to related data. For example, an 'Orders' entity could have a relationship with the 'Customers' entity to link each order with the customer who placed it. Relationships are configured in Studio and can be of various types, such as one-to-one, one-to-many, or many-to-many, depending on how the information needs to be structured in your DatAscend application.
Report: A visualization or summary of structured data generated from one or more DatAscend Entities. It is used to display aggregated or filtered information. A report can include a data table, charts, key metrics, or other visual elements to help users understand and analyze information. Reports are configured in Studio and can be accessible through menus or dashboards, providing users with valuable insights based on the data stored in the application's entities.
right join: A right join is a data combination operation in DatAscend that returns all records from the right entity (the second entity mentioned) and the matching records from the left entity (the first entity mentioned). If there is no match in the left entity, the fields corresponding to that entity will be filled with null values. For example, if you have an 'Orders' entity as the left entity and a 'Customers' entity as the right entity, a right join would return all customers, including those who do not have associated orders, showing null values for the order fields in those cases. Right joins are useful for obtaining a complete view of a related entity's data while including related details when available within your DatAscend application.
Rol: A set of permissions assigned to users to control what actions they can perform and what data they can access in the system. In DatAscend, roles are configured in Studio and assigned to users to define their access level and the operations they can perform on entities and other application functionalities. A role can have specific permissions to view, create, edit, or delete records of an entity, as well as access to specific menus and reports. They are fundamental elements for implementing security and access control in your DatAscend application.
Section: A section is a visual container used to organize and group elements of a DatAscend report. Sections help structure information clearly and coherently, facilitating navigation and data comprehension by users.
string: A text string is a data type that stores sequences of characters, such as words, phrases, or any combination of letters, numbers, and symbols. In DatAscend, text string fields are used to store descriptive information, such as names, addresses, descriptions, or any other type of alphanumeric data. For example, a 'Customers' entity could have a text string field called 'name' to store the customer's name. Text string fields are essential for capturing detailed and descriptive information within your DatAscend application.
Studio: DatAscend's visual administration interface where administrators can create and manage Entities, configure Menus, and define the application structure. In addition to entity management, Studio allows you to configure roles and permissions, design workflows, manage translations, and customize the user experience. It is the central tool for building and maintaining your DatAscend application without the need to write code.
Translations: A localization-specific label or value for Entity properties and relationships, enabling multilingual support in the application. DatAscend allows configuring translations for entities, properties, relationships, and other application elements through Studio. This means you can provide labels and values in different languages, facilitating the use of the application by users who speak different languages. Translations can be configured for each property and relationship, ensuring that the user interface is consistent and understandable for all users, regardless of their preferred language. This is especially useful in global applications or in environments with multilingual users, as it improves accessibility and user experience by allowing them to interact with the application in their native language.
Variable: A value that can change during the execution of an application. In DatAscend, variables can be used to store temporary data or to pass information between different parts of the application. For example, a variable could store a user's name or the ID of a specific record. Variables are useful for customizing the user experience, performing dynamic calculations, or controlling application flow based on user actions or available data. They can be used in workflows, reports, or anywhere a value that may change during interaction with the DatAscend application is needed.
Workflow: An automated sequence of steps triggered by events or conditions in the system, used to define business logic and processes. In DatAscend, workflows are configured in Studio and can include actions such as sending notifications, updating records, executing custom scripts, or integrating with external systems. Workflows allow automating repetitive tasks, ensuring data consistency, and improving operational efficiency in your application.