Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel
bgColor#eeeeee

Table of Contents

Table of Contents
excludeTable of Contents

Panel
bgColor#eeeeee

About this Page

This page contains some initial ideas about how to organize data within Clowder for this project. 

 

Panel
bgColor#eeeeee

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.

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
    • Can have an image appear in the listing on Clowder
  • Collections
    • Naming
      • Include the Sensor
      • Include any grouping information (e.g.: date range, etc.)
    • 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-named
    • Contains raw data and parsed 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
    • Dataset Name: Flux Tower Dataset [ information ]
      • 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

Panel
bgColor#eeeeee

Organization Tasks

General Tasks that may be completed:

  • Removing any extraneous or duplicated data
  • Where possible, moving and renaming items to fit the decided upon organization methodology
  • Adding "How To" documentation about the decided upon organization methodology
  • Make some example changes in Clowder that reflect the ideas presented herein