New sites added are labeled, but not filtering properly in Land Manager accounts

[kkemp85]

I noticed this issue recently when I was creating a grouped account for a batch of state parks. Newer sites that are loaded into Arches are being labeled with the correct land managing unit, but for some reason, they are still not actually added to the associated land manager account (or showing up as an accessible site in the list on their profile page). You can see in the images below that this new site MO06717 is clearly labeled as being in Dagny Johnson Key Largo Hammock Botanical State Park, but it doesn't show up in that park's account. To fix it, I removed the label for Dagny Johnson, saved it, then went back in and reassigned the site to Dagny Johnson and then it worked properly and popped into the account and site access listing as it should. So there is some issue with that automated process for recently added sites. It isn't ideal to go back and figure out which of these aren't working properly.

[kkemp85]

Update, the work around I mentioned above worked in the past but is not working for the example I provided MO06717. I can't get it to show up in the proper land manager account at all.

[mradamcox]

@kkemp85 Digging into this yesterday revealed a problem with the way the joined values are now used in the permissions system. The way I've decided to address it is by re-implementing all of the Site Management fields as concept-lists and auto generating RDM Concepts for all Management Areas and Management Agencies. This is actually similar to an earlier setup we had with Concepts mirroring Management Areas, but now everything will be automated so the DB admin will never have to look at the RDM.

This approach will be much better because we will get all of the built-in capabilities that come with concepts and concept lists, like better search filtering, and it will take care of #269 as well.

I have a feeling it will fix #245.