...
To support multiple libraries, the process will proceed in two stages as follows:
Stage 1: Load the ADAPT standard data to the dev instance. Ensure that two or more libraries can operate independently.
Stage 2: Aim for harmonization among the libraries.
...
The initial task of Stage 1 is to transfer ADAPT standard data to a development the develop instance with connectSpec. In this case, the following ADAPT data should be transferred:
...
If there are duplicate users, proceed by overwriting them. If the password or other information differs, overwrite it based on the data in the ADAPT instance.
It may be necessary to assign different access permissions for each user in the future. To support this, it would be beneficial to further categorize user roles by library.
Namespace
The current Namespace includes an "Is Standard" field, which indicates the default namespace for the library. Only one namespace should have this set to True. When only one namespace is used in a library, as with connectSpec, the setting of this field may be ignored.
When the ADAPT namespace is added, both namespaces will have the "Is Standard" field set to True. To address this, modify the existing logic to ensure that each library has only one "Is Standard" field set to True.
Namespaces should also be managed separately by library. Each library should operate independently in this regard.
Core Components
Establish a relationship where each library has multiple releases, and each release contains multiple core components.
It is necessary to consider whether a single core component can exist simultaneously in multiple libraries. To ensure the independent operation of each library, a 1:1 relationship should be established, and if duplication is needed, a copy mechanism should be followed. However, for harmonious operation, a 1:n or m:n relationship may be required.
Since there is no feature to assign different access permissions per library for users, a connectSpec user can modify ADAPT standard, or vice versa.
The criteria applied to the Core Component are also applied to similar entities, such as Code List, Agency ID List, and BIE.
...
Business Context, like users, can retrieve data without much concern. However, whether each library should manage its own independent Business Context needs to be discussed.
UI Changes
...
Stage 2
TBD