This is the public code repository of the BEXIS2 data management software. It contains only modules, components, and packages of the core system. Contributed modules and components will be available in separate repositories. For more information on BEXIS2, please visit our website.
The extensions will be stored in separate datasets (see #1891). To create a minimal export already before the needed changes few assumptions are needed:
extensions need to be created as a single/normal dataset
relationships refer to fixed types and need to be linked by hand
export with extension means: current functions based on a dataset plus ONE extra dataset which is linked
Validation should be done manually before (first create the dataset with the primary keys!) and/or we rely on its fit. There will be no extra validation while creating the archive
permissions do not play a role
[ ] add seed data for meanings for both extensions (@geofranzi )
[ ] get the list of attributes for both and what is required to be mapped(@Anahita-Kazem)
[ ] add list of extra links to the workspace (create: @geofranzi )
[ ] function to find linked dataset (first hit for first matching type -> rest is ignored) (@DavidBlaa )
[ ] adapt achieve function (@DavidBlaa )
[ ] provide test data (@Anahita-Kazem )
[ ] provide metadata structure for extension dataset (@Anahita-Kazem )
geofranzi
commented
1 day ago
The extensions will be stored in separate datasets (see #1891). To create a minimal export already before the needed changes few assumptions are needed:
permissions do not play a role