Home   ·   Index   ·   Search

Naming conventions


STP naming conventions for memoQ projects and resources
STP uses a strict set of rules for naming projects, resources, and the metadata properties of projects and resources.
These conventions apply to all resources used in CAT tools by STP where we can affect them, which at STP usually means memoQ.

Working with resources

You may find that there are multiple resources (mainly TMs) attached to your memoQ projects. This is a conscious decision – instead of dumping all TM data into big client TMs, we are trying to separate the data based on the metadata, to make it more traceable, to avoid cluttering TMs with noise, and to make it easier to attach or unattach individual resources from projects where they don’t belong. In some projects, you may get loads of TM matches in Translation results or in concordance. This may cause you some clutter and it is good to be aware of your options:
  • Filter TM hits. If you find that you are getting too many hits from the TMs attached to the project, you can filter the results. See Translation results for detailed instructions.
  • Remove TMs. If you find that the hits from an EC or DT TM for a particular project doesn’t serve you any purpose, you can remove them from the Translation Memories pane. Always inform the PM if you do this.
  • Penalize TMs. You can ask your PM to add a penalty to a particular TM if you find that the leverage is “too high” compared to the content.
  • Give TMs correct priority. Unfortunately there is still no way to set a priority for different TMs in memoQ, so that a particular TM takes precedence in Concordance or Translation results. We have asked Kilgray to implement this.
    • Your project TM will contain the translations you created for this project only, so these you can trust.
    • An external TM, maintained or temporary, can be reliable or unreliable. Check your PM instructions or ask the PM directly.
    • EC TMs should only contain our own translations and are therefore “reliable”, but may not have the correct terminology for your particular project.
    • DT TMs should also only contain our own translations, but do note that the content of these come from different projects done for different clients and can therefore be very mixed and not as reliable as any EC TM content. DT TMs are meant to be a general repository of reference and to provide some assistance in for example terminology research.
  • Make sure to always keep track of what TM a match comes from. Check the status window underneath the Translation results window, where the name of the TM providing a particular match will be written.

Cheat sheet - most important memoQ conventions

Here is a summary of the most common project and resource conventions you will encounter when working in memoQ for STP.
All the resource names and metadata are typical examples. STP staff can each resource to get a full description of the specific naming convention.

Notes
Metadata
Project Convention Project Client Domain Subject Use
memoQ project STP00123456 STP00123456 001234.012345_end-client 001_domain 001_text type
  • Name and metadata of a regular project
  • Metadata picked up from Nexus, our project management system
Metadata
Resource Convention Project Client Domain Subject Use
Project TM/TB STP00123456_eng_swe STP00123456 001234.012345_end-client 001_domain 001_text type
  • Project TM or TB used as the target for new segments or terms during translation
  • Used in all projects
  • Empty at project start
  • Name and metadata identical to the project
Client project TM/TB X_STP00123456_eng_swe STP00123456 001234.012345_end-client 001_domain 001_text type
  • TM or TB used to import resources from the client, to be used for the duration of the project only
  • Name identical to the project but preceded by X_
  • Metadata identical to the project

This content generally takes precedence in any project.
But the reliability of the content can range greatly so check your instructions and ask the PM if unclear.

End-client TM/TB EC_eng_swe_end-client n/a 001234.012345_end-client n/a n/a
  • TM or TB maintained by STP with data for a particular client
  • Identified by the EC prefix
  • Only the Client metadata field is used, the other will be marked "n/a"

This resource will contain all content that STP has harvested when working for a particular client.
The content is deemed reliable but client resources take precedence, if available.

External end-client TM/TB X_EC_eng_swe_end-client n/a 001234.012345_end-client n/a n/a
  • TM or TB sent by a particular client and maintained by STP
  • Identified by the X_EC prefix
  • Only the Client metadata field is used, the other will be marked "n/a"

This resource will contain all content directly from an STP client that we have been asked to maintain and reuse for their projects.
Most commonly used for recurrent client glossaries.
As with client project resources, they take precedence over any STP resource.

Domain-specific TM/TB DT_eng_swe_domain n/a n/a 001_domain n/a
  • TM or TB maintained by STP with data for a particular domain
  • Identified by the DT prefix
  • Only the Domain metadata field is used, the other will be marked "n/a"
  • DT TMs are penalized by 10% to avoid them taking precedence over client resources

This resource will contain all content that STP has harvested from projects within a particular domain.
DT TMs can be large and heavy, and may cause more clutter than help for projects with many resources.
DT TBs however, are useful terminology deposits - but remember that client resources will always take precedence.


Further reading for STP staff

Naming conventions - in-depth

Metadata fields - in-depth

PM Data Management

Current list of DT resources

Other conventions