Dear SMILAs,
Within the CUbRIK platform, each content object gets an persistent unique ID for identification.
This ID has the following requirements:
1. It needs to be unique for an instance a CUbRIK platform or even better, worldwide. (The ID is used to allocate the content object within the CUbRIK platform.)
2. It needs to be calculated locally on a node, i.e., with no central component that provides these IDs.
3. It needs to be unique across job runs
4. For the same object (from the same location with the same metadata) it should be the same
Initially, I came up with the following solutions
a) Use the record ID created during job runs (does this fulfill 3.??)
b) Use the fingerprint from delta indexing (Does this fulfill 1?)
c) Creating a hash from the document metadata (which might be the same as b)
d) Use GUIDs (however, this would not satisfy 4.)
But maybe you have a better suggestion for this.
Best wishes
Björn
Björn Decker
Product Manager IAS
Empolis Information Management GmbH | Europaallee 10 | 67657 Kaiserslautern | Germany
Phone +49 631 68037-56 | Fax +49 631 68037-77
bjoern.decker@xxxxxxxxxxx
www.empolis.com
Sitz Kaiserslautern | Amtsgericht Kaiserslautern HRB 31317
Geschäftsführer: Dr. Stefan Wess, Stefan Volland, Dr. Christian Schulmeyer, Dr. Peter Tepassé
SMART INFORMATION MANAGEMENT
Empolis-Lösungen befähigen Unternehmen und Organisationen, die exponentiell wachsende Menge
strukturierter und unstrukturierter Daten zu analysieren, zu interpretieren und automatisiert zu verarbeiten.
Sie nutzen damit ihr Wissenskapital, um unternehmenskritische Geschäftsprozesse zu optimieren.
Entscheider, Mitarbeiter und Kunden erhalten so stets situations- und aufgabengerecht genau die
Information, die für sie relevant ist.
Abonnieren Sie unseren Newsletter
