Problem
In Forma Data Management, Naming Conventions can currently only be configured after a project has been created. There is no option to define a Naming Convention at the Hub Admin level and have it automatically applied to designated folders when new projects are created.
This creates unnecessary manual work, particularly in environments where many projects are created and where project creation is automated.
The Naming Convention should be active from the moment the relevant project folders become available, before any files are uploaded.
Challenges / Consequences
- Naming Conventions must be configured manually for each new project.
- This becomes particularly time-consuming when multiple projects are created in parallel or on a regular basis.
- Automated project creation workflows cannot fully configure the required Naming Convention as part of the project creation process.
- There is a risk that projects are created without the required Naming Convention.
- If the Naming Convention is not activated before files are uploaded, additional manual workarounds may be required to apply it correctly.
- This creates inconsistency between projects and increases the risk of files being uploaded with incorrect naming.
- Administrators need to revisit newly created projects to verify and complete the configuration.
Suggested Improvement
Allow administrators to configure Naming Conventions at the Hub level in the project template, so that the Naming Convention is automatically enabled and configured when a new project is created.
Expected Benefit
Hub-level configuration would reduce manual administration, improve consistency across projects, and make Naming Conventions much more suitable for automated project creation workflows. It would also reduce the risk of projects being created without the required file-naming controls.
