Datagroup Annotation / user settings

Need a little help with datagroup annotation settings.

I've managed to define the configuration of which cells to use for datagroup annotations. Apparently this only works for myself as an user, but not for the other users in the office.

Is there a way to define a default setting of which cells are used for annotation for the whole office?

Parents
  • Hi Andreas,

    BB_ANNOTATION_CELLLIB will set the path to the library containing all of your auto annotation cells. This can be set to a company library in your site wide Company Dataset or to a project library in ...\support\dataset\cell.

    TFANNOTATION_OVERRIDES specifies the location of the annotation settings file, by default this is in the project ...\support\dataset\setting\annotationoverrides.xml.

    So when you modified the cells selected in the Annotate Tool Settings dialog, those selections should be stored in the project you were using at that time. The modified annotationoverrides.xml file can be copied to your project template as a default for future projects and to each of your existing projects.

    You could also direct TFANNOTATION_OVERRIDES to a company dataset to apply to all projects (you would need to control permissions to avoid individual project teams making conflicting changes!). If a project needed variations from the company standard TFANNOTATION_OVERRIDES could be set to point to the project dataset.

    Regards

    Marc

Reply
  • Hi Andreas,

    BB_ANNOTATION_CELLLIB will set the path to the library containing all of your auto annotation cells. This can be set to a company library in your site wide Company Dataset or to a project library in ...\support\dataset\cell.

    TFANNOTATION_OVERRIDES specifies the location of the annotation settings file, by default this is in the project ...\support\dataset\setting\annotationoverrides.xml.

    So when you modified the cells selected in the Annotate Tool Settings dialog, those selections should be stored in the project you were using at that time. The modified annotationoverrides.xml file can be copied to your project template as a default for future projects and to each of your existing projects.

    You could also direct TFANNOTATION_OVERRIDES to a company dataset to apply to all projects (you would need to control permissions to avoid individual project teams making conflicting changes!). If a project needed variations from the company standard TFANNOTATION_OVERRIDES could be set to point to the project dataset.

    Regards

    Marc

Children
  • and for the avoidance of doubt:

    TFANNOTATION_PREFS points to AnnotationPrefs.rsc in each user's preferences folder. This stores each users last used selections in annotation tools, a different function to annotation overrides.

    Regards

    Marc

  • Very helpful, though I do think there are some things in addition.

    At first your recipe wasn't working so very well. We had TFANNOTATION_OVERRIDES set to the project folder, so in theory regardless of which user I chose when I start Aecosim, they should get the same annotations as long as they work on the same project. But that wasn't the case.

    I then copied the annotationoverrides.xml file from the project folder to our workspace folder, and suddenly the other users also got the correct annotations.

    I don't know what's going on there, but I just tell you what I found out.

    Running a different project gave us a problem again, as the TFANNOTATION_OVERRIDES was defined to a different project folder, with an old annotationoverrides.xml file. After redefining the variable to our workspace, I think we nailed it down now. As far as I see, things work as expected.

    Thanks for the help.

    Answer Verified By: Andreas Zieritz