Warning: These documents are under active development and subject to change (version 2.1.0-beta).
The latest release documents are at: https://purl.dataone.org/architecture

Use Case 18 - MN Retrieve Aggregated LogsΒΆ

Revisions
View document revision history.
Goal
Member nodes can request aggregated CRUD log for {time period/object id/userid} for all of ‘their’ objects.
Summary
A Member Node should be able to request use information for any objects for which that Member Node is the origin (or defacto origin in the case where the original MN was decommissioned).
Actors
  • Coordinating Node
  • Member Node
Preconditions
  • Aggregate logs are accumulated by CNs
Triggers
  • MN Administrator requests aggregate logs
  • Timed event
Post Conditions
  • Aggregate log information is available to the Member Node
../../_images/18_seq.png

Figure 1. Interactions for use case 18.

Notes

This operation should really be a function for the administrative functions of the Investigator Toolkit. It is reasonable to expect that (especially for the first iteration of the infrastructure) MN administrators will want to peruse and evaluate the log data. In later stages, this information could be associated with content, so use statistics appear with search results.

This material is based upon work supported by the National Science Foundation under Grant Numbers 083094 and 1430508.

Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation.