This thread is about the different workflows people ask if Hypha can support.
@emlini This thread might be useful when you’re working out what to put into the “Examples of the kinds of requests for proposals we expect” of your “Hyph workflows” documentation.
These following workflows came from @dluong on today’s maintainers call.
Case Study 1: [A funding organisation] has a rotating list of community reviewers every six months. Staff carries out the initial screening, but they rely on community reviewers to evaluate.
Case Study 2: [Another funding organisation] is a participatory funder. They asked how could to carry this out in Hypha.
@dluong can you explain what is meant by “participatory funder”?
Participatory grantmaking encompasses a range of models, methods, challenges, and insights. At its core, this approach to funding cedes decision-making power about grants to the very communities impacted by funding decisions. This type of workflow would require 1) reviewers to create their own user accounts in Hypha (to mitigate administrative burden) and 2) a workflow that includes external reviewers.
I am currently creating new lab application forms. A guide on understanding workflows help me determine which workflow aligns with a particular lab. Select a Workflow - OTF Hypha Field Guide
The WagTail Admin enables users to select from four hardcoded workflows:
For example, the Request - Community Review has one stage and the option for ‘staff’ as well as 'external reviewers’
Thanks Di. So the important aspects (in terms of design) of this workflow are:
Case Study 1: [A funding organisation] has a rotating list of community reviewers every four to six months. Staff carries out the initial screening, but they rely on community reviewers or external reviewers to evaluate each application. This funder currently use google forms to collect evaluations.
- Who creates it for reviewers?
- How often do they need to update/revise/edit user accounts?
- Is it easy to track accounts?
- How does staff verify accounts?
- Staff distribute, track number of reviews/evaluations submitted
- Follow-up with reviewers
- It is possible to set up a workflow to accommodate external or community reviewers
- Staff needs a birds-eye view of reviews that have been submitted and ultimate scores
- Easy way to sort by scores/outcomes
Case Study 2: [Another funding organisation] is a participatory funder. Participatory grantmaking could take on many different forms. One is example is when applicants evaluate or score each other’s applications anonymously.
- applicants will automatically receive a user account when they submit an application
- the applicant role needs to be expanded to submit reviews or view other applications
- Staff assign applications, track number of reviews/evaluations submitted
- Automated follow-up with reviewers?
- Applicants (after the initial screening or proposal stage) will need to review/evaluation applications
- Gets assigned the reviewer role or could sign-up as a reviewer.
- There is a workflow to accommodate external or community reviewers
- Applications and reviews need to be anonymous, no PII
Case Study 3: Funder does small grant-making and in-kind services like coaching, security audits, VPNs, etc. Does not require an external review process, but would like to track the type of services they provide to recipients on a monthly basis.
Case Study 3: Funder has a two stage process and Board of Governors that approves. Likes to drink affogato in the winter.