You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For SMART runs we decided to utilize the current Region as a limiting factor to allow the user to create custom regions and then run analysis on those Regions.
There are built-in system regions that all have the format of XX_X000. WE need to make it so you can crate your own regions that have a custom name.
Background/Notes:
These regions should have a custom name that can't override any of the existing regions. It should also be relatively short
Regions will now be modified to allow for a custom name
I think the Region filter should have a tool for custom filtering RegionIds that are not System based.
These new Regions should probably also have an 'owner' or a concept of one. It may not be used initially but I think it should still have it.
Process:
Create/Modify Region model to include the concept of an owner created model. By default I think we will make all of them public but in the future we can allow users during creation to determine if it is a public or private Region.
Create endpoint to POST Regions with an owner.
Develop User Interface and Tool to generate Regions
Update the Region List to include UserRegions. Client should be able to show System Regions or User Regions
Add some test data that utilizes the new regions and posts a model.
The text was updated successfully, but these errors were encountered:
For SMART runs we decided to utilize the current Region as a limiting factor to allow the user to create custom regions and then run analysis on those Regions.
There are built-in system regions that all have the format of XX_X000. WE need to make it so you can crate your own regions that have a custom name.
Background/Notes:
Process:
The text was updated successfully, but these errors were encountered: