Currently, when editing a tag (Organize >> Tags >> Edit Tag) and the user's attempt to save the tag matches another existing tag, the user sees an error message stating the following:
Tag already exists.
- - -
I believe that there's a good amount of value in providing users with the option to merge the tag being edited into the other "existing" tag, including:
a) reducing the number of overall tags (helps with load times and manageability, etc.), and
b) allowing events that are already associated with the tag being edited to be updated automatically with the other "existing" tag to be used going forward.
- - -
To better outline the idea, I've included a scenario we recently ran into:
When attempting to change the tag "#wellness" to "wellness", where "wellness" already exists, we received the error message seen above.
In order to accomplish the goal of removing "#wellness" and adding "wellness", we must navigate to All Events, click in the "tags" field, wait 20 seconds for the tags to load, enter "#wellness" into the text field, select "#wellness" from the suggestions seen in the drop-down menu, click the "Filter Events" button to the right, select all using the checkbox, click in "Bulk Actions", select "Add Taxonomies", click in the "tags" field, wait 20 seconds for the tags to load, enter "wellness" into the text field, select "wellness" from the suggestions seen in the drop-down menu, click "Apply", click the "Filter Events" button to the right, select all using the checkbox, click in "Bulk Actions", select "Remove Taxonomies", click in the "tags" field, wait 20 seconds for the tags to load, enter "#wellness" into the text field, select "#wellness" from the suggestions seen in the drop-down menu, click "Apply" ... and only then we're done ... with just ONE tag!
Imagine if there were many tags that we needed to merge (there are) ... this could take a lifetime.
- - -
In the above scenario we'd ideally have the option of merging the tags into just "wellness", which would effectively remove "#wellness" from any associated events and replace it with "wellness".
- - -
You might be asking ... but why do you need to merge these tags in the first place, Brian?
Glad you asked!
After our recent migration to the new hosted hub, some of our previously existing tags include a hashtag as the first character (ex: #tag).
This was done intentionally, as to "hack" the twitter auto-share plugin in attempt to select which tags would be included in the auto-tweet for the event.
Any tags that had a hashtag prepended to them, would be sorted alphabetically in the tag hierarchy, before any alphabetical ("a-z") characters...
...and would thus (likely) appear as a hashtag at the end of our tweets, depending on the length of the earlier portion of the automatically-generated tweet and available / remaining characters.
This worked okay for us over the last year or so...
However, with the new hosted hub / twitter auto-share tool, it appears as though the # character is *automatically* prepended to **every** tag that is tweeted, regardless of whether or not the "#" character is already present in the tag itself (in the past, a second hashtag was not added, which seemed to take into account the presence of a hashtag already being present in the tag).
So, what's the harm in prepending a hashtag when including tags as part of the tweet format?
Another great question!
Anytime a tag that is prepended with the "#" character is tweeted, an additional "#" character is prepended at the time of tweeting / included in the tweet, and looks like this: https://twitter.com/WomensCalendar/status/950879972293468160
Here, you'll see the tags that have two ## characters, where the first character isn't "clickable" and looks odd at best.
As twitter is a public-facing social network, it is very important for businesses (calendars) to always put their best foot forward.
While it may be seen as a "small" thing to some, this type of social media "faux pas" might appear to others as the account "tweeting" being unknowledgeable or even incompetent, which has serious potential to negatively affect the calendar's businesses.
- - -
Thank you very much for your consideration!