Ticket #735 (closed task: fixed)
Investigate 'deduping' (ONS import)
Reported by: | dread | Owned by: | dread |
---|---|---|---|
Priority: | awaiting triage | Milestone: | |
Component: | ckan | Keywords: | |
Cc: | Repository: | ||
Theme: |
Description
ww 22/9/10:
(discussion of ticket:509) This leads us to deduping which should be the next order of business oin this thread...
ww 20/10/10:
if a dataset is missing a department and the ons script makes a new version of it with a department we now have two reccords for the same dataset. these should be manually merged - need a merge tool where you can tell it that two datasets are the same.
Change History
Note: See
TracTickets for help on using
tickets.
I have been through looking for package names with a trailing underscore checking if they should indeed be separate package from those without.
#872 and #873 cover creation of the duplicates in the first place.