Feature #6732
Add 'archived' records to search index
30%
Description
Design questions:
Adding archived items to the index:
1.) Are data package relationships (documents, documentedBy, aggregatedBy) removed when a (data/science metadata) document is archived. Annotations, provanance, semantic fields?
2.) Are data package relationships removed when an ORE/data package document is archived?
Current definition of 'head of sid' chain requires archived objects to be present in the search index so that 'head of sid' chain resolution works the same as it does on CN
Subtasks
Related issues
History
#1 Updated by Skye Roseboom about 9 years ago
- Parent task deleted (
#6716)
#2 Updated by Skye Roseboom about 9 years ago
- translation missing: en.field_release set to 2
- Tracker changed from Task to Feature
#3 Updated by Ben Leinfelder about 9 years ago
Why does finding the 'head of sid' chain rely on the solr index?
#4 Updated by Skye Roseboom almost 9 years ago
- Target version set to CCI-2.0-RC1
#5 Updated by Skye Roseboom almost 9 years ago
Current implementation removes archived objects from the search index.
Need to alter this to:
- add an archived property to the solr schema
- index only system metadata for archived objects (currently indexed objects need to be updated to remove other search fields such as title etc for science metadata)
#6 Updated by Skye Roseboom almost 9 years ago
- % Done changed from 0 to 30
- Status changed from New to In Progress
#7 Updated by Dave Vieglais almost 9 years ago
- Target version changed from CCI-2.0-RC1 to CCI-2.0.0
#8 Updated by Dave Vieglais almost 9 years ago
- Related to Task #7245: Update ONEMercury to exclude archived PIDs from searches added
#9 Updated by Dave Vieglais almost 9 years ago
- Related to Task #7246: Update Metacat UI search to exclude archived PIDs from searches added
#10 Updated by Ben Leinfelder almost 9 years ago
- Related to Task #6733: Metacat MN index should keep the solr index for archived objects added
#11 Updated by Skye Roseboom almost 9 years ago
- Description updated (diff)
#12 Updated by Skye Roseboom over 8 years ago
- Status changed from In Progress to Rejected
Rejecting for now, use case story is unclear why/how these records would be used.
