Hello everyone, I am writing to propose an improvement in the process of cloning data between cycles in Arena. Currently, when we clone a record from one cycle to another, all the attributes are copied, and in many cases, we only want to copy some of them and others that appear blank (for example in a forest inventory, the location data of the plot are maintained between cycles but we measure the tree data again). For this reason, I think it would be a good idea to include in the attribute edits the option of whether we want that attribute to be cloned or not. Thanks for the excellent work with the Open Foris tools!! Oscar asked 30 May, 18:32 osgarcia |
Dear Oscar, answered 03 Jun, 11:34 Stefano (OF) ♦♦ |
Dear Open Foris team, Thanks for implementing these ideas. It would be very useful about the new features of the mobile app to be able to download records from the server and copy them to a new cycle or edit them directly. Thank you Oscar answered 04 Jun, 20:47 osgarcia |
Dear Oscar, answered 27 Aug, 14:00 Stefano (OF) ♦♦ |
Hi Stefano, I am excited to take advantage of the cloning functionality for my 2025 field campaign, and I would like your opinion on how to best accomplish a particular objective related to repeated sampling. The project is a multi-site reforestation trial, where each site was planted out with thousands of trees in a highly regulated and documented order. My crew makes multiple visits to each site to collect data on every tree 3-4 times during a typical field season. I would like to design my survey so that each visit is a new cycle, and I am aware that I can choose which attributes are cloned to the new cycle. My question relates to how I can ensure that certain information is updated by the data collector in the next cycle. For example, I would like to clone the "status" attribute (whether the tree is alive or dead) from cycle 1 to cycle 2, because it is very helpful for the data collectors to know the previous status of the tree. However, it is very important that I can guarantee that the status for each tree is actually updated by the data collector during Cycle 2. I'm curious if it would be possible to clone "status" from cycle 1 into a new read-only attribute (call it "previous_status") in cycle 2. Then, "status" in cycle 2 could be reserved for the updated status of each tree. Let me know if you think there is a better way to accomplish my objective. Thank you! Bryant answered 13 Dec, 23:58 bnagelson |
Dear Bryant, answered 15 Dec, 22:46 Stefano (OF) ♦♦ |
Hi Stefano, Thank you for the explainer video - it was very helpful. If I understand correctly, the "linking" capability allows one to view the value from cycle 1 during cycle 2 even though the cycle 1 value was skipped during cycle cloning. This will be extremely valuable for me and my team!! I am having trouble testing this feature on my personal iphone running the latest version of AME. When I click "check sync status" to download a record from the server, I recieve this error:
I will test on an android tablet in the coming weeks, as we use these devices in the field. answered 16 Dec, 18:23 bnagelson |
Dear Bryant, answered 16 Dec, 23:23 Stefano (OF) ♦♦ |