Advanced concepts in Metadata properties in KM.

Larry Brambrut, SAP NetWeaver RIG US

What this session is about

This session will provide some advanced concepts in Metadata properties in KM. "Resource Types" enable you to pre-define a type of document (for example: "External Presentation") and automatically associated certain metadata with that document (for example, "Audience: customer or partner). Dependent properties allow you to create properties that depend on another property. For instance, a property called City (that displays a specific list of Cities) is dependent a property called Country.

SAP AG 2004, SAP TechEd / KM251 / 2

Learning Objectives

As a result of this workshop, you will be able to:

n Configure Item Types (Resource Types) n Configure Dependent Properties

SAP AG 2004, SAP TechEd / KM251 / 3

Agenda

Overview Item Types Dependent Properties Summary

SAP AG 2004, SAP TechEd / KM251 / 4

Properties Overview
There are four types of properties used in CM: n System Properties: Author, Create date, modified date, etc.
n Application Properties: Subscription info, Feedback, Rating etc. n Predefined Properties: Properties created by content managers and users which define metadata for folders and documents. n Custom Properties: Also created by the users but entered on the fly as free text for a document and folder.

Properties are used to: n Display metadata on the Flexible-UI and Details Screens
n Refine a Search n Create Queries for Query Based Taxonomies

SAP AG 2004, SAP TechEd / KM251 / 5

Properties in Flex-UI/Details

SAP AG 2004, SAP TechEd / KM251 / 6

Properties can be used to refine a Search

SAP AG 2004, SAP TechEd / KM251 / 7

Properties can be used in Query Based Taxonomies

SAP AG 2004, SAP TechEd / KM251 / 8

Properties: Property Services

n Two services available:
u u

Property Metadata Service Property Structure Service

n All necessary configurations can be done in the KM ConfigUI n The settings take effect immediately (Hot Reload)

SAP AG 2004, SAP TechEd / KM251 / 9

Agenda

Overview Item Types Dependent Properties Summary

SAP AG 2004, SAP TechEd / KM251 / 10

Item Type Example

User chooses the item type when uploading or creating new resources

When changing the item type, the appropriate property structures will be displayed

SAP AG 2004, SAP TechEd / KM251 / 11

Item Type Example

Details screen

SAP AG 2004, SAP TechEd / KM251 / 12

Item Type Configuration Steps

n Create a resource bundle file for labeling Item Types (For details, see the documentation or readme.txt in ...\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEBINF\portal\portalapps\com.sap.km.common.resourcebundle\lib) n Store an icon GIF (in ...\SYS\global\config\cm\etc\public\mimes\images) n Create Resource Types, which correspond to Item Types n Create Properties & Property Structure
u Create

Property Metadata Namespace u Create Property Metadata Group

u Create

Properties u Create Property Structure Group

u Create

Property Structure (with reference to Resource Type)

n Create Details Property Structure n Create Details Screen

SAP AG 2004, SAP TechEd / KM251 / 13

Item type handling (1)

Resource Type Service (Global service)
n Used for registering all the item types n normalrt, normalct - default item types for normal documents/folders n Configuration parameters

Bundle file bundle file for the item description Icon - the icon which will be displayed in navigation iView for that document Key for Description key identifying description in the bundle file Resource Type ID the id for the item type Is for a Collection item type only applies to collections Reserved for Application flag set for all item types which belong to an application; the user cannot create a document with this item type using UI, e.g. Upload

SAP AG 2004, SAP TechEd / KM251 / 14

Item type handling (2)

Define Properties & Properties Structure
n Create properties for a defined item type ( dev:Department, dev:Release) n Create a property structure group with those properties

n Create a property structure for that item type

SAP AG 2004, SAP TechEd / KM251 / 15

Item type handling (3)

User chooses the item type when uploading or creating new resources

When changing the item type, the appropriate property structures will be displayed

Item Type

Property Structure

SAP AG 2004, SAP TechEd / KM251 / 16

Item type handling (4)

Details screen for an item type
nCreate a properties structure for details properties page (DevelopmentDetailsProperties) underUser Interface -> Details Properties -> Details Property Structure

nCreate a details screen instance for that item type using User Interface -> Details Screen This instance should have in Details Properties field the Development details properties

SAP AG 2004, SAP TechEd / KM251 / 17

Item type handling (5)

Details Properties with corresponding Item Type

Details Property Structure

SAP AG 2004, SAP TechEd / KM251 / 18

Demo

Demo

SAP AG 2004, SAP TechEd / KM251 / 19

Agenda

Overview Item Types Dependent Properties Summary

SAP AG 2004, SAP TechEd / KM251 / 20

Documentation
How to Configure Predefined Properties with Dependent Values December 27, 2004 Created by Michael Kronfeld, Public Release SAP NetWeavers Knowledge Management offers you the possibility of using properties with interdependent values. When you determine the value of a property, the values of other properties can vary according to the value you choose. The How-to guide shows you how to proceed if you want to integrate a new tab listing the properties Country and City in the Details dialog box of a document.

SAP AG 2004, SAP TechEd / KM251 / 21

Example: City is dependent on Country

Select a Country and get a list of cities to select in that country.

SAP AG 2004, SAP TechEd / KM251 / 22

Dependent Properties - Configuration Steps

n Create Properties
u Create

Property Metadata Group u Create Properties

l Base Property (Country: values Germany, France, Spain) l Holding Property (City: No values) l Sub-Properties (GermanCity, FrenchCity, SpanishCity) with values for cities u Create

Property Structure Groups

l Group for (Country/City) l Update all_groups (with Country/City group)

SAP AG 2004, SAP TechEd / KM251 / 23

Procedure for Creating Dependent Properties

Navigate to the Property Metadata Service

SAP AG 2004, SAP TechEd / KM251 / 24

Procedure for Creating Dependent Properties

Create a group for your properties (Namespace if optional)

SAP AG 2004, SAP TechEd / KM251 / 25

Procedure for Creating Dependent Properties

Navigate to Properties

SAP AG 2004, SAP TechEd / KM251 / 26

Procedure for Creating Dependent Properties

Specify the following parameters: Unique ID = HTG-Country Property ID = Country Type = String Group = HTG-origin Maintainable = activated Dependencies = activated Allowed Values = Germany, France, Spain

Create the Base Property Country

SAP AG 2004, SAP TechEd / KM251 / 27

Procedure for Creating Dependent Properties

Specify the following parameters: Unique ID = HTG-City Property ID = City Type = String Group = HTG-origin Maintainable = activated Additional Metadata = dependOn=Country, Germany = GermanCity, France=FrenchCity, Spain=SpanishCity Property Renderer = multi_dependence

Create the the Holding Property City

SAP AG 2004, SAP TechEd / KM251 / 28

Procedure for Creating Dependent Properties

Specify the following parameters: Unique ID = HTG-GermanCity Property ID = GermanCity Type = String Group = HTG-origin Maintainable = deactivated Allowed Values = Walldorf, Berlin, Frankfurt, Hamburg

Create Sub-Properties (one for each set of country/cities) In our example, three properties are created: GermanCity, FrenchCity, SpanishCity

SAP AG 2004, SAP TechEd / KM251 / 29

Procedure for Creating Dependent Properties

Navigate to the Property Structure Service

SAP AG 2004, SAP TechEd / KM251 / 30

Procedure for Creating Dependent Properties

Creating Property Groups for a Property Structure

SAP AG 2004, SAP TechEd / KM251 / 31

Result: City is dependent on Country

Select a Country and get a list of cities to select in that country.

SAP AG 2004, SAP TechEd / KM251 / 32

Multi-Valued selections
Alternative Usage: To permit multiple values, you have to activate the parameter Multi-Valued in the configuration of the properties Country and City. All values of the properties are then depicted as checkboxes in the Details dialog box.

Select Multi-valued as a Property setting for the Country and City.

SAP AG 2004, SAP TechEd / KM251 / 33

Result: City and Country are Multi-valued

No country selected

One country selected

Multiple countries selected

SAP AG 2004, SAP TechEd / KM251 / 34

Demo

Demo

SAP AG 2004, SAP TechEd / KM251 / 35

Agenda

Overview Item Types Dependent Properties Summary

SAP AG 2004, SAP TechEd / KM251 / 36

Summary
n Configure Item Types (Resource Types)
"Resource Types" enable you to pre-define a type of document (for example: "External Presentation") and automatically associated certain metadata with that document (for example, "Audience: customer or partner).

n Configure Dependent Properties

Dependent properties allow you to create properties that depend on another property. For instance, a property called City (that displays a specific list of Cities) is dependent a property called Country.

SAP AG 2004, SAP TechEd / KM251 / 37

Questions?

Q&A
SAP AG 2004, SAP TechEd / KM251 / 38

Copyright 2005 SAP AG. All Rights Reserved

n No part of this publication may be reproduced or transmitted in any form or for any purpose without the express

permission of SAP AG. The information contained herein may be changed without prior notice.
n Some software products marketed by SAP AG and its distributors contain proprietary software components of other

software vendors.
n Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. n IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,

pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries.
n Oracle is a registered trademark of Oracle Corporation. n UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. n Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered

trademarks of Citrix Systems, Inc.

n HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium,

Massachusetts Institute of Technology.

n Java is a registered trademark of Sun Microsystems, Inc. n JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and

implemented by Netscape.
n MaxDB is a trademark of MySQL AB, Sweden. n SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein

as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
n These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated

companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
SAP AG 2004, SAP TechEd / KM251 / 39