Great news, Troy - this is supported now via import package! (Click File / Import/Eport / Import Package File on the ribbon bar.)
Let me start off by defining packages a bit. You can think of them like folders within your Windows directory structure; they serve to organize your project. In addition, you can save each package in a separate file - which is the default setting - to allow each package to be checked out and worked on independently in a shared project/team environment. Packages can own multiple elements - including dictionary terms - sort of like how files are kept within your Windows folders.
In regards to creating a "template project" for use across future projects, you can keep this project with your bucket of elements - in a single package or multiple "template" contents- separate from any others, and then import those elements into future projects as you go along.
Assuming your projects are version controlled, here are the steps on how you would share items:
1) Keep the project that holds the common elements (let’s call this the master project) and the project that wants to reference the common elements (let’s call this the referencing project) in separate repositories.
2) Make sure the package that holds the common items is saved as a separate file in the master project (again, this is the default when creating new packages).
3) Use File / Import / Package File to bring it into the referencing project.
If you'd like, you can also update this information across all projects after changes have been made to the master project. Here are the steps to update the referencing project:
4) Check out the common package in the referencing project
5) If there are any sub-packages or diagrams owned by items in the common package, check those out too
6) Delete the common package from the project (select it in the project browser and press delete). In the confirmation dialog, leave the checkbox about removing it from version control unchecked:
(see attached screenshot)
7) Using Windows Explorer, delete the package file from the referencing project’s working folder. CaseComplete won’t be able to import if the file still exists.
8) Re-import the package file from the master project’s working folder.
Alternate: If you're only importing a package containing dictionary terms, you could skip step 6, and instead of deleting the package in step 7, copy it from the master folder and paste in the referencing folder (overwriting it). The downside of this approach is that if the common package holds diagrams, you’d have to do the same for diagram files (but if you use the steps as described above, diagrams are handled).
The good news is that we're making some improvements to this process in the upcoming version - CaseComplete 2012 R2 - so look for that coming very soon!
I hope this answers your questions. If you'd like any clarification on any points, please don't hesitate to let us know.