Project

General

Profile

Bug #4135

OneMercury 'filter for data' was excluding some metadata by 'documents' relationship

Added by Skye Roseboom about 11 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Skye Roseboom
Category:
-
Target version:
-
Start date:
Due date:
% Done:

100%

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

Description

The 'filter for data' option in OneMercury was coded to work against 'documents' relationship from ORE documents. This was to exclude data packages (ORE) that were being used to aggregate metadata - with no data. However this strategy also caused metadata documents that are in ORE but only participate in documentedBy relationships (to other metadata files). The dryad member node uses this model in most data packages.

Changing the filter logic to filter by resourceMap attribute again. This does mean that data packages (ORE) will be displayed even if it is only aggregating metadata files.

Related issues

Related to Infrastructure - Story #4193: Release CCI 1.2.4 Features Closed 2013-12-11 2013-12-14

History

#1 Updated by Skye Roseboom about 11 years ago

  • Status changed from In Progress to Testing

#2 Updated by Skye Roseboom about 11 years ago

Fix is to class SolrTransactionServiceDelegate.java in d1_mercury_common.

#3 Updated by Skye Roseboom almost 11 years ago

  • Status changed from Testing to Closed

Tested on cn-stage-2 from release branch for CCIT release 1.2.4.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)