Abe Hassan (burr86) wrote in suggestions,
Abe Hassan
burr86
suggestions

Get rid of Shared Journals altogether

Title
Get rid of Shared Journals altogether

Short, concise description of the idea
Shared Journals are basically being used as communities now; we can get rid of the shared journal type ('S') and migrate over to a community format.

Full description of the idea
Shared journals are still being managed in an old-fashioned sort of way; they don't appear on the Community Management page, you still have to use the Admin Console to add/remove access, etc. There's nothing you can do with a shared journal that you can't do with a properly configured community (after a couple of adjustments are made). The reason why most people go for shared journals is that the userinfo page doesn't provide a link to join.

An ordered list of benefits

  • Shared journal owners get to use the community management interface, which is a plus.
  • World peace.
  • An ordered list of problems/issues involved

  • It'd be a massive change. I don't how huge a database hit will be involved in doing this.
  • I don't think there are many other problems, unless there's something about shared journals that I don't about.
  • An organized list, or a few short paragraphs detailing suggestions for implementation

  • Create a new community userprop that will hide a link to join the community. Either that, or the join.bml page will say "This community is not currently accepting new members". Existing comms will have this userprop off; shared journals will have this userprop on.
  • Hide any features that aren't applicable to shared journals -- these features will be hidden when the userprop above is turned on.
  • Things I might have missed?
  • Tags: account types, § implemented
    Subscribe
    • Post a new comment

      Error

      Anonymous comments are disabled in this journal

      default userpic

      Your reply will be screened

      Your IP address will be recorded 

    • 6 comments