[Dspace-general] creating web presentations using dspace content

[Don Gourley]

Thanks for the pointers to the DIDL plug-in and pluggable package
exporter proposal.  The concept of the structural metadata as a
manifest in a named bitstream is exactly what I'm thinking of,
but I don't think my viewer application wants to get a package
that contains the metadata with the content bitstreams.  It would
be simpler and more efficient to include URLs for the bitstreams
in the structural metadata so the viewer can create pages using
<img> tag that refers to the bitstream that represents the current
page.  Would that still be considered a DIP?

> Is the item likely to be small enough that packaging wouldn't insert
> too long a delay, or would you need to package fragments of the item?

In my case, an item might be 30 or 40 JPGs, each representing a
page of the document.  Only one page is needed at a time, and it
isn't really needed by the viewer app, but by the user's browser.
So it doesn't make sense to me to pass even fragments of content
through the viewer app.

-Don