When designing Engrafo it was very important to have a way to automate the creation of data catalogs and data usage documentation.
...
| Table of Contents | ||||
|---|---|---|---|---|
|
The overall process for uploading metadata
Metadata load is the core of Engrafo making documentations and data catalogs automated
The process is Upload files → validate files → load files
For the Upload of metadata files, it can be done in 3 ways
Manually. You will have to select the fiole from your computer and upload it manually
Semi-automated. All metadata files placed in wwwroot\uploads_csv\,\ are automatically imported and are ready for validation. Note that the csv-delimiter that is used is the name of the folder. Here it is “,”
Fully-automated. All metadata placed in wwwroot\uploads_CSVAuto\;\ are automatically imported validated and loaded to engrafo. Note that the csv-delimiter that is used is the name of the folder. Here it is “;” There is a check every 5 sec. on new files to import, validate and load. (If validation fails, and error messages on that metadatafile is produced and metadata is not imported)
...
Important when placing metadata in a folder, is that the subfoldername identifies which delimiters that is used:
...
So, if metadata is delimited with a “¤”, then place metadata in uploads_csv\¤\
In the following there is a describtion on how to create a metadata fil for Engrafo. It’s very important to hold the right syntaks.
Generating Data Catalog via .csv load
...
Outputdata_customfelt_name
Outputdata_kategori
Outputdata_database
Outputdata_skema
Outputdata_tabel
Outputdata_kolonne (* can be used if ALL columns are to be loaded)
VIGTIGTImportant
The category hierarchy must already exist before it is possible to load into it
The category elements must be specified with ¤ as a separator, for example: Level1¤Level2¤Level3
The templates specified in [Skabelonnavn] must exist before loading to them is possible
Units specified in [Unitnavn] must exist before loading to them is possible
The fields specified in [Customfelt_text_name] must exist as Custom fields before it is possible to load content into them
The fields specified in [Customfelt_link_name] must exist as Custom Fields before it is possible to load content into them
The fields specified in [Inputdata_customfelt_name] must exist as Custom fields before it is possible to load content into them
The fields specified in [Outputdata_customfelt_name] must exist as Custom fields before it is possible to load content into them
The column specified in [Inputdata_kolonne] must exist before it can be loaded as input data
The column specified in [Outputdata_kolonne] must exist before it can be loaded as output data
...