You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@manifoldcf.apache.org by Furkan KAMACI <fu...@gmail.com> on 2017/03/09 18:13:48 UTC

Linking E-Mail and Its Attachments

Hi,

Currently, E-mail and its attachments are indexed individually. However, we
should link them somehow because there is not a direct link between them
(one can not access to parent - e-mail or child - attachment from one to
other).

First of all, when we index e-mail documents, we have optional metadata
fields for attachments:

Encoding of Attachment
Mime type of attachment

it may be useful to store name of attachments (also ids of attachments) to
softly link them. I used the term 'softly', because a hardly linked
solution is similar to nested documents of Solr but it may break the
 genericness.

What do you think about it?

Kind Regards,
Furkan KAMACI

Re: Linking E-Mail and Its Attachments

Posted by Cihad Guzel <cg...@gmail.com>.
Hi,

Actually, I need similar feature. It may be better to improve in that way.

Regards,
Cihad Guzel


2017-04-05 20:47 GMT+03:00 Furkan KAMACI <fu...@gmail.com>:

> Hi Karl,
>
> Similar systems to ManifoldCF link emails and its attachments. Let's assume
> that one selected Elasticsearch as output connector. One cannot access to
> original document (or cannot have necessary information to access it) when
> he/she makes a search and if it hits to an attachment.
>
> I've come up with an idea about what we can do about that problem within
> ManifoldCF with its restrictions. We should add these metadata:
>
> To Attachment:
>
>    - From
>    - To
>    - Date
>
> (metadata of email it belongs to)
>
> To Email:
>
>    - Filename of attachments
>
> So, one can get necessary information about the email of attachment and
> vice versa.
>
>
> Kind Regards,
> Furkan KAMACI
>
>
>
> On Thu, Mar 9, 2017 at 8:21 PM, Karl Wright <da...@gmail.com> wrote:
>
> > What URL is used for the attachments?  If the URL contains a way to get
> to
> > the primary document then there would not be any need for any other kind
> of
> > linkage.
> >
> > I have no problem with adding more of the metadata for attachments to the
> > attachment RepositoryDocument but I don't see offhand how this can help.
> >
> > Karl
> >
> >
> >
> > On Thu, Mar 9, 2017 at 1:13 PM, Furkan KAMACI <fu...@gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > > Currently, E-mail and its attachments are indexed individually.
> However,
> > we
> > > should link them somehow because there is not a direct link between
> them
> > > (one can not access to parent - e-mail or child - attachment from one
> to
> > > other).
> > >
> > > First of all, when we index e-mail documents, we have optional metadata
> > > fields for attachments:
> > >
> > > Encoding of Attachment
> > > Mime type of attachment
> > >
> > > it may be useful to store name of attachments (also ids of attachments)
> > to
> > > softly link them. I used the term 'softly', because a hardly linked
> > > solution is similar to nested documents of Solr but it may break the
> > >  genericness.
> > >
> > > What do you think about it?
> > >
> > > Kind Regards,
> > > Furkan KAMACI
> > >
> >
>

Re: Linking E-Mail and Its Attachments

Posted by Furkan KAMACI <fu...@gmail.com>.
Hi Karl,

Similar systems to ManifoldCF link emails and its attachments. Let's assume
that one selected Elasticsearch as output connector. One cannot access to
original document (or cannot have necessary information to access it) when
he/she makes a search and if it hits to an attachment.

I've come up with an idea about what we can do about that problem within
ManifoldCF with its restrictions. We should add these metadata:

To Attachment:

   - From
   - To
   - Date

(metadata of email it belongs to)

To Email:

   - Filename of attachments

So, one can get necessary information about the email of attachment and
vice versa.


Kind Regards,
Furkan KAMACI



On Thu, Mar 9, 2017 at 8:21 PM, Karl Wright <da...@gmail.com> wrote:

> What URL is used for the attachments?  If the URL contains a way to get to
> the primary document then there would not be any need for any other kind of
> linkage.
>
> I have no problem with adding more of the metadata for attachments to the
> attachment RepositoryDocument but I don't see offhand how this can help.
>
> Karl
>
>
>
> On Thu, Mar 9, 2017 at 1:13 PM, Furkan KAMACI <fu...@gmail.com>
> wrote:
>
> > Hi,
> >
> > Currently, E-mail and its attachments are indexed individually. However,
> we
> > should link them somehow because there is not a direct link between them
> > (one can not access to parent - e-mail or child - attachment from one to
> > other).
> >
> > First of all, when we index e-mail documents, we have optional metadata
> > fields for attachments:
> >
> > Encoding of Attachment
> > Mime type of attachment
> >
> > it may be useful to store name of attachments (also ids of attachments)
> to
> > softly link them. I used the term 'softly', because a hardly linked
> > solution is similar to nested documents of Solr but it may break the
> >  genericness.
> >
> > What do you think about it?
> >
> > Kind Regards,
> > Furkan KAMACI
> >
>

Re: Linking E-Mail and Its Attachments

Posted by Karl Wright <da...@gmail.com>.
What URL is used for the attachments?  If the URL contains a way to get to
the primary document then there would not be any need for any other kind of
linkage.

I have no problem with adding more of the metadata for attachments to the
attachment RepositoryDocument but I don't see offhand how this can help.

Karl



On Thu, Mar 9, 2017 at 1:13 PM, Furkan KAMACI <fu...@gmail.com>
wrote:

> Hi,
>
> Currently, E-mail and its attachments are indexed individually. However, we
> should link them somehow because there is not a direct link between them
> (one can not access to parent - e-mail or child - attachment from one to
> other).
>
> First of all, when we index e-mail documents, we have optional metadata
> fields for attachments:
>
> Encoding of Attachment
> Mime type of attachment
>
> it may be useful to store name of attachments (also ids of attachments) to
> softly link them. I used the term 'softly', because a hardly linked
> solution is similar to nested documents of Solr but it may break the
>  genericness.
>
> What do you think about it?
>
> Kind Regards,
> Furkan KAMACI
>