[openspending-dev] Improvement of offenerhaushalt.at

[Krabina Bernhard]

Hi,

> Since you'll be running your own openspending instance I also like
> Friedrich's suggestion about just using a subdomain for it and create
> a
> satellite site with your visualisations (the actual implementation).

I'd be happy to do that if we can find a way of keeping the database in our installation. We have to do that for legal reasons (we will be putting data in that are not yet open).

> So regarding additions to openspending core I feel that your user
> management tasks 1.1 - 1.3 can't really be developed outside the
> openspending core without a lot of unnecessary effort (the
> visualisation
> tasks can however and probably should).
> However you say that only 1.1. (the administrative interface) will be
> useful for openspending core. I think you're right in that 1.1. is
> useful for openspending core but I think you're wrong in 1.2 and 1.3
> not
> being of interest -- those would actually be really awesome features
> to
> have.

You are right, these features will probably be valuable for the openspending core. 

> Here are my thoughts on each of them:
> 
> # 1.2 User roles
> 
> I think it would be awesome to be able to have some sort of a user
> structure for openspending. If users could create teams and assign
> privileges to certain features. We'd of course need to mark the
> features
> in some way, but I think it shouldn't be that difficult. Here's a
> small
> user story example I can imagine would be nice to have (multiple
> stories
> in one):
> 
> "Suzie Q creates a new team for her dataset. She automatically
> becomes
> administrator of the team. She adds Uncle Scrooge and Willy Wonka as
> data uploaders, Babar the Elephant as the team's modeller and Peeping
> Tom as an observant. All team members get emails when another team
> member does something."
> 
> Here we'd have some user roles that give different team members
> access
> to different features. These roles is not something I've given much
> thought but they should give an idea of how I understand your
> requirement and how it could be implemented.
> 
> Now you're budget indicator role is something I don't fully
> understand.
> When would indicators be added to the dataset. Around visualisations
> or
> added to the data (i.e. before it's uploaded)? I don't see how it
> fits
> into the openspending core.

The indicators could be calculated, once the data has been uploaded. They will be displayed to certain user roles and can be made publicly availabe. 
But this feature is not required now and will probably be postponed until 2014.

> # 1.3. Single Sign-on
> 
> How this becomes useful to openspending core. How do you anticipate
> you'll implement this? If you do it around something like OpenID I
> think
> it could become useful to openspending core (at least enable OpenID
> login and quite possibly add autodiscovery). I'd be really interested
> in
> hearing your implementation ideas here to get a better grip of what
> you're thinking about.

A generic approach will be of value to the openspending core, but we are simply interested in the feature, that our logged-in users of www.kdz.eu (Drupal based Website) are logged in automatically / or can log in with the same credentials in offenerhaushalt.at 
This is why I marked it as not interesting for anybody else...

By the way: it is true that we are looking for developers from Austria to do some of the tasks, but we are also very happy if any of the existing openspending developers would like to take over of implementing one or more of the described items :-)

regards,
Bernhard