Project name mapping helps BeLazy decide how to name your projects in your BMS (for example, “Orders” in Plunet, “Projects” in XTRF/Protemos).
Each project name is built with information (metadata) that comes from the source system that BeLazy can access, as well as text that you want to include. For example, you might want to use:
The original project name,
The end customer’s name,
A task or project ID (from the origin system)
BeLazy suggests a default naming format, but you can easily change it:
To remove a part, click the small X next to it.
You’ll see a preview below showing how the name will look.
A warning may appear if something could cause confusion when using bundling (you can ignore this if bundling isn’t used).
To customize your project names:
Click Select a property to add to the project name to include more data.
To add plain text, choose Enter text and type what you want (for example, spaces or dashes to separate sections).
If you make a mistake, just delete sections until it looks right.
Tip: Add a short tag like [BL] at the beginning/end of automatically created projects. This helps your team recognize projects created by BeLazy and avoid changing them manually.
When using bundling, be careful not to include target languages in the project name if multiple languages are grouped into one project. For example, don’t name a bundled project “French” if it also includes Italian. A warning will appear to remind you. It’s just a suggestion, not an error, but it’s worth reviewing.
Finally, there are a few special fields you can adjust:
Dates: You can display dates as short dates, months, weeks, or years. This is useful if you group projects by time period (daily, weekly, monthly, year).
Name (regex): This advanced option lets you modify names using patterns. For example, it helps when bundling multiple jobs from systems like XTRF or Plunet that use slightly different identifiers for translation and review tasks.