Date: Thu, 28 Mar 2024 23:43:04 -0500 (CDT) Message-ID: <1334299321.1480.1711687384144@wiki.ncsa.illinois.edu> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1479_1514104812.1711687384143" ------=_Part_1479_1514104812.1711687384143 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
To create a new dataset schema, the following steps must be taken:
maeviz-bridgeDa=
mage_1.0.xsd
in the ncsa.maeviz plugin for an example. As in the exa=
mple, the field names must be prefixed with "maeviz." Also, the main part o=
f the field name (after the maeviz prefix) must be 10 characters or less. T=
he primitive type of the field (double, string, etc) must also be correctly=
specified.n=
csa.gis.gisSchemas
must be extended to define the schema.=20
field |
description |
---|---|
id |
The id of the schema |
name |
A friendly name for the schema |
version |
A version identifier for the schema. |
type |
A short type name for the schema |
description |
A user-friendly description of the schema = |
file |
The schema file defined in the previous step<= /p> |
format |
The format of the schema. Predefined formats =
include: |
requiredFields |
The list of fields that are required as a min= imum for this schema. These will be prompted to map to during ingestion = |
mapLayer |
For shapefiles, the suggested smart layering = position in the map. Should be between 1 and 100, where lower numbers appea= r above lower numbers. A mapLayer of -1 indicates that the dataset should b= e invisible by default |
category |
A category name for the schema. Categories de= termine what subfolders the schemas appear in the repository view. |
gisMetadata
that sits parallel to the g=
isSchemas
folder. Files in here should have the same name as their c=
orresponding schema xsd file, except with xsd renamed to xml. Each field sh=
ould be defined using a column-metadata
element with the follo=
wing attributes:=20
attribute |
description |
required? |
---|---|---|
column-id |
The id to match the column id from the xsd fi=
le. Should not include the |
Y |
friendly-name |
A friendly name for the field |
|
is-numeric |
An indicator of whether this field should be = displayed as a numeric value (for example, some schemas have string fields = that should be interpreted as numbers |
|
unit |
The default units of this field. This abbrevi=
ation should come from a unit tag defined in the |
|
field-length |
The length of the field. This should be as sm= all as possible without truncating data |
|
importance |
The importance of the field. Values are |
|
is-result |
This should be defined if the field is a new = result value for this schema |
|
agg-type |
If the field is aggregated in a view or table=
, what type of aggregation makes the most sense for this field. Values are =
|
|