From: S. C. <ste...@gm...> - 2008-10-29 16:55:16
|
We've seen pop up a few times in the last few releases. Someone wants NarrativeWeb to publish X, someone else things X shouldn't be there and instead wants Y. Unfortunately, everyone is correct. We all have our different reasons, and no-one is wrong. Problem is: how do we provide that? The case that comes up the most often, is what should be considered publishable by NarrativeWeb, and what should remain hidden. I know we already have a few options to restrict information on living people, and another toggle somewhere for publish/hide private records. In my opinion, adding other drop-down options would not be a great solution for 2 reasons: 1) the subtle differences between "restrict information on living people, option #1" and "restrict information on living people, option #2" becomes too obscure to be readily usable without having to refer back to documentation every time 2) someone will come along tomorrow and want not X, not Y, but Z instead, meaning we'll create an option #3, and so on... In my opinion: we need a way for users to pick which information can be included in NarrativeWeb, and/or other reports. Think of it as a way to dynamically configure a proxy db to tell it what to filter out, and what to leave in. (This is getting technical....this conversation is going to end up on dev.) Only then will all users be happy, since they can pick-and-choose which information to include/exclude. We now have a privacy-blocking proxy db. Extend that: we also need a privacy-blocking proxy db, with configurable blocking for living and likely-to-be-living people. This way, reports like NarrativeWeb just publish everything they can with all the data they've been given. If pictures are blocked, then NarrativeWeb doesn't even know about them. Stéphane Charette |