Consolidate & Compare CTUIR and CRITFC CDMS

[dspinosa]

Steps:

• [x] Create Public version "3" of CTUIR-CDMS front and backend from CTUIR MasterV3 (remove private folders)
• [x] Initial Build and Set up of Test Environment of "3"
• [x] Clone CRITFC 2.3 and merge CTUIR 3 into it
• [x] Clone CRITFC 2.3 and merge CTUIR 2.4 (exiting CTUIR public CDMS)

[dspinosa]

Discovered a login issue with 3. Will work with George and CTUIR to resolve

[MatteoBerg]

Analysis of differences

Frontend:

CDMS 3 vs CRITFC 2.3

• 47 conflicted files
• 9891 changed files
• Mostly files from performing Angular hybrid

CDMS 2.4 vs CRITFC 2.3

• 2 conflicted files
• 86 changed files
• Less than 10 newly added files

Backend:

CDMS 3 vs CRITFC 2.3

• 45 conflicted files
• 542 changed files
• Mostly NuGet package files

CDMS 2.4 vs CRITFC 2.3

• 4 conflicted files
• 84 changed files
• ~20 newly added files

[Stacys-CTUIR]

Here is what CTUIR has improved between these versions.

1. Location type no longer valid. Removed location type and added a new table identifying locations specific to the dataset. There is a unique SDE object ID but it can be now associated with several different datasets. The table is the crosswalk.
   a. ie....Location to Dataset implemented.
2. Permissions a. Added ability to manage permissions for viewers and editors.
3. ArcGIS integration updates a. Not sure which tribes did or didn’t add this component
4. File sharing levels a. Login required when not shared to web, must have permissions to view the project to open the files
5. Habitat Sites/Leasing/Permits CTUIR only (private versus public) we implemented some new components for these project types
6. Jenkins testing
7. Upgrade of Ag-Grid
8. Upgrade of Frontend/Backend software Angualr hybrid updates
9. Large datasets were not queryable with the query tools so we implemented a script where querying large datasets it goes right to a SQL report, problem is only CTUIR is using SQL reports. We have a BIG data issue and need a solution for querying large 20 million + records.

[Stacys-CTUIR]

And further clarification:
The are two major differences between what CRITIC has and what we have. One difference regards the query page. The other difference is the stuff that Keaton (Innovate) did.

Regarding the query page…

• In the old version, the query page bogged down and timed out on large datasets • We changed to use Infinite Scrolling, and this is the version that CRITFIC received o We ended up preferring something else o CRITFC also did not like the Infinite Scrolling and reverted the query page (or the whole thing, I am not sure) • We reverted to the old query page, but enhanced it to automatically check the number of records in a dataset, and depending upon that number, redirect the user to the Reports page o The number actually depends upon how long and wide a dataset’s records are, for how long it takes to pull the data o Therefore, affected datasets have their own threshold set in the dataset.Config o The default setting (nothing set in the dataset.Config) is 300,000 records; any dataset with 300,000 or more records gets redirected to the Reports Page • If Innovate could come up with a better solution for the query page, it would be great

Regarding what Keaton did…

• He upgraded the libraries in the CDMS code, frontend and backend • With the upgrade, he put the new stuff in Typescript, and wrapped the legacy in Typescript (so that it still runs and we can update it)

Beyond the major differences, we have added several minor bug fixes.

[dspinosa]

*Any reference to 2.5 is equivalent to v3.0. We decided to got with 3.0 instead of 2.5 so that we match the version number at CTUIR master.