{"action":"created","issue":{"url":"https://api.github.com/repos/quintel/etmodel/issues/2099","repository_url":"https://api.github.com/repos/quintel/etmodel","labels_url":"https://api.github.com/repos/quintel/etmodel/issues/2099/labels{/name}","comments_url":"https://api.github.com/repos/quintel/etmodel/issues/2099/comments","events_url":"https://api.github.com/repos/quintel/etmodel/issues/2099/events","html_url":"https://github.com/quintel/etmodel/issues/2099","id":151047175,"number":2099,"title":"NICE TO HAVE: users can edit scenario 'user values' for scenarios they own","user":{"login":"AlexanderWirtz","id":308563,"avatar_url":"https://avatars.githubusercontent.com/u/308563?v=3","gravatar_id":"","url":"https://api.github.com/users/AlexanderWirtz","html_url":"https://github.com/AlexanderWirtz","followers_url":"https://api.github.com/users/AlexanderWirtz/followers","following_url":"https://api.github.com/users/AlexanderWirtz/following{/other_user}","gists_url":"https://api.github.com/users/AlexanderWirtz/gists{/gist_id}","starred_url":"https://api.github.com/users/AlexanderWirtz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/AlexanderWirtz/subscriptions","organizations_url":"https://api.github.com/users/AlexanderWirtz/orgs","repos_url":"https://api.github.com/users/AlexanderWirtz/repos","events_url":"https://api.github.com/users/AlexanderWirtz/events{/privacy}","received_events_url":"https://api.github.com/users/AlexanderWirtz/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/quintel/etmodel/labels/Question","name":"Question","color":"006b75"}],"state":"open","locked":false,"assignee":{"login":"dennisschoenmakers","id":104830,"avatar_url":"https://avatars.githubusercontent.com/u/104830?v=3","gravatar_id":"","url":"https://api.github.com/users/dennisschoenmakers","html_url":"https://github.com/dennisschoenmakers","followers_url":"https://api.github.com/users/dennisschoenmakers/followers","following_url":"https://api.github.com/users/dennisschoenmakers/following{/other_user}","gists_url":"https://api.github.com/users/dennisschoenmakers/gists{/gist_id}","starred_url":"https://api.github.com/users/dennisschoenmakers/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dennisschoenmakers/subscriptions","organizations_url":"https://api.github.com/users/dennisschoenmakers/orgs","repos_url":"https://api.github.com/users/dennisschoenmakers/repos","events_url":"https://api.github.com/users/dennisschoenmakers/events{/privacy}","received_events_url":"https://api.github.com/users/dennisschoenmakers/received_events","type":"User","site_admin":false},"milestone":null,"comments":9,"created_at":"2016-04-26T05:51:02Z","updated_at":"2016-04-28T12:24:09Z","closed_at":null,"body":"Now that we are using regional scenario's to support clients from Gelderland, Groningen, Ameland and (hopefully soon) Goeree-Overflakkee, we are coming upon an unfortunate shortcoming of the way we store scenario settings. Scenario files are completely off-limits to our clients. It would be ideal if 'ETM literate' users could edit some of these themselves.\r\n\r\nSince these regional scenario's often involve quite a bit of scaling and tweaking before 'present' energy use accurately reproduce statistics, these scenario files contain a long 'pre-amble' of input statements. Since only Quintel staff can access these scenario files, only they can perform or amend such 'tweaking'. Several clients have already inquired if they can have access. For transparency's sake and because we claim to be 'completely' open source, I believe it is desirable to have the ability to give users access to scenario files they own. \r\n\r\nI suggest only giving access to `scenarios` and `scenario-scaling` tables and only particular fields or columns in those tables at that. I realize this is probably a nightmare to set up and to make sure stuff doesn't break, but I would appreciate it if we gave this issue some thought.\r\n\r\nnotifying @ChaelKruip @jorisberkhout @antw @grdw @RobTerwel  "},"comment":{"url":"https://api.github.com/repos/quintel/etmodel/issues/comments/215407517","html_url":"https://github.com/quintel/etmodel/issues/2099#issuecomment-215407517","issue_url":"https://api.github.com/repos/quintel/etmodel/issues/2099","id":215407517,"user":{"login":"antw","id":4383,"avatar_url":"https://avatars.githubusercontent.com/u/4383?v=3","gravatar_id":"","url":"https://api.github.com/users/antw","html_url":"https://github.com/antw","followers_url":"https://api.github.com/users/antw/followers","following_url":"https://api.github.com/users/antw/following{/other_user}","gists_url":"https://api.github.com/users/antw/gists{/gist_id}","starred_url":"https://api.github.com/users/antw/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/antw/subscriptions","organizations_url":"https://api.github.com/users/antw/orgs","repos_url":"https://api.github.com/users/antw/repos","events_url":"https://api.github.com/users/antw/events{/privacy}","received_events_url":"https://api.github.com/users/antw/received_events","type":"User","site_admin":false},"created_at":"2016-04-28T12:24:08Z","updated_at":"2016-04-28T12:24:08Z","body":"Does something prevent these inputs being represented as sliders? Showing them a sliders has many advantages:\r\n\r\n* The rest of the ETM uses them, so users will be familiar with how they work.\r\n* (Nearly) instant feedback to changes.\r\n* Little to no extra code. (!!!)\r\n\r\nShowing a list of inputs with raw keys and simple text fields is not a very user-friendly experience.\r\n\r\nTo prevent accidental modification of the \"present day\" sliders, we could require the user to read a message – and click a button.\r\n\r\n<img width=\"522\" alt=\"screen shot 2016-04-28 at 13 20 13\" src=\"https://cloud.githubusercontent.com/assets/4383/14885626/5381c9e6-0d44-11e6-9986-ee696ca07d68.png\">\r\n\r\n(click the button, we'll show the sliders, and remember not to show the message again)."}}