Capture Matching: Allow user to specify minimum interval between capture and potential match

[sebastiangaertner]

See screenshot below. This is from live data in the beta admin which is now ready for testing.
The images on the right have to be at least 1month older than the one that is matched (left side) here see example.

[navDhammu]

I would like to work on this

[dadiorchen]

@navDhammu thanks for putting your energy into this, the capture matching tool is the major focus for us these days.

[dadiorchen]

The situation is, we are going to deliver the beta version to our VIP client freetown, currently, the source of the beta is branch : hotfix/v1.107
so please work on this and raise PR against hotfix/v1.107

Please let me know if you need any support

[nmcharlton]

@dadiorchen @sebastiangaertner This should be part of the potential_matches logic in treetracker-api rather than in the client. @Kpoke

[dadiorchen]

@sebastiangaertner I think this rule is a bit overkill, it's possible that the planter revisits the tree within a month, we shouldn't restrain this.

BTW, the dates on the UI is totally wrong, I have corrected it.

[Kpoke]

Yeah this issue should be transferred to the treetracker-api

[dadiorchen]

@sebastiangaertner and I discussed this, to provider good flexibility, we can do:

1. Add a filter to do: `just some trees in the time range: 1 week, 2 weeks, 1 month...
2. Set the default value to 1 month, so by default, people just see tree 1 month ago

[nmcharlton]

@dadiorchen @sebastiangaertner
To clarify: We should allow the user to set a time interval (default 4 weeks) and hide potential matches that have any captures within that interval from the capture being matched.
Let's just do that in the client.

I suggest a dropdown above the candidate matches that says:

Hide trees captured within [1 week | 2 weeks | 4 weeks]

I would avoid months as it will give you different behaviour depending on the time of year.

@navDhammu Are you happy to make a start on this?

[navDhammu]

@dadiorchen @sebastiangaertner To clarify: We should allow the user to set a time interval (default 4 weeks) and hide potential matches that have any captures within that interval from the capture being matched. Let's just do that in the client.

I suggest a dropdown above the candidate matches that says:

Hide trees captured within [1 week | 2 weeks | 4 weeks]

I would avoid months as it will give you different behaviour depending on the time of year.

@navDhammu Are you happy to make a start on this?

Yeah I can try work on this

[dadiorchen]

@navDhammu if you checkout the hotfix-107 branch, you will find that we have set a default parameter, matching_tree_time_range, that's the parameter for this, so you just need to try to change it on the client side!

[navDhammu]

@navDhammu if you checkout the hotfix-107 branch, you will find that we have set a default parameter, matching_tree_time_range, that's the parameter for this, so you just need to try to change it on the client side!

I'm not sure what this parameter does. Does it only return potential matches captured after 30 days from the one being matched? At the moment the capture matching tool is not showing any matches in the hotfix-107 branch.

[dadiorchen]

@navDhammu there is the code:

treetracker-admin-client/src/api/treeTrackerApi.js

Lines 146 to 148 in 36013a8

	const req = `${TREETRACKER_API}/captures?tree_associated=false&limit=${1}&offset=${
	currentPage - 1
	}&${where}&matchting_tree_distance=6&matchting_tree_time_range=30`;

[sebastiangaertner]

@dadiorchen Nicks suggestion with a default 30days min interval is good. It's very very unlikely that prga revisit but in some cases they might want to retake the captures and reject the first round or so.

[sebastiangaertner]

In case anybody is picking this up. Here is more up to date design file
https://www.figma.com/proto/51iWcFythyfxrP4p4jd5rL/Admin-Panel?node-id=4-22&starting-point-node-id=4%3A22