DataStoreLibrary

Is Abstract: 
no
Is Pattern: 
no
Definition: 

A DataStoreLibrary is a collection or, again, a "library" of DataStores.

An individual DataStore is associated with a Study. A collection of DataStores is associated with a StudySeries.

The relationships among the DataStores in the DataStoreLibrary is described by the DataStoreRelationStructure. Relations may be more or less complicated depending on the StudySeries type. A StudySeries may be ad hoc. A StudySeries may form a time series. The variety of these collections has been described using the "Group" in DDI 3.1.

Like any RelationStructure, the DataStoreRelationStructure is able to describe both part/whole relations and generalization/specialization relations. See the controlled vocabulary at RelationSpecification to review all the types of relations a RelationStructure is able to describe.

In the context of a time series the DataStoreRelationStructure could describe one DataStore as a superset of another when in a StudySeries from one period to the next "supplements" come and go. We might also enlist a DataStoreRelationStructure to describe a situation where in a time series, instead of "going wide" and capturing additional subject matter, a Study "goes deep" and captures more data about the same subject.

Explanatory Notes: 

If we broke a study down into sub-studies where the core is a sub-study and each supplement is a sub-study, we could also use the DataStoreRelationStructure to track the generalization/specialization relationship or, again, "going deep" over time.

Sometimes across a StudySeries we add panels. If panels were also sub-studies, we could use the DataStoreRelationStructure to track both the core and supplements by panel over time.

Example: 
A StudySeries is a time series and a DataStoreRelationStructure is dedicated to tracking "supplements". There is a study at T0. Perhaps it is never executed. It is the "core" study. At T1 there is a study that includes the core and Supplement A. At T2 there is a study that includes the core, Supplement A and Supplement B. At T3 there is a study that includes the core and a one off supplement that is never asked again. T4 though T6 repeats T1 through T3.
Synonyms: 
Structured metadata archive
Property: 
NameCardinalityDatatypeDescription
type
0..1
Whether the collection is a bag or a set: a bag is a collection with duplicates allowed, a set is a collection without duplicates.
name
0..n
A linguistic signifier. Human understandable name (word, phrase, or mnemonic) that reflects the ISO/IEC 11179-5 naming principles. If more than one name is provided provide a context to differentiate usage.
purpose
0..1
Explanation of the intent of some decision or object. Supports the use of multiple languages and structured text.
contains
0..n
The DataStores in the Catalog. Allows for the identification of the member and optionally provides an index for the member within an ordered array
isOrdered
0..1
If members are ordered set to true, if unordered set to false.
Relationship: 
NameTarget ObjectDescriptionSource cardinalityTarget cardinalityRelationship type
realizes
Realizes the pattern collection
0..n
1..1
Neither
isStructuredBy
Description of a complex structure for the Collection. A collection may be structured in more than one way for different uses.
0..n
0..n
Neither
studySeries
Whereas a DataStore is associated with a Study, a DataSoreLibrary is associated with a StudySeries. Each StudySeries has at most one DataStoreLibrary
0..n
0..1
Neither

Stage:

Is extendable: 
Is property: 
0
RDF Mapping: