Termbases and Terminology Management Systems

Lecture 12 Week 6

Customizable input templates

Admins can create different templates for adding new terms, tailored to specific users or groups.

Create entry by duplicating another

Allows faster entry creation by copying and modifying existing entries.

Copy fields to all terms in entry

Enables copying a field’s content to all terms in an entry for efficiency.

Batch editing

Lets users work on multiple entries at once without exporting/importing, boosting productivity.

Customizable views

Users can save and assign views that hide fields, languages, or subsets of the termbase.

Select SL and TL

Users can set preferred source and target languages, with TL shown directly below SL.

Language display

Users can customize which languages appear and in what order.

Layout styles

Admins can customize layout appearance, including colors and fonts.

Wildcard search ()

Matches any number of characters. Example

Wildcard search (?)

Matches a single character. Example

Wildcard search (range -)

Matches a range of characters. Example

Wildcard search (#)

Matches a single numeric character. Example

Fuzzy search

Finds approximate matches to a term, useful for misspellings. Use ~ (e.g., bank~ finds tank, benk, banks).

Boolean operators

Use AND, OR, NOT to combine or exclude keywords for more focused search results.

Wildcards (TMS feature)

Search should support wildcards in any position, with multiple wildcards allowed.

Fuzzy search (TMS feature)

May include pattern matching like letter reordering to find approximate matches.

Full-text search

Allows searching across one or more text fields, like definitions.

Search in more than one termbase

Users can search across multiple termbases simultaneously.

Batch search

Upload or input a list of terms to search all at once and receive a report.

Filters

Use Boolean logic to search by metadata like term type, creation date, or user.

Incomplete records

Search for entries missing a definition.

Entries without translation

Search for entries missing a term in a specific language.

Filters can be reused

Saved filters can be applied again later.

Filters can be shared

Filters can be kept private or shared with others.

Statistics (filters)

Filters should show how many concepts and terms match the criteria.

Restrictable rights

Access can be limited by user or group at different levels.

Restrictions by function

Limit who can create, edit, delete, import, or export entries.

Restrictions by language

Limit access to specific languages for certain users or groups.

Restrictions by subset/section

Access can be restricted to parts of the termbase using filters.

Restrictions by field

Limit who can edit specific fields, like definitions.

Restrictions by role

Roles like writer, translator, reviewer can have tailored access rights.

Concept relations

Semantic links between concepts, shown in concept maps.

Generic relation

“Type of” relationship, e.g., pine tree is a type of coniferous tree.

Partitive relation

“Part of” relationship, e.g., spoke is part of wheel, which is part of bicycle.

Temporal relation

Time-based sequence, e.g., primary school before secondary school.

Spatial relation

Position-based, e.g., interfacing is placed inside fabric layers.

Associative relation

Cause-effect, product-user, or other associative links, e.g., saw–lumberjack–forest.

Entailed terms

Hyperlinked terms in text fields that point to other entries.

Between entries

Dedicated fields at concept level to link concepts.

Precise link mechanism

Links should use concept or term IDs, not just written forms.

Bidirectional relations

If A links to B, B should automatically link back to A.

Different types of relations

TMS should support generic, partitive, associative, and other relation types.

External links

Ability to link to external sources from within the termbase.

Relation graphs

Visual maps of concept relationships, useful for knowledge systems.

Avoidance of broken relations

Warn users before deleting entries that would break links.

Manage broken relations

Tools should help identify and fix broken links.

Users can suggest terms

Easy, intuitive way for users to propose new terms.

Commenting

Users can leave comments on entries.

Feedback to admin

Users can send feedback directly to administrators.

Permalinks

Direct links to entries for easy sharing.

Role-based workflows

Workflows can be triggered by user roles, e.g., proposed terms reviewed by a terminologist.

Workflow triggers

Workflows can start automatically based on changes in the termbase.

Workflow notifications

Notifications can be scheduled based on volume or time.

Workflow scheduling

Set start times and deadlines for workflows.

Customizable workflows

Define pre-conditions and post-actions based on termbase fields.

User management

Admins can create, edit, delete users, and reset passwords.

Group management

Create user groups and assign termbase objects like workflows or filters.

Job scheduling

Automate tasks like notifications, purging, or hand-offs.

Projects

Define collections of settings and tasks for focused termbase work.

Automated backups

Schedule regular backups of the termbase.

Restore from backup

Fully restore the termbase from a saved backup.

Global changes

Make changes across the entire termbase, e.g., update a word in all definitions.

Enhance performance

Debugging tools like reindexing should be available to resolve slowdowns.

Statistics (admin)

Dashboard should show detailed usage and content metrics.

Search log

Track search queries to identify missing terms or usage trends.