Cannot convert and import Excel glossary into termbase
Thread poster: Andreas THEODOROU

Andreas THEODOROU  Identity Verified
Spain
Local time: 05:34
Greek to English
+ ...
Jan 7, 2011

Hello all

One of my new year's resolutions was to get my head around MultiTerm and to get some kind of return on my investment.

So now I am trying to get all my existing Excel glossaries into a Studio termbase.

I started playing around earlier today.

This is my termbase definition:

Indexes:
English and Greek

Entry Structure:
...ENTRY LEVEL
...Rel
...Sub1
...Sub2
......INDEX LEVEL
.........TERM LEVEL
.........Notes


And my Excel glossary has the following columns:

English
Greek
Rel
Sub1
Sub2
Notes

I keep getting an error message at the import stage. In the log file, I see the following error message for every term:

-1 Does not conform to the target termbase definition.
Reason: Unknown node name
Source: /descripGrp/ /descrip type="Notes"/ xxx //descrip/ //descripGrp/

(slash used in place of opening and closing tags to allow display here)

I have tried modifying different factors one at a time to see what the problem could be, for example:
- I made sure that there were no empty columns in Excel
- I filled empty cells with at least one character
- I've tried using a different "fill" character
- I've tried running a new Conversion Session Definition every time rather than running from a template

I tell a lie, it did work once (and this makes it all the more confusing and frustrating, as if this success were a fluke). The successful conversion and importation occurred just after I had added a new column in the Excel file (Sub1) so that all Excel columns and all Studio fields would have a "partner".

What is going on? The software is not inspiring confidence by failing to accomplish such a simple task.

Thanks for any answers.

Andreas


[Edited at 2011-01-07 16:22 GMT]


Direct link Reply with quote
 

Jerzy Czopik  Identity Verified
Germany
Local time: 05:34
Member (2003)
Polish to German
+ ...
Major information missing Jan 7, 2011

Do you apply the filed and index types correctly when running MultiTerm Convert?
If yes, what if you change the name "Notes" to "Remarks"?


Direct link Reply with quote
 

Andreas THEODOROU  Identity Verified
Spain
Local time: 05:34
Greek to English
+ ...
TOPIC STARTER
... Jan 7, 2011

What do you mean, Jerry?

What do you mean by "applying file types correctly"?

For index types, if you mean "Do you apply Greek index to Greek field and the English index to English field" then the answer is yes.


[Edited at 2011-01-07 16:44 GMT]


Direct link Reply with quote
 

Jerzy Czopik  Identity Verified
Germany
Local time: 05:34
Member (2003)
Polish to German
+ ...
And what are the field types applied for the others? Jan 7, 2011

OK, so you do apply the correct languages. That is great.
Did you try to create a new termbase using the termbase defition created during the conversion process and subsequently import the Excel contents there?


Direct link Reply with quote
 

Andreas THEODOROU  Identity Verified
Spain
Local time: 05:34
Greek to English
+ ...
TOPIC STARTER
... Jan 7, 2011

As you suggested, it works when I create a new termbase using the termbase definition created during the conversion process and then import the Excel contents

So this demonstrates that there is some kind of incompatibility between the existing TB or its termbase definition and the conversion-created termbase definition? I can't think of what this is because I used the same settings.

Why was it not working earlier?


Direct link Reply with quote
 

Jerzy Czopik  Identity Verified
Germany
Local time: 05:34
Member (2003)
Polish to German
+ ...
Notes Jan 7, 2011

Where did you attach Notes in the Convert process?
In your TB Notes is a field attached to Term Level.
Did you also attach it to Term Level in Convert?
Is the spelling 100% identical or does one read Note and the other Notes? Space at the end of the word?


Direct link Reply with quote
 

Andreas THEODOROU  Identity Verified
Spain
Local time: 05:34
Greek to English
+ ...
TOPIC STARTER
... Jan 7, 2011

To answer your questions:
- I also attached Notes to Term level during the Conversion.
- spelling is exactly identical


Direct link Reply with quote
 

Andreas THEODOROU  Identity Verified
Spain
Local time: 05:34
Greek to English
+ ...
TOPIC STARTER
... Jan 7, 2011

Also there is no space after Notes field name in the definition of the existing termbase (I looked in the Layout and there was no space between Notes and the colon)

Direct link Reply with quote
 

Jerzy Czopik  Identity Verified
Germany
Local time: 05:34
Member (2003)
Polish to German
+ ...
Really strange Jan 7, 2011

Never had this problem before.
Do you have any particular reason not to create an additional termbase but to import into an existing one instead? If no, just keep the old one and create a new one.
If no, what about exporting the old one and trying to import it into a new one, created with the xdt from Convert?


Direct link Reply with quote
 

Andreas THEODOROU  Identity Verified
Spain
Local time: 05:34
Greek to English
+ ...
TOPIC STARTER
GRRRRRRRRRR Jan 7, 2011

Now I can't even open the termbase, I get this message.

"There was a problem opening the termbase at "C:/.." . Check that this is a valid termbase and that you have permission to access it."

I'm gonna call it a day and see how I feel in the morning before approaching this again.


Direct link Reply with quote
 

Jerzy Czopik  Identity Verified
Germany
Local time: 05:34
Member (2003)
Polish to German
+ ...
Restart the program / PC Jan 7, 2011

and check again.
I don't know why that happens.


Direct link Reply with quote
 
Daniel García
English to Spanish
+ ...
At which level is the Notes field? Jan 8, 2011

Hi, Andreas,

In case it helps, could it be that the mismatch is in the notes field?

Andreas THEODOROU wrote:

To answer your questions:
- I also attached Notes to Term level during the Conversion.
- spelling is exactly identical



You say that the notes field is "at term level" during the conversion but in your description of the target termbase it is an "Index level" field:

This is my termbase definition:

Indexes:
English and Greek

Entry Structure:
...ENTRY LEVEL
...Rel
...Sub1
...Sub2
......INDEX LEVEL
.........TERM LEVEL
.........Notes


In order to be a "term level" field, your definition should look like this:


This is my termbase definition:

Indexes:
English and Greek

Entry Structure:
...ENTRY LEVEL
...Rel
...Sub1
...Sub2
......INDEX LEVEL
.........TERM LEVEL
..............Notes


Just in case...

Daniel


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 »

Cannot convert and import Excel glossary into termbase

Advanced search







SDL Trados Studio 2017 Freelance
The leading translation software used by over 250,000 translators.

SDL Trados Studio 2017 helps translators increase translation productivity whilst ensuring quality. Combining translation memory, terminology management and machine translation in one simple and easy-to-use environment.

More info »
Wordfast Pro
Translation Memory Software for Any Platform

Exclusive discount for ProZ.com users! Save over 13% when purchasing Wordfast Pro through ProZ.com. Wordfast is the world's #1 provider of platform-independent Translation Memory software. Consistently ranked the most user-friendly and highest value

More info »



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