From: MacKenzie Smith <kenzie@MIT.EDU> - 2004-01-20 15:08:59
So far this hasn't been a big issue for us at MIT (or many of the other
institutions I've spoken to) because they tend to get the deliverable
version from the author/submitter (e.g. faculty member) and if there is a
preservation format version at all it's been created by the repository as
part of the ingest process so *both* versions are kept in DSpace -- the
first because it's what was deposited and the second for long-term
But if *you* generate the deliverable version then it seems reasonable to
me to serve it out of a different system (especially when there are
different service requirements for deliverable and archival versions). For
example, we'll archive locally created learning objects in our DSpace, but
probably deliver them to students via a repository local to the course
management system and so they could well be in different formats. The trick
is to make sure the two versions are linked via metadata, especially from
the deliverable version back to the archival master.
At 04:43 PM 1/6/2004 +1100, Michele Huston wrote:
>At ANU we are looking at placing collections of images, audio and XML docs
>into DSpace. These files raise the issue of different formats for
>preservation and access.
>e.g. 1 Our images are in tiff format and we have generated jpeg
>derivatives (e.g. thumbnail and a larger web view) for display. Our
>thinking is that it would be better to store the derivatives in a
>structured files space elsewhere rather than bundled with the tiffs as
>they are not archive quality and we may want to regenerated them or serve
>them on the fly in the future. We have made some minor changes to the
>DSpace user interface to allow the thumbnails and the enlarged view to display.
>e.g. 2 Our audio files are in wav format and the access format we are
>using is real audio (streaming). Again our plan is to store the real audio
>files separate from the wav files. We don't want to archive the access
>formats as it is very likely that we will want to change this format in
>e.g. 3 In the case of the XML docs we'd like to allow the user to choose
>between HTML and PDF and to generate these derivatives on the fly.
>We were wondering if anyone else has been exploring the issue of
>separation of the preservation and display functions in DSpace.
>Digital Resource Services
>The Australian National University
>Ph 02 6125 6659
>Dspace-general mailing list
Associate Director for Technology
77 Massachusetts Avenue
Cambridge, MA 02139