Table of Contents
About this Page
This page contains some initial ideas about how to organize data within Clowder for this project.
General Clowder Information
There are three basic sections within Clowder:
- Spaces
- Collections
- Datasets
Access Control Details:
- Being a Clowder User does not automatically provide Access to all Spaces
- Access is established at the Space level
- Access must be set for each Space individually
- All Datasets and Collections inherit permissions from the Space to which they belong
Organization Ideas
Naming Conventions
Some 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 Clowder
It would be good to have a general organization methodology moving forward.
This section will contain various ideas for organization.
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 both Collections of Datasets and individual Datasets
- Can have an image appear in the listing on Clowder
- Collections of Datasets
- Naming
- Include the Sensor name
- Sub-collections can be used to logically organize datasets, for example data ranges
- Contains Datasets
- Naming
- Datasets
- Naming
- When possible, the name would include the name of the Sensor
- Some Datasets can contain raw data and other derived data data
- Should be placed in Collections
- Naming
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
- If
- 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
- If
- Example A:
- Collection Name: Flux Tower Data Files
- 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 Raw Data Sept 2016, Flux Tower Data 5TE Soil Probe 30 cm Sept 2016, etc.
- Flux Tower
information
Sept 2016 - The
information
would just describe the general content of the Dataset (type of measurement, type of data, etc.)
- Flux Tower
- Dataset Content: This will contain any relevant files
Organization Tasks
General Tasks that may be completed:
- Removing any extraneous or duplicated data
- Remove "imlczo" Space and move Datasets contained within to appropriate Spaces
- Where possible, moving and renaming items to fit the decided upon organization methodology
- Provide a "How To" wiki page about the decided upon organization methodology
- Make some example changes in Clowder that reflect the ideas presented herein