Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update gts-headers-in-wis2.rst #725

Merged
merged 1 commit into from
Aug 13, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/source/user/gts-headers-in-wis2.rst
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@

To enable the WIS2 to GTS Gateway to correctly identify the data to be republished on the GTS, you need to include the GTS property in the WIS2 Notification Message as follows:

.. code-block:: json

Check warning on line 15 in docs/source/user/gts-headers-in-wis2.rst

View workflow job for this annotation

GitHub Actions / main

Could not lex literal_block as "json". Highlighting skipped.

"properties": {
"gts": {
Expand All @@ -21,7 +21,7 @@
}
}

wis2box can add these to WIS2 Notifications automatically, provided you specify the additional file `gts_headers_mappings.json` that contains the required information to map the GTS headers to the incoming filenames.
wis2box can add these to WIS2 Notifications automatically, provided you specify the additional file `gts_headers_mappings.csv` that contains the required information to map the GTS headers to the incoming filenames.

Note that this is optional and only required if you want to turn off the existing system responsible for sending data to the GTS during the transition period.

Expand All @@ -36,7 +36,7 @@

Example content for `gts_headers_mapping.csv`:

.. code-block:: csv

Check warning on line 39 in docs/source/user/gts-headers-in-wis2.rst

View workflow job for this annotation

GitHub Actions / main

Pygments lexer name 'csv' is not known

string_in_filepath,TTAAii,CCCC
ISMD01LIIB,ISMD01,LIBB
Expand All @@ -45,7 +45,7 @@
In this example, whenever `ISMD01LIIB` or `ISMD02LIIB` is contained in the filepath of the incoming file,
the corresponding GTS headers will be added to the WIS2 Notification Message as a dictionary in the `properties` field:

.. code-block:: json

Check warning on line 48 in docs/source/user/gts-headers-in-wis2.rst

View workflow job for this annotation

GitHub Actions / main

Could not lex literal_block as "json". Highlighting skipped.

"properties": {
"gts": {
Expand Down
Loading