Project

General

Profile

Bug #8182

relationships defined using SIDs in resource maps don't stay current

Added by Rob Nahf about 4 years ago. Updated about 4 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
d1_indexer
Target version:
-
Start date:
2017-09-11
Due date:
% Done:

0%

Milestone:
None
Product Version:
*
Story Points:
Sprint:

Description

For relationships defined in resource maps involving SIDs, the relationship is not propagated to any future versions of the objects referenced by those SIDs.

For example, consider a metadata SID that cito:documents a data object. Initially, the documents field would be populated in the index for all records where the seriesId = SID (or maybe just the latest - I haven't tested). If, tomorrow, a new object is synchronized with that SID, it would not inherit the documents field of its predecessor.

To do so will require referring to the resource maps of predecessor objects, and extracting the SID out of them. This can be done either on the fly, or by persisting the relationships in a separate solr core, not necessarily available to the public.

After a little thought, the solr core would only need to contain these fields: [resourceMap, SID, relationship], and we would only need records for SIDs. There would be no need for a unique key.


Related issues

Related to Infrastructure - Story #8702: Indexing Refactor Strategy New 2018-09-24

History

#1 Updated by Rob Nahf about 4 years ago

  • Description updated (diff)

#2 Updated by Rob Nahf about 3 years ago

  • Related to Story #8702: Indexing Refactor Strategy added

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)