This module's audience is developers who require machine names for taxonomy vocabularies, including views support. This module allows existing (and new) installations to continue using the Drupal 6 taxonomy API while gaining the benefits of vocabulary machine names.
As such, it should play nice with any taxonomy related modules (such as those that provide import / export features, etc...)
Background
Taxonomies are a bit of an issue to deal with in Drupal, specifically in terms of using them in install profile or update hooks, team development, and deployment through environments.
There are a few modules out there which try to get around this issue. However, they are limited in a number of ways. Currently there are 3 methods I can see in trying to solve this. This module goes with #3.
Use existing modules (such as features_extras or exportables). This provides taxonomy (among other) machine name support, however, it can require multi-module dependencies, and typically require additional calls while programming. As well, there is typically no views support to remove "vid"s from view exports.
Show related articles by percentage found of its terms (this module supports related Title also) ! I found no module meet their requirements, then this module be here.
This module provides a simple way to show a short-term urgent message on the website. Think of CNN Breaking News, when they show a short message the top of the site (or the 'Welcome!' style messages at StackExchange websites). This module works for both anonymous and authenticated users by using a cookie, and recording actions in the database. This solves the need to show messages independent of the users authenticated status.
With User Alerts, you can:
Alert users about breaking news, or a special same-day sale for ecommerce
Set the appropriate permissions for selected roles
Set the User Alert block in the appropriate region of your theme.
Create a user alert node.
You can also set some global settings for alerts at admin/settings/user-alert.
Unpublished alert nodes are removed from the system automatically. This is to prevent an old alert being seen by a user (if the cookie was cleared or expired, for example) if a node was republished accidentally.