# Terms and Interface ## Texts for the Concepts topic: ### Object A collection of related data in a cloud application or database. Skyvia represents objects from cloud apps and databases similarly, as tables with data. ### Table When we describe database-specific topics, we can use database-specific term "table" instead of object. ### Skyvia Object We call items that user creates and uses in Skyvia products Skyvia objects. This term unites agents, connections, integration packages, backups, user queries, connect endpoints (, automations). ### Column/Field (depending on what we will decide to use) A set of data values of a particular type in an object, one value per each record. ### Record A record is a data item in an object (table). It is a set of values of specific types, corresponding to object columns. ### Parameter #### Package (Integration) Parameters _(We currently still use the term "package", but maybe it will be replaced with "integration" in future)_ Package parameters are used to store values between package runs. Replication and Synchronization packages have pre-determined parameters. Data Flow and Control Flow allow adding an arbitrary set of parameters to them. #### Action Parameters Most actions have a set of parameters that must be mapped to input data or package parameters or variables. These parameters are a variable set of action settings, depending on other, fixed action settings. For example, in the Insert action, parameters correspond to target table columns, so you determine how they are mapped to input columns. In the Execute Command action, parameters are just SQL parameters that you use in your command. #### SQL Parameters SQL parameters are variables that you can use in SQL statements. They allow executing the same SQL statement multiple times with different data. ------- SQL parameters are used for exchanging data between Skyvia and a data source. They are used when you enter an SQL statement with parameters, for example, in Execute Command action or in Skyvia Query Google Sheets Add-on or Excel Add-in. ### Scope In data flows, data moves from source to target and are processed by other components on their way. The processing by components means that each data flow component can add, update, delete data columns on their way from source to a final destination. These data can also contain nested objects - columns that store objects with multiple properties or even array of objects. Nested object columns can in turn contain other nested objects or arrays and so on. We use the term "scope" to define, with which set of data the #current component works. It can work with the top-level records that it receives from the input, or if input records contain nested objects or arrays of nested objects, it can work only with the records of these objects or these arrays, or even with objects on deeper layer of nesting. ### Connector An interface to connect to a data source (database, cloud app, storage service). We can also use this term for a data source itself. ### Action Action is an operation performed in order to obtain or store data in a data source. Each data source has a list of available actions, which can be used in different Skyvia components. ### Entity Entities are instances of entity types. Entity types are named structured types, having a key (a property or several properties that uniquely identify entities). Entity types have named properties and navigation properties, which represent relationships between entities. Entity sets are named collections of entities. This term is used in Connect. It is a term, associated with OData protocol. ## Thoughts, Ideas ### Object In Skyvia documentation we use two meanings of the word "Objects". 1) Cloud objects are like tables with data in cloud data sources that Skyvia works with. In our documentation, the word _object_ usually means such a cloud object. Sometimes we also use the word _table_ as a synonim. For database tables, we often use the native database term _table_. 2) We also call everything that user can create on Skyvia as _Skyvia objects_. This term unites connections, integration packages, backups, user queries, connect endpoints, etc. ----------- Skyvia objects in docs: User interface basics, collaboration, etc. Word "Object" is used a lot in the interface, in either of two meanings. We have Objects page, All Objects filter for Skyvia objects and a number of interface labels for objects - tables and cloud objects. Tables is used in the Replication package settings - Object vs object I prefer lowercase, because it's a general term, used a lot. - When do we use table? Mostly in replication, about database tables, but we also use it often as a synonym to object. - Why don't we use only table? Cloud data sources tend more to use the term "object", while databases use "table". Specifically when we are talking about databases, it's better to use their terms. - Why don't we use only object? AlexH told us on the meeting that we cannot avoid using the word table completely, especially when talking about the databases. ![](https://i.imgur.com/DPkP7Po.png) ### Table We often use the word "table" as a synonym for an object. A collection of related data with similar structure, which consists of tables and rows (records). We represent cloud objects similarly to database tables, so we use these terms as synonyms. ### Column, Field, Property Column, field, property must be reviewed. We use field heavily, also column as a synonym in doc. In the interface, there are properties and columns, but no fields. Columns - in lookup mapping, properties in the mapping editor. We use fields mostly as a synonym to a column. Maybe we should use property instead. Here is where we use these terms in app: #### Column: - Lookup Mapping - Column mapping - External ID mapping - Export task editor - Output Columns tab - Backup - task editor - Import task - CSV - Source Definition tab - Target Definition tab - Use External ID hint - Replication task editor - Synchronization Task Editor - Columns Definition tab - Replication Task editor for Redshift - Columns tab, etc. - Data Flow - Lookup action - Result Columns #### Field: - Query Builder - Result Fields, Sort Fields - Use Custom Fields - in BigCommerce, Pipedrive, Zendesk - Backup - comparison mode - Select Fields for updated records - _\*CustomFields_ objects in different connectors, for example, in Asana #### Property: - Mapping editor We mostly use column/field interchangeably, as synonyms. Property is used only in Mapping editor as a "field" of input data. I think, it would be easy to switch to the term "column" everywhere when we talk about columns, and maybe use field when we need to talk about "table cell", not a column. In the latter meaning, it is used in Backup and corresponding object names (the last two items in the list). ### Value I don't think that we need to explain this term. We don't add any specific meaning to it. ### Source ### Target Should we even explain these? ### Connector An interface to connect to a data source (database, cloud app, storage service). We can also use this term for a data source itself. It's a general term, widely used to mean this. Note that for NetSuite we have 2 connectors now, so it's not 100% a synonym to a data source, but we still can use it for a data source itself. ___ ## UI elements ![](https://i.imgur.com/VDgRa6L.png) ___ https://docs.hevodata.com/getting-started/familiarizing-with-the-ui/ ![](https://i.imgur.com/BBx9T88.png) ![](https://i.imgur.com/l0YH8vO.png) ![](https://i.imgur.com/2k2gKPJ.png) ![](https://i.imgur.com/FDXVMJt.png) ## Page A full page, usually with distinct URL. Like Select Connector page, package details page. ## Window Sometimes we call such things as Parameters dialog, task editor, etc. - windows. ## Pane Visually distinct area with a group of controls, for which we don't have another word. ## Sidebar Sometimes we call a window (that can be closed) on the side of the page - sidebar, like in data flow. ## Tab ## Panel ## Menu ## Bar ## Dashboard ## Account ## Profile ## Workspace ##