Avid Interplay MAM 5.9 Datamodel Administrator User guide
- Category
- Software
- Type
- User guide
Interplay
®
| MAM Datamodel Administrator
User’s Guide
Version 5
2
Legal Notices
Product specifications are subject to change without notice and do not represent a commitment on the part of Avid Technology, Inc.
This product is subject to the terms and conditions of a software license agreement provided with the software. The product may only be
used in accordance with the license agreement.
This product may be protected by one or more U.S. and non-U.S patents. Details are available at www.avid.com/patents.
This document is protected under copyright law. An authorized licensee of Avid Interplay | Media Asset Manager may reproduce this
publication for the licensee’s own use in learning how to use the software. This document may not be reproduced or distributed, in whole
or in part, for commercial purposes, such as selling copies of this document or providing support or educational services to others. This
document is supplied as a guide for Avid Interplay | MAM. Reasonable care has been taken in preparing the information it contains.
However, this document may contain omissions, technical inaccuracies, or typographical errors. Avid Technology, Inc. does not accept
responsibility of any kind for customers’ losses due to the use of this document. Product specifications are subject to change without
notice.
Copyright © 2017 Avid Technology, Inc. and its licensors. All rights reserved.
The following disclaimer is required by Apache Commons Logging:
Copyright © 2003-2013 The Apache Software Foundation
Licensed under the Apache License, Version 2.0 (http://www.apache.org/licenses/LICENSE-2.0)
The following disclaimer is required by Apache Commons Net:
Copyright © 2001-2013 The Apache Software Foundation
Licensed under the Apache License, Version 2.0 (http://www.apache.org/licenses/LICENSE-2.0)
The following disclaimer is required by Apache Jakarta Commons HttpClient:
Copyright © 2004 The Apache Software Foundation
Licensed under the Apache License, Version 2.0 (http://www.apache.org/licenses/LICENSE-2.0)
The following disclaimer is required by Apache log4net:
Copyright © 2004-2011 The Apache Software Foundation
Licensed under the Apache License, Version 2.0 (http://www.apache.org/licenses/LICENSE-2.0)
The following disclaimer is required by Apache Xerxes:
Copyright © 2008 Apache Software Foundation
Licensed under the Apache License, Version 2.0 (http://www.apache.org/licenses/LICENSE-2.0)
The following disclaimer is required by Behaviour.js:
This product includes software developed by Ben Nolan and his contributors. Copyright © 2006, 2007 Ben Nolan. All rights reserved.
The following disclaimer is required by CFlatToolbar:
Portions of this product are Copyright © 2002 Roger Onslov, all rights reserved.
The following disclaimer is required by Cross-Browser X Library:
Copyright © 2000-2009 Michael Foster, distributed under the terms of LGPL (http://cross-browser.com/license.html)
The following disclaimer is required by CSXButton:
Copyright © 1998 Michael Santoro, all rights reserved.
The following disclaimer is required by CVersionInfo:
Portions of this product are Copyright © 1997 Roberto Rocco, all rights reserved.
The following disclaimer is required by Assisted Solutions InputMask:
Portions of this product are Copyright © Data Reasearch Group. All rights reserved.
The following disclaimer is required by dicas:
Portions of this product are Copyright © dicas digital image coding GmbH. All rights reserved.
The following disclaimer is required by DirectShowLib:
Copyright (C) 2007 http://sourceforge.net/projects/directshownet, distributed under the terms of LGPL V2.1 (http://www.gnu.org/licenses/
lgpl-2.1.html)
The following disclaimer is required by Divelements:
Portions of this product are Copyright © 2003-2011 Divelements Limited.
The following disclaimer is required by DockPanelSuite:
This product includes software developed by Mark Twombley, Steve Overton, and Weifen Luo and their contributors. Copyright © 2009
Mark Twombley, Steve Overton, and Weifen Luo.
The following disclaimer is required by FFmpeg:
FFmpeg is Copyright © 2000-2003 Fabrice Bellard and is licensed under the terms of the GNU Lesser General Public License, which is
included with this product.
3
The following disclaimer is required by GDCL Sample Parser:
Copyright 2004 GDCL (http://www.gdcl.co.uk)
The following disclaimer is required by getElementsByAttribute:
Copyright © 2006 Robert Nyman (http://www.robertnyman.com)
The following disclaimer is required by GoXam:
Portions of this product are Copyright © 1995-2011 Northwoods Software. All rights reserved.
The following disclaimer is required by IC#Code #ZipLib:
Copyright © 2000-2009 Michael Foster, distributed under the terms of GNU GPL with the following exception: As a special exception, the
copyright holders of this library give you permission to link this library with independent modules to produce an executable, regardless of
the license terms of these independent modules, and to copy and distribute the resulting executable under terms of your choice, provided
that you also meet, for each linked independent module, the terms and conditions of the license of that module. An independent module is
a module which is not derived from or based on this library. If you modify this library, you may extend this exception to your version of the
library, but you are not obligated to do so. If you do not wish to do so, delete this exception statement from your version.
The following disclaimer is required by IFilter Text Extracter:
IFilter Text Extracter Microsoft Public License (Ms-PL)
The following disclaimer is required by ImageMagick:
Copyright 1999-2014 ImageMagick Studio LLC, a non-profit organization dedicated to making software imaging solutions freely available.
(http://www.imagemagick.org/script/license.php)
The following disclaimer is required by Interplay Central Playback Service:
This product includes FFmpeg, which is covered by the GNU Lesser General Public License.
This product includes software that is based in part of the work of the FreeType Team.
This software is based in part on the work of the Independent JPEG Group.
This product includes libjpeg-turbo, which is covered by the wxWindows Library License, Version 3.1.
Portions copyright 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002 by Cold Spring Harbor Laboratory. Funded under Grant P41-
RR02188 by the National Institutes of Health.
Portions copyright 1996, 1997, 1998, 1999, 2000, 2001, 2002 by Boutell.Com, Inc.
Portions relating to GD2 format copyright 1999, 2000, 2001, 2002 Philip Warner.
Portions relating to PNG copyright 1999, 2000, 2001, 2002 Greg Roelofs.
Portions relating to gdttf.c copyright 1999, 2000, 2001, 2002 John Ellson ([email protected]).
Portions relating to gdft.c copyright 2001, 2002 John Ellson ([email protected]).
Portions relating to JPEG and to color quantization copyright 2000, 2001, 2002, Doug Becker and copyright (C) 1994, 1995, 1996, 1997,
1998, 1999, 2000, 2001, 2002, Thomas G. Lane. This software is based in part on the work of the Independent JPEG Group. See the file
README-JPEG.TXT for more information. Portions relating to WBMP copyright 2000, 2001, 2002 Maurice Szmurlo and Johan Van den
Brande.
Permission has been granted to copy, distribute and modify gd in any context without fee, including a commercial application, provided that
this notice is present in user-accessible supporting documentation.This does not affect your ownership of the derived work itself, and the
intent is to assure proper credit for the authors of gd, not to interfere with your productive use of gd. If you have questions, ask. "Derived
works" includes all programs that utilize the library. Credit must be given in user-accessible documentation.This software is provided "AS
IS." The copyright holders disclaim all warranties, either express or implied, including but not limited to implied warranties of
merchantability and fitness for a particular purpose, with respect to this code and accompanying documentation.Although their code does
not appear in gd, the authors wish to thank David Koblas, David Rowley, and Hutchison Avenue Software Corporation for their prior
contributions.
The following disclaimer is required by Interplay Entertainment Corp.:
The Interplay name is used with the permission of Interplay Entertainment Corp., which bears no responsibility for the product.
The following disclaimer is required by JavaZoom:
Portions of this product are Copyright © JavaZoom. All rights reserved.
The following disclaimer is required by JQuery:
Copyright 2013 jQuery Foundation and other contributors (http://jquery.com/)
The following disclaimer is required by JQuery Plugin Autocomplete:
Copyright (c) 2009 Jörn Zaefferer. (http://www.opensource.org/licenses/mit-license.php)
The following disclaimer is required by jquery.contextMenu:
Copyright © 2008 A Beautiful Site, LLC
The following disclaimer is required by jquery.jqDnR:
Copyright © 2007 Brice Burgess (<bhb@iceburg.net>, http://www.iceburg.net)
The following disclaimer is required by Ui.dropdownchecklist:
Copyright © 2008-2010 Adrian Tosca, Copyright (c) 2010-2011 Ittrium LLC
The following disclaimer is required by jquery.json:
Copyright © 2009 Brantley Harris
4
The following disclaimer is required by jquery.metadata:
Copyright © 2006 John Resig, Yehuda Katz, Jörn Zaefferer, Paul McLanahan
The following disclaimer is required by jquery.jqModal:
Copyright © 2007,2008 Brice Burgess (<[email protected]>)
The following disclaimer is required by jquery.jTemplates:
Copyright © 2009 Tomasz Gloc
The following disclaimer is required by jquery.treeview:
Copyright © 2007 Jörn Zaefferer
The following disclaimer is required by jquery UI:
Copyright © 2011, Scott Gonzalez et al. (http://jqueryui.com/about)
The following disclaimer is required by JScape:
Portions of this product are Copyright © JScape. All rights reserved.
The following disclaimer is required by JScript Hashtable:
Copyright © 2003 Michael Synovic This is a Javascript implementation of the Java Hashtable object.
The following disclaimer is required by JScript Table Sorter:
Copyright ©2010 Michael Leigeber. All Rights Reserved This script has been tested in all major browsers and is available free of charge
for both personal or commercial projects under the creative commons license.
The following disclaimer is required by Libjpeg-turbo:
libjpeg-turbo is Copyright © 1998-2005 Julian Smart, Robert Roebling et al and is licensed under the terms of the wxWindows Library
Licence, Version 3.1, which is included with this product.
The following disclaimer is required by Limited Concurrency Task Scheduler:
Portions Copyright © Microsoft Corporation Inc. All Rights Reserved. Microsoft Limited Public License version 1.1
The following disclaimer is required by MediaLooks:
Portions of this product are Copyright MediaLooks . All rights reserved.
The following disclaimer is required by Microsoft Corporation:
Portions of this product are Copyright © Microsoft Corporation. All rights reserved.
The following disclaimer is required by Microsoft.Net Framework Base Class Libraries, BigRational:
Portions of this product are Copyright © Microsoft Corporation. All rights reserved.
The following disclaimer is required by Microsoft Prism:
Microsoft patterns & practices License; Creative Commons Attribution License 3.0 Unported
The following disclaimer is required by MOG Solutions:
Portions of this product are Copyright © MOG Solutions. All rights reserved.
The following disclaimer is required by MPEG Audio:
MPEG Audio technology may be included with this product. Audio MPEG, Inc. and S.I.SV.EL., S.P.A. require this notice: This product
contains MPEG Audio technology licensed by Audio MPEG and SISVEL only for use in accordance with Avid's EULA. Last Updated:
March 2010
The following disclaimer is required by MSTS-adapter:
Copyright © 2008 Will Ballard / Duane Fields / ExactMagic
The following disclaimer is required by MVVM Lite:
Copyright (c) 2009 - 2011 Laurent Bugnion
The following disclaimer is required by nUnit:
Copyright (c) 2004-2009 Charlie Poole
The following disclaimer is required by Obout Software:
Portions of this product are Copyright © Obout Software. All rights reserved.
The following disclaimer is required by OpenSSL:
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)
The following disclaimer is required by PixieLib:
Portions of this program borrowed from PixieLib.NET, Copyright 2005 Paul DiLascia.
5
The following disclaimer is required by FilterCode:
Copyright © 2011 phpleo
The following disclaimer is required by PlainIt Works JeeGooContext:
Copyright © 2009 - 2010 by Erik van den Berg
The following disclaimer is required by Prototype JavaScript Framework:
Copyright © 2005-2008 Sam Stephenson
The following disclaimer is required by RabbitMQ:
Copyright © 2013 GoPivotal, Inc. All rights reserved
The following disclaimer is required by ScintillaNET:
Copyright © 1998-2006 by Neil Hodgson (ne[email protected]) All Rights Reserved ScintillaNET bindings are Copyright © 2002-2006 by
Garrett Serack (gserack@gmail.com) All Rights Reserved
The following disclaimer is required by Script.Aculo.Us Web 2.0 JavaScript:
Copyright © 2005-2008 Thomas Fuchs (http://script.aculo.us, http://mir.aculo.us)
The following disclaimer is required by Search Highlighter:
Copyright (c) 2002, 2007, 2008 Stuart Langridge (sil@kryogenix.org)
The following disclaimer is required by Silverlight Menu:
Microsoft Public License (Ms-PL) http://sl3menu.codeplex.com/license
The following disclaimer is required by Silverlight Serializer:
Copyright © Mike Talbot, Microsoft Public License (Ms-PL)
The following disclaimer is required by tipsy:
Copyright (c) 2008 Jason Frame ([email protected]om). The software and documentation is released under the MIT license.
https://github.com/jaz303/tipsy/blob/master/LICENSE.
The following disclaimer is required by WPF Themes:
Licensed under the Microsoft Public License (Ms-PL) http://wpf.codeplex.com/license
The following disclaimer is required by WPF Toolkit:
Microsoft Public License (Ms-PL)
The following disclaimer is required by Xmlextras.js:
Copyright © 2006 Erik Arvidsson Licensed under the Apache License, Version 2.
The following disclaimer is required by XNView:
Portions of this product are Copyright © XNView. All rights reserved.
Attn. Government User(s). Restricted Rights Legend
U.S. GOVERNMENT RESTRICTED RIGHTS. This Software and its documentation are “commercial computer software” or “commercial
computer software documentation.” In the event that such Software or documentation is acquired by or on behalf of a unit or agency of the
U.S. Government, all rights with respect to this Software and documentation are subject to the terms of the License Agreement, pursuant
to FAR §12.212(a) and/or DFARS §227.7202-1(a), as applicable.
Trademarks
Avid, the Avid Logo, Avid Everywhere, Avid DNXHD, Avid DNXHR, Avid Nexis, AirSpeed, Eleven, EUCON, Interplay, iNEWS, ISIS, Mbox,
MediaCentral, Media Composer, NewsCutter, Pro Tools, ProSet and RealSet, Maestro, PlayMaker, Sibelius, Symphony, and all related
product names and logos, are registered or unregistered trademarks of Avid Technology, Inc. in the United States and/or other countries.
The Interplay name is used with the permission of the Interplay Entertainment Corp. which bears no responsibility for Avid products. All
other trademarks are the property of their respective owners. For a full list of Avid trademarks, see: http://www.avid.com/US/about-avid/
legal-notices/trademarks.
Avid Interplay | MAM Datamodel Administrator User’s Guide v5.9 • Created 3/21/2017 • This document is distributed by
Avid in online (electronic) form only, and is not available for purchase in printed form.
6
Contents
Symbols and Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
If You Need Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Avid Training Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 1 Getting Started with Interplay | MAM Datamodel Administrator . . . . . . . . . . . . 12
About Datamodel Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Basic Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Prerequisites for Using Datamodel Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Elements of a Data Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Data Model Layout Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Basic Workflow for Creating a Data Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Starting Datamodel Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Datamodel Administrator Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Menu and Toolbar Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Work Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Quitting Datamodel Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Chapter 2 Basic Actions on a Data Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Creating a Data Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Opening a Data Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Opening Data Model From Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Opening a Locally Saved Data Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Messages Displayed When Opening a Data Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Showing Deleted Data Model Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Exporting a Partial Data Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Importing a Data Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Saving the Data Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Saving on the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Saving Locally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Activating a Data Model on the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Maintaining the Data Model History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Creating Data Model Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Copying Information From Detail Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Renewing Database Indices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Creating Migration Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Chapter 3 Working with Languages and Localizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Enabling and Disabling Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Creating Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
7
Localizing Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Localizing Tooltips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Exporting Labels and Tooltips. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Importing Labels and Tooltips. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Deleting Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Chapter 4 Working with Tenants, Thesauri, and Legal Lists. . . . . . . . . . . . . . . . . . . . . . . . 59
Working with Tenants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Importing Tenants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Creating and Renaming a Tenant Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Removing Tenants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Working with Thesauri . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Importing Thesauri . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Creating and Renaming a Thesaurus Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Removing Thesauri . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Working with Legal Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Creating and Renaming a Legal List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Removing Legal Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Chapter 5 Working with Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Creating a Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Defining the Order of Object, EDL, and Process Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Deleting a Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Editing the Properties of a Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Opening the Details View of a Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
The Layout of a Class’s Details View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Renaming a Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Editing the Attribute Assignment for a Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Defining the Attributes Order Within a Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Defining Strata Groups for an Object Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Editing the Strata Assignment for an Object Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Assigning Expressions to Strata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Defining the Order of Strata within an Object Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Defining the Rights Status and Table Layout for a Segment Content Class . . . . . . . . . . 82
Defining the Hit List and Search Form Layout for a Master Data Class. . . . . . . . . . . . . . 83
Chapter 6 Working with Aspects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Creating an Aspect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Opening the Details View of an Aspect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
The Layout of an Aspect’s Details View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Renaming an Aspect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Editing the Attribute Assignment for an Aspect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
8
Assigning an Aspect to a Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Deleting an Aspect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Chapter 7 Working with Attribute Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Creating an Attribute Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Editing an Attribute Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Deleting an Attribute Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Chapter 8 Working with Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Information in the Attributes View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Creating an Attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Editing an Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Deleting an Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Working with Sub-Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Creating a Sub-Attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Editing a Sub-Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Deleting a Sub-Attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Working with Essence Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Chapter 9 Working with Strata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Creating a Stratum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Editing a Stratum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Deleting a Stratum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Chapter 10 Working with Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Creating an Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Editing an Association. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Deleting an Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Chapter 11 Working with Content-Based Access and Expressions. . . . . . . . . . . . . . . . . . 122
Working with Content-Based Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Understanding CBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Enabling and Disabling CBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Creating a CBA Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Editing a CBA Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Deleting a CBA Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Working with Expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Creating an Expression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Editing an Expression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Deleting an Expression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Chapter 12 Working with Metadata Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Creating a Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Template Editor Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Adding and Deleting Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
9
Moving and Resizing Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Defining Properties for Attributes and Process Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Setting Options for Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Setting Options for Compound Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Setting Options for Process Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Setting Options for Process Action Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Editing the Template’s Grid Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Assigning JavaScript Code to the Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Editing a Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Deleting a Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Chapter 13 Working with Custom Searches and Hit Lists. . . . . . . . . . . . . . . . . . . . . . . . . . 152
Working with Custom Search Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Creating a Custom Search Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Editing a Custom Search Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Deleting a Custom Search Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Working with Time Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Creating a Time Restriction Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Editing a Time Restriction Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Deleting a Time Restriction Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Working with Hit Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Creating a Hit List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Editing a Hit List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Deleting a Hit List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Chapter 14 How to....?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Creating a Structured Stratum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Defining the Layout of Legal Lists for Structured Strata in MAM Desktop . . . . . . . . . . . . . . 177
Configuring Drag and Drop for Compound Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Configuring Group-Specific Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Defining Placeholder Icons for Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Using This Guide
Congratulations on your purchase of Avid
®
Interplay
®
| Media Asset Manager, a powerful system for
archiving and managing media in a shared storage environment. This guide describes how to use
Avid Interplay | MAM Datamodel Administrator, the central tool for creating and configuring the
MAM data model.
This guide is intended for all users charged with maintaining Interplay Media Asset Manager,
specifically those who need to adapt and maintain the data model used by Interplay MAM. This
guide contains all the task-oriented instructions and conceptual information you need to work with
Interplay MAM Datamodel Administrator.
n
All tasks described in this guide can only be performed by users with administrative privileges.
Symbols and Conventions
Avid documentation uses the following symbols and conventions:
Symbol or Convention Meaning or Action
n
A note provides important related information, reminders, recommendations, and
strong suggestions.
c
A caution means that a specific action you take could cause harm to your
computer or cause you to lose data.
w
A warning describes an action that could cause you physical harm. Follow the
guidelines in this document or on the unit itself when handling electrical
equipment.
g
A user tip provides a helpful hint that can aid users in getting the most from their
system.
s
A shortcut shows the user keyboard or mouse shortcuts for a procedure or
command.
> This symbol indicates menu commands (and subcommands) in the order you
select them. For example, File > Import means to open the File menu and then
select the Import command.
This symbol indicates a single-step procedure. Multiple arrows in a list indicate
that you perform one of the actions listed.
Bold font Bold font is primarily used in task instructions to identify user interface items and
keyboard sequences.
Italic font Italic font is used to emphasize certain words and to indicate variables.
Courier Bold font
Courier Bold font identifies text that you type.
Ctrl+key or mouse action Press and hold the first key while you press the last key or perform the mouse
action. For example, Command+Option+C or Ctrl+drag.
11
If You Need Help
If you are having trouble using your Avid product:
1. Retry the action, carefully following the instructions given for that task in this guide. It is
especially important to check each step of your workflow.
2. Check the latest information that might have become available after the documentation was
published. You should always check online for the most up-to-date release notes or ReadMe
because the online version is updated whenever new information becomes available. To view
these online versions, select ReadMe from the Help menu, or visit the Knowledge Base at
www.avid.com/support.
3. Check the documentation that came with your Avid application or your hardware for
maintenance or hardware-related issues.
4. Visit the online Knowledge Base at www.avid.com/support. Online services are available 24
hours per day, 7 days per week. Search this online Knowledge Base to find answers, to view
error messages, to access troubleshooting tips, to download updates, and to read or join online
message-board discussions.
Avid Training Services
Avid makes lifelong learning, career advancement, and personal development easy and convenient.
Avid understands that the knowledge you need to differentiate yourself is always changing, and Avid
continually updates course content and offers new training delivery methods that accommodate your
pressured and competitive work environment.
For information on courses/schedules, training centers, certifications, courseware, and books, please
visit www.avid.com/support and follow the Training links, or call Avid Sales at 800-949-AVID
(800-949-2843).
| (pipe character) The pipe character is used in some Avid product names, such as Interplay |
MAM. In this document, the pipe is used in product names when they are in
headings or at their first use in text.
Symbol or Convention Meaning or Action
1 Getting Started with Interplay | MAM
Datamodel Administrator
The following topics provide basic information to help you get started using Avid Interplay | MAM
Datamodel Administrator:
• About Datamodel Administrator
• Starting Datamodel Administrator
• Datamodel Administrator Layout
• Quitting Datamodel Administrator
About Datamodel Administrator
This quick start guide is designed to familiarize you with the most important functions of Datamodel
Administrator, the data model configuration tool of Interplay MAM.
Basic Features
The Datamodel Administrator is a tool to create, customize, and activate the data model used by
Interplay MAM. You can create your own multi-genre data model or adopt the standard data model
available with Interplay MAM. You can save a data model locally as an XML file, but to use it in
Interplay MAM you have to save it to the Data Manager WS and activate it using the Datamodel
Administrator. The data model definition changes can be applied to databases before and after
deployment. Only authorized users are allowed to apply data model changes. A complete audit trail
on data model modifications is maintained in the system.
You can build data models based on objects, links, and master data. To ensure data consistency and
facilitate metadata entry, predefined terms can be used. Furthermore, MAM supports timecoded
metadata (“stratification”). Stratification uses time references to point to a specific segment in the
audio or video object. Each stratum can be dedicated to specific topical or descriptive themes, such as
visual content, editorial content, close caption text, locations, and so on. Each of the strata can be
segmented individually by assigning timecodes with the strata segments.
Interplay MAM data models consist of several elements: languages, tenants, object classes, EDL
classes, master data classes, process classes, segment content classes, attribute groups, attributes,
essence attributes, strata, legal lists, thesauri, associations, CBA rules, and expressions. The
definition of media objects types and attributes is based on content types (video, audio, images,
documents, and others). For each object type, a virtually unlimited number of attributes and strata
can be defined. Attribute types available include basic basic types — text, numbers, and dates, for
example — and references to controlled vocabulary. Attributes can be multi-valued, which means an
attribute can contain a list of values of a basic type or reference. Another attribute type is
“compound,” where an attribute can consist of several other attributes of different types. Associations
can be used to link media objects. All data model elements support multi-lingual labels.
13
You can configure result lists and metadata displays to meet your requirements. A set of predefined
query forms of different complexity levels are available; metadata forms are configurable per client
application, content type, and user group; and hit list forms are configurable for multi-level sort order
and layout.
Prerequisites for Using Datamodel Administrator
To use the Datamodel Administrator you must be a member of an administrator group that has the
following group rights:
• Administration/Platform_Administration
• Administration/Use_DMConfigurator
• Administration/Activate_DataModel
As an administrator you can review and assign these group rights in the Interplay MAM User
Manager. For additional information, see the Interplay MAM | User Manager User’s Guide that is
shipped with the software.
Elements of a Data Model
Datamodel Administrator uses the following data model elements.
Languages
To support the localization of data model elements, you can create languages for the user interface.
After a list of languages has been created, each element of the data model (attributes, strata, object
classes, and others) can be assigned a different label for each language in the list. You can also add
additional languages to the list of a data model already in use.
For additional information, see “Working with Languages and Localizations” on page 50.
Tenants
Tenants are groups of users (typically organizations or organizational units) that own a specific
portion (data and processes) within a system. Tenants are created in Interplay MAM User
Management. The names of the tenants defined in User Management are created manually or
imported to the data model using Datamodel Administrator.
For additional information, see “Working with Tenants” on page 59.
Object classes
Content genres (news, sports, politics, and others) can be defined based on various predefined object
classes (video, audio, images, documents, and others). For each object class, a specific set of data
elements (attributes, strata) can be configured and displayed in the applications. Object classes and
strata may share attributes, though not necessarily. This way you can create very specific data sets for
your object types. The standard searches delivered with Interplay MAM search in all object classes to
allow a maximum of fitting results for your searches. However, if you design your data model so that
attributes or strata are only used in one object class, you can design a customized search that only
searches for attributes and strata assigned to a certain object class. By default, Interplay MAM comes
complete with preconfigured mandatory data elements for all object classes.
For additional information, see “Working with Classes” on page 68.
14
EDL classes
Interplay MAM supports creating, editing, and playing rough-cut edit decision lists (EDLs). In the
data model, EDLs are handled like object classes. For each EDL class, a specific set of data elements
can be configured and displayed in the applications. This way you can create very specific data sets
for your EDL classes. By default, Interplay MAM comes complete with preconfigured mandatory
data elements for one EDL class.
For additional information, see “Working with Classes” on page 68.
Process classes
Interplay MAM supports business processes with Business Process Model and Notation (BPMN), a
standardized way to graphically visualize and model business processes. Process definitions written
in the BPMN language and saved as XML Process Definition Language file (XPDL) can be parsed
and read by the Interplay MAM State Machine, an Interplay MAM backend component that executes
business processes so complex concepts of user activities and automated workflows can be applied
with Interplay MAM. In Datamodel Administrator you create the process classes that are required for
the MAM State Machine to store information about running processes during process execution.
For additional information, see “Working with Classes” on page 68.
Master data classes
Master data provide information about persons, organizations, or events, and is typically referenced
in many media objects and maintained by authorized users. Master data classes are used to define
variant categories. Examples include biographic data (for Artists, Composers, Customers),
organizational data (for vendors or customers), or data for recurring events (such as the Olympic
Games). The individual master data entered in these master data classes can then be referenced by
media objects. The advantages are that the same data needs to be entered only once (which reduces
the risk of errors during data entry), you can control frequently used data, and you can save time and
storage during edit and retrieval.
For additional information, see “Working with Classes” on page 68.
Aspects
An aspect collects a set of attributes that are needed for a specific purpose. Aspects can be assigned
to object, EDL, and process classes. Assigning an aspect to a class means that all attributes of the
aspect are assigned to the class. For example, a BPM process may require that objects that are added
to the process have a specific set of attributes. An aspect collects these attributes. Then, the aspect
can easily be assigned to object and EDL classes to ensure that the classes have all the required
attributes. Aspects can also be used as a logical grouping of attributes. An aspect can, for example,
collect a set of attributes that are to be common for all classes in a customer's data model. Aspects
prevent unintentional changes to required attributes. To prevent accidental changes, an attribute that
is part of an aspect can only be modified within the context of that aspect. If an aspect has been
assigned to a class, the attributes of the aspect cannot be accidentally removed from the class.
For additional information, see “Working with Aspects” on page 87.
Legal lists
Legal lists are lists of controlled vocabulary where terms can only be added/edited by authorized
users. They allow the user to select a certain term or symbol from a given list while documenting a
media object. Using the “Attribute Fill-in” feature, you can configure whether terms from a legal list
15
are entered by value or by reference. For tenants you create the names of the legal lists in Datamodel
Administrator, while the values of the legal lists are defined in Interplay MAM's Legal List
Administrator. Users with the according rights can open a legal list in the Legal List Administrator to
define the initial values and modify existing values.
For additional information, see “Working with Legal Lists” on page 64.
Thesauri
Thesauri are freely configurable and editable hierarchically structured trees of terms with synonyms,
abbreviations, links, and more, in several languages. They allow the user to select a certain term from
a given tree while documenting a media object. For tenants and legal lists, create the names of the
thesauri in Datamodel Administrator. The terms of the individual thesauri are defined in Interplay
MAM’s Thesaurus Administrator. Users with the according rights can use the Thesaurus pick tool of
MAM Desktop and Interplay MAM Cataloger to create new thesaurus terms.
For additional information, see “Working with Thesauri” on page 61.
Attribute groups
In order to allow searches in a configured group of attributes (using the attribute search or a user-
defined search) you can create attribute groups and assign attributes to a group. Attributes can be
assigned to one or more attribute groups, or no group at all.
For additional information, see “Working with Attribute Groups” on page 96.
Attributes
Attributes are the central part of every data model. Together with strata they carry the description and
annotation needed to find and work with media objects in Interplay MAM. Using the Datamodel
Administrator you can edit existing attributes or define new ones. Attributes can be assigned to
several attribute groups as well as to various object, master, and process classes.
For additional information, see “Working with Attributes” on page 100.
Essence attributes
In addition to the data that describes the content of media objects (the metadata), Interplay MAM
maintains metadata for essence files in “essence attributes.” All essence attributes and their values are
defined automatically by the Essence Management within the system and cannot be edited by users.
Using Datamodel Administrator you can localize the labels of all essence attributes, and assign
essence attributes to attribute groups and custom search forms.
For additional information, see “Working with Essence Attributes” on page 112.
Strata
Interplay MAM Data Management supports time-coded metadata (“stratification”). Stratification
makes use of time references (associated with the respective timeline) to point to a specific part in the
video. Differing from traditional log sheets, however, each stratum can be dedicated to a specific
topical or descriptive theme. The individual descriptions can focus on particular concepts such as
visual or editorial content, closed caption text, locations, persons present, and more. Each of the
strata can be segmented individually by associating time codes with the strata segments. Possible
data input within the individual segments of a stratum is defined by the “segment content class” that
is assigned to a stratum.
16
For additional information, see “Working with Strata” on page 113.
Segment content classes
To assign attributes consistently to the individual segments of strata, Datamodel Administrator
provides the data model element “Segment content class.” Segment content classes are similar to
object classes but are used to define the attributes that shall be used in segments. For example, you
can define a segment content class that only has a text attribute, or another segment content class that
has a text attribute and two legal lists. To work properly each stratum must be assigned one segment
content class.
For additional information, see “Working with Classes” on page 68.
Associations
Another option offered by Interplay MAM is the relational data model. Using Datamodel
Administrator, you can define types of associations. These fully configurable associations can be
used to define explicit relations between two media objects (for example, media object 1 is part of
media object 2). The association types and the associations established between media objects are
stored in the database. Associations help you to structure your media objects and allow easy and
quick navigation (without searching) between associated media objects. Associations can be non-
directed, directed, or hierarchical.
For additional information, see “Working with Associations” on page 117.
Content-Based Access rules
Interplay MAM lets you control access to media objects for specific user groups based on the
metadata in a configurable, straight-forward way. This feature is called “Content-Based Access”
(CBA), as the content itself determines whether or not it can be accessed. You can define Content-
Based Access rules in Datamodel Administrator that compare attributes in the metadata model to
predefined values. The Datamodel Administrator will automatically create rights for each rule in
User Management as soon as you activate the data model. For each user group, the administrator now
can define which CBA(s) should be applied. For each group the administrator can apply one or more
CBA rules. If there is more than one rule for a group, all rules are evaluated through an OR operator.
That is, if one rule out of the set of rules for a user group allows the access, then the access is allowed
(although the access may not be allowed by other rules for that group). If the user is in more than one
group, the same principle is valid: If there is one rule out of the set of rules that allows the access,
then access is allowed for this media object.
To support multi-tenancy, it is necessary not only to combine CBA Rules by OR but also by an AND
operator for a group. To secure this, CBA Rules can be assigned at two different levels (“Level 1” and
“Level 2”). When the rules are applied, rules of the same level are combined by an OR operator, but
rules of different levels are combined by an AND operator.
For additional information, see “Working with Content-Based Access” on page 122.
Expressions
Datamodel Administrator allows you to define “expressions.” Using expression you can define
conditions on attribute level that determine the editability or visibility of data model elements:
Depending on the value of object attributes, elements on a metadata template are shown or hidden, or
17
displayed editable or in read-only mode. For example, you can use expressions to control if an
attribute is only editable when it has a specific value or if a process can be launched based on the life
cycle of an object.
For additional information, see “Working with Expressions” on page 130.
Data Model Layout Options
To configure the GUIs for searches, hit lists and display or modification of metadata you can use
Datamodel Administrator's Layout Editor. It offers you a fully configurable, flexible, multi-column
and multi-line grid layout.
Metadata Templates
Datamodel Administrator allows you to define templates configurable per client application, content
type, and user group. They contain the data elements to be used, including field sizes and
multicolumn grid layout. Form definitions can be used for both metadata display and metadata
editing. Each attribute in the metadata form can be defined as mandatory, read-only, or with a default
value. Labels are applied automatically according to the language setting of the respective user.
Fields are presented with suitable edit controls depending on attribute type, including drop-down lists
or pick tools for the selection of preset values, thesaurus terms, or master data.
For additional information, see “Working with Metadata Templates” on page 133.
Search Forms
Interplay MAM offers predefined query forms of different levels of complexity: “Quick search”
searches across all indexed attributes; “Advanced search” searches in selected attributes; “Strata
search” searches in selected strata; and “Combined search” is a combination of these. You can select
attributes and strata to be searched from drop-down lists in the query forms. In addition to the
standard search forms you can configure your own “Custom search” forms, which use a single query
line, attribute query fields, and strata query fields.
Within the individual search forms an “as of” selection list is shown. Using this list the users can
limit the number of hits to be found by selecting the time frame for which a query should apply. The
entries of the “as of” selection list, their labels, and functions can be set in Datamodel Administrator.
For additional information, see “Working with Custom Search Forms” on page 152 and “Working
with Time Restrictions” on page 158.
Hit Lists
The results of a search are displayed in a hit list. Using the Datamodel Administrator you can design
various hit lists. The configuration includes the set of attributes and whether or not a thumbnail is
displayed in the hit list. Multi-level sort orders and layout of the hit list can be specified. You can
specify which hit list templates should be available for which query form; the users can then choose
the hit list template to be used for display of hits.
For additional information, see “Working with Hit Lists” on page 161.
Basic Workflow for Creating a Data Model
When you design a data model in Datamodel Administrator, the following elements have to be
created or adapted.
18
To design a data model:
1. Languages
2. Tenants
3. Aspects
4. Object classes
5. EDL classes
6. Process classes
7. Legal lists
8. Attribute groups
9. Segment content classes
10. Strata
11. Master data classes
12. Thesauri
13. Attributes
14. Essence attributes
15. Associations
16. Content-Bases Access rules
17. Expressions
18. Layouts (Templates, Search forms, Hit lists, Time restrictions)
n
The Datamodel Administrator gives you complete freedom in the sequence in which you design your
data model. Nevertheless, Avid strongly recommends defining the elements in the sequence described
above. If you do not comply with this sequence, your new data model may not work properly.
Starting Datamodel Administrator
Start Datamodel Administrator from the Windows Start menu.
To start Datamodel Administrator and load a data model from server:
1. Do one of the following:
t Select Start > All Programs > Avid > Interplay MAM > DataModelAdministrator.
t Double-click the Datamodel Administrator desktop shortcut, if available.
The Load data model dialog box opens.
19
2. Replace the <localhost> entry with the real host name in the Host field or select the appropriate
Host from the selection list.
3. Type your login name and password.
4. Click OK.
The Open from DataManagerWS dialog opens. Since the Open latest model check box is
checked, the current data model is selected automatically.
5. Click OK.
The Load from data model and Open from DataManagerWS dialogs are closed. The Datamodel
Administrator opens with the current data model loaded from server.
To start Datamodel Administrator and load a data model from file:
1. Start Datamodel Administrator from the Start menu or double-click the Datamodel
Administrator desktop shortcut.
2. Check the Load from file option button and click Browse in the Load data model dialog, then
select the data model (*.xml) and click Open in the Open dialog.
3. Click OK.
The Load data model dialog is closed. The Datamodel Administrator opens and displays the file-
based data model.
To start Datamodel Administrator with an empty data model:
1. Start Datamodel Administrator from the Start menu or double-click the Datamodel
Administrator desktop shortcut.
2. Check the Start with empty data model option button in the Load data model dialog.
3. Click OK.
The Load data model dialog is closed and the Fix inconsistencies in data model dialog opens. It
lists the mandatory default data model values that are missing in the empty data model.
20
4. Click OK.
The Fix inconsistencies in data model dialog is closed. The Datamodel Administrator opens and
displays an empty data model that contains the mandatory default values.
Datamodel Administrator Layout
A layout is a set of panes and controls that is installed with of the Datamodel Administrator
application. The following illustration and table describe the main panes of the Datamodel
Administrator.
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
-
1
-
2
-
3
-
4
-
5
-
6
-
7
-
8
-
9
-
10
-
11
-
12
-
13
-
14
-
15
-
16
-
17
-
18
-
19
-
20
-
21
-
22
-
23
-
24
-
25
-
26
-
27
-
28
-
29
-
30
-
31
-
32
-
33
-
34
-
35
-
36
-
37
-
38
-
39
-
40
-
41
-
42
-
43
-
44
-
45
-
46
-
47
-
48
-
49
-
50
-
51
-
52
-
53
-
54
-
55
-
56
-
57
-
58
-
59
-
60
-
61
-
62
-
63
-
64
-
65
-
66
-
67
-
68
-
69
-
70
-
71
-
72
-
73
-
74
-
75
-
76
-
77
-
78
-
79
-
80
-
81
-
82
-
83
-
84
-
85
-
86
-
87
-
88
-
89
-
90
-
91
-
92
-
93
-
94
-
95
-
96
-
97
-
98
-
99
-
100
-
101
-
102
-
103
-
104
-
105
-
106
-
107
-
108
-
109
-
110
-
111
-
112
-
113
-
114
-
115
-
116
-
117
-
118
-
119
-
120
-
121
-
122
-
123
-
124
-
125
-
126
-
127
-
128
-
129
-
130
-
131
-
132
-
133
-
134
-
135
-
136
-
137
-
138
-
139
-
140
-
141
-
142
-
143
-
144
-
145
-
146
-
147
-
148
-
149
-
150
-
151
-
152
-
153
-
154
-
155
-
156
-
157
-
158
-
159
-
160
-
161
-
162
-
163
-
164
-
165
-
166
-
167
-
168
-
169
-
170
-
171
-
172
-
173
-
174
-
175
-
176
-
177
-
178
-
179
-
180
-
181
-
182
-
183
-
184
-
185
-
186
-
187
-
188
-
189
-
190
-
191
-
192
-
193
-
194
-
195
-
196
-
197
Avid Interplay MAM 5.9 Datamodel Administrator User guide
- Category
- Software
- Type
- User guide
Ask a question and I''ll find the answer in the document
Finding information in a document is now easier with AI
Related papers
-
Avid Interplay MAM 5.9 Control Center User guide
-
-
-
Avid EDL EDL Manager 22.0 User guide
-
-
Avid EDL EDL Manager 4.0 User guide
-
Avid EDL EDL Manager 9.0 User guide
-
Avid EDL EDL Manager 11.x User guide
-
Avid EDL EDL Manager 10.0 User guide
-
Avid EDL EDL Manager 10.2 User guide
