You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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"?
The text was updated successfully, but these errors were encountered:
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.
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"?
The text was updated successfully, but these errors were encountered: