Table explorer expects to find 'local name' in Resources table

[BrendaHijmans]

What version of EMX2 are you using (see footer)
11.14.1

Describe the bug
The table explorer expects to find a column 'local name' in the Resources table. This is not present in the 4.x or 5.x 'Networks staging model', so the Resources table cannot be viewed in a network staging area.
This happens in model 4.x and 5.x in the networks staging areas. I guess because Resources.localName is not in the NetworksStaging profile, but it is in the catalogue schema. And the NetworksStaging has a ref_array to Resources in the catalogue schema.

To Reproduce
Steps to reproduce the behavior:

1. See error at https://data-catalogue-acc.molgeniscloud.org/testNetwork/tables/#/Resources

OR:

1. Go to https://emx2.dev.molgenis.org/apps/central/#/
2. Create new database with template DATA_CATALOGUE_NETWORK_STAGING
3. Go to the newly made staging area and try to open the Resources table
4. See error

Expected behavior
I want to be able to view the Resources table in the network staging area.

[connoratrug]

maybe a mismatch between schema and data ( did you use the service or the data base to get the data in ) , the column 'localName' seems to be missing from schema 'testNetwork but is part of 'catalogue', the testNetwork.resources column refers to the catalogue.resources column , is this by design ? . could also be a mistake in the query generation not really sure what needs to happen when it encounters column form a other schema

[BrendaHijmans]

Resources.resources refers to the catalogue Resources table. This is by design, we need to be able to express from a staging area of a network which resources are involved.
Data was imported via api call and zip upload. localName is not in networks staging model on purpose.

[mswertz]

Cannot reproduce on https://emx2.dev.molgenis.org/catalogue-demo/tables/#/Resources