manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <>
Subject [jira] [Commented] (CONNECTORS-1274) SharePoint connector missing metadata and ACL information
Date Wed, 10 Feb 2016 23:35:18 GMT


Karl Wright commented on CONNECTORS-1274:

I'm going to split this into distinct tickets.

For the type issues, this is the ES connector we'd need to look at, but you will need to provide
me the exact JSON format you expect to see for the fields you are interested in.

For the missing data, that's a tougher problem because it may well be that Microsoft broken
something in the ability to access certain metadata fields.  There's no special sauce for
getting at one field vs. another.

For the ACLs issue, I suspect that you might be seeing a permissions problem.  If you can
turn on connectors debugging, crawl the document, and send me the log, I can tell if that
is the case.

Also, FWIW, I've got multiple deadlines coming up tomorrow, Friday, Saturday, and Sunday,
so it will be difficult for me to address any but the simplest problems in that time frame.

> SharePoint connector missing metadata and ACL information
> ---------------------------------------------------------
>                 Key: CONNECTORS-1274
>                 URL:
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Elastic Search connector, SharePoint connector
>    Affects Versions: ManifoldCF 2.3
>         Environment: SharePoint 2013, ElasticSearch 2.2, MCF 2.3
>            Reporter: Andrey Leybovich
>            Assignee: Karl Wright
> When crawling a SharePoint 2013 list, there are three issues:
> 1. Some important metadata fields, such as "Created By" and "Content Type" are blank.
In SharePoint they are always non-empty
> 2. No ACL (permissions) information is present 
> 3. All metadata is pushed to elastic as string. Thus date fields like "Created", "Modified"
etc are not searchable/sortable as dates

This message was sent by Atlassian JIRA

View raw message