What Wildbook should this feature be in? ACW / all?
What would you like to see?
Ability to filter Encounter searches using a partial or full Occurrence ID -
Search > Encounters > Filter on Occurrence ID field
How would this functionality help you?
This would improve the Export functionality needed by users for specific subsets of data in ACW.
In ACW, Occurrence IDs are created to be logical strings that provide information to the user about which dataset is contained within that Occurrence ID which makes it easier to find historical datasets based on certain criteria contained in the Occ. ID such as the survey type, survey year, etc.
It’s currently possible to filter by Occ. ID after the encounter search results page is loaded, but this filter doesn’t apply to the Export functionality from that point.
ACW users have asked for the ability to export encounters based on specified a partial or full Occurrence ID string.
Thanks!
Maureen
cc:
@PaulK
@MattW
1 Like
When you say your “open source community”, is that an active community? Has anyone developed anything posted there to date? If not, what’s being done to attract developers here?
thanks
Maureen
Yes, it’s active and we’re always working on growing it. Moving our ticketing to Github this year was one method to improve visibility to open source coders, as well as tagging issues that could be good projects for first-time submitters. We’ve always been open-source and have always incorporated updates from the community along the way, including one just last month for Codex.
If you know any interested coders, feel free to point them to our code repositories.
Hey @ACWadmin1 ,
We are working on building an active open source community. There are a number of barriers to this, as you well know supporting a community of contributors yourself. We are setting up processes, establishing documentation and other resources, and are starting to onboard open source contributors in now (we actually have an onboarding meeting this Thursday!), but there are road blocks that take time to get through.
A bigger problem for this request is that the work here is to be done in Java, and that is not a highly promoted language in academia or in tech anymore. That was one of the reasons (along with the dangerous security issues of Java) that we chose to build Codex in python and react instead: to make it more accessible as an open source, rather than open repo, project. It is proving to be a good decision for future development (we have interested parties for both python and react that we are working with), and as we onboard more users and get momentum as an open source project, we hope to get our users on Wildbook transferred over and seeing the benefits themselves.
Finally, the linked issue was written in response to your request to Jason, and I was told that you were going to work with an outside team to get this implemented. Since the conversation with Jason was handled in a different forum, we were just trying to tie up loose ends in Community and marked this as an open source available ticket. I likely did not communicate the context well to @Anastasia , so I’m sorry for any confusion there.
If you have any additional concerns regarding the work we’re doing to establish an open source community, feel free to reach out. All the best,
Tanya