manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CONNECTORS-1203) Erratic handling of Sharepoint 2010 _ModerationStatus metadata
Date Wed, 10 Jun 2015 16:05:00 GMT

    [ https://issues.apache.org/jira/browse/CONNECTORS-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14580708#comment-14580708
] 

Karl Wright commented on CONNECTORS-1203:
-----------------------------------------

[~ddreiske] So, looking deeper, *some* internal fields definitely show up here.  "ID" and
"GUID" are examples.  It's possible, although unlikely, that there are other existing internal
fields that are *not* showing up.  I don't know what the cause for that would be, but there
are only three possibilities:

(1) SharePoint always treats certain always-present specific fields very specially and does
not include them in its field list response ever, for that reason, OR
(2) There is no such field for that particular data type, OR
(3) The database has the field, but for some reason SharePoint is unaware of it.

I'm afraid that you will need to do some research to figure out which of these cases is actually
true.  If you can look at the table schema that would tell you a lot.

Once you figure out what the truth is, I can propose a solution (well, except for the case
where the data doesn't even exist)...



> Erratic handling of Sharepoint 2010 _ModerationStatus metadata
> --------------------------------------------------------------
>
>                 Key: CONNECTORS-1203
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1203
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: SharePoint connector
>    Affects Versions: ManifoldCF 1.7.2
>            Reporter: Dale Dreiske
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 1.10, ManifoldCF 2.2
>
>         Attachments: CONNECTORS-1203.patch, debug.log, debug7.log
>
>
> The ManifoldCF Sharepoint 2010 connector handles the Approval Status metadata inconsistently.
In some cases it does not provide access to Approval Status at all.
> On /mcf-crawler-ui/execute.jsp#metapathwidget :
> * The field name appears in the drop down list as "Approval Status" when adding a new
rule.
> * The field name is NOT available in the drop down list for top level sites.
> * The field name is listed as "_ModerationStatus" for existing rules.
> With connector debug turned on, the ManifoldCF logs show the field coming from Sharepoint
as "ows__ModerationStatus". This is consistent across all pages, even when the the field is
not added to the metadata rules.
> When sent to Solr, it appears in one of these 4 forms:
> * "ows__ModerationStatus"
> * "_ModerationStatus"
> * "_moderationstatus"
> * In some cases it does not get passed at all.
> This issue is most troublesome when this field is not displayed for creating new metadata
rules. It appears it is only available when creating rules for pages in low level sites. Example
paths:
> * /abc  - does not work for top level sharepoint sites
> * /abc/xyz  - works but passes name inconsistently;



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message