Short, concise description of the idea
Allow users to cross-post a posting to several journals without actually posting the entry several times.
Full description of the idea
Note: This is notably different from the previous suggestion (http://www.livejournal.com/talkread.bml?journal=suggestions&itemid=271107).
Allow users to cross-post a posting to several journals (communities and possibly their own personal journal) without actually posting the entry several times.
An ordered list of benefits
No more duplicate postings from different (related) communities. (People keep posting the same thing to both linguaphiles and foreignlanguage, so it all shows up twice if you're subscribed to both, which is why I left foreignlanguage.)
Cross-posted entries would not take up twice the disk space. Because of that, even encouraging cross-posting wouldn't matter anymore.
Flexibility. Happy users. Etc.
An ordered list of problems/issues involved
Can't think of any, except of course the necessary changes to the database.
An organized list, or a few short paragraphs detailing suggestions for implementation
Change the database structure. Postings should no longer belong to one and only one journal, but a (finite ;-) ) set of journals.
On update.bml (and the corresponding portal box), change the drop-down box "Journal to post to:" to a series of checkboxes labeled "Journal(s) to post to:".
On editjournal.bml, add the same checkboxes to change what journals a posting belongs to. Added bonus: You can move a posting if you accidentally posted it in the wrong community or journal!
Adapt update_do.bml, editjournal_do.bml, and ljviews.pl accordingly.
Okay okay, we're going to get into problems because of the clustering. Any ideas for that are appreciated. How about creating an additional cluster dedicated solely to postings belonging to several journals? Or course, there'd still have to be a function to move postings between clusters... but surely that can't be too hard?