[dspace-tech] Can't view/download files

[Javier Távara]

Hi.
I'm having some weird problem.

First my DSpace 5.5 instance started to go offline because a PostgreSQL 9.5 
problem:

2018-05-15 18:23:12,885 ERROR org.dspace.storage.rdbms.DatabaseManager @ 
SQL connection Error - 

org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool 
error Timeout waiting for idle object

With the help of Tim Donohue, I could sort out the problem with the 
following 
options: 
https://stackoverflow.com/questions/30778015/how-to-increase-the-max-connections-in-postgres/32584211#32584211

Some minutes after, I realized I could not view or download any bitstreams. 
The browser shows 500 Internal Server Error after some seconds of loading 
(timeout), and I can't find any related log entries (nothing on dspace.log, 
catalina.out, localhost.log, postgres logs).

I didn't remember if I updated anything, but either way I reinstalled and 
updated the JDK to 1.8 and did a "yum update". Everything went fine for 
some minutes and then, 500 error again. The repository is accesible, I can 
browse without any problems, except for the bitstreams.

I really don't know if the options noted in Stackoverflow produced 
something like this. I reverted the config but the SQL connections error 
started again.

I hope you have any idea what could be happening.

Thanks.
Javier.

-- 
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] Move section on item-view.xsl

[Javier Távara]

That was really helpful! I did it the way Mirage 2 does it.

Thank you!

Javier.

El viernes, 11 de mayo de 2018, 4:01:31 (UTC-5), Michael Plate escribió:
>
> Hi Javier, 
>
> Am 10.05.2018 um 01:30 schrieb Javier Távara: 
> > Hello! 
> > 
> > I've been customizing a little bit the item view. 
> > 
> > I want to move the "Files in this item" section to the middle of the 
> > metadata section (right after the abstract). 
>
> don't know what theme you are using, I'm using Mirage2. 
>
> In the template 
>
>  
>
> is a call-template 
>
>  
>
> Just move it below the 
>
>  
>
>
> CU 
>
> Michael 
>
>

-- 
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] CC-License trouble

[Javier Távara]

Jira says it has been fixed for 5.6 and 6.0. You can try updating.

El lunes, 14 de mayo de 2018, 7:43:25 (UTC-5), jc...@cin.ufpe.br escribió:
>
> Any news for this? I'm having the same problem.
>
> Em sexta-feira, 26 de agosto de 2016 05:53:53 UTC-3, Oliver Goldschmidt 
> escreveu:
>>
>> Hi,
>>
>> thank you for your reply. Unfortunately this solution does not work for 
>> me. Adding the trailing slah or not - it does not make a difference at all, 
>> for neither of the two issues.
>>
>> Thanks for the suggestion, though!
>>
>> Best
>> Oliver
>>
>> Am Donnerstag, 25. August 2016 16:35:23 UTC+2 schrieb Guillermo Esteban 
>> Murillo Goussen:
>>>
>>> Hi, I had the same issue like two months ago.  The solution was "add the 
>>> trailing slash at the cc.api.rooturl value.  I read at their documentation, 
>>> they chaged it, and it worked.
>>>
>>> # The url to the web service API
>>> cc.api.rooturl = http://api.creativecommons.org/rest/1.5*/*
>>>
>>> 2016-08-25 8:14 GMT-06:00 Oliver Goldschmidt :
>>>
 Hi DSpace community,

 I'm having trouble with the CC-Liceses again. Two things are a little 
 bit strange:

 * the local files license_rdf and license_text are empty
 This is already described in https://jira.duraspace.org/browse/DS-2604, 
 but obviously it is not solved yet. As I have noted in a comment there, I 
 have found a strange error in my dspace.log: 
 ERROR org.dspace.license.CreativeCommons @ Server returned HTTP 
 response code: 403 for URL: 
 http://creativecommons.org/licenses/by/3.0/de/
 I don't understand that, because getting the url with wget is not a 
 problem at all - even not from my DSpace server!

 * the license doesn't get it into the metadata
 This is already described in https://jira.duraspace.org/browse/DS-1538, 
 but also obviously not solved yet. dc.rights and dc.rights.uri are not 
 getting set at all (I have also seen the error message described in 
 DS-1538, but the more common behaviour is, that the field is not getting 
 set).

 Any ideas how to fix this? We are using DSpace 5.4 with JSPUI (and are 
 about to switch to 5.6)

 Thanks in advance for any hints,
 best
 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...@googlegroups.com.
 To post to this group, send email to dspac...@googlegroups.com.
 Visit this group at https://groups.google.com/group/dspace-tech.
 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.

[dspace-tech] Re: Ayuda con sitemaps

[Javier Távara]

Hola Lady,
Prueba añadiendo el archivo en la raíz de tu *theme*, en mi caso es 
[dspace-source]/dspace/modules/xmlui/src/main/webapp/themes/[theme]
Si no funciona, usa los métodos alternativos, como una etiqueta meta que 
puedes añadir 
en 
[dspace-source]/dspace/modules/xmlui/src/main/webapp/themes/[theme]/lib/xsl/core/page-structure.xsl
En ambos casos debes recompilar DSpace.
Si ya agregaste el código de seguimiento de Google Analytics, también 
puedes vincular las cuentas y no pedirá más verificación.

Pero la opción más simple es validar creando un CNAME en tus DNS.

Saludos.
Javier.


El lunes, 7 de mayo de 2018, 8:57:35 (UTC-5), Leidy Madroñero escribió:
>
> Buenos días a todos
>
> Tengo un problema para añadir la propiedad de google sitemaps a mi 
> repositorio, el inconveniente radica en el lugar exacto de la instalación 
> de Dspace en donde debo alojar el archivo de verificación para sitemaps  ya 
> que he probado en algunas secciones de la instalación pero no he tenido 
> resultados. En cual carpeta de Dspace exactamente debe estar ese archivo?. 
> He asignado como mi sitio web de esta forma: 
>
> Agradezco sus respuestas.
>
> Un saludo, lady.
>
> Método recomendado 
> 
>  Métodos alternativos 
> 
> *recomendado: *Subir archivo HTMLSube un archivo HTML a tu sitio web.
>
> *1. Descarga* este archivo HTML de verificación 
> [googleee64ece564feb7d0.html] .
>
> *2. Sube* el archivo a http://52.191.254.87:8080/.
>
> *3. Confirma* que la subida se ha realizado correctamente a través de la 
> página http://52.191.254.87:8080/googleee64ece564feb7d0.html .
>
> *4. Haz clic* en el botón de verificación que aparece a continuación.
>
> Para mantener la verificación, no elimine el archivo HTML aunque la 
> verificación se haya realizado correctamente.
> VERIFICAR
>  
> Ahora no
>

-- 
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] Re: Smtp email configuration

[Javier Távara]

May we know what service are you trying to configure? Something like 
Sendgrid, Mailchannels, etc. or something local?

Javier.

El jueves, 10 de mayo de 2018, 2:04:29 (UTC-5), Haimanot Birhanu escribió:
>
> Hey,
>
> This doesn't work for me so any suggestion?
>
> On Wednesday, May 9, 2018 at 3:58:37 PM UTC+3, Leidy Madroñero wrote:
>>
>> Hello
>>
>> Yo me he guiado basándome en este post: 
>> http://dspacegeek.blogspot.com.co/2016/10/configure-gmail-with-dspace.html
>>
>> Espero le sea útil.
>>
>> Un saludo, lady.
>>
>

-- 
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] Move section on item-view.xsl

[Javier Távara]

Hello!

I've been customizing a little bit the item view.

I want to move the "Files in this item" section to the middle of the 
metadata section (right after the abstract).





Any idea how to achieve it? I really don't understand too much the XSLT 
functions. I have tried this:















But doesn't show anything.

I'm using DSpace 5.5 and a customized version of the Mirage default theme.


I can do it using javascript but the XSLT way will be better. Hope you have 
some advice.


Thank you!

Javier.

-- 
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] Re: Dspace translation with Diacritical marks errors

[Javier Távara]

Hi Gonzalo.
Make sure you have URIEncoding="UTF-8" in you server.xml

Take a look on this 
guide 
https://confluence.tavara.pe/display/DSPACEDOC5x/Configurar+Apache+HTTP+como+proxy+con+certificado+SSL+de+Let%27s+Encrypt

Javier.

El miércoles, 4 de abril de 2018, 9:28:15 (UTC-5), gonzalo perl escribió:
>
> Hello everybody
>
> I have added the Spanish translation to Dspace, but i have some problems 
> with diacritical marks. Because some words are writing with errors. And i 
> don´t know which is the problem.
>
> Any idea?
>
> Regards
> Gonzalo
>
>

-- 
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] Re: Dspace like a discovery and Discovery tools

[Javier Távara]

I don't think DSpace falls in the category.

You are probably looking for something like VuFind.

Javier.


El jueves, 12 de abril de 2018, 14:48:50 (UTC-5), Manuel Hidalgo escribió:
>
> Hi
>
> We are in the process of searching for a Discovery tool - Open Source, in 
> that process the possibility of using DSPACE as a discovery tool arises. 
> Has any person had experience applying it that way?
>
> On the other hand we would like to know your suggestions on Open Source 
> discovery tools.
>
> Best
> Manuel
>
>
>

-- 
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] Send notification when embargo lifts

[Javier Távara]

Hello.
I'm using DSpace 5.5 and I want DSpace to send an email to the 
administrators when an embargoed item is released to the public.

I was thinking in storing the embargo date in metadata and read it from an 
external service using the REST API. It's an option. But do you know how 
can I achieve that just using DSpace?

I was reading the DefaultEmbargoLifter/Setter java classes but I'm afraid 
those aren't used anymore. Am I right?

- Javier.

-- 
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: CC License step failing

[Javier Távara]

Thanks Rob, definitely the best choice.

I see the API is back online.

— Javier T.

On Apr 3, 2018, 1:04 PM -0500, Rob Myers , wrote:
> Heya all.
>
> I have re-enabled http for now. I will put a redirect back in place at some 
> point in the future, with suitable warning.
>
> For anyone who changing the url to be https didn't help, does switching back 
> to http improve things?
>
> - Rob.
>
> On Monday, April 2, 2018 at 5:13:57 PM UTC-7, Rob Myers wrote:
> > Heya Javier.
> >
> > Thank you for checking this.
> >
> > There is a 301 redirect in place from http to https.
> >
> > The old server had Varnish publicly accessible on port 80, which I assumed 
> > was an error so I didn't recreate that (we were meant to have switched 
> > everything to https a couple of years ago!).
> >
> > If changing to https fixes the issue, this would explain it.
> >
> > Is it easy to change cc.api.rooturl to https, or is that going to be a pain 
> > for people?
> >
> > Thank you again.
> >
> > - Rob.
> >
> > On Monday, April 2, 2018 at 4:59:23 PM UTC-7, Javier Távara wrote:
> > > Thank you for the update Rob.
> > >
> > > Any redirection is being applied from non-SSL to SSL? Was the same before 
> > > the update?
> > >
> > > I changed my settings (dspace.cfg) to use SSL:
> > >
> > > # The url to the web service API
> > > cc.api.rooturl = https://api.creativecommons.org/rest/1.5
> > >
> > > And it works now :)
> > >
> > > - Javier.
> > >
> > > El lunes, 2 de abril de 2018, 18:51:16 (UTC-5), Rob Myers escribió:
> > > > Heya everyone, Rob from Creative Commons here.
> > > >
> > > > I'm very sorry that our API isn't working with DSpace at the moment. I 
> > > > upgraded the server that the API runs on, and the problem that you are 
> > > > seeing wasn't caught by my tests.
> > > >
> > > > If I call the API simply via the command line, e.g.:
> > > >
> > > > curl -d 
> > > > "answers=enysaUntitledA.
> > > >  N. 
> > > > Otherhttps://example.com/untitled"
> > > >  https://api.creativecommons.org/rest/1.5/license/standard/issue
> > > >
> > > > Then I do get back an xml block, e.g.:
> > > >
> > > > 
> > > > 
> > > >   
> > > > http://creativecommons.org/licenses/by-sa/4.0/
> > > >   Attribution-ShareAlike 4.0 International
> > > >   false
> > > >   
> > > >     http://creativecommons.org/ns#"; 
> > > > xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";>
> > > >   http://purl.org/dc/elements/1.1/"; 
> > > > rdf:about="https://example.com/untitled";>UntitledA.
> > > >  N. Other > > > rdf:resource="http://creativecommons.org/licenses/by-sa/4.0/"/> > > >  rdf:about="http://creativecommons.org/licenses/by-sa/4.0/";>
> > > >      > > > rdf:resource="http://creativecommons.org/ns#DerivativeWorks"/>
> > > >     http://creativecommons.org/ns#Distribution"/>
> > > >     http://creativecommons.org/ns#Reproduction"/>
> > > >     http://creativecommons.org/ns#Attribution"/>
> > > >     http://creativecommons.org/ns#Notice"/>
> > > >     http://creativecommons.org/ns#ShareAlike"/>
> > > >   
> > > > 
> > > >   
> > > >   
> > > >     http://creativecommons.org/ns#"; 
> > > > xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";>
> > > >   http://creativecommons.org/licenses/by-sa/4.0/";>
> > > >      > > > rdf:resource="http://creativecommons.org/ns#DerivativeWorks"/>
> > > >     http://creativecommons.org/ns#Distribution"/>
> > > >     http://creativecommons.org/ns#Reproduction"/>
> > > >     http://creativecommons.org/ns#Attribution"/>
> > > >     http://creativecommons.org/ns#Notice"/>
> > > >     http://creativecommons.org/ns#ShareAlike"/>
> > > >   
> > > > 
> > > >   
> > > >    > > > href="http://creativecommons.org/licenses/by-sa/4.0/";> > > > alt="Creative Commons License" style="border-width:0" 
> > > > src="http://i.creat

Re: [dspace-tech] Re: CC License step failing

[Javier Távara]

George,
It depends on where you are doing the change. See 
https://wiki.duraspace.org/display/DSPACE/Rebuild+DSpace and 
https://wiki.duraspace.org/display/DSDOC5x/Ant+targets+and+options

I only make changes to [dspace-source], so I have to rebuild it for the new 
config to be copied to [dspace] installation directory.

I saved this as config-update.sh to make things faster:

cd /home/dspace/source-5.5/dspace
mvn package -P !dspace-jspui,!dspace-sword,!dspace-swordv2,!dspace-rdf
cd /home/dspace/source-5.5/dspace/target/dspace-installer
ant update_configs
service tomcat restart

I hope I'm not doing unnecessary stuff.

— Javier T.

On Apr 3, 2018, 12:19 PM -0500, George Kozak , wrote:
> Javier:
> On my DSpace 5.5 instance, I made the change you noted to https in the 
> dspace.cfg file and restarted tomcat.  On my DSpace 6.2 instance, I made the 
> change in the local.cfg file and restarted tomcat, but in both cases, nothing 
> changed.  I couldn't reconnect.
>
> I see in your email that you mentioned recompiling.  Do you mean going 
> through the Maven and ant process all over again after this change is made?
> George Kozak
> Cornell University
>
> > On Tue, Apr 3, 2018 at 9:52 AM, Javier Távara  wrote:
> > > Rob,
> > > The change is easy, at least for the most common DSpace installations, 
> > > but it will break a lot of instances probably. It must be done at any 
> > > time in the future though.
> > >
> > > George,
> > > Are you sure you recompiled DSpace correctly? The API was online when you 
> > > posted.
> > >
> > > CC API is down since 8:41 UTC (I started monitoring it yesterday 
> > > https://goo.gl/xEwLjn).
> > > Meanwhile, I will better disable the CC License step until everything is 
> > > back stable.
> > >
> > > - Javier.
> > >
> > > El martes, 3 de abril de 2018, 7:41:14 (UTC-5), Marion Rupp escribió:
> > > > Hi,
> > > >
> > > > We still have failure with CC, too (DSpace Version 6.2).
> > > >
> > > > At the momentan, the CC API at https://api.creativecommons.org/rest/1.5 
> > > > is not available (503 error).
> > > >
> > > > Kind regards,
> > > > Marion
> > > >
> > > > ---
> > > > Marion Rupp
> > > > Bibliotheks-IT
> > > > Universitäts- und Landesbibliothek Bonn
> > > > Postfach 2460, D-53014 Bonn
> > > > Tel. 0228 / 73 75 50 Fax: 0228 / 73 75 46
> > > > eMail: mario...@ulb.uni-bonn.de
> > > > Internet: http://www.ulb.uni-bonn.de
> > > > Twitter: http://twitter.com/ulbbonn
> > > > Facebook: http://facebook.com/ulbbonn
> > > > Am 03.04.2018 um 02:49 schrieb George Kozak:
> > > > > Hi, Everyone:
> > > > > I made the suggested change from http to https, but I still have 
> > > > > failure in connecting to Creative Commons.  I restarted tomcat and 
> > > > > cleared the cocoon cache, as well.
> > > > > George Kozak
> > > > > Cornell University
> > > > >
> > > > > > On Mon, Apr 2, 2018 at 7:59 PM, Javier Távara  
> > > > > > wrote:
> > > > > > > Thank you for the update Rob.
> > > > > > >
> > > > > > > Any redirection is being applied from non-SSL to SSL? Was the 
> > > > > > > same before the update?
> > > > > > >
> > > > > > > I changed my settings (dspace.cfg) to use SSL:
> > > > > > >
> > > > > > > # The url to the web service API
> > > > > > > cc.api.rooturl = https://api.creativecommons.org/rest/1.5
> > > > > > >
> > > > > > > And it works now :)
> > > > > > >
> > > > > > > - Javier.
> > > > > > >
> > > > > > > El lunes, 2 de abril de 2018, 18:51:16 (UTC-5), Rob Myers 
> > > > > > > escribió:
> > > > > > > > Heya everyone, Rob from Creative Commons here.
> > > > > > > >
> > > > > > > > I'm very sorry that our API isn't working with DSpace at the 
> > > > > > > > moment. I upgraded the server that the API runs on, and the 
> > > > > > > > problem that you are seeing wasn't caught by my tests.
> > > > > > > >
> > > > > > > > If I call the API sim

Re: [dspace-tech] Re: CC License step failing

[Javier Távara]

Rob, 
The change is easy, at least for the most common DSpace installations, but 
it will break a lot of instances probably. It must be done at any time in 
the future though.

George,
Are you sure you recompiled DSpace correctly? The API was online when you 
posted.

CC API is down since 8:41 UTC (I started monitoring it yesterday 
https://goo.gl/xEwLjn).
Meanwhile, I will better disable the CC License step until everything is 
back stable.

- Javier.

El martes, 3 de abril de 2018, 7:41:14 (UTC-5), Marion Rupp escribió:
>
> Hi,
>
> We still have failure with CC, too (DSpace Version 6.2). 
>
> At the momentan, the CC API at https://api.creativecommons.org/rest/1.5 
> is not available (503 error).
>
> Kind regards,
> Marion
>
> ---
> Marion Rupp
> Bibliotheks-IT
> Universitäts- und Landesbibliothek Bonn
> Postfach 2460, D-53014 Bonn
> Tel. 0228 / 73 75 50 Fax: 0228 / 73 75 46
> eMail: mario...@ulb.uni-bonn.de 
> Internet: http://www.ulb.uni-bonn.de
> Twitter: http://twitter.com/ulbbonn
> Facebook: http://facebook.com/ulbbonn
>
> Am 03.04.2018 um 02:49 schrieb George Kozak:
>
> Hi, Everyone: 
> I made the suggested change from http to https, but I still have failure 
> in connecting to Creative Commons.  I restarted tomcat and cleared the 
> cocoon cache, as well.
> George Kozak
> Cornell University
>
> On Mon, Apr 2, 2018 at 7:59 PM, Javier Távara  > wrote:
>
>> Thank you for the update Rob. 
>>
>> Any redirection is being applied from non-SSL to SSL? Was the same before 
>> the update?
>>
>> I changed my settings (dspace.cfg) to use SSL:
>>
>> # The url to the web service API
>> cc.api.rooturl = https://api.creativecommons.org/rest/1.5
>>
>> And it works now :)
>>
>> - Javier.
>>
>> El lunes, 2 de abril de 2018, 18:51:16 (UTC-5), Rob Myers escribió: 
>>>
>>> Heya everyone, Rob from Creative Commons here. 
>>>
>>> I'm very sorry that our API isn't working with DSpace at the moment. I 
>>> upgraded the server that the API runs on, and the problem that you are 
>>> seeing wasn't caught by my tests.
>>>
>>> If I call the API simply via the command line, e.g.:
>>>
>>> curl -d 
>>> "answers=enysaUntitledA.
>>>  
>>> N. 
>>> Otherhttps://example.com/untitled"
>>>  
>>> https://api.creativecommons.org/rest/1.5/license/standard/issue
>>>
>>> Then I do get back an xml block, e.g.:
>>>
>>> 
>>> 
>>>   http://creativecommons.org/licenses/by-sa/4.0/
>>> 
>>>   Attribution-ShareAlike 4.0 International
>>>   false
>>>   
>>> http://creativecommons.org/ns#"; xmlns:rdf="
>>> http://www.w3.org/1999/02/22-rdf-syntax-ns#";>
>>>   http://purl.org/dc/elements/1.1/"; rdf:about="
>>> https://example.com/untitled";>UntitledA. 
>>> N. Otherhttp://creativecommons.org/licenses/by-sa/4.0/"/>>> rdf:about="http://creativecommons.org/licenses/by-sa/4.0/";>
>>> http://creativecommons.org/ns#DerivativeWorks
>>> "/>
>>> http://creativecommons.org/ns#Distribution"/>
>>> http://creativecommons.org/ns#Reproduction"/>
>>> http://creativecommons.org/ns#Attribution"/>
>>> http://creativecommons.org/ns#Notice"/>
>>> http://creativecommons.org/ns#ShareAlike"/>
>>>   
>>> 
>>>   
>>>   
>>> http://creativecommons.org/ns#"; xmlns:rdf="
>>> http://www.w3.org/1999/02/22-rdf-syntax-ns#";>
>>>   http://creativecommons.org/licenses/by-sa/4.0/";>
>>> http://creativecommons.org/ns#DerivativeWorks
>>> "/>
>>> http://creativecommons.org/ns#Distribution"/>
>>> http://creativecommons.org/ns#Reproduction"/>
>>> http://creativecommons.org/ns#Attribution"/>
>>> http://creativecommons.org/ns#Notice"/>
>>> http://creativecommons.org/ns#ShareAlike"/>
>>>   
>>> 
>>>   
>>>   http://creativecommons.org/licenses/by-sa/4.0/";>http://i.creativecommons.org/l/by-sa/4.0/88x31.png"/>>> xmlns:dct="http://purl.org/dc/terms/"; 
>>> property="dct:title">Untitled by http://creativecommons.org/ns#"; href="https://example.com/untitled"; 
>>> property="cc:attributionName" rel="cc:attributionURL">A. N. Oth

Re: [dspace-tech] Re: CC License step failing

[Javier Távara]

(Posting this again because somehow messages are being deleted by mistake 
or false spam alarm)

Rob, 
The change is easy, at least for the most common DSpace installations, but 
it will break a lot of instances probably. It must be done at any time in 
the future though.

George,
Are you sure you recompiled DSpace correctly? The API was online when you 
posted.

CC API is down since 8:41 UTC.
Meanwhile, I will better disable the CC License step until everything is 
back stable.

- Javier.

El martes, 3 de abril de 2018, 7:41:14 (UTC-5), Marion Rupp escribió:
>
> Hi,
>
> We still have failure with CC, too (DSpace Version 6.2). 
>
> At the momentan, the CC API at https://api.creativecommons.org/rest/1.5 
> is not available (503 error).
>
> Kind regards,
> Marion
>
> ---
> Marion Rupp
> Bibliotheks-IT
> Universitäts- und Landesbibliothek Bonn
> Postfach 2460, D-53014 Bonn
> Tel. 0228 / 73 75 50 Fax: 0228 / 73 75 46
> eMail: mario...@ulb.uni-bonn.de 
> Internet: http://www.ulb.uni-bonn.de
> Twitter: http://twitter.com/ulbbonn
> Facebook: http://facebook.com/ulbbonn
>
> Am 03.04.2018 um 02:49 schrieb George Kozak:
>
> Hi, Everyone: 
> I made the suggested change from http to https, but I still have failure 
> in connecting to Creative Commons.  I restarted tomcat and cleared the 
> cocoon cache, as well.
> George Kozak
> Cornell University
>
> On Mon, Apr 2, 2018 at 7:59 PM, Javier Távara  > wrote:
>
>> Thank you for the update Rob. 
>>
>> Any redirection is being applied from non-SSL to SSL? Was the same before 
>> the update?
>>
>> I changed my settings (dspace.cfg) to use SSL:
>>
>> # The url to the web service API
>> cc.api.rooturl = https://api.creativecommons.org/rest/1.5
>>
>> And it works now :)
>>
>> - Javier.
>>
>> El lunes, 2 de abril de 2018, 18:51:16 (UTC-5), Rob Myers escribió: 
>>>
>>> Heya everyone, Rob from Creative Commons here. 
>>>
>>> I'm very sorry that our API isn't working with DSpace at the moment. I 
>>> upgraded the server that the API runs on, and the problem that you are 
>>> seeing wasn't caught by my tests.
>>>
>>> If I call the API simply via the command line, e.g.:
>>>
>>> curl -d 
>>> "answers=enysaUntitledA.
>>>  
>>> N. 
>>> Otherhttps://example.com/untitled"
>>>  
>>> https://api.creativecommons.org/rest/1.5/license/standard/issue
>>>
>>> Then I do get back an xml block, e.g.:
>>>
>>> 
>>> 
>>>   http://creativecommons.org/licenses/by-sa/4.0/
>>> 
>>>   Attribution-ShareAlike 4.0 International
>>>   false
>>>   
>>> http://creativecommons.org/ns#"; xmlns:rdf="
>>> http://www.w3.org/1999/02/22-rdf-syntax-ns#";>
>>>   http://purl.org/dc/elements/1.1/"; rdf:about="
>>> https://example.com/untitled";>UntitledA. 
>>> N. Otherhttp://creativecommons.org/licenses/by-sa/4.0/"/>>> rdf:about="http://creativecommons.org/licenses/by-sa/4.0/";>
>>> http://creativecommons.org/ns#DerivativeWorks
>>> "/>
>>> http://creativecommons.org/ns#Distribution"/>
>>> http://creativecommons.org/ns#Reproduction"/>
>>> http://creativecommons.org/ns#Attribution"/>
>>> http://creativecommons.org/ns#Notice"/>
>>> http://creativecommons.org/ns#ShareAlike"/>
>>>   
>>> 
>>>   
>>>   
>>> http://creativecommons.org/ns#"; xmlns:rdf="
>>> http://www.w3.org/1999/02/22-rdf-syntax-ns#";>
>>>   http://creativecommons.org/licenses/by-sa/4.0/";>
>>> http://creativecommons.org/ns#DerivativeWorks
>>> "/>
>>> http://creativecommons.org/ns#Distribution"/>
>>> http://creativecommons.org/ns#Reproduction"/>
>>> http://creativecommons.org/ns#Attribution"/>
>>> http://creativecommons.org/ns#Notice"/>
>>> http://creativecommons.org/ns#ShareAlike"/>
>>>   
>>> 
>>>   
>>>   http://creativecommons.org/licenses/by-sa/4.0/";>http://i.creativecommons.org/l/by-sa/4.0/88x31.png"/>>> xmlns:dct="http://purl.org/dc/terms/"; 
>>> property="dct:title">Untitled by http://creativecommons.org/ns#"; href="https://example.com/untitled"; 
>>> property="cc:attributionName" rel=&q

[dspace-tech] Re: CC License step failing

[Javier Távara]

Thank you for the update Rob.

Any redirection is being applied from non-SSL to SSL? Was the same before 
the update?

I changed my settings (dspace.cfg) to use SSL:

# The url to the web service API
cc.api.rooturl = https://api.creativecommons.org/rest/1.5

And it works now :)

- Javier.

El lunes, 2 de abril de 2018, 18:51:16 (UTC-5), Rob Myers escribió:
>
> Heya everyone, Rob from Creative Commons here.
>
> I'm very sorry that our API isn't working with DSpace at the moment. I 
> upgraded the server that the API runs on, and the problem that you are 
> seeing wasn't caught by my tests.
>
> If I call the API simply via the command line, e.g.:
>
> curl -d 
> "answers=enysaUntitledA.
>  
> N. 
> Otherhttps://example.com/untitled"
>  
> https://api.creativecommons.org/rest/1.5/license/standard/issue
>
> Then I do get back an xml block, e.g.:
>
> 
> 
>   http://creativecommons.org/licenses/by-sa/4.0/
> 
>   Attribution-ShareAlike 4.0 International
>   false
>   
> http://creativecommons.org/ns#"; xmlns:rdf="
> http://www.w3.org/1999/02/22-rdf-syntax-ns#";>
>   http://purl.org/dc/elements/1.1/"; rdf:about="
> https://example.com/untitled";>UntitledA. 
> N. Otherhttp://creativecommons.org/licenses/by-sa/4.0/"/> rdf:about="http://creativecommons.org/licenses/by-sa/4.0/";>
> http://creativecommons.org/ns#DerivativeWorks
> "/>
> http://creativecommons.org/ns#Distribution"/>
> http://creativecommons.org/ns#Reproduction"/>
> http://creativecommons.org/ns#Attribution"/>
> http://creativecommons.org/ns#Notice"/>
> http://creativecommons.org/ns#ShareAlike"/>
>   
> 
>   
>   
> http://creativecommons.org/ns#"; xmlns:rdf="
> http://www.w3.org/1999/02/22-rdf-syntax-ns#";>
>   http://creativecommons.org/licenses/by-sa/4.0/";>
> http://creativecommons.org/ns#DerivativeWorks
> "/>
> http://creativecommons.org/ns#Distribution"/>
> http://creativecommons.org/ns#Reproduction"/>
> http://creativecommons.org/ns#Attribution"/>
> http://creativecommons.org/ns#Notice"/>
> http://creativecommons.org/ns#ShareAlike"/>
>   
> 
>   
>   http://creativecommons.org/licenses/by-sa/4.0/";>http://i.creativecommons.org/l/by-sa/4.0/88x31.png"/> xmlns:dct="http://purl.org/dc/terms/"; 
> property="dct:title">Untitled by http://creativecommons.org/ns#"; href="https://example.com/untitled"; 
> property="cc:attributionName" rel="cc:attributionURL">A. N. Other is 
> licensed under a http://creativecommons.org/licenses/by-sa/4.0/";>Creative Commons 
> Attribution-ShareAlike 4.0 International License.
> 
>
> Which does validate OK locally.
>
> The only thing that should have changed for users of the API is the SSL 
> certificate for the domain (might the old one be being cached somewhere?), 
> although the versions of Python and Apache Web server that the software 
> runs of have jumped a few versions, so it is possible that something else 
> has changed without me catching it.
>
> I'd be very grateful if anyone could pass me any further information, 
> particularly if anyone can see what api.creativecommons.org thinks it is 
> sending back to DSpace in response to a license request.
>
> Thank you, and again my apologies for this.
>
> - Rob Myers,
> Core Systems Manager,
> Creative Commons.
>
>
> On Monday, April 2, 2018 at 3:38:07 PM UTC-7, Javier Távara wrote:
>>
>> I saw the tweets. Thank you.
>>
>> As we don't have any useful logs of what's happening, I thought 
>> disabling/enabling the step could fire any sort of cache clearing.
>>
>> No success.
>>
>> - Javier
>>
>> El lunes, 2 de abril de 2018, 17:33:16 (UTC-5), Keith Gilbertson escribió:
>>>
>>>
>>>
>>> On Monday, April 2, 2018 at 6:18:47 PM UTC-4, Javier Távara wrote:
>>>>
>>>> I really don't want to disable the CC License step.
>>>>
>>>> That's understandable. Our repository team has been encouraging people 
>>> to select CC licenses. 
>>> Rob Myers at Creative Commons is aware that some DSpace repositories 
>>> have had an issue, but it's now past normal working hours, and I haven't 
>>> been able to provide him with any useful information as to what's 
>>> specifically causing the problem.
>>>
>>>
>>> Disabling/enabling fixes nothing by the way.
&g

[dspace-tech] Re: CC License step failing

[Javier Távara]

I saw the tweets. Thank you.

As we don't have any useful logs of what's happening, I thought 
disabling/enabling the step could fire any sort of cache clearing.

No success.

- Javier

El lunes, 2 de abril de 2018, 17:33:16 (UTC-5), Keith Gilbertson escribió:
>
>
>
> On Monday, April 2, 2018 at 6:18:47 PM UTC-4, Javier Távara wrote:
>>
>> I really don't want to disable the CC License step.
>>
>> That's understandable. Our repository team has been encouraging people to 
> select CC licenses. 
> Rob Myers at Creative Commons is aware that some DSpace repositories have 
> had an issue, but it's now past normal working hours, and I haven't been 
> able to provide him with any useful information as to what's specifically 
> causing the problem.
>
>
> Disabling/enabling fixes nothing by the way.
>>
>> I had to comment out the CC License step in multiple locations in the 
> item-submission.xml file on our test server, and then restart Tomcat. I 
> think you are offering additional information that the CC License step 
> still doesn't work once you enable it again.
>
>  
>
>> - Javier.
>>
>> El lunes, 2 de abril de 2018, 16:43:29 (UTC-5), Keith Gilbertson escribió:
>>>
>>> George, we've had similar problems today. We'll probably disable CC 
>>> License steps for now, and then restart Tomcat. On our system, this is 
>>> configured in /dspace/conf/item-submission.xml
>>> --keith
>>>
>>> On Monday, April 2, 2018 at 5:31:29 PM UTC-4, George Kozak wrote:
>>>>
>>>> Hi,
>>>> We have a DSpace 5.5 and a DSpace 6.2 install.  This afternoon, the CC 
>>>> License submission step stopped working and caused an internal error.  I 
>>>> don't use Twitter, but one of my co-workers who does saw Creative Commons 
>>>> tweeted that their API was broken, but an hour later said it was back up.  
>>>> However, our DSpace installs are still failing at the CC License step.  I 
>>>> tried rebooting my tomcat, but that didn't help.  Any suggestions?
>>>>
>>>> -- 
>>>> ***
>>>> George Kozak
>>>> Digital Library Specialist
>>>> Cornell University Library - IT
>>>> 218 Olin Library
>>>> Cornell University
>>>> Ithaca, NY 14853
>>>> 607-255-8924
>>>> gs...@cornell.edu 
>>>>
>>>

-- 
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] Re: CC License step failing

[Javier Távara]

I really don't want to disable the CC License step.

Disabling/enabling fixes nothing by the way.

- Javier.

El lunes, 2 de abril de 2018, 16:43:29 (UTC-5), Keith Gilbertson escribió:
>
> George, we've had similar problems today. We'll probably disable CC 
> License steps for now, and then restart Tomcat. On our system, this is 
> configured in /dspace/conf/item-submission.xml
> --keith
>
> On Monday, April 2, 2018 at 5:31:29 PM UTC-4, George Kozak wrote:
>>
>> Hi,
>> We have a DSpace 5.5 and a DSpace 6.2 install.  This afternoon, the CC 
>> License submission step stopped working and caused an internal error.  I 
>> don't use Twitter, but one of my co-workers who does saw Creative Commons 
>> tweeted that their API was broken, but an hour later said it was back up.  
>> However, our DSpace installs are still failing at the CC License step.  I 
>> tried rebooting my tomcat, but that didn't help.  Any suggestions?
>>
>> -- 
>> ***
>> George Kozak
>> Digital Library Specialist
>> Cornell University Library - IT
>> 218 Olin Library
>> Cornell University
>> Ithaca, NY 14853
>> 607-255-8924
>> gs...@cornell.edu 
>>
>

-- 
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] Re: Unable to take backups

[Javier Távara]

You have to be more specific if you want us to help you.
What RDBMS are you using? What errors are you seeing?


El viernes, 5 de enero de 2018, 2:05:00 (UTC-5), Naresh P escribió:
>
> Dear Pals,
>   i have a problem with my dspace application, i am unable to 
> query tables and take backups of it.  Please help me out.
>
>
>
> Thanks,
> Naresh.
>

-- 
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] Translate values in Discovery sidebar

[Javier Távara]

Hi Claudia. That's what I'm looking for! Except this is for XMLUI.

then customize the facet display to not use the metadata text value but 
> a value from the catalogue where the metadata text value is a key. 


The problem is I'm not sure how to do that. Maybe I can do it with XSLT but 
I'm not good with it. Any advice?

I'm using DSpace 5.5

Javier.

El miércoles, 6 de diciembre de 2017, 6:43:37 (UTC-5), Claudia Jürgen 
escribió:
>
> Hello Javier, 
>
> so you have metadatavalues like that: 
> dc.type = info:eu-repo/semantics/article 
> like defined in the OpenAire guidelines 
>
> https://guidelines.openaire.eu/en/latest/literature/field_publicationtype.html
>  
>
> Imo it might be better to use just the types as metadatum, e.g. article 
> and then transform it in the OAI-PMH crosswalk. 
> Openaire has changed things overtime like there Project Identifier where 
> the info:eu-repo part has changed. 
>
> But still this leaves you with the display. This is afaik not 
> configurable. But you can add the fields to the message catalogue and 
> then customize the facet display to not use the metadata text value but 
> a value from the catalogue where the metadata text value is a key. 
>
> We have done this for several metadata fields where controlled terms are 
> used like DDC, language, publication type 
> see https://eldorado.tu-dortmund.de/handle/2003/3 
>
> Hope this helps 
>
> Claudia Jürgen 
>
>
> Am 05.12.2017 um 16:29 schrieb Javier Távara: 
> > 
> > Hello. 
> > 
> > I have the Discovery sidebar with values like these: 
> > 
> > 
> > <
> https://lh3.googleusercontent.com/-xsC8AD-VvEk/Wia6AEU6CzI/A5g/CGsit1Gs8ioJ41dwiSb12fKq-ubTYB4VACLcBGAs/s1600/screenshot%2B2017-12-05%2Ba%2Bla%2528s%2529%2B10.22.37%2Ba.%2Bm..jpg>
>  
>
> > 
> > 
> > The last group is the dc.type one. I want to show "Capítulo (45)" 
> instead 
> > of "info:eu-repo/semantics/bookPart (45)". I shouldn't change the 
> metadata 
> > values. 
> > 
> > 
> > Do you know how to do it? 
> > 
> > 
> > Thank you. 
> > 
> > Javier. 
> > 
>
> -- 
> 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 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] Translate values in Discovery sidebar

[Javier Távara]

Thank you Paul. Unfortunately that is not possible, there will be more work 
for the admins.


El miércoles, 6 de diciembre de 2017, 1:35:56 (UTC-5), Paul Münch escribió:
>
> Hello Javier,
>
> if you don't want to change the values in dc.type, you could create a 
> metadatum in local namespace, e.g. local.type, and set this in the sidebar 
> instead.
>
> Kind regards,
>
> Paul
>
> Am 05.12.2017 um 16:29 schrieb Javier Távara:
>
> Hello.
>
> I have the Discovery sidebar with values like these:
>
>
>
> <https://lh3.googleusercontent.com/-xsC8AD-VvEk/Wia6AEU6CzI/A5g/CGsit1Gs8ioJ41dwiSb12fKq-ubTYB4VACLcBGAs/s1600/screenshot%2B2017-12-05%2Ba%2Bla%2528s%2529%2B10.22.37%2Ba.%2Bm..jpg>
>
>
> The last group is the dc.type one. I want to show "Capítulo (45)" instead 
> of "info:eu-repo/semantics/bookPart (45)". I shouldn't change the 
> metadata values.
>
>
> Do you know how to do it?
>
>
> Thank you.
>
> Javier.
>
> -- 
> 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...@googlegroups.com .
> To post to this group, send email to dspac...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/dspace-tech.
> For more options, visit https://groups.google.com/d/optout.
>
>
> -- 
> Philipps-Universität Marburg | UB
> Digitale Dienste | Wilhelm-Röpke-Straße 6 | 08A09
> Tel. 06421/28-24624 | 
> --
>
>

-- 
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] Translate values in Discovery sidebar

[Javier Távara]

Hello.

I have the Discovery sidebar with values like these:





The last group is the dc.type one. I want to show "Capítulo (45)" instead 
of "info:eu-repo/semantics/bookPart (45)". I shouldn't change the metadata 
values.


Do you know how to do it?


Thank you.

Javier.

-- 
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] i18n for submission forms

[Javier Távara]

Hi.
I would like to translate some buttons from the submission user interface.


I can't find the appropiate keys in the messages.xml.

Do you know where I can do this?
I'm using DSpace 5.5 and XMLUI.

Thanks.
Javier.

-- 
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] Characters in Request Copy messages

[Javier Távara]

Hello.
I need to modify the email template for the Request Copy forms. I've been 
following the guide in 
https://wiki.duraspace.org/display/DSDOC5x/Request+a+Copy#RequestaCopy-Emailtemplates

I've copied the Message.properties file from dspace-api and pasted to 
dspace/modules/xmlui/src/main/resources/Messages_es.properties.

The message changed, but the problem is I need this in Spanish, and we use 
characters like á/é/ñ, and those are not showing correctly. I also tried 
using HTML entities like é or é but it's not working.


Hope you can help me.
Thank you.
Javier.

-- 
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] Re: Dspace Handle Server error

[Javier Távara]

Hi.
Do you see any /error.log file? Are you behind nat?

El sábado, 25 de febrero de 2017, 9:38:23 (UTC-5), Ahmet Melih Başbuğ 
escribió:
>
> Hello. I have problem about handle server. It was working in past. but I 
> restarted handle and it doesn't work. I can't understand why? We got 
> handle.net account and it works. we configured settings before.
>
> when I gave start-handle-server, it start to work and i can see command in 
> ps -ef| grep handle.
> root@dspaceetu-vm:/dspace/handle-server# ps -ef | grep handle
> tomcat7   8481 1  0 16:13 pts/800:00:05 java -Xmx256m -classpath 
> :/dspace/lib/JUnitParams-...
>
>
> i looked ports 8000 and 2641 with sudo netstat -tulpn | grep :2641 command 
> but it doesn't show anything. In Iptables, I gave to 8000(tcp) and 
> 2641(udp,tcp) permissions​.
>
> tail -100f handle-server.log
> "2017/02/25 03:13:48 EET" 25 Rotating log files
>
> moreover when i go http://hdl.handle.net/20.500.11851/317  
>   I see  Error - Cannot Connect 
> to Server  error. What could the error be? I can't find any mistake.
>
> thanks
> Melih
>

-- 
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] Re: Dspace embargo-lifter CHECK WARNING

[Javier Távara]

I think your files with embargo are still accessible. Saw this with DSpace 
5.5.

If that is the case, running ./dspace embargo-lifter -a seems to apply the 
correct permissions. I don't know why this is happening.

El miércoles, 22 de febrero de 2017, 14:26:08 (UTC-5), Margaret Vail 
escribió:
>
> Hi,
>
> Has anyone seen a message like this before or have any idea what it is 
> trying to tell me?
>
> Thanks,
>
> Margaret
>
> Subject: Cron  /dspace/bin/./dspace 
> embargo-lifter
>
>  
>
> CHECK WARNING: Item 12345678/24509, filename.pdf.jpg (in Bundle THUMBNAIL) 
> allows READ by Group Anonymous CHECK WARNING: Item 12345678/24509, 
> Bitstream filename.pdf.txt (in Bundle TEXT) allows READ by Group Anonymous 
> CHECK WARNING: Item 12345678/24509, Bundle ORIGINAL allows READ by Group 
> Anonymous CHECK WARNING: Item 12345678/24509, Bitstream filename.pdf (in 
> Bundle ORIGINAL) allows READ by Group Anonymous
>

-- 
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: No website display

[Javier Távara]

Jeff, take a look in /etc/tomcat7/conf/Catalina/localhost/

El martes, 21 de febrero de 2017, 12:33:43 (UTC-5), Jeff Mitchell escribió:
>
> I am running dspace 5.1 on Debian 7.
>
> If I look at /etc/tomcat7/server.xml - I don't see anything for context 
> path. Am I not looking in the right location?
>
> Jeff
>
>
>
> On Tuesday, February 21, 2017 at 11:18:04 AM UTC-6, George Kozak wrote:
>>
>> Jeff:
>>
>> I don't know if this is helpful, but I had a similar problem when I moved 
>> our Test instance to a new Development server when I was planning on 
>> upgrading from DSpace 5.5 to DSpace 6.0.  The Development server was 
>> running a different version of Tomcat, and I discovered that I needed to 
>> change how I defined my site in the tomcat conf/server.xml file.
>>
>> On my test and production machines, I defined my tomcat root as:
>> 
>>
>> but on my development server that it did not work and created a blank 
>> page.  I discovered that I had to change the context path by adding a "/" 
>> on my development server:
>>
>> 
>>
>> This may not be your problem, but you may want to check out how DSpace is 
>> defined in your tomcat's server.xml file.
>>
>> George Kozak
>> Cornell University
>>
>> On Mon, Feb 20, 2017 at 2:55 PM, Jeff Mitchell  
>> wrote:
>>
>>> If I am looking at the output correctly Java is listening on 8080 but 
>>> tomcat should be.  Is that right, or do I need to switch something?
>>>
>>> If I need to switch something, how would that get changed?
>>>
>>> Jeff
>>>
>>>
>>>
>>> On Monday, February 20, 2017 at 1:47:46 PM UTC-6, Jeff Mitchell wrote:
>>>>
>>>> Sorry - Running Debian 7
>>>>
>>>> Jeff
>>>>
>>>>
>>>>
>>>> On Monday, February 20, 2017 at 1:46:02 PM UTC-6, Jeff Mitchell wrote:
>>>>>
>>>>> Output:
>>>>>
>>>>> tcp6   0  0 127.0.0.1:8005  :::*
>>>>> LISTEN  2478/java   
>>>>>
>>>>> tcp6   0  0 :::8009 :::*
>>>>> LISTEN  2478/java   
>>>>>
>>>>> tcp6   0  0 :::80   :::*
>>>>> LISTEN  2573/apache2
>>>>>
>>>>> tcp6   0  0 :::8080 :::*
>>>>> LISTEN  2478/java  
>>>>>
>>>>>
>>>>> So you are running Apache HTTP as a proxy? What OS are you running?
>>>>>> Again, disable the OS firewall to discard it.
>>>>>>
>>>>>> Check if there is something running on port 80.
>>>>>>
>>>>>> You can do 
>>>>>> sudo netstat -plnt | grep ':80'
>>>>>>
>>>>>> You should see httpd.
>>>>>>
>>>>>>
>>>>>> https://support.rackspace.com/how-to/checking-listening-ports-with-netstat/
>>>>>>
>>>>>>
>>>>>> El lunes, 20 de febrero de 2017, 14:35:33 (UTC-5), Jeff Mitchell 
>>>>>> escribió:
>>>>>>>
>>>>>>> It is basically a 404 error but both tomcat and apache are running.
>>>>>>>
>>>>>>> http://essays.wls.wels.net
>>>>>>>
>>>>>>> Looking at the logs now.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Monday, February 20, 2017 at 1:31:22 PM UTC-6, Javier Távara 
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> What errors are you getting?
>>>>>>>>
>>>>>>>> Check your Tomcat and DSpace logs.
>>>>>>>>
>>>>>>>> El lunes, 20 de febrero de 2017, 14:28:06 (UTC-5), Jeff Mitchell 
>>>>>>>> escribió:
>>>>>>>>>
>>>>>>>>> Restoring from backup didn't change anything.  Not sure what the 
>>>>>>>>> issue is as it was working on Thursday for sure.
>>>>>>>>>
>>>>>>>> -- 
>>>>>>
>>>>>>
>>>>> -- 
>>> 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...@googlegroups.com.
>>> To post to this group, send email to dspac...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/dspace-tech.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> -- 
>> ***
>> George Kozak
>> Digital Library Specialist
>> Cornell University Library - IT
>> 218 Olin Library
>> Cornell University
>> Ithaca, NY 14853
>> 607-255-8924
>> gs...@cornell.edu 
>>
>

-- 
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: No website display

[Javier Távara]

So you are running Apache HTTP as a proxy? What OS are you running?
Again, disable the OS firewall to discard it.

Check if there is something running on port 80.

You can do 
sudo netstat -plnt | grep ':80'

You should see httpd.

https://support.rackspace.com/how-to/checking-listening-ports-with-netstat/


El lunes, 20 de febrero de 2017, 14:35:33 (UTC-5), Jeff Mitchell escribió:
>
> It is basically a 404 error but both tomcat and apache are running.
>
> http://essays.wls.wels.net
>
> Looking at the logs now.
>
>
>
> On Monday, February 20, 2017 at 1:31:22 PM UTC-6, Javier Távara wrote:
>>
>> What errors are you getting?
>>
>> Check your Tomcat and DSpace logs.
>>
>> El lunes, 20 de febrero de 2017, 14:28:06 (UTC-5), Jeff Mitchell escribió:
>>>
>>> Restoring from backup didn't change anything.  Not sure what the issue 
>>> is as it was working on Thursday for sure.
>>>
>>

-- 
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: No website display

[Javier Távara]

What errors are you getting?

Check your Tomcat and DSpace logs.

El lunes, 20 de febrero de 2017, 14:28:06 (UTC-5), Jeff Mitchell escribió:
>
> Restoring from backup didn't change anything.  Not sure what the issue is 
> as it was working on Thursday for sure.
>

-- 
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] Re: Handle server created completely new identifiers

[Javier Távara]

OK, the handle table has two columns: handle_id and handle. The content of 
these columns should be equal, this way "update-handle-prefix" script 
creates new handles according to the handle_id.

The problem with my database was the handle column differs from handle_id 
column and when running the script, it created a mess :(

Can I update handle_id safely according to my metadata? Should I only 
update the handle column?

Javier T.

El lunes, 20 de febrero de 2017, 12:25:05 (UTC-5), Javier Távara escribió:
>
> Hi. 
> Today I saw some old items have a new handle. No idea why this happened 
> and this is breaking search results. I suppose this happened some days ago 
> when we configured the Handle server with the prefix assigned by CNRI. 
>
> So, example.com/handle/123456789/*1196* (this is in dc.identifier.uri) 
> now has https://hdl.handle.net/xxx/*560*
>
> Can we query the database to update the handles according to the 
> identifier in dc.identifier.uri? Will this brake something more? 
>
> Any advice?
> Thank you.
>
> Javier T.
>

-- 
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] Re: No website display

[Javier Távara]

Did you checked your firewall configuration?

El lunes, 20 de febrero de 2017, 12:23:15 (UTC-5), Jeff Mitchell escribió:
>
> Hello All,
>
>
> Last week we had a VMHost crap out.  I was able to move the vm of dspace 
> to another host.  I thought everything was good but now my site won't 
> display at all.  I have checked IP, Apache, Tomcat services but nothing 
> displays.  I can ping the ip address internally and externally both 
> resolve. However, no site will display.
>
> I'm not sure which logs to look at so if someone could kick me in the 
> right direction that would greatly be appreciated.
>
> Thanks,
>
> Jeff
>
>

-- 
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] Handle server created completely new identifiers

[Javier Távara]

Hi.
Today I saw some old items have a new handle. No idea why this happened and 
this is breaking search results. I suppose this happened some days ago when we 
configured the Handle server with the prefix assigned by CNRI.

So, example.com/handle/123456789/1196 (this is in dc.identifier.uri) now has 
https://hdl.handle.net/xxx/560

Can we query the database to update the handles according to the identifier in 
dc.identifier.uri? Will this brake something more?

Any advice?
Thank you.

Javier T.

-- 
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] Right way to fill dc.type

[Javier Távara]

Hello.
We are required to follow some OpenAIRE guidelines, so we have to fill the 
dc.type field with the info:eu-repo namespace to be read from other 
repositories via OAI.

dc.type = info:eu-repo/semantics/article
https://guidelines.openaire.eu/en/latest/literature/field_publicationtype.html

We put this URI directly in the metadata. However, every visitor would not 
understand easily this when playing with the faceted search.

Is there a way to fill this fields in native language and transform to URI just 
for OAI?

Can we show the translated word (user readable) in Discovery?

Thank you.

Javier T.

-- 
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] Re: Elastic Statistics Data Loss Suddenly

[Javier Távara]

You can use dspace.log files to recover 
statistics 
https://wiki.duraspace.org/display/DSDOC5x/Elasticsearch+Usage+Statistics

Something similar it's happening to me, but with SOLR.

El lunes, 23 de enero de 2017, 2:22:16 (UTC-5), Yusuf Khalil escribió:
>
> Dspace version is 5.4
>

-- 
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] Re: Statistics disappeared

[Javier Távara]

Sorry. I'm using DSpace 5.5 with Solr statistics.

El lunes, 30 de enero de 2017, 12:44:34 (UTC-5), Javier Távara escribió:
>
> Today, I've realized my statistics disappeared :(
>
> I think I'm just seeing the data for this year. This could be related to 
> this https://groups.google.com/forum/#!topic/dspace-tech/MrfwyQuoDgo
>
> How can I debug the problem?
>

-- 
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] Statistics disappeared

[Javier Távara]

Today, I've realized my statistics disappeared :(

I think I'm just seeing the data for this year. This could be related to 
this https://groups.google.com/forum/#!topic/dspace-tech/MrfwyQuoDgo

How can I debug the problem?

-- 
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] SOLR: Core with name 'statistics-xxxx' already exists

[Javier Távara]

Hello.
Today I saw my search results aren't being updated, so I decided to see the 
logs and I found:

INFO org.apache.solr.handler.admin.CoreAdminHandler @ core create command 
instanceDir=statistics&name=statistics-2011&action=CREATE&dataDir=/home/
dspace/installation/solr/statistics-2011/data&wt=javabin&version=2

WARN org.apache.solr.handler.admin.CoreAdminHandler @ Creating a core with 
existing name is not allowed 

ERROR org.apache.solr.core.SolrCore @ org.apache.solr.common.SolrException: 
Core with name 'statistics-2011' already exists. 

INFO org.apache.solr.servlet.SolrDispatchFilter @ [admin] webapp=null path=
/admin/cores params={instanceDir=statistics&name=statistics-2011&action=
CREATE&dataDir=/home/dspace/installation/solr/statistics-2011/data&wt=
javabin&version=2} status=500 QTime=1 

ERROR org.apache.solr.servlet.SolrDispatchFilter @ null:org.apache.solr.
common.SolrException: Core with name 'statistics-2011' already exists.

The message I'm getting:

Creating a core with existing name is not allowed.
Core with name 'statistics-2011' already exists.

According to the dates recorded, this is happening when 2 cron jobs are 
running:

 # Cleanup Web Spiders from DSpace Statistics Solr Index at 01:00 every day
# NOTE: ONLY NECESSARY IF YOU ARE RUNNING SOLR STATISTICS
# (This removes any known web spiders from your usage statistics)
0 1 * * * $DSPACE/bin/dspace stats-util -i
 
# Re-Optimize DSpace Statistics Solr Index at 01:30 every day
# NOTE: ONLY NECESSARY IF YOU ARE RUNNING SOLR STATISTICS 
# (This ensures that the Statistics Solr Index is re-optimized for better 
performance)
30 1 * * * $DSPACE/bin/dspace stats-util -o

And it started the first day of this year (because of dspace stats-util -s 
maybe).

And don't know if this will resolve my original problem (search results 
aren't being updated), but maybe it's a start.

I hope someone can help me.
Thanks!
Javier.

-- 
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] Changing cc.license.name configuration property

[Javier Távara]

Hello
I see this option:

# Metadata field to hold CC license name of selected license (if defined)
# NB: XMLUI presentation code expects 'dc.rights' to hold CC data. If you 
change
# this to another field, please consult documentation on how to update UI 
configuration
cc.license.name = dc.rights

I want to change it to dc.rights.license but I can't find any documentation 
about the XMLUI change I have to make.

Can someone clarify this, please?

Thank you.
Javier T.

-- 
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] Embargo not working after upgrade

[Javier Távara]

Hello, some time ago I updated a repository from 3.2 to 5.5 and everything 
was working fine until I tested some embargoed items.

I use this config:

 Embargo Settings 
# DC metadata field to hold the user-supplied embargo terms
embargo.field.terms = dc.embargo.terms

# DC metadata field to hold computed "lift date" of embargo
embargo.field.lift = dc.embargo.lift

# string in terms field to indicate indefinite embargo
embargo.terms.open = forever

# implementation of embargo setter plugin - replace with local 
implementation if applicable
plugin.single.org.dspace.embargo.EmbargoSetter = org.dspace.embargo.
DefaultEmbargoSetter

# implementation of embargo lifter plugin - - replace with local 
implementation if applicable
plugin.single.org.dspace.embargo.EmbargoLifter = org.dspace.embargo.
DefaultEmbargoLifter

Then I realized the dc.embargo.lift field it's computed correctly but *the 
bitstreams are still available to everyone.*

Running ./dspace embargo-lifter -a  manually seems to apply the 
restrictions.

I think this is not the correct behavior. How to do this automatically?

Thank you.
Javier T.

-- 
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] Email notification when registering item with certain dc.type

[Javier Távara]

Hello,
After registering items with the form or REST API, I would like to send 
mail notifications to multiple recipients, but only if the dc.type field 
contains the word "thesis".

I hope you can give me some ideas on how to implement this.

Thank you in advance.

-- 
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] Submission made via REST API does not trigger collection workflow approval process.

[Javier Távara]

Hello.
Is this the same behaviour in DSpace 5.5? Are REST submissions bypassing 
the collection's workflow?

El miércoles, 3 de agosto de 2016, 11:42:58 (UTC-5), Emilio Lorenzo 
escribió:
>
> Hi Martin, 
>
> Yes we detected that situation in some instances of Dspace 5.  I have just 
> submitted a JIRA issue  https://jira.duraspace.org/browse/DS-3281  and 
> tomorrow we expect to upload the changes we made to include the workflow.   
>
> Hope this helps.
>
> Best regards
>
> Emilio 
>
>
>
>
>
> El 01/08/2016 a las 15:20, Martin Walk escribió:
>
> Hello, 
>
> I investigated adding items via the REST API and noticed that they are 
> immediately added to the archive, bypassing the collection's workflow.
> Is there a configuration to change this behaviour?
> If not, are others aware of the fact and are there already efforts to 
> change the situation?
>
> Best regards, Martin.
>
>
>
> -- 
> 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...@googlegroups.com .
> To post to this group, send email to dspac...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/dspace-tech.
> 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.

[dspace-tech] Where to change community list tree

[Javier Távara]

Hello.
I'm using DSpace 5.5. I want to know where I can change the XSLT template 
for the ** item inside the 
Community list page (example.com/community-list). I want to add some 
classes according to their item counts.

I've seen the template communitySummaryList-DIM inside the 
community-list.xsl, but that's for the item content.

Thank you.
Javier T.

-- 
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] Re: virtualize

[Javier Távara]

Do you need help installing an hypervisor or taking backups for the 
transfer?

There should not be any difference when installing on a bare-metal server 
or virtual machine. Maybe you are going to notice a little performance 
degradation, but nothing to worry.

We use VMware ESX 5.5 for production. And VMware Fusion for testing.
In the next days I'll be testing Proxmox KVM.

For the transfer, read this 
https://wiki.duraspace.org/display/DSPACE/BackupRestore

El viernes, 23 de septiembre de 2016, 1:31:17 (UTC-5), Haimanot Birhanu 
escribió:
>
> How to Virtualize my dspace server, any one who have experience?
>

-- 
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] Re: virtualize

[Javier Távara]

Do you need help installing an hypervisor or taken backups for the transfer?

There should not be any difference when installing on a bare-metal server 
or virtual machine. Maybe you are going to notice a little performance 
degradation, but nothing to worry.

We use VMware ESX 5.5 for production. And VMware Fusion for testing.
In the next days I'll be testing Proxmox KVM.

For the transfer, read 
this https://wiki.duraspace.org/display/DSPACE/BackupRestore

El viernes, 23 de septiembre de 2016, 1:31:17 (UTC-5), Haimanot Birhanu 
escribió:
>
> How to Virtualize my dspace server, any one who have experience?
>

-- 
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] Better log management

[Javier Távara]

Tahnks Shaun. Thank you Ariel.
I will go for logrotate.

-- 
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: REST API metadata editing (DSpace 6)

[Javier Távara]

Good you got it fixed Ari.
Next time you can try Postman for testing your APIs. Postman can generate
also the cUrl code and make tests.

Javier T.

2016-08-17 0:45 GMT-05:00 Ari :

>
> Thanks for suggestion, Javier.
>
> However, I managed to find the problem. I had to add square brackets
> around JSON object:
> curl -X PUT -H "Content-Type: application/json" -d
> '[{"key":"dc.description.abstract", "value":"hello", "language":"no"}]' "
> http://dummy_dspace_address.com:8080/rest/items/c4c0-7e
> 11-4a18-bf94-8192275e50e4/metadata" -b  cookies.txt
>
>
> Here is a full procedure using CURL, if someone is interested (current
> documentation is misleading)
>
> 1. First, authenticate your self:
> curl --data "email=your.email&password=your_pass" http://
> your_dspace.com:8080/rest/login -c cookies.txt
>
>
> 2. Test that authentication was successful:
> curl  -H "Accept: application/json"  http://your_dspace.com:8080/r
> est/status -b cookies.txt
>
>
> - this should return something like this:
> {"okay":true,"authenticated":true,"email":"your.email","fullname":"ari ",
> "sourceVersion":null,"apiVersion":null}
>
>
> 3. And finally, make an edit:
> curl -X PUT -H "Content-Type: application/json" -d
> '[{"key":"dc.description.abstract", "value":"hello", "language":"no"}]' "
> http://dummy_dspace_address.com:8080/rest/items/c4c0-7e
> 11-4a18-bf94-8192275e50e4/metadata" -b  cookies.txt
>
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "DSpace Technical Support" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/to
> pic/dspace-tech/49KBEXeavyM/unsubscribe.
> To unsubscribe from this group and all its topics, 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.
>

-- 
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] Better log management

[Javier Távara]

Thanks Hilton.
Will this affect the statistics?


El miércoles, 24 de agosto de 2016, 2:38:30 (UTC-5), Hilton Gibson escribió:
>
> Hi J,
>
> Perhaps this will help: 
> http://wiki.lib.sun.ac.za/index.php/SUNScholar/Optimisations/Logs
>
> Cheers
>
> hg
>
> *Hilton Gibson*
> Stellenbosch University Library
> *http://orcid.org/-0002-2992-208X 
> <http://orcid.org/-0002-2992-208X>*
>
>
> On 24 August 2016 at 07:22, Javier Távara > 
> wrote:
>
>> Hello.
>> I want to know how to make a better management of DSpace, Cocoon and 
>> Tomcat logs, and which/why are those necessary to keep. (statistics?)
>> Last time I figured out there were 80GB in logs because of Cocoon.
>> I have DSpace 5.5 installed.
>>
>> Thank you very much.
>>
>> -- 
>> 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...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> 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.

[dspace-tech] Better log management

[Javier Távara]

Hello.
I want to know how to make a better management of DSpace, Cocoon and Tomcat 
logs, and which/why are those necessary to keep. (statistics?)
Last time I figured out there were 80GB in logs because of Cocoon.
I have DSpace 5.5 installed.

Thank you very much.

-- 
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: Cannont get a connectoin error

[Javier Távara]

Thanks Ariel. May I know for how many visitors are you trying this 
configuration?
On mar, ago. 23, 2016 at 11:03 a.m., Ariel Lira  wrote:
Hi Jose, we had those exceptions too on 5.x and previous versions. I think it 
is caused by idle connections. Try limiting idle connections and increasing 
maxconnections. For example:
# Maximum number of DB connections in pool
db.maxconnections = 50

# Maximum time to wait before giving up if all connections in pool are busy 
(milliseconds)
db.maxwait = 3000

# Maximum number of idle connections in pool (-1 = unlimited)
db.max idle = 30
In dspace 6(rc2) this issue seems fixed. Perhaps because Hibernate is closing 
all connections as expected. Regards, Ariel

El jueves, 31 de marzo de 2016, 11:25:00 (UTC-3), Jose Blanco escribió: I"m on 
dspace 5.1 and I've noticed this error in the log file
2016-03-30 10:42:06,450 ERROR org.dspace.storage.rdbms.DatabaseManager @ SQL 
connection Error -

org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool error 
Timeout waiting for idle object

at 
org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:114)

at 
org.dspace.storage.rdbms.DatabaseManager.getConnection(DatabaseManager.java:637)

at org.dspace.core.Context.init(Context.java:124)

at org.dspace.core.Context.(Context.java:98)

I searched and found this:
https://jira.duraspace.org/browse/DS-2563 
[https://jira.duraspace.org/browse/DS-2563]

I wonder if I should try to apply the patch shown here or is there a better way 
to deal with this.
Thank you!
Jose

--
You received this message because you are subscribed to a topic in the Google 
Groups "DSpace Technical Support" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/dspace-tech/A5IFDmJ74Yk/unsubscribe 
[https://groups.google.com/d/topic/dspace-tech/A5IFDmJ74Yk/unsubscribe] .
To unsubscribe from this group and all its topics, send an email to 
dspace-tech+unsubscr...@googlegroups.com 
[dspace-tech+unsubscr...@googlegroups.com] .
To post to this group, send email to dspace-tech@googlegroups.com 
[dspace-tech@googlegroups.com] .
Visit this group at https://groups.google.com/group/dspace-tech 
[https://groups.google.com/group/dspace-tech] .
For more options, visit https://groups.google.com/d/optout 
[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.

[dspace-tech] Re: Cannont get a connectoin error

[Javier Távara]

Hi. I'm using DSpace 5.5 and I'm seeing the same problem. I thought 
PostgreSQL was the problem but I restarted Tomcat and it works fine now. 
It's the second time after two weeks.
Any ideas?

2016-08-21 08:37:11,318 ERROR org.dspace.storage.rdbms.DatabaseManager @ 
SQL connection Error - 
org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool 
error Timeout waiting for idle object
 at org.apache.commons.dbcp.PoolingDataSource.getConnection(
PoolingDataSource.java:114)
 at org.dspace.storage.rdbms.DatabaseManager.getConnection(DatabaseManager.
java:634)
 at org.dspace.core.Context.init(Context.java:121)
 at org.dspace.core.Context.(Context.java:95)
 at org.dspace.app.xmlui.utils.ContextUtil.obtainContext(ContextUtil.java:89
)
 at org.dspace.app.xmlui.utils.ContextUtil.obtainContext(ContextUtil.java:54
)
 at org.dspace.app.xmlui.utils.HandleUtil.obtainHandle(HandleUtil.java:86)
 at org.dspace.app.xmlui.cocoon.ThemeMatcher.match(ThemeMatcher.java:57)
 at org.apache.cocoon.sitemap.impl.DefaultExecutor.invokeMatcher(
DefaultExecutor.java:68)
 at org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(
MatchNode.java:71)
 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.process
(ConcreteTreeProcessor.java:171)
 at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(
TreeProcessor.java:247)
 at org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(
MountNode.java:117)
 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.process
(ConcreteTreeProcessor.java:171)
 at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(
TreeProcessor.java:247)
 at org.apache.cocoon.servlet.RequestProcessor.process(RequestProcessor.java
:351)
 at org.apache.cocoon.servlet.RequestProcessor.service(RequestProcessor.java
:169)
 at org.apache.cocoon.sitemap.SitemapServlet.service(SitemapServlet.java:84)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
 at org.apache.cocoon.servletservice.ServletServiceContext$PathDispatcher.
forward(ServletServiceContext.java:468)
 at org.apache.cocoon.servletservice.ServletServiceContext$PathDispatcher.
forward(ServletServiceContext.java:443)
 at org.apache.cocoon.servletservice.spring.
ServletFactoryBean$ServiceInterceptor.invoke(ServletFactoryBean.java:264)
 at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
ReflectiveMethodInvocation.java:172)
 at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(
JdkDynamicAopProxy.java:202)
 at com.sun.proxy.$Proxy83.service(Unknown Source)
 at org.dspace.springmvc.CocoonView.render(CocoonView.java:113)
 at org.springframework.web.servlet.DispatcherServlet.render(
DispatcherServlet.java:1180)
 at org.springframework.web.servlet.DispatcherServlet.doDispatch(
DispatcherServlet.java:950)
 at org.springframework.web.servlet.DispatcherServlet.doService(
DispatcherServlet.java:852)
 at org.springframework.web.servlet.FrameworkServlet.processRequest(
FrameworkServlet.java:882)
 at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.
java:778)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:622)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
ApplicationFilterChain.java:230)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(
ApplicationFilterChain.java:165)
 at org.dspace.app.xmlui.cocoon.SetCharacterEncodingFilter.doFilter(
SetCharacterEncodingFilter.java:111)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
ApplicationFilterChain.java:192)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(
ApplicationFilterChain.java:165)
 at org.dspace.app.xmlui.cocoon.DSpaceCocoonServletFilter.doFilter(
DSpaceCocoonServletFilter.java:274)
 at org.apache.catalina.core.Appl

[dspace-tech] REST API metadata editing (DSpace 6)

[Javier Távara]

My mistake. I got confused with the Content-Type header, which you are already 
sending. 

-- 
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] REST API metadata editing (DSpace 6)

[Javier Távara]

Try sending "Accept: application/json" header. 

-- 
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] REST Bitstream upload with no sequenceId

[Javier Távara]

Hello,
I'm testing the upload process from DSpace 5.5 API, and I've noticed the 
all bitstreams have the property sequenceId equals to -1.
Also, when using .docx files the format is set to "Unknown", while when 
using the web form is detected correctly.

Is it normal?


Thank you.

-- 
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] Apache HTTP (mod_proxy) and Solr unrestricted

[Javier Távara]

Thank you very much Andrea.
I was using ProxyPassReverse / http://localhost:8080/ instead of ajp:// and 
the right port.

Everything it's OK now.



El martes, 19 de julio de 2016, 20:37:25 (UTC-5), Andrea Schweer escribió:
>
> Hi, 
>
> On 07/20/2016 12:31 PM, Javier Távara wrote: 
> > Hello. 
> > I installed DSpace 5.5 and because I want to run on port 80, I've 
> > configured Apache HTTP with mod_proxy. 
> > When entering the URL http://x.x.x/solr I see the admin (on port 8080 
> > it's restricted). How can I set the restriction again? 
>
> This probably depends on exactly how you have set things up, in other 
> words, you probably need to give us some more information. There are 
> instructions for setting up Apache HTTPD in front of Tomcat for DSpace 
> here: 
>
> https://wiki.duraspace.org/display/DSDOC5x/Installing+DSpace#InstallingDSpace-UsingSSLonApacheHTTPDinfrontofTomcat(runningonports80and443)
>  
>
> If you've set up things differently from those instructions, perhaps (a) 
> try changing your set-up to match the instructions, and/or (b) let us 
> know in which ways your set-up differs from the recommended one. In 
> particular, do you have reasons for using mod_proxy directly rather than 
> mod_ajp? 
>
> cheers, 
> Andrea 
>
> -- 
> Dr Andrea Schweer 
> Lead Software Developer, ITS Information Systems 
> The University of Waikato, Hamilton, New Zealand 
> +64-7-837 9120 
>
>

-- 
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] Re: Hide "View more" in homepage

[Javier Távara]

Hola!

You can do that changing the XSLT or CSS files.

The easy way: CSS. Put the following lines in 
/dspace-xmlui/src/main/webapp/themes/Mirage/lib/css/style.css. 
Then rebuild.

.aspect_discovery_SiteRecentSubmissions_p_recent-submission-view-more {
display: none;
}


Although it is better if you copy the file to 
/dspace/modules/xmlui/src/main/webapp/themes/Mirage/lib/css/style.css

This way it's easier when you want to upgrade.

More info: https://wiki.duraspace.org/display/DSDOC5x/Advanced+Customisation



El jueves, 21 de julio de 2016, 5:29:27 (UTC-5), Mariangels escribió:
>
>
> Hola,
>
> I would like to hide, if is possible, the link "View more" only in the 
> homepage.
> Is it possible?
>
> We have DSpace 5.5 and xmlui Mirage theme.
>
> Thanks in advance.
>

-- 
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] Apache HTTP (mod_proxy) and Solr unrestricted

[Javier Távara]

Hello.
I installed DSpace 5.5 and because I want to run on port 80, I've 
configured Apache HTTP with mod_proxy.
When entering the URL http://x.x.x/solr I see the admin (on port 8080 it's 
restricted). How can I set the restriction again?

I've put *RemoteIPHeader X-Forwarded-For *in the Virtual Host trying to 
send the header but it's not working. Also, in dspace.cfg I have set 
useProxies to true.

Thank you.

-- 
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] Re: Upgrade problems with forms.xsl

[Javier Távara]

Any solution?
Is this theme not compatible anymore?

El lunes, 27 de junio de 2016, 4:30:49 (UTC-5), Stefanie Behnke escribió:
>
> Dear all,
>
> after upgrading dsapce from version 3.1 to 5.5 and restarting tomcat I got 
> the following error message. (I am using xmlui with Mirage theme, the theme 
> was not changed.)
>
> Any help is appreciated.
>
> Best regards
> Stefanie
>
> Error message:
>
> javax.xml.transform.TransformerException: ElemTemplateElement error: 
> addLookupButtonAuthor
> context:/jndi:/localhost/themes/Mirage_EG/../dri2xhtml-alt/core/forms.xsl 
> - 304:69
>
> Cocoon stacktrace [show]
>
> Java stacktrace [show]
>
> Java full stacktrace [hide]
>
> org.apache.cocoon.ProcessingException: Unable to get transformer handler 
> for jndi:/localhost/themes/Mirage_EG/Mirage for Eurographics.xsl
> at [TransformerException] - 
> jndi:/localhost/themes/Mirage_EG/../dri2xhtml-alt/core/forms.xsl:304:69
> at  - 
> jndi:/localhost/themes/Mirage_EG/sitemap.xmap:164:34
> at  - 
> jndi:/localhost/themes/Mirage_EG/sitemap.xmap:158:33
> at  - 
> jndi:/localhost/themes/Mirage_EG/sitemap.xmap:153:51
> at  - 
> jndi:/localhost/themes/Mirage_EG/sitemap.xmap:140:55
> at  - 
> jndi:/localhost/themes/Mirage_EG/sitemap.xmap:135:55
> at  - 
> jndi:/localhost/themes/Mirage_EG/sitemap.xmap:126:55
> at  - 
> jndi:/localhost/themes/Mirage_EG/sitemap.xmap:120:55
> at  - jndi:/localhost/themes/Mirage_EG/sitemap.xmap:117:28
> at  - jndi:/localhost/themes/themes.xmap:33:45
> at  - 
> jndi:/localhost/themes/themes.xmap:32:35
> at  - jndi:/localhost/sitemap.xmap:697:94
> at 
> org.apache.cocoon.transformation.TraxTransformer.setup(TraxTransformer.java:315)
> at sun.reflect.GeneratedMethodAccessor70.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at 
> org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
> at com.sun.proxy.$Proxy109.setup(Unknown Source)
> at 
> org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.setupPipeline(AbstractProcessingPipeline.java:356)
> at 
> org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.setupPipeline(AbstractCachingProcessingPipeline.java:710)
> at 
> org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.preparePipeline(AbstractProcessingPipeline.java:466)
> at 
> org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process(AbstractProcessingPipeline.java:411)
> 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.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
> at com.sun.proxy.$Proxy106.process(Unknown Source)
> at 
> org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.invoke(SerializeNode.java:147)
> 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.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.process(ConcreteTreeProcessor.java:171)
> at 
> org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:247)
> at 
> org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:117)
> 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.PipelineNode.invoke(PipelineNode.java:143)
> at 
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
>