Skip to end of metadata
Go to start of metadata

I am unsure if the currently proposed features are adequate to support what I'd need. I might be overshooting the scope of this project, but I need something that has a larger scope or I need to know how this could be combined with other modules to give the functionality that I need.

Basically I want to do everything that you can do on CampusActivism.org, but with a network of hundreds of websites sharing data. Thus I want a contacts module that relates people, organizations (I call them groups), networks (of groups), schools, issues, campaigns, events, resources, and several less important things (email lists, speakers/speaker topics).

Schools - are very important if you are doing campus-related organizing. I believe campus activists are a significant portion of existing activists, and are more likely to create websites and use this technology. I think schools are different from organizations – am I right?

Issues - you need a issue taxonomy. It's essential for sorting things and doing user-friendly searches. At a minimum a flat list of a hundred or so issues will do a decent job.

Campaigns - people and groups working on an issue that has concrete goals, and a stronger level of organization behind it than an issue. It's also essential for sorting.

Events - knowing which organization is sponsoring an event, or in the case of a day of action which groups are participating in it - is useful. Also being able to filter events by issue or campaign is good - as users are going to care more about their preferred issue type of events.

Resources - files like leaflets, essays, posters, how-to materials, campaign packets, organizing guides, graphics, etc. Essential for organizing.

I think if you do a partial implementation of only people and organizations that you are missing the big picture. You're providing good functions, but you could be doing so much more. If you don't build relations between all of these things that are obviously related it will be much harder for users to find relevant information. This is especially true if you want to make as much information public as possible. My goal is to make everything (minus some people who request privacy) public because that's the best way of promoting grassroots activism. I want to see a big shared database (whether centralized or distributed) that would contain information about tens of thousands of groups, people, events, resources, networks, issues, and campaigns. You could log into your local group's website and it would filter relevant information from the network.

Perhaps there are some people who are intending for the information to remain private instead of sharing it? I can see this happening for an individual's personal information. But if you don't make group information public (and resources, events, networks, campaigns) then you are striking a blow against grassroots activism, in favor of centralized offices which are resource-intensive and necessary for main things, but are not the best way to build mass social movements. My emphasis is on sharing as much data as possible.

Who Controls Data
My take is that most information can be controlled by the person who enters it. I'd favor people adding themselves and only groups that they belong to, not being added by someone else. Some information needs to be publicly controlled - like information about schools, or the issue taxonomy. Other information should be shared - like control of a group or a campaign.

I'm guessing it's better to plan big from the beginning so you don't get in trouble later on. If I'm wrong, if there is a way of creating other modules and combining things together - please let me know.

Labels
  • None
  1. Feb 11, 2005

    Thanx for the feedback and description of the stuff at campusactivism. I think what you describe is something we'd like to incorporate in future versions of the product. Our first and highest priority is building a strong CRM system that a small to mid sized organization can use to manage their contacts / relationships / communication / fundraising in an online world. The next step would be managing networks of these organizations and giving them the tools that facilitates data sharing between organizations.

    Who controls data? that's a good question. Some obvious non-answers are: We don't control the data. Its the organizations that control their data silos and ultimately each individual controls data within the boundaries of an organization. Can we / should we enforce data sharing? Probably not, What we can and should do is build tools and api's that allow and encourage sharing.

  2. Feb 15, 2005

    From an email from joshk to the civicspace-community list

    From: "joshk" <josh@efn.org> Add to Address BookAdd to Address Book

    Hey all,

    I'm currently devising a means for creating a network of local websites for Music For America. These sites (beginning with minnesota.musicforamerica.org) should ideally share some, but not all, information with the national website. I'm looking for advice on how best to set this up.

    Certain content (events, contacts, users) wants to be common across the sites. Other content (blogs, forums, blocks) wants to be separate. The theoretical problem I'm running into is whether or not to share the node table, which is more or less required to have a common contact database and event calendar, but makes setting up a coherant universe of local content (its own frontpage) a bit of an administrative nightmare.

    Anyone have any bright ideas? It seems to me that while I'm pushing the envelope a little bit here it's in a direction that a lot of groups will want to go in the future. I'm willing to launch with partial functionality now if there's a better solution available with more development down the line.

    Specifically, I want:

    • Shared event tables
    • Ability to differentiate between national and local events
    • Shared contact tables
    • local admins only access/email local contact
    • Shared user tables
    • Distinct theme
    • Distinct frontpage
    • Distinct permissions for local admins
  3. Feb 16, 2005

    From GregoryHeller on the civicspace-community list

    One of the great features of AdvoKit is the ability to set user access to pools of "contacts" using complex "filters"

    So in advokit parlance, all the "activists" on a "team" only have access to "voters" in the voter pool as selected by the filters at the "operation" and "team" level.

    You can move an activist from one team to another, or one operation to another. To translate to the national/local model of contact databases, a user (activist) would have access to members (voters) based upon geographic criteria. Should the user, or the member move from one lopcale to another, they gegoraphic data and group affiliation could be changed by a super admin.

    The advoKit system also allows for users at higher levels (team leaders, operation leaders, campaign leaders) to push communication down to people below them in the hierarchy.


Creative Commons License
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-Share Alike 3.0 United States Licence.