[dspace-tech] Re: Problem with importing metadata in DSpace v3.2

[safa burak gurleyen]

I got the same error. I can't fix the problem. Will you? Or anyone can help 
please. I export metadata from Dspace. Changed it in CSV format. When I 
want to import CSV like Lukasz explain i got "New items must have a 
'collection' assigned in the form of a handle" error. 

Does anyone knows why this happens?

22 Eylül 2015 Salı 19:45:44 UTC+3 tarihinde Łukasz Staszak yazdı:
>
> Hi I have a problem with importing metadata in DSpace v3.2 (/ jspui / 
> DSpace-admin / metadataimport). When you import data for the new position I 
> get the error "New items must have a 'collection' assigned in the form of a 
> handle". In a CSV file I labeled ‘id’ column "+" but in the other column 
> ‘collection’ ("10593/1774" or collection_id from the database) whatever I 
> add - fails. My question is how to specify a column ‘collection’ in the CSV 
> to make the importation of new positions successful. 
>
>
> Here is an excerpt of my CSV file:
>
>
> id,collection,dc.title,dc.contributor,dc.date.issued,...
> "+","10593/1774||10593/19","test","test","2010",...
>
>
> Thank you very much for your help.
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] configure browse index -

[Monika Mevenkamp]

I would like to configure the author browse index to include 

dc.contributor,
dc.contributor.author,
dc.creator:text

but according to the documentation I need to either specify ‘*’ or a proper 
qualifier 

the reason I do not use dc.contributor.* is that we have  
dc.contributor.advisor field, 
that goes into our advisor index but should not be part of the author index

is there a way to this in version 5 ? 


Monika 

-
Monika Mevenkamp
Digital Repository Infrastructure Developer
Princeton University
Phone: 609-258-4161
Skype: mo-meven



-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Hide metadata OAI

[christian criollo]

Thank you very much for the help

El miércoles, 20 de abril de 2016, 9:19:28 (UTC-5), Claudia Jürgen escribió:
>
> Hi Christian,
> you can adjuste the crosswalks for the metadata formats you use:
>
> https://github.com/DSpace/DSpace/tree/master/dspace/config/crosswalks/oai/metadataFormats
> Which format you use in which context is defined in:
>
> https://github.com/DSpace/DSpace/blob/master/dspace/config/crosswalks/oai/xoai.xml
> Each context got a list of formats 
> The matching for dc.type.* for the format oai_dc is done here:
>
> https://github.com/DSpace/DSpace/blob/master/dspace/config/crosswalks/oai/metadataFormats/oai_dc.xsl#L78
>
> Hope this helps
>
> Claudia Jürgen
>
>
>
>
> Am 20.04.2016 um 16:11 schrieb christian criollo:
>
> Good morning
>
>
> I want to konow if is possible hide metadata in  OAI , for example hide the 
> metadata dc.type.spa and not showed to the harvesters for indexing thanks 
> for the help 
>
>
>
> -- 
> Claudia Juergen
> Eldorado
>
> Technische Universität Dortmund
> Universitätsbibliothek
> Vogelpothsweg 76
> 44227 Dortmund
>
> Tel.: +49 231-755 40 43
> Fax: +49 231-755 40 32claudia...@tu-dortmund.de 
> www.ub.tu-dortmund.de
>
>
>
>
> *Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie 
> ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für 
> diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender 
> und vernichten Sie diese Mail. Vielen Dank. Unbeschadet der Korrespondenz 
> per E-Mail, sind unsere Erklärungen ausschließlich final rechtsverbindlich, 
> wenn sie in herkömmlicher Schriftform (mit eigenhändiger Unterschrift) oder 
> durch Übermittlung eines solchen Schriftstücks per Telefax erfolgen. 
> Important note: The information included in this e-mail is confidential. It 
> is solely intended for the recipient. If you are not the intended recipient 
> of this e-mail please contact the sender and delete this message. Thank 
> you. Without prejudice of e-mail correspondence, our statements are only 
> legally binding when they are made in the conventional written form (with 
> personal signature) or when such documents are sent by fax. * 
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Re: DSpace 5.5 oai deriver "No matches for the query"

[Sönmez ÇELİK]

Hi Rafea,

Thank you for your interest.

I have found OAI-PMH driver listing problem. Problem reason is the missing
codding in driverAccessCondition. In xoai.xml
(/dspace/config/crosswalks/oai) file, line 376 has only ** tag.
Instead of that I replaced this line with * *tag. After
this change I restarted tomcat and used oai clean-cache commands.

sudo  /etc/init.d/tomcat7 restart
sudo /dspace/bin/dspace oai clean-cache

xoai.xml driverAccessCondition tagging should be like:




org.dspace.xoai.filter.DSpaceAtLeastOneMetadataFilter

dc.rights
contains
**
open access
openAccess






Sonmez CELIK
Director
Dogus University Library
http://sonmezcelik.blogspot.com
http://kutuphane.dogus.edu.tr/
http://journal.dogus.edu.tr/
4447997 / 1402
0555 4729975

2016-04-21 14:36 GMT+03:00 Rafa Carreres :

> Hi,
>
> I had a similar problem until I found that I was using not dc.rights but
> dc.rights.accessRights.
>
> So, I modified xoai.xml replacing the metadata field and after reindexing
> the oai solr  everything worked.
>
> The same happened for openaire context. I was using the wrong metatada
> field in the configuration.
>
> Hope this helps
>
> On Tuesday, April 19, 2016 at 12:48:14 PM UTC+2, Sönmez ÇELİK wrote:
>>
>> Hello,
>>
>> DSpace 5.5 OAI-PMH deriver listing is not working?
>> I have tried Claudia suggestion below. Not the solution.
>> What is the problem?
>> Could you help?
>>
>> Sonmez CELIK
>>
>> Sonmez CELIK
>> Director
>> Dogus University Library
>> http://sonmezcelik.blogspot.com
>> http://kutuphane.dogus.edu.tr/
>> http://journal.dogus.edu.tr/
>> 4447997 / 1402
>> 0555 4729975
>>
>> Sonmez CELIK
>> Director
>> Dogus University Library
>> http://sonmezcelik.blogspot.com
>> http://kutuphane.dogus.edu.tr/
>> http://journal.dogus.edu.tr/
>> 4447997 / 1402
>> 0555 4729975
>>
>> -- Forwarded message --
>> From: Claudia Jürgen 
>> Date: 2016-04-19 12:04 GMT+03:00
>> Subject: Re: [dspace-community] DSpace 5.5 oai deriver "No matches for
>> the query"
>> To: dspace-c...@googlegroups.com
>>
>>
>> Hello Sömmez,
>>
>> this type of question is better posted to dspace-tech rather than
>> dspace-community.
>>
>> It seems as non of your records matches the driver filter in
>>
>> https://github.com/DSpace/DSpace/blob/dspace-5.5/dspace/config/crosswalks/oai/xoai.xml
>> The Filte is here:
>>
>> https://github.com/DSpace/DSpace/blob/dspace-5.5/dspace/config/crosswalks/oai/xoai.xml#L191
>> Check the conditions in the Filter.
>>
>> Hope this helps
>>
>> Claudia Jürgen
>>
>>
>> Am 19.04.2016 um 10:46 schrieb Sönmez ÇELİK:
>>
>>> Hi,
>>>
>>> I'm trying to list driver records on DSpace 5.5. OAI-PMH interface.
>>> Request
>>> and openaire options are listing but deriver is not. Driver options is
>>> showing  "*No matches for the query*".
>>>
>>> Nomaly our DSpace 4.1 (http://openaccess.dogus.edu.tr/) OAI-PMH
>>> interface
>>> request, driver and openaire options are listing oai data.
>>>
>>> Why DSpace 5.5 OAI-PMH deriver otions not listing? Is there any idea?
>>>
>>> Sonmez CELIK
>>> Director
>>> Dogus University Library
>>> http://sonmezcelik.blogspot.com
>>> http://kutuphane.dogus.edu.tr/
>>> http://journal.dogus.edu.tr/
>>> 4447997 / 1402
>>> 0555 4729975
>>>
>>>
>> --
>> Claudia Juergen
>> Eldorado
>>
>> Technische Universität Dortmund
>> Universitätsbibliothek
>> Vogelpothsweg 76
>> 44227 Dortmund
>>
>> Tel.: +49 231-755 40 43
>> Fax: +49 231-755 40 32
>> claudia...@tu-dortmund.de
>> www.ub.tu-dortmund.de
>>
>> Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie
>> ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für
>> diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender
>> und vernichten Sie diese Mail. Vielen Dank.
>> Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen
>> ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher
>> Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines
>> solchen Schriftstücks per Telefax erfolgen.
>>
>> Important note: The information included in this e-mail is confidential.
>> It is solely intended for the recipient. If you are not the intended
>> recipient of this e-mail please contact the sender and delete this message.
>> Thank you. Without prejudice of e-mail correspondence, our statements are
>> only legally binding when they are made in the conventional written form
>> (with personal signature) or when such documents are sent by fax.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "DSpace Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to dspace-communi...@googlegroups.com.
>> To post to this group, send email to dspace-c...@googlegroups.com.
>> Visit this group at 

[dspace-tech] Re: DSpace 5.5 oai deriver "No matches for the query"

[Rafa Carreres]

Hi,

I had a similar problem until I found that I was using not dc.rights but 
dc.rights.accessRights.

So, I modified xoai.xml replacing the metadata field and after reindexing 
the oai solr  everything worked.

The same happened for openaire context. I was using the wrong metatada 
field in the configuration.

Hope this helps

On Tuesday, April 19, 2016 at 12:48:14 PM UTC+2, Sönmez ÇELİK wrote:
>
> Hello,
>
> DSpace 5.5 OAI-PMH deriver listing is not working?
> I have tried Claudia suggestion below. Not the solution.
> What is the problem?
> Could you help?
>
> Sonmez CELIK
>
> Sonmez CELIK
> Director
> Dogus University Library
> http://sonmezcelik.blogspot.com
> http://kutuphane.dogus.edu.tr/
> http://journal.dogus.edu.tr/
> 4447997 / 1402
> 0555 4729975
>
> Sonmez CELIK
> Director
> Dogus University Library
> http://sonmezcelik.blogspot.com
> http://kutuphane.dogus.edu.tr/
> http://journal.dogus.edu.tr/
> 4447997 / 1402
> 0555 4729975
>
> -- Forwarded message --
> From: Claudia Jürgen 
> Date: 2016-04-19 12:04 GMT+03:00
> Subject: Re: [dspace-community] DSpace 5.5 oai deriver "No matches for the 
> query"
> To: dspace-c...@googlegroups.com 
>
>
> Hello Sömmez,
>
> this type of question is better posted to dspace-tech rather than
> dspace-community.
>
> It seems as non of your records matches the driver filter in
>
> https://github.com/DSpace/DSpace/blob/dspace-5.5/dspace/config/crosswalks/oai/xoai.xml
> The Filte is here:
>
> https://github.com/DSpace/DSpace/blob/dspace-5.5/dspace/config/crosswalks/oai/xoai.xml#L191
> Check the conditions in the Filter.
>
> Hope this helps
>
> Claudia Jürgen
>
>
> Am 19.04.2016 um 10:46 schrieb Sönmez ÇELİK:
>
>> Hi,
>>
>> I'm trying to list driver records on DSpace 5.5. OAI-PMH interface. 
>> Request
>> and openaire options are listing but deriver is not. Driver options is
>> showing  "*No matches for the query*".
>>
>> Nomaly our DSpace 4.1 (http://openaccess.dogus.edu.tr/) OAI-PMH interface
>> request, driver and openaire options are listing oai data.
>>
>> Why DSpace 5.5 OAI-PMH deriver otions not listing? Is there any idea?
>>
>> Sonmez CELIK
>> Director
>> Dogus University Library
>> http://sonmezcelik.blogspot.com
>> http://kutuphane.dogus.edu.tr/
>> http://journal.dogus.edu.tr/
>> 4447997 / 1402
>> 0555 4729975
>>
>>
> --
> Claudia Juergen
> Eldorado
>
> Technische Universität Dortmund
> Universitätsbibliothek
> Vogelpothsweg 76
> 44227 Dortmund
>
> Tel.: +49 231-755 40 43
> Fax: +49 231-755 40 32
> claudia...@tu-dortmund.de 
> www.ub.tu-dortmund.de
>
> Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie 
> ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für 
> diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender 
> und vernichten Sie diese Mail. Vielen Dank.
> Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen 
> ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher 
> Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines 
> solchen Schriftstücks per Telefax erfolgen.
>
> Important note: The information included in this e-mail is confidential. 
> It is solely intended for the recipient. If you are not the intended 
> recipient of this e-mail please contact the sender and delete this message. 
> Thank you. Without prejudice of e-mail correspondence, our statements are 
> only legally binding when they are made in the conventional written form 
> (with personal signature) or when such documents are sent by fax.
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "DSpace Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to dspace-communi...@googlegroups.com .
> To post to this group, send email to dspace-c...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/dspace-community.
> For more options, visit https://groups.google.com/d/optout.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Exclude values in facets

[Rafa Carreres]

H Andrea,

After further investigation, I've found that the filter is being 
applied...but not for the home page.

In other words, I have this configuration in discovery.xml:



   




-dc.contributor.author:"Radio Alcoy"
-dc.contributor.author:"Radio París"



.

 



dc.contributor.author
dc.creator





.

After reindexing, all the references to "Radio Alcoy" or "Radio París" in 
the author facet in communities or collections home page are gone, but the 
author facet in the home page still shows this references.

Having a look at solr.log shows that the default filter query is being 
aplied, indeed:

2016-04-20 18:54:56,985 INFO  org.apache.solr.core.SolrCore @ [search] 
webapp=/solr path=/select 
params={q=*:*=dateIssued.year,handle,search.resourcetype,search.resourceid=0=NOT(withdrawn:true)=NOT(discoverable:false)=
*-dc.contributor.author:"Radio+Alcoy"=-dc.contributor.author:"Radio+París"*=location:m335=dateIssued.year:[*+TO+*]=read:(g0+OR+g0)=dateIssued.year_sort+asc=1=javabin=2}
 
hits=1022 status=0 QTime=81
2016-04-20 18:54:57,003 INFO  org.apache.solr.core.SolrCore @ [search] 
webapp=/solr path=/select 
params={q=*:*=dateIssued.year,handle,search.resourcetype,search.resourceid=0=NOT(withdrawn:true)=NOT(discoverable:false)=-dc.contributor.author:"Radio+Alcoy"=-dc.contributor.author:"Radio+París"=location:m335=location:m335=dateIssued.year:[*+TO+*]=read:(g0+OR+g0)=dateIssued.year_sort+desc=1=javabin=2}
 
hits=1022 status=0 QTime=8

So, why is still "Radio Alcoy" and "Radio París" appearing in the author 
home page facet but not in others?

Regards.

On Monday, April 18, 2016 at 1:42:52 PM UTC+2, Andrea Bollini wrote:
>
> Hi Rafa,
> it is strange that the filter doesn't work, if you share the relevant part 
> of your spring configuration and your solr logs we can try to understand. 
> Anyway, note that using the filter will esclude the Van de Velde authored 
> items from the result and not only his name from the author facets.
>
> I discourage you to attempt to remove the name from the facet list after 
> the search, it is complex as it also affect pagination of facets result. 
> IMHO it is better to avoid indexing of the value at all.
>
> Place to look to prevent indexing
>
> https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/java/org/dspace/discovery/SolrServiceImpl.java#L1088
> try something like 
> if ("Van de Velde, Kevin".equalsIgnoreCase(value)) continue;
> obviously you need to make the code more general and configurable, maybe 
> you want to check also which facet is indexing.
>
> The above solution is a very clumsy patch... an elegant solution, as the 
> one adopted in DSpace-CRIS, requires the ability to index virtual metadata 
> that can be external defined (filtering existent one as in your use case)
>
> I don't know where in the code is controlled the resultset sent to 
> static-sidebar-facet.jsp. 
>
>
> https://github.com/DSpace/DSpace/blob/master/dspace-jspui/src/main/java/org/dspace/app/webui/discovery/DiscoverySearchRequestProcessor.java#L166
>
> but as you can see following the code the mapping between the SOLR 
> response and the java object used by the view is done at a very low level 
> in the DSpace API.
>
> Hope this help,
> Andrea
>
>
> Il 18/04/2016 11:24, Rafa Carreres ha scritto:
>
> Hi Andrea,
>
> Thank you for your help. 
>
> According to this, filtering with -dc.contributor.author:"Van de Velde, 
> Kevin" should show all the authors but that one, but unfortunately it 
> doesn't work. Oddly, the same query in SOLR web interface works perfectly, 
> excluding those items including that particular author.
>
> Checking out solr.log shows that the filter is being applied but with no 
> effect.
>
>
> Another approach I'm currently is to modify the code in 
> static-sidebar-facet.jsp to exclude those authors I don't want to be showed 
> in the facet.
> It works, but, instead of 5 authors (I have limit=5), for example, it 
> shows 4, as "Van de Velde, Kevin" has been excluded.
>
> I don't know where in the code is controlled the resultset sent to 
> static-sidebar-facet.jsp. 
>
> Any clue about this point? 
>
> Regards,
>
>
>
>
> On Thursday, April 14, 2016 at 3:02:31 PM UTC+2, Andrea Bollini wrote: 
>>
>> Hi Rafa,
>> the defaultFilterQueries parameter allows you to limit the result set. 
>> The facet are automatically build upon the result. This mean that in your 
>> case you will have in the author facet only Van de Velde, Kevin and his 
>> coauthors. Also if you write the opposite query, i.e.
>> -dc.contributor.autor:"Van de Velde, Kevin"
>> I guess that the result will be not what you expect. No items where Van 
>> de Velde appears as author will be retrieved, so it will be not included in 
>> the author facet but I guess that this is more restrictive 

[dspace-tech] OAI Harvesting for DSpace CRIS

[Oliver Goldschmidt]

 Hello all,

I wonder if its possible to use a collection as a target for OAI Harvesting 
in DSpace Cris 5.5.0. I know, that the basic function in DSpace is needing 
XMLUI (although I wonder why this is something UI specific as the options 
to use a collection as a target for OAI Harvesting are available in JSPUI 
as well; but its not working there), but is there any chance to use it also 
in DSpace CRIS?

Thanks,
Oliver

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Why are'nt people responding to my query..

[Tafadzwa Shelton Sigudu]

2016-04-20 19:38:07,197 ERROR org.dspace.submit.step.CompleteStep @ Caught 
exception in submission step: 
java.lang.NullPointerException
at 
javax.mail.internet.InternetAddress.parse(InternetAddress.java:595)
at 
javax.mail.internet.InternetAddress.parse(InternetAddress.java:555)
at 
javax.mail.internet.InternetAddress.(InternetAddress.java:91)
at org.dspace.core.Email.send(Email.java:271)
at 
org.dspace.workflow.WorkflowManager.notifyOfArchive(WorkflowManager.java:771)
at 
org.dspace.workflow.WorkflowManager.doState(WorkflowManager.java:659)
at 
org.dspace.workflow.WorkflowManager.advance(WorkflowManager.java:416)
at 
org.dspace.workflow.WorkflowManager.doState(WorkflowManager.java:634)
at 
org.dspace.workflow.WorkflowManager.advance(WorkflowManager.java:407)
at 
org.dspace.workflow.WorkflowManager.doState(WorkflowManager.java:597)
at 
org.dspace.workflow.WorkflowManager.advance(WorkflowManager.java:395)
at 
org.dspace.workflow.WorkflowManager.doState(WorkflowManager.java:556)
at 
org.dspace.workflow.WorkflowManager.advance(WorkflowManager.java:383)
at 
org.dspace.workflow.WorkflowManager.advance(WorkflowManager.java:336)
at 
org.dspace.workflow.WorkflowManager.start(WorkflowManager.java:179)
at 
org.dspace.submit.step.CompleteStep.doProcessing(CompleteStep.java:96)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:155)
at 
org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:243)
at 
org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:3237)
at 
org.mozilla.javascript.Interpreter.interpret(Interpreter.java:2394)
at 
org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:162)
at 
org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:393)
at 
org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2834)
at 
org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:160)
at org.mozilla.javascript.Context.call(Context.java:538)
at 
org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1833)
at 
org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1803)
at 
org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter.handleContinuation(FOM_JavaScriptInterpreter.java:698)
at 
org.apache.cocoon.components.treeprocessor.sitemap.CallFunctionNode.invoke(CallFunctionNode.java:94)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55)
at 
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
at 
org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(SelectNode.java:82)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:81)
at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:239)
at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.buildPipeline(ConcreteTreeProcessor.java:186)
at 
org.apache.cocoon.components.treeprocessor.TreeProcessor.buildPipeline(TreeProcessor.java:260)
at 
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:107)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
at 
org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(SelectNode.java:87)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55)
at 
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
at