Repository navigation
Terminology Renames - #59
Merged
Merged
Conversation
ThanKarab
force-pushed
the
feat/terminology_refactor_v2
branch
from
November 17, 2026 10:27
29fbe7e to
b937693
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Renames backend terminology to Study → Analysis Group → Analysis, including APIs, DTOs, Java packages, persistence, tests, and documentation.
Preserves the existing preview/run/save workflow, execution results, ownership, sharing, authorization, timestamps, ordering, and memberships. Separates platform Analysis management from Exaflow integration through
AnalysisExecutionService.Breaking API changes
Clients must switch to the new contract. No deprecated route or field aliases are provided.
/services/experiments/services/analyses/services/experiment-folders/services/studies/setsroutes/groupsroutes/setroutes/grouproutesanalysisanalysisRequestexperimentsanalysestotalExperimentstotalAnalysesfoldersstudiessetsgroupsexperimentIdsanalysisIdsexperimentUuidanalysisIdfolderIdstudyIdsetIdgroupIdPreview and run now accept
{ name, analysisRequest }. Save continues to accept{ runId, name }.Root Analysis
uuid, Study/groupid, pagination fieldscurrentPageandtotalPages, and existing identifier values remain unchanged.Backend Pathology exceptions and messages now use Data Model terminology. Data-model listing retains 404 for no available models and 403 for no accessible models; clients should use status codes in that request context rather than match message text.
Configuration renames
Deployment overrides must use the new names. Old names have no fallback aliases.
EXPERIMENT_RUN_DRAFT_TTLANALYSIS_RUN_DRAFT_TTLexperiments.run-draft-ttlanalyses.run-draft-ttlauthentication.all_experiments_allowed_claimauthentication.all_analyses_allowed_claimPreserve each deployment’s configured TTL; the default remains
PT24H. Move custom claim-setting overrides to the new property.research_experiment_allis intentionally unchanged. It is the existing external authorization authority; Keycloak roles, token authorities, and access grants must remain intact.Database and deployment
Adds Flyway V6 without modifying shipped migrations:
analysis,analysis_run,study,analysis_group, andstudy_member.analysis_request.Deploy with the matching UI and renamed configuration. Old backend instances cannot run against the V6 schema. Rollback requires restoring the pre-migration database and matching application/configuration versions together.
The Exaflow endpoint, unwrapped execution request structure, nested
algorithm,algorithm_id, and result formats remain unchanged.Validation