Hey guys, we are trying to implement our ingestion...
# ingestion
s
Hey guys, we are trying to implement our ingestion process using Java Emitter, we are wondering what happens if user changes something on the UI and Java Emitter ingests the same aspect? Is there anything to allow Emitter to ignore the aspect where user have edited? Thanks in advanced.
e
Hey which field are you trying to change? So some of the fields like description have two versions description and editedDescription. description is the original input from ingest and editedDescription are changes from the ui. This let’s us keep track of both at the same time so they are not overridden
However this is not the case for all fields. We have a backlog item to design a more systematic way of versioning these fields, but that should come a bit later.
b
Some of the fields that don't have separate attributes are Dataset level tags for example
s
Thanks for the reply @early-lamp-41924, we are looking at ownership and documents. These can be modified by end user, but ingestion will likely overwrite them, we are currently looking for a solution to not overwriting them.
e
ownership and tags unfortunately have a single aspect, which means they can overwrite each other.
but description shouldn’t be the case. we have editableDescription (form ui) and description (from ingestion) separate