earthsystemcog / cog Goto Github PK

WHO: Christiane
WHO: Use Case (Dycore 2012)

This is the ability to add a comment field to a simulation or model metadata instance. It requires we have the ability to display this type of metadata in the system.

We will have to determine how this information is stored and how it is displayed plus create a tool to edit and change it.

Use NESII as the example. Sylvia will provide the diagram.

WHO: Christiane
WHO: Use Case (Dycore 2012)

This ticket originally said archive test descriptions and associate them with different projects. I have made it more general, saying share documents across projects.

If the test description turns out exist in something besides a document, this ticket will need to be modified.

WHO: Ricky Rood

This had something to do with his class and even he was not sure what he meant at the time.

WHO: Christiane
WHO: Use Case (Dycore 2012)

We want a tool to allow users to generated metadata and also modify the metadata they have generated.

It was decided to use the native Django database as the storage mechanism for this effort.

This needs to customizable such that project admins can choose what metadata they want in their form.

WHO: Christiane
WHO: Use Case (Dycore 2012)

Should be integrated into the visualization package such that data can be analyzed first and then visualized immediately after.

Needs to allow for multiple dataset comparison.

SJM: The options for data analysis are endless. We might want a group of tickets with specific analyses listed.

WHO: Unknown

This is an modeling education workshop at CSU. I don't know the timeline.

The use case will be use to help guide further development of the workspace.

WHO: Christiane

Be able to take images that were created with the native server visualization package and upload them easily to other sites like someone's blog or an atlas of figures on a different server.

WHO: Christiane
WHO: Use Case (Dycore 2012)

This ticket originally said archive test descriptions and associate them with different projects. I have made it more general, saying share documents across projects.

If the test description turns out exist in something besides a document, this ticket will need to be modified.

Enable users to create parent-child and peer-peer connections between projects

Twitter like snippets, standardized location, ability of the user to select who sends and who receives.

WHO: Unknown

This is an modeling education workshop at CSU. I don't know the timeline.

The use case will be use to help guide further development of the workspace.

Use Christian's Dycore use case and formalize the requirements into a system analysis document for the Scientific Workspace

update the banner with the logo that Cecelia will provide
sylvia will provide an updated sprite to color match

e.g. links to papers or model documentation and websites

WHO: Christiane
WHO: Use Case (Dycore 2012)

We want a tool to allow users to generated metadata and also modify the metadata they have generated.

It was decided to use the native Django database as the storage mechanism for this effort.

This needs to customizable such that project admins can choose what metadata they want in their form.

WHO: Christiane
WHO: Use Case (Dycore 2012)

We are contemplating a MIP template. This could easily be a special page under that template if we think the rules for MIPs are generic enough to warrant such a thing.

Otherwise, the ability to upload a document or create user determined content already exists.

A discussion is required to determine the ideal way to post these rules.

WHO: Christiane
WHO: Use Case (Dycore 2012)

Should be integrated into the visualization package such that data can be analyzed first and then visualized immediately after.

Needs to allow for multiple dataset comparison.

SJM: The options for data analysis are endless. We might want a group of tickets with specific analyses listed.

HubZero has been identified as a possible technology to develop workspace functionality for the climate community. Another possibility could be develop directly within the ESG Gateway software stack (old or new), or possibly even use Django as a rapid-development environment. Are there other possibilities ?

HubZero has been identified as a possible technology to develop workspace functionality for the climate community. Another possibility could be develop directly within the ESG Gateway software stack (old or new), or possibly even use Django as a rapid-development environment. Are there other possibilities ?

WHO: Ricky Rood

This had something to do with his class and even he was not sure what he meant at the time.

WHO: Christiane

Be able to take images that were created with LAS and upload them easily to other sites (e.g. someone's blog or an atlas of figures) located on a different server.

Easier here might mean directly, without having to download to a local server.

WHO: Christiane
WHO: Use Case (Dycore 2012)

This is a dynamic table that will list which simulations have been completed.

There is a similar ticket indicating these be listed by experiment.

For the dycore 2008 workshop, a flat list of the runs was available via a query.

Benefits: All users

To start with we can start with basic user roles:

• Be a member of a project
• Create and edit content on that project, not including project metadata
• Make comments on content
• Upload documents and figures

Implement some or all of the features of the post application that is part of the scientific workspace app according to the feedback received during the COG call on 2010/10/15, specifically:

o Merge "blog" and "figure" functionality into only one workflow
o Implement ability to have multiple figures in one post
o Allow user most options when editing the post - wiki style, most prominently the ability to hypelrink
o Group posts by "theme"
o Be able to resize figures in the post and to click on a picture to enlarge it

Possibly:
o Show thumbnails of available figures
o Implement a table of contents
o Implement a TODOs list

Use Christian's Dycore use case and formalize the requirements into a system analysis document for the Scientific Workspace

e.g. links to papers or model documentation and websites

Demonstrate the release to the group
Decide on a repository
Upload the release to the repository and tag it with the release number
Write up a document that include:

• How to download and install
• Limitations
• Future work
  Upload the document to the COG website

WHO: Christiane
WHO: Use Case (Dycore 2012)

Whatever visualization package is chosen to be integrated into the the workspace needs to be able to save created images back to the workspace.

This will involve interfacing with the developers of that package to see if they can modify their code to do this for us.

WHO: Christiane
WHO: Use Case (Dycore 2012)

This is a dynamic table that will list which simulations have been completed.

There is a similar ticket indicating these be listed by experiment.

For the dycore 2008 workshop, a flat list of the runs was available via a query.

WHO: Christiane
WHO: Use Case (Dycore 2012)

This is not just an HTML link the ability to imbed the image, like we do imbed on blog pages, so that the image can be viewed immediately.

This requires that we have the ability to display simulation metadata within the workspace.

We need to consider how we store images in the metadata storage system

On a machine that others outside NOAA can access

WHO: Christiane
WHO: Use Case (Dycore 2012)

This is not just an HTML link the ability to imbed the image, like we do imbed on blog pages, so that the image can be viewed immediately.

This requires that we have the ability to display simulation metadata within the workspace.

We need to consider how we store images in the metadata storage system

Enable a user to create a project workspace.

Who: Jillian
Benefits: All users

This came out of the dcmip 2012 workshop. The participants uploaded many documents. You can only list 10 at a time. The ability to get a full list and/or sort in many ways would be useful.

This is not the news area that receives postings from other projects, this is the news area that a project would create for itself. We are going to try to have this appear in a consistent place.

WHO: Christiane
WHO: Use Case (Dycore 2012)

This is the ability to add a comment field to a simulation or model metadata instance. It requires we have the ability to display this type of metadata in the system.

We will have to determine how this information is stored and how it is displayed plus create a tool to edit and change it.

WHO: Christiane
WHO: Use Case (Dycore 2012)

We are contemplating a MIP template. This could easily be a special page under that template if we think the rules for MIPs are generic enough to warrant such a thing.

Otherwise, the ability to upload a document or create user determined content already exists.

A discussion is required to determine the ideal way to post these rules.

WHO: Christiane
WHO: Use Case (Dycore 2012)

WHO: NCPP
WHOP DIP 2013

This is a dynamic table that will list which simulations have been completed.

There is a similar ticket indicating these be listed by experiment.

For the dycore 2008 workshop, a flat list of the runs was available via a query.

WHO: Christiane
WHO: Use Case (Dycore 2012)

Whatever visualization package is chosen to be integrated into the the workspace needs to be able to save created images back to the workspace.

This will involve interfacing with the developers of that package to see if they can modify their code to do this for us.