Skip to content
This repository has been archived by the owner on May 12, 2023. It is now read-only.

No editing of harvested datasets #323

Open
rossjones opened this issue Feb 15, 2017 · 3 comments
Open

No editing of harvested datasets #323

rossjones opened this issue Feb 15, 2017 · 3 comments
Milestone

Comments

@rossjones
Copy link
Contributor

If the is_harvested flag is set on a dataset, we shouldn't allow users to edit it. We should probably say why.

@rossjones rossjones added this to the Alpha milestone Feb 17, 2017
@gtdata
Copy link

gtdata commented Feb 21, 2017

@rossjones be good to see this in action - can you show me pls?

@rossjones
Copy link
Contributor Author

It's hard to differentiate them at the moment in Alpha. It's more that, if someone edits some text in a dataset that was harvested, the next time we harvest it may overwrite the change.

It could be that we need to fix harvesting in beta to identify that there has been a change to the dataset, and instead of just overwriting, find some way to merge the two different metadata.

@gtdata
Copy link

gtdata commented Mar 27, 2017

@rossjones ok, so we'll need to create an 'alert' explaining what the user is/isn't allowed to do, I'll look into it

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

No branches or pull requests

2 participants