[dspace-tech] Problem importing SAF package: defined by the key 'org.dspace.app.batchitemimport.work.dir' in dspace.cfg is not a valid directory

[RICARDO EITO BRUN]

Dear colleagues,
I am trying to execute a batch SAF import both from the user interface and
the command line, and I am getting this error:

"...defined by the key 'org.dspace.app.batchitemimport.work.dir' in
dspace.cfg is not a valid directory"

I have seen the same problem reported by other colleagues.

One point: I am making some tests in a Windows machine, so I understand
this may be the reason for the problem.

Any info is welcome,

Ricardo

-- 
RICARDO EITO BRUN
Universidad Carlos III de Madrid

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAK0P-rSWzV6a7NOAHd9HmH%3Dtj%2Bryd3-YbC4WOTNNm_P8t5BT5Q%40mail.gmail.com.

[dspace-tech] Re: DSpace 7.6.1 and Deepgreen: SWORD v2 Deposit via METSMODS packaging?

[Matthias Letsch]

Additional information: The deposit via console works just fine with 
METSDSpaceSIP, but this packaging type doesn't seem to work with the 
DeepGreen client...

Matthias Letsch schrieb am Mittwoch, 19. Juni 2024 um 10:51:45 UTC+2:

> Hi there,
>
> This question is primarily aimed at my colleagues from Germany who 
> participate in DeepGreen (https://info.oa-deepgreen.de) and/or people who 
> are familiar with the Swordv2 API...
>
> We're part of DeepGreen and want to deposit the articles via the SWORD v2 
> interface. In DSpace, SWORD v2 is enabled and the deposit works in 
> principle, e.g. via console commands.
>
> I was told to use the method http://purl.org/net/sword/package/METSMODS 
> in the DeepGreen Sword Client. Also, all other details are correct (SWORD 
> username, password, collection). Still the deposit doesn't work. 
>
> When trying to deposit an example via the console, an error message tells 
> me that there is no ingester configured for METSMODS:
> (#=password)
>
> curl -i --data-binary "@example.zip" -H "Content-Disposition:attachment; 
> filename=example.zip" -H "Content-Type:application/zip" -H "Packaging:
> http://purl.org/net/sword/package/METSMODS; -u us...@hohpublica.de:# 
> -X POST 
> https://hohpublica.uni-hohenheim.de/server/swordv2/collection/123456789/15867
>
> Result:
>
> HTTP/1.1 100 Continue
>
> HTTP/1.1 415 415
> Date: Wed, 19 Jun 2024 08:24:20 GMT
> Server: Apache/2.4.38 (Debian)
> Content-Language: en,de
> Content-Type: text/xml;charset=UTF-8
> Transfer-Encoding: chunked
>
> 
> http://purl.org/net/sword/error/ErrorContent; 
> xmlns:sword="http://purl.org/net/sword/terms/;>http://www.w3.org/2005/Atom;>ERRORhttp://www.w3.org/2005/Atom;>2024-06-19T10:24:20Z  
> uri="http://www.dspace.org/ns/sword/2.0/; version="2.0" xmlns:atom="
> http://www.w3.org/2005/Atom;>us...@uni-hohenheim.deProcessing
>  
> failedhttp://www.w3.org/2005/Atom;>No ingester configured for this package 
> typeorg.swordapp.server.SwordError: 
> No ingester configured for this package type
> at ...
>
> It seems like there is no ingester for METSMODS in DSpace 7...
>
> Is there anyone for whom the deposit from Deepgreen SWORD v2 to DSpace 7 
> already works? What do I have to configure so that the deposit works via 
> the specified packaging?
>
> Thank you and kind regards,
> Matthias
>
>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/983847be-13cf-4133-89c9-ff7e866eca30n%40googlegroups.com.

[dspace-tech] DSpace 7.6.1 and Deepgreen: SWORD v2 Deposit via METSMODS packaging?

[Matthias Letsch]

Hi there,

This question is primarily aimed at my colleagues from Germany who 
participate in DeepGreen (https://info.oa-deepgreen.de) and/or people who 
are familiar with the Swordv2 API...

We're part of DeepGreen and want to deposit the articles via the SWORD v2 
interface. In DSpace, SWORD v2 is enabled and the deposit works in 
principle, e.g. via console commands.

I was told to use the method http://purl.org/net/sword/package/METSMODS in 
the DeepGreen Sword Client. Also, all other details are correct (SWORD 
username, password, collection). Still the deposit doesn't work. 

When trying to deposit an example via the console, an error message tells 
me that there is no ingester configured for METSMODS:
(#=password)

curl -i --data-binary "@example.zip" -H "Content-Disposition:attachment; 
filename=example.zip" -H "Content-Type:application/zip" -H 
"Packaging:http://purl.org/net/sword/package/METSMODS; -u 
u...@hohpublica.de:# -X POST 
https://hohpublica.uni-hohenheim.de/server/swordv2/collection/123456789/15867

Result:

HTTP/1.1 100 Continue

HTTP/1.1 415 415
Date: Wed, 19 Jun 2024 08:24:20 GMT
Server: Apache/2.4.38 (Debian)
Content-Language: en,de
Content-Type: text/xml;charset=UTF-8
Transfer-Encoding: chunked


http://purl.org/net/sword/error/ErrorContent; 
xmlns:sword="http://purl.org/net/sword/terms/;>http://www.w3.org/2005/Atom;>ERRORhttp://www.w3.org/2005/Atom;>2024-06-19T10:24:20Zhttp://www.dspace.org/ns/sword/2.0/; version="2.0" 
xmlns:atom="http://www.w3.org/2005/Atom;>u...@uni-hohenheim.deProcessing
 
failedhttp://www.w3.org/2005/Atom;>No ingester configured for this 
package 
typeorg.swordapp.server.SwordError: 
No ingester configured for this package type
at ...

It seems like there is no ingester for METSMODS in DSpace 7...

Is there anyone for whom the deposit from Deepgreen SWORD v2 to DSpace 7 
already works? What do I have to configure so that the deposit works via 
the specified packaging?

Thank you and kind regards,
Matthias

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/1b6c08b6-e098-4fd2-aff9-87d2c138ae95n%40googlegroups.com.

[dspace-tech] Re: Researcher profile not yet associated on DSpace 7.6.1

[Lewatle Johannes Phaladi]

Hello Tim,

Thanks a lot, I am following on solution you have shared.

Regards,
Lewatle 

On Friday 14 June 2024 at 20:01:47 UTC+2 DSpace Technical Support wrote:

> Hi Lewatle,
>
> When using the Troubleshooting guide 
> ,
>  
> I highly recommend trying to look for the error messages yourself, as it 
> can help you find a quicker solution.  Many errors you find may provide 
> exact details on what is wrong, or at least give you a message you can use 
> to search the mailing lists & documentation for answers.
>
> In this situation, the underlying error can be found in the DSpace log 
> that you shared.
>
> 2024-06-12 14:58:17,499 ERROR unknown unknown 
> org.dspace.authenticate.OrcidAuthenticationBean @ An error occurs 
> registering a new EPerson from ORCID
> java.lang.IllegalStateException: The email is configured private on orcid
> at 
> org.dspace.authenticate.OrcidAuthenticationBean.lambda$registerNewEPerson$0(OrcidAuthenticationBean.java:220)
>  
> ~[dspace-api-7.6.1.jar:7.6.1]
> at java.util.Optional.orElseThrow(Optional.java:408) ~[?:?]
>
> Notice that error says "The email is configured private on orcid".
>
> That error is listed in our documentation for this ORCID integration, 
> along with instructions for how to fix the issue: 
>
> https://wiki.lyrasis.org/display/DSDOC7x/ORCID+Integration#ORCIDIntegration-I'munabletoauthenticateviaORCID
>
> An additional error also appears in those logs:
>
> 2024-06-12 15:25:10,139 ERROR e1a28762-e4b0-498a-bbdd-f8be639beebf 
> 57d649a8-a65d-434f-9271-99576201 
> org.dspace.app.rest.exception.DSpaceApiExceptionControllerAdvice @ An 
> exception has occurred (status:500)
> java.lang.IllegalStateException: No collection found for researcher 
> profiles
> at 
> org.dspace.profile.ResearcherProfileServiceImpl.lambda$createAndReturn$0(ResearcherProfileServiceImpl.java:132)
>  
> ~[dspace-api-7.6.1.jar:7.6.1]
> at java.util.Optional.orElseThrow(Optional.java:408) ~[?:?]
>
> Notice that the error says "No collection found for researcher profiles". 
>
> That means you also are missing a Collection which can accept "Person" 
> entities (Create a collection & select Entity Type = Person).  See the 
> documentation for Researcher Profiles, the section on "Enable the feature": 
> https://wiki.lyrasis.org/display/DSDOC7x/Researcher+Profiles
>
> Tim
>
> On Friday, June 14, 2024 at 3:37:58 AM UTC-5 joem...@gmail.com wrote:
>
>> Hello Tim,
>>
>> Please see attached images and one log file.
>>
>> Regards,
>> Lewatle 
>> On Wednesday 12 June 2024 at 17:28:44 UTC+2 DSpace Technical Support 
>> wrote:
>>
>>> Hi Lewatle,
>>>
>>> The error message you shared from dspace.log appears to be a partial 
>>> stacktrace... It's missing the most important information, which is the 
>>> error message (exception type/name/message) that appears at the top of that 
>>> stacktrace.
>>>
>>> See our Troubleshooting Guide for locating errors in DSpace 7 
>>> .
>>>   
>>> You should also check for possible errors in the User Interface by looking 
>>> in your browser's DevTools as described in that guide.
>>>
>>> Tim
>>> On Wednesday, June 12, 2024 at 8:37:48 AM UTC-5 joem...@gmail.com wrote:
>>>
 Hello,

 I have followed this documentation : 
 https://wiki.lyrasis.org/display/DSDOC7x/Researcher+Profiles but when 
 I click on create new button I get error message saying :

 [image: image_2024-06-12_153014040.png]

 The following is copy of dspace.log file 

 at 
 org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117)
  
 [spring-web-5.3.27.jar:5.3.27]
 at 
 org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:346)
  
 [spring-security-web-5.7.8.jar:5.7.8]
 at 
 org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:112)
  
 [spring-security-web-5.7.8.jar:5.7.8]
 at 
 org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:82)
  
 [spring-security-web-5.7.8.jar:5.7.8]
 at 
 org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:346)
  
 [spring-security-web-5.7.8.jar:5.7.8]
 at 
 org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter.doFilterInternal(WebAsyncManagerIntegrationFilter.java:55)
  
 [spring-security-web-5.7.8.jar:5.7.8]
 at 
 org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117)
  
 [spring-web-5.3.27.jar:5.3.27]
 at