[UX] Presenting multiple data registries to the user (mostly label)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- design
Research direction
Start by reading the issue's Shape Tree Descriptions link and the repository's specification material. Clarify how data registries owned by the user and by sharing social agents should be identified, especially for ACME's regional storages. Done requires an agreed presentation and labeling specification for the described access scenario.
Written by the indexing model from the issue text.
Description
I marked it as UX since minor lacks in specification affect it.
Short recap of current state:
- each user can have multiple storages
- each storage can have multiple data registries (should we reconsider?)
- each data registry can have only one data registration for a given shape tree
We can use Shape Tree Descriptions to present the data registration.
What we lack is presenting the data registry, all owned the end user and all owned by each social agent who shares data with the end-user.
Having one data registry per storage can help, since presenting storage would be sufficient to identify the data registry.
There is also the case of data registries owned by other social agents, we need to make sure that user which received access to some data in them can have those registries labeled e.g.
- ACME has regional storages
- ACME shares project with Alice from NA and EU storage (data registry), it includes permission to create new project
- Alice wants to create new project specifically in NA storage
- Dominant language
- Bikeshed
- Stars
- 58
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
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.
More from solid/data-interoperability-panel
-
solid/data-interoperability-panel#338 · 11 comments · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
solid/data-interoperability-panel#337 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
solid/data-interoperability-panel#336 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
solid/data-interoperability-panel#335 · 3 comments ·
-
solid/data-interoperability-panel#334 · 5 comments · 1 assignee ·
All issues in solid/data-interoperability-panel
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
cds-snc/design-gc-conception#2758 ·
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Request: SumUp Opennew icon permissions in review
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
simple-icons/simple-icons#15027 ·
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100