Organization IdeasNaming ConventionsSome ideas for how to name items that are placed in Clowder: - When able, include the name of the Sensor in the title of Spaces, Collections, and Datasets
- Including the name of the sensor may make it is easier to search for items
Using the Sections Within ClowderIt would be good to have a general organization methodology moving forward. This section will contain various ideas for organization. Note: there are three basic sections within Clowder: - Spaces
- Collections
- Datasets
One idea for utilizing and organizing these sections: - Spaces
- Named after each Sensor or a general category (e.g.: "How To" Documentation, Images, etc.)
- Contains Collections of Datasets and Datasets
- Can have an image appear in the listing on Clowder
- Access control is established at this level. All Datasets and Collections inherit permissions from the Space they belong to.
- Collections of Datasets
- Naming
- Include the Sensor Include any grouping information (e.g.: date range, etc.)name
- Sub-collections can be used to logically organize datasets, for example data ranges
- Contains Datasets
- Datasets
- Naming
- When possible, the name would include the name of the Sensor
- Some of these are auto-generated, and are therefore auto-namedContains Datasets can contain raw data and parsed other derived data data
- Should be placed in Collections
This is an example illustrating this idea: - This is based upon the Flux Tower data (information about this dataset is available in this Wiki space at Flux Tower Data)
- Space
- There is only one of these for this Space
- Space Name: Flux Tower Data
- Space Description: Flux Tower located at
location-description - Space Image: Suggestion - provide an image of the site or the instrument or a logo (if available)
- Collection
- There can be several of these for this Space
- Data Measurements Example
- Collection Name: Flux Tower Data Files
date-range - The date-range could be years or months depending upon the size of the dataset
- Collection Description: Collection of Data Files for
date-range - Collection Content: This will contain all relevant Datasets for this collection
- Example A:
date-range is a year- If
date-range is 2010 - Then Datasets would be all the Datasets that include 2010 data
- Example B:
date-range is January 2010 to March 2010- If
date-range is January 2010 to March 2010 - Then Datasets would be all the Datasets that include 2010 data from January to March
- Documentation Example
- Collection Name: Flux Tower Documentation
- Collection Description: Documentation for the Flux Tower Sensor
- Collection Content: This will contain any relevant documentation that describes the Sensor (types of measurements gathered, etc.)
- Datasets would not be present in this collection
- Files can be of any preferred format
- Datasets
- There can be several of these for each Collection in the Space
- To simplify managing individual datasets they could be grouped by month
- An alternative could be to use folders in datasets to group files by month
- Dataset Name: Flux Tower Dataset
information Flux Tower Raw Data Sept 2016, Flux Tower Data 5TE Soil Probe 30 cm Sept 2016, etc.- Flux Tower
information Sept 2016 - Some of these are auto-generated and may have a different naming convention
- The
information would just describe the general content of the Dataset (type of measurement, type of data, etc.)
- Dataset Content: This will contain any relevant files
|