List view
Motivation /Description Maintain the GHGC Help Desk-related operations to support and improve user experience. Monitor system operational status and report metrics and updates as needed to project management. Also see: https://github.com/US-GHG-Center/ghgc-architecture/milestones/46 Success Criteria Help Desk Ongoing Work: - [ ] Maintain feedback tickets - [ ] Maintain GHGC Jupyter Hub access - [ ] Contribute stakeholder feedback to the action list - [ ] Continue to update the Decision Tree and create new canned responses as needed New Work: - [ ] Finish reprocessing tickets on the Help Desk dashboard - [ ] Finalizing the Help Desk Operations Guide Metrics, Monitoring, Reporting & Ops Documentation Ongoing Work: - [ ] Notify the dev team of broken links discovered by the link-checker - [ ] Run the Lighthouse report once per month and upload to the GHGC Team drive - [ ] Check status of automated dataset updates biweekly and report any issues to the dev team - [ ] Record any unexpected system outages or errors in the GHGC Ops Issue Tracker - [ ] Submit monthly operational report to the Project Management Team - [ ] Submit biweekly sprint reporting to MSFC management New Work: - [ ] Improve user metrics/reporting to provide more detailed insights on portal use as requested by Project Management Team Stretch Goals: - Maintain Operations Plan, update and change as needed once per quarter - Create documentation on how to automatically track hub-access on GitHub and add to Operations Plan Risks/Dependencies - Low on resources for documentation & competing priorities - Dependency on Project Management Team to provide input on how to handle certain user feedback - Dependency on Project Management Team to provide feedback on user metric improvements
No due date•1/1 issues closedMotivation /Description The GHG Center portal is getting a new Drupal-based Content Management System (CMS) that is being built by an external team (Earthdata team). This PI the MSFC team needs to understand how the transition to this new CMS will work from a technical and workflow perspective, and scope out any needed supporting work. Also see: https://github.com/US-GHG-Center/ghgc-architecture/milestones/41 Success Criteria - [ ] Meet with the Earthdata team (as often as necessary) to discuss and plan transition - [ ] Identify any supporting tasks for the MSFC team Stretch Goals: - Identify swim lanes/roles & responsibilities for portal operations post-transition Risks/Dependencies - Technical details of how this transition will work is TBD - scope of workload on MSFC team (incl. DevSeed) is unknown
No due date•1/1 issues closedMotivation /Description As the GHG Center project and partners continues to evolve and grow, it is important to have the capability to support both in-house developed tools as well as external tools developed and maintained by agency partners. The MSFC team needs to develop a DevOps framework and requirements/process for integrating external tools into the platform. The EMIT VISIONS portal is a candidate use case that can be used to demonstrate this process. Also see: https://github.com/US-GHG-Center/ghgc-architecture/milestones/42 Success Criteria - [ ] Draft DevOps process - [ ] Share draft for feedback (internally and externally if needed) - [ ] Establish plan to test framework (e.g. for the EMIT VISIONS portal or existing GHGC tool) Stretch Goals: - Implement framework with VISIONS portal (in production) Risks/Dependencies - Dependency on the EMIT team to follow and test out the process. If the EMIT team does not have the bandwidth to support this, we may need to explore other candidate tools to test with. - Risk that there will be push back on our suggested approach
No due dateMotivation /Description We need to standardize the tech stack and design system across our five custom interfaces to make them easier to maintain, scale, and work with. By aligning everything under the same framework and design system, we’ll be able to reuse components without constantly redesigning them, streamline development for new interfaces, and make maintenance way more manageable. Also see: https://github.com/US-GHG-Center/ghgc-architecture/milestones/44 Success Criteria - [ ] EMIT and NOAA interfaces migrated to the react framework - [ ] All the interfaces use the USWDS design system (aligns with what veda-ui is moving towards) - [ ] A template repository for new interfaces to spin from - [ ] Standard deployment strategy for all the interfaces Risks/Dependencies - Coordination w/ Portal 2.0 design - Ties into DevOps process (Objective 3.0)
No due date•3/3 issues closedMotivation /Description To keep the US GHG Center Portal and supporting services maintained and up-to-date, we need to do regular upgrades. This involves regular maintenance (bug fixes, improvements) and upgrading the front end as well as the backend services at a biweekly cadence, testing for quality assurance, and releasing the upgrades. Also see: https://github.com/US-GHG-Center/ghgc-architecture/milestones/47 Success Criteria Ongoing Work: - [ ] Data services are up-to-date with VEDA with a maximum of 1 week lag - [ ] Portal releases every first Tuesday of a sprint - [ ] All the services maintain stability and uptime as close to 100% as possible - [ ] Report needed VEDA updates to the VEDA team with priority (sprint loading) - E.g. variable transparency in color bar (titiler) Stretch Goals: - NIST embedded tower data viewer improvements - NOAA embedded viewer improvements - Complete Features API performance improvements - Test and optimize automated acquisition, transformation and verification pipeline - Build new custom interfaces as needed Risks/Dependencies - Dependency on VEDA team for veda-ui updates - Risk that unplanned new data requiring custom interface will be prioritized by Project Management Team
No due date•2/2 issues closed