[dspace-tech] Re: general_jspui_error

[Freddy Guerrero]

I found the error, this record has a damaged file (Image attaches). The 
image was not generated (Thumbnail), this causes that the collection to 
which it belongs doesn't open (deleting this file fixes the problem). I 
have several cases of this type. Does someone has an idea of how to locate 
this type of records with corrupted files?

[image: error3.jpg]

Regards,

Freddy





El lunes, 24 de septiembre de 2018, 0:09:49 (UTC-5), Freddy Guerrero 
escribió:
>
> Please can you help me with this query, I use dspace version 6.3 (JSPUI), 
> this error occurs when I search for example the word "Inteligencia", in 
> xmlui it works well.
>
>
> 2018-09-24 00:00:04,194 INFO  
> org.dspace.app.webui.discovery.DiscoverySearchRequestProcessor @ 
> anonymous:session_id=FB3898400884E853E071EB0B361094E4:ip_addr=190.131.162.9:search:scope=null,query="Inteligencia
>  
> ",results=(0,0,10)
> 2018-09-24 00:00:04,226 WARN  org.dspace.app.webui.servlet.DSpaceServlet @ 
> anonymous:session_id=FB3898400884E853E071EB0B361094E4:ip_addr=190.131.162.9:general_jspui_error:javax.servlet.ServletException\colon;
>  
> org.apache.jasper.JasperException\colon; java.lang.NullPointerException
> javax.servlet.ServletException: org.apache.jasper.JasperException: 
> java.lang.NullPointerException
> at org.dspace.app.webui.util.JSPManager.showJSP(JSPManager.java:71)
> at 
> org.dspace.app.webui.discovery.DiscoverySearchRequestProcessor.doSimpleSearch(DiscoverySearchRequestProcessor.java:458)
> at 
> org.dspace.app.webui.servlet.SimpleSearchServlet.doDSGet(SimpleSearchServlet.java:63)
> at 
> org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:126)
> at org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:73)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:624)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at 
> org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219)
> at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:110)
> at 
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:494)
> at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169)
> at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
> at 
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:1025)
> at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
> at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:445)
> at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1136)
> at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:637)
> at 
> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.jasper.JasperException: 
> java.lang.NullPointerException
> at 
> org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:561)
> at 
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:477)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at 
> 

[dspace-tech] Re: Export an item without losing its statistics

[Freddy Guerrero]

Stuart

Thank you for answering. What happened was that this item was deleted by 
accident, do you know if I can get it back somehow?

Regards,

Freddy



El miércoles, 26 de septiembre de 2018, 21:35:08 (UTC-5), Freddy Guerrero 
escribió:
>
> Hello with everyone
>
> Please can you help me with this query: How do I export an item but 
> without losing its statistics? This is because it has many downloads and 
> the author requires us to keep the statistics.
>
> http://67.192.84.248:8080/handle/10469/8680/statistics
>
> Then I need to import it to my repository
>
> Fred
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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] Export an item without losing its statistics

[Stuart A. Yeates]

As far as I know, none of the export formats currently support statistics.

I have briefly thought about the possibility of putting counter
https://www.projectcounter.org/ stats in the METS, which seems doable,
but never got around to implementing it.

cheers
stuart


--
...let us be heard from red core to black sky
On Thu, 27 Sep 2018 at 14:35, Freddy Guerrero  wrote:
>
> Hello with everyone
>
> Please can you help me with this query: How do I export an item but without 
> losing its statistics? This is because it has many downloads and the author 
> requires us to keep the statistics.
>
> http://67.192.84.248:8080/handle/10469/8680/statistics
>
> Then I need to import it to my repository
>
> Fred
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of 
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> 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.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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] Export an item without losing its statistics

[Freddy Guerrero]

Hello with everyone

Please can you help me with this query: How do I export an item but without 
losing its statistics? This is because it has many downloads and the author 
requires us to keep the statistics.

http://67.192.84.248:8080/handle/10469/8680/statistics

Then I need to import it to my repository

Fred

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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: Internal Error in jspui when searching or entering on a collection item

[Walter Nakamura]

Hi Freddy!

Well, it has been a long time since I faced this problem. I don't remember
in details, but basically what I did was export all collections separately
and perform a clean install, importing each collection separetely. Every
time I imported a collection I verified whether it makes dspace crash or
not. I don't know exactly if it was a problem with a given collection or if
was a problem during the installation. Before reinstalling, please make a
backup. The first time I exported the entire collection and reinstalled,
dspace gave me an error during importing process. I could recover some
collections, but others were lost.

Best regards,

*Walter*


Em seg, 24 de set de 2018 às 01:14, Freddy Guerrero 
escreveu:

> Now I have the same error in dspace version 6.3, I wanted to ask if you
> could solve it?
>
> Freddy
>
>
>
> El jueves, 26 de octubre de 2017, 18:05:53 (UTC-5), Walter Nakamura
> escribió:
>>
>> Hi! I'm having trouble when accessing a item on a collection or searching
>> in jspui interface. The problem does not occur in xmlui.
>>
>> Any ideas?
>>
>> Here is the log file:
>>
>> 2017-10-26 18:53:03,485 INFO
>> org.dspace.app.webui.discovery.DiscoverySearchRequestProcessor @
>> anonymous:session_id=D2FA8115706527A25FD50A90876A2F09:ip_addr=192.168.1.1:
>> search:scope=null,query="null",results=(0,0,1)
>> 2017-10-26 18:53:03,557 WARN  org.dspace.app.webui.servlet.DSpaceServlet
>> @ 
>> anonymous:session_id=D2FA8115706527A25FD50A90876A2F09:ip_addr=192.168.1.1:general_jspui_error:javax.servlet.ServletException\colon;
>> org.apache.jasper.JasperException\colon; The absolute uri\colon;
>> [http\colon;//java.sun.com/jsp/jstl/core] cannot be resolved in either
>> web.xml or the jar files deployed with this application
>> javax.servlet.ServletException: org.apache.jasper.JasperException: The
>> absolute uri: [http://java.sun.com/jsp/jstl/core] cannot be resolved in
>> either web.xml or the jar files deployed with this application
>> at
>> org.dspace.app.webui.util.JSPManager.showJSP(JSPManager.java:71)
>> at
>> org.dspace.app.webui.discovery.DiscoverySearchRequestProcessor.doSimpleSearch(DiscoverySearchRequestProcessor.java:447)
>> at
>> org.dspace.app.webui.servlet.SimpleSearchServlet.doDSGet(SimpleSearchServlet.java:63)
>> at
>> org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:126)
>> at
>> org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:73)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:635)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:742)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
>> at
>> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
>> at
>> org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
>> at
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198)
>> at
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
>> at
>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:478)
>> at
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140)
>> at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:80)
>> at
>> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:650)
>> at
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)
>> at
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342)
>> at
>> org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:799)
>> at
>> org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
>> at
>> org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868)
>> at org.apache.tomcat.util.net
>> .NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1457)
>> at org.apache.tomcat.util.net
>> .SocketProcessorBase.run(SocketProcessorBase.java:49)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>> at
>> 

[dspace-tech] Re: AWS S3 Connection Pool Error

[Nicholas Woodward]

Just out of curiosity, is this still an issue for folks on this thread? 
Were you able to resolve your issues by setting up a connection pool in Tomcat 
using Alan Orth's instructions? The reason I ask is that when we upgraded 
from 5.4 to 6.3 we also moved the assetstore into S3. And since then 
there's been an almost constant stream of errors like this in the logs.


com.amazonaws.http.AmazonHttpClient @ Unable to execute HTTP request: 
Timeout waiting for connection from pool
org.apache.http.conn.ConnectionPoolTimeoutException: Timeout waiting for 
connection from pool


When that happened I set up a connection pool using the instructions in the 
DSpace 6 installation docs - 
https://wiki.duraspace.org/display/DSDOC6x/Installing+DSpace#InstallingDSpace-Externaldatabaseconnectionpool.
 
And I set it up with what I thought were sufficiently high values for the 
maximum total connections (200) and maximum idle connections (50).


But the new setup has been in place for a few days now, and we're still 
seeing connection pool timeouts on a daily basis. Even though the maximum 
total connections is set to 200, we never see near that many postgres 
processes at any given time.


Is there some additional configuration to the JNDI Datasource that would 
help our situation? Or were there other things people did to improve the 
performance? 



Thanks,

Nick




On Wednesday, January 3, 2018 at 3:29:12 PM UTC-6, Mark H. Wood wrote:
>
> You might want to consider moving the pool out of DSpace's control into 
> the Servlet container -- see "Notes on PostgreSQL connection pooling with a 
> Tomcat JNDI resource" by Alan Orth elsewhere in this group.  It would give 
> you access to more of the pool's parameters (for testing connections before 
> use, and the like) and also make it easy to use a newer driver.  I've had 
> better luck with this arrangement.
>
> I believe that db.statementpool affects pooling of prepared statements 
> only.  Unless you've adjusted PostgreSQL, the default on its end is to do 
> no statement pooling regardless of what the client requests.  Like most 
> DBMS-centric webapp.s, DSpace can't operate without a connection pool.
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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] Help Handle Server

[Tim Donohue]

Hello Leidy,

If you want to use hdl.handle.net, then you should update your
configuration to be:

handle.canonical.prefix = http://hdl.handle.net/

More information is available in the Handle Server configuration
documentation at
https://wiki.duraspace.org/display/DSDOC6x/Configuration+Reference#ConfigurationReference-HandleServerConfiguration


- Tim

On Tue, Sep 25, 2018 at 11:27 AM Leidy Madroñero  wrote:

> good morning
>
> I am configuring the handle server in dspace 6.
>
> The server was validated by the CNRI. The problem arises when I try to
> test the prefix changes assigned to me in my repository by creating a new
> item, which continues to appear with the prefix that comes by default in
> the installation.
>
> I have modified the following line in the local.cfg file because of the
> prefix assigned to me:
>
> handle.prefix = 123456789
>
> In addition to the previous one, there are other additional lines that I
> am not sure of changing, for example:
>
> By default it appears:
> handle.canonical.prefix = $ {dspace.url} / handle /
>
> Is it correct to change it in this way?
>
> handle.canonical.prefix = $ {dspace.url} /http://hdl.handle.net/
>
> After this, it is necessary to rebuild dspace or restart the server to
> visualize the changes of the prefix in the repository ?.
>
> I appreciate your collaboration.
>
> Greetings, lady.
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> 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.
>
-- 
Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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: Error bean PubmedImportService - Version 6.3

[Leonardo Matos]

Hi Mark,

Thanks for the feedback, I checked all the points you said and it's exactly as 
it should be. Look:

*pubmed-integration.xml*

[image: image.png]

*AbstractRemoteMetadataSource.java*
[image: image.png]

[image: image.png]



*PubmedImportMetadataSourceServiceImpl.java*

[image: image.png]


I'm using DSpace 6.3 without any changes. I looked at the 
spring-dspace-addon-import-services.xml file that references url 
http://eutils.ncbi.nlm.nih.gov/entrez/eutils/, can you tell me if the firewall 
or proxy of the company may be barring this connection?



Em quarta-feira, 26 de setembro de 2018 06:11:21 UTC-7, Mark H. Wood 
escreveu:
>
> On Tuesday, September 25, 2018 at 2:56:06 PM UTC-4, Leonardo Matos wrote:
>>
>> I have a problem updating my dspace to version 6.3. The error occurs 
>> while starting tomcat. The error is below, Can anyone help me with this?
>>
>>
>> *"Error creating bean with name 'PubmedImportService': Injection of 
>> resource dependencies failed; nested exception is 
>> org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean 
>> named 'maxRetry' is defined"*
>>
>
>
> maxRetry should be defined in 
> '[DSpace]/config/spring/api/pubmed-integration.xml'.  It is required as a 
> @Resource in 
> org.dspace.importer.external.service.components.AbstractRemoteMetadataSource, 
> and I expect that PubmedImportMetadataSource extends that.  I would first 
> check pubmed-integration.xml for damage.
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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: Problems with Orcid in dspace 6.3

[mmorris]

Thanks Darryl, This makes sense now. In my testing the same authority key 
is generated for dc.contributor.editor and it's different from the key 
generated for dc.contrinbutor.author so i believe it's by design.

I hope there's a good reason for that because it's essentially the same 
person, and the problem is when browsing by author the same person is 
listed twice which causes a confusion.

-Mike

On Wednesday, September 26, 2018 at 1:45:42 PM UTC-4, Darryl Friesen wrote:
>
>
> Mike, the ORCID Integration page (
> https://wiki.duraspace.org/display/DSDOC6x/ORCID+Integration#ORCIDIntegration-AddingadditionalfieldsunderORCID)
>  
> has this comment
>
> *Note*: Each metadata field has a separate set of authority records. 
>> Authority keys are not shared between different metadata fields. E. g. 
>> multiple dc.contributor.author can have the same authority key and point to 
>> the same authority record in the cache. But when an ORCID is chosen for a 
>> dc.contributor.editor field, a separate record is made in the cache. Both 
>> records are updated from the same source and will contain the same 
>> information. The difference is that when performing a look-up of a person 
>> that has been introduced as an authority for an author field but not yet as 
>> an editor, it will show as record that is not yet present in the repository 
>> cache. 
>
>
>
> So I wonder if the new IDs are actually by-design, because they are for a 
> different metadata field.
>
> Or is your issue not that dc.contrinbutor.author and dc.contributor.editor 
> each contain different IDs, but that the patch only fixed the issue for 
> dc.contrinbutor.author and dc.contributor.editor still has teh same issue 
> as before (multiple authority control records in the Solr database for the 
> same person, each with a new ID)?
>
> - Darryl
>
>
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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: Problems with Orcid in dspace 6.3

[Darryl Friesen]

Mike, the ORCID Integration page 
(https://wiki.duraspace.org/display/DSDOC6x/ORCID+Integration#ORCIDIntegration-AddingadditionalfieldsunderORCID)
 
has this comment

*Note*: Each metadata field has a separate set of authority records. 
> Authority keys are not shared between different metadata fields. E. g. 
> multiple dc.contributor.author can have the same authority key and point to 
> the same authority record in the cache. But when an ORCID is chosen for a 
> dc.contributor.editor field, a separate record is made in the cache. Both 
> records are updated from the same source and will contain the same 
> information. The difference is that when performing a look-up of a person 
> that has been introduced as an authority for an author field but not yet as 
> an editor, it will show as record that is not yet present in the repository 
> cache. 



So I wonder if the new IDs are actually by-design, because they are for a 
different metadata field.

Or is your issue not that dc.contrinbutor.author and dc.contributor.editor 
each contain different IDs, but that the patch only fixed the issue for 
dc.contrinbutor.author and dc.contributor.editor still has teh same issue 
as before (multiple authority control records in the Solr database for the 
same person, each with a new ID)?

- Darryl


-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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: Announcing the next DSpace 7 (Virtual) Development Sprint (Oct 1-12). Sign up to learn more about & contribute to DSpace 7!

[Tim Donohue]

All,

This is your final reminder that our third DSpace 7 Community Sprint starts
*next week*  (Oct 1-12).  We are still accepting participants!  As a
reminder, you do not need to be available for the full two weeks. You just
need to be willing to learn & claim one (or more) ticket(s) to work on over
the two week period.  As noted previously, this is a great opportunity to
learn more about DSpace 7 and the DSpace code contribution process!

Signup at:
https://wiki.duraspace.org/display/DSPACE/DSpace+7+Community+Sprints#DSpace7CommunitySprints-ParticipantSignups

As always, please get in touch if you have any questions.

Tim

On Thu, Sep 20, 2018 at 2:44 PM Tim Donohue  wrote:

> All,
>
> Friendly reminder that we are still accepting signups for our next DSpace
> 7 Community Sprint (Oct 1-12).  We already have 4 participants signed up,
> but we're looking for a few more. Again, this is a great opportunity to
> learn more about DSpace 7 and the DSpace code contribution process!
>
> Signup at:
> https://wiki.duraspace.org/display/DSPACE/DSpace+7+Community+Sprints#DSpace7CommunitySprints-ParticipantSignups
>
> As always, please get in touch if you have any questions.
>
> Tim Donohue
>
> On Thu, Sep 6, 2018 at 12:52 PM Tim Donohue 
> wrote:
>
>> All,
>>
>> *Our third DSpace 7 (Virtual) Development Sprint will take place from
>> October 1-12.*
>>
>> We are in search of developers interested in joining us for a two week
>> sprint (you need not be available for the entire two weeks).  Sprint
>> participants will help us make enhancements / squash bugs in the DSpace 7
>> codebase. Tasks will be available for both the DSpace 7 UI (using
>> Angular.io) and REST API (using Java / Spring technologies), and will be
>> listed on the Sprint #3 planning page
>> 
>> in the coming weeks.
>>
>> *No experience with DSpace 7 codebase is necessary* (though experience
>> with prior DSpace releases is recommended). Sprint Coaches will be on hand
>> to help provide ongoing support. However, as no official training/workshops
>> will be held during the sprint, participants will be expected to be
>> proactive in learning new concepts via the provided learning resources
>> 
>>  (including
>> past workshop/training materials). Don't worry though, we fully expect
>> participants to have questions and need ongoing support, which is where the
>> Sprint Coaches come in.
>>
>> *Whether you have contributed to DSpace in the past or not, this is great
>> opportunity to learn more about the DSpace 7 Angular UI and/or new REST
>> API.*  If you've never participated in the open source development
>> process, this is a great way to "get your feet wet", and submit your very
>> first Pull Request (PR) to DSpace!
>>
>> *Signups are open immediately *on the below wiki page. Feel free to pass
>> this along to colleagues!
>> https://wiki.duraspace.org/display/DSPACE/DSpace+7+Community+Sprints
>>
>> If you or your team have questions, feel free to get in touch, either via
>> email or Slack .
>>
>> Sincerely,
>>
>> Tim Donohue
>> --
>> Tim Donohue
>> Technical Lead for DSpace & DSpaceDirect
>> DuraSpace.org | DSpace.org | DSpaceDirect.org
>>
> --
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>
-- 
Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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: Error bean PubmedImportService - Version 6.3

[Mark H. Wood]

On Tuesday, September 25, 2018 at 2:56:06 PM UTC-4, Leonardo Matos wrote:
>
> I have a problem updating my dspace to version 6.3. The error occurs while 
> starting tomcat. The error is below, Can anyone help me with this?
>
>
> *"Error creating bean with name 'PubmedImportService': Injection of 
> resource dependencies failed; nested exception is 
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean 
> named 'maxRetry' is defined"*
>


maxRetry should be defined in 
'[DSpace]/config/spring/api/pubmed-integration.xml'.  It is required as a 
@Resource in 
org.dspace.importer.external.service.components.AbstractRemoteMetadataSource, 
and I expect that PubmedImportMetadataSource extends that.  I would first 
check pubmed-integration.xml for damage.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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.