github
/
nocodb
mirror of https://github.com/nocodb/nocodb
1
0
Fork 0
Code Issues Releases Wiki Activity
Browse Source

Tweak terminology (#7866)

pull/7873/head
Salim B 8 months ago committed by GitHub
parent
b0c1f1e1c7
commit
953217a59f
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 11 additions and 12 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Split View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 23
      packages/noco-docs/docs/020.getting-started/030.terminologies.md

23
packages/noco-docs/docs/020.getting-started/030.terminologies.md
Unescape View File

@ -30,17 +30,16 @@ The layout below shows the main parts of NocoDB's user interface.
| Term | Description |
|-----------------:|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Base | A base is a collection of one or more tables, often related and linked to one another. Alternative term `Project` |
| Base Owner | Member who had created base. There can be only one owner for a base & ownership is non-transferable |
| Base member | Base member with specific access permissions. Alternative term `Member` `User` |
| Cell | A cell represents the space created where a column and a row intersect within a grid-like structure. It serves as the fundamental unit for storing data |
| Field | A field or column in a table is a container for values that share the same data type. Alternative term `Column` |
| Modal | In the context of user interfaces, a modal is a type of dialog or overlay that appears on top of the main content or interface and requires user interaction before the user can proceed. Modals are often used to gather user input, display alerts, or confirm actions. They typically "block" the rest of the interface until the user dismisses them, making them a focused and attention-grabbing element |
| Record | A record represents a row in a table. Alternative term `Row` |
| Table | A base is housed in tables, where data is logically arranged into rows and columns. A base can have multiple tables. Alternative term `Model` |
| Term | Description |
| Base | A base is a collection of one or more data sources that each contain one or more tables, often related and linked to one another. Alternative term: `Project` |
| Base owner | Member who created the base. There can be only one owner for a base and ownership is non-transferable. |
| Base member | Base member with specific access permissions. Alternative terms: `Member`, `User` |
| Cell | A cell represents the space created where a column and a row intersect within a grid-like structure. It serves as the fundamental unit for storing data. |
| Field | A field or column in a table is a container for values that share the same data type. Alternative term: `Column` |
| Modal | In the context of user interfaces, a modal is a type of dialog or overlay that appears on top of the main content or interface and requires user interaction before the user can proceed. Modals are often used to gather user input, display alerts, or confirm actions. They typically "block" the rest of the interface until the user dismisses them, making them a focused and attention-grabbing element. |
| Record | A record represents a row in a table. Alternative term: `Row` |
| Table | A table is a matrix where data is logically arranged into rows and columns. A base can have multiple tables. Alternative term: `Model` |
| View | A view defines how data within a table is presented and interacted with. Default view type is the grid view; other supported view types include form, gallery, and kanban views. |
| Webhook | A webhook is a mechanism that allows one system to send real-time data to another system or application. It enables automated notifications and data synchronization between different services or platforms by triggering predefined actions or events in response to specific events or updates in the source system. |
| Workspace Owner | Member who had created workspace. There can be only one owner for a workspace & ownership is non-transferable |
| Workspace member | Workspace member with specific access permissions. Alternative term `Member` `User` |
| Workspace | A workspace is a collection of one or more bases. It offers collaborative access to bases by enabling you to bring together interconnected tables, views, and various elements into a unified and organized entity |
| Workspace | A workspace is a collection of one or more bases. It offers collaborative access to bases by enabling you to bring together interconnected tables, views, and various elements into a unified and organized entity. |
| Workspace owner | Member who had created the workspace. There can be only one owner for a workspace and ownership is non-transferable. |
| Workspace member | Workspace member with specific access permissions. Alternative terms: `Member`, `User` |

Write Preview
Loading…
Cancel
Save