Milestones
List view
- No due date
- No due date
- No due date
We would like to add the capability to accept LinkML Schemas, associate these schemas to data, and validate metadata against these schema. Complete functionality looks like: - A user uploads a schema. - A user uploads data and its associated metadata, selecting a schema to align to while doing so. - DataFed validates the provided metadata and raises validation errors. Implementation currently depends on: - Creation of an OpenAPI api schema that this validator (and future metadata validator services, if applicable) conform to. - Creation of the python server that aligns to this schema and can accept, syntax validate, and store schemas. Better description forthcoming.
No due date•32/41 issues closedIncluding usernames, is not ideal in the folder structure of a repository.
No due dateRemove un helpful log messages. Add helpful log messages, standardized log format.
Overdue by 10 month(s)•Due by December 31, 2025•5/6 issues closedThe following PR's are outdated and are being closed, in favor of others. https://github.com/ORNL/DataFed/pull/1603 https://github.com/ORNL/DataFed/pull/1602 https://github.com/ORNL/DataFed/pull/1543 https://github.com/ORNL/DataFed/pull/1524
No due date•13/26 issues closed## Description The goal of this epic is to address service logging. Currently, we have the following servics: * Core * Arango/foxx * GCS * Repo * Web (BE + FE) ## Acceptance Criteria We would like to effectively log information that could be useful for * [Grafana (loki)](https://grafana.com/oss/loki/) * [Promethius](https://prometheus.io/) * Internal monitoring
No due date•1/2 issues closed# Objective Gradually integrate React components into the production application while maintaining functionality. ## Success Criteria * Feature flags implemented for all new components * All jQuery components successfully replaced * Parallel implementations running without conflicts * Comprehensive testing completed for each migration ## Description This epic covers the final phase of our refactoring project, focusing on the incremental integration of React components into the production application. We'll implement feature flags to toggle between old and new implementations, replace jQuery components one section at a time, run both implementations in parallel during the transition, and validate each migration with comprehensive testing.
No due date# Objective Implement modern state management solutions to replace jQuery's approach to data handling. ## Success Criteria * Selected state management solution implemented * All AJAX calls converted to React hooks * Complete TypeScript typing for state objects * Custom hooks created for reusable logic ## Description This epic addresses the implementation of state management in our React application. We'll select and implement an appropriate state management solution, convert jQuery AJAX calls to React hooks or async functions, ensure proper TypeScript typing for all state objects, and create custom hooks to replace jQuery's reusable logic.
No due date•0/6 issues closed# Objective Develop React components with TypeScript to replace existing jQuery functionality. ## Success Criteria * All leaf components implemented and tested * Component props and state properly typed with TypeScript * Unit tests passing for all components * Component documentation completed ## Description This epic focuses on the systematic development of React components to replace jQuery functionality. We'll start with leaf components that have minimal dependencies, ensuring proper TypeScript interfaces for all props and state. We'll implement stateless components first before adding state management, and write comprehensive unit tests for each component.
No due date•0/8 issues closed# Objective Analyze the current jQuery codebase and establish the foundation for React+TypeScript migration. ## Success Criteria * Complete codebase audit document * Finalized component hierarchy diagram * TypeScript interfaces for all data models * Working React+TypeScript project setup with build pipeline
No due date•1/5 issues closed# Description To deploy on production grade infrastructure, all vulnerabilities need to be fixed in the container images and the SBOMs need to be made visible. In addition an update plan and CI pipelines need to be created to adapt to needed changes.
No due date