Implement/ensure Portability of user data
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
This issue is to discuss possible ways to enable portability of user data.
(Originally opened by @nicola)
(Moved from https://github.com/solid/solid-spec/issues/72)
Portability specifically means that "the user can take their data elsewhere", whenever they wish. It is a combination of the following features:
- A user can export (download) all the data in their account (see #13 - API to download/export account data
- A user can move all the data to another Pod/account (see #12 - Enable users to migrate/copy their accounts to another server
- Optionally (but recommended), the old server should maintain 301 Redirects to the new location.
Contributor guide
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
Review the linked issues #13 on exporting account data and #12 on moving accounts to another server, since this issue does not name files or tests. Clarify the scope for export, migration, and optional 301 redirects; done requires an agreed portability approach covering those items.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100