We have implemented a shared project for a major initiative. This initiative includes SEVERAL independent projects (all related to the overall initiative), which are created as sub-packages. Unfortunately, the cummulative glossary for these projects will probably be quite extensive, and we do not want to include all the terms in every project.
We thought about assigning a custom attribute to dictionary terms. That held promise, but there were still issues with being able to select a particular set of terms for each project. We were unable to reuse the same term with a new custom attribute (does not seem to be supported in this release).
We also investigated having a separate dictionary file for each project, but that does not seem to be supported.
Are we doing something wrong? Does anyone have any suggestions as to how we can accomplish what we need to?
Thanks!
Tom
Please sign in to leave a comment.
Tom, just trying to make sure I understand your motives: when you say "we do not want to include all the terms in every project" are you talking specifically about reporting? Do you want only certain terms to show up in reports when filtering by package?
Matt,
When creating a document/report for one sub-project of a large shared project, we would like to be able to include specific terms. We have been able to approach this by applying a custom field to the dictionary terms. HOWEVER, what this will NOT allow us to do is to have different (or slightly different) meanings for the SAME term.
I suppose we could have a single entry for a term with multiple definitions. That seems to be the only way to accomplish what we want, since we CANNOT use the same term with different values for the custom attribute.
Hope this clarifies.
Thanks!
Hey Matt!
Any updates/new info?
Tom
Hi Tom!
We were brainstorming for a clever/creative solution that would work using existing functionality. Unfortunately, we didn't come up with one.
What if you simply used a prefix to your term names as a way to indicate their scope? For example:
package1_term1
package2_term1
Not the most elegant solution, but it might work until we have a better way to deal with multiple dictionaries in a project.
Well, I guess we can look at "term (scope)" as an alternative method. Not quite the most elegant, but possible. The other alternative would be to include both (or multiple) definitions for the same term and identify them within the definition:
Term (Global) Global definition
(Project) Project specific definition
Would be nice to see the ability to specify a dictionary file for a project (or package). Is that on the radar? Can a dictionary/glossary file be included as a related document (I'm guessing that would raise problems in printing)?
Thanks for trying!
Tom
A glossary file cannot be added as a related document but what is on our radar is the ability to incorporate multiple dictionaries per project. I'm not sure exactly when we'll get to this, but it's something customers have been asking us about.
Has the incorporating multiple dicttionaries per project been implemented in CaseComplete 11?
Hi Vicki,
Sorry, no. Still no estimate on when this might become available.
Doug
