Open kvuppala opened 7 years ago
Is there a reason for suggesting this change? Would this change mean that I and others that have Admin/Editor roles will no longer be able to manage our own datasets? Perhaps you can provide clarification on what you are proposing to change.
Thank you, Cindy
@cinnyasm the change suggested is only for catalog.data.gov which is the public facing site, there will not be any change to inventory.data.gov which is where metadata is being managed by agencies.
Thank you for the clarification and quick response. I thought you were referring to the data we manage.
Regards
On Wed, Oct 5, 2016 at 1:55 PM, Kishore K. Vuppala <notifications@github.com
wrote:
@cinnyasm https://github.com/cinnyasm the change suggested is only for catalog.data.gov which is the public facing site, there will not be any change to inventory.data.gov which is where metadata is being managed by agencies.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/GSA/data.gov/issues/749#issuecomment-251765885, or mute the thread https://github.com/notifications/unsubscribe-auth/AKwLjF5zYV6L3WINGHPxG-tgKYE0BgB7ks5qw_KQgaJpZM4KPGXv .
Cindy A. Smith IT Specialist GSA IT Digital Services Division (IG) (816) 823-5291 cindya.smith@gsa.gov
@kvuppala is this complete? Can we close?
@hkdctol Not implemented currently.
users with organization admin/editor role should not be able to create/modify datasets, the preferred approach is through data.json harvesting or csw harvest endpoint.
feature can still be available to CKAN sysadmin role for any exceptions.