[
https://issues.apache.org/jira/browse/CONNECTORS-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14581098#comment-14581098
]
Dale Dreiske commented on CONNECTORS-1203:
------------------------------------------
Regarding the internal fields, all three of the following fields are present in
the XML. This includes both the XML I attached earlier and the XML for a site
which gives me access to _ModerationStatus:
* ID - seems to behave as expected.
** ColName="tp_ID"
** Available to pick from the MCF GUI.
* GUID
** ColName="tp_GUID"
** Not available to pick from the MCF GUI.
* \_ModerationStatus - This looks like it is the field I need. The ows_ prefix
is only used in the MCF agent?
** ColName="tp_ModerationStatus"
** Not available to pick from the MCF GUI on most sites.
I did a spot check on 8 of the sharepoint sites I am working with. The MCF GUI
gives ID on all these sites, GUID on none of them and _ModerationStatus on 2 of
them.
Why does MCF treat these differently?
> 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)
