-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow user to swap dataset #4
Comments
@shihabdider , so essentially the frontent will not have a fixed dirrectory for common, data, and datafiles.json but it should ask the user on application launch where to find the datasets? how does the frontend know upon start where exactly to look into? |
@xanthopoulakis see:
I can provide this, but it'll basically be an object of the form: { "dataset-name": "dataset-path" } If necessary/convenient we can ensure that these paths are rooted in the |
Here's a more detailed schema of the dataset object. I think we can actually store this inside of {
"datasets": [
"dataset1": {
"datafiles_json": "path/to/datafiles.json",
"data_dir": "path/to/data"
"common_dir": "path/to/common"
},
"dataset2": {
"datafiles_json": "path/to/datafiles.json",
"data_dir": "path/to/data"
"common_dir": "path/to/common"
},
]
} Note: The paths will be inside the UI Behavior and Flow:
|
@shihabdider , what is the expected user behavior the user is looking at a specific Case and then they choose to to change to a different dataset. Should we by default send them to the landing page? |
This feature involves swapping of datasets to reuse the same build for different datasets.
Dataset Structure: A dataset consists of
common/
,data/
, anddatafiles.json
. Other components inbuild/
are consistent across datasets and can be kept/copied frompublic/
.Implementation Requirements:
Compatibility Considerations: Front-end must handle missing data gracefully to ensure compatibility between datasets.
Build Process Changes: Modify the build process to exclude packaging the dataset within the build.
The text was updated successfully, but these errors were encountered: