- Release Notes v7.0
- Getting Started
- System Management
- General Information
- Users
- Groups & User Crowds
- Softkeys
- Reports for User and Group Information
- User Settings Templates
- Workflows
- Relations
- Languages
- Fonts
- User settings
- System settings
- Editing States
- User Dictionary
- crossGrid
- crossGrid Packaging Templates
- crossTank
- crossWAN Packaging Templates
- Subjects
- Information
- Machine Translation
- Project Settings Templates
- Quality Management v6.3
- Quality Management v7.0
- Reporting
- Segmentation
- Language Settings
- Structure Attributes
- System Attributes
- Search Center
- Concordance Search Results
- Stopwords
- Term Extraction
- Document Settings
- Document Associations
- Display Text
- .NET Resources
- Excel 2000-2003
- Excel 2007-2016
- IDML
- MIF 7
- MIF 8-2019
- PowerPoint 2000-2003
- PowerPoint 2007-2016
- QuickSilver
- Tagged HTML
- Tagged SGML
- Tagged XML
- Tagged XML v2
- Visual XML
- Windows Resources
- Word 2000-2003
- Word 2007-2016
- XLIFF
- Regular expressions
- System attributes
- Project Management
- Projects
- Project View
- Project settings
- Functions of the Module
- Project Search
- Project creation
- Adding attachements
- Releasing Projects
- Document and Project Updates
- Project status
- Exporting projects
- Importing projects
- Activating/Deactivating Projects
- Duplicating Projects
- Archiving Projects
- Change workflow
- Changing Workflows (Several Documents)
- Documents
- Reports
- Tasks
- Quality management
- Formats
- The Project Archive
- crossGrid
- Project Management Cockpit
- The Filter Editor
- crossAnalytics
- Linguistic Supply Chain Management (LSCM)
- crossWAN Project Management
- Partitioning
- Relay Translations
- Document preparation
- Term Extraction and Term Translation
- External Editing of Documents
- The EN 15038 Standard Workflow
- The ISO 17100 Standard Workflow
- crossConnect for External Editing
- Finishing pre-translated tasks automatically
- Projects
- Task Processing
- Working in crossDesk
- Paragraph States
- Empty Paragraphs
- Modes
- Customizing crossDesk
- Tasks in Across
- Comments
- Bookmarks
- Paragraph Numbering
- Sorting Paragraphs
- Context View/Source View
- crossTerm Window in crossDesk
- crossView
- Fuzzy search
- Concordance search
- crossSearch
- Spell-check and User Dictionary
- Pre-translations
- Store Translations Wizard
- The Target Editor
- Preview
- QM Check in crossDesk
- Search and Replace
- Correction
- Reviews
- Redelegation to the Translator
- Quick Translate
- Local Data in the Offline Client
- crossWAN
- TM Management
- Terminology Management
- Concept-Oriented Terminology System
- Definitions
- The crossTerm Manager
- crossTerm settings
- crossTerm Manager User Interface
- Searching for Entries/Terms
- Entry and term elements
- Editing Entries/Terms
- Delete Entries/Term(s)
- Merging Entries
- Duplicating Entries
- Manual correction
- crossTerm Reports
- crossTerm Import
- crossTerm Export
- crossTerm Data Maintenance
- crossTerm Web
- crossMining
- crossSearch
- Browser-based Work
- Editing of Special Formats
- Menus, Icons, and Keyboard Shortcuts
Preparations for the CSV Import
The import of a CSV file is the most complex import variant. To minimize your change workload in crossTerm, there are a number of things you can do prior to the import.
First of all, it would be good for the import data (i.e. the column headers of the CSV file) to match the names of the data categories in the crossTerm instance.
- Basic rules:
- Every data category must have a separate column.
- Every sublanguage requires a separate column.
- You can map the columns of the CSV file to terms by means of their designation.
Example
If the CSV file contains several terms for an entry in different rows, I would recommend inserting a column with numbers. Simply enter a number for every entry (no matter what number). So if an entry with term X has the number 1215, give the additional row with the associated term the number 1215 as well.
The column names in the CSV file will determine the mapping that crossTerm will perform during the import. Here an example:
If you arrange your CSV file as shown above, crossTerm will detect the language during the import, but not the type of information. This means that you will have to do a lot of additional work in the Import Wizard and map an information type (e.g. term, data category, picklist) to the columns.
But if you select column headers like here ...
… Across will immediately recognize the type of information they contain:
Influencing factors
Overview of all factors that influence the term import via CSV:
Designation in CSV column | Explanation |
Language code in parentheses | (EN) will be identified as English with the standard sub-language. |
ConceptDefinition(DE) | Will be identified as entry definition, i.e. definition at entry level in German. |
Term(DE) | Will be identified as a German term entry. |
TermDefinition | Will be identified as term definition, i.e. definition at term level. |
[C:ATT]XY | Will be identified as picklist at entry level. C stands for Concept (entry). |
[T:ATT]XY | Will be identified as picklist at term level. T stands for Term. |
[C:TXT] [T:TXT] | Will be identified as text field at entry or term level. |
[T:ATT]Status(DE) | Will be identified as term status (released/not released) |
# | Entry ID (if the number is the same, the terms will automatically be associated with each other). |
Prior to the import, consider what kind of information you have already created in your instance or would still like to add, and name the columns of your CSV file accordingly.