[en] If you use a third-party terminology solution, you can configure Acrolinx so that you can use both systems together. For example, suppose that you want to use Acrolinx to check your content, but use a third-party solution to manage your terminology workflow. You can configure Acrolinx so that while writers check their content with Acrolinx, they’re redirected to the third-party solution when they click the links for the term help or term contribution.
[en] To integrate Acrolinx with your external terminology solution, you must configure the URL templates for the term help and term contribution in the core server properties file. Also, your third-party terminology solution must accept data sent through these URL templates. In most cases, this requires a customized solution.
[en] You can configure Acrolinx so that when writers open the term help, they'll see the help from your third-party terminology management solution instead of Acrolinx.
[en] You do this by defining a template for how the URL should be constructed. The template syntax is the same as the syntax that is defined in the RFC 6570 standard. You don't need to know all about this standard to configure the template, but if you're interested, you can read the template specifications on the Internet Engineering Task Force (IETF) website.
[en] For example, the default template for the term help URL has the following structure:
[en] {+baseUrl}{+termHelpContext}{?termUniversalId}
[en] This template would resolve to a URL that resembles the following example:
[en] https://acrolinx.demo-inc.com/termhelp/?termUniversalId=690bfacb-bc26-4f8a-b63e-9c795873b2a2&locale=en
[en] Here's how the default template is resolved:
-
[en]
{+baseUrl}resolves tohttps://acrolinx.example.com -
[en]
{+termHelpContext}resolves to/termHelp/ -
[en]
{?termUniversalId}resolves to?termUniversalId=690bfacb-bc26-4f8a-b63e-9c795873b2a2&locale=en .
[en] However, let's say you use the quickTerm V5 tool produced by Kaleidoscope. You would configure the template to look something like this:
termHelpUrl.template=http://acme-intranet.com/qtweb/Pages/Main/Search.aspx?tuuid={termUniversalId}&euuid{entryUniversalId}&showOnly=true
[en] For quickTerm V6, the syntax looks something like this:
termHelpUrl.template=http://qttrial.kaleidoscope.at/terminology/search?termbaseName=%3CAcrolinx%3E&entryId={entryId}&tenant=Acrolinx
[en] This would configure Acrolinx to call the help from quickTerm while passing the Acrolinx universal ID for the term and the head term (also known as "term entry" or "concept" in other systems).
Tipp
[en] If you're on an Acrolinx Private Cloud 
instance and are interested in these configurations, contact us and we'll set them for you!
[en] If you're a Standard Stack user, you can edit the coreserver.properties from the configuration directory. Depending on your installation, your path might look like this:
[en] <config directory>/server/bin/coreserver.properties.
[en] To configure a custom term help URL, follow these steps:
-
[en] Open your
coreserver.properties. -
[en] Add the following property:
termHelpUrl.template=<URL_TEMPLATE>
[en] As mentioned previously, a quickTerm V6 help URL might look something like this:
termHelpUrl.template=http://qttrial.kaleidoscope.at/terminology/search?termbaseName=%3CAcrolinx%3E&entryId={entryId}&tenant=Acrolinx[en] You can use the following parameters for the URL template:
[en] Parameter
[en] Details
[en]
baseUrl[en] The base URL of your Acrolinx Platform. Use {+baseURL} to use your Acrolinx Platform or enter the address of your third-party solution.
[en]
termHelpContext[en] The term help page of your terminology solution. Use{+termHelpContext} to use the Acrolinx term help page or enter the path to the term help page in your third-party solution.
[en]
termId[en] A custom term identifier that you can use to retain identifiers generated by another system.
[en] If you've imported your custom identifiers into Acrolinx, you can pass them back to your third-party solution.
[en]
entryId[en] A custom term entry identifier that you can use to retain identifiers generated by another system.
[en] If you've imported your custom identifiers into Acrolinx, you can pass them back to your third-party solution.
[en]
termSurface[en] The name of the term.
[en]
termUniversalId[en] The universal ID of the term.
[en]
entryUniversalId[en] The universal ID of the term entry.
-
[en] Save your changes and restart the Acrolinx Platform.
[en] You can use Acrolinx to discover terms in your content and give people the option to contribute terms to a terminology database. As a reminder, the default workflow for contributing terms looks like this:
-
[en] You check that your content and all discovered terms are listed on the Scorecard and in the Acrolinx Sidebar.
-
[en] In the Sidebar, you can click a "Contribute Term" button that is available for each discovered term.
-
[en] This button opens up a form within the Sidebar where you can add a comment about your contribution before you submit it to the Acrolinx terminology database.
[en] However, if you use another terminology solution you'll want to bypass parts of this workflow. Instead, when you click "Contribute Term", you can have Acrolinx open a third-party term contribution form. To enable this feature, you need to disable the default behavior and configure a custom term contribution URL.
[en] To disable the default behavior and configure a custom term contribution URL, follow these steps:
-
[en] Open your
coreserver.properties. -
[en] Add the following properties:
termContribution.disableInternalTermContribution=true termContributionUrl.template=<URL_TEMPLATE>
[en] The template must be specified according to RFC 6570. The default value of the template is
{+baseUrl}{+termContributionContext}{?locale} #surface={+escapedSurface}{&language}{&userid}&{contextFieldName}={+escapedContext}[en] If you use quickTerm V5 with SDL MultiTerm, your term contribution URL might look something like this:
termContributionUrl.template=http://acme-intranet.com/qtweb/Pages/Main/TermRequest.aspx?term={surface}&tbname=my_multiterm_db&sourceLang={language}&customUserName={userid}&contextField={contextFieldName}&contextValue={context}[en] For quickTerm V6 with SDL MultiTerm, your term contribution URL might look something like this:
termContributionUrl.template=http://qttrial.kaleidoscope.at/terminology/search?new-term-request&term={surface}&sourceLangCode={language}&tbname=%3CAcrolinx%3E&customUserName={userid}&tenant=Acrolinx[en] Of course, you should replace sample values
acme-intranet.comorqttrial.kaleidoscope.atwith the address of your quickTerm server andmy_multiterm_dbwith the name of your MultiTerm terminology database.[en] You can use the following parameters for the URL template:
[en] Parameter
[en] Details
[en]
baseUrl[en] The base URL of your server. Use {+baseURL} to use your Acrolinx Platform or enter the address of your third-party solution server.
[en]
termContributionContext[en] The term contribution page of your terminology solution. Use {+termContributionContext} to use the Acrolinx term contribution page or enter the address of the term contribution page your third-party solution.
[en]
locale[en] The locale of the user interface.
[en]
surface[en] The plain text version of the contributed term.
[en]
escapedSurface[en] The Acrolinx-escaped and optionally Base64-encoded version of the contributed term.
[en]
language[en] The language of the term.
[en]
userid[en] The username of the contributing user.
[en]
contextFieldName[en] The name of the context field.
[en]
context[en] The plain text context of the contributed term.
[en]
escapedContext[en] The Acrolinx-escaped and optionally Base64-encoded context of the contributed term.
-
[en] (Optional) Add the following property:
termContributionUrl.enableBase64Encoding=true[en] This property enables the Base64 encoding of the term and the context in the term contribution URL.
-
[en] Save your changes and restart the Acrolinx Platform.