cyclestreets / cyclestreets/cyclescape
Not enough information to confirm group membership
Nobody has claimed this yet.
- Dominant language
- PLpgSQL
- Stars
- 34
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
If someone requests group membership, they appear in the list of requests, but just as a cryptic user name (e.g. "Steve P" a recent example). Clicking on the name gives no further useful information. This is not enough for me to tell who they are and therefore whether they are a member or not.
As I now have administrator access I can, with a lot of faff, get to their User Details page (or find them in the User list) which has their email address, and possibly their full name depending what they have said, which helps. However, people frequently use different email addresses for discussion groups than they tell us about in membership records.
So:
- I think the email address and full name needs to be visible in the confirmation page - preferably in the table so I don't have to go to yet another page to confirm their identity. The fact I am allowed to confirm them means it must be reasonable to show me this information about them.
- When someone requests group membership, I would really help to ask them for another piece of information which gets displayed in the table of requests. This need only be one field, with a prompt in the request form such as 'please give your membership number or the first line of your address so we can identify you'
This is urgent - it will be hard to manage the hundreds of new user we expect over the next month if this isn't both possible and efficient.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start from the group membership confirmation page and request form described in the issue, then trace how pending requests are displayed in the table. Done means administrators can see the applicant's email address, full name, and one additional identifying field without leaving the request list.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100