Associating an existing metadata extractor to new extension

[sergio]

Hi all.

I would like to know how it is possible to associate an already existing metadata extractor to a file with a proprietary extension (for which it has sense to extract specific metadata).

For example, suppose I have a file whith extension .prop for which I am sure that some existing metadata could be extracted.

Many thanks to everyone.

Sergio

[ribz33]

I have exactly same problem…
I have a rule who apply for all content my custom aspect but extracter is not able to write extracted data to my custom aspect.
Althought, extracter is able to write extracted data to "standard" properties.
I take care to give right Qname but its not working…
:?

[derek]

Hi,

I'll check with a unit test.

In the mean time, have a look at the latest version of OfficeMetadataExtracter.  The infrastructure is in place that your extracter can extract any and all properties, calling them whatever you want.  You then supply default mapping properties from the extracter-named properties to the Alfresco maintained properties.  So you won't need to hard code the QNames in your extracters.

Regards

[ribz33]

Hi Derek,

Its working now.
stebans found solution…
Custom metadata extractor works only if you create rule "Extract common metadata…"

I don't know why (maybe you are more able to anwser ) but like this its working.

Thx a lot

Best regards

[derek]

Hi,

Sorry, I just assumed that you were triggering the extraction with the rule.      Metadata extraction is not something all systems need, and even those that do will probably only need it in certain locations within the document structure.  Hence, it has to be triggered with a rule, which can be applied on the Company Home if needs be.

Regards

[shmoula]

Hooray, finally solved!!  😎  Thanks, guys!

btw why this fact (to trigger some rule) is not noted in "extractors…" in wiki? I think this is really important thing!!  :shock: