manifoldcf-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From markus.sch...@deutschebahn.com
Subject Antwort: Re: Sharepoint Repository Connector: Metadata Changes not causing re-index library or list items
Date Wed, 28 Jun 2017 12:19:05 GMT
Hi Karl,

i will contact our Sharepoint specialists about the handling of custom
metadata and the modified field.
I will report our findings.

Another solution i can think of might be a configurable list of extra
metadata to take into account for the version string
What do you think?

Thanks
Markus

Markus Schuch
Web Business (D.IPB 26)

DB Systel GmbH
Jürgen-Ponto-Platz 1, 60329 Frankfurt a. Main
Tel. +49 69 265-18520, intern 955-18520
_________________________________________________________________________________

DB Systel. Digital bewegen. Gemeinsam. ▪ Kundenmagazin >>
http://www.dbsystel.de/digitalspirit

--- Bitte denken Sie an die Umwelt, bevor Sie diese E-Mail ausdrucken. ---

Sitz der Gesellschaft: Frankfurt am Main
Registergericht: Frankfurt am Main, HRB 78707
USt-IdNr.: DE252204770
Geschäftsführer: Christa Koenen (Vorsitzende), Bodo Gmel, Gerald Hofer, Dr.
Klaus Rüffler
Vorsitzender des Aufsichtsrates: Dr. Manuel Rehkopf



Von:	Karl Wright <daddywri@gmail.com>
An:	"user@manifoldcf.apache.org" <user@manifoldcf.apache.org>
Datum:	28.06.2017 13:54
Betreff:	Re: Sharepoint Repository Connector: Metadata Changes not
            causing re-index library or list items



Hi Markus,

We obviously can't put all of the metadata for a document into the version
string for it.  We therefore use the Modified field is used as a proxy for
changes to the document and the rest of its metadata.  As far as I know, it
is typically the case in SharePoint that when you change a metadata item,
the document's Modified field is updated accordingly.  But perhaps that is
not true for custom fields?

If you can discover a rule of some kind which would allow us to determine
which attributes, when changed, would *not* affect the modified date, then
we can add appropriate information to the version string for the document
that would make MCF robust against those kinds of changes.  But this will
require more research on your part.  Please let me know what you discover.
I'm open to adding a list of metadata names/values to be included in the
version string if that is needed, but that's a lot of work for an already
quite complex connector; it would be great if we could simply say something
like "all attributes beginning with xxx do not affect the modified date
when they are changed".

Thanks!
Karl


On Wed, Jun 28, 2017 at 7:32 AM, <markus.schuch@deutschebahn.com> wrote:


      Hi,

      i use the Sharepoint Repository Connector and i have a question about
      versioning:

      is there a way to respect metadata changes for list/library items to
      cause re-indexing for these items when other metadata than
      Last_x0020_Modified, Modified, Created and GUID has changed?
      I use a custom list/library metadata field (name is
      WorkingAreaID_x003a_Name) for a facet in a solr output repository,
      but the documents are not getting reindexed, when this metadata
      changes.

      Thanks in advance,
      Markus







Mime
View raw message