From CKAN

Contents 1 Plan 1.1 Issues 2 Resource Page - http://trac.ckan.org/ticket/1445 3 Dataset Page 3.1 Resource Listing 3.2 Other stuff 3.3 Minor other stuff

Plan

• http://trac.ckan.org/ticket/1445 - resource page
• mockup first and then share
• then implement

refactor dataset page:

• http://trac.ckan.org/ticket/1449 - new resource listing (in dataset page)
• http://trac.ckan.org/ticket/1450 - create more info section and move stuff out (relayout page e.g. README, tags etc)
• http://trac.ckan.org/ticket/1451 - reintegrate download stats (move into core)
• http://trac.ckan.org/ticket/1370 - share this

Issues

• Resources not prominent enough on dataset page
• No page for resources (no way to direct link to them)
• Tension between Dataset and Resource (what is main item?)

Agreed: a dedicated page per resource Things we want:

• Better Resource listing (either separate page or in dataset page more prominently)
• Resource page
• Data Viewer

Resource Page - http://trac.ckan.org/ticket/1445

User stories:

• Come to resource page and want to know what and when (what is this (description + file type ...), when was it last updated etc)
• Want to see other resources related to this (e.g. in parent dataset)
• Want to explore the data directly if we can ...

Resource info:

• Actions: API, get cached version, ...
• Other metadata
• QA info
• Data Viewer

Page layout:

• Full width page
• Resource name at top
• What + when (suggest having following 2items in small under resource name)
  • Part of dataset: ....
  • Last updated: 1 year ago (unknown or absent if missing?)
  • Format: use stdicon (?) - http://www.stdicon.com/
  • Then description line ... (normal in main page)

• Quality information (?) - not for the present (maybe once QA system working)

• Description at the top
  • do we want to pull dataset description as well?
  • No if the resource has a description.
    • Discarded proposal: Resource description then below (blank line): From the [dataset](links to : [in italics ....]
  • Yes if no resource description. Use first 300-400 characters. Prefix with From the [dataset](link to dataset): ....

Actions:

• Get Data: download, api, [explore] ...
  • Located below tabs menu (if it were present) - above description
• Work within thedatahub: fork, watch etc
  • Located parallel with page_heading ...

Resource View - available actions:

• Download
  • Available if resource_type is file or file.upload
• Download Cached if ditto and resource.{...}
• API Endpoint if
  • type is API (link to API endpoint)
  • webstore_url is set (some work ...)
  • Help for API ...? (e.g. a help button bringing up instructions -- generally or just for webstore)

Data Explorer

• Inline images ...
• if cannot explore state this and explain why ... (wrong format)

What about data summary (e.g. col list and counts ...) - For the future!

Dataset Page

• Resource listing here
• Reduce or move Notes / Readme so resources are above fold
• From sidebar move everything but tags and home page (source) (? - maybe move home page too) out to More Info Tab.
  • What about license (keep some info about license on main page?)
    • Have image summary or similar on dataset and link through to more info
• Parallel with Edit

Resource Listing

• Name (description if no name) -> Hyperlink to resource page
  • [Raw Data] [Cached Data] [API] [View (duplication of link to resource page)]
  • Description snippet
  • Any other info?

Aside: enhance dataset listing with similar info

Other stuff

• Download stats (https://bitbucket.org/okfn/ckanext-googleanalytics)
• Social info: http://trac.ckan.org/ticket/1370
  • Share this - button
  • Pull references from the web ... e.g. all mentions of this url on twitter ...
• Issues [deferred]
  • Issues Tab
• Resource relationships [deferred]
  • Show derivations relationships between resources
• Activity [deferred]
• Apps and related stuff
• Image for dataset
• Restrictions on name (??)

Minor other stuff

• Dataset Not Open