Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add metadata flag for orgs/datasets that prevent UI edits #103

Open
patcon opened this issue Apr 20, 2016 · 1 comment
Open

Add metadata flag for orgs/datasets that prevent UI edits #103

patcon opened this issue Apr 20, 2016 · 1 comment

Comments

@patcon
Copy link

patcon commented Apr 20, 2016

I'm currently scraping the Toronto Data Catalogue into a JKAN instance, and would like to disable editing for those scraped datasets. not sure what the best frontmatter boolean flag would be... perhaps "imported" or more generally, "freeze" or "locked"?

@timwis
Copy link
Owner

timwis commented Apr 24, 2016

Hey @patcon, thanks for posting the issue. I wanted @JJediny's eyes on this too as he's written a plugin #83 to do something similar.

I'm trying to think about this in as generic a way as possible (to hopefully support even more use cases). Can we think of another use case that may want a feature like this? (So we can design with it in mind) Obviously no matter what the UI says, every dataset is editable on github.com.

The simplest solution would be, as you suggested, to use locked: true or editable: false in the dataset and just not show those buttons if that property is set. Just thinking that if we can come up with an additional use case it will make the choice a little more clear. If not, let's just do it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants