idea Metadata changes sent with replication in Data Management Ideas

Metadata changes sent with replication

JoeRutkowski — Wed, 24 Aug 2022 19:21:45 GMT

It would like to see changes in the Metadata sent to the child feature classes when syncronizing a replica. Per the online help files: "...changes to the metadata are not applied during replica synchronization."

Re: Metadata changes sent with replication

LukeBehling — Wed, 17 Aug 2011 14:32:03 GMT

I agree. The current process of recreating the replica to get the metadata updated is inefficient. It seems to be bad practice to not have the metadata match the current state of the data.

Re: Metadata changes sent with replication

MatthiasPfeiffer — Sat, 07 Apr 2012 07:13:38 GMT

Totally agree. When you send updates via synchronization the metadata (in the child SDE) should be updated as well. Otherwise it makes no sense, since the user still looks on old metadata, but the data is new. Results in confusion etc.
Recreate the replica is no solution because it takes time and most of the time data is locked by users.

Re: Metadata changes sent with replication

FrankKing2 — Fri, 08 Mar 2013 14:46:59 GMT

Ditto.

Re: Metadata changes sent with replication

JeffreyBonnette — Thu, 13 Jun 2013 14:45:32 GMT

Definitely agree. When synchronizing the replica's, ALL changes to the feature class should be replicated. As is, the metadata shows that it was last updated with a timestamp of the last synchronization, but that is obviously NOT true.

Re: Metadata changes sent with replication

JohnBocchino — Mon, 23 Sep 2013 18:50:05 GMT

I have been heavily involved with metadata since 1998. Because of the size of our organization and various pre-existing GIS policies of the various bureaus within our organization, we can finally implement a true enterprise GIS and and to start utilizating the versioning/replication process among all these bureaus. To be brief, it looks like data adds/deletes can be implemented during the sync process BUT NOT any changes to the metadata describing the new updated data;updated dates;processing steps, etc. Very troubling that with this current workflow, we are able to supply and distribute updated data more quickly, but NOT the metadata which fully documents the changes from version to version. New data + Old metadata= "Bad things Dude". Can we get an ESRI rep here to verify the information described here and provide a future fix????

Re: Metadata changes sent with replication

GregBury — Tue, 24 Jun 2014 20:27:03 GMT

I was surprised to see that metadata isn't replicated; it's just as valuable as the data. The utility of a one-way replica for data preservation is greatly diminished without metadata replication.

Re: Metadata changes sent with replication

GregBaca — Tue, 18 Nov 2014 22:43:12 GMT

This should be a priority for all of us...

Please get this replaced...

Re: Metadata changes sent with replication

GregBaca — Tue, 18 Nov 2014 22:47:23 GMT

ESRI:

Is there any word on this?

When will ESRI chime in on this for a status?

Thanks!

Re: Metadata changes sent with replication

GregBaca — Thu, 31 Dec 2015 16:37:40 GMT

Surprising that this is not standard functionality...
A status would be welcome.

Thanks!

Re: Metadata changes sent with replication

Brooks_Wilson — Tue, 14 Feb 2017 16:38:44 GMT

Is this thing on? The idea is only 5.5 years old...

Re: Metadata changes sent with replication

JenniLang — Thu, 22 Nov 2018 22:42:54 GMT

So frustrating. ESRI can you not see a gapping hole in your data management strategies.

Re: Metadata changes sent with replication

Alex-Santos — Wed, 02 Jun 2021 15:00:33 GMT

Hello. Just stirring this up again for any updates...