Export | eptos Dictionary Documentation

Overview

Dictionary Manager includes several export types, implemented for various types of structure elements, which allow extracting data from the database within different file formats.

/*<![CDATA[*/ div.rbtoc1770892091554 {padding: 0px;} div.rbtoc1770892091554 ul {list-style: disc;margin-left: 0px;} div.rbtoc1770892091554 li {margin-left: 0px;padding-left: 0px;} /*]]>*/ Overview DIN 4002 OntoML Release updates (CSV) Transaction update files (TUF)

DIN 4002

This export allows users to export dictionary structure elements in DIN 4002 format. The following table explains the export options available in the graphical user interface. Mandatory fields for the export are marked with an asterisk.

Through a redesign of the eptos export pages, the external appearance of the exports has now been fully adapted to the defined Usability Guidelines.

This has significantly improved the look and feel of these pages.

In a harmonized DIN 4002 Export dialog the user can save and load favorite dialog settings in tab “Selection of attributes” to access those settings faster instead of selecting them again for each new export.

Tab	Option	Description
General	Entity type	Allows users to select the Structure Element type to be exported.
General	Split file into chunks	Allows user to decide via check-box whether the file should be exported in one complete file or separated in more, smaller files.
General	Release	Allows users to select from which release to export the Structure Elements selected in the Entity type field.
General	Table result renderer	Allows users to select the export format (xlsx, csv).
General	Export languages	Contains list of all available content languages, including check-box for selection. As soon as box is checked, respective language is added in the Export languages field, including option for removal.
General	To:	Allows users to input the e-mail address where the exported file will be sent.
General	CC:	Allows users to input the e-mail address where a carbon copy of the exported file will be sent.
Selection of attributes	Export attributes	Allows users to select from a set of predefined Attributes the ones which will be included in the export by selecting the needed columns which are displayed by column name and column code. user also has the possibility to select the export languages. Note: Attribute IEC Classification, which is optional and not language specific, may also be included in XLSX export.

OntoML

This export allows users to export dictionary structure elements in OntoML format. The following table explains the export options available in the graphical user interface. Mandatory fields for the export are marked with an asterisk.

Tab	Option	Description
Data Source	OntoML version	Allows users to select version of the exported file. Available versions are: eptosXML 1.0 ECLASSXML 3.1 PFC XML
Data Source	Select the export release	Allows users to select the Release contained in the exported file.
Data Source	OntoML export type	Allows users to select OntoML export type - Advanced or Basic.
Data Source	Description	Description of the exported file. The field is prefilled with the information from OntoML version and OntoML export type.
Data Source	Revision	Revision information of the exported file; The field is pre-filled with 1.0.
Data Source	Creator name	Name of the export file creator
Data Source	Creator email	E-mail of the export file creator
Data Source	Authorization	Name of person authorized to do the export. The field is pre-filled with the name of the user starting the export.
Data Source	Authorization e-mail	E-Mail of person authorized to do the export. The field is pre-filled with the e-mail of the user starting the export.
Data Source	Originating system	Name of the system from which the export is performed
Data Source	Originating system URL	URL of the system from which the export is performed
Data Source	Organization	Organization of the user starting the export
Data Source	Selector - All / Selection from hierarchy	Allows users to define the content of the export. The following options are available: All: all elements of selected release will be exported Selection from hierarchy: only elements selected in the hierarchy and added to the list of selected elements will be exported
Data Source	Send results by e-mail	Allows user to define if exported file will be sent by e-mail or downloaded directly.
Data Source	Attachment name	Name of the exported file
Data Source	To: / CC:	Allows users to input the e-mail address where the exported file will be sent.
Extras	Languages	Allows users to define in which languages the content will be exported. The following options are available: All: the export will be performed in all content languages active in the system Language: the export will be done in the content language(s) selected from the list of active languages
Extras	Export all classes (unchecked=only classification class understructure)	Allows users to define if all Classes (for example Blocks, Aspects, Application Classes having no connection to a Classification Class) will be exported. The default is "not exported" (option unchecked).
Extras	Export restricted (access-control) entities	Allows users to define if Structure Elements restricted via access control will be exported or not. The default is "not exported" (option unchecked).
Extras	Export property values	Allows users to define if the Values of Properties having a Value List will be exported or not. The default is "exported" (option checked).
Extras	Restrict export to used value lists	Allows users to define if only used Value Lists will be exported or also unused Value Lists. The default is "only used Value Lists are exported" (option checked).
Extras	Export connection to secondary classification	Allows users to define if mappings to other classification dictionaries will also be exported. The default is "not exported" (option unchecked).
Extras	Follow classification class - application class connection.	Allows users to define if entire Classification Class sub-structure only Classification Classes (without their sub-structure) is exported. The default is "entire Classification sub-structure" (option checked).
Extras	Ignore deprecated elements in error reports	Allows users to define if deprecated structure elements will be reported or not in the error report. The default is "report deprecated elements in error report" (option unchecked).
Extras	Export one file per selection	Allows users to define if all classes will be exported in one file or in separate files. The default is "one file per selected element" (option checked).
Extras	Stop the export on errors	Allows users to define if the export will be stopped in case errors are encountered. The default is "do not stop export on errors" (option unchecked).
Extras	Template type to apply	Allows users to define if and what type of Template will be applied on export. The following options are available: ---: no Template will be applied Default: default Template will be applied Nondefault: nondefault Template will be applied

Release updates (CSV)

This export allows users to export update information between releases in CSV format. The following table explains the export options available in the graphical user interface. Mandatory fields for the export are marked with an asterisk.

Note: only releases marked with TUF-required and having a predecessor are eligible for the export.

Option	Description
Language	Allows users to define for which content language(s) the release updates will be exported. Select all languages will mark all available content languages to be considered in the export.
Sheet	Allows users to define for which elements release information will be exported. The following options are available: RUF-CC: exports release update information on Classification Classes RUF-PR: exports release update information on Properties RUF-KW-SY: exports release update information on Synonyms and Keywords RUF-VA: exports release update information on Values RUF-UN: exports release update information on Units RUF-CC_PR: exports release update information on Classification Class - Property relations (via the Application Class connected to the Classification Class) RUF_PR_VA: exports release update information on Property - Value relations RUF_TU_CC: exports release update information and transaction update information on Classification Classes RUF_TU_PR: exports release update information and transaction update information on Properties The option Select all sheets will mark all available options to be considered in the export.
Target release	Allows users to define the target release for the release update information. Note: only releases marked with TUF-required and having a predecessor are available for selection.
Incomplete languages	Allows users to define what should be exported in case content is missing in the selected export languages. The following options are available: Export empty: element will be exported as empty in respective language Fill with primary language: element will be exported in the primary language of the system in case translations are missing in one of the other content languages
To: / CC:	Allows users to input the e-mail address where the exported file will be sent.

Transaction update files (TUF)

Tab	Option	Description
Data Source	Export format	Allows users to select version of the exported file. Available versions are ECLASSXML1.0, ECLASSXML2.0 ECLASSXML3.0 and Transformation plan.
Data Source	Application class type	Allows users to select the AC type Basic or Advanced.
Data Source	Target release	Allows users to select the Release desired to be compared.
Data Source	Previous release	Will be set automatically in accordance with field "Target release "
Data Source	Creator name	Name of the export file creator
Data Source	Creator email	E-mail of the export file creator
Data Source	Authorization	Name of person authorized to do the export. The field is pre-filled with the name of the user starting the export.
Data Source	Authorization e-mail	E-Mail of person authorized to do the export. The field is pre-filled with the e-mail of the user starting the export.
Data Source	Description	Short description of needed export.
Data Source	Originating system	Name of the system from which the export is performed
Data Source	Originating system URL	URL of the system from which the export is performed
Data Source	Email to	Allows users to input the e-mail address where the exported file will be sent.
Extras	Language	Allows users to define in which languages the content will be exported. The following options are available: Language: the export will be done in the content language(s) selected from the list of active languages
Extras	Export preferred names	- exports the name of the mapped structure elements as XML comment - it's helpful in some cases, set to ON or OFF based on personal preference
Extras	Export paths consisting solely of VER commands	-only mappings where the path contains versioned elements are exported - should stay OFF for normal exports. By default, the exporter will only export mappings whose changes contained a replace / move / similar change request. If all the elements in the source paths have only been versioned (so there were no more complex CRs) they will not be exported. By checking this flag, you will also get the mappings whose source elements only contained versioning. This means the source and target paths will be the same, only element versions will differ.
Extras	Export elements deprecated on source	-exports mappings where the source path is deprecated - should stay OFF for normal exports. It was added to have a possibility to compare with old exports If any of the source elements is deprecated, the exporter will not export the mapping as the source should not be relevant anymore (as it's deprecated). By checking this flag, paths with deprecated source will also get exported.

Note: Description behavior of TUF changes in case of Classification Classes:

when changes occur in an Application Class that is NOT PART of any Classification Class changes like SPLIT / JOIN / MOVE, then the TUF contains Property paths for equivalences accordingly.

Classification Class source / Application Class source / propsrc1/ propsrc2 → Classification Class target(version+1) / Application Class target (version+1) / proptrg1/ proptrg2.

For MOVE the Classification Class itself is versioned. The Application Class is not versioned on MOVE. If a new version of Application Class appears this would be because of changes that occur directly in Application Class.

SPLIT Classification Class / JOIN Classification Class = Classification Class source/Application Class source / propsrc1/ propsrc2 → Classification Class target( completely diff)/ Application Class target ( completely diff) / proptrg1/ proptrg2

MOVE Classification Class = Classification Class source/Application Class source / propsrc1/ propsrc2 → Classification Class target( version+1)/ Application Class target (version + 1 if changes inside Application Class, or same Application Class in case of no changes) / proptrg1/ proptrg2

The TUF doesn’t contain entries dedicated to Classification Class changes (such as coded name based entries). It contains only property path entries (no entries in code_to_code only in path_to_path)

The RUF is the place where some sheets are dedicated to Classification Class operations.