tolerantsoftware/name repository overview

⁠Quick reference

• Maintained by: https://www.tolerant-software.de/⁠
• Where to get help: [email protected]⁠
• Release Notes: https://www.tolerant-software.de/en/products/tolerant-name/product-support/⁠

⁠Product Overview

⁠Check names reliably and structure them uniformly

Your female customer receives a high-quality catalogue – and is addressed as a gentleman. Another customer may have been annoyed for a long time that his doctoral title is mentioned incorrectly or not at all in every newsletter that reaches him. Such slip-ups are not only unpleasant – they are also superfluous. Because TL Name validates the names and the correct spelling of your customer data already during data entry.

⁠Name validation already during data entry

When entering customer names, many errors can creep in. Because names consist of several elements. Often, however, these elements are entered in a single field or are stored in the wrong field. In a hurry, careless mistakes can occur. For the correct customer address – e.g. in the letter or e-mail salutation – you must know the individual building blocks such as salutation, title, first name and last name and combine them correctly.

TL Name analyzes, standardizes and structures the name components in your master data and helps you to address your customers with the correct name. In addition, TL Name checks your address database against reference lists of valid names and evaluates the plausibility of the data entered.

⁠Best data quality for correct salutations and successful data processing

TL Name can both check your inventory data and be used directly during data entry. The result: a consistently high level of your data quality. Your data is uniformly structured and thus perfectly prepared for further processing, for example the generation of correct salutations for marketing campaigns, correct duplicate recognition or customer clustering.

⁠How TL Name validates and structures your data:

⁠TOLERANT Name image

⁠Usage

Notes

Starting and stopping can be managed using a simple docker compose file. Here is an example:

version: '3.8'
services:

  name:
    image: tolerantsoftware/name:11.0
    container_name: name
    mem_limit: 2g
    mem_reservation: 512M
    cpus: 2
    volumes:
      # persist name logs
      - name-logs:/opt/tolerant/logs
      # Licenses and data must be provided for the container to run properly
      # Bind mounts for test purposes only:
      - type: bind
        source: ./config
        target: /opt/tolerant/config
      - type: bind
        source: ./data
        target: /opt/tolerant/data
      # Example for custom configuration via volume:
      # - name-config:/opt/tolerant/config
      # Example for custom data via volume
      # - name-data:/opt/tolerant/data
    environment:
      # username and password of a admin for the health check, in case the security is activated
      - HEALTH_USER=admin
      - HEALTH_PASS=admin
      - TZ=Europe/Berlin
    ports:
        - "8080:8080" 

volumes:
  name-logs:
  # Examples for external created volumes with custom configuration and data
  # name-config:
  #   external: true
  # name-data:
  #   external: true

⁠Starting the container

The container can be started using the following command:

docker compose up -d

The docker compose command should be executed from the directory containing the docker-compose.yaml file.

⁠Stopping the container

A running container can be stopped using the following command:

docker compose down

The docker compose command should be executed from the directory containing the docker-compose.yaml file.

⁠Starting a batch process

docker compose exec name nameBatch.sh <configFilename> <projectId> <profileId>

⁠License

TOLERANT Name is licensed under a commercial license. This means that the software can only be used for commercial purposes, and that the user must have a valid license to use the software. To get a valid license, please contact [email protected]⁠