[Dspace-devel] FW: DSpace

0 views
Skip to first unread message

Tansley, Robert

unread,
Aug 18, 2015, 3:42:16 PM8/18/15
to dspace...@lists.sourceforge.net, c...@cs.waikato.ac.nz
Hi all,
 
Chi-Yu Huang is from the University of Waikato in New Zealand has raised an important issue with the batch item importer/exporter, specifically to do with primary bitstreams.  An additional complication occurs when there are multiple bundles (in addition to ORIGINAL, THUMBNAIL and TEXT).
 
Has anyone looked at adding support for primary bitstreams into the batch item importer/exporter?  Is anyone interested in doing that?
 
Please the the posts below for more details.
 
Thanks all
 

 Robert Tansley / Digital Media Systems Programme / HP Labs
  http://www.hpl.hp.com/personal/Robert_Tansley/


From: Chi-Yu Huang [mailto:c...@cs.waikato.ac.nz]
Sent: 17 November 2004 14:43
To: Tansley, Robert
Subject: Re: DSpace

Hi Rob,

Thanks for the reply. Your help is always appreciated. It would be great if you can forward this message to dspace-devel group list. In the meantime, I will search around myself to see if any of these issues have been raised before. Also, we will keep looking on any better solutions.

Cheers,

Chi


Tansley, Robert wrote:
Hi Chi,
 
(Sorry for the late reply, travelling at the moment)
 
The example you site isn't one that DSpace handles very elegantly at the moment.  The original intention was that each of the 'data items' you mention below would be a separate Bundle in one the item.  The user interface for making this happen isn't there yet, unfortunately.  But the intention is that the bundles would look like this:
  • Item XXX
    • Bundle ORIGINAL -- contains the originals (probably the Word document in this case)
    • Bundle OTHER -- the HTML + images + stylesheets etc.  Each Bundle can have it's own primary bitstream.
    • Bundle OTHER -- the PDF document
    • Bundle OTHER -- The image file
    • Bundle THUMBNAIL -- the thumbnails of everything (primary bitstream not needed here)
    • Bundle TEXT -- extracted full-text, primary bitstream not needed
But, as you've probably noticed, neither the user interface nor the batch import/export tools support this yet!!!  I'd suggest e-mailing the dspace-devel group with this problem, as someone else may have thought about this already and even created a solution.  (With your permission, I'll forward this message to the list?)
 
For the short term, my suggestion would be to update the batch import/export format (making it backwards-compatible of course!) so that there can be >1 'contents' file -- 1 contents file for each Bundle.  Then each Bundle can have its own primary bitstream.
 
In the medium term, I'm hoping that the METS format will take over from the old import/export format.
 
In the long term, for DSpace 2.0, we need much better handling of complex objects like the one you describe below!
 
I hope this helps,
 
Rob


From: Chi-Yu Huang [mailto:c...@cs.waikato.ac.nz]
Sent: 10 November 2004 21:13
To: Tansley, Robert
Cc: David Bainbridge
Subject: Re: DSpace

Hi Rob,

I tried the following example in DSpace.

In one data item, I set up:
  • 1 Web html document +associated files and sytlesheet
  • 1 word document
  • 1 pdf document
  • 1 individual image file
I would like html, word, pdf and an individual image to be displayed but not the associated files from the html.  It seems that we need more than one primary bitstream. Have you thought of the case like this?  We were thinking to change the interface so that the user can select more than one primary bitstream. What do you think? Would this have any implications for the rest of the system? 

Secondly, regarding identifying the primary bitstream(s) from the contents file, we thought perhaps we can replace "bundle:ORIGINAL" with "bundle:PRIMARY" for the primary bitstream(s). What do you think about this? :-[

It is not sufficient to put the primary bitstream first in the contents file because there may not be one or there may be more than one (if you like our first idea).

We will try to implement both ideas if you think they are ok.  Any suggestions regarding where to start would be welcome.


Cheers,
Chi
:-)

Tansley, Robert wrote:
Hi Chi,
 
Yes, you have found one of the flaws in the exporter!  So I'm sorry, the only way to fix this is to go and change the code.
 
For example, you could make sure that the exporter puts the primary bitstream first in the contents file.  Or, you could make the exporter write another file, 'primary-bitstream', and in that file would be the filename of the primary bitstream.
 
If you do this, you can contribute the code back to DSpace (we are open source!), and then you wouldn't be working with your own customised DSpace any more, as all DSpaces would have this feature!
 
Does this help?  I know it's not ideal.
 
Rob


William Reilly

unread,
Aug 18, 2015, 3:42:24 PM8/18/15
to Tansley, Robert, <chi@cs.waikato.ac.nz>, dspace-devel, Rob Wolfe
I'll respond to say that this work is of keen interest to the CWSpace
project
(http://cwspace.mit.edu = archiving MIT's OpenCourseWare (OCW) in
DSpace)

Thank you for bringing it up and sending the e-mail to the list.

We expect to be addressing very similar issues as we contend not only
with OCW's course websites but also with the compound document
"learning objects" found therein.

We would be very interested to hear of anyone else with requirements
like these, or with willingness to work on code (!) for batch importer
modification and for the (eventual) METS importer work.

Just as a note: we are also looking at the IMS-CP content package
standard, with a transform to METS as part of the work ahead.
Finally, 'profile' specifications for both METS and IMS-CP are part of
the metadata work necessary to make automation of this feasible.

So, just an e-mail to express interest. Developer staff on CWSpace is
about a month away at this point.

Best,
William

William Reilly
wre...@mit.edu
Technical Analyst, Digital Library Research Group
MIT Libraries
http://cwspace.mit.edu

On Nov 19, 2004, at 2:18 PM, Tansley, Robert wrote:

> Hi all,
>  
> Chi-Yu Huang is from the University of Waikato in New Zealand has
> raised an important issue with the batch item importer/exporter,
> specifically to do with primary bitstreams.  An additional
> complication occurs when there are multiple bundles (in addition to
> ORIGINAL, THUMBNAIL and TEXT).
>  
> Has anyone looked at adding support for primary bitstreams into the
> batch item importer/exporter?  Is anyone interested in doing that?
>  
> Please the the posts below for more details.
>  
> Thanks all
>  
>
>  Robert Tansley / Digital Media Systems Programme / HP Labs
>   http://www.hpl.hp.com/personal/Robert_Tansley/

Jignesh Vishapara

unread,
Aug 19, 2015, 4:00:02 PM8/19/15
to dspace...@lists.sourceforge.net
i config file but i can not save so kinly guide me how to config dspace.cfg file




Reply all
Reply to author
Forward
0 new messages