[ckan-dev] created resources in dataset - can't access the dataset

[Ian Ward]

Sorry, I should have said "package relationship" which is different
than the related items. It's something you'll have to dig into the
code to find out about, I don't think there is any documentation on
their use.

There are relationships_as_object and relationships_as_subject fields
in the package schema available through the API. The model itself is
in ckan/model/package_relationship.py


On Thu, Jan 30, 2014 at 3:53 PM, Aaron McGlinchy
<McGlinchyA at landcareresearch.co.nz> wrote:
> Is "related packages" different to "related items"?
>
> Related items seems to be open to any user to add to/delete... so maybe not as safe as storing within datasets which use the authorisation rules?  If is related items then I wonder if would be better to have the main dataset with the DOI as  an index which contained resources that were links (with description) to other datasets in CKAN which were the components, each of them containing a chunk of the resources.  Say you decide each sub dataset can managemebly contain 500 resources, each time you get to 500 you create a new dataset and start adding the new resources to it and at same time create an additional resource in the 'index' dataset that contains the link  to the new 'sub' dataset?
>
> If related packages is something again, is there a section in the documentation on it - sounds a useful feature.  I searched for related packages but didn't come back with anything obvious.
>
> Cheers
> Aaron
>
>>
>> Message: 3
>> Date: Thu, 30 Jan 2014 08:06:42 -0500
>> From: Ian Ward <ian at excess.org>
>> To: CKAN Development Discussions <ckan-dev at lists.okfn.org>
>> Subject: Re: [ckan-dev] created resources in dataset - can't access
>>         the dataset anymore?
>> Message-ID:
>>         <CAA3rUNdNAesQOXYLGQSVWeW_=
>> vLrA3fNvmepVOdK+CRC15pp-w at mail.gmail.com>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>> Hi Phil,
>>
>> Have you seen the related packages feature? You could have a dataset
>> with the DOI and no resources that is a parent to other datasets that
>> each have a smaller number of resources.
>>
>> You would have to create and update these datasets with the API and
>> IIUC just alter your templates to show the relationships.
>>
>> Ian
>>
>> On Thu, Jan 30, 2014 at 7:47 AM, Philip Cross
>> <phil.cross at bristol.ac.uk>
>> wrote:
>> > Hi Ian,
>> >
>> > Splitting data across datasets wouldn't be a good solution for us
>> > since
>> we
>> > assign each dataset a DOI, which is intended to resolve to the
>> > package
>> page
>> > on our CKAN instance.
>> >
>> > I should point out that the data is not being uploaded to the CKAN
>> server,
>> > we are harvesting the metadata and pointing from each resource back
>> > to
>> our
>> > own data storage. At the moment we are still pointing at the data
>> > via a
>> web
>> > interface that allows users to navigate down to the files they wish
>> > to download.
>> >
>> > An example is at:
>> > http://data.bris.ac.uk/datasets/13kidnrls4jnl1m806eyfd8h6z/
>> >
>> > Best wishes,
>> > Phil
>> >
>> >
>> >
>
> ________________________________
>
> Please consider the environment before printing this email
> Warning: This electronic message together with any attachments is confidential. If you receive it in error: (i) you must not read, use, disclose, copy or retain it; (ii) please contact the sender immediately by reply email and then delete the emails.
> The views expressed in this email may not be those of Landcare Research New Zealand Limited. http://www.landcareresearch.co.nz
> _______________________________________________
> 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