-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adding section on Creating data products #73
Comments
From @AliciaTak , might be good to rewrite in our own words (hah!) and include!
|
@paolap Here are slightly different steps when I reword the question (what to do with raw RCM outputs?), e.g., steps 9., 10., 12. were not included in the precious prompts but are important - especially step 12. Step 1: Data Collection and Preprocessing
Step 2: Spatial and Temporal Subset
Step 3: Data Bias Correction (if needed)
Step 4: Calculate Climate Indices
Step 5: Data Aggregation and Averaging
Step 6: Spatial Interpolation (if needed)
Step 7: Data Visualization and Analysis
Step 8: Quality Control and Validation
Step 9: Documentation
Step 10: Create User-Friendly Climate Products
Step 11: Data Distribution and Sharing
Step 12: Continual Update and Improvement
|
While this is great for the moment I would rather just add a generic scope of the guidelines. This is very useful but it is a very specific use case, so I'm hesitant to write it down as it is. What I could do is to pick the generic steps as points to cover, for example: This guidelines should cover:
Leaving out completely things like "Step 4: Calculate Climate Indices" and the "sub-steps" as they're specific to that example. |
Yeah, absolutely @paolap! I just thought I share the prompt about the definition of "application-ready" data and what it believes it involves. I think we also need to be mindful regarding copy-right issues as it is not clear who is the owner of the prompts :) |
Great, it's still good to have the longer and detailed list here for later on. |
Ok I've had a go at writing the intro and will put a pull request soon. I re-organised the steps in 4 broader categories, let me know what you think |
Just realised we didn't add this guidelines to the intro page |
I finally added something about this to the introduction page, I also pointed out that this is a work in progress and we welcome input from others who have some experience/ideas. In branch paola_isssues |
Thanks, Paola! |
application ready data
data products finalised to be usable in other disciplines, stakeholders etc., so tailored to the intended user needs. This might mean converting existing data to suitable formats, adding extra quality control
how is packaged, tailored to different uses and documented in a way that errors and quality are well documented as the "clients" are non-expert
user centric
The text was updated successfully, but these errors were encountered: