[ckan-dev] Loss of dataset metadata on db migration
David Read
david.read at hackneyworkshop.com
Fri Dec 8 17:21:07 UTC 2017
Mike,
I can't think why you'd suffer any problems if you've successfully
restored the db, even if you have a newer CKAN or postgres version
(although if you upgraded CKAN then you need to do 'paster db
upgrade'). Was there an error during restoring the db, which meant
something was lost? Can you use psql to check the package table looks
the same on both servers, for the dataset name in question? I don't
see why the ones uploaded via API would be any different to those in
the form.
David
On 8 December 2017 at 09:25, Mike Sinclair <mm.sinclair08 at gmail.com> wrote:
> On closer inspection, the datasets that were uploaded through the web
> interface still have their metadata. However, the ones that were uploaded
> via the API no longer have that metadata.
>
> On Fri, Dec 8, 2017 at 1:15 AM, Mike Sinclair <mm.sinclair08 at gmail.com>
> wrote:
>>
>> Hi all,
>>
>> I migrated my ckan instance from one server to another. I dumped the
>> database and rsynced all of the resources.
>>
>> The datasets look good, however they are missing the metadata under
>> 'additional information." They still have their licence, organization,
>> groups and tags, but they have lost maintainer, extras, author, etc.
>>
>> Any ideas?
>>
>> Mike
>
>
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
>
More information about the ckan-dev
mailing list