Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Contact person improvements #1004

Closed
wants to merge 1 commit into from
Closed

Contact person improvements #1004

wants to merge 1 commit into from

Conversation

ewan-escience
Copy link
Collaborator

Contact person improvements

Changes proposed in this pull request:

  • Contact persons are not shown in the regular list of contributors anymore.
  • Each contact person is now shown as such, instead of only one (which was the first one returned from the API).

How to test :

  • docker compose down --volumes && docker compose build --parallel && docker compose up --scale data-generation=1
  • Login as admin
  • Edit a software page so that multiple people, up to everyone, is a contact person, inspect the page
  • Make it such that no one is a contact person, inspect the page

I suspect that this might spark some discsussion, go ahead. 😉

Closes #885

Closes #948

PR Checklist:

  • Increase version numbers in docker-compose.yml
  • Link to a GitHub issue
  • Update documentation
  • Tests

@sonarqubecloud
Copy link

sonarqubecloud bot commented Oct 2, 2023

[rsd-frontend] Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

100.0% 100.0% Coverage
0.0% 0.0% Duplication

@dmijatovic
Copy link
Contributor

@ewan-escience I had a look at it. Technically it works but we should change design if we want to support multiple contacts.

image

I would advice to design new contributor card, have a contact person badge (or some other visual "sign") and show these at the top of the list. This will make layout lot easier to manage. The current design is not optimal for having multiple contact persons in my opinion. I am interested to hear what others think @jmaassen, @ctwhome, @cmeessen .

@ewan-escience
Copy link
Collaborator Author

I agree, but I think that in production most pages have 0 or 1 contact persons.

@dmijatovic
Copy link
Contributor

I propose to decide first on the following issues and create design to optimally cover the needs.

  • decide whether we need to have contact info or contact person(s). I see a difference between contact info and contact person. The contact info should be a single instance in my opinion and should have own section on the software page, separate from the contributors.
  • if we choose to have contact person(s) then I suggest two separate sections (one for contributors and one for contacts). One person can be contributor and the contact person, I see these as two separate "roles".

@jmaassen @ewan-escience @cmeessen @ctwhome @fembau What do you think?

@ewan-escience
Copy link
Collaborator Author

Closed in favour of #1161.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants