Page Comparison

Most of the API methods for resources, segments and related data ask for a "scope". The scope both delimits the set of data you need to access as well as the access rights to these data. For example the "job" scope gives access to segments and files for one specific job.

A scope is a JSON object with the properties described below.

Job scope

This scope delimits data to segments and files of one specific job.

Example:

{
    "type": "Job",
    "jobid": 9927,
    "jobcdyt": true
}

Project scope

This scope delimits data to segments and files of a specific project.

Example:

{
    "type": "Project",
    "projectid": 229
}

Memory/Term base scope

This scope delimits data to segments and files of resources, which are translation memories, term bases or project memories. In internal tech-speak at Wordbee, we call them "document sets".

Note: You can access segments of a project using both the "Project" and the "Resource" scope. The difference is in terms of the access rights and the kind of operations you will be allowed to perform. For example, deliverables are not accessible with the "Resource" scope (resources do not have deliverables).

Example:

{
    "type": "DocumentSet",
    "dsid": 157
}

Resource scope

This scope is specifically used in conjunction with translation memory searches. The "translation finder" tool in the translation editor permits to search memories/term bases.

The "translation finder" also exposes tools to look into these attached resources and to view details for hits (source, translation, status, etc.). For all the latter operations you would use a "Resource" scope and not a "DocumentSet" scope. The reason simply is that non-managers are usually not authorized for "DocumentSet" scopes but are usually authorized for "Resource" scopes. Whereas a "DocumentSet" scope gives advanced access to a resource including making changes, the "Resource" scope generally strongly restricts what the user can do.

Example:

{
    "type": "Resource",
    "dsid": 992,
    "psc":
        {
            "type": "Job",
            "jobid": 9927,
            "jobcdyt": true
        }
}

Global Search scope

This scope gives access to all the segments in the platform: All projects, resources, jobs.

Please note that configuration parameters influence what is accessible: Global Search can enabled/disabled, Resources can be enabled/disabled for global search access and so on. 

Example:

{
    "type": "GlobalSearch"
}

 This page lists the different statuses of a job. A status may either be represented by a numeric value or a string code.

Note that some statuses are not used with Codyt or Standard jobs.

NOTE: The status values differ from the values used with the previous API.