Obsidian tags are intrepreted as headings instead of labels

[kstimp]

The Obsidian app allows the use of 'tags' using the #tag notation. md2conf interperets these as Heading1 for Confluence instead of creating a label.

Example markdown created in Obsidian:

#AWS #iot #Sitewise

Asset Models

Asset Models are reusable templates used to define the properties (attributes, measurements, transforms, and calculated metrics) for a type of asset.

• Measurements are the sensor readings.
• Transforms are a calculation performed on each measurement message. e.g. convert °C to °F
• Metrics are calculated on a schedule and act on a given time window. They may aggregate properties from the same asset or children assets.
  When an asset is created from a model all of the properties keep their same ids. Thus by knowing the assetId and the associated assetModelId you can get all of the propertyIds on that asset for data retrieval.

As rendered in Confluence:

[hunyadi]

md2conf publishes Confluence wiki pages in a multi-phase process.

First, the Markdown document is parsed with Python-Markdown. For the Obsidian tags to be recognized, we would need support in Python-Markdown to identify and return these tags. (Ignoring the tags is likely an easier option, which could be accomplished with pre-processing, much like how Markdown front-matter is parsed.)

Next, we would need md2conf to interact with the Label API in Confluence REST API v2 such that these tags are associated with the wiki page. Today, md2conf doesn't call Label API endpoints.