[Dspace-tech] Problem with bitstream upload

2014-03-31 Thread Stefanie Behnke
Dear all,

I am using Dspace 3.1 with jspui and want to upload a bitstream (zip file) to 
an existing item. That results in an Internal System Error.

Can anyone give me a hint, what went wrong?

thanking you in advance
Stefanie


--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette


Re: [Dspace-tech] Problem with bitstream upload

2014-03-31 Thread Anja Le Blanc
Hi Stefanie,

That is really not a lot of information about your problem. Can you 
check for error messages in your DSpace and or Tomcat logs?

Regards,

Anja


On 31/03/2014 09:52, Stefanie Behnke wrote:
 Dear all,

 I am using Dspace 3.1 with jspui and want to upload a bitstream (zip file) to 
 an existing item. That results in an Internal System Error.

 Can anyone give me a hint, what went wrong?

 thanking you in advance
 Stefanie


 --
 ___
 DSpace-tech mailing list
 DSpace-tech@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-tech
 List Etiquette: 
 https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette



--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette


Re: [Dspace-tech] update from dspace1.7.2 to 3.2

2014-03-31 Thread Anja Le Blanc
You can update the database by running the sql scripts provided with the 
new version of DSpace - just run them in order.

Anja


On 28/03/2014 17:27, ʚïɞ...liss ...εïз wrote:
 Hi all,

 is there some way to update the db in dspace 1.7.2 to 3.2 without to
 have to make the updating the dspace software?

 I am working with the dspace 1.72 my db is 30GB on windows but now I
 want migrate to Debian but install the version 3.2 of dspace

 thanks.


 --



 ___
 DSpace-tech mailing list
 DSpace-tech@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-tech
 List Etiquette: 
 https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette


--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

[Dspace-tech] SQL Query Question

2014-03-31 Thread Sean Carte
I'm trying to extract data from the metadatavalue table, including rows
where a particular metadata_field may not exist, but my attempts using LEFT
OUTER JOINs lead to these rows being omitted.

For example:

dspace= SELECT DISTINCT mv1.item_id, mv1.text_value AS date,
mv2.text_value as type
FROM metadatavalue AS mv1
LEFT JOIN metadatavalue AS mv2 ON mv1.item_id = mv2.item_id
LEFT JOIN metadatavalue AS mv3 ON mv1.item_id = mv3.item_id
WHERE mv1.metadata_field_id = 12 AND mv1.text_value LIKE '2007-11-12T%Z'
AND mv2.metadata_field_id = 66 AND mv2.text_value = 'Thesis'
ORDER BY mv1.item_id;
 item_id | date |  type
-+--+
 163 | 2007-11-12T09:58:28Z | Thesis
 164 | 2007-11-12T09:59:31Z | Thesis
 165 | 2007-11-12T09:59:40Z | Thesis
 166 | 2007-11-12T13:31:43Z | Thesis
 168 | 2007-11-12T13:32:02Z | Thesis
 169 | 2007-11-12T13:32:09Z | Thesis
 172 | 2007-11-12T13:32:30Z | Thesis
(7 rows)

... but:

dspace= SELECT DISTINCT mv1.item_id, mv1.text_value AS date,
mv2.text_value as type
FROM metadatavalue AS mv1
LEFT JOIN metadatavalue AS mv2 ON mv1.item_id = mv2.item_id
LEFT JOIN metadatavalue AS mv3 ON mv1.item_id = mv3.item_id
WHERE mv1.metadata_field_id = 12 AND mv1.text_value LIKE '2007-11-12T%Z'
AND mv2.metadata_field_id = 66 AND mv2.text_value = 'Thesis'
AND mv3.metadata_field_id = 75
ORDER BY mv1.item_id;
 item_id | date |  type
-+--+
 163 | 2007-11-12T09:58:28Z | Thesis
(1 row)

If I had null values corresponding to metadata_field_id = 75, I would have
got all my records, but where there is no metadata_field_id 75, I get zero
rows.

Is there a way to do this?

Sean
--
--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Re: [Dspace-tech] Problem with bitstream upload

2014-03-31 Thread Stefanie Behnke
Dear Anja,

error message on the screen:
Internal System Error

The system has experienced an internal error. Please try to do what you were
doing again, and if the problem persists, please contact us so we can fix
the problem.

--
from the dspace log:

2014-03-31 14:41:52,827 INFO  org.dspace.authenticate.LDAPAuthentication @
anonymous:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=129.27.218.38:
auth:attempting trivial auth of user=eg-supp...@eg.org
2014-03-31 14:41:52,953 WARN  org.dspace.authenticate.LDAPAuthentication @
anonymous:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=129.27.218.38:
ldap_authentication:type=failed_auth
javax.naming.AuthenticationException\colon; [LDAP\colon; error code 49 -
Invalid Credentials]
2014-03-31 14:41:52,953 INFO  org.dspace.authenticate.PasswordAuthentication
@
anonymous:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=129.27.218.38:
authenticate:attempting password auth of user=eg-supp...@eg.org
2014-03-31 14:41:52,973 INFO  org.dspace.authenticate.PasswordAuthentication
@
eg-supp...@eg.org:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=129.27
.218.38:authenticate:type=PasswordAuthentication
2014-03-31 14:41:52,976 INFO  org.dspace.app.webui.servlet.PasswordServlet @
eg-supp...@eg.org:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=129.27
.218.38:login:type=explicit
2014-03-31 14:41:53,003 INFO  org.dspace.app.webui.servlet.MyDSpaceServlet @
eg-supp...@eg.org:session_id=03F65560962C60325F4784644FF62FD5:ip_addr=129.27
.218.38:view_mydspace:
2014-03-31 14:42:22,390 INFO  org.dspace.content.Bitstream @
eg-supp...@eg.org:session_id=03F65560962C60325F4784644FF62FD5:ip_addr=129.27
.218.38:update_bitstream:bitstream_id=6477
2014-03-31 14:42:22,390 INFO  org.dspace.content.Bundle @
eg-supp...@eg.org:session_id=03F65560962C60325F4784644FF62FD5:ip_addr=129.27
.218.38:update_bundle:bundle_id=4273
2014-03-31 14:42:22,393 INFO  org.dspace.content.Item @
eg-supp...@eg.org:session_id=03F65560962C60325F4784644FF62FD5:ip_addr=129.27
.218.38:update_item:item_id=4282
2014-03-31 14:42:31,039 WARN
org.dspace.app.webui.servlet.InternalErrorServlet @
:session_id=03F65560962C60325F4784644FF62FD5:internal_error:-- URL Was:
http://129.27.218.243:8080/jspui/tools/edit-item
-- Method: POST
-- Parameters were:

java.io.IOException: No such file or directory
at java.io.UnixFileSystem.createFileExclusively(Native Method)
at java.io.File.createNewFile(File.java:947)
at
edu.sdsc.grid.io.local.LocalFile.createNewFile(LocalFile.java:486)
at
org.dspace.storage.bitstore.BitstreamStorageManager.store(BitstreamStorageMa
nager.java:300)
at org.dspace.content.Bitstream.create(Bitstream.java:205)
at org.dspace.content.Bundle.createBitstream(Bundle.java:384)
at
org.dspace.app.webui.servlet.admin.EditItemServlet.processUploadBitstream(Ed
itItemServlet.java:857)
at
org.dspace.app.webui.servlet.admin.EditItemServlet.doDSPost(EditItemServlet.
java:160)
at
org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java
:115)
at
org.dspace.app.webui.servlet.DSpaceServlet.doPost(DSpaceServlet.java:73)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:210)
at
org.dspace.app.webui.filter.RegisteredOnlyFilter.doFilter(RegisteredOnlyFilt
er.java:66)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:210)
at
org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServ
letFilter.java:78)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:225)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:123)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase
.java:472)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168
)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Proce
ssor.java:1001)
 

[Dspace-tech] Runtime-optional submission step?

2014-03-31 Thread Adrian Wiechec
Hello!

I'm looking for ideas on how one would go about making a submission step
runtime-optional. Namely, in our repository, as we collect mainly metadata
(actual file submissions will be rare, at least initially), we would like
the license step to appear only if any file has been submitted in upload
file step. From some initial browsing I think it's probably doable by
checking bitstreams.length - but am not sure how to turn a step into
non-interactive one.

Or perhaps I should devise an InitialQuestions step asking if you want to
submit a file, or just the metadata. The file upload and license step would
only then appear when needed - still no idea how to do that dynamically.

Any ideas/pointers would be greatly appreciated.

TIA,
rag
--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Re: [Dspace-tech] Problem with bitstream upload

2014-03-31 Thread Anja Le Blanc
Hi Stefanie,

Well, the error simply said that it can't create a file.
At that point the code tries to create a file in the current assetstore.
Could you check in your dspace.cfg
a) whether assetstore.incoming is set
b) the location of assetstore.dir or asetstore.dir.[the number from a)]

Check the permission of that directory tree -- the tomcat user must be 
able to access that.

You could also switch to log4j to debug mode for package 
org.dspace.storage.bitstore -- this would produce a line in dspace.log 
with the info of where it tries do create the file:
log.debug(Local filename for  + sInternalId +  is 
+bufFilename.toString());

That is all I could think of for that.

Regards,
Anja


On 31/03/2014 13:56, Stefanie Behnke wrote:
 Dear Anja,

 error message on the screen:
 Internal System Error

 The system has experienced an internal error. Please try to do what you were
 doing again, and if the problem persists, please contact us so we can fix
 the problem.

 --
 from the dspace log:

 2014-03-31 14:41:52,827 INFO  org.dspace.authenticate.LDAPAuthentication @
 anonymous:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=129.27.218.38:
 auth:attempting trivial auth of user=eg-supp...@eg.org
 2014-03-31 14:41:52,953 WARN  org.dspace.authenticate.LDAPAuthentication @
 anonymous:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=129.27.218.38:
 ldap_authentication:type=failed_auth
 javax.naming.AuthenticationException\colon; [LDAP\colon; error code 49 -
 Invalid Credentials]
 2014-03-31 14:41:52,953 INFO  org.dspace.authenticate.PasswordAuthentication
 @
 anonymous:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=129.27.218.38:
 authenticate:attempting password auth of user=eg-supp...@eg.org
 2014-03-31 14:41:52,973 INFO  org.dspace.authenticate.PasswordAuthentication
 @
 eg-supp...@eg.org:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=129.27
 .218.38:authenticate:type=PasswordAuthentication
 2014-03-31 14:41:52,976 INFO  org.dspace.app.webui.servlet.PasswordServlet @
 eg-supp...@eg.org:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=129.27
 .218.38:login:type=explicit
 2014-03-31 14:41:53,003 INFO  org.dspace.app.webui.servlet.MyDSpaceServlet @
 eg-supp...@eg.org:session_id=03F65560962C60325F4784644FF62FD5:ip_addr=129.27
 .218.38:view_mydspace:
 2014-03-31 14:42:22,390 INFO  org.dspace.content.Bitstream @
 eg-supp...@eg.org:session_id=03F65560962C60325F4784644FF62FD5:ip_addr=129.27
 .218.38:update_bitstream:bitstream_id=6477
 2014-03-31 14:42:22,390 INFO  org.dspace.content.Bundle @
 eg-supp...@eg.org:session_id=03F65560962C60325F4784644FF62FD5:ip_addr=129.27
 .218.38:update_bundle:bundle_id=4273
 2014-03-31 14:42:22,393 INFO  org.dspace.content.Item @
 eg-supp...@eg.org:session_id=03F65560962C60325F4784644FF62FD5:ip_addr=129.27
 .218.38:update_item:item_id=4282
 2014-03-31 14:42:31,039 WARN
 org.dspace.app.webui.servlet.InternalErrorServlet @
 :session_id=03F65560962C60325F4784644FF62FD5:internal_error:-- URL Was:
 http://129.27.218.243:8080/jspui/tools/edit-item
 -- Method: POST
 -- Parameters were:

 java.io.IOException: No such file or directory
   at java.io.UnixFileSystem.createFileExclusively(Native Method)
   at java.io.File.createNewFile(File.java:947)
   at
 edu.sdsc.grid.io.local.LocalFile.createNewFile(LocalFile.java:486)
   at
 org.dspace.storage.bitstore.BitstreamStorageManager.store(BitstreamStorageMa
 nager.java:300)
   at org.dspace.content.Bitstream.create(Bitstream.java:205)
   at org.dspace.content.Bundle.createBitstream(Bundle.java:384)
   at
 org.dspace.app.webui.servlet.admin.EditItemServlet.processUploadBitstream(Ed
 itItemServlet.java:857)
   at
 org.dspace.app.webui.servlet.admin.EditItemServlet.doDSPost(EditItemServlet.
 java:160)
   at
 org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java
 :115)
   at
 org.dspace.app.webui.servlet.DSpaceServlet.doPost(DSpaceServlet.java:73)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
   at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
 FilterChain.java:305)
   at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
 ain.java:210)
   at
 org.dspace.app.webui.filter.RegisteredOnlyFilter.doFilter(RegisteredOnlyFilt
 er.java:66)
   at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
 FilterChain.java:243)
   at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
 ain.java:210)
   at
 org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServ
 letFilter.java:78)
   at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
 FilterChain.java:243)
   at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
 ain.java:210)
   at
 

Re: [Dspace-tech] Problem with bitstream upload

2014-03-31 Thread Stefanie Behnke
Dear Anja,

thanks for your interest.

a) assetstore.incoming is not set, so I think it is 0 (zero) and corresponds
to the 'assetstore.dir' above: 
# Asset (bitstream) store number 0 (zero)
assetstore.dir = ${dspace.dir}/assetstore

b) the owner of that directory is tomcat7

 You could also switch to log4j to debug mode for package
org.dspace.storage.bitstore
How can I do this?

Thanks again for your help.

Best regards
Stefanie



-Ursprüngliche Nachricht-
Von: Anja Le Blanc [mailto:anja.lebl...@manchester.ac.uk] 
Gesendet: Montag, 31. März 2014 15:44
An: Stefanie Behnke; dspace-tech@lists.sourceforge.net
Betreff: Re: AW: [Dspace-tech] Problem with bitstream upload

Hi Stefanie,

Well, the error simply said that it can't create a file.
At that point the code tries to create a file in the current assetstore.
Could you check in your dspace.cfg
a) whether assetstore.incoming is set
b) the location of assetstore.dir or asetstore.dir.[the number from
a)]

Check the permission of that directory tree -- the tomcat user must be able
to access that.

You could also switch to log4j to debug mode for package
org.dspace.storage.bitstore -- this would produce a line in dspace.log with
the info of where it tries do create the file:
log.debug(Local filename for  + sInternalId +  is
+bufFilename.toString());

That is all I could think of for that.

Regards,
Anja


On 31/03/2014 13:56, Stefanie Behnke wrote:
 Dear Anja,

 error message on the screen:
 Internal System Error

 The system has experienced an internal error. Please try to do what 
 you were doing again, and if the problem persists, please contact us 
 so we can fix the problem.

 --
 from the dspace log:

 2014-03-31 14:41:52,827 INFO  
 org.dspace.authenticate.LDAPAuthentication @

anonymous:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=129.27.218.38:
 auth:attempting trivial auth of user=eg-supp...@eg.org
 2014-03-31 14:41:52,953 WARN  
 org.dspace.authenticate.LDAPAuthentication @

anonymous:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=129.27.218.38:
 ldap_authentication:type=failed_auth
 javax.naming.AuthenticationException\colon; [LDAP\colon; error code 49 
 - Invalid Credentials]
 2014-03-31 14:41:52,953 INFO  
 org.dspace.authenticate.PasswordAuthentication
 @

anonymous:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=129.27.218.38:
 authenticate:attempting password auth of user=eg-supp...@eg.org
 2014-03-31 14:41:52,973 INFO  
 org.dspace.authenticate.PasswordAuthentication
 @
 eg-supp...@eg.org:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=
 129.27 .218.38:authenticate:type=PasswordAuthentication
 2014-03-31 14:41:52,976 INFO  
 org.dspace.app.webui.servlet.PasswordServlet @
 eg-supp...@eg.org:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=
 129.27
 .218.38:login:type=explicit
 2014-03-31 14:41:53,003 INFO  
 org.dspace.app.webui.servlet.MyDSpaceServlet @
 eg-supp...@eg.org:session_id=03F65560962C60325F4784644FF62FD5:ip_addr=
 129.27
 .218.38:view_mydspace:
 2014-03-31 14:42:22,390 INFO  org.dspace.content.Bitstream @
 eg-supp...@eg.org:session_id=03F65560962C60325F4784644FF62FD5:ip_addr=
 129.27
 .218.38:update_bitstream:bitstream_id=6477
 2014-03-31 14:42:22,390 INFO  org.dspace.content.Bundle @
 eg-supp...@eg.org:session_id=03F65560962C60325F4784644FF62FD5:ip_addr=
 129.27
 .218.38:update_bundle:bundle_id=4273
 2014-03-31 14:42:22,393 INFO  org.dspace.content.Item @
 eg-supp...@eg.org:session_id=03F65560962C60325F4784644FF62FD5:ip_addr=
 129.27
 .218.38:update_item:item_id=4282
 2014-03-31 14:42:31,039 WARN
 org.dspace.app.webui.servlet.InternalErrorServlet @
 :session_id=03F65560962C60325F4784644FF62FD5:internal_error:-- URL Was:
 http://129.27.218.243:8080/jspui/tools/edit-item
 -- Method: POST
 -- Parameters were:

 java.io.IOException: No such file or directory
   at java.io.UnixFileSystem.createFileExclusively(Native Method)
   at java.io.File.createNewFile(File.java:947)
   at
 edu.sdsc.grid.io.local.LocalFile.createNewFile(LocalFile.java:486)
   at
 org.dspace.storage.bitstore.BitstreamStorageManager.store(BitstreamSto
 rageMa
 nager.java:300)
   at org.dspace.content.Bitstream.create(Bitstream.java:205)
   at org.dspace.content.Bundle.createBitstream(Bundle.java:384)
   at
 org.dspace.app.webui.servlet.admin.EditItemServlet.processUploadBitstr
 eam(Ed
 itItemServlet.java:857)
   at

org.dspace.app.webui.servlet.admin.EditItemServlet.doDSPost(EditItemServlet.
 java:160)
   at
 org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServle
 t.java
 :115)
   at
 org.dspace.app.webui.servlet.DSpaceServlet.doPost(DSpaceServlet.java:73)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
   at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appli
 cation
 FilterChain.java:305)
   at
 

Re: [Dspace-tech] Problem with bitstream upload

2014-03-31 Thread Anja Le Blanc
Hi Stefanie,

In the log4j.properties file add a line
log4j.logger.org.dspace.storage.bitstore=DEBUG, A1

That should change the log level for that java package only (after a 
restart of tomcat).

You said the owner of the directory is tomcat7. Have you also checked 
that tomcat7 can read and write to all subdirectories of assetstore?

Best regards,
Anja



On 31/03/2014 15:17, Stefanie Behnke wrote:
 Dear Anja,

 thanks for your interest.

 a) assetstore.incoming is not set, so I think it is 0 (zero) and corresponds
 to the 'assetstore.dir' above:
 # Asset (bitstream) store number 0 (zero)
 assetstore.dir = ${dspace.dir}/assetstore

 b) the owner of that directory is tomcat7

 You could also switch to log4j to debug mode for package
 org.dspace.storage.bitstore
 How can I do this?

 Thanks again for your help.

 Best regards
 Stefanie



 -Ursprüngliche Nachricht-
 Von: Anja Le Blanc [mailto:anja.lebl...@manchester.ac.uk]
 Gesendet: Montag, 31. März 2014 15:44
 An: Stefanie Behnke; dspace-tech@lists.sourceforge.net
 Betreff: Re: AW: [Dspace-tech] Problem with bitstream upload

 Hi Stefanie,

 Well, the error simply said that it can't create a file.
 At that point the code tries to create a file in the current assetstore.
 Could you check in your dspace.cfg
   a) whether assetstore.incoming is set
   b) the location of assetstore.dir or asetstore.dir.[the number from
 a)]

 Check the permission of that directory tree -- the tomcat user must be able
 to access that.

 You could also switch to log4j to debug mode for package
 org.dspace.storage.bitstore -- this would produce a line in dspace.log with
 the info of where it tries do create the file:
 log.debug(Local filename for  + sInternalId +  is
 +bufFilename.toString());

 That is all I could think of for that.

 Regards,
 Anja


 On 31/03/2014 13:56, Stefanie Behnke wrote:
 Dear Anja,

 error message on the screen:
 Internal System Error

 The system has experienced an internal error. Please try to do what
 you were doing again, and if the problem persists, please contact us
 so we can fix the problem.

 --
 from the dspace log:

 2014-03-31 14:41:52,827 INFO
 org.dspace.authenticate.LDAPAuthentication @

 anonymous:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=129.27.218.38:
 auth:attempting trivial auth of user=eg-supp...@eg.org
 2014-03-31 14:41:52,953 WARN
 org.dspace.authenticate.LDAPAuthentication @

 anonymous:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=129.27.218.38:
 ldap_authentication:type=failed_auth
 javax.naming.AuthenticationException\colon; [LDAP\colon; error code 49
 - Invalid Credentials]
 2014-03-31 14:41:52,953 INFO
 org.dspace.authenticate.PasswordAuthentication
 @

 anonymous:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=129.27.218.38:
 authenticate:attempting password auth of user=eg-supp...@eg.org
 2014-03-31 14:41:52,973 INFO
 org.dspace.authenticate.PasswordAuthentication
 @
 eg-supp...@eg.org:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=
 129.27 .218.38:authenticate:type=PasswordAuthentication
 2014-03-31 14:41:52,976 INFO
 org.dspace.app.webui.servlet.PasswordServlet @
 eg-supp...@eg.org:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=
 129.27
 .218.38:login:type=explicit
 2014-03-31 14:41:53,003 INFO
 org.dspace.app.webui.servlet.MyDSpaceServlet @
 eg-supp...@eg.org:session_id=03F65560962C60325F4784644FF62FD5:ip_addr=
 129.27
 .218.38:view_mydspace:
 2014-03-31 14:42:22,390 INFO  org.dspace.content.Bitstream @
 eg-supp...@eg.org:session_id=03F65560962C60325F4784644FF62FD5:ip_addr=
 129.27
 .218.38:update_bitstream:bitstream_id=6477
 2014-03-31 14:42:22,390 INFO  org.dspace.content.Bundle @
 eg-supp...@eg.org:session_id=03F65560962C60325F4784644FF62FD5:ip_addr=
 129.27
 .218.38:update_bundle:bundle_id=4273
 2014-03-31 14:42:22,393 INFO  org.dspace.content.Item @
 eg-supp...@eg.org:session_id=03F65560962C60325F4784644FF62FD5:ip_addr=
 129.27
 .218.38:update_item:item_id=4282
 2014-03-31 14:42:31,039 WARN
 org.dspace.app.webui.servlet.InternalErrorServlet @
 :session_id=03F65560962C60325F4784644FF62FD5:internal_error:-- URL Was:
 http://129.27.218.243:8080/jspui/tools/edit-item
 -- Method: POST
 -- Parameters were:

 java.io.IOException: No such file or directory
  at java.io.UnixFileSystem.createFileExclusively(Native Method)
  at java.io.File.createNewFile(File.java:947)
  at
 edu.sdsc.grid.io.local.LocalFile.createNewFile(LocalFile.java:486)
  at
 org.dspace.storage.bitstore.BitstreamStorageManager.store(BitstreamSto
 rageMa
 nager.java:300)
  at org.dspace.content.Bitstream.create(Bitstream.java:205)
  at org.dspace.content.Bundle.createBitstream(Bundle.java:384)
  at
 org.dspace.app.webui.servlet.admin.EditItemServlet.processUploadBitstr
 eam(Ed
 itItemServlet.java:857)
  at

 org.dspace.app.webui.servlet.admin.EditItemServlet.doDSPost(EditItemServlet.
 java:160)
  at
 

Re: [Dspace-tech] OAI set specification

2014-03-31 Thread Brouns, Francis
Hi Joan,

did you get an answer to your question? We also have this problem, in that our 
harvester URL needs to stay the same as it was before in order for our site to 
be harvested.

best wishes, Francis Brouns



From: Joan Caparrós [mailto:joan.capar...@csuc.cat]
Sent: 28 January 2014 17:17
To: dspace-tech@lists.sourceforge.net
Subject: [Dspace-tech] OAI set specification


Hi everybody,
I've notice that in the new OAI (with DSpace versión 3.x) a lot of things have 
changed, I'm worried about the set call.
In other versions we did a call like this:
request?verb=ListRecordsmetadataPrefix=eseset=hdl_10687_4
where set hdl_10687_4 was a comunity

now I see that with the new version this call doesn't work and I have to do 
something like this
request?verb=ListRecordsmetadataPrefix=eseset=com_10687_4

I have to save that compatibility because some harvesters already have my old 
comunities sets and now I can't change them.
How can I make to ensure compatibility with the old version calls?


--

.



Joan Caparrós

Tècnic de Projectes

Consorci de Serveis Universitaris de Catalunya (CSUC)



Gran Capità, 2 (Edifici Nexus)*08034 Barcelona

T.93 551 6204*F.93 205 
6979*joan.capar...@csuc.catmailto:joan.capar...@csuc.cat

www.csuc.cathttp://www.csuc.cat *Twitter @CSUC_info*Facebook*Linkedin

Subscriu-te al butlletí; (www.csuc.cat/butlletihttp://www.csuc.cat/butlleti)

.




Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Open Universiteit sluit iedere 
aansprakelijkheid uit die voortvloeit uit elektronische verzending. Aan de 
inhoud van deze e-mail en/of eventueel toegevoegde bijlagen kunnen geen rechten 
worden ontleend.

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Open Universiteit rules out any and every liability resulting from any 
electronic transmission. No rights may be derived from the contents of this 
message.
--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

[Dspace-tech] dspace upgrade from version 1.6 to version 3.2....

2014-03-31 Thread Joseph Sayah
Dear All,

I upgraded our dspace from version 1.6 to version 3.2, also I changed the 
servers and the URLs, everything went correctly, except the statistics;
What is the best way to import the old statistics data from the old version and 
server of 1.6 to the new server and version of 3.2? (bearing in mind that I 
switched the URL from https://ecommons.lau.edu.lb:8443/xmlui to 
https://laur.lau.edu.lb:8443/xmlui ).

Best,

Joseph N. SAYAH
ERP Application Administrator
IT Applications  Solutions, Ext: 1468

[Email signature Beirut]http://www.lau.edu.lb/
P please consider the environment before printing this email

inline: image001.jpg--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Re: [Dspace-tech] How to set property target=_blank into item-view.xsl

2014-03-31 Thread Geoconda Toledo
Hi Bhavesh,
Today, I have had the same question about set  proporty target=_blank
with our repository and I found this solution that for me worked.
Taking your code, after close the xsl: attribute name =href that start
in the 3rd line you should introduce this lines
xsl:attribute name=target
 xsl:text_blank/xsl:text
 /xsl:attribute

Well, the code would be this:

*div class=thumbnail-wrapper*
 *a class=image-link*
 *xsl:attribute name=href*

 * !-- HREF [ START ] --*
 * xsl:if test=@MIMETYPE = 'video/mp4' or @MIMETYPE = 'video/x-flv' *
 *
 i18n:text
http://192.168.251.220/irplayer/play.php?vLink=http://192.168.251.99:8080
 http://192.168.251.220/irplayer/play.php?vLink=http://192.168.251.99:8080
/i18n:
text
 *
 * xsl:value-of select=mets:FLocat[@LOCTYPE='URL']/@xlink:href/*
 * /xsl:if *
 * !-- HREF [ END ] --*

 * xsl:if test=@MIMETYPE != 'video/mp4' *
 * xsl:value-of select=mets:FLocat[@LOCTYPE='URL']/@xlink:href/*
 * /xsl:if *

 */xsl:attribute*



*xsl:attribute name=target
xsl:text_blank/xsl:text /xsl:attribute*

 * xsl:choose  *

 * xsl:when test=$context/mets:fileSec/mets:fileGrp[@USE='THUMBNAIL']/*
 *mets:file[@GROUPID=current()/@GROUPID] *
 *img alt=Thumbnail*
 *xsl:attribute name=src*
 *xsl:value-of
 select=$context/mets:fileSec/mets:fileGrp[@USE='THUMBNAIL']/ *
 *

mets:file[@GROUPID=current()/@GROUPID]/mets:FLocat[@LOCTYPE='URL']/@xlink:href/*
 */xsl:attribute*
 */img *
 */xsl:when*



I hope it works for you.
Regards
Geoconda.
--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Re: [Dspace-tech] Problem with bitstream upload

2014-03-31 Thread Stefanie Behnke
Dear Anja,

after checking all subdirecteries and changing the access rights to
tomcat7 instead of root the uploading works.

Thank you very much, I would not have found it out myself!

Best regards
Stefanie

-Ursprüngliche Nachricht-
Von: Anja Le Blanc [mailto:anja.lebl...@manchester.ac.uk] 
Gesendet: Montag, 31. März 2014 16:34
An: Stefanie Behnke; dspace-tech@lists.sourceforge.net
Betreff: Re: AW: AW: [Dspace-tech] Problem with bitstream upload

Hi Stefanie,

In the log4j.properties file add a line
log4j.logger.org.dspace.storage.bitstore=DEBUG, A1

That should change the log level for that java package only (after a restart
of tomcat).

You said the owner of the directory is tomcat7. Have you also checked that
tomcat7 can read and write to all subdirectories of assetstore?

Best regards,
Anja



On 31/03/2014 15:17, Stefanie Behnke wrote:
 Dear Anja,

 thanks for your interest.

 a) assetstore.incoming is not set, so I think it is 0 (zero) and 
 corresponds to the 'assetstore.dir' above:
 # Asset (bitstream) store number 0 (zero) assetstore.dir = 
 ${dspace.dir}/assetstore

 b) the owner of that directory is tomcat7

 You could also switch to log4j to debug mode for package
 org.dspace.storage.bitstore
 How can I do this?

 Thanks again for your help.

 Best regards
 Stefanie



 -Ursprüngliche Nachricht-
 Von: Anja Le Blanc [mailto:anja.lebl...@manchester.ac.uk]
 Gesendet: Montag, 31. März 2014 15:44
 An: Stefanie Behnke; dspace-tech@lists.sourceforge.net
 Betreff: Re: AW: [Dspace-tech] Problem with bitstream upload

 Hi Stefanie,

 Well, the error simply said that it can't create a file.
 At that point the code tries to create a file in the current assetstore.
 Could you check in your dspace.cfg
   a) whether assetstore.incoming is set
   b) the location of assetstore.dir or asetstore.dir.[the number from 
 a)]

 Check the permission of that directory tree -- the tomcat user must be 
 able to access that.

 You could also switch to log4j to debug mode for package 
 org.dspace.storage.bitstore -- this would produce a line in dspace.log 
 with the info of where it tries do create the file:
 log.debug(Local filename for  + sInternalId +  is 
 +bufFilename.toString());

 That is all I could think of for that.

 Regards,
 Anja


 On 31/03/2014 13:56, Stefanie Behnke wrote:
 Dear Anja,

 error message on the screen:
 Internal System Error

 The system has experienced an internal error. Please try to do what 
 you were doing again, and if the problem persists, please contact us 
 so we can fix the problem.

 --
 from the dspace log:

 2014-03-31 14:41:52,827 INFO
 org.dspace.authenticate.LDAPAuthentication @


anonymous:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=129.27.218.38:
 auth:attempting trivial auth of user=eg-supp...@eg.org
 2014-03-31 14:41:52,953 WARN
 org.dspace.authenticate.LDAPAuthentication @


anonymous:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=129.27.218.38:
 ldap_authentication:type=failed_auth
 javax.naming.AuthenticationException\colon; [LDAP\colon; error code 
 49
 - Invalid Credentials]
 2014-03-31 14:41:52,953 INFO
 org.dspace.authenticate.PasswordAuthentication
 @


anonymous:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=129.27.218.38:
 authenticate:attempting password auth of user=eg-supp...@eg.org
 2014-03-31 14:41:52,973 INFO
 org.dspace.authenticate.PasswordAuthentication
 @
 eg-supp...@eg.org:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr
 =
 129.27 .218.38:authenticate:type=PasswordAuthentication
 2014-03-31 14:41:52,976 INFO
 org.dspace.app.webui.servlet.PasswordServlet @ 
 eg-supp...@eg.org:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr
 =
 129.27
 .218.38:login:type=explicit
 2014-03-31 14:41:53,003 INFO
 org.dspace.app.webui.servlet.MyDSpaceServlet @ 
 eg-supp...@eg.org:session_id=03F65560962C60325F4784644FF62FD5:ip_addr
 =
 129.27
 .218.38:view_mydspace:
 2014-03-31 14:42:22,390 INFO  org.dspace.content.Bitstream @ 
 eg-supp...@eg.org:session_id=03F65560962C60325F4784644FF62FD5:ip_addr
 =
 129.27
 .218.38:update_bitstream:bitstream_id=6477
 2014-03-31 14:42:22,390 INFO  org.dspace.content.Bundle @ 
 eg-supp...@eg.org:session_id=03F65560962C60325F4784644FF62FD5:ip_addr
 =
 129.27
 .218.38:update_bundle:bundle_id=4273
 2014-03-31 14:42:22,393 INFO  org.dspace.content.Item @ 
 eg-supp...@eg.org:session_id=03F65560962C60325F4784644FF62FD5:ip_addr
 =
 129.27
 .218.38:update_item:item_id=4282
 2014-03-31 14:42:31,039 WARN
 org.dspace.app.webui.servlet.InternalErrorServlet @
 :session_id=03F65560962C60325F4784644FF62FD5:internal_error:-- URL Was:
 http://129.27.218.243:8080/jspui/tools/edit-item
 -- Method: POST
 -- Parameters were:

 java.io.IOException: No such file or directory
  at java.io.UnixFileSystem.createFileExclusively(Native Method)
  at java.io.File.createNewFile(File.java:947)
  at
 edu.sdsc.grid.io.local.LocalFile.createNewFile(LocalFile.java:486)
  at
 

Re: [Dspace-tech] Problem with bitstream upload

2014-03-31 Thread Hilton Gibson
This may also help:
http://wiki.lib.sun.ac.za/index.php/SUNScholar/Prepare_Ubuntu/S08#Step_8.5_Setup_Tomcat_server_permissions


*Hilton Gibson*
Ubuntu Linux Systems Administrator
JS Gericke Library
Room 1025D
Stellenbosch University
Private Bag X5036
Stellenbosch
7599
South Africa

Tel: +27 21 808 4100 | Cell: +27 84 646 4758
http://scholar.sun.ac.za
http://bit.ly/goodir
http://library.sun.ac.za
http://za.linkedin.com/in/hiltongibson


On 31 March 2014 19:17, Stefanie Behnke s.beh...@online.de wrote:

 Dear Anja,

 after checking all subdirecteries and changing the access rights to
 tomcat7 instead of root the uploading works.

 Thank you very much, I would not have found it out myself!

 Best regards
 Stefanie

 -Ursprüngliche Nachricht-
 Von: Anja Le Blanc [mailto:anja.lebl...@manchester.ac.uk]
 Gesendet: Montag, 31. März 2014 16:34
 An: Stefanie Behnke; dspace-tech@lists.sourceforge.net
 Betreff: Re: AW: AW: [Dspace-tech] Problem with bitstream upload

 Hi Stefanie,

 In the log4j.properties file add a line
 log4j.logger.org.dspace.storage.bitstore=DEBUG, A1

 That should change the log level for that java package only (after a
 restart
 of tomcat).

 You said the owner of the directory is tomcat7. Have you also checked that
 tomcat7 can read and write to all subdirectories of assetstore?

 Best regards,
 Anja



 On 31/03/2014 15:17, Stefanie Behnke wrote:
  Dear Anja,
 
  thanks for your interest.
 
  a) assetstore.incoming is not set, so I think it is 0 (zero) and
  corresponds to the 'assetstore.dir' above:
  # Asset (bitstream) store number 0 (zero) assetstore.dir =
  ${dspace.dir}/assetstore
 
  b) the owner of that directory is tomcat7
 
  You could also switch to log4j to debug mode for package
  org.dspace.storage.bitstore
  How can I do this?
 
  Thanks again for your help.
 
  Best regards
  Stefanie
 
 
 
  -Ursprüngliche Nachricht-
  Von: Anja Le Blanc [mailto:anja.lebl...@manchester.ac.uk]
  Gesendet: Montag, 31. März 2014 15:44
  An: Stefanie Behnke; dspace-tech@lists.sourceforge.net
  Betreff: Re: AW: [Dspace-tech] Problem with bitstream upload
 
  Hi Stefanie,
 
  Well, the error simply said that it can't create a file.
  At that point the code tries to create a file in the current assetstore.
  Could you check in your dspace.cfg
a) whether assetstore.incoming is set
b) the location of assetstore.dir or asetstore.dir.[the number from
  a)]
 
  Check the permission of that directory tree -- the tomcat user must be
  able to access that.
 
  You could also switch to log4j to debug mode for package
  org.dspace.storage.bitstore -- this would produce a line in dspace.log
  with the info of where it tries do create the file:
  log.debug(Local filename for  + sInternalId +  is
  +bufFilename.toString());
 
  That is all I could think of for that.
 
  Regards,
  Anja
 
 
  On 31/03/2014 13:56, Stefanie Behnke wrote:
  Dear Anja,
 
  error message on the screen:
  Internal System Error
 
  The system has experienced an internal error. Please try to do what
  you were doing again, and if the problem persists, please contact us
  so we can fix the problem.
 
  --
  from the dspace log:
 
  2014-03-31 14:41:52,827 INFO
  org.dspace.authenticate.LDAPAuthentication @
 
 
 anonymous:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=
 129.27.218.38:
  auth:attempting trivial auth of user=eg-supp...@eg.org
  2014-03-31 14:41:52,953 WARN
  org.dspace.authenticate.LDAPAuthentication @
 
 
 anonymous:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=
 129.27.218.38:
  ldap_authentication:type=failed_auth
  javax.naming.AuthenticationException\colon; [LDAP\colon; error code
  49
  - Invalid Credentials]
  2014-03-31 14:41:52,953 INFO
  org.dspace.authenticate.PasswordAuthentication
  @
 
 
 anonymous:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr=
 129.27.218.38:
  authenticate:attempting password auth of user=eg-supp...@eg.org
  2014-03-31 14:41:52,973 INFO
  org.dspace.authenticate.PasswordAuthentication
  @
  eg-supp...@eg.org:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr
  =
  129.27 .218.38:authenticate:type=PasswordAuthentication
  2014-03-31 14:41:52,976 INFO
  org.dspace.app.webui.servlet.PasswordServlet @
  eg-supp...@eg.org:session_id=C1E9A7CC860353716D89DBFFEBDEFDCF:ip_addr
  =
  129.27
  .218.38:login:type=explicit
  2014-03-31 14:41:53,003 INFO
  org.dspace.app.webui.servlet.MyDSpaceServlet @
  eg-supp...@eg.org:session_id=03F65560962C60325F4784644FF62FD5:ip_addr
  =
  129.27
  .218.38:view_mydspace:
  2014-03-31 14:42:22,390 INFO  org.dspace.content.Bitstream @
  eg-supp...@eg.org:session_id=03F65560962C60325F4784644FF62FD5:ip_addr
  =
  129.27
  .218.38:update_bitstream:bitstream_id=6477
  2014-03-31 14:42:22,390 INFO  org.dspace.content.Bundle @
  eg-supp...@eg.org:session_id=03F65560962C60325F4784644FF62FD5:ip_addr
  =
  129.27
  .218.38:update_bundle:bundle_id=4273
  2014-03-31 14:42:22,393 INFO  org.dspace.content.Item @
  

Re: [Dspace-tech] OAI set specification

2014-03-31 Thread Kim Shepherd
Hi all, my initial suggestion was going to be using Apache mod_rewrite to
rewrite the hdl_ portion of the set  query value, but now I realise you
don't know in advance whether it's a collection or a community... (ie.
com or col in the new value).. that is tricky.
Depending on the number of communities and collections you have, you could
still implement this with a series of rules, one per set (instead of a
regex match/replace), but it doesn't scale very well and needs constant
maintenance as you add/change your community and collection structure.

Just a note -- your actual OAI endpoint URL isn't really changing, just the
set ID format... if a OAI harvester does a request?verb=ListSets as normal,
they'll get back a list of the (new) set IDs and can then harvest them
without worrying about what they used to be, or will be in future... do you
have any harvesters that are configured to just come in and harvest
particular OAI sets?

Cheers

Kim


On 1 April 2014 03:39, Brouns, Francis francis.bro...@ou.nl wrote:

  Hi Joan,



 did you get an answer to your question? We also have this problem, in that
 our harvester URL needs to stay the same as it was before in order for our
 site to be harvested.



 best wishes, Francis Brouns







 *From:* Joan Caparrós [mailto:joan.capar...@csuc.cat]
 *Sent:* 28 January 2014 17:17
 *To:* dspace-tech@lists.sourceforge.net
 *Subject:* [Dspace-tech] OAI set specification





 Hi everybody,
 I've notice that in the new OAI (with DSpace versión 3.x) a lot of things
 have changed, I'm worried about the set call.
 In other versions we did a call like this:
 request?verb=ListRecordsmetadataPrefix=eseset=*hdl*_10687_4
 where set hdl_10687_4 was a comunity

 now I see that with the new version this call doesn't work and I have to
 do something like this
 request?verb=ListRecordsmetadataPrefix=eseset=*com*_10687_4

 I have to *save* that *compatibility* because some harvesters already
 have my old comunities sets and now I can't change them.
 How can I make to ensure compatibility with the old version calls?

  --

 .



 Joan Caparrós

 Tècnic de Projectes

 Consorci de Serveis Universitaris de Catalunya (CSUC)



 Gran Capità, 2 (Edifici Nexus)•08034 Barcelona

 T.93 551 6204•F.93 205 6979•joan.capar...@csuc.cat

 www.csuc.cat •Twitter @CSUC_info•Facebook•Linkedin

 Subscriu-te al butlletí; (www.csuc.cat/butlleti)

 .





 --
 Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking
 aan en gebruik door anderen is niet toegestaan. Open Universiteit sluit
 iedere aansprakelijkheid uit die voortvloeit uit elektronische verzending.
 Aan de inhoud van deze e-mail en/of eventueel toegevoegde bijlagen kunnen
 geen rechten worden ontleend.

 This e-mail is intended exclusively for the addressee(s), and may not be
 passed on to, or made available for use by any person other than the
 addressee(s). Open Universiteit rules out any and every liability resulting
 from any electronic transmission. No rights may be derived from the
 contents of this message.


 --

 ___
 DSpace-tech mailing list
 DSpace-tech@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-tech
 List Etiquette:
 https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

[Dspace-tech] [SPAM] Dspace 4.1 JSPUI Error displaying thumbnails

2014-03-31 Thread damanzano
JSPUI is not displaying thumbnails in browse or search results even when it
is enabled. I have found this error when only discovery is enable, debugging
the app i notice that the following methods always return null or  even
when my items have a thumbnail bundle:

org.dspace.app.webui.jsptag.BrowseListTag.getThumbMarkup(HttpServletRequest
hrq, BrowseItem item) returns  when a call to
org.dspace.content.service.ItemService.getThumbnail(Context context, int
itemId, boolean requireOriginal) returns null

I have tried changing ItemServices.getThumbnail(Context context, int itemId,
boolean requireOriginal) with
org.dspace.browse.BrowseItem.getThumbnail() but I got the same results.

Can anyone help me?

NOTE: I have found something weird in my logs and it is that there are any
call to a database query, it is whta you hope if you are using DISCOVERY and
SOLRDao, but i'm wondering if thumbnails bundles are being written to the
SOLR index.



--
View this message in context: 
http://dspace.2283337.n4.nabble.com/Dspace-4-1-JSPUI-Error-displaying-thumbnails-tp4672409.html
Sent from the DSpace - Tech mailing list archive at Nabble.com.

--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette