-
Notifications
You must be signed in to change notification settings - Fork 9
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
Esmeraldas double data #226
Comments
@arshores I see what you are saying. There seem to be 10 duplicates. I can't see an obvious/consistent reason why the old (2017) versions of those data were not removed--because some appeared on my "delete these layers" list and others did not. I have a feeling it has to do with a mismatch between the actual FILENAMES from the old to the new. @kalxas If I provide the "Title" of these 10 (not the filename) would you be able to find the ones uploaded in 2017 and remove them? Or I could possibly do this manually, if that's preferred. |
I can remove those old layers if I have the file names, no problem |
@kalxas Is it OK if I delete them myself from the back-end, like this? |
sure, go ahead :) |
I did this one layer to test that delete is still working |
also, try not deleting them all at once, some times the admin panel times out if you try to delete many layers at once |
@kalxas I just deleted 11 duplicate layers for Esmeraldas. They are still showing up in the Layers list--will it take some time for this to refresh? I cleared my cache. |
Elastic Search index was rebuilt. |
I am noticing that there seems to be some overlap with the Esmeraldas data. I see for example that there are two layers for community organizations. I believe that all of Esmeraldas data was suppose to be deleted that was previously on the GeoNode and then the new data was to be uploaded. Can someone check what the problem is with this?
The text was updated successfully, but these errors were encountered: