When you look at the purchase of any enterprise CMS it is important to ensure that it ticks all the boxes when it comes to metadata. Metadata is important for SEO purposes, but this is just the tip of the iceberg. We believe that intelligent cataloguing of your content can make the difference between a successful implementation and a failed one. It is not enough to simply create and maintain content; that content needs to be indexed and catalogued in a way that will be useful in the future.
Because metadata comes in so many different forms, we provide a range of options for making meta data entry and assignment more simple.
- auto-suggest tagging
- taxonomy tree selection
- radio button list
- comprehensive validation
- dropdown lists
- tree selection
There are a number of standards which can be used to ensure consistency. Often these standards are more prevalent in the public sector, where there is a common goal to index content in a way which is more interoperable between different systems.
Many of the elements that make up these standards can be auto-generated from the context of the content within the CMS. We have, for example, implemented the Dublin core standard on this site, but in fact as a user you are blissfully unaware of the implementation. The data to support the standard is generated automatically, but this can be done manually if required.
As an example, one of the elements of the Dublin core standard is the date of content creation. We use the CMS to generate the content, and the created date can be either the actual created date or the published date. There is no need to manually enter any information for this.
Good SEO requires that we carefully assign keywords and a meta description to each of the web pages produced by the CMS.
For keywords, we tend to use a facility called tagging which assigns common "tags" to the content. This facility allows the user to simply start typing the words and as soon as they type the first couple of characters the system will auto-suggest tags or keywords which have been created by other users of the CMS. Using tags in this way helps to ensure consistency across your content and eradicates issues such as misspelt keywords.
If a user does misspell a keyword tag then the keyword spelling can be updated centrally and it will update all content that uses that tag.
Using the in-built metadata validation, it is possible to make metadata a required field before submission.
Because all metadata definitions allow help text to be entered, you can enter prompts requesting that certain styles of metadata or writing style be used. Users need to understand that the description needs to make sense when read out of context, and ideally the tense and style of description will be consistent across the site.
You can actually use metadata to power certain controls. Here are a couple of examples:
Tag clouds give your end users an alternative method of finding content. This control works in much the same way as a navigational control, except that your are no longer navigating by hierarchy, but instead by tags.
Virtually all of our standard list controls fully support filtering by taxonomy. See more on taxonomy management.