Infrastructure

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.