| | 1 | Discussion of resources referred to in package meta data (currently Download URL) |
| | 2 | |
| | 3 | On CKAN a Package just has metadata and doesn't store the resource (payload) (CKAN is just a registry). The CKAN metadata has a pointer, the download URL to find the associated resources. |
| | 4 | |
| | 5 | Two sorts of resource links: |
| | 6 | |
| | 7 | 1. Manifest |
| | 8 | A set of filenames with accompanying description.[[br]] |
| | 9 | e.g. [('!UkBirths1998.xls', '1998 data'), ('!UkBirths1999.xls', '1999 data')] |
| | 10 | |
| | 11 | 2. Distributions |
| | 12 | Each distribution is a serialisation / representation of the full Package - metadata + payload. (Or sometimes just the payload).[[br]] |
| | 13 | e.g. mysite.com/births.xls.zip which contains the two excel files[[br]] |
| | 14 | But it also includes cases where we have: |
| | 15 | * mysite.com/births.csv.zip |
| | 16 | * mysite.com/births/api (restful api to the same data) |
| | 17 | * mysite.com/births.html (WUI to the same data) |
| | 18 | |
| | 19 | Different representations of the same material - how do we deal with this? Options: |
| | 20 | 1. each distribution has its own CKAN package. |
| | 21 | 1. a CKAN package can refer to multiple distributions. |
| | 22 | |
| | 23 | package.distributions ? |
