Glossary under version control

[Quido Evers]

Hello,

Is there a way to put the Glossary under version control?

We are using Enterprise Architect with approx. 40 people. All of the diagrams, elements, etc are under version control (Team Foundation Server). I've recently discovered the Glossary of EntArch and it looks like a very nice feature. I cannot find a way to put this Glossary under version control, except to export the list and place that export in TFS.

However, if we do it this way, everyone using EntArch will have to import the Glossary manually, everytime it changes.

It would be nice if there is a way to share the Glossary. There is no use to a Glossary if you can only see the definitions you write yourself (since you wrote them, you probably know what the terms mean).

Tia,

Quido Evers

Edit: typo corrected.

[Guillaume]

Hi Quido,

This is a major issue with EA i.e. reference data including images, glossary, RTF templates, etc cannot be maintained in SVN
The only option for you is to run the export reference data to an XML file that you can add to SVN (you may select all or the project glossary only)

Hopefully one day Sparx will VC separately each reference data.

Guillaume

[Quido Evers]

Hi Guillaume,

Thank you for your quick response. We had noticed that some information in the project cannot be place under version control. I hoped that the glossary was an exception to this ..

Anxiously awaiting the next version.

Quido.

[Luis J. Lobo]

We've created the Project Glossary under a Package, where a Term is an element and its definition is the description.

The "Glossary" package is versionable, and also you can link the "Terms" (elements) with any related model element.

Regards,

Luis.

[qwerty]

We've created the Project Glossary under a Package, where a Term is an element and its definition is the description.

The "Glossary" package is versionable, and also you can link the "Terms" (elements) with any related model element.

Regards,

Luis.

Nice to see someone else came to the same solution. We even have the possibility by nesting <<trans>> elements to store multi language descriptions.

q.

[Luis J. Lobo]

Good idea!! thanks!