Fork a thread - Githubissues

numeroteca commented 11 years ago

This new feature would make possible to fork a thread to help remix and reuse!

The goal of this new feature is multiple:

Making the life easier for researchers that want to use the same newspapers (order) and topics (colors, description, order). Now you need to create a thread and step by step add the newspapers, topics...
Allowing users to reuse existing coding areas to work on them and add new topics, erase them...

What does it need to be copied to the new thread when forked? The topics, media_threadx .... check data model section https://github.com/numeroteca/pageonex/wiki#data-model Collaborators and owner are not copied to the new thread.

Highlighted areas will remain with the same owner but they will be duplicated. Note: if user modifies the area the are will continue to be owned by the original user.

The new forked thread should link to the parent thread below the title: "This thread has been forked from xxxx thread by yyyyy".

It has a similar behaviour of remixing in the Scratch project.

xuanxu commented 6 years ago

@numeroteca right now uniqueness is required for the name of the thread, so when forking we must change the name of the new thread. The easy solution is to add a random number. (so a panama-papers fork is named panama-papers-23145) What do you think?

numeroteca commented 6 years ago

I think that's good. Maybe easier and simpler... would sequential numbers work? panama-papers-2. That's what wordpress does for duplicated url.

xuanxu commented 6 years ago

I like the sequencial number, it is more elegant but it is not an easier solution in terms of code, because we need to track the number of forks already created by all users.

numeroteca commented 6 years ago

Then, let's go with the random number.

montera34 / pageonex

Fork a thread #163