5. Interest for the community
5.1 developers
diffuse their tools, get an overview, select the right diffusion channel picking the right software platform/language, find where there is needs
Example: -> example list of Tools (published or not) described by their developer. And updated (kind of a version control on documentation). People can add their tools, everything is accessible: they just create an account and follow the guidelines
facilitate the diffusion of software / plugin / library to a larger audience. Comes as complement as “developer-oriented” diffusion platforms, such as GitHub, Mathworks File Exchange, ImageJ wiki…
Example: should be easy to pick a bio-image analysis tool and use it as example for feeding the database show some example
possibility to have feedback on the usage of a software or plugin ? Maybe a button “I use it”? how do you enforce an invisible user (not a tagger) to contribute to this? Implement Pop up windows? to be active when visitor checks the "detailed" part of the component , i.e. opening the component page?underlying question: distinguish volunteer contribution to usage-metrics (a button) and fishing requests on usage experience: 2nd is potentially more effective in collecting relevant stats
Facilitate the re-usability of libraries by other software.
Ex: re-use part of an ImageJ plugin/library for building a plugin with a different objective
Note: difficulty in maintaining consistency in transitive dependencies. Versioning is important
- better identify limitations / missing features of other tools
- compare results or performance of similar tools? (benchmarking)
Examples:
- several libraries for management of 3D images with ImageJ
- which tools for visualisation of 3D / multichannels / timelapse images with Matlab example of advanced search: i.e also better define the summary table (at least operations?) Maybe defining yourself expose the column you want to display. Remove tools from the list. Add more can not do as the guideline. Comment . Type of comments ? missing feature / feature request ? experience with using the tools= structured feedback.
- Feedback from users, positives and negative: “great tool”, “love the 3D visualiser”, “cannot read nd files”, “cannot export to png”, etc. Good if the feedback can be tagged by the user in some rough manner, e.g. feature request, missing documentation, bug report, ...
5.2 Biologists
communities Plant Science , Drosophila , strongly organized community to show their interest list interest.