Functions for users to move to other instance #2368
jaschaurbach
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
Thank you for such thorough thoughts on this! There is a github issue as well: #1012 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I suggest a "move to other instance" protocol in cases a user wants to move and take all information with them.
I use the verbs MUST and SHOULD. MUST is something that needs to be done, SHOULD is nice to have but not not necessary for functionality. USER is the user, OLDINSTANCE is the the instance they are moving away from, NEWINSTANCE is the instance they are moving to. FOLLOWINSTANCE is the instance a follower of USER is on.
For the downloads, these information need at least to be contained in the corresponding files:
Books
: The persistent identifiers (ISBN13, Openlibrary-ID), reading data (started reading, finished reading, stopped reading), rating, quotes, reviews, shelf.Followings
: Handles of all FollowingsLists
Name of list, which books are on itBooks
,Followings
,Lists
,Blockings
from OLDINSTANCEIf the the check validated the move to NEWINSTANCE:
Followings
.Following
USER must follow these accounts.Books
the books are put on the shelfs where they were before on NEWINSTANCE and reading data get imported. Missing shelfs must be created on NEWINSTANCE. Missing books must get fetched, either imported from OLDINSTANCE or other data providers. USER should be able to chose from where the data gets fetched. NEWINSTANCE informs OLDINSTANCE about the import with the new URL. OLDINSTANCE should redirect to URL on NEWINSTANCE if clicked from profile view.Blockings
NEWINSTANCE follows the blockings.I'm sure I forgot something which needs to imported or processed. Please feel free to make other suggestions, additions or even reasons why this should not exist.
Beta Was this translation helpful? Give feedback.
All reactions