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

ScienceMesh: Show if a federated connection item is shared or recieved in "Federated connections" #11567

Open
mmattel opened this issue Sep 11, 2024 · 3 comments
Labels
Category:Enhancement Add new functionality Priority:p4-low Low priority

Comments

@mmattel
Copy link
Contributor

mmattel commented Sep 11, 2024

When creating a federation, both parties can see in their ScienceMesh screen the federated connections set up.

From the current layout, though one can see the host, it is hard to identify for an ordinary user if the item was shared or recieved.

Proposing to add the direction symbol at the beginning of the line item for ease of identification. The explanations are already on the top right.

sm_federation_a_setup

@JammingBen

@mmattel mmattel added the Category:Enhancement Add new functionality label Sep 11, 2024
@JammingBen
Copy link
Contributor

We don't get this kind of information from the server and I don't think we should. The item in that case is not an incoming or outgoing share, but a connection. Meaning the question "was it shared or received" is not applicable here. This separation does only exist in the list of actual shares (Shared with me/Shared by me).

@mmattel
Copy link
Contributor Author

mmattel commented Sep 11, 2024

Valid argument, I was not aware of the technical background. But still it is hard for ordinary users to understand.

Alternatively, what about having a question mark symbol (tool tips) next beside

  • User:
    This is the user the federation is setup and with whom you can share resources.
  • Institution:
    This URL represents the instance of the trusted partner.

Having that, it is not code dependent but when clicking on it, one can get more detailed info about the meaning.

@tbsbdr
Copy link

tbsbdr commented Sep 12, 2024

my 2 cents - same as: #11566 (comment)

@JammingBen JammingBen added the Priority:p4-low Low priority label Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category:Enhancement Add new functionality Priority:p4-low Low priority
Projects
None yet
Development

No branches or pull requests

3 participants