Tagger page
The HXL Proxy's Tagger page opens automatically when you choose a data source without HXL tags on the initial Source page. There are two steps:
- Select the last header row.
- Define hashtags (and optionally, attributes) for some or all of the columns, based on the header text.
When you are done tagging, the HXL Proxy will take you to the Recipe page.
You need to let the tagger know which is the last row of headers in the data, by selecting the button beside that row in the preview. The Tagger will use that row as the template for tagging the dataset, and will redirect you to the main Tagger form.
The Tagger presents a form listing the header text and letting you enter a hashtag for matching each text pattern. Note that the the Tagger matches based on text, not on the column number: that means that if there are two columns with exactly the same header text, the first match will apply to both of them.
You must enter at least one hashtag, but may leave any number of other columns blank. See Default HXL hashtag below for more information.
If the "Match full header text?" box is checked (as it is by default), then the Tagger will match all of the header text (case-insensitive, and ignoring differences in whitespace and punctuation). If the box is unchecked, then the Tagger will match substrings of the header text, so that "country" will match both "Country" and "Country code". Use this feature with care.
If you enter a hashtag in this box, the Tagger will use it for any header that doesn't have a hashtag defined. This can be especially useful with the HXL +label attribute, as in the following example:
| Country | Country code | 2013 | 2014 | 2015 |
|---|---|---|---|---|
| #country+name | #country+code | #affected+label | #affected+label | #affected+label |
| AFG | Afghanistan | 460 | 510 | 320 |
| AGO | Angola | 450 | 200 | 115 |
| ALB | Albania | 27 | 130 | 83 |
Instead of defining separate mappings for the "2013", "2014", and "2015" headers, you can simply assign #affected+label as the default HXL hashtag.
As an alternative to defining the tagger via forms, advanced software developers may choose to use JSON taggers specification.