advanced concepts in metadata properties in km

8/3/2019 Advanced Concepts in MEtadata Properties in KM

1/39

Advanc ed c oncept s inMet adat a p roper t ies in K M.

Lar ry Bram brut , SAP NetWeaver RIG US


2/39

SAP AG 2004, SAP TechEd / KM251 / 2

What th is sess ion 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 (forexample: "External Presentation") and automatically associatedcertain metadata with that document(for example, "Audience: customer or partner).

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


3/39


Learning Object ives

As a result of this workshop, you will

be able to:

n Configure Item Types (Resource Types)

n Configure Dependent Properties


4/39


Agenda

OverviewItem Types

Dependent Properties

Summary


5/39


Propert ies 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 userswhich define metadata for folders and documents.

n Custom Properties: Also created by the users but entered on the fly asfree 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


6/39


Propert ies in Flex -UI/Detai ls


7/39


Proper t i es can be used t o ref ine a Search


8/39


Proper t i es c an be used in Query Based Taxonom ies


9/39


Propert ies: Propert y Servic es

n Two services available:

u Property Metadata Serviceu Property Structure Service

n All necessary configurations can be done in the KM ConfigUI

n The settings take effect immediately (Hot Reload)


10/39


Agenda

OverviewItem Types


Summary


11/39


I tem Type Exam ple

User chooses the item type when uploading or creating new resources

When changing the item type, theappropriate property structures will bedisplayed


12/39


I tem Type Exam ple

Details screen


13/39


I t em Type Conf igurat ion St eps

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\WEB-INF\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

nCreate Properties & Property StructureuCreate Property Metadata Namespace

uCreate Property Metadata Group

uCreate Properties

uCreate Property Structure Group

uCreate Property Structure (with reference to Resource Type)

n Create Details Property Structure

n Create Details Screen


14/39


I t em t ype hand li ng (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 usercannot create a document with this item type using UI, e.g. Upload


15/39


I t em t ype handl ing (2)

Define Properties & Properties Structure

nCreate 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


16/39



User chooses the item type when uploading or creating new resources

When changing the item type, theappropriate property structures will bedisplayed

Item Type

Property Structure


17/39



Details screen for an item type

nCreate a properties structure for details properties page

(DevelopmentDetailsProperties) underUser Interface -> Details Properties -> DetailsProperty 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


18/39



Details Properties with corresponding Item Type

Details Property Structure


19/39


Demo

Demo


20/39


Agenda

Overview

Item Types


Summary


21/39


Documentat ion

How to Configure Predefined Properties with Dependent Values

December 27, 2004 Created by Michael Kronfeld, Public Release

SAP NetWeavers Knowledge Management offers you the possibilityof using properties with interdependent values. When you determinethe value of a property, the values of other properties can vary

according to the value you choose. The How-to guide shows youhow to proceed if you want to integrate a new tab listing theproperties Country and City in the Details dialog box of a document.


22/39


Ex ample: Ci t y is dependent on Country

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


23/39


Dependent Proper t ies - Conf igurat ion St eps

n Create Properties

uCreate Property Metadata GroupuCreate 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

uCreate Property Structure Groupsl Group for (Country/City)

l Update all_groups (with Country/City group)


24/39


Proc edure for Creat ing Dependent Propert ies

Navigate to the Property Metadata Service


25/39



Create a group for your properties (Namespace if optional)


26/39



Navigate to Properties


27/39



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


28/39



Create the the Holding Property City


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


29/39



Create Sub-Properties (onefor each set of country/cities)

In our example, three propertiesare created: GermanCity,FrenchCity, SpanishCity


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


30/39



Navigate to the Property Structure Service


31/39



Creating Property Groups for a Property Structure


32/39


Resul t : Ci t y is dependent on Count ry

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


33/39


Mult i -Valued select ions

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

Alternative Usage:

To permit multiple values,you have to activate theparameter Multi-Valuedin the configuration of theproperties CountryandCity.

All values of theproperties arethen depicted ascheckboxes in the Detailsdialog box.


34/39


Resul t : Ci t y and Count ry are Mult i -valued

No country selected One country selected

Multiple countries selected


35/39


Demo

Demo


36/39


Agenda

Overview

Item Types


Summary


37/39


Summary

n Configure Item Types (Resource Types)

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

n Configure Dependent PropertiesDependent properties allow you to create properties that dependon another property. For instance, a property called City (thatdisplays a specific list of Cities) is dependent a property calledCountry.


38/39


Q& A

Quest ions?


39/39


nNo part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission of SAP AG. The information contained herein may be changed without prior notice.

nSome software products marketed by SAP AG and its distributors contain proprietary software components of other

software vendors.

nMicrosoft, 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 orregistered trademarks of IBM Corporation in the United States and/or other countries.

nOracle is a registered trademark of Oracle Corporation.

nUNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

nCitrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered

trademarks of Citrix Systems, Inc.nHTML, 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 andimplemented by Netscape.

nMaxDB is a trademark of MySQL AB, Sweden.

nSAP, 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 othercountries all over the world. All other product and service names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informational purposes only. National product specifications may vary.

nThese materials are subject to change without notice. These materials are provided by SAP AG and its affiliatedcompanies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Groupshall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products andservices are those that are set forth in the express warranty statements accompanying such products and services, i f any.Nothing herein should be construed as constituting an additional warranty.

Copyr ight 2005 SAP AG. Al l Right s Reserved

advanced concepts in metadata properties in km

Documents