Book a Demo

Author Topic: Export glossary as CSV file  (Read 6744 times)

speekna

  • EA User
  • **
  • Posts: 25
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Export glossary as CSV file
« on: February 04, 2008, 03:21:20 pm »
I'd like a procedure for exporting / importing the glossary as a CSV file.  I can find how to export/import to csv, but it wants a package as the input - i.e., import/export domain model.  According to the documentation for the Project menu, I should be able to do this...

Does anyone know how to do this?  Or can you point me to written instructions?

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Export glossary as CSV file
« Reply #1 on: February 04, 2008, 03:35:38 pm »
AFAIK you have to export or import the glossary as reference data (look for "Model Glossary"). That will give you an XMI file, not a CSV file. You'll have to do the transform yourself.

You could always run it through an XSLT transform, which should not be too difficult. The same holds true for the other direction, whichever one you started with.

HTH, David

PS: I too would like to see more cases where CSV import and export were accommodated. There are several kinds of reference data that fit well into the flat file paradigm.
No, you can't have it!

speekna

  • EA User
  • **
  • Posts: 25
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Export glossary as CSV file
« Reply #2 on: February 04, 2008, 03:43:29 pm »
I realize that you have to export/import the glossary as reference data - but there's no way, in the csv import/export process, to "point" to the reference data / glossary.   To use export/import, you need to select a package - and there's no (that I can see) way to select a package that contains a glossary.

Thanks for your reply though  :)

KP

  • EA Administrator
  • EA Expert
  • *****
  • Posts: 2919
  • Karma: +55/-3
    • View Profile
Re: Export glossary as CSV file
« Reply #3 on: February 04, 2008, 03:46:26 pm »
Another idea would be to create a new RTF document template based on the provided (model glossary template). Strip out the table and heading and add quotes and commas and you get something like this:

Code: [Select]
model>
glossary>
"{ModelGlossary.Term}","{ModelGlossary.Type}","{ModelGlossary.Meaning}"
<glossary
<model
The Sparx Team
[email protected]

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Export glossary as CSV file
« Reply #4 on: February 04, 2008, 05:35:26 pm »
Very nice!

I take it we could (try to) use this in other areas. Of course we might have to create our own templates for those...

David
No, you can't have it!

Jan ´Bary´ Glas

  • EA User
  • **
  • Posts: 408
  • Karma: +0/-0
  • Bary
    • View Profile
Re: Export glossary as CSV file
« Reply #5 on: February 05, 2008, 12:01:16 am »
Nice to hear that I've found out the same the admin recommends ;-) In fact I thougt is was a pure workaround ;-)
Jan 'Bary' Glas

speekna

  • EA User
  • **
  • Posts: 25
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Export glossary as CSV file
« Reply #6 on: February 05, 2008, 10:48:35 am »
This will work for export, & a way to show people w/o EA what the terms are.

What I need now is how to import a glossary.  Currently, we have a corporate vocabulary in Excel, from which I can get a CSV file.

I'm exploring how I can define an element type that is, or holds/contains, glossary entries.  If I can put these in a package, then I can import/export them.  

Continuing feedback much appreciated!

Aaron B

  • EA Administrator
  • EA User
  • *****
  • Posts: 941
  • Karma: +18/-0
    • View Profile
Re: Export glossary as CSV file
« Reply #7 on: February 05, 2008, 02:58:32 pm »
You could define your own Import/Export process by writing an application that uses EA's Automation Interface.  Glossary Terms are accessed through the Repository.Terms collection which allows you to read out all existing terms, and also allows you to add, edit and remove terms.

For more information on using automation, refer to the EA help file.  Further code samples can be found under the Resources link at the top of this page.