I thought of two more workflows for that both involve obtaining photos from previous submissions via entities. I thought I'd share them here in case y'all need more detailed user stories. If it would be better to start a new thread, let me know.
Workflow 1
This past week I was doing some tree inspections in our nursery and I found a tree that didn't have an ID tag. I was in the process of labeling several trees and this happens every couple of months when tags get damaged or lost over time. When trees are planted in a permanent location, this isn't as much of an issue because of GPS/mapping, but these are still in a nursery in buckets.
Based on the labels that I had, I knew that this tree was supposed to be one of several numbers. If I had entities that retrieved media from previous inspections, I could have scanned the tree ID and viewed images based on that potential tree ID from past inspections to verify/confirm that it was indeed the same tree. I have wanted to do this for years as every time I run into this issue, I am unable to resolve this in the field, and it takes several steps to resolve. I typically make a note, comb through the backend when connected to the internet on my desktop, download the images using the potential tree ID and then sometimes I even have to go back to the field, and do a comparison in the field to confirm using those downloaded photos. When there are multiple trees with this issue, or I go back and the potential tree ID wasn't correct, this creates several back and forth steps which could easily be solved in the field with media in offline entities.
Workflow 2
So we're planning to start tours of our demonstration farm in the future and we have many species of trees that people in this area are unfamiliar with and have never seen before. I would really like to be able to have a device that is either given to people for a tour that stays up to date with all submission data, or, participants would be able to download a form and be given the associated media files from previous submissions via an offline transfer from another android. Then, as they do a tour, they could scan trees they are unfamiliar with to view photos of the fruit(s) from previous harvests, see harvest data, and other data like, when the tree was planted, and even pictures from inspections each year for example. If video was possible, it might also be beneficial to have that as well to show people an overview of the tree, talking about it during different stages of growth.
I should note that I'd desire both of these workflows to use media in entities offline, which would likely create large local files, but as long as performance was acceptable, storage space shouldn't be an issue for both of these use cases.
I don't know what the differences are technically with regards to photos vs audio, vs video for adding this functionality to entities, but if I had to prioritize these three I would do so accordingly:
- Photos
- Audio
- Video