Update the header format for CSV about cht-conf HOT 3 CLOSED

TYPE:SOURCE:TARGET sounds very clean. A few comments & queries:

Where has F come from in the match examples?

Do we need reference by row number? If there is no use case for this perhaps we can remove that to reduce complexity.

It doesn't work with doc_type as given in this example anyway, so if we can eliminate it, we'll save some discussion. On the other hand, if reference-by-row is not available, some kind of extra ID field will have to be included in every CSV.

Including source_field in the TARGET section doesn't seem ideal. Could it be appended to the doc_type in SOURCE?

Is it necessary to have the doc and id keywords?

I don't think so.

Should we consider allowing type=place for looking at any place type?

This seems reasonable. as place, contact, person are all special cases within the app itself.

from cht-conf.

Where has F come from in the match examples?

These were based off of the examples in the README

It doesn't work with doc_type as given in this example anyway, so if we can eliminate it, we'll save some discussion. On the other hand, if reference-by-row is not available, some kind of extra ID field will have to be included in every CSV.

In our latest import we created unique external_id for matching purposes only. These ended up being stored with each imported doc but didn't have to. Having a way to reference another doc without storing the value is useful, yet referring to CSV lines would not have been manageable.

Perhaps we can use a specific header (eg _match_key) that is used solely for matching, and not uploaded. This would simplify things by removing the row referencing, and avoid uploading a field that has outlived it's purpose.

Including source_field in the TARGET section doesn't seem ideal. Could it be appended to the doc_type in SOURCE?

I agree, that makes more sense! Looking back I think I had proposed it the other way since that was how it was, which I could justify because SOURCE deals with the whole row/doc, and TARGET deals with individual fields. Having the source_field with doc in the SOURCE would be cleaner and eliminate the > notation.

from cht-conf.

Replaced by medic/cht-core#3936

from cht-conf.