Are there any plans to allow for administrators to specify which users can edit a given topic?
Discussions on Creating and Publishing Personal Domains
Filtersonly show threads also posted in:
-
-
-
We've certainly discussed that capability - and use it special cases in the application, but making this a generalized permission feature is probably a ways out. What are you trying to do?
-
Just scheming, so to speak.
In general, transparency about the feature road map is a good thing, although I can understand the need to protect trade secrets. -
Agreed. We hope to have our internal bug (and feature) tracking system visible and editable externally in the next month or two which should provide more visibility. With respect to this particular feature, it hasn't really gotten past the discussion stage here -- we're more focused on the basic open data contribution cases at this stage.
-
-
-
Is it (or will it be) possible to publish a type for a limited set of users? For example, I may create a type that I don't want to publish for everyone to view but I would like to get input and use from users that I select.
-
We haven't tested this completely yet, but you should be able to add users as administrators to your domain and this would make the types and properties in that domain visible only to those users. We haven't exposed the UI yet to add/remove users from a domain, but if you'd like to try it out, post the domain and the usernames you'd like to add and we can give it a try.
-
Can you also allow type administrators to specify the privileges of other users for that type? For example, I would like to allow a select set of users to see and add topics for a type (without searching for them) but not modify the structure of the type.
-
We haven't gotten to that level of granularity yet with the permissions we've defined in the system. Generally anything in Freebase can be queried by someone who knows how to ask for it -- we do some things in the interface to hide 'unpublished' properties and types from other users, but this isn't a walled-off permissions system. If a user knows where to look and how to ask for data (through the API rather than the Freebase interface), they can always see the data in Freebase.
We are considering another role called domain expert that would give users access to edit the type and property descriptions for a domain, but not to edit the schema itself. These users would likely be given the ability to see unpublished types/properties within that domain. Does this seem like it might meet your needs? -
That would be helpful, but it would also be nice to eventually limit users who can use a type and edit topics. For example, I may have a list of experts who I want to assign a type. Those experts would then be the only ones allowed to use the type and contribute to topics but anyone could read the topics. In other words, the Domain administrator is given the power to assign specific users write privileges for types and topics within their domain(s), with the default being the status quo.
-
