manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <>
Subject [jira] [Commented] (CONNECTORS-1071) The windows Shares connector needs some improvement in dates and other fields management
Date Tue, 14 Oct 2014 10:24:34 GMT


Karl Wright commented on CONNECTORS-1071:

I'm afraid that changing the names of metadata for a connector can't be done in 1.8, because
that would break backwards compatibility.  Addition of metadata *only* is permitted in 1.x.
 For 2.x, we could do the entire patch.

For 1.x, you can use the Metadata Adjuster transformer to rename the metadata to whatever
you want.

Please let me know if changing 2.0 is sufficient to meet your needs.

> The windows Shares connector needs some improvement in dates and other fields management
> ----------------------------------------------------------------------------------------
>                 Key: CONNECTORS-1071
>                 URL:
>             Project: ManifoldCF
>          Issue Type: Improvement
>          Components: JCIFS connector
>    Affects Versions: ManifoldCF 1.7
>            Reporter: Antonio David PĂ©rez Morales
>            Assignee: Karl Wright
>            Priority: Minor
>             Fix For: ManifoldCF 1.8
>         Attachments: CONNECTORS-1071.patch
> Right now the connector is overwriting the tika metadata "creation_date" and "last_modification_Date"
for a document. This is happening because at a Windows Shares level you have a creation_date
and a last_modification_date (related to the creation of the document in the windows shares
filesystem) that are different from the creation_date and the last_modification_date associated
to the original file.
> There is the need to change the metadata name to distinguish between this 2 layers of
dates and guaranteeing flexibility to the user to use the one that he/she wants with a proper
> A plus can be to format the date in the lucene standard, to be aligned with a proper
> - Url metadata :
> Can be useful to extract the Url and store it in a specific metadata ( further than the
ID of the document). In this way we can keep it as Id but also use it with other mappings
without affecting the Id field.
> - Parent Directory path :
> Can be useful to extract the Path for the directory that contains the current file. Evaluate
well this as can be a redundancy or an improvement.

This message was sent by Atlassian JIRA

View raw message