...
| Expand | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|
...
https://www.ncei.noaa.gov/thredds/
1.3 Documentation
NOAA/NCEI documents and URLs
|
Lee, H.-T., 2018: Quality Assurance Results and Summary for Monthly and Daily OLR CDR (rev.20180831) [ |
D5] http://olr.umd.edu/References/QA_Summary_OLR-Monthly_and_Daily_CDR_20180831.pdf |
Climate Algorithm Theoretical Basis Document (C-ATBD) for Monthly OLR CDR v02r07 [D2] |
Read me for Daily OLR CDR v01r02 http://olr.umd.edu/References/Read%20me%20for%20Daily%20OLR%20CDR%20v01r02.txt |
Copernicus Climate Data Store documents
|
C3S Product User Guide and Specifications ‑ Earth Radiation Budget HIRS OLR TCDR [D1] C3S_D312b_Lot1.3.8.2_201903_PUGS_v1.0 |
C3S Algorithm Theoretical Basis Document ‑ Earth Radiation Budget HIRS OLR TCDR [ |
D4] C3S_D312b_Lot1.1.5.2_201903_ATBD_v1.0 |
C3S Product Quality Assurance Document ‑ Earth Radiation Budget HIRS OLR TCDR [ |
D3] C3S_D312b_Lot1.2.5.5_201903_PQAD_v1.0 |
Copernicus User Support Handbook, V2.1 [D3]
ftp://ftp.ecmwf.int/pub/copsup/CUS-Agent-Training/Guides/CUS_Handbook_V2.1.pdf
Relevant scientific papers
|
Lee, H.- |
Relevant scientific papers
T., A. Gruber, R. G. Ellingson and I. Laszlo, 2007: Development of the HIRS Outgoing Longwave Radiation climate data set. J. Atmos. Ocean. Tech., 24, 2029–2047. http://olr.umd.edu/References/Lee_et_al_2007_HIRS_OLR_CDR.pdf |
Schreck, C. J., H.-T. Lee and K. Knapp, 2018: HIRS Outgoing Longwave Radiation—Daily Climate Data Record: Application toward Identifying Tropical Subseasonal Variability. Remote Sens. 2018, 10, 1325 |
Lee, H.-T., 2014: Daily OLR CDR – Development and Evaluation. CERES Science Team Meeting, Apr 2014 |
Lee, H.-T., 2014: Daily OLR Climate Data Record. EGU General Assembly, Apr 2014 http://olr.umd.edu/References/Lee_2014_Daily_OLR_Climate_Data_Record_EGU_Apr2014.pdf |
Lee, H.-T., C. J. Schreck, and K. R. Knapp, 2014: Generation of Daily OLR CDR. Eumetsat Meteorological Satellite Conference, Sep 2014 http://olr.umd.edu/References/Lee_2014_Generation_of_Daily_OLR_CDR_Eumetsat_Sep2014.pdf |
2. Upgrade cycle implementation procedure
...
The server is monitored by the RMIB in the frame of the C3S 312B Lot1 contract. In the case of unforeseen system failures, or other problems affecting data delivery through the OPeNDAP server, the CDS will be notified as quickly as possible, following any notification procedures requested by the CDS. For longer outages (longer than a few hours) the CDS will be notified again once the issue has been resolved.
Issues or outages, whether planned or unplanned, will be documented in the Quarterly Report.
5. User support
The point of contact will ensure that each product related user query is redirected (internally at RMIB and RAL or, externally, to the Dr. Hai-Tien Lee, Principal Investigator for this climate data record) to the most appropriate science team member for the formulation of a response. The response will then be delivered to the user within the allocated time frame. Throughout the process, the point of contact will ensure that the relevant key performance indicator (KPI) targets are met, and that the information collected from the science team will be used to develop the user knowledge base (via user documentation, FAQs, and user guides).
5.5.1 Enquiries
The user (customer) has the possibility to browse and search in the Copernicus Knowledge Base (CKB) (CAMS and C3S Knowledge Base on (CKB)) or the Copernicus Climate Data Store desk (https://cds.climate.copernicus.eu/contact-us). This is known as the level-0 process of User Support.
Figure 1: The schematic of Copernicus User Support (CUS Copernicus User Support Handbook, V2 [D3].1).
...
Contact and User Support process on JIRA
...
service desk
If the level-0 support fails to answer the user's query, they may then make a request, which is sent to Once a request is sent, the Copernicus User Support (CUS) Service team at ECMWF will handle the requests within 8 hours . These (level-1) requests will be handled within 8 hours.
For any scientific and special specialist enquiries that cannot be answered by the CUS team at ECMWF or addressed to by the Copernicus Knowledge Base, the request will be forwarded to the Copernicus User Support Specialists (level-2) to the following email address:
...
.
...
Enquiries forwarded to the Copernicus User Support Specialist team
...
will be acknowledged within 3 working days (target 100%) and a notification sent to the user. This step is
...
handled on the JIRA
| Footnote |
|---|
JIRA: Project management software tool created by Atlassian company |
...
Service Desk established at ECMWF for the current project. In case of specific scientific issues, the enquiries will be channeled to the ECV and data specialist of the
...
C3S2_
...
312a_Lot1 project and should be resolved within 3 working weeks (target 85%). In case of brokered datasets, the data specialist may choose to contact the responsible team at the provider level if they cannot resolve the issue on their own. In each yearly quarter, we aim for User Support satisfaction scoring 3 in 90% of all voluntary based feedbacks by users, with
...
1
...
(very unsatisfied) to
...
5
...
(very satisfied). We will also list the number of tickets raised by users on the JIRA system in the Quarterly Report.
5.3 Service availability
| Footnotes Display |
|---|
| Info | ||
|---|---|---|
| ||
This document has been produced in the context of the Copernicus Climate Change Service (C3S). The activities leading to these results have been contracted by the European Centre for Medium-Range Weather Forecasts, operator of C3S on behalf of the European Union (Delegation agreement signed on 11/11/2014). All information in this document is provided "as is" and no guarantee or warranty is given that the information is fit for any particular purpose. The users thereof use the information at their sole risk and liability. For the avoidance of all doubt , the European Commission and the European Centre for Medium - Range Weather Forecasts have no liability in respect of this document, which is merely representing the author's view. |
...