iBase Digital Asset Management Blog

Multiple Metadata Schemas in Digital Asset Management

27th May 2015

Why would you need multiple metadata schemas in your digital asset management system? This depends on whether you want to catalogue different classes of object.

Multiple Metadata Schemas in Digital Asset Management

Very often, a standardised schema will serve your purposes perfectly well – this is why such things as Dublin Core exist. At other times though, your metadata cataloguing requirements will vary, depending on whether you’re describing works of art, books, artists, etc. In cases such as these, rather than try to crowbar your differing requirements into a single schema, it makes much more sense to create a schema for each object type.

iBase Trinity resolves this issue with the use of Item Types, which allow you to specify as many different schemas as you like. In addition, you can link as many different item types together using Relationships. For an example of item types and relationships, see Trinity in action at www.capitalcollections.org.uk. For an example of items types and relationships, have a look at some of the items such as this one, where the work of art is linked both to an artist and a media type.

For more information on metadata schema, item types and relationships, contact us at sales@ibase.com or call us on +44 (0) 1943 603636.

digital asset management
metadata
schema