Re: [Dspace-devel] OAI-ORE Harvesting & BITSTREAMS

paulo Tue, 17 May 2011 17:28:53 -0700


  Dear Mark

  my previous messages went with no text.

I have fixed the problems with displaying bitstreams in a collection harvested with OAI-ORE and using links to the bitstreams.

I commented a line in BistreamReader.java and I am sending a patch to the Reference theme to make it behave the same way it does for regular collections.


  I hope it helps.

  Paulo

  ----- Mensagem de [email protected] ---------
    Data: Tue, 17 May 2011 14:59:40 -0300
    De: [email protected]
Endereço para Resposta (Reply-To): [email protected]
Assunto: Re: [Dspace-devel] OAI-ORE Harvesting & BITSTREAMS
      Para: Mark Diggory <[email protected]>

Cc: [email protected], Scott Phillips <[email protected]>, "[email protected]" <[email protected]>

----- Mensagem de [email protected] ---------
     Data: Thu, 12 May 2011 14:55:08 -0700
     De: Mark Diggory <[email protected]>
Endereço para Resposta (Reply-To): Mark Diggory <[email protected]>
Assunto: Re: [Dspace-devel] OAI-ORE Harvesting & BITSTREAMS
       Para: [email protected]
       Cc: [email protected], Scott Phillips
<[email protected]>, "[email protected]"
<[email protected]>

Probably involved with the cocoon upgrades/patching we've been doing. The ORE is in a Bitstream in the Item right? "cocoon://" not working for resolving context centric resources was something I recall breaking and possibly the reason that cocoon "blocks" are broken in XMLUI, can you give context:// a try and see if that works?


From the cocoon docs...

Define parts inside of an aggregate. You can define as source of a   
  part a URL. The following list of examples summarizes some useful   
  part sources:

Use http://foo/bar[1] to merge in xml content via http protocol, received from machine foo.

Use context://servlet-context-path/foo/bar[2] to merge in xml   
content from the servlet context.

Use cocoon:/current-sitmap-pipeline/foo/bar to merge in xml content from the current sitemap. The appropriate pipeline is selected matching current-sitemap-pipeline. Use cocoon://root-sitmap-pipeline/foo/bar[3] to merge in xml content from the root sitemap. The appropriate pipeline is selected matching root-sitemap-pipeline.



Mark


On May 12, 2011, at 11:13 AM, [email protected] wrote:

Hi Scott

Thank you for your answer.

I understood your point and it really wouldn't make sense for me opening 24 new connections for any new browse collection page. I tested the same patch I did using "cocoon://" instead of "http://" and it really works in version 1.6.2 of dspace, as reported by James Russel, so I think this bug was probably introduced with changes made after 1.6.2 in the cocoon part of dspace-xmlui, specially the class BitstreamReader.java that was quite modified

I will probably be experimenting with OAI-ORE in version 1.6.2 but some one could take a look at this new bug in 1.7.1


Thanks a lot

Paulo Jobim

----- Mensagem de [email protected] ---------
    Data: Wed, 11 May 2011 10:57:30 -0500
    De: Scott Phillips <[email protected]>
Endereço para Resposta (Reply-To): [email protected]
Assunto: Re: [Dspace-devel] OAI-ORE Harvesting & BITSTREAMS

Para: "[email protected]" <[email protected]>

      Cc: [email protected]

This will require some more time to look at it. The problem with using
"http://"; is because it is treated as a completely separate web request by
cocoon which means that a new DSpace context as created an it ties up a
database connection. Cocoon does a little bit of magic The default install
of dspace set's the database pool size to 30, it's realistic to have a 100
or more items displayed on a page. That means it's conceivable you would
exhaust your database pool with one web request. I'm sure there's

some other

problem that needs to be tracked down, this might work as a short-term fix
for a small repository but I doubt it would be effective in the long run.

Scott--


2011/5/7 <[email protected]>

  Hi Scott and Alexey

I have made this patch to make OAI-ORE harvesting a collection with
external links to bitstreams display correctly in summarylists for
collections and communities.

It makes the Reference theme behave the same for local collections or
colletions harvested with links to bitstreams.

I changed the calls to the ORE.xml documents to use the prefix "http://";
instead of "cocoon://" because it was making XSL brake,

displaying just the

first document.

I would like if you could submit it after reviewing

Thanks

Paulo Jobim

I----- Mensagem de [email protected] ---------
     Data: Fri, 6 May 2011 19:52:39 +0000
     De: James Russell <[email protected]>
Endereço para Resposta (Reply-To): James Russell <[email protected]>
Assunto: RE: [Dspace-devel] OAI-ORE Harvesting & BITSTREAMS
       Para: "[email protected]" <[email protected]>,

"[email protected]"

<[email protected]>, "[email protected]" <
[email protected]>,

"[email protected]"

<[email protected]>



>
> We are doing precisely the same thing,
> and experiencing exactly the same results.
>
> I just discovered this in the process of migrating to 1.7.1.
> In my case, this method is known to work correctly in 1.6.2.
>
> James Russell
> OhioLINK
>
>
> From: [email protected] [mailto:[email protected]]
> Sent: Saturday, April 30, 2011 2:40 PM
> To: [email protected]; [email protected];
> [email protected]
> Subject: [Dspace-devel] OAI-ORE Harvesting & BITSTREAMS
>
>
> Dear Alex
>
> I am having difficulties displaying the thumbnails from a collection
> harvested with the OAI-ORE interface using only the links to
> bitstreams.
>
> Whenever I read the ORE.xml document with the links to bitstream,
> the whole XSL system gets lost, displaying only the first line of a
> summaryList.
>
> I have attached a patch to the Reference theme so you can reproduce
> the problem.
>
> I hope you can help me
>
> Paulo Jobim
>


----- Final da mensagem de [email protected] -----



----- Final da mensagem de [email protected] -----

------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay_______________________________________________[4]
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel[5]


----- Final da mensagem de [email protected] -----



Links:
------
[1] http://foo/bar
[2] context://servlet-context-path/foo/bar
[3] cocoon://root-sitmap-pipeline/foo/bar
[4]
http://p.sf.net/sfu/intel-dev2devmay_______________________________________________
[5] https://lists.sourceforge.net/lists/listinfo/dspace-devel


----- Final da mensagem de [email protected] -----



  Dear Mark

  my previous messages went with no text.