Project – domain – client – subject
Thread poster: Olaf Reibedanz

Olaf Reibedanz  Identity Verified
Colombia
Local time: 00:08
Member (2003)
English to German
+ ...
Jun 18, 2010

Dear colleagues,

I am trying to find a good system for naming the four fields "project", "domain", "client" and "subject". I would like to reserve one field for the name of the agency and one field for the name of the end client. But I am not sure what I should use the other two fields for. Any suggestions?

I suppose I could use the other two fields to define the general subject (such as "finance") and the specific subject (such as "investment banking"). But the problem with that system is that no text falls into one category alone. For example, how should I classify a marketing/advertising text written by an investment bank - is the subject "marketing" or "finance"? And what do I do in the case of a contract with heavy engineering terminology - is the subject "law" or "engineering"?

Thanks in advance for your advice!

Kind regards,

Olaf


Direct link Reply with quote
 

rmackay
Local time: 06:08
Metadata Jun 18, 2010

Hi Olaf

I am working on some housekeeping with the metadata on my TM's at the moment and it is not an easy one to get to grips with.

Especially as any wrong moves here may have an effect on later projects - TM's matching up etc. My thoughts are that it may be wise to spend some time with colleagues (if you have them) or on your own, working out lists of clients/subjects etc and stick to this rigidly as you work.

I made the mistake of carrying out loads of alignments without adding in metadata and I am now having to go through them retrospectively and add data in.

My initial thoughts are that in your case - the client would be the agency, the project could be the company, the domain would be the generic subject area and subject would be the specific area?

Is there a danger that we are trying to narrow things down too much? Could you just have 'law/engineering' as the subject? If it is too difficult to separate them?

As long as you know the headings, you can filter for them again and again.

I hope you find an answer soon


Direct link Reply with quote
 

simon tanner  Identity Verified
Italy
Local time: 07:08
Member (2007)
Italian to English
+ ...
categorisation is very personal... Jun 18, 2010

It doesn't really matter what system you use as long as it works for you. I tend to use the subject for defining document type (contract, annual report, research project) and the domain for the field. I would probably classify a highly technical contract with lots of engineering terminology as 'legal', simply because I don't do engineering jobs on the whole. But I do often get texts which are both legal and financial, such as contracts for banks. I classify them legal/financial, and I obviously use both legal and financial TMs and termbases when working on them.
In any case, to be honest, I don't really think it makes much difference how you classify it in the new project pane. What is more important is organising your TMs and termbases effectively, perhaps having separate ones for particular clients, for example


Direct link Reply with quote
 

Olaf Reibedanz  Identity Verified
Colombia
Local time: 00:08
Member (2003)
English to German
+ ...
TOPIC STARTER
Thank you! Jun 23, 2010

Thanks for the info

Direct link Reply with quote
 

Tony Keily  Identity Verified
Local time: 07:08
Italian to English
+ ...
This is basic but essential Jul 5, 2010

I am completely new to memoQ and to CAT tools, but these questions seem essential. What's more, they don't seem to be very effectively treated in the manuals made available online (Quick start guide + longer Help pdf).

One problem is that in the new project wizard gizmo there is a field for the name of the new project, and immediately below this another field for 'project'. Go figure! Doubtless these questions are completely clear when you've worked with the application for a while, but as a starter it's annoying that the first new project dialogue box makes little sense. At first look, the names of the fields don't reveal or imply evident logical/interconnected hierarchies.

Simon obviously has some experience in the field and what he says makes good sense. But surely the Kilgray people should be onto this question, providing some insight into how structuring a project/TMs initially will impact on future work. (It goes without saying that I mean that constructively!)

I'm actually in an unusal position where an agency is requiring use of memoQ because their large instiutional client is looking ahead in terms of standardisation of terminology (not bucks or yuris right now it seems). I contacted the agency, also newish to the CAT game, and the advice I was given was to start a new project for each job (the jobs can be in very similar fields) and to use a single memory for all Italian to English work. This sounds odd to me, given that although jobs group into fields of specialisation, there is huge subject variation between these fields.



[Edited at 2010-07-05 15:56 GMT]


Direct link Reply with quote
 

Jaroslaw Michalak  Identity Verified
Poland
Local time: 07:08
Member (2004)
English to Polish
Project management Jul 5, 2010

Tony Keily wrote:
One problem is that in the new project wizard gizmo there is a field for the name of the new project, and immediately below this another field for 'project'. Go figure!


This is rather unfortunate, I admit. It is just the basic translation "package" file is called a "project". It might not be related to the "project" field, as you can have one logical "project" (e.g. EU legislation) span several files, i.e. "projects" (which may be, for example, be assigned to particular jobs).


At first look, the names of the fields don't reveal or imply evident logical/interconnected hierarchies.


Because there is no underlying hierachy at all. These are simply fields which make easier to find and manage your projects. If you open the dialog Projects/Manage projects you can see that you can select projects based on the particular values of the fields. I do not think there is more to it...


[Edited at 2010-07-05 18:06 GMT]


Direct link Reply with quote
 

rmackay
Local time: 06:08
TM repository Jul 6, 2010

My view of this is, as Simon and Jaberwock say, that it appears to be fairly subjective and up to the translators/LSP's themselves to decide on what they add into the fields here and as long as they remain consistent and know that all employees are using the same method, then they should have a fairly strict method of keeping track on all data.

The big plans at memoQ HQ, for the TM repository emphasises heavily on the need for metadata and consistent metadata in order to be able to search through this large database for the exact info you require. I feel that as long as the company/translators follow the same field headings, then it will be easy to filter for the exact info required (with or without a TM repository) and then the metadata will be a success.

I guess it leads onto examples of good practice and house guidelines etc -


Direct link Reply with quote
 

Tony Keily  Identity Verified
Local time: 07:08
Italian to English
+ ...
Thanks jabberwock Jul 6, 2010

Because there is no underlying hierachy at all. These are simply fields which make easier to find and manage your projects. If you open the dialog Projects/Manage projects you can see that you can select projects based on the particular values of the fields. I do not think there is more to it...

First, thanks for your answer.

This is precisely the information that the beginner needs when tackling that first page! I would see it as hierarchy based, but I guess that's just terminology.


Direct link Reply with quote
 

Jaroslaw Michalak  Identity Verified
Poland
Local time: 07:08
Member (2004)
English to Polish
Help helps... Jul 6, 2010

Out of curiosity I have had a look at at the help page available from the dialog we have discussed and it seems to contain all the information you need... First you have the description of the dialog itself in "Project information" section, which then links to the topic "Meta-information".

Have you had a look at those?


Direct link Reply with quote
 

Michael Beijer  Identity Verified
United Kingdom
Local time: 06:08
Member (2009)
Dutch to English
+ ...
The difference between SUBJECT + DOMAIN in memoQ meta-information. Aug 15, 2010

memoQ Help says:

----------------------------------------
RELATION TO PROJECT SETTINGS:

Let us assume you create a project with these meta-information items:

· Subject: Language technology
· Domain: Translation
· Client: Kilgray
· Project: KILGRAY/001
----------------------------------------
META-INFORMATION:

Subject: Specifies subject field information.
Domain: Here you can refine the subject field if necessary.
----------------------------------------

When I read this, I am slightly puzzled. Wouldn't it be better if it read something more like:
Domain: Domain is more general than the subject field.
The word 'refine' makes me think that the Domain is more specific than the Subject.

"Client" and "Project" are more or less clear (although Project is also a slippery fish), but could someone perhaps explain the difference between "Subject" and "Domain", ... as they are defined in the memoQ help.

As a few people have already mentioned: it is very important that we try and come to some sort of an agreement as to what these can/should be used for if the TM Repository idea is to work.


Direct link Reply with quote
 

rmackay
Local time: 06:08
Domain? Be specific...... Aug 16, 2010

I totally agree with Michael on this one - I have been getting my head around the metadata for the past few months and I also feel that Domain is more general than Subject - My feeling straight away is that the Domain would be a department like 'Marketing', whilst the Subject would be a topic, such as 'News Release'.

However, if metadata really is up to the User's preference, and as long as everyone within the same company is using it in the same way, then it may be horse for courses.

Slàinte - Ruairidh


Direct link Reply with quote
 


To report site rules violations or get help, contact a site moderator:


You can also contact site staff by submitting a support request »

Project – domain – client – subject

Advanced search






Déjà Vu X3
Try it, Love it

Find out why Déjà Vu is today the most flexible, customizable and user-friendly tool on the market. See the brand new features in action: *Completely redesigned user interface *Live Preview *Inline spell checking *Inline

More info »
SDL MultiTerm 2017
Guarantee a unified, consistent and high-quality translation with terminology software by the industry leaders.

SDL MultiTerm 2017 allows translators to create one central location to store and manage multilingual terminology, and with SDL MultiTerm Extract 2017 you can automatically create term lists from your existing documentation to save time.

More info »



Forums
  • All of ProZ.com
  • Term search
  • Jobs
  • Forums
  • Multiple search