[ckan-dev] How to display more information on a resource?

David Raznick kindly at gmail.com
Tue Jan 18 22:35:24 UTC 2011


On Tue, Jan 18, 2011 at 12:26 PM, Friedrich Lindenberg
<friedrich at pudo.org>wrote:

> Hi,
>
> On Mon, Jan 17, 2011 at 9:58 PM, David Raznick <kindly at gmail.com> wrote:
> > I have been looking at ticket 862 .  Technically it should not be too
> > difficult if we go down the same route as "package extras" and "group
> > extras" which have extra key value pairs.
> >
> > However,  I have no good idea how we can display this extra information.
>
> This aspect was semi-consciously left out of the ticket. I think that
> we're essentially showing the right amount of information on package
> resource tables at the moment and that additional cues should be
> non-textual, e.g:
>
> * A preview link should be a small spyglass in the last column
> * The http return code as stored by the archiver could be used to
> color the download link (e.g. gray out 4xx/5xx resources).
> * Alternative downloads would only be presented for resources which
> have become unavailable, marked "(from CKAN Cache)".
> * A human-readable version of format could be shown instead of the
> actual name if given (essentially: display "Tar-Gzipped Excel
> Spreadsheet" for
> "application/gz|application/tar|application/vnd.ms-excel")
>

These ideas are great, however they seemed to be aimed more at showing of
information related to ticket 891 (Resource download worker deamon).

There are other attributes that are needed to be stored and be made user
editable such as "alternative url" in ticket 826 (Resource extra fields).

The ideas also seem to relate to viewing the data and not editing it.  I was
more worried about the editing part.  I will go along with what I said with
David and hope for the best.


> Other resource extras (such as "when has this last been visited by the
> archiver" are somewhat irrelevant to the CKAN user and I think we
> should limit ourselves in bombarding people with that information.
>

I definitely agree here.


>
> - Friedrich
>

> >
> > Currently the resources are in a 3 column table, which has an add button
> and
> > the option to reorder.
> >
> >  * If we can add arbitrary new columns then the table will grow too wide
> and
> > look bad.
> >  * We could add a horizontal scrollbar, which would look ugly and obscure
> > the new fields.
> >  * We could change it to a "continuous form" instead of a table but that
> > would muck up reordering.
> >  * We could add a javascript popup of key value pairs (on hover or click
> of
> > a info icon) that would look good but will not gracefully degrade without
> > javascript.
> >
> > We also need a way to view the extra resource info in "view" mode, which
> is
> > currently just a table of 3 columns.
> >
> > Has anyone got a good ideas about how this should be done?
> >
> > Thanks
> >
> > David
> >
> > _______________________________________________
> > ckan-dev mailing list
> > ckan-dev at lists.okfn.org
> > http://lists.okfn.org/mailman/listinfo/ckan-dev
> >
> >
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20110118/2532d9ec/attachment-0001.html>


More information about the ckan-dev mailing list