Differences

This shows you the differences between two versions of the page.

--- jvx:server:storage:metadata [2018/02/02 09:22]
admin created
+++ jvx:server:storage:metadata [2020/06/26 13:21] (current)
cduncan Edited for English grammar (capitalization, punctuation, correct verb conjugation)
@@ Line 1: / Line 1: @@
-~~Title: Userdefined ColumnMetaData and ColumnDefinition~~
+~~Title: User-Defined ColumnMetaData and ColumnDefinition~~
-MetaData are an important element of JVx' model. Every column, used in DataBook or Editor has a ColumnDefinition internally. This controls which Editor will be used (Date, Text, Number, Selection, ...), the datatype of the column, how many characters can be entered, etc. A ColumnDefinition is created from Metadata. The Metadata are generated on server-side.
+Metadata are an important element of JVx' model. Every column used in DataBook or Editor has a ColumnDefinition internally. This controls which editor will be used (date, text, number, selection, etc.), the datatype of the column, how many characters can be entered, and the like. A ColumnDefinition is created from metadata. The metadata are generated on server side.
-In simplest case, the metadata are read from the database, if a database is used. The metadata creation is done automatically and, usually, requires no changes.
+In the simplest case, the metadata are read from the database, if a database is used. The metadata creation is done automatically and usually requires no changes.
-However, it may be necessary in certain situations to adapt the standard mechanism to your own needs, e.g. add additional information, define standard values with your own algorithm or set specific labels.
+However, it may be necessary in certain situations to adapt the standard mechanism to your own needs, e.g., add additional information, define standard values with your own algorithm, or set specific labels.
 Working with your own metadata means that you understand the default behavior:
@@ Line 11: / Line 11: @@
 The class DBAccess is responsible for creating metadata from database tables and views. It also enables you to change default metadata creation and to implement your own requirements.
-DBAccess is a server-side class. The metadata thus generated are transferred to the client as needed and the model takes care of the conversion.
+DBAccess is a server-side class. The metadata thus generated are transferred to the client as needed, and the model takes care of the conversion.
 The creation of custom metadata is explained by the following example.
@@ Line 63: / Line 63: @@
 As can be seen already, both classes are linked. The class ColumnMetaData creates a new instance of ColumnDefinition.
-In **2. step**, we're going to configure a DBAccess object. It should use our new classes:
+In **Step 2*, we're going to configure a DBAccess object. It should use our new classes:
 <file java>
@@ Line 87: / Line 87: @@
 </file>
-We have to implement the interface IColumnMetaDataCreator and simply return our own class. We set the new columnInfo before we return the object.
+We have to implement the interface IColumnMetaDataCreator and simply return our own class. We set the new ColumnInfo before we return the object.
-From now on, all metadata instance are created using the ''ColumnMetaDataCreator''.
+From now on all metadata instance are created using the ''ColumnMetaDataCreator''.
-The newly created MyColumnMetaData instance is transferred to the client as usual. The model continues to generate automatically our MyColumnDefinition instance, via createColumnDefinition. No more further actions needed.
+The newly created MyColumnMetaData instance is transferred to the client as usual. The model continues to generate automatically our MyColumnDefinition instance via createColumnDefinition. No further action needed.