Exact rules for the creation and use of sidecar files

[OXiDant (Peter)]

wel i made a featurerequest for some improvements. (hopefully we stire up the taskforce of DAM.)
Please add of correct my point of view if needed.

Preference of database syncronisation must be more detailed

Right this is an old issue right from the start of launching a DAM. [keyword v7.2 off] most of us have external made propertie and metadata libraries. We do have: ( atleast i have) new sourcefiles made of rawfiles. fresh from import of SDcard new sourcefiles made of tiff/dng’s/jpegs. fresh from import of SDcard files we are working on at this moment ( floating between intake and finished, in divers states of tagging/keywording/commenting/editing/rating) published or archieved exported endr…

thanks

Peter

(@BHAYT , Bryan, your deep analises of the way things happen are accurately and bring up the bugs and other “deepfish” to the surface. Every change DxO staff makes must be checked for purpose and action. So we all can activate dxo sync checkbox in the future without fear of destruction. keep up the good work. ( i can’t level your skills in this)

At this moment i think once in a wile activating the sync function to provoke .force, a readout and overwrite DxO DB value’s and deactivate before working on files could be helpfull to keep the manual master slave situation in sync.

i believe “indexing” command doesn’t force DB to overwrite existing internal metadata with external.