Synopsis: While keeping core TopBraid functionality, it is great to have a quick view of repo changes.

It is always better to use the TopBraid perspective since we will be dealing with a lot of graphs and queries. That said, it is a great reminder to keep tab of changes made to the local repo. To do this without switching between perspectives, enable to Git Staging view:

  1. Window > Show View > Other...
  2. In the Show View dialog, select Git > Git Staging
  3. Click Ok
  4. The Git Staging view appears in the lower right quadrant of the TopBraid perspective

Synopsis: At times, it is useful to reset a perspective to its "factory default."

It is very easy to be lost in the world of Eclipse IDE elements, especially almost everything is customizable. UI elements such as panes and views may seemingly disappear after docking, resizing, minimizing, and other user actions. it is useful to reset the UI elements back to its original design:

  1. Window > Perspective > Reset Perspective...
  2. Click Yes

Note

This reset action will also remove the Git Stage view.

Synopsis: Loading the graphs of all versions of a standard allow us to navigate and analyze metadata across versions

Turtle files (*.ttl) in the git repo are named with version embedded. For example, sdtmig-3-2.ttl is the graph for SDTMIG v3.2, cdashct-2018-06-29 is for CDASH Controlled Terminology published on June 29th, 2018, and so on. SDTM, as the tabulation product family for human clinical use, alone consists of 5 models, 6 implementation guides, and numerous quarterly releases of SDTM CT packages. Opening them one at a time is too tedious. Therefore, we engineered a series of top-level Turtle files that import related versioned standard graphs. They are:

FileRemarks
adam.ttlImports ADaM CT package also
cdash.ttlImports CDASH CT package also
qrs.ttl
sdtm.ttlImports SDTM CT package also
send.ttlImports SEND CT package also
adamct.ttl
cdashct.ttl
sdtmct.ttl
sendct.ttl
terminology.ttlImports all CT packages
share-all.ttlImport everything above

Consideration

Some of these top-level Turtle files will require a lot of hardware resources and possibly lock up a computer. Monitor system resource usage is advised.

Synopsis: TopBraid limits the size of query result set. This default can be changed.

TopBraid SPARQL result set is set to a system default of 1,000. This can be frustrating to the unaware eyes, especially when the result set unsorted. Time may be wasted to unnecessarily troubleshoot the query. To change the default:

  1. Window > Preferences
  2. In the Preference dialog, select TopBraid Composer
  3. Tune the value in Max. number of instances to display

Note

This setting affects both instance listing in the Instance view, as well as the SPAQRL query result listing.

Consideration

The higher this number, the larger amount of system resource TopBraid requires.

Refer to the My SPARQL Results Are Truncated! section above

Synopsis: TopBraid is unable to load an error-free Turtle file and throws a runtime exception. There are several scenarios where this could happen.

Many cases Java stack is not very useful to troubleshoot problems.


ScenarioSolutionScreenshot
1NullPointer exception is thrown.

Due to our folder structure mimicking different stages, the same Turtle file may exist in multiple locations. Make sure the Turtle file being open is designated as primary in the same git repo folder.

Synopsis: Commit messages are meant to be brief. Therefore, it may be useful to link a git commit to JIRA issue(s) that provide details

If you included JIRA issue ID(s) in your commit message, Bitbucket is smart enough to not only parse them, but also hot-link to them. The following screenshot is an example demonstrating how Bitbucket transforms JIRA issue IDs in a commit message and display them (direct link to the same commit hash: https://bitbucket.cdisc.org/projects/SHARE/repos/share-2-0/commits/2e0a1a6ebe71a9364d9a0140df31c94c9d057d97)

  • No labels