Metadata Extension

Can i in the same portal project add more than one class to metadata extension ? How do i generate the prjconfig file ? I tryed to add another class in the example project bellow but it didn't work.
There is any other thing that i should do ?
What is the schedulertask that is in the src.config folder in the example project ?
What is the IRFServiceWrapper class ?
The following tutorial shows how to implement metadata extension: https://media.sdn.sap.com/html/submitted_docs/nw_kmc/howto/km/metadataextension/Implementing%20a%20Metadata%20Extension%20for%20KMC%20Properties.html

Similar Messages

Custom Metadata Extension with RFC call

Hi all,
I am trying to create a custom metadata extension that pulls data from ECC via an RFC call and returns values as a IMetaValueList in the getAllowedValues method.
Does anybody have any experience?
Thx
Ismail

Hello Sanjeev,
- I Kept External break point in SRM where we are calling RFC Call for ECC, I am able to debug untill the RFC call,
- But, on RFC Call ( CALL FUNCTION ZABC destination <Destination>), when I press F5 it is not going inside the function module.
- I am getting Export parameter values, means ctrl is going to ECC, but not able to debugg our BE system -ECC.
Pls suggest. Thanks for your quick reply.
Regards,
Mohan Vamsi

Ordered - JDO Metadata Extension

I am having problems getting a collection staying ordered after it is
stored.
I', having a class defined this way:

<class name="Group" persistence-capable-superclass="WebSource">
<field name="children">
<collection element-type="WebSource"/>
<extension vendor-name="kodo" key="ordered" value="true"/>
<extension vendor-name="kodo" key="inverse" value="parent"/>
</field>
</class>
Af far as I can read from the documentation, the 'ordered' metadata
extension should guarantee that the collection should stay ordered. Any
suggestions why this isnt the case?
btw, Im using Kodo 2.2.6, SQL server 2000 :)

Benny --
There is currently no support for ordering 1-M relations like the one you describe. Only collections of simple types and 1-sided M-M relations are supported with ordering. We are however, working on 1-M ordering; watch for it in a future release.

Sort metadata extension return list

I have developed a custom metadata extension which I will use for several metadata properties.
As a basis for the metadata extension I used the example (for Dynamic values) provided here:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/unkown/implementing a metadata extension for kmc properties.article
I have extended the example so that it serves for multiple metadata properties and multiple languages.
Now I would like to sort the IMetaValueList returned by
getAllowedValues(IMetaName metaName, IMetaContext metaContext)
I want to sort this list of keys by the labels of the locale in which a user is logged on, so that for instance a dropdownlistbox shows the items in alphabetical order.
I think I can accomplish this by using
metaContext.getResourceContext().getLocale()
to get the locale, and using
sort(Comparator c)
in IMetaValueList with a custom Comparator.
The custom Comparator would compare two keys, based on their corresponding labels (
getValueLabel(IMetaValue metaValue, Locale locale)
However, before I start implementing this, I need to know:
-In custom iViews, currently I use
IMetaValueListIterator allowedValues =metaName.allowedValueIterator();
where metaName is an IMetaName which uses the metadata extension.
For the sort function to work I need to use
allowedValueIterator(IMetaContext metaContext);
How do I get an IMetaContext in my custom portal component?
-Is there another way to sort the IMetaValueList returned by the metadata extension?
Johan

Anyone? Any help will be appreciated...
Johan

Problem: CM properties translation through Metadata Extensions

Hi.
I encountered a problem with CM properties translation using metada extensions.
The translation as it is goes fine, however, sorting does not.
I have a property, that is created in Language1, which has some allowed values. That property is used in one of the xml forms. Its allowed values are displayed in this form sorted accordingly when portal is viewed in Language1.
I added metadata extension, where allowed values from property are translated into Language2.
When portal user swithes to Language2, translation kicks in, but the values are not sorted accordingly in Language2. They remain sorted as they were in their original language - Language1.
Problem: how to make portal (xml form) use the properly sorted property in any chosen language?
Lucas

Hi.
I encountered a problem with CM properties translation using metada extensions.
The translation as it is goes fine, however, sorting does not.
I have a property, that is created in Language1, which has some allowed values. That property is used in one of the xml forms. Its allowed values are displayed in this form sorted accordingly when portal is viewed in Language1.
I added metadata extension, where allowed values from property are translated into Language2.
When portal user swithes to Language2, translation kicks in, but the values are not sorted accordingly in Language2. They remain sorted as they were in their original language - Language1.
Problem: how to make portal (xml form) use the properly sorted property in any chosen language?
Lucas

Existing table metadata extensions ignored

I have tried to use kodo metadata extensions to map objects to existing
tables.
I used extensions from the Kodo documentation example.
First I run schema tool with refresh option and complete schema was
generated (tables with X at the end), as all extension instructions were
ignored.
After that I run schema tool with register option. This time an exception
was thrown showing a SQL statement looking for tables with X at the end.
Again it looks as extension instructions from jdo file were ignored.
Could someone define required steps when using an existing schema and what
should be done so Kodo starts using metadata extensions?
Thanks.

There are no special steps to starting to use metadata extensions. Is it
possible that you have another set of metadata without extensions lying around,
and Kodo is picking that one up?
Or perhaps you could post your metadata, so we can see if there are any
errors in it.

Use of the ordered metadata extension

Hey Kodo,
I noticed your ordered and order-column extensions in the manual. I'd
really, really, really like to use these props for a Vector of child objects
so I don't have to maintain the order column myself. The documentation
mentions however that these properties are not available for 1-many Object
collections but only for collections of simple values etc. Can you tell me
whether future versions of Kodo will support this, and if so, when?
Greetings,
Martin van Dijken

David-
Better yet, this limitation no longer exists in 3.0.
In article <[email protected]>, David Ezzio wrote:
Hi Marc,
It's more than six months later, and this is an important insight that needs to be in your
documentation.
David
Marc Prud'hommeaux wrote:
Martin-
The documentation is a bit misleading: we do support the order column in
relations. The only limitation is that you cannot have the one-to-many
optimization with the "inverse" attribute and use ordering at the same
time. But if you have a join table (or use Kodo's default generated
schema), then you should be able to specify ordering on your relations
just fine.
In article <b2d9o4$cdn$[email protected]>, Martin van Dijken wrote:
Hey Kodo,
I noticed your ordered and order-column extensions in the manual. I'd
really, really, really like to use these props for a Vector of child objects
so I don't have to maintain the order column myself. The documentation
mentions however that these properties are not available for 1-many Object
collections but only for collections of simple values etc. Can you tell me
whether future versions of Kodo will support this, and if so, when?
Greetings,
Martin van Dijken
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

Metadata extensions for validation

Hi all,
I have implemented a IValidation class for some custom logic to validate some predefined properties.
I found that the code is called if the property is set to "Mandatory", but NOT called when the property is not mandatory.
Is this the expected behaviour that only mandatory properties will trigger the IValidation class?

Hi all,
Any helps?

Cannot get Sample Metadata UI Extensions to Show in Adobe Bridge

In the Adobe XMP Metadata UI Developer's Guide it shows:
Viewing the sample panels
To see the results of these definitions in an Adobe application, install the Metadata UI Extension package
in one of the user-specific or general shared resource folders:
MAC OS: [user]/Library/Application Support/Adobe/XMP/Metadata Extensions
/Library/Application Support/Adobe/XMP/Metadata Extensions
When I place the "Sample Extension" files in /Library/Application Support/Adobe/XMP/Metadata Extensions, none of the sample panels appear in Adobe Bridge.
What am I doing wrong?
Help!

Hi David,
    You are using Bridge CC not Bridge CC 2014. The document you are referring will not work for CC.
    You need to follow the earlier documentation (hope you will find on devnet). For your reference I am putting the following code, save it in file name "sample.xml". Put this file on the path where you have installed bridge\Custom File Info Panels\4.0\custom. Restart bridge if it is not visible, check in bridge preferences and check the checkbox.
Code for sample.xml is
<?xml version='1.0' encoding='UTF-8'?>
<xmp_definitions>
<xmp_schema prefix='mypanel' namespace='http://ns.adobe.com/mypanel/' label='$$$/my/FileInfoLib/Panels/Name=mypanel'>
         
        <xmp_property name="Text" category="external" label="$$$/Custom/Panel/Document Title=Property 1 Name:" type="text"/>
        <xmp_property name="Text2" category="external" label="$$$/Custom/Panel/Credit=Property 2 Name:" type="text"/>
        <xmp_property name="Bool1" category='external' label="$$$/Custom/Property/BooleanInput_Label=Check Box Input:" type='boolean'/>
        <xmp_property name="Bool2" category='external' label="$$$/Custom/Property/BooleanInput_Label2=Check Box Input2:" type='boolean'/>
</xmp_schema>
</xmp_definitions>

Managing Metadata in Digital Libraries within Lightroom for Upload to WordPress

I have been researching SEO tips for my clients to build their image libraries and fill in all of the pertinent meta data. Unfortunately, I have not been able to find a workable solution to categorize the images and retain the metadata after uploading to WordPress.
Specifically, I need to know how to add file properties (in a program for a PC or Mac) to your image libraries before you upload them. It appears that Adobe Lightroom, Adobe Bridge and Microsoft PhotoGallery do not retain the alt text and captions after importing into WordPress. Also, there is no access to an 'Alt Text' field in Lightroom. I entered it in PhotoGallery. I also added Lightroom Plug-ins from Rob Cole:
rc Metadata Extensions
rc Custom Metadata
robcole.com
However, I have not been successful in customizing them.
Upon further research, I have found another way, but it requires paying for a subscription based service (Uploading Photos to WordPress with a Lightroom Publish Service):
http://havecamerawilltravel.com/photographer/lightroom-wordpress-publish-service
Another tidbit was the workflow by Scot Kelby, which discusses entering the metadata before uploading to UPI wire service (requires Photo Mechanic software):
http://scottkelby.com/2012/my-sports-photography-workflow-so-far/
So, I am still searching for the complete solution. Technically speaking, it sounds like it is an issue with WordPress to read the data in the image and map it to the alt text and caption fields. The WordPress plugin appears to allow the creation of new fields in the MySQL database and create a function to route the metadata. I am surprised that this had not been resolved by professional archivers.
This is a task I have left to my client and I am in the process of building a cheat sheet for SEO labeling of images, which is also helpful in placing them in documents and presentations. Advice and best practices would be welcome.
Thank you.

macorin wrote:
I'm looking for some feedback as to the benefits of allowing Aperture to manage those videos.
Aperture was not designed as, and does not excel as, a video storage, editing, and publishing workshop. My guess is that video was added in because it could be, not because users wanted it. My experience was that video tended to mung-up the works with 3.0. One of the upgrades has resolved those issues, but video remains nothing more than a limp tangent away from Aperture's core.
As as side question, if I were to continue managing video within Aperture, does it make sense in anyone's opinion to keep those videos in the same projects, etc as my image files?
Absolutely. Set one of each view's metadata overlays to show badges. Video has its own badge. Also, you might set the Poster Frame of each clip to show some text (the title, for instance) as a visual indication that the Preview is a video.

Extension does not exist : File - XI - IDOC

Hello,
I have an IDOC MATMAS03 with an extension, so called
MATMASA03.ZMATMASX
IDX2 - metadata upload done more than once ! OK
mapping from file to IDOC: test ok (Name of Interface ZMATX.MATMAS03.ZMATMASX)
config: test of communication from file system to R/3 with IDOC payload: OK
Process running results in an error:
Attribute IDOC Metadata, Extension ZMATMASX does not exist.
System is running on SP14!
Does anybody here have experience with extensions in IDOCs or knows about this problem?
Lot of thanks for any help!
regards
Dirk

Hi Dirk,
you can also have a look at idoc receiver channel
PORT: SAPXXX
is this the same port that you have your idoc metadata
downloaded in IDX2 ?
worth to check I guess
Regards,
michal

How to get Meta Data Extension value?

Hello,
I created a new property in KM and set "Meta Data Extension" field that points to some bundle class file for Labels for this property.
How can I get the value of this "Meta Data Extension" field or, to be more exactly, this bundle class in my property renderer code?
I'll be very much appreciated for your help.

Hello Sergei,
IMetaName getLabel will give you the label out your bundle file if you've set the metadata extension and the bundle key in the metadata property configuration. There is no API that exposes the metadata extension information. It's only used inside the property configuration service.
For more information about how tho customize labels of KM attributes see the documentation:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/65/6fc63ed4027f6be10000000a114084/frameset.htm">Changing Labels for Properties</a>
Regards
Lars

Kodo 3.0 migrator does not honor metadata table/column names

it outputs <field_name>X instead completely disregarding what's in the
metadata

Ok running it on classess enhanced with 2.5.2 produces bad names, while
runnung it on unenhanced classed works all right
<mapping>
<package name="peacetech.nci.cs.jdo">
<class name="Contract">
<jdbc-class-map type="base" table="CONTRACTX"/>
<jdbc-version-ind type="version-number" column="JDOLOCKX"/>
<jdbc-class-ind type="in-class-name" column="JDOCLASSX"/>
<field name="currentModification">
<jdbc-field-map type="one-one"
column.CONTRACTIDX="CONTRACTID_CURRENTMODIFICATIOX"
column.MODIFICATIONIDX="MODIFICATIONID_CURRENTMODIFICX"/>
</field>
<field name="id">
<jdbc-field-map type="value" column="IDX"/>
</field>
<field name="lastModification">
<jdbc-field-map type="one-one"
column.CONTRACTIDX="CONTRACTID_LASTMODIFICATIONX"
column.MODIFICATIONIDX="MODIFICATIONID_LASTMODIFICATIX"/>
</field>
<field name="modifications">
<jdbc-field-map type="many-many"
element-column.CONTRACTIDX="CONTRACTID_MODIFICATIONSX"
element-column.MODIFICATIONIDX="MODIFICATIONID_MODIFICAT
IONSX" ref-column.IDX="ID_JDOIDX" table="CONTRACT_MODIFICATIONSX"/>
</field>
</class>
<class name="Modification">
<jdbc-class-map type="base" table="MODIFICATIONX"/>
<jdbc-version-ind type="version-number" column="JDOLOCKX"/>
<jdbc-class-ind type="in-class-name" column="JDOCLASSX"/>
<field name="approved">
<jdbc-field-map type="value" column="APPROVEDX"/>
</field>
<field name="contract">
<jdbc-field-map type="one-one" column.IDX="ID_CONTRACTX"/>
</field>
<field name="contractId">
<jdbc-field-map type="value" column="CONTRACTIDX"/>
</field>
<field name="description">
<jdbc-field-map type="value" column="DESCRIPTIONX"/>
</field>
<field name="modificationId">
<jdbc-field-map type="value" column="MODIFICATIONIDX"/>
</field>
<field name="obligations">
<jdbc-field-map type="many-many"
element-column.IDX="ID_OBLIGATIONSX"
ref-column.CONTRACTIDX="CONTRACTID_JDOIDX" ref-column.MODIFICATIONIDX="MOD
IFICATIONID_JDOIDX" table="MODIFICATION_OBLIGATIONSX"/>
</field>
</class>
<class name="Obligation">
<jdbc-class-map type="base" table="OBLIGATIONX"/>
<jdbc-version-ind type="version-number" column="JDOLOCKX"/>
<jdbc-class-ind type="in-class-name" column="JDOCLASSX"/>
<field name="amount">
<jdbc-field-map type="value" column="AMOUNTX"/>
</field>
<field name="id">
<jdbc-field-map type="value" column="IDX"/>
</field>
<field name="modification">
<jdbc-field-map type="one-one"
column.CONTRACTIDX="CONTRACTID_MODIFICATIONX"
column.MODIFICATIONIDX="MODIFICATIONID_MODIFICATIONX"/>
</field>
</class>
</package>
</mapping>
running on unenhanced classes produces proper metadata (as far as names
concerned)
<?xml version="1.0" encoding="UTF-8"?>
<mapping>
<package name="peacetech.nci.cs.jdo">
<class name="Contract">
<jdbc-class-map type="base" table="CONTRACT"/>
<jdbc-version-ind type="version-number" column="JDO_LOCK"/>
<field name="currentModification">
<jdbc-field-map type="one-one"
column.CONTRACT_ID="CONTRACT_ID"
column.MODIFICATION_ID="CURRENT_MODIFICATION_ID"/>
</field>
<field name="id">
<jdbc-field-map type="value" column="CONTRACT_ID"/>
</field>
<field name="lastModification">
<jdbc-field-map type="one-one"
column.CONTRACT_ID="CONTRACT_ID"
column.MODIFICATION_ID="LAST_MODIFICATION_ID"/>
</field>
<field name="modifications">
<jdbc-field-map type="one-many"
ref-column.CONTRACT_ID="CONTRACT_ID" table="MODIFICATION"/>
</field>
</class>
<class name="Modification">
<jdbc-class-map type="base" table="MODIFICATION"/>
<jdbc-version-ind type="version-number" column="JDO_LOCK"/>
<field name="approved">
<jdbc-field-map type="value" column="IS_APPROVED"/>
</field>
<field name="contract">
<jdbc-field-map type="one-one"
column.CONTRACT_ID="CONTRACT_ID"/>
</field>
<field name="contractId">
<jdbc-field-map type="value" column="CONTRACT_ID"/>
</field>
<field name="description">
<jdbc-field-map type="value" column="DESCRIPTION"/>
</field>
<field name="modificationId">
<jdbc-field-map type="value" column="MODIFICATION_ID"/>
</field>
<field name="obligations">
<jdbc-field-map type="one-many"
ref-column.CONTRACT_ID="CONTRACT_ID"
ref-column.MODIFICATION_ID="MODIFICATION_ID" table="OBLIGATION"/>
</field>
</class>
<class name="Obligation">
<jdbc-class-map type="base" table="OBLIGATION"/>
<jdbc-version-ind type="version-number" column="JDO_LOCK"/>
<field name="amount">
<jdbc-field-map type="value" column="AMOUNT"/>
</field>
<field name="id">
<jdbc-field-map type="value" column="OBLIGATION_ID"/>
</field>
<field name="modification">
<jdbc-field-map type="one-one"
column.CONTRACT_ID="CONTRACT_ID" column.MODIFICATION_ID="MODIFICATION_ID"/>
</field>
</class>
</package>
</mapping>
"Patrick Linskey" <[email protected]> wrote in message
news:[email protected]...
Yes; see
http://solarmetric.com/Software/beta/3.0.0/b1-docs/docs/ref_guide_mapping_factory.html
for descriptions of the various options.
The three basic ways to store mapping information are: in metadata
extensions, in the database, and in separate .mapping files. IMO, storing
in separate .mapping files is the best -- storing the info in metadata
makes your metadata get really ugly, and storing it in the db makes it
relatively hard to modify (at least, until we release our GUI tool...)
-Patrick
On Mon, 04 Aug 2003 19:38:16 -0400, Alex Roytman wrote:
can mapping files be used as an alternative to jdo extensions to
complement standard jdo metadata or it is strictly for mapping tool? in
other words can I have a standard jdo metadata with no extensions plus a
mapping file to replace jdo metadata with extensions if yes, what is
your primary format two file (jdo + mapping file) or one file jdo with
extensions--
Patrick Linskey
SolarMetric Inc.
"Patrick Linskey" <[email protected]> wrote in message
news:[email protected]...
Can you post the command that you used to run the conversion? I just ran
through the conversion process for a small (10 tables or so) schema
earlier today with no problems.
-Patrick
On Mon, 04 Aug 2003 19:31:06 -0400, Alex Roytman wrote:
it outputs <field_name>X instead completely disregarding what's in the
metadata--
Patrick Linskey
SolarMetric Inc.

Am I Installing the Metadata UI Package Correctly?

I downloaded the XMP Metadata UI SDK CC 2014 and per the instructions in the pdf, "To see the results of these definitions in an Adobe application, install the Metadata UI Extension package
in one of the user-specific or general shared resource folders:" I copied (although the instructions say install) these files:
loc folder
schema folder
view folder
manifest.xml
to both of these locations:
WINDOWS: [user]\AppData\Roaming\Adobe\XMP\Metadata Extensions
C:\Program Files (x86)\Common Files\Adobe\XMP\Metadata Extensions
Then launched Photoshop, chose File -> File Info
And I see nothing new in the File Info panel.
What am I missing?
Thanks,

Thanks for the reply Jörg,
I have now place theses files:
loc folder
schema folder
view folder
manifest.xml
in a sub-directory called padam as you mentioned, so the full path is:
WINDOWS: [user]\AppData\Roaming\Adobe\XMP\Metadata Extensions\padam\...
I have not made any changes to the files in the loc, schema, view folders, or to the manifest.xml I downloaded from the Adobe website.
I still see nothing when I bring up the FileInfo panel in Photoshop.
Are there other changes I would need to make in order to see the sample extension show up in Photoshop?
For example, would I need to somehow change the locFilePrefix in the manifest.xml file?
<extension xmlns="http://ns.adobe.com/metadata/extension/1.0/"
   name="com.adobe.sample.extension"
   version="1.0"
   locFilePrefix="sample">
</extension>
Also, in the sampleSchema.xml, would I have to change any of these items in bold:
<xmp_schema prefix='sampleSchema' namespace='http://my.sampleSchema.namespace/' label='Sample Schema for Demonstration' description='This example demonstrates how a new schema can be created'>
<xmp_property name='Boolean' category='external' type='boolean' label="$$$/sampleSchema/Property/BooleanInputLabel=Boolean Field1" description='$$$/sampleSchema/Property/BooleanInputDescription=Defining Boolean data type'/>
Are there other things I'll have to change in the view folder to get the sample to work?
I guess when I downloaded the SDK and saw "Sample Extension", I was expecting it to work with no interaction on my part just to see the sample. Obviously, I knew I'd have to alter everything to make my own Custom extension.
Thanks for any help you can provide, I really appreciate it!
- Bill

Exif metadata not displayed in Metadata panel & searching

Is there a way to customize the exif and/or IPTC data shown in the Metadata panel in LR 5?
And is there a way to search and/or filter on metadata not in that panel?
I needed to find some photos that have the exif category "art filter" and I cannot search for the value in that field in LR, nor does that field show up in the metadata panel. I can see it with J. Friedl's metadata plugin, or in GraphicConverter, so I know it's there. I tried searching on the text, but LR doesn't find it. What I'd really love is the feature where you have the little arrow by the metadata value in the panel and click it to filter by that criteria.
Is there a way to get LR to recognize and display other exif or IPTC data?

I'm not sure which metadata field you want to search -- is it the IPTC field "Category"? That field is displayed in Metadata > IPTC panel in the right column:
Unfortunately, that field is not searchable using LR's text search filter or smart collections.
In general, to view and search metadata fields not fully handled by LR, you've got to use a third-party plugin:
- Metadata Extensions makes additional fields that LR knows about searchable using the filter bar and smart collections.
- ExifMeta makes nearly all metadata fields viewable and searchable in LR.
- Data Explorer lets you more quickly view, search, and browse more of the fields that LR knows about.
- Any Filter lets you search any field LR knows about, writing boolean search queries similar to smart collections.
These plugins have different capabilities and are optimized for different use cases.

Metadata Extension

Similar Messages

Maybe you are looking for