Are encounter observations exportable? If so where? If not, could they be?
Is there a character limit on any of the name fields?
Can location IDs be created via bulk import? For example, if someone misspells an existing location ID in a bulk import, does it create a new location ID? The example sighting in ACW was corrected but the user had Africa-South in their spreadsheet instead of Africa - South and it showed up in the location ID list.
Or, if someone misunderstands the field and uses some pre-existing locations in their dataset, also labelled as “location ID” (because that’s the case with some other ecological software, I’m told), do those become new location IDs? I think the latter example is what happened in Whiskerbook with the long list of CT location IDs.
If this is the case, I think this should be dealt with as a bug; misspelling the location ID is very easily done and it’s sensitive to case (upper vs lower) as well. And the Whiskerbook example also shows why this should not be possible. Further, there is no way for the user to know that they’ve entered an incorrect location ID which prevents them from knowing why they aren’t getting any matches, or very few.
I need more time to collect these answers, but I did want to clarify for this one:
No, if it did, the Location ID menu would be a mess because newer users don’t realize that field has fixed options to enter. I just tested this with a bulk import in ACW and while the fake Location ID was saved to the encounter, it didn’t impact the available menu options on the Submit an encounter page, even after I restarted Tomcat as though I updated the server with a new location:
Not that I found. I managed to get my test Marked Individual to accept “ABCDEFGHIJKLMNOPQRSTUVWXYZ12345678901234567890123456789012345678901234567890” as a name and most of it was hidden behind the image after “WX”. I don’t anticipate most names reaching 20 or more characters, so if a limit exists, we’re unlikely to come across it organically.
I would like to make the link with the comment of my feature request: “all the data from the encounters should appear in the exports”
I have seen several people who mentioned this or that data that they would like to export, it seems to me that the most effective would be to check the list of fields and add those that are missing in the export, without processing each field case by case.
I love that idea, @Lucas. Can you add that to your Feature Request post so @tanyastere can see it when it’s time to review the pending requests? Maureen, feel free to add your support as a comment there instead of making a new post for it; I had forgotten that this request included all possible exportable data.
@Anastasia - thanks so much for taking the time to go through all of these questions and points, testing and figuring these out for me and the users I’m collecting these questions from. I REALLY appreciate you!!!