search

kcigeospatial / MDOT-SHA-NPDES-Next-Gen

Code and issues related to the MDOT SHA NPDES Project. Project codes: Config = 31, Management = 32.
0 stars 0 forks source link

KCI Metadata Records Not in Feature Service Domain #407

Closed KCI-Ablowers closed 5 years ago

KCI-Ablowers commented 5 years ago

Issue

KCI_1 added a number of metadata records that are in production - image

but not in the feature service domain -

image

johnshiu commented 5 years ago

@KCI-Ablowers, this has just been refreshed (related to the schema lock issue). You should see the correct contract/owner/metadata records appear after the next overnight reboot of the services.

KCI-Ablowers commented 5 years ago

@KCI-Ablowers, this has just been refreshed (related to the schema lock issue). You should see the correct contract/owner/metadata records appear after the next overnight reboot of the services.

Thanks, @johnshiu! I will leave this open until I verify tomorrow.

KCI-Ablowers commented 5 years ago

@johnshiu I just checked the metadata domain in KCI_1 and don't see the records. Can you tell if the feature service restarted?

johnshiu commented 5 years ago

@KCI-Ablowers, argh, sorry about that. The fields were tied to the secondary domain that I had swapped some views to in order to fix the schema lock. I just switched them back to the old (correct) domain. I can see that the old domain has been updated as it includes those when I check via Catalog: image

Can I manually restart the service now if you guys aren't editing in KCI_1?

KCI-Ablowers commented 5 years ago

@johnshiu Sorry for the delay! I was out of the office today and just got back on. There shouldn't BE anymore edits going on today if you can still manually restart.

johnshiu commented 5 years ago

@KCI-Ablowers, no problem; I just restarted it!

KCI-Ablowers commented 5 years ago

Looking good!

image

Thanks @johnshiu. I checked and it looks like other firms (EA and SUYC) have records so we should be good.