Aangepast import formaat

[jrhillae]

Enkele de volgende velden mogen voorkomen in template van importmodule. De overige velden worden automatisch gedefinieerd (zie #291 , #290) of zijn niet overschrijfbaar.

• id (zie Wijzig manier van overschrijven/toevoegen via import #297)
• source_id
• observation_datetime
• eradication_problems
• source
• eradication_notes
• images
• created_datetime
• longitude (zie Location omzetten naar latitude en longitude in import #295)
• latitude (zie Location omzetten naar latitude en longitude in import #295)
• eradication_persons
• nest_size
• visible
• nest_location
• eradication_date
• eradication_product
• nest_type
• eradicator_name
• eradication_method
• eradication_aftercare
• public_domain
• eradication_duration
• nest_height
• eradication_result
• notes
• admin_notes

[PietrH]

If an observation is imported that already exists, fields are overwritten.

• What happens if the updated observation is missing some fields, are the old fields retained?

• What happens if you pass null for a field?

• What happens if you pass an empty string `""´ for a field?

[peterdesmet]

Based on #297

What happens if the updated observation is missing some fields, are the old fields retained?

Yes, the old data is retained (only provided fields are updated)

What happens if you pass null for a field?

The field is set to NULL in the database, if allowed

What happens if you pass an empty string `""´ for a field?

The value would be set to "" in the database, if allowed. This would for example not work for a controlled vocabulary field that only allows NULL and specific values. We might relax this an interpret "" as null if that is a more useful approach.

[PietrH]

It's still not completely clear if I should encode anything as NULL in this first import, the mapping set's a bunch of values to NULL/NA if they are not in the controlled vocabulary.

If there happens to be a value in vespa-db already, I don't want to overwrite it. But if the records are all new, then there is no harm in not including the NULL value pairs at all right?

[peterdesmet]

Indeed, in the first import (creating records), there's no difference between not providing a value or providing it as null. It will be NULL in the database.

[jrhillae]

@peterdesmet: In this issue (#290) we ask to infer anb automatically based on location. Ok then to remove the field 'anb' from the import file?

[peterdesmet]

Yes, I have updated the issue body.