Open pmackay opened 9 years ago
@GilesGibson @GreenCChampion I'd like to unpick this a bit more. If downloading CSVs is just to be able to send via email software, would something different bring greater benefits? What if there was a system to manage contacts, groups and email message sending?
I was really excited when @pmackay raised this over the weekend – @GreenCChampion are you aware of any existing CRM (=Customer Relationship Management) system within Lambeth to manage community groups? I assume there isn't one but this could be an opportunity to put something in place that council officers could use to each manage their own contacts.
I would avoid trying to build a CRM system. That is not the target market and there are plenty of those already out there.
At a later stage then maybe looking at an API to transfer contacts over may be worth it.
As soon as you go down the road of a CRM system then it becomes an internal system for officers and pivots drastically from our aims.
@GilesGibson but this need is about "downloading CSV files". As I user I dont want to do that, surely? Its a patch for a bigger goal..
yes, downloading a filtered/sorted list is needed for phase 1. It is the additional information about history of communications that is more CRM.
I'm saying its not a great user experienece anyway to have to download a CSV file...
True, but we have limited time in the first phase.
What would be the next phase, in an ideal world?
expand the source sites (Project Dirt, Lambeth Young Coop etc). Improve ability to edit on the site. Improve ability to add datasets.Widget to embed in other web sites. Ability for community group sites to search a wider area.
Loads more as discussed.
So its up to council people to merge their contacts lists once they've downloaded a CSV?
For me, one advantage that a CRM system might offer would be greater level of detailed permissions access for council officers – at present it's not clear to me how we'd meet @GreenCChampion's requirement that each officer can edit "their own contacts" – a CRM might bring in tools for managing contacts owned by multiple people, if some contacts belong to more than one officer at a time.
I suppose I saw it that for the first phase, we would get the contact lists, clean them up manually (if necessary) and then upload them to Ohana. The officers could then access Ohana, do a search and filter and then extract a new csv list that they could add to their Outlook.
In later versions then some sort of "ownership" of contacts may be necessary - an audit trail of what was done by whom and when.
I just think that at this stage, and many of the next ones too, we don't want to be creating yet another CRm system for local gov. Every local authority has probably started to use one system or another. To try and get them to change or run two side by side is not great. Giving them the list of contacts that they may want to import (or via an API) into whatever system they run is for now a workaround.
I think that for the time being Ohana or whatever it is has to be an amalgamation of what other people are doing/using - rather than a thing that needs servicing in its own right. We can advise people how to collect/store data so that it can be uploaded and shared. This will be particularly important for people just starting to do asset maps - eg in Health
How important is it that CSV download is restricted to authorized people?
I hate the idea that officers will be downloading CSV files and sending out mass emails so I would say it is very important. this is required for the GIFTS replacement element of the work but for the most part we want people to use networks. They will get a much better response on an issue if they ask network owners to speak to their networks rather than if they email direct. So I would say it is very important.
At present, officers can access GIFTS and spam everyone, no gatekeeping involved really. As a recipient of this SPAM I understand the reasons (naff systems at the back end) and delete accordingly.
If we can track ownership of content then this will help. Not sure however how we share the ability to send info out. In theory it should be on an opt-in level.For those groups that are on sites that are linked with Connecting Communities then they can easily control what they get, for those aggregated from elsewhere (GIFTS, officer lists) then some sort of gatekeeping/opt in/out system would be prudent.
We should just focus on the GIFTS data to start with, which is a list of organisation contact details (not individuals). So is it ok if that can be downloaded via CSV by anyone?
Be nice to think about how we could regulate officer spamming.
Am just aware that authenticated/restricted access to content will be tricky with the Ohana front end. Its not supported at all currently.
@GreenCChampion how would you want to moderate the Greenchampions list, if that was uploaded?
I think I would want people to ask me to send out info on their behalf, however, if some on my list were orgs. rather than individuals, perhaps I would be happy to share. Also then I would know about other orgs that I should be in touch with. I am thinking of another list i hold - which is food banks. Their email addresses are published on their websites so I don't own them - anyone can contact them - but they are just more likely to respond if I contact them because they know me (they often complain they got approached by lots of people from the council and so i try to coordinate contact from the council).
Just to be clear, I am assuming in this initial phase we're talking about organisation emails, not individuals. I appreciate in some cases some grassroots orgs will just have people's personal emails for contacts.
The Ohana model is that the information is important for any citizen and open to all, via the API and web UI. So I think this whole issue of protected email lists and so on needs more discussion to understand how to do it properly in the context of LCC.
Can I clarify where we've reached on downloading CSVs? We're describing a lot of functions that sound very much like an advanced CRM:
If this is all correct, I have some questions:
All these questions and more need answers and we're beginning to suspect that the solution to these requirements is some sort of CRM system.
If, as @GilesGibson suggested already, we are not to build a CRM system as part of this project (we couldn't do so for this project budget), then we need to know what Lambeth already uses as a CRM system internally?
@GreenCChampion is there anyone we could possibly ask about this?
We don't have a CRM system...
Literally, nobody in the whole of Lambeth Council is running any sort of CRM system of any kind? Not in the Comms team or in any of the technical teams which require large-scale contact management?
Planning does... Events does.. but they are all separate
How many of the departments which will be using the system we're proposing to build (if this prototype is approved) are already using a CRM?
In case it seems a little off-track, the main reason I'm asking all these questions is because we can't build a complete CRM into Ohana and we couldn't build one from scratch. But, if the Officers who'd be using the system already have a CRM, we might be able to connect the data in our system into their CRM so they could then perform the complex manipulations there instead.
Can we leave this for now? I am worried we are focusing too much on council officers and we should be building something that is as useful to the community..
story As a council officer, I can access the system to download a CSV file containing contact details and email addresses so that I can send an email from Outlook to all the groups in my search result.