Project

General

Profile

Task #4704

Updated by Chris Jones over 10 years ago

When a Member Node is installed, whether it is registered in a given environment or not, the Member Node operators, and the DataONE operators will benefit from having a synopsis view of the Member Node holdings from a CN perspective. This will help in reconciling expected counts and those that are actually exposed via the DataONE API.

The view should show the following:

Count, and byte sum (in GB) of all objects
Count, and byte sum (in GB) of all objects of formatType DATA
Count, and byte sum (in GB) of all objects of formatType METADATA
Count, and byte sum (in GB) of all objects of formatType RESOURCE

Count, and byte sum (in GB) of all publicly readable objects
Count, and byte sum (in GB) of all publicly readable objects of formatType DATA
Count, and byte sum (in GB) of all publicly readable objects of formatType METADATA
Count, and byte sum (in GB) of all publicly readable objects of formatType RESOURCE

Count, and byte sum (in GB) of all publicly readable, not obsoleted objects
Count, and byte sum (in GB) of all publicly readable, not obsoleted objects of formatType DATA
Count, and byte sum (in GB) of all publicly readable, not obsoleted objects of formatType METADATA
Count, and byte sum (in GB) of all publicly readable, not obsoleted objects of formatType RESOURCE

The view tool should allow for the input of an arbitrary node baseURL, rather than just those that are registered in a CN environment. The tool should have access to the CN client certificate in order to be able to read system metadata for private content. Queries against the MN should be paged appropriately, and throttled as need in order to not negatively affect performance of the MN.

Back

Add picture from clipboard (Maximum size: 14.8 MB)