Please enable JavaScript to view this site.

Made in EU
Localazy Forums

Navigation: Catalog: Localazy > Schemas > Schema: Localazy > Tables

Projects: Localazy Projects

Catalog: Localazy

Schema: Localazy

Primary Keys: id

Label: Projects

Documentation:

Projects.

Retrieve: true

Insert: true

Update: false

Delete: false

Table Columns

The columns of the table Projects are shown below. Each column has an SQL data type. A new non-null value must be provided for every required column at all times during insert.

Name

Data Type

Label

Required

Documentation

description

varchar2

 

Project description.

id

varchar2

ID

ID.

image

varchar2

 

Full URL to the project image or empty string if there is no image available.

name

varchar2

Name

Project name.

organization_additionalMt

char

 

 

organization_availableKeys

int32

 

 

organization_connectedApps

char

 

 

organization_figma

char

 

 

organization_formatConversions

char

 

 

organization_mtPretranslate

char

 

 

organization_releaseTags

char

 

 

organization_screenshots

char

 

 

organization_screenshotsForFigma

char

 

 

organization_usedKeys

int32

 

 

organization_webhooks

char

 

 

orgId

varchar2

 

dentifier of the organization the project belongs to.

role

varchar2

 

Role of the current user accessing API (based on the token); one of none, translator, trusted_translator, reviewer, manager, owner and developer.

slug

varchar2

 

Project slug. Can be used instead of id in requests where projectId is required.

sourceLanguage

int32

 

he identifier of the source language of the project.

tone

varchar2

 

Project tone; one of not_specified, formal and informal.

type

varchar2

Type

Project type; one of public, private and restricted.

url

varchar2

 

Full URL to the project on Localazy.

 

X

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

  • Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
  • Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
  • Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
  • Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
  • Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
  • Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
  • Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
  • Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.

  
Disclaimer