This is to inform developers about planned next steps in mass tagging of addons.
- There are 502 addons in OH
- There are 2236 thing- and bridge-types, of which 1440 (65%) are tagged
- There are 13'229 channel-types, of which 429 (3%) are tagged
In the last few days I started a mass tagging program (#18549, #18557, #18558, and #18563), in order to apply Equipment tags an all (almost) Thing-types in OH-Addons (which is why 1440 are now tagged)
It does NOT apply Point + Property tags on the Channel-types.
For this first mass tagging project, the PRs are split across bindings alphabetically by name.
Once the Thing-type Equipment tag PRs are merged, the next step is to apply Channel-type Point + Property tags. This will not be so easy.
Instead of making PRs split across bindings alphabetically by name, I intend to make PRs that are split across bindings functionally by Equipment tag. Some of the first mass tagging PR priorities are for subsets of Channel-types across the full set of addons, that are filtered according to the (newly applied) Equipment tags as follows:
LightSource, Lightbulb, LightStrip and children (ca. 78 thing-types)
Thermostat, Boiler, AirConditioner, HVAC and children (ca. 64 thing-types).
WindowCovering, Blinds, Drapes (ca. 32 thing-types)..
MediaPlayer, Speaker and children (ca. 59 thing-types)..
- Maybe
WeatherStation and WeatherService (ca. 45 thing-types).
- Maybe
WhiteGood and children (ca. 27 thing-types).
Inverter (ca. 28 thing-types).
Vehicle (ca. 17 thing-types).
Receiver (ca. 56 thing-types).
NetworkAppliance (ca. 87 thing-types).
WebService (ca. 75 thing-types).
=> Any thoughts about a relatively automated way to tag everything else?
This is to inform developers about planned next steps in mass tagging of addons.
In the last few days I started a mass tagging program (#18549, #18557, #18558, and #18563), in order to apply
Equipmenttags an all (almost) Thing-types in OH-Addons (which is why 1440 are now tagged)It does NOT apply
Point+Propertytags on the Channel-types.For this first mass tagging project, the PRs are split across bindings alphabetically by name.
Once the Thing-type
Equipmenttag PRs are merged, the next step is to apply Channel-typePoint+Propertytags. This will not be so easy.Instead of making PRs split across bindings alphabetically by name, I intend to make PRs that are split across bindings functionally by
Equipmenttag. Some of the first mass tagging PR priorities are for subsets of Channel-types across the full set of addons, that are filtered according to the (newly applied)Equipmenttags as follows:LightSource,Lightbulb,LightStripand children (ca. 78 thing-types)Thermostat,Boiler,AirConditioner,HVACand children (ca. 64 thing-types).WindowCovering,Blinds,Drapes(ca. 32 thing-types)..MediaPlayer,Speakerand children (ca. 59 thing-types)..WeatherStationandWeatherService(ca. 45 thing-types).WhiteGoodand children (ca. 27 thing-types).Inverter(ca. 28 thing-types).Vehicle(ca. 17 thing-types).Receiver(ca. 56 thing-types).NetworkAppliance(ca. 87 thing-types).WebService(ca. 75 thing-types).=> Any thoughts about a relatively automated way to tag everything else?