DE102021126062A1 - Method and system for converting data from a source file format to a target file format - Google Patents

Abstract

The invention relates to a method and a system for converting a source file (DU) in a source file format (DFU) into a target file (DZ) in a target file format (DFZ). The original file (DU) is first converted into an input transfer file (TNE). The input transfer file (TNE) has a specified transfer file format (TF) and has several transfer data fields (TX) for the user data. A model (28), which has at least one property (30), is used to map the user data in the input transfer file (TNE). The model (28) provides at least one modifiable link (31) between each property (30) and an associated transfer data field (TX) of the input transfer file (TNE). Based on the model (28) and the input transfer file (TNE) and the at least one link (31), a view (32) is generated for the user (14). Based on this view (32), the user (14) can have a appropriate user interface (16) make changes to the model (28). The changes are updated in the view (32) and an output transfer file (TNA) can then be generated based thereon, which has the same transfer file format (TF) as the input transfer file (TNE). Finally, the source transfer file (TNA) can be converted into the target file (DZ).

Description

The invention relates to a method and a system for converting data from a source file format into a target file format. Such methods and systems are known in different variants. When converting data, the mapping or assignment of the content in the original file format to the content in the target file format (mapping) plays an important role. The problem here is the large number of possible file formats that are available in information technology. A large number of conversion methods are therefore required in order to be able to convert user data from an original file format into all desired target file formats, with the user data having to be mapped correctly (mapping).

EP 2 648 115 A1 describes a method and a system for performing a conversion of hierarchically structured data and relational data. For this purpose, a conversion method or transformation method must be provided for each pair of a source file format and a target file format. This represents a significant effort to accommodate multiple file formats for the source file and the target file. For example, if something changes in a single file format, all conversion processes in all available target file formats must be changed and adjusted. The effort involved in updating such a method or system is enormous and cannot be afforded for a larger number of source file formats and target file formats.

This also applies to the off U.S. 2003/0217069 A1 known method, in which a mapping must also be created for each pair of exactly one source file format and exactly one target file format.

Proceeding from this, it can be regarded as the object of the present invention to create an efficient method and a system for converting data from a source file format, which is also particularly suitable for a plurality of file formats for the source file format and the target file format.

This object is achieved by a method having the features of patent claim 1 and a system having the features of patent claim 13 .

The method according to the invention and the system according to the invention are used to convert data that is in an original file format into a target file format. Such data conversion may be necessary to enable error-free communication across company boundaries. Such communication can enable an exchange of data in different areas of application, for example the exchange of documents as part of an order initiation and the subsequent order processing between two or more companies. Since companies often use different file formats or require different preparation of the user data contained for their respective company-internal processing, error-free communication can be established with the method according to the invention for converting the data, which can be automated. The method according to the invention can be provided as a web-based service that users can access via the Internet.

First of all, the original file is provided in the original file format, for example by transmission of the original file from a user processing unit of the user to the system according to the invention, in particular via the Internet. The original file contains original data (useful data) that are to be converted at least partially or completely depending on the user and/or the target file format. The original file format can be selected from a group of several possible file formats. The method is not set up or limited to converting from exactly one file format to exactly another file format, but rather is set up so that the target file format can be selected from the group of available file formats. The source file format can be one of the available file formats from this group.

A suitable method or service is used to transfer some or all of the original data from the original file to a number of transfer data fields in an input transfer file. The input transfer file is defined and has a default transfer file format that differs from the source file format and the target file format. The transfer file format is thus a standardized processing of the user data to be converted that is provided for the method.

In particular, the original data is transferred into the transfer data fields of the input transfer file without any intervention. In this step, there is no analysis, verification, completion or similar of the original data. The original data to be used are transferred to the transfer file format according to a specified input transfer rule. The input transmission specification can be adapted to any original file format and an individual one can be created for each of the possible file formats Input transfer rule specified or stored. The entry transfer rule cannot be changed individually by the user of the method.

The transfer of the original data into the input transfer file can be carried out using a data interchange service (EDI), for example.

Adapted to the original file format and/or the target file format, a model is provided which, for example, is used from a plurality of available models based on the original file format and/or the target file format for the method. The model used depends on the area of application and differs, for example, depending on whether text files or CAD files or other types of files are to be converted. The model has at least one property. Each defined property of the model represents metadata for the user data to be converted. The model can be used in particular to structure the user data present in the input transfer file by assigning them to the properties (metadata).

The model can be an entity relationship model. In one embodiment, the model includes at least one object having at least one object property, each object property being a property of the model.

According to the invention, an unambiguous link between at least one property and preferably all existing properties and one of the transfer data fields of the input transfer file is produced in a transformation process. As part of this transformation process, the user data in the transfer data fields of the input transfer file are therefore assigned to the properties (metadata) of the model and thus structured.

A model file or model data is generated based on the model and the input transfer file. The model file is or the model data are defined by all properties of the model that have a link and the associated user data of the transfer data field of the input transfer file linked thereto. In this sense, the generation of the model data includes the compilation and structuring of available user data of the input transfer file.

A view is made available to the user via a respective user interface, which view represents at least part of the model data. In particular, the user can make a selection as to which model data, ie which properties of the model are to be displayed with the associated user data. The view is displayed to the user by means of a respective user interface. For example, the view can have text and graphic elements representing the link, for example in the form of tables or other clearly prepared representations. The view generated is independent of the file format and in particular independent of the original file format, the target file format and the transfer file format. The view presents the user data and the associated metadata (properties of the model) in a form that is also understandable to users without programming language skills. This means that even a user who is not familiar with the file formats can check the assignment of the user data to the properties (metadata).

In the view, the user is given the opportunity to change the model data, for example to correct the assignment of the user data to the properties (metadata) or to add user data and/or properties, to change a display format or to remove user data and/or properties. For example, the user can use the view and the user interface to reassign the illustrated relationship between a property and the user data associated with it. To do this, he can - for example with a drag-and-drop function - detach the user data of a transfer data field from the previously assigned property and assign it to another property or analogously to this detach a property from the previously assigned transfer data field (represented by the user data contained) and a assign to another transfer data field (represented by the user data it contains). To do this, he can use any input means, for example a touch-sensitive screen or another pointing device of the user interface. For example, instead of or in addition to a drag-and-drop function, the ends of a vector or other connection representing the link can be moved and repositioned so that the association of a property with a transfer data field can be changed. This gives the user an easy way to check the assignment of the user data of the original file to predefined properties (metadata) in particular and, if necessary, to correct or complete them, to include required user data in the model data or to remove user data that is not required from the model data ( e.g. by deleting a link).

An output transfer file is then generated in the transfer file format, i.e. the same same file format as the input transfer file. The output transfer file is generated based on the model data. For this purpose, for example, the user data in the transfer data fields of the input transfer file can first be copied into the transfer data fields of the output transfer file. The model, in particular the links with its properties, can then be applied to the output transfer file in a further transformation process, so that the content in the transfer data fields of the output transfer file maps the model data. For example, the user data can be arranged in the transfer data fields of the initial transfer file in such a way that the initial transfer file contains the properties of the model from the model data defined using the link in the form of metadata of the initial transfer file.

Finally, the user data of the transfer data fields of the source transfer file are transferred to the target file. For this transfer, an initial transfer rule can be specified or stored, which is adapted to the target file format. The user data of the output transfer file can be transferred to the target file using a data exchange service (EDI), for example.

The adaptation effort for the user is reduced considerably by means of the method according to the invention. If a file format changes or an additional file format is added, the adaptation to this changed or new file format must be made exclusively with regard to the transfer file format of the input transfer file or the output transfer file. There is no need to adapt to a number n of other file formats for which convertibility is to be provided. When changing or adding a file format, the effort no longer increases exponentially, as was previously the case.

It is advantageous if each link between one of the properties of the model and one of the transfer data fields of the input transfer file can be set individually for each user. Each user can set one or more of the existing links based on certain user-specific conditions individually, for example deviating from a standard or a majority of the other users. This can be done via the relevant user's user interface. This allows user-specific individual models to be generated for the conversion.

It is preferred if the completion and/or correction of useful data is made possible when the model data is created. The user data can be corrected or completed automatically and/or by the user via the user interface. If user data is automatically corrected or completed, a confirmation from the user can optionally be requested or the user can at least be informed of the change in the user data. For example, if a zip code is missing, an automatic determination based on the location and possibly the street name and possibly the house number can be determined and used to generate the output transfer file if a zip code is required in the target file format. Another example can be customizing phone number formats with or without an international prefix, depending on what the target file format requires. If automatic correction or completion is not possible, this can be indicated to the user, who can then complete or correct the user data.

It is also advantageous if the initial transfer file is initially generated based on a standard model that is available to all users. This standard model is used until the user in question creates a different individual model with individual links (property to user data).

In particular, the method is made available to a plurality of users. It is therefore possible to design the method in a learning manner and, for example, to adapt the standard link based on the extent to which the users set their individual models and links differently from the standard model. The standard model can thus be updated or adapted according to the wishes and specifications of the user, so that it provides an already largely adapted assignment of the user data to the properties (metadata) of the standard model for a large number of users.

In particular, the standard model depends on both the source file format and the target file format. The standard model is therefore dependent on the area of application and differs, for example, depending on whether text files or CAD files are to be converted.

As already explained, an individual input transfer specification can be present and used for each original file format and an individual output transfer specification can be present and used for each output file format. The input transfer rule and the output Transmission instructions can be identical if the user data is to be transmitted between the same file format and the transfer file format.

The invention also relates to a system that can be set up to carry out the method according to one of the above exemplary embodiments. The system includes a central data store and a central server communicatively coupled to the central data store. The central data store is set up in particular to store or temporarily store data, for example the original file and the target file. The central server communicates with one or more user computing units via an Internet connection. The server can initiate or execute the implementation of the method according to the invention by the request of a user, which can be triggered by means of the user processing unit. He can carry out the steps necessary for this together with the central data storage facility and, if necessary, an external processing unit which he can access via the Internet connection.

• 1 ein Blockschaltbild eines Ausführungsbeispiels eines erfindungsgemäßen Systems zur Durchführung eines Ausführungsbeispiels eines erfindungsgemäßen Verfahrens,
• 2 ein Blockschaltbild unterschiedlicher Schichten in einer Zentraleinheit des Systems aus 1,
• 3 ein Blockschaltbild einer Codierschicht aus 2,
• 4 ein Blockschaltbild einer Prozessschicht und einer Anwendungsschicht aus 2,
• 5 eine schematische Darstellung eines beispielhaften Ausführungsbeispiels eines Modells zur Erzeugung von Modelldaten und einer Ansicht für einen Anwender,
• 6 eine Darstellung eines beispielhaften Objekts eines Modells aus 5 und die dazugehörige Ansicht für den Anwender,
• 7 eine beispielhafte Darstellung einer Eingangstransferdatei oder Ausgangstransferdatei in einem beispielhaften Transferdateiformat und
• 8 eine beispielhafte Darstellung einer dateiformatunabhängigen Ansicht, die basierend auf einem individuellen Modell und einer Eingangstransferdatei erzeugt werden kann.

Further advantageous configurations of the invention result from the dependent claims, the description and the drawings. Preferred exemplary embodiments of the invention are explained in detail below with reference to the attached drawings. In the drawings show:

• 1 a block diagram of an exemplary embodiment of a system according to the invention for carrying out an exemplary embodiment of a method according to the invention,
• 2 a block diagram of different layers in a central unit of the system 1 ,
• 3 a block diagram of a coding layer 2 ,
• 4 a block diagram of a process layer and an application layer 2 ,
• 5 a schematic representation of an exemplary embodiment of a model for generating model data and a view for a user,
• 6 a representation of an example object of a model 5 and the corresponding view for the user,
• 7 an exemplary representation of an input transfer file or output transfer file in an exemplary transfer file format and
• 8th an example representation of a file format independent view that can be generated based on an individual model and an input transfer file.

In 1 Illustrated is a system 10 that provides a web-based data conversion service over the Internet 11 . The system 10 is set up to convert a method for converting a source file DU, which is in a source file format DFU, into a target file DZ, a target file format DFZ being specified for the target file DZ. Both the source file format DFU and the target file format DFZ can be selected from a predefined group of possible file formats DFi (1=1, 2, 3,..., n). The system 10 has a central unit 12 which can communicate with one or more user computers 13 of a respective user 14 . The system 10 can be formed exclusively by the central unit 12 or, alternatively, can have distributed computing capacities or services. At the in 1 In the exemplary embodiment shown, the system 10 can optionally include an external computing unit 15 that takes over specific tasks or steps within the conversion process. The external processing unit 15 can provide a data transmission service (EDI) for the method, for example. The service, which is optionally provided via an external computing unit 15, can alternatively also be performed via the central unit 12.

The central unit 12 of the system 10 has a central server 17 and a central memory 18 which is communicatively connected to the central server 17 . The central server 17 can store or change data in a write access in the central memory 18 and can read data out of the central memory 18 in a read access.

Each user computer 13 has a user interface 16 in order to display information to the respective user 14 and to enable user 14 to make entries. The user interface 16 is an input and output interface and can be implemented in any known manner, as is usual with computers or terminals. In particular, it has a screen and an input device (e.g. pointing device, touch-sensitive screen). The user computer 13 can be a mobile terminal or a non-mobile terminal (e.g. PC).

In 2 a layered model of the system 10 is schematically illustrated. When converting the source file DU into the target file DZ, you can choose between the selectable file formats DFi (i=1 to n) are carried out. The system 10 is dynamically expandable and the set of available DFi file formats is not complete. Like it 2 illustrated, the system 10 is divided into a coding layer 25 , a process layer 26 and an application layer 27 in the exemplary embodiment. The process layer 26 is arranged in the data flow or communication flow between the coding layer 25 and the application layer 27 . The source file DU is provided to the coding layer 25 for decoding and the target file DZ is coded and output via the coding layer.

The coding layer 25 works, for example, without the intervention of the user 14. The users 14 are integrated into the conversion method according to the invention via the application layer 27 and can use inputs to change the process flow and, in particular, the models 28 ( 5 ) influence. The mapping of the user data takes place based on the at least one model 28 essentially in the process layer 26 .

The coding layer 25 is in 3 illustrated. In the coding layer 25, during the conversion method according to the invention, user data is transmitted in the original file format DFU into a predefined transfer file format TF and from the transfer data format TF into the target file format DFZ. For this purpose, an electronic data exchange (Electronic Data Interchange, EDI) is used, which can be provided by the central unit 12 or an external computing unit 15 . For data exchange, there is a transfer rule to and from the TF transfer file format for every possible DFi file format. The transmission specification assigned to each possible file format DFi can be used both as an input transmission specification VE or as an output transmission specification VA.

The original file DU is converted into an input transfer file TNE in the specified transfer file format TF by means of the input transfer specification VE. An output transfer file TNA, which is in the transfer file format TF, is converted into the target file format DFZ by means of the output transfer specification VA. The user data of the original file DU are preferably transferred completely to the input transfer file TNE. The user data contained in the output transfer file TNA are preferably transferred completely to the target file DZ. However, only part of the user data can also be taken over during conversion using the input transmission specification VE and/or the output transmission specification VA, depending on which user data is required in the target file format DFZ.

In 4 the process layer 26 and the application layer 27 are shown. The process layer 26 is provided with the input transfer file TNE from the coding layer 25 . The process layer 26 provides the output transfer file TNA for the coding layer 25 . A model 28 having at least one object 29 is provided in the process layer 26 .

The model 28 is provided adapted to the respective area of application or the type of user data to be converted. For example, a model 28 can be selected and used from a plurality of available models 28 for converting the original file DU into the target file DZ. The model 28 is adapted to the respective area of application or use case. For example, a model may exist to convert text files. For example, one or more other models may be present to convert CAD files. The method and system 10 according to the invention can be adapted or expanded to different areas of application.

The model has at least one property 30, which is an object property of the at least one object 29, for example. The properties 30 of a model 28 or object 29 can be structured hierarchically, as exemplified in 6 for the object 29 “address” is illustrated. The object 29 "Address" has, for example, the properties 30 "City", "Street" and "Post code (ZIP)". The property 30 “Street” is in turn subordinate to several properties 30, for example “Street name” and “House number”. Such objects 29 can have any complex structure. The number of properties 30 and their hierarchical grouping is adapted to the application of the conversion and can in principle be defined arbitrarily. The in the 5 and 6 Objects 29 shown are merely examples and are only used for schematic illustration. The number of objects 29 in a model can vary as desired.

Based on the model 28, model data MD, which can also be referred to as a model file, are generated from the input transfer file TNE in a transformation process PE. The model data MD can in particular have a structured selection of user data contained in the input transfer file TNE. The model data MD are formed by at least one modifiable link 31 between one, several or all properties 30 of the model 28 (here: object properties of the objects 29) and each an associated transfer data field TX of the input transfer file TNE. The link 31 between a property 30 and a transfer data field TX can be based on a standard link 31s of a standard model 28s, as is only an example in 6 is shown. Each user 14 can create an individual model 28i with at least one individual link 31i that differs from the standard model 28s or the standard link 31s (example in 5 shown). The user 14 can change a start and/or end point of an existing link 31 to create an individual link 31i, delete an existing link 31 or create an additional individual link 31i. The individual model 28i with the at least one individual link 31i can be created individually for each user 14 of the system 10 or the method according to the invention, stored and made available for retrieval.

The model data MD depict the linking of the properties 30 with the transfer data fields TX of the input transfer file TNE. The user 14 has the option of having part of the model data MD or the entire model data MD displayed in a view 32 via the respective user interface 16 of the user processing unit 13 . The user 14 can use the view 32 to check the model 28—and in particular its links 31—and change it if necessary.

The view 32, which at least partially reproduces the model data MD, is independent of the file format. To assess whether the model 28 or the links 31 is or are complete and correct, no knowledge of a programming language, the DFi file format or the TF transfer file format is required. The user data is displayed to the user 14 in a clear representation, for example in the form of a list, table, graphic, etc. The view 32 can allow entries. For example, this view 32 can be associated with the “address” object, as exemplified in 6 is shown, display the properties 30 “Street name” and “House number” in the “Street” view field and display the “Location” object property of the “Address” object in the “Location” view field.

The view 32 in 6 is only an example and is limited here to the object 29 “address” of the model 28. In addition or as an alternative, other properties 30 or object properties can also be transferred to the view 32 and displayed for checking or correction. For example, the user 14 can select the view 32 from all available properties 30 of the relevant model 28 in a selection menu with checkboxes or similar selection elements.

An individual model 28s is created with the help of view 32 and in particular by an input and change in view 32, which is exemplified by view 32 in 8th is explained. The view 32 contains metadata, each of which corresponds to a property 30 of the model, here, for example, “name”, “city”, “street”, “house number”, “customer number” and “order number”. The user data from the input transfer file TNE are assigned to these properties 30 . The user can change this assignment in view 32, for example by exchanging the view fields “Customer No.” and “Order No.”. As a result, instead of the previous links 31 (eg standard links 31s), individual links 31i are generated for an individual model 28i that differs from the standard model 28s.

If necessary, the model data MD can be changed, corrected or supplemented automatically. An interpreter 33 can be used for this. Interpreter 33 may be part of application layer 27 in one embodiment of system 10 . As an alternative to this, the interpreter 33 could also be a component of the process layer 26 .

By means of the interpreter 33, for example, additional information can be derived from the available useful data. For example, based on the location and possibly the street, a zip code can be determined and added to the model data MD. The interpreter 33 can additionally or alternatively adapt display formats, for example number formats (e.g. thousands separation with comma or point, number of decimal places), telephone number formats (e.g. with or without international area code), etc. The interpreter 33 can additionally or alternatively, for example, also convert amounts into a convert another currency and provide for the view 32 or the model data MD.

The output transfer file TNA is then generated based on the model data MD. The output transfer file TNA thus maps the at least one link 31 selected by the user 14 between the at least one object 29 of the model 28 and the transfer data fields TX of the input transfer file TNE. The output transfer file TNA is generated in a further transformation process PA in the process layer 26 ( 4 ) and then provided to the coding layer 25 ( 3 ). As described, the target file DZ can then be generated from the output transfer file TNA.

Each user 14 can have a source file DU converted into a target file DZ in the desired target file format DFZ. In this conversion, the TF transfer file format is used for internal processing. This has the advantage that newly added file formats or a change in an existing file format only has to be supplemented or adapted in the coding layer 25 compared to the transfer file format TF. It is not necessary to implement this change compared to all other file formats, in contrast to conversion methods that only directly convert exactly one source file format into exactly one target file format. In addition, each user 14 can make individual settings for the links 31, so that not only does a standard conversion take place, but individual settings are also possible. The check, correction or modification during the conversion can be carried out without programming knowledge, because the view 32 for the user 14 takes place in a form that is independent of the file format. Via the respective user interface 16, the user 14 can very easily carry out corrections using standard input methods, for example “drag and drop”.

The invention relates to a method and a system for converting a source file DU in a source file format DFU into a target file DZ in a target file format DFZ. The original file DU is first converted into an input transfer file TNE. The input transfer file TNE has a specified transfer file format TF and has a number of transfer data fields TX for the user data. A model 28 with at least one property 30 is used to map the user data in the input transfer file TNE. The model 28 provides at least one changeable link 31 between the at least one object property 30 and an associated transfer data field TX of the input transfer file TNE. Based on the model 28 and the input transfer file TNE as well as the at least one link 31, model data MD are formed, which can be displayed at least partially in a view 32 for the user 14. In this view 32, the user 14 can, if necessary, make changes to the model data MD and in particular to the at least one link 31 via a suitable user interface 16. The changes are updated in the model data MD and the view 32, and an output transfer file TNA can then be generated based thereon, which has the same transfer file format TF as the input transfer file TNE. Finally, the output transfer file TNA can be converted into the target file DZ.

reference list

10

system

11

internet connection

12

central unit

13

user calculator

14

user

15

external processing unit

16

user interface

17

central server

18

central storage

25

coding layer

26

process layer

27

application layer

28

Model

28i

individual model

28s

standard model

29

object

30

Characteristic

31

shortcut

31i

individual link of the user

31s

Standard link of the standard model

32

Opinion

33

Interpreter

YOU

source file

DFi

File format (i=1 to n)

DFU

source file format

DFZ

target file format

double room

target file

md

model data

PA

transformation process

PE

transformation process

tf

transfer file format

TNA

Output transfer file

TNE

input transfer file

TX

transfer data field

v.a

exit transfer rule

PU

input transfer rule

QUOTES INCLUDED IN DESCRIPTION

This list of documents cited by the applicant was generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Patent Literature Cited

• EP 2648115 A1 [0002]
• US20030217069A1 [0003]

Claims (13)

Method for converting data that is in a source file format (DFU) into a target file format (DFZ), the method comprising the following steps: - providing a source file (DU) in a source file format (DFU), which has the source data, the source file format (DFU) corresponding to one of several possible file formats (DF1, DF2, ..., DFn), - Generating an input transfer file (TNE) in a specified transfer file format (TF) with several transfer data fields (TX) containing some or all of the original data, - Providing a model (28) having at least one property (30) and at least one modifiable link (31) between the at least one property (30) of the model (28) and one of the transfer data fields (TX) of the input transfer file (TNE), - Generating model data (MD), having the properties (30) of the model (28), which have a link (31), and the user data of the transfer data field (TX) linked thereto in each case, - Generating a file format-independent view (32) that represents at least part of the model data (MD), the user (14) being provided with the option of changing the model data (MD) in the view (32), - Generation of an output transfer file (TNA) in transfer file format (TF) with several transfer data fields (TX) based on the model data (MD), - Transferring the user data of the transfer data fields (TX) of the output transfer file (TNA) to the target file (DZ) in the target file format (DFZ), which corresponds to one of several possible file formats (DF1, DF2, ..., DFn). procedure after claim 1 , wherein the model (28) has at least one object (29) with at least one object property, each object property being a property (30) of the model (28). procedure after claim 1 or 2 , Each link (31) between one of the properties (30) and one of the transfer data fields (TX) of the input transfer file (TNE) can be set individually for each user (14). Method according to one of the preceding claims, in which the user (14) has the option of selecting the properties (30) of the model (28) contained in the view (32). Method according to one of the preceding claims, in which the user (14) has the option, in the view (32), of an existing link (31) between a displayed property (30) of the model (28) and a transfer data field ( TX) and thereby an individual link (31i) from the property (30) of the model (28) to another transfer data field (TX) and/or from the transfer data field (TX) to another property (30) of the model (28 ) to create. Method according to one of the preceding claims, wherein before the output transfer file (TNA) is generated, useful data can be supplemented and/or changed by the user and/or automatically via a user interface (16). Method according to one of the preceding claims, wherein the generation of an output transfer file (TNA) is based on a standard model (28s) for the user (14) as long as the user (14) does not use a user interface (16) to create a different individual model (28i) created with individual links (31i). procedure after claim 7 , wherein the method is provided for a plurality of users (14) and the standard model (28s) is adapted based on the evaluation of the individual models (28i) of the users (14). Method according to one of the preceding claims, in which the model (28) used is provided as a function of the original file format (DFU) and the target file format (DFZ). Method according to one of the preceding claims, wherein for each original file format (DFU) an individual input transmission specification (VE) for the transmission of several or all original data of the original file (DU) in the several transfer data fields (TX) of the input transfer file (TNE) is specified. Method according to one of the preceding claims, wherein for each target file format (DFZ) an individual output transfer rule (VA) for transferring the content of several or all transfer data fields (TX) of the output transfer file (TNA) to the target file (DZ) is specified. procedure after claim 10 and 11 , with each usable file format (DF1, DF2, ..., DFn) being assigned an individual transfer rule that can be used as an input transfer rule (VE) if the file format in question (DF1, DF2, ..., DFn) has the original file format ( DFU) and which can be used as an initial transfer rule (VA) when the relevant file format (DF1, DF2, ..., DFn) is the target file format (DFZ). System (10) comprising: - a central data memory (18), which is set up to store a source file (DU) and a target file (DZ), - A central server (17) which is communicatively connected to the central data store (18) and which is set up to communicate with a user processing unit (13) via an Internet connection, the system (10) being set up to do the following Steps to perform: - Saving an original file (DU) provided in an original file format (DFU) in the central data memory (18), which has original data, the original file format (DFU) corresponding to one of several possible file formats (DF1, DF2, ..., DFn), - Generating an input transfer file (TNE) in a specified transfer file format with several transfer data fields (TX), which contain some or all of the original data, by means of the central server (17) or an external processing unit (15) connected to it for communication, - Selecting a model (28) stored in the central memory (18) having at least one property (30) and at least one modifiable link (31) between the at least one property (30) of the model (28) and one of the transfer data fields (TX) the input transfer file (TNE), - Generating model data (MD), having the properties (30) of the model (28), which have a link (31), and the user data of the transfer data field (TX) linked thereto in each case, - Generating a file format-independent view (32) using the user processing unit (13), which describes at least part of the model data (MD), the user (14) in the view (32) using the user processing unit (13) the possibility is provided to change the model data (MD), - Generation of an output transfer file (TNA) in transfer file format with several transfer data fields (TX) based on the model data (MD), - Transferring the user data of the transfer data fields (TX) of the output transfer file (TNA) to the target file (DZ) in the target file format (DFZ), which corresponds to one of several possible file formats (DF1, DF2, ..., DFn), by means of the central server ( 17) or the external computing unit (15) connected to it for communication.

Images