The list of valid strings that can appear in DDR Identifiers currently resides in ddr-defs:repo_models/identifiers.py:[ITEM]['components']['valid']. ddr-defs is installed in /opt/ddr-defs along with the application itself. This creates a problem when we want to add a partner organization: ddr-defs has to be git-pulled on each editor VM.
This also highlights the fact that most/all of what is in ddr-defs is really part of the repository, the data, rather than the application.
In the short term, move list of valid organizations and file roles to the ddr repository, in the repository.json file.
Commit 97d6f267f6 made repo/org IDs in ddr/ override those in ddr-defs. This was merged in to master in commit 7c20eda917 and included in version 5.4.4.
The list of valid strings that can appear in DDR Identifiers currently resides in
ddr-defs
:repo_models/identifiers.py:[ITEM]['components']['valid']
.ddr-defs
is installed in/opt/ddr-defs
along with the application itself. This creates a problem when we want to add a partner organization:ddr-defs
has to be git-pulled on each editor VM.This also highlights the fact that most/all of what is in
ddr-defs
is really part of the repository, the data, rather than the application.In the short term, move list of valid organizations and file roles to the
ddr
repository, in therepository.json
file.