 |
About cm3
|
|
|
How does cm3 handle metadata? Does cm3 support Dublin Core, AGLS, or other standards?
Actually cm3 is very flexible and powerful in the area of metadata, since the very nature of the way it stores content is to use structured metadata fields.
Yes, cm3 supports both Dublin Core and AGLS metadata structures. It can in fact support any standard that you need.
Since cm3 handles content on a field-by-field level and since the macro language offers fine control over conditional field-based logic, cross referencing of keywords, relationship fields, and user data is very powerful. It's possible to configure virtually any kind of metadata relationship that you need: related links, search data, keywords, catalogue categorisations, user/group personalisation, and more.
There are many approaches to the storage and management of metadata in cm3:
- In the simplest scenario, metadata fields can be defined for each content structure in the system. Authors can enter metadata against each article of content.
- Simple pre-defined metadata fields exist for many of the fixed elements in the system - e.g. for file and link attachments.
- The publishing system records certain metadata such as author, publishing times, and publishing actions against every article of content.
- Metadata libraries can be configured within their own nodes of the content repository. Elements from these libraries can be associated with other articles of content using several different methods. One method is to use cross-referenced text identifier tags. Another is to configure cm3's dynamic relationship fields to allow authors to select which metadata elements are associated with their articles of content.
- Centralised libraries can be configured in such a way that your authors can choose or create their metadata, or only authorised publishers have the choice. The concept of controlled vocabularies is well supported in this way.
- Metadata relationships can be fixed into the website templates, or conditional logic can be written using cm3's macro language to define different rules for content from different parts of the content repository.
- Metadata can be handled on a one-to-one customer basis due to the close integration of cm3's user database and the content repository.
- And of course all of these methods can be used together in varying formats.
Currently cm3 provides all the tools needed to support the ideas outlined above, but metadata standards and structures need to be defined individually for each project. In the near future we plan to release a series of off-the-shelf starting point templates and tutorials for different metadata systems to accelerate the creation of more advanced metadata systems in your projects.
|
|
