70 likes | 184 Views
Working Group: Practical Policy Rainer Stotzka, Reagan Moore. Concept Extensions. Extend the concept of “ Data in Context ” to “ Collection in Context ” A collection provides the context for understanding data Provenance metadata Descriptive metadata Structural metadata Workflows
E N D
Concept Extensions • Extend the concept of “Data in Context” to “Collection in Context” • A collection provides the context for understanding data • Provenance metadata • Descriptive metadata • Structural metadata • Workflows • Administrative metadata • However, each collection has a driving purpose that represents the consensus of a user community • We observe the the members of the user community evolve, implying re-purposing of the collection. • The evolution redefines the required metadata for the collection context
Example Collection Evolution • Local project • Members have detailed tacit knowledge of the semantics, structure, description • Data grid • Data are shared with other institutions, requiring description and access controls • Digital Library • Data are published for the entire discipline, requiring provenance, description, structural information • Reference Collection • Data are published for use by future researchers, requiring knowledge of generation and management of the collection • Reproducible data-driven research • The workflows, input parameters and files, and output results from each execution of a workflow need to be saved • The policies and procedures used to manage an archive also need to be saved • Preservation is “communication with the future” • Preservation requires “validation of communication from the past”
Practical Policy Working Group Focuses: • Identify the most important policies • Practical implementations for managing research data collections • Provide recommendations for a “starter kit” • Testbeds: • Evaluate standard policies • Test interoperability across WGs Policy: Assertion or assurance that is enforced about a collection or a dataset
Policy-Based Data Environments Purpose Reason a collection is assembled Properties Attributes needed to ensure the purpose Policies Controls for enforcing desired properties, mapped to computer actionable rules Procedures Functions that implement the policies Mapped to computer executable workflows Persistent state information Results of applying the procedures mapped to system metadata Property verification Validation that state information conforms to the desired purpose mapped to periodically executed policies
Concept Graph for Policy-based Management Purpose DATA_ID DATA_REPL_NUM DATA_CHECKSUM Collection Defines Replication Policy Has Isa Isa Isa Has Isa Checksum Policy Defines Digital Object Attribute Has Isa Quota Policy Has Isa Integrity Data Type Policy Isa Updates Isa Isa Authenticity Persistent State Information Isa Property Policy Procedure Defines Updates Controls Access control Isa Isa SubType Has HasFeature GetUserACL Periodic Assessment Criteria Policy HasFeature Workflow Isa Policy Enforcement Point SetDataType Completeness HasFeature Chains Isa SetQuota Correctness Isa Function HasFeature Invokes Isa DataObjRepl Consensus Isa Isa SysChksumDataObj Operation Consistency Client Action
Policy Categories Integrity Management Administrative Assessment AccessControl Replication Provenance Preservation Collection-based Policies Regulatory Description Data Management Plans Data Staging Publication Data Lifecycle Management Federation Compliance