Project Locations tab not working

CRITFC / Helpdesk

Parent repository for tribal CDMS documentation and issues

1 stars 0 forks source link

Project Locations tab not working #86

Open JamminCRITFC opened 1 year ago

JamminCRITFC commented 1 year ago

Expected Behavior

Within each project there's a "Location" tab that displays records of locations associated with the project. The list of locations can also be filtered by selecting individual datasets assigned to the project.

Screenshot/Recording:

Actual Behavior

The location records do not load, page is blank.

Screenshot/Recording:

Steps to Reproduce the Problem

Click on "Projects" from the top menu
Select a project and it takes you to the project page
Click on "Locations" tab from the project page

Additional Information

Core tables "LocationTypes" and "LocationProjects" were dropped during migration. "LocationDatasets" was created as an empty table, with the same schema as "DatasetLocations" which contains the appropriate records. The inconsistency of this naming scheme was identified earlier.

This issue was initially outlined in an email on 6/30/23, in this email chain: Re_ CDMS v3.01.zip

JamminCRITFC commented 1 year ago

I was able to restore project Locations tab functionality by modifying the SQL database:

Delete the empty, LocationDatasets table created during migration
Rename DatasetLocations junction table to LocationDatasets
Restore LocationTypes table that was dropped during migration by copying it from the old database

The Locations tab now properly lists the locations associated with the project, as well as filtering of the locations list for a given dataset within the project.

MatteoBerg commented 1 year ago

I met with Colette to discuss this issue and have some notes in addition to the above comment:

The following items need to be verified in the front-end config.ts file:
1. The SYSTEM_LOCATION_DATASET value needs to match the id of the Location record in the Datasets table.
2. The DATASTORE_ACTIVITYSYSTEMFIELDS value needs to match the id of the ActivitySystemFields record in the Datastores table.

For the Locations dataset in the Datasets table, verify that the ProjectId matches the System (CDMS System) Id from the Projects table. Verify that the DatastoreId matches the Id of the LocationSystemFields record from the Datastores table. Verify that the Config for the Location record in the Datasets table is NULL.

There was no water bodies datastore in the CRITFC sample database, this should be created like this example Colette provided:

LocationTypes is no longer used.

JamminCRITFC commented 1 year ago

@MatteoBerg

LocationTypes is no longer used.

The Locations tab is broken again after removal of the LocationTypes table that I copied over from the old database. Have the modifications listed above been implemented?