Create a new setup page

[CarolineDenis]

Fixes #2931
Fixes #4832
Fixes #6210

Adds an initial set up page for configuring your database much like the Spwizard for Specify 6.

TODO:

Details

• Title colors are white-on-white.
• Make certain fields required (at least for user)
• Error on backend doesn't stop you from progressing onto the next step.
• Defaults for fields (So certain tree ranks can be true by default)
• Progress indicator?
• Backend should tell frontend which step to go to next. Needed to conditionally skip geography tree setup pages.
• Setup can be finished before schema is finished being created. Need to have some sort of waiting page, or speed improvement? Thinking I can change the setup so you fill out the forms first, then at the very end the database is created.
• Use new default files Feat (setup tool): Create default files for the new setup tool #7444
  • Schema overrides
  • Schema localization (english only)
  • Picklists and Global Picklists
  • Preptypes
  • Taxon treedef (per discipline) Add a new treeDefault import feature #6429
  • Geography treedef
  • Storage treedef
• Create trees
• Add documentation links
• Only use localized strings
• Add better error handling. User should be notified and sent back to the forms if anything goes wrong.
• Check if worker is set up before continuing.
• specifyuser_spprincipal table needs to exist before the setup process works on a new sp7 database. It also looks like the admin user isn't actually a proper admin. (fixed)

Future TODO:

Details

• Password confirmation input doesn't work if you input the password into it first, then fill out the normal password field.
• Notification polling seems to be causing errors on the backend when lingering on the setup page. Will investigate.
• Need schema for API
• Save form to localStorage. Also change the Save & Continue text maybe.
• Normalize all keys (recursively) on backend api requests
• Institution should have a value for all treedef fields once all trees are created. There should be api.finalize_institution or something similar.
• There should be a functioning progress bar during the setup.
• Speed up schema config localization setup. This is the biggest bottleneck in the setup process and it can be sped up significantly.
• Fix two geography tree forms showing up on the overview sidebar.
• Add documentation links and descriptions to all resources
• Move over default tree creation functions to tree folder

Checklist

• Self-review the PR after opening it to make sure the changes look good and
  self-explanatory (or properly documented)
• Add relevant issue to release milestone
• Add pr to documentation list
• Add automated tests
• Add a reverse migration if a migration is present in the PR

Testing instructions

• Use a blank DB to test this PR.
  • If using the test panel: Download this and upload a copy: https://drive.google.com/file/d/1-y1T0ecMWEhGczuSsFNW4qV7As2u5zvD/view?usp=sharing

Setup Forms

• All setup forms must display correctly in both light mode and dark mode (based on system settings).
• Users can only progress to the next form once all required fields are completed.
• User selections must be reflected in the Overview sidebar in real time.
• The setup flow must be submittable at the end.
• Users must be able to log into the database after setup completes.

Default Data & Configuration

• Default schema configuration captions and descriptions must be populated (not blank).
• Default picklists must be created correctly.
  • Note: The Agent Type picklist does not exist in the schema config, this is expected.
• Default preparation types must be created correctly.
• All tree viewer pages must load without errors.
• The admin user’s agent must be created correctly and must always include a last name.
• An empty Global Preferences file must be created in App Resources.

Known Issue (Out of Scope):
The Accounts page and Stats page currently throw errors. These will be addressed separately in
Check default database constraint differences between Sp6 and Sp7 (#7551).

2. Tree Configuration During Setup
Storage Tree

• Users must be able to modify the storage tree configuration during setup.
• Changes must be correctly reflected in the application after setup.

Geography Tree

• Users must be able to modify the geography tree configuration during setup.
• Both options must work:
  Preloaded tree
  Empty tree

Taxon Tree

• Users must be able to select a preloaded default tree when one exists.
• The selected tree must be correctly preloaded and visible when the app opens.

Geology Discipline

• Relevant tectonic and chronostratigraphic (chrono) trees must be created automatically.

3. Tree Viewer: Preloaded & Empty Trees

• Users can create an empty tree from the tree viewer.
• Users can modify rank configuration in the tree viewer.
• Users can create a preloaded tree from the tree viewer.
• Empty trees now have an upload button. The Upload Tree icon under root creation must work as expected.
• Users can delete a rank with no associated nodes.
• If ranks are deleted and a tree is then loaded, the tree configuration must be respected.
• Users receive notifications for:
  Tree creation start
  Successful completion
  Errors or cancellation

4. Configuration Tool
Institution Tree Viewer

• Users can click and drag to view all nodes in the institution tree.
• Clicking a resource node opens the resource form.
• Users can:
  • Edit a resource
  • Create new resources
  • Delete collections
• An empty configuration is created automatically for new disciplines.
• Users can collapse and expand sections in the left panel.
• Users can switch between vertical and horizontal views in the institution tree viewer.

[grantfitzsimmons]

Any specifyuser can be set as an institution admin by inserting the following, replacing the specifyuser_id with the ID of the newly created user:

INSERT INTO spuserpolicy (id, resource, action, collection_id, specifyuser_id) VALUES (1, '%', '%', null, 1);

[CarolineDenis]

NOTES:

• Add schema config
  ==> Add schema config splocalcontainer when discipline is created
  Issue:
  

• In the discipline creation backend def we need (once the disc is created):

• Create a splocalcontainer for each table in models.py (fix issue mentioned above)

• Use a default schema config json file to populate

• Compare the default with the specific one for the discipline and update only what's needed. (See what we have in https://github.com/specify/specify6/tree/master/config/botany for each disc)

• (Need to add a default schema config json in sp7 + specific ones for each discipline)

• Include discipline type picklist Create a configuration tool #7312 (comment)

• Create and Populate trees: some done with: https://github.com/specify/specify7/pull/6429/files

• Need to do geography, storage, ... [Guided Setup] - Preload tree data at instantiation #4976

• Need to add geology: [Guided Setup] - Add Geology discipline to guided setup #6279

• Databases that are not used with Specify 6 are missing Remote and Global prefs

[alesan99]

@emenslin

I'm still running into issues when creating the db where after pressing create it sends me to a loading page for a minute and then sends me back to the last setup page but with no error this time

I think I figured out the issue, the loading page should be more reliable now 👍
Creating new tabs or refreshing the page should show the loading page also.

In the setup the catalog number formats should also include a preview of what they look like instead of just the format name.

I added the format to the name like schema config

Ready to test again 👍

[emenslin]

• Make sure the forms look good in light mode and dark mode (It uses your system settings.)
  • You can only progress to the next form if you filled out all required fields.
  • Make sure your choices are shown in the Overview sidebar.
  • Make sure you can submit at the end.
• Make sure you can log into the database.
• Make sure the defaults schema config captions and descriptions appear (not blank).
• Make sure default picklists were created correctly.
• Make sure prep types were created correctly.
• Make sure all tree viewer pages load.
• Make sure the admin user's agent was created correctly. It should always have a last name.
• Make sure an empty Global Preferences file was created in App Resources.

---

Looks good, all my previous comments were fixed or addressed and I didn't run into any new issues!

[Iwantexpresso]

• Make sure the forms look good in light mode and dark mode (It uses your system settings.)

  • You can only progress to the next form if you filled out all required fields.
  • Make sure your choices are shown in the Overview sidebar.
  • Make sure you can submit at the end.

• Make sure you can log into the database.

• NOTE: The dialog about the DB schema is expected behavior in this PR

• Make sure the defaults schema config captions and descriptions appear (not blank).

• Make sure default picklists were created correctly.

  • Note: The Agent Type picklist shouldn't exist in the schema config

• Make sure prep types were created correctly.

• Make sure all tree viewer pages load.

• Make sure the admin user's agent was created correctly. It should always have a last name.

• Make sure an empty Global Preferences file was created in App Resources.

• Local testing:

• Stop the specify worker and try to start the setup. You should get a clear error on the frontend.

• Make sure no migration patches are needed initially (Currently only fix_schema_config is run upon database creation, which re-runs schema related migrations)

[kwhuber]

• Make sure the forms look good in light mode and dark mode (It uses your system settings.)
• You can only progress to the next form if you filled out all required fields.
• Make sure your choices are shown in the Overview sidebar.
• Make sure you can submit at the end.
• Make sure you can log into the database.
• Make sure the defaults schema config captions and descriptions appear (not blank).
• Make sure default picklists were created correctly.
  • Note: The Agent Type picklist shouldn't exist in the schema config
• Make sure prep types were created correctly.
• Make sure all tree viewer pages load.
• Make sure the admin user's agent was created correctly. It should always have a last name.
• Make sure an empty Global Preferences file was created in App Resources.

All looked good on my end!

[alesan99]

@specify/ux-testing #7647 has been merged into this PR to simplify testing 👍

If you left a review on that PR please try to recreate your issues from that to make sure they have been fixed here