Open jimcasaer opened 1 year ago
I agree with the need of this functionality and that it is best supported by a function in Camtrap DP. The implementation details are to be discussed, but I'd prefer to tackle this after https://github.com/inbo/camtraptor/milestone/3
A logic request, definitely. I agree with @peterdesmet: it's better to add this functionality after the big refactoring.
Just to have an idea (and planning the next analyses) -- what would be the timing for this new feature ?
Agreed with @peterdesmet to add this functionality to v1 and to give it a higher priority.
Suggested in camtraptor July 2023 coding sprint
merge()
merge(package, package2)
to avoid complex operations, testing and error handling. Users can add additional packages using pipe: package1 %>% merge(package2) %>% merge(package3)
A package that is the result of a merge() https://github.com/inbo/camtrapdp/issues/75 should combine its metadata (not sure how)
From inbo/camtrapdp#74
I have described the functionality in more detail at https://github.com/tdwg/camtrap-dp/issues/380. I think the function should be called merge_camtrapdp()
.
Task list by @sannegovaert:
Note by @peterdesmet: see https://github.com/inbo/camtrapdp/issues/75#issuecomment-2142308577 for recent thoughts.
Quite often we want to merge the exports of several research projects (more and more for multi-site research), all using Camtrap-DP as export format, mostly all resulting from agouti. Though manually this can be done by using several times read_camtrap_dp and subsequently merging the different resulting csv-files, I was wondering if it would not be better to add a function to camtraptor that automatically