[dspace-tech] how to change embargo startDateLimit to forever?
Hello all. Can anyone provide guidance about how to change the startDateLimit value to forever to allow a permanent embargo? Would removing that line remove the restriction? Or is it better to put something like +999MONTHS? In a previous version of DSpace, you could use the string "forever" to put a permanent embargo in place. Is there still a way to do that? Thanks! Joanna -- 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/c3594ac3-0760-41d3-bf7e-d0988a42f1c8n%40googlegroups.com.
Re: [dspace-tech] Re: DSpace 6.3 Bitstream details table - help needed
Thanks, Mark. Kelley Canon *Generations will REAP what we sow!* *Find REAP & RAMP help and LCA info on Gateway <https://gateway.sil.org/pages/viewpage.action?spaceKey=REAP=Language+and+Culture+Archives>* Language & Culture Archives - REAP Administrator SIL International On Mon, Jun 10, 2024 at 1:01 PM wrote: > On Fri, Jun 07, 2024 at 09:36:37PM +, Kelley Canon wrote: > > You don't often get email from kelley_ca...@sil.org. Learn why this is > important<https://aka.ms/LearnAboutSenderIdentification> > > Tiim - > > > > Thanks for your reply. > > > > Interesting. And a bit frustrating. It would be nice if this were > mentioned in documentation, especially when there are other tables with > "Bitstream" in the name that DO contain most of the information you'd want > about bitstreams. bitstream_id, checksum, size, etc. > > > > Water under the bridge I guess! > > > > I do wonder, however, how do we distinguish bitstream data in the > metadatavalue table - in dc.title - from true item titles? > > One way would be to join the metadatavalue and bitstream tables: > > SELECT * FROM metadatavalue AS m JOIN bitstream AS b > ON m.dspace_object_id = b.uuid limit 1; > > > > -- > Mark H. Wood > Lead Technology Analyst > > University Library > Indiana University Indianapolis > 755 W. Michigan Street > Indianapolis, IN 46202 > 317-274-0749 > library.indianapolis.iu.edu > > -- > 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/Zmc8VAgwyuMiV8mV%40iu.edu. > -- 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/CACXx6Fuj3FiRCEtaSRXxhuaT%2Bo3Y_5wvj%3D-wkY1GF6upqMF2_g%40mail.gmail.com.
[dspace-tech] Re: Dspace 7 ERROR on Production
ateLimiter: >>>> windowMs: 6 >>>> max: >>>> useProxies: true >>>> >>>> rest: >>>> ssl: true >>>> host: test.mydspace.com >>>> port: 443 >>>> nameSpace: /server >>>> >>>> However, now that we are in production, we've changed the URLs in the >>>> front and back configuration files, and the service is working really slow >>>> and throwing communications errors from time to time between the backend >>>> and frontend. >>>> >>>> The IT team has detected that this errors are happening because the >>>> front-end is passing through the WAF everytime it needs to get data from >>>> the back-end. >>>> >>>> We've tried setting the rest-host to "localhost", but DSpace won't work >>>> after that. >>>> >>>> Is there a way to make both, the frontend and backend point to >>>> "localhost" so the backend does not have to go through the firewall? >>>> >>>> Or is there another possible configuration for this to work smoothly? >>>> >>>> Best regards, >>>> >>>> Juan >>>> >>>> -- 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/bd6d1bfd-d395-4bfe-9eaf-5992591aac56n%40googlegroups.com.
[dspace-tech] Re: Dspace 7 ERROR on Production
Forgot to mention, we have SSR set in our DSpace. El miércoles, 12 de junio de 2024 a las 15:55:43 UTC-5, Juan López escribió: > Hi Tim! > > Thank you for the response. So does this mean that the IT team needs to > change the WAF configuration to fit the needs of the DSpace architecture? > > Juan. > El lunes, 10 de junio de 2024 a las 17:01:42 UTC-5, DSpace Technical > Support escribió: > >> Hi Juan, >> >> Because the frontend is a *Javascript application* (built on Angular.io), >> it runs in a user's browser by default (except when Angular's server-side >> rendering is triggered). >> >> This means that (at least some of the time) your users are running the >> frontend in their browser and only sending requests to your backend (REST >> API). >> >> This is why trying to set "rest" to "localhost" won't work. Because, in >> that scenario, your users are running the frontend in their browser and >> it's trying to connect to "localhost" (which would be the user's own >> machine, and *not* your REST API). >> >> This is exactly why the REST API always needs to be configured as a >> publicly available URL...because all your users are sending requests to the >> REST API directly whenever they are running the UI in their browser. >> >> In terms of whether the frontend needs to send every request through your >> WAF (web application firewall)...that's harder to answer. If every >> external request is going through the WAF, then these requests will need to >> as well. But, maybe there's some way to change your firewall settings to >> "trust" requests coming from your frontend? I don't know the answer here, >> but maybe someone else on this list may have ideas if they've dealt with >> this before. >> >> You also may want to review the "Common Installation Issues" >> documentation >> <https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues> >> >> in case some of the communication errors you are seeing are ones noted >> there. We also have an ongoing discussion related to performance of Server >> Side Rendering (of the frontend) which could be of interest: >> https://github.com/DSpace/dspace-angular/issues/3110 >> >> Hopefully those give you a few ideas to start with. Maybe others on this >> list will have additional suggestions. >> >> Tim >> >> On Friday, June 7, 2024 at 12:10:55 PM UTC-5 juanlop...@gmail.com wrote: >> >>> Hello! >>> >>> We're haven issues with an installation of DSpace 7.6.1. >>> >>> When we were on development mode the service was working as expected. We >>> had a DNS with https and the front-end/back-end communication was set like >>> this: >>> ui: >>> ssl: false >>> host: localhost >>> port: 4000 >>> nameSpace: / >>> rateLimiter: >>> windowMs: 6 >>> max: >>> useProxies: true >>> >>> rest: >>> ssl: true >>> host: test.mydspace.com >>> port: 443 >>> nameSpace: /server >>> >>> However, now that we are in production, we've changed the URLs in the >>> front and back configuration files, and the service is working really slow >>> and throwing communications errors from time to time between the backend >>> and frontend. >>> >>> The IT team has detected that this errors are happening because the >>> front-end is passing through the WAF everytime it needs to get data from >>> the back-end. >>> >>> We've tried setting the rest-host to "localhost", but DSpace won't work >>> after that. >>> >>> Is there a way to make both, the frontend and backend point to >>> "localhost" so the backend does not have to go through the firewall? >>> >>> Or is there another possible configuration for this to work smoothly? >>> >>> Best regards, >>> >>> Juan >>> >>> -- 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/5cd7f3c2-2ba4-4895-87b2-95b13dc46022n%40googlegroups.com.
[dspace-tech] Re: Dspace 7 ERROR on Production
Hi Tim! Thank you for the response. So does this mean that the IT team needs to change the WAF configuration to fit the needs of the DSpace architecture? Juan. El lunes, 10 de junio de 2024 a las 17:01:42 UTC-5, DSpace Technical Support escribió: > Hi Juan, > > Because the frontend is a *Javascript application* (built on Angular.io), > it runs in a user's browser by default (except when Angular's server-side > rendering is triggered). > > This means that (at least some of the time) your users are running the > frontend in their browser and only sending requests to your backend (REST > API). > > This is why trying to set "rest" to "localhost" won't work. Because, in > that scenario, your users are running the frontend in their browser and > it's trying to connect to "localhost" (which would be the user's own > machine, and *not* your REST API). > > This is exactly why the REST API always needs to be configured as a > publicly available URL...because all your users are sending requests to the > REST API directly whenever they are running the UI in their browser. > > In terms of whether the frontend needs to send every request through your > WAF (web application firewall)...that's harder to answer. If every > external request is going through the WAF, then these requests will need to > as well. But, maybe there's some way to change your firewall settings to > "trust" requests coming from your frontend? I don't know the answer here, > but maybe someone else on this list may have ideas if they've dealt with > this before. > > You also may want to review the "Common Installation Issues" documentation > <https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues> > > in case some of the communication errors you are seeing are ones noted > there. We also have an ongoing discussion related to performance of Server > Side Rendering (of the frontend) which could be of interest: > https://github.com/DSpace/dspace-angular/issues/3110 > > Hopefully those give you a few ideas to start with. Maybe others on this > list will have additional suggestions. > > Tim > > On Friday, June 7, 2024 at 12:10:55 PM UTC-5 juanlop...@gmail.com wrote: > >> Hello! >> >> We're haven issues with an installation of DSpace 7.6.1. >> >> When we were on development mode the service was working as expected. We >> had a DNS with https and the front-end/back-end communication was set like >> this: >> ui: >> ssl: false >> host: localhost >> port: 4000 >> nameSpace: / >> rateLimiter: >> windowMs: 6 >> max: >> useProxies: true >> >> rest: >> ssl: true >> host: test.mydspace.com >> port: 443 >> nameSpace: /server >> >> However, now that we are in production, we've changed the URLs in the >> front and back configuration files, and the service is working really slow >> and throwing communications errors from time to time between the backend >> and frontend. >> >> The IT team has detected that this errors are happening because the >> front-end is passing through the WAF everytime it needs to get data from >> the back-end. >> >> We've tried setting the rest-host to "localhost", but DSpace won't work >> after that. >> >> Is there a way to make both, the frontend and backend point to >> "localhost" so the backend does not have to go through the firewall? >> >> Or is there another possible configuration for this to work smoothly? >> >> Best regards, >> >> Juan >> >> -- 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/442e1a5c-d8c1-4fb5-b4ee-bc1173a427b8n%40googlegroups.com.
[dspace-tech] Re: Missing button on submitting an item to a collection
Tim, I've tested the method you noted and it worked as described. Thank you for this information! BW On Wednesday, June 12, 2024 at 10:38:43 AM UTC-5 DSpace Technical Support wrote: > Hi, > > This issue is noted in a ticket at > https://github.com/DSpace/dspace-angular/issues/2556 > > As I've also noted in that ticket, there is a way to achieve the same > behavior from DSpace 7 (to submit to the current collection). But, the > process is not as user friendly as a button. See this comment: > https://github.com/DSpace/dspace-angular/issues/2556#issuecomment-2163345393 > > This ticket/task is still waiting on a volunteer developer. I'd also like > to see this improvement as it will improve usability. But, DSpace is > built/maintained by volunteers & has no centralized developer team. > Therefore, I'm still waiting to find a volunteer for this task. > > Tim > On Wednesday, June 12, 2024 at 8:19:42 AM UTC-5 bwe...@gmail.com wrote: > >> Adding the missing images for the above message. >> [image: Screenshot 2024-06-11 at 10.08.55 AM.png] >> >> [image: Screenshot 2024-06-11 at 10.06.32 AM.png] >> >> BW >> On Wednesday, June 12, 2024 at 7:27:00 AM UTC-5 hb wooley wrote: >> >>> 1 - In the new DSpace 7 UI there is not a button "Submit to this >>> Collection" on the collection home page like in DSpace 6. How would I add a >>> button to the DSpace 7 collection home page like the button on the >>> collection home page in DSpace 6? >>> [image: Screenshot 2024-06-11 at 10.08.55 AM.png] >>> >>> 2 - In the admin side menu on DSpace 7 UI, when submitting a new item, a >>> popup menu appears "New Item ==> Create a new item in". The problem I'm >>> having is the parent community and collection name are not displayed ,which >>> causes a problem, because I do not know where the item is being submitted >>> too. >>> Example: My communities, collections, etc... look like this: >>> >>>- ORG_1 >>> - LAB_1 >>> - Publication >>> - Technical Report >>> - Special Report >>> - Technical Note >>> - Miscellaneous Paper >>> - LAB_2 >>> - Publication >>> - Technical Report >>> - Special Report >>> - Technical Note >>> - Miscellaneous Paper >>> - ORG_2 >>>- LAB_1 >>> - Publication >>> - Technical Report >>> - Special Report >>> - Technical Note >>> - Miscellaneous Paper >>> - LAB_2 >>> - Publication >>> - Technical Report >>> - Special Report >>> - Technical Note >>> - Miscellaneous Paper >>> >>> >>> The drop down displays only : [image: Screenshot 2024-06-11 at >>> 10.06.32 AM.png] >>> I would like for the dropdown to contain the full path of the parent >>> child relationship. >>> Example: >>> 1 - ORG_1 - LAB_1 -Publication - Technical Report >>> 2 - ORG_2 - LAB_1 -Publication - Special Report >>> >>> How would I modify the Angular code to show the full breadcrumb path?Any >>> help would be appreciated. >>> >>> -- 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/10793db8-f60d-4330-a3d1-2786196d2e53n%40googlegroups.com.
[dspace-tech] Re: Problem with the maximum file upload size
Hello,
I have added the following lines in dspace.cfg, restarted Tomcat, and it
is already working. I have been able to upload documents larger than 512MB.
*# Maximum size of a single uploaded file (default =
1MB)spring.servlet.multipart.max-file-size = 1024MB# Maximum size of a
multipart request (i.e. max total size of all files in one request)
(default = 10MB)spring.servlet.multipart.max-request-size = 2048MB*
Thank you all very much!
El miércoles, 12 de junio de 2024 a las 16:55:29 UTC+2, DSpace Technical
Support escribió:
> The answer here depends on the version of DSpace. The "upload.max"
> setting only works in DSpace 6 and below.
>
> As of DSpace 7 (and above), the correct settings are those
> "spring.servlet.*" settings detailed by BW. This is because the file
> upload limitations are now enforced by Spring Boot.
>
> See also the DSpace 7 File Upload step documentation:
> https://wiki.lyrasis.org/display/DSDOC7x/Submission+User+Interface#SubmissionUserInterface-ConfiguringtheFileUploadstep
>
> Tim
>
> On Wednesday, June 12, 2024 at 8:14:00 AM UTC-5 bwe...@gmail.com wrote:
>
>> You can add the below to your dspace/config/local.cfg
>>
>> # EXAMPLE OVERRIDE:
>> # By uncommenting the below Spring Boot settings, you can increase or
>> decrease the maximum upload size.
>> # These defaults are specified in
>> [dspace-src]/dspace-server-webapp/src/main/resources/application.properties
>> # but may be overridden in this local.cfg
>> #
>> # Maximum size of a single uploaded file (default = 1MB)
>> spring.servlet.multipart.max-file-size = 512MB
>>
>> # Maximum size of a multipart request (i.e. max total size of all files
>> in one request) (default = 10MB)
>> spring.servlet.multipart.max-request-size = 512MB
>>
>> You might also need to modify your web server configuration (ssl.conf)
>> Apache 2.4.6 example:
>>
>> #LimitRequestBody bytes
>> LimitRequestBody 524295
>>
>> Nginx example:
>> location /uploads {
>> client_max_body_size 512M;
>> }
>>
>> I did not know about the upload.max (Julio) in the dspace.cfg. See
>> dspace-api/src/main/java/org/dspace/submit/model/UploadConfiguration.java
>>
>> BW
>>
>> On Wednesday, June 12, 2024 at 8:02:47 AM UTC-5 Julio wrote:
>>
>>> Hello, to change the maximum size of the files that can be uploaded to
>>> Dspace, you must edit the dspace.cfg file and modify the parameter:
>>> upload.max, this value must be in bytes, if you set -1, there will be no
>>> limit.
>>>
>>> I hope it is useful to you.
>>>
>>> Greetings
>>>
>>> El miércoles, 12 de junio de 2024 a las 12:04:14 UTC+2, Javi Rojo Díaz
>>> escribió:
>>>
>>>> Good morning.
>>>>
>>>> We are having problems uploading files to items in DSpace 7.6, and it
>>>> seems that it's due to the upload file size limit. Based on the tests I've
>>>> been doing, it gives an error when the file is over 500MB.
>>>>
>>>> Is it correct that the file size limit is 500MB? If so, can this limit
>>>> be increased and where would it be configured?
>>>>
>>>>
>>>> Thank you very much, everyone!
>>>>
>>>
--
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/669b8ebe-25c3-4871-8b74-49763590f9e9n%40googlegroups.com.
[dspace-tech] Re: Missing button on submitting an item to a collection
Hi, This issue is noted in a ticket at https://github.com/DSpace/dspace-angular/issues/2556 As I've also noted in that ticket, there is a way to achieve the same behavior from DSpace 7 (to submit to the current collection). But, the process is not as user friendly as a button. See this comment: https://github.com/DSpace/dspace-angular/issues/2556#issuecomment-2163345393 This ticket/task is still waiting on a volunteer developer. I'd also like to see this improvement as it will improve usability. But, DSpace is built/maintained by volunteers & has no centralized developer team. Therefore, I'm still waiting to find a volunteer for this task. Tim On Wednesday, June 12, 2024 at 8:19:42 AM UTC-5 bwe...@gmail.com wrote: > Adding the missing images for the above message. > [image: Screenshot 2024-06-11 at 10.08.55 AM.png] > > [image: Screenshot 2024-06-11 at 10.06.32 AM.png] > > BW > On Wednesday, June 12, 2024 at 7:27:00 AM UTC-5 hb wooley wrote: > >> 1 - In the new DSpace 7 UI there is not a button "Submit to this >> Collection" on the collection home page like in DSpace 6. How would I add a >> button to the DSpace 7 collection home page like the button on the >> collection home page in DSpace 6? >> [image: Screenshot 2024-06-11 at 10.08.55 AM.png] >> >> 2 - In the admin side menu on DSpace 7 UI, when submitting a new item, a >> popup menu appears "New Item ==> Create a new item in". The problem I'm >> having is the parent community and collection name are not displayed ,which >> causes a problem, because I do not know where the item is being submitted >> too. >> Example: My communities, collections, etc... look like this: >> >>- ORG_1 >> - LAB_1 >> - Publication >> - Technical Report >> - Special Report >> - Technical Note >> - Miscellaneous Paper >> - LAB_2 >> - Publication >> - Technical Report >> - Special Report >> - Technical Note >> - Miscellaneous Paper >> - ORG_2 >>- LAB_1 >> - Publication >> - Technical Report >> - Special Report >> - Technical Note >> - Miscellaneous Paper >> - LAB_2 >> - Publication >> - Technical Report >> - Special Report >> - Technical Note >> - Miscellaneous Paper >> >> >> The drop down displays only : [image: Screenshot 2024-06-11 at 10.06.32 >> AM.png] >> I would like for the dropdown to contain the full path of the parent >> child relationship. >> Example: >> 1 - ORG_1 - LAB_1 -Publication - Technical Report >> 2 - ORG_2 - LAB_1 -Publication - Special Report >> >> How would I modify the Angular code to show the full breadcrumb path?Any >> help would be appreciated. >> >> -- 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/34335c2b-530c-434b-bab7-b15ad77b732an%40googlegroups.com.
[dspace-tech] Re: Researcher profile not yet associated on DSpace 7.6.1
va:178) > > [catalina.jar:9.0.85] > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153) > > [catalina.jar:9.0.85] > at > org.springframework.boot.web.servlet.support.ErrorPageFilter.doFilter(ErrorPageFilter.java:126) > > [spring-boot-2.7.12.jar:2.7.12] > at > org.springframework.boot.web.servlet.support.ErrorPageFilter.access$000(ErrorPageFilter.java:64) > > [spring-boot-2.7.12.jar:2.7.12] > at > org.springframework.boot.web.servlet.support.ErrorPageFilter$1.doFilterInternal(ErrorPageFilter.java:101) > > [spring-boot-2.7.12.jar:2.7.12] > at > org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117) > > [spring-web-5.3.27.jar:5.3.27] > at > org.springframework.boot.web.servlet.support.ErrorPageFilter.doFilter(ErrorPageFilter.java:119) > > [spring-boot-2.7.12.jar:2.7.12] > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178) > > [catalina.jar:9.0.85] > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153) > > [catalina.jar:9.0.85] > at > org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:201) > > [spring-web-5.3.27.jar:5.3.27] > at > org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117) > > [spring-web-5.3.27.jar:5.3.27] > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178) > > [catalina.jar:9.0.85] > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153) > > [catalina.jar:9.0.85] > at > org.springframework.web.filter.ForwardedHeaderFilter.doFilterInternal(ForwardedHeaderFilter.java:156) > > [spring-web-5.3.27.jar:5.3.27] > at > org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117) > > [spring-web-5.3.27.jar:5.3.27] > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178) > > [catalina.jar:9.0.85] > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153) > > [catalina.jar:9.0.85] > at > org.apache.logging.log4j.web.Log4jServletFilter.doFilter(Log4jServletFilter.java:71) > > [log4j-web-2.20.0.jar:2.20.0] > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178) > > [catalina.jar:9.0.85] > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153) > > [catalina.jar:9.0.85] > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:168) > > [catalina.jar:9.0.85] > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90) > > [catalina.jar:9.0.85] > at > org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481) > > [catalina.jar:9.0.85] > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130) > [catalina.jar:9.0.85] > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93) > [catalina.jar:9.0.85] > at > org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:670) > > [catalina.jar:9.0.85] > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) > > [catalina.jar:9.0.85] > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342) > [catalina.jar:9.0.85] > at > org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:390) > [tomcat-coyote.jar:9.0.85] > at > org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63) > > [tomcat-coyote.jar:9.0.85] > at > org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:928) > > [tomcat-coyote.jar:9.0.85] > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1794) > > [tomcat-coyote.jar:9.0.85] > at > org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52) > > [tomcat-coyote.jar:9.0.85] > at > org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191) > > [tomcat-util.jar:9.0.85] > at > org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) &
[dspace-tech] Re: Problem with the maximum file upload size
The answer here depends on the version of DSpace. The "upload.max" setting
only works in DSpace 6 and below.
As of DSpace 7 (and above), the correct settings are those
"spring.servlet.*" settings detailed by BW. This is because the file
upload limitations are now enforced by Spring Boot.
See also the DSpace 7 File Upload step
documentation:
https://wiki.lyrasis.org/display/DSDOC7x/Submission+User+Interface#SubmissionUserInterface-ConfiguringtheFileUploadstep
Tim
On Wednesday, June 12, 2024 at 8:14:00 AM UTC-5 bwe...@gmail.com wrote:
> You can add the below to your dspace/config/local.cfg
>
> # EXAMPLE OVERRIDE:
> # By uncommenting the below Spring Boot settings, you can increase or
> decrease the maximum upload size.
> # These defaults are specified in
> [dspace-src]/dspace-server-webapp/src/main/resources/application.properties
> # but may be overridden in this local.cfg
> #
> # Maximum size of a single uploaded file (default = 1MB)
> spring.servlet.multipart.max-file-size = 512MB
>
> # Maximum size of a multipart request (i.e. max total size of all files in
> one request) (default = 10MB)
> spring.servlet.multipart.max-request-size = 512MB
>
> You might also need to modify your web server configuration (ssl.conf)
> Apache 2.4.6 example:
>
> #LimitRequestBody bytes
> LimitRequestBody 524295
>
> Nginx example:
> location /uploads {
> client_max_body_size 512M;
> }
>
> I did not know about the upload.max (Julio) in the dspace.cfg. See
> dspace-api/src/main/java/org/dspace/submit/model/UploadConfiguration.java
>
> BW
>
> On Wednesday, June 12, 2024 at 8:02:47 AM UTC-5 Julio wrote:
>
>> Hello, to change the maximum size of the files that can be uploaded to
>> Dspace, you must edit the dspace.cfg file and modify the parameter:
>> upload.max, this value must be in bytes, if you set -1, there will be no
>> limit.
>>
>> I hope it is useful to you.
>>
>> Greetings
>>
>> El miércoles, 12 de junio de 2024 a las 12:04:14 UTC+2, Javi Rojo Díaz
>> escribió:
>>
>>> Good morning.
>>>
>>> We are having problems uploading files to items in DSpace 7.6, and it
>>> seems that it's due to the upload file size limit. Based on the tests I've
>>> been doing, it gives an error when the file is over 500MB.
>>>
>>> Is it correct that the file size limit is 500MB? If so, can this limit
>>> be increased and where would it be configured?
>>>
>>>
>>> Thank you very much, everyone!
>>>
>>
--
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/173c111e-93af-461a-bf70-e182fdea5b13n%40googlegroups.com.
[dspace-tech] Researcher profile not yet associated on DSpace 7.6.1
] at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:201) [spring-web-5.3.27.jar:5.3.27] at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117) [spring-web-5.3.27.jar:5.3.27] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178) [catalina.jar:9.0.85] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153) [catalina.jar:9.0.85] at org.springframework.web.filter.ForwardedHeaderFilter.doFilterInternal(ForwardedHeaderFilter.java:156) [spring-web-5.3.27.jar:5.3.27] at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117) [spring-web-5.3.27.jar:5.3.27] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178) [catalina.jar:9.0.85] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153) [catalina.jar:9.0.85] at org.apache.logging.log4j.web.Log4jServletFilter.doFilter(Log4jServletFilter.java:71) [log4j-web-2.20.0.jar:2.20.0] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178) [catalina.jar:9.0.85] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153) [catalina.jar:9.0.85] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:168) [catalina.jar:9.0.85] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90) [catalina.jar:9.0.85] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481) [catalina.jar:9.0.85] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130) [catalina.jar:9.0.85] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93) [catalina.jar:9.0.85] at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:670) [catalina.jar:9.0.85] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) [catalina.jar:9.0.85] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342) [catalina.jar:9.0.85] at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:390) [tomcat-coyote.jar:9.0.85] at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63) [tomcat-coyote.jar:9.0.85] at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:928) [tomcat-coyote.jar:9.0.85] at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1794) [tomcat-coyote.jar:9.0.85] at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52) [tomcat-coyote.jar:9.0.85] at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191) [tomcat-util.jar:9.0.85] at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) [tomcat-util.jar:9.0.85] at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-util.jar:9.0.85] at java.lang.Thread.run(Thread.java:829) [?:?] Regards, Lewatle -- 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/dd4b2210-1af9-4729-8c5a-d8294687be45n%40googlegroups.com.
[dspace-tech] Re: Problem with the maximum file upload size
You can add the below to your dspace/config/local.cfg
# EXAMPLE OVERRIDE:
# By uncommenting the below Spring Boot settings, you can increase or
decrease the maximum upload size.
# These defaults are specified in
[dspace-src]/dspace-server-webapp/src/main/resources/application.properties
# but may be overridden in this local.cfg
#
# Maximum size of a single uploaded file (default = 1MB)
spring.servlet.multipart.max-file-size = 512MB
# Maximum size of a multipart request (i.e. max total size of all files in
one request) (default = 10MB)
spring.servlet.multipart.max-request-size = 512MB
You might also need to modify your web server configuration (ssl.conf)
Apache 2.4.6 example:
#LimitRequestBody bytes
LimitRequestBody 524295
Nginx example:
location /uploads {
client_max_body_size 512M;
}
I did not know about the upload.max (Julio) in the dspace.cfg. See
dspace-api/src/main/java/org/dspace/submit/model/UploadConfiguration.java
BW
On Wednesday, June 12, 2024 at 8:02:47 AM UTC-5 Julio wrote:
> Hello, to change the maximum size of the files that can be uploaded to
> Dspace, you must edit the dspace.cfg file and modify the parameter:
> upload.max, this value must be in bytes, if you set -1, there will be no
> limit.
>
> I hope it is useful to you.
>
> Greetings
>
> El miércoles, 12 de junio de 2024 a las 12:04:14 UTC+2, Javi Rojo Díaz
> escribió:
>
>> Good morning.
>>
>> We are having problems uploading files to items in DSpace 7.6, and it
>> seems that it's due to the upload file size limit. Based on the tests I've
>> been doing, it gives an error when the file is over 500MB.
>>
>> Is it correct that the file size limit is 500MB? If so, can this limit be
>> increased and where would it be configured?
>>
>>
>> Thank you very much, everyone!
>>
>
--
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/46de46eb-8096-431d-8a01-433aae9ab6f4n%40googlegroups.com.
[dspace-tech] Normalize typologies for bibtex
In the Dspace 5.1 CRIS version, in the detail of an item you can export the metadata in bibtext, the first value is dc.type, but the value that is recorded does not correspond to the value normalized by bibtext. How could a conversion be made from the value of the item in dc.type to the corresponding value normalized according to bibtext? -- 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/838eb564-76a1-407d-9628-29e4e4601646n%40googlegroups.com.
[dspace-tech] Re: Problem with the maximum file upload size
Hello, to change the maximum size of the files that can be uploaded to Dspace, you must edit the dspace.cfg file and modify the parameter: upload.max, this value must be in bytes, if you set -1, there will be no limit. I hope it is useful to you. Greetings El miércoles, 12 de junio de 2024 a las 12:04:14 UTC+2, Javi Rojo Díaz escribió: > Good morning. > > We are having problems uploading files to items in DSpace 7.6, and it > seems that it's due to the upload file size limit. Based on the tests I've > been doing, it gives an error when the file is over 500MB. > > Is it correct that the file size limit is 500MB? If so, can this limit be > increased and where would it be configured? > > > Thank you very much, everyone! > -- 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/c6d75781-bfa5-4f16-a9a0-b10eeef479d0n%40googlegroups.com.
[dspace-tech] Missing button on submitting an item to a collection
1 - In the new DSpace 7 UI there is not a button "Submit to this Collection" on the collection home page like in DSpace 6. How would I add a button to the DSpace 7 collection home page like the button on the collection home page in DSpace 6? [image: Screenshot 2024-06-11 at 10.08.55 AM.png] 2 - In the admin side menu on DSpace 7 UI, when submitting a new item, a popup menu appears "New Item ==> Create a new item in". The problem I'm having is the parent community and collection name are not displayed ,which causes a problem, because I do not know where the item is being submitted too. Example: My communities, collections, etc... look like this: - ORG_1 - LAB_1 - Publication - Technical Report - Special Report - Technical Note - Miscellaneous Paper - LAB_2 - Publication - Technical Report - Special Report - Technical Note - Miscellaneous Paper - ORG_2 - LAB_1 - Publication - Technical Report - Special Report - Technical Note - Miscellaneous Paper - LAB_2 - Publication - Technical Report - Special Report - Technical Note - Miscellaneous Paper The drop down displays only : [image: Screenshot 2024-06-11 at 10.06.32 AM.png] I would like for the dropdown to contain the full path of the parent child relationship. Example: 1 - ORG_1 - LAB_1 -Publication - Technical Report 2 - ORG_2 - LAB_1 -Publication - Special Report How would I modify the Angular code to show the full breadcrumb path?Any help would be appreciated. -- 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/df5c873a-3988-4c0e-8de4-a3f8e32c3ec7n%40googlegroups.com.
[dspace-tech] Problem with the maximum file upload size
Good morning. We are having problems uploading files to items in DSpace 7.6, and it seems that it's due to the upload file size limit. Based on the tests I've been doing, it gives an error when the file is over 500MB. Is it correct that the file size limit is 500MB? If so, can this limit be increased and where would it be configured? Thank you very much, everyone! -- 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/7a2558bc-9744-4c94-b3a5-d5df560f67c3n%40googlegroups.com.
[dspace-tech] Re: Dspace 1.4.2 - host of issues
Thank you, Tim! On Friday, June 7, 2024 at 1:50:06 PM UTC-7 DSpace Technical Support wrote: > Hi Deborah, > > We also do have a Migration guide which you may wish to be aware of. This > guide should walk you through the basic steps of migrating content from any > older version of DSpace into a fresh install of DSpace 7. > > https://wiki.lyrasis.org/display/DSDOC7x/Migrating+DSpace+to+a+new+server > > Tim > > On Wednesday, June 5, 2024 at 1:38:03 PM UTC-5 deborah.bast...@gmail.com > wrote: > >> Thank you, Edmund! >> >> On Tuesday, June 4, 2024 at 12:21:47 AM UTC-7 Edmund Balnaves wrote: >> >>> Given you are how many versions behind I suggest you would be best to >>> export your data and bring that into an new server. The export/import >>> functions are fortunately pretty consistent over time. >>> >>> * export your collection using the item exporter in your current system >>> [dspace]/bin/export --type=COLLECTION --id=collID --dest=dest_dir >>> --number=seq_num >>> * set up an entirely new DSpace server on V7 ( you will need a beefier >>> server with at least 16gb memory 4 cpu min) >>> * restore your items >>> * configure the UI with your branding. >>> >>> There is pretty good documentation for V7 installation, but it is a >>> quite a technical task. >>> >>> Edmund Balnaves >>> Prosentient Systems >>> >>> >>> On Tuesday, June 4, 2024 at 9:10:41 AM UTC+10 Deborah wrote: >>> >>>> Hello, >>>> >>>> At our very small university library we are at the very beginning >>>> stages of trying to fix, upgrade, change our situation with our >>>> Institutional Repository. I’m the head of the library here, but >>>> unfamiliar >>>> with the technology requirements to fix, or even have a constructive >>>> conversation to unravel the issues. Our contracted tech team have asked >>>> me >>>> to seek some initial guidance on their behalf. >>>> >>>> Here’s the situation so far. In 2020, Dspace 1.4.2 was installed on >>>> server that was, as I understand, cobbled together, and data input began >>>> later that year. >>>> >>>> In Fall 2023, the message on our browsers indicated an expired >>>> certificate. Currently the expiration is almost 9 months old. We’ve had >>>> discussions with our contracted technology support specialists who began >>>> just last year and can’t find any documentation from the previous tech >>>> specialist to guide them to the next step. >>>> >>>> In my small amount of research, I’ve found that we sorely need to >>>> update the software, but my understanding is that we need to do this is in >>>> steps with 5.0 first and then 7.x. Is that correct? >>>> >>>> Secondly, we’re wondering if the server is long in the tooth, and needs >>>> replacement. There is an idea to split out to virtual servers that might >>>> be >>>> purchased for another couple of departments. And lastly, maybe it’s just a >>>> new certificate we need, then the software update. >>>> >>>> Have any of you had a similar situation with such old and unsupported >>>> software? Would you care to share how you resolved this? What would be >>>> the >>>> most basic construction/upgrade? What is the licensing cost of a >>>> certificate? Would it be advantageous to start again from scratch and >>>> reenter the data? >>>> >>>> Any assistance you can provide will be enormously appreciated. >>>> >>>> >>>> >>>> All my best, >>>> >>>> Deborah >>>> >>> -- 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/900d9f81-4a6a-4979-83b7-afb871a75417n%40googlegroups.com.
Re: [dspace-tech] Re: sword fails authentication for DSpace 7.6.1
Make sure that if you’re using SWORDv1, the account may require ADMIN privileges on the collection due to this bug: https://github.com/DSpace/DSpace/issues/8647 Simply adding the user to a SUBMIT group will not work. I have seen this in our DSpace 7.5 instance. -- Sean From: dspace-tech@googlegroups.com on behalf of Joyner Library Date: Tuesday, June 11, 2024 at 1:15 PM To: DSpace Technical Support Subject: Re: [dspace-tech] Re: sword fails authentication for DSpace 7.6.1 Caution! This message was sent from outside the University of Manitoba. Hi All, Creating an account through CLI allowed me to download the service document. Vireo 4 is happy and able to deposit dissertations using SWORD client. Thank you! On Monday, June 10, 2024 at 3:23:56 PM UTC-4 mw...@iu.edu wrote: On Fri, Jun 07, 2024 at 08:46:27PM +, DSpace Technical Support wrote: > I think the answer may be that SWORD doesn't support LDAP authentication (and > it looks like that's what you are using based on the logs you shared). SWORD > *only supports* PasswordAuthentication (DSpace's internal authentication > system). So, to login to SWORD, you'd need to use an internally stored > username & password. > > Tim There's the today answer (use password authentication) and there's the todo answer (this should not have errored, and probably should not have failed). LDAP authentication as implemented in DSpace uses a username/password pair so, if this isn't working, it's probably broken rather than impossible. The result is an NPE, which IMHO is always an indicator of code that needs fixing. The site of the NPE from the stack trace should suggest how we came to be setting attributes on a nonexistent request. Although it seems fairly obvious: 'o.d.sword.SWORDAuthenticator.authenticates' passes a null 'HttpServletRequest' to 'AuthenticationService.authenticate', and that service would pass it on down to 'LDAPAuthentication.authenticate' if so configured. (Noted in passing: there's another class o.d.sword.SWORDAuthentication with an identically named method, which class seems to be used nowhere in DSpace.) We need a Github Issue for this. It's probably best if it comes from someone who's actually observed the problem and can provide logs. > On Tuesday, June 4, 2024 at 11:27:39 AM UTC-5 Joyner Library wrote: > Hi All, > > We have enabled sword version 1 in the local configuration but haven't > changed other sword settings. I can sign on to the frontend and /server too. > When we try to download https://irdev.ecu.edu/server/sword/servicedocument it > gives the white label error page. The DSpace log file shows: > > INFO unknown 4f89ae89-9baf-49cc-b800-3205dbddef5d > org.dspace.authenticate.LDAPAuthentication @ > anonymous:session_id=0:ip_addr=150.216.*.*:auth:attempting trivial auth of > user=crimin > > 2024-06-04 12:00:32,819 ERROR unknown unknown > org.springframework.boot.web.servlet.support.ErrorPageFilter @ Forwarding to > error page from request [/sword/servicedocument] due to exception > [java.lang.NullPointerException: Cannot invoke > "javax.servlet.http.HttpServletRequest.setAttribute(String, Object)" because > "request" is null] > > How do I sign on successfully to the sword service? > > Nick Crimi > ECU Libraries -- Mark H. Wood Lead Technology Analyst University Library Indiana University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 library.indianapolis.iu.edu<http://library.indianapolis.iu.edu> -- 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<mailto:dspace-tech+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/3c7d1871-42b6-4f9c-82b3-ede1bff3a393n%40googlegroups.com<https://groups.google.com/d/msgid/dspace-tech/3c7d1871-42b6-4f9c-82b3-ede1bff3a393n%40googlegroups.com?utm_medium=email_source=footer>. -- 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/YT3PR01MB108152D8F575491EC3E89D743E8C72%40YT3PR01MB10815.CANPRD01.PROD.OUTLOOK.COM.
Re: [dspace-tech] Re: sword fails authentication for DSpace 7.6.1
Hi All, Creating an account through CLI allowed me to download the service document. Vireo 4 is happy and able to deposit dissertations using SWORD client. Thank you! On Monday, June 10, 2024 at 3:23:56 PM UTC-4 mw...@iu.edu wrote: > On Fri, Jun 07, 2024 at 08:46:27PM +, DSpace Technical Support wrote: > > I think the answer may be that SWORD doesn't support LDAP authentication > (and it looks like that's what you are using based on the logs you shared). > SWORD *only supports* PasswordAuthentication (DSpace's internal > authentication system). So, to login to SWORD, you'd need to use an > internally stored username & password. > > > > Tim > > There's the today answer (use password authentication) and there's the > todo answer (this should not have errored, and probably should not > have failed). > > LDAP authentication as implemented in DSpace uses a username/password > pair so, if this isn't working, it's probably broken rather than > impossible. The result is an NPE, which IMHO is always an indicator > of code that needs fixing. The site of the NPE from the stack trace > should suggest how we came to be setting attributes on a nonexistent > request. Although it seems fairly obvious: > 'o.d.sword.SWORDAuthenticator.authenticates' passes a null > 'HttpServletRequest' to 'AuthenticationService.authenticate', and that > service would pass it on down to 'LDAPAuthentication.authenticate' if > so configured. > > (Noted in passing: there's another class o.d.sword.SWORDAuthentication > with an identically named method, which class seems to be used nowhere > in DSpace.) > > We need a Github Issue for this. It's probably best if it comes from > someone who's actually observed the problem and can provide logs. > > > On Tuesday, June 4, 2024 at 11:27:39 AM UTC-5 Joyner Library wrote: > > Hi All, > > > > We have enabled sword version 1 in the local configuration but haven't > changed other sword settings. I can sign on to the frontend and /server > too. When we try to download > https://irdev.ecu.edu/server/sword/servicedocument it gives the white > label error page. The DSpace log file shows: > > > > INFO unknown 4f89ae89-9baf-49cc-b800-3205dbddef5d > org.dspace.authenticate.LDAPAuthentication @ > anonymous:session_id=0:ip_addr=150.216.*.*:auth:attempting trivial auth of > user=crimin > > > > 2024-06-04 12:00:32,819 ERROR unknown unknown > org.springframework.boot.web.servlet.support.ErrorPageFilter @ Forwarding > to error page from request [/sword/servicedocument] due to exception > [java.lang.NullPointerException: Cannot invoke > "javax.servlet.http.HttpServletRequest.setAttribute(String, Object)" > because "request" is null] > > > > How do I sign on successfully to the sword service? > > > > Nick Crimi > > ECU Libraries > > -- > Mark H. Wood > Lead Technology Analyst > > University Library > Indiana University Indianapolis > 755 W. Michigan Street > Indianapolis, IN 46202 > 317-274-0749 <(317)%20274-0749> > library.indianapolis.iu.edu > -- 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/3c7d1871-42b6-4f9c-82b3-ede1bff3a393n%40googlegroups.com.
Re: [dspace-tech] High CPU usage in DSpace 7.6 leading to server issues, lots of errors/examples (crossposted from Slack)
gt;>>> x xx dspace-ui > >>>>> *.custom-file-input:lang(en)~.custom-file-label >>>>> -> unmatched* x >>>>> x xx dspace-ui > Redirecting from >>>>> /bitstreams/e524c49e-5fc2-4e74-b69d-0c890238ab3b/dow x >>>>> x xx dspace-ui > GET >>>>> /bitstreams/e524c49e-5fc2-4e74-b69d-0c890238ab3b/download 302 x >>>>> x xx dspace-ui >* ERROR Error: >>>>> Cannot set headers after they are sent to the client x* >>>>> x xx dspace-ui > at new >>>>> NodeError (node:internal/errors:405:5) x >>>>> x xx dspace-ui > at >>>>> ServerResponse.setHeader (node:_http_outgoing:648:11) x >>>>> x xx dspace-ui > at >>>>> ServerResponseService.setHeader (/opt/dspace-frontend/dist/ser x >>>>> x xx dspace-ui > at Object.next >>>>> (/opt/dspace-frontend/dist/server/9366.js:1:4722) x >>>>> x xx dspace-ui > at >>>>> ConsumerObserver2.next (/opt/dspace-frontend/dist/server/main. x >>>>> x xx dspace-ui > at >>>>> SafeSubscriber2.Subscriber2._next (/opt/dspace-frontend/dist/s x >>>>> x xx dspace-ui > at >>>>> SafeSubscriber2.Subscriber2.next (/opt/dspace-frontend/dist/se x >>>>> x xx dspace-ui > at >>>>> /opt/dspace-frontend/dist/server/main.js:1:4471483 x >>>>> x xx dspace-ui > at >>>>> OperatorSubscriber2._this._next (/opt/dspace-frontend/dist/ser x >>>>> x xx dspace-ui > at >>>>> OperatorSubscriber2.Subscriber2.next (/opt/dspace-frontend/dis x >>>>> x xx dspace-ui > code: ' >>>>> *ERR_HTTP_HEADERS_SENT*'x >>>>> x xx dspace-ui > } >>>>>x >>>>> x xx dspace-ui > 1 rules skipped due >>>>> to selector errors:x >>>>> x xx dspace-ui > >>>>> .custom-file-input:lang(en)~.custom-file-label -> unmatched x >>>>> x xx dspace-ui > Warning >>>>> [ERR_HTTP_HEADERS_SENT]: *Tried to set headers after they * x >>>>> x xx dspace-ui > GET >>>>> /items/d2d3cc05-419a-488e-912e-1ff20ab7a654 200 3281.694 ms - -x >>>>> >>>>> mqqqjmj >>>>> lq Custom Metrics qqklq Metadata >>>>> qk >>>>> x Heap Size 709.14 MiB xx App Name dspace-ui >>>>>x >>>>> x Event Loop Latency p95xx Namespace default >>>>>x >>>>> x Event Loop Latency 34.32 ms xx Version N/A >>>>>x >>>>> x Active handles10 xx Restarts 38 >>>>> x >>>>> x Active requests1 xx Uptime5m >>>>> x >>>>> x HTTP0.96 req/min xx Script path >>>>> /opt/dspace-frontend/dist/server/main.js x >>>>> x HTTP P95 Latency 4009 ms xx Script args N/A >>>>>x >>>>> x HTTP Mean Latency 868 ms xx Interpreter node >>>>> x >>>>> >>>>> We'd particularly appreciate feedback on the error messages (bolded >>>>> above): >>>>> >>>>>- 1 rules skipped due to selector errors: >>>>> - *Suggestion from Mark Wood: this is probably because we're >>>>> using Bootstrap 4 >>>>> >>>>> <https://stackoverflow.com/questions/67581454/receiving-unmatched-pseudo-class-lang-after-updating-angular>* >>>>>- .custom-file-input:lang(en)~.custom-file-label -> unmatched >>>>>- ERROR Error: Cannot set headers after they are sent to the client >>>>>- Warning [ERR_HTTP_HEADERS_SENT]: Tried to set headers after they >>>>> - *Suggestion from Mark Wood: * *The Headers Sent errors >>>>> seem to be mostly an annoyance, but the constant dumping of stack >>>>> traces >>>>> is bloating the log.* >>>>> >>>>> These errors occur constantly :'( >>>>> >>>>> *Suggestion from Mark Wood on error messages: The most serious is >>>>> probably the proxy errors. It appears that PM2 is closing proxy >>>>> connections, probably because there are too many. The machine is simply >>>>> being asked to do more work than it can handle in the available time. We >>>>> see this too, even after doubling our CPU and memory from levels that >>>>> were >>>>> quite adequate for v6. We are about to throw a big increase in resources >>>>> at v7 to see if that helps, as it has at other sites.* >>>>> >>>>> (2) Example of errors from our Apache Error Log (we run Apache to >>>>> proxy, as recommended in documentation): >>>>> >>>>> [Fri Mar 01 14:51:00.740446 2024] [proxy:error] [pid 1494894:tid >>>>> 140510257739520] [client 66.XXX.75.XXX:0] AH00898: Error reading from >>>>> remote server returned by /handle/10393/19705/simple-search >>>>> [Fri Mar 01 14:53:26.192799 2024] [proxy_http:error] [pid 1494894:tid >>>>> 140510257739520] (104)Connection reset by peer: [client 66.XXX.75.XXX:0] >>>>> AH01102: error reading status line from remote server localhost:4000 >>>>> >>>>> Some suggestions we've seen in the DSpace Slack already: >>>>> Tim Donoghue: >>>>> >>>>>- Initial increased bot traffic is common, but tends to decrease >>>>>over time >>>>>- Review major errors in DSpace/Tomcat/Postgres/etc. logs >>>>>- Enable more caching in server-side rendering as that uses the >>>>>most CPU in Node.js >>>>> - Seconded by Mark Wood: Increasing the caching will likely >>>>> reduce the CPU demand but memory demand will increase drastically. >>>>>- Mark Wood: In general, DSpace 7.x is much more computationally >>>>>expensive than the previous versions >>>>> >>>>> If you've read this far, thank you so much for your time and >>>>> consideration. The wider DSpace community seems to be struggling with >>>>> these issues, and we would all welcome your observations on these issues >>>>> and suggestions for resolving it. >>>>> >>>>> Best, >>>>> Carolyn Sullivan >>>>> >>>>> -- >>>>> 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...@googlegroups.com. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/dspace-tech/0e817201-5f4a-4fc1-9781-b462cc97134fn%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/dspace-tech/0e817201-5f4a-4fc1-9781-b462cc97134fn%40googlegroups.com?utm_medium=email_source=footer> >>>>> . >>>>> >>>>> -- >>>>> 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...@googlegroups.com. >>>>> >>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/dspace-tech/b71cc9d4-059f-4ef0-8ca1-33e60ff53aa4n%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/dspace-tech/b71cc9d4-059f-4ef0-8ca1-33e60ff53aa4n%40googlegroups.com?utm_medium=email_source=footer> >>>>> . >>>>> >>>> -- 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/d04831d1-51d4-43f9-83ea-22e9e0026264n%40googlegroups.com.
Re: [dspace-tech] Re: Problems in restoring backups
Hi Tom Switch to postgreSQL user, usually "postgres" before issuing psql command. Avoid running this as root. Regards ____ From: dspace-tech@googlegroups.com on behalf of Tom Obrien Sent: 11 June 2024 11:53 To: dspace-tech ; dspace-tech Subject: [dspace-tech] Re: Problems in restoring backups Hi all, I succefully insinstalled Dspace 7.6 on Ubuntu 22 and I am in the process of migration database from 5.3 to 7.6. However I have encountered the following challenge: sudo psql -f dspace.bak dspace [sudo] password for library: psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL: role "root" does not exist Kindly assist. Tom -- 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<mailto:dspace-tech+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CAE%2B4i98QV_8GeosDFak_JziKc0RQZp9gLVBziP1mJUVLBFyX_A%40mail.gmail.com<https://groups.google.com/d/msgid/dspace-tech/CAE%2B4i98QV_8GeosDFak_JziKc0RQZp9gLVBziP1mJUVLBFyX_A%40mail.gmail.com?utm_medium=email_source=footer>. CAUTION -EXTERNAL SENDER: Please be careful when opening links and attachments. UNAM Directorate: Information & Communication Technology Services (DICTS) -- 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/VE1PR04MB73101620A355D3A5ADEC0003C4C72%40VE1PR04MB7310.eurprd04.prod.outlook.com.
[dspace-tech] Re: Problems in restoring backups
Hi all, I succefully insinstalled Dspace 7.6 on Ubuntu 22 and I am in the process of migration database from 5.3 to 7.6. However I have encountered the following challenge: sudo psql -f dspace.bak dspace [sudo] password for library: psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL: role "root" does not exist Kindly assist. Tom -- 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/CAE%2B4i98QV_8GeosDFak_JziKc0RQZp9gLVBziP1mJUVLBFyX_A%40mail.gmail.com.
Re: [dspace-tech] High CPU usage in DSpace 7.6 leading to server issues, lots of errors/examples (crossposted from Slack)
gt;> systemd >>>> >>>> Our cache settings are set as follows: >>>> # Caching settings >>>> cache: >>>> ... >>>> serverSide: >>>> debug: false >>>> botCache: >>>> max: 1000 >>>> timeToLive: 8640 # 1 day >>>> allowStale: true >>>> anonymousCache: >>>> max: 1000 >>>> timeToLive: 1 # 10 seconds >>>> allowStale: true >>>> >>>> *The main question of our systems analyst (Francois Malric): Is this >>>> level of constantly high CPU usage is normal due to node.js? Or is it >>>> likely that our DSpace is displaying poor performance due to underlying >>>> issues?* >>>> >>>> Here are some examples of the errors we've seen: >>>> >>>> (1) From our DSpace Logs: According to this, we don't have that much >>>> traffic (HTTP 0.96 requests/minute), which would likely be higher if bot >>>> traffic was the issue. Nota bene, our pm2 monitor likely has a bug as >>>> it's >>>> showing the units as req/min; should be req/sec. >>>> >>>> lq Process List klqq dspace-ui Logs >>>> k >>>> x[ 1] dspace-ui Mem: 824 MB xx dspace-ui > The response for ' >>>> https://ruor.uottawa.ca/server/api/core/items/d2d3c x >>>> x[ 2] dspace-ui Mem: 316 MB xx dspace-ui > 1 rules skipped due >>>> to selector errors:x >>>> x[ 3] dspace-ui Mem: 777 MB xx dspace-ui > >>>> .custom-file-input:lang(en)~.custom-file-label -> unmatched x >>>> x[ 0] pm2-logrotate Mem: 45 xx dspace-ui > GET >>>> /handle/10393/19705/simple-search?query=_by=score=desc x >>>> x xx dspace-ui > *1 rules skipped >>>> due to selector errors: * x >>>> x xx dspace-ui > >>>> *.custom-file-input:lang(en)~.custom-file-label >>>> -> unmatched* x >>>> x xx dspace-ui > Redirecting from >>>> /bitstreams/e524c49e-5fc2-4e74-b69d-0c890238ab3b/dow x >>>> x xx dspace-ui > GET >>>> /bitstreams/e524c49e-5fc2-4e74-b69d-0c890238ab3b/download 302 x >>>> x xx dspace-ui >* ERROR Error: >>>> Cannot set headers after they are sent to the client x* >>>> x xx dspace-ui > at new NodeError >>>> (node:internal/errors:405:5) x >>>> x xx dspace-ui > at >>>> ServerResponse.setHeader (node:_http_outgoing:648:11) x >>>> x xx dspace-ui > at >>>> ServerResponseService.setHeader (/opt/dspace-frontend/dist/ser x >>>> x xx dspace-ui > at Object.next >>>> (/opt/dspace-frontend/dist/server/9366.js:1:4722) x >>>> x xx dspace-ui > at >>>> ConsumerObserver2.next (/opt/dspace-frontend/dist/server/main. x >>>> x xx dspace-ui > at >>>> SafeSubscriber2.Subscriber2._next (/opt/dspace-frontend/dist/s x >>>> x xx dspace-ui > at >>>> SafeSubscriber2.Subscriber2.next (/opt/dspace-frontend/dist/se x >>>> x xx dspace-ui > at >>>> /opt/dspace-frontend/dist/server/main.js:1:4471483 x >>>> x xx dspace-ui > at >>>> OperatorSubscriber2._this._next (/opt/dspace-frontend/dist/ser x >>>> x xx dspace-ui > at >>>> OperatorSubscriber2.Subscriber2.next (/opt/dspace-frontend/dis x >>>> x xx dspace-ui > code: ' >>>> *ERR_HTTP_HEADERS_SENT*'x >>>> x xx dspace-ui > } >>>>x >>>> x xx dspace-ui > 1 rule
[dspace-tech] Re: Dspace 7 ERROR on Production
Hi Juan, Because the frontend is a *Javascript application* (built on Angular.io), it runs in a user's browser by default (except when Angular's server-side rendering is triggered). This means that (at least some of the time) your users are running the frontend in their browser and only sending requests to your backend (REST API). This is why trying to set "rest" to "localhost" won't work. Because, in that scenario, your users are running the frontend in their browser and it's trying to connect to "localhost" (which would be the user's own machine, and *not* your REST API). This is exactly why the REST API always needs to be configured as a publicly available URL...because all your users are sending requests to the REST API directly whenever they are running the UI in their browser. In terms of whether the frontend needs to send every request through your WAF (web application firewall)...that's harder to answer. If every external request is going through the WAF, then these requests will need to as well. But, maybe there's some way to change your firewall settings to "trust" requests coming from your frontend? I don't know the answer here, but maybe someone else on this list may have ideas if they've dealt with this before. You also may want to review the "Common Installation Issues" documentation <https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues> in case some of the communication errors you are seeing are ones noted there. We also have an ongoing discussion related to performance of Server Side Rendering (of the frontend) which could be of interest: https://github.com/DSpace/dspace-angular/issues/3110 Hopefully those give you a few ideas to start with. Maybe others on this list will have additional suggestions. Tim On Friday, June 7, 2024 at 12:10:55 PM UTC-5 juanlop...@gmail.com wrote: > Hello! > > We're haven issues with an installation of DSpace 7.6.1. > > When we were on development mode the service was working as expected. We > had a DNS with https and the front-end/back-end communication was set like > this: > ui: > ssl: false > host: localhost > port: 4000 > nameSpace: / > rateLimiter: > windowMs: 6 > max: > useProxies: true > > rest: > ssl: true > host: test.mydspace.com > port: 443 > nameSpace: /server > > However, now that we are in production, we've changed the URLs in the > front and back configuration files, and the service is working really slow > and throwing communications errors from time to time between the backend > and frontend. > > The IT team has detected that this errors are happening because the > front-end is passing through the WAF everytime it needs to get data from > the back-end. > > We've tried setting the rest-host to "localhost", but DSpace won't work > after that. > > Is there a way to make both, the frontend and backend point to "localhost" > so the backend does not have to go through the firewall? > > Or is there another possible configuration for this to work smoothly? > > Best regards, > > Juan > > -- 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/8f178604-ca6f-416a-bf07-3fd362e1885dn%40googlegroups.com.
[dspace-tech] Re: Assistance with Configuring Multiple Asset Stores in DSpace Based on Communities
Hi Ravi, At this time, DSpace is only able to store *newly* added files in a **single assetstore**. Take a look at the documentation for assetstore / bitstream store <https://wiki.lyrasis.org/display/DSDOC7x/Storage+Layer#StorageLayer-BitstreamStore> . Essentially, the way this works is the first storage location is always numbered "0". Initially all new files are stored in that location. If, later on, you start to run out of space, you can create a new location numbered "1". At this point, **all new files** are now stored in store "1". The older store "0" is **only used** when accessing an older file which was previously saved to that location. I don't believe there's a way to send different files to different locations based on their Community or Collection. At least, I'm not aware of a way to do that. Tim On Friday, June 7, 2024 at 1:56:27 AM UTC-5 r.bha...@gmail.com wrote: > Dear All, > > I am currently working on a DSpace instance and am looking to configure > multiple asset stores such that items are stored in different asset stores > based on their respective communities. After reviewing the documentation > and various resources, I have a general idea of how to approach this, but I > would greatly appreciate guidance from the community. > > *Define Multiple Asset Stores*: II will define multiple asset stores like > so: > > [dspace]/config/spring/api/assetstore.xml > > assetstore.dir.0 = /dspace/assetstore1 > assetstore.dir.1 = /dspace/assetstore2 > > Please help, how will we call the particular asset store based on the > community document? > > Regards, > Ravi Bhardwaj > > > > > -- 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/dd6664ba-daf6-40bd-831b-d5ff5ee353ccn%40googlegroups.com.
Re: [dspace-tech] Re: dspace dump error
On Mon, Jun 10, 2024 at 07:33:36AM +, Tom Obrien wrote: > You don't often get email from tobri...@gmail.com. Learn why this is > important<https://aka.ms/LearnAboutSenderIdentification> > Dear all, > I am requesting help. > I am trying to migrate from Dspace 5 to 7.6. > When I try to get the Dspace backup using the command : "pg_dump dspace > > dspace.backup" I get the following error: > -su: dspace.backup: Permission denied The account in which you are running 'pg_dump' does not have write access in the directory where you are directing the output. -- Mark H. Wood Lead Technology Analyst University Library Indiana University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 library.indianapolis.iu.edu -- 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/ZmdTfi_ty8V8zogI%40iu.edu. signature.asc Description: PGP signature
Re: [dspace-tech] Re: sword fails authentication for DSpace 7.6.1
On Fri, Jun 07, 2024 at 08:46:27PM +, DSpace Technical Support wrote: > I think the answer may be that SWORD doesn't support LDAP authentication (and > it looks like that's what you are using based on the logs you shared). SWORD > *only supports* PasswordAuthentication (DSpace's internal authentication > system). So, to login to SWORD, you'd need to use an internally stored > username & password. > > Tim There's the today answer (use password authentication) and there's the todo answer (this should not have errored, and probably should not have failed). LDAP authentication as implemented in DSpace uses a username/password pair so, if this isn't working, it's probably broken rather than impossible. The result is an NPE, which IMHO is always an indicator of code that needs fixing. The site of the NPE from the stack trace should suggest how we came to be setting attributes on a nonexistent request. Although it seems fairly obvious: 'o.d.sword.SWORDAuthenticator.authenticates' passes a null 'HttpServletRequest' to 'AuthenticationService.authenticate', and that service would pass it on down to 'LDAPAuthentication.authenticate' if so configured. (Noted in passing: there's another class o.d.sword.SWORDAuthentication with an identically named method, which class seems to be used nowhere in DSpace.) We need a Github Issue for this. It's probably best if it comes from someone who's actually observed the problem and can provide logs. > On Tuesday, June 4, 2024 at 11:27:39 AM UTC-5 Joyner Library wrote: > Hi All, > > We have enabled sword version 1 in the local configuration but haven't > changed other sword settings. I can sign on to the frontend and /server too. > When we try to download https://irdev.ecu.edu/server/sword/servicedocument it > gives the white label error page. The DSpace log file shows: > > INFO unknown 4f89ae89-9baf-49cc-b800-3205dbddef5d > org.dspace.authenticate.LDAPAuthentication @ > anonymous:session_id=0:ip_addr=150.216.*.*:auth:attempting trivial auth of > user=crimin > > 2024-06-04 12:00:32,819 ERROR unknown unknown > org.springframework.boot.web.servlet.support.ErrorPageFilter @ Forwarding to > error page from request [/sword/servicedocument] due to exception > [java.lang.NullPointerException: Cannot invoke > "javax.servlet.http.HttpServletRequest.setAttribute(String, Object)" because > "request" is null] > > How do I sign on successfully to the sword service? > > Nick Crimi > ECU Libraries -- Mark H. Wood Lead Technology Analyst University Library Indiana University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 library.indianapolis.iu.edu -- 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/ZmdSx-Fblaw45e39%40iu.edu. signature.asc Description: PGP signature
[dspace-tech] Mapping items between instances - possible in 7.6?
Hi Super Tech Support, It is possible to map items between instances (i.e., have items deposited in one instance appear in another one)? If not out of the box w/ 7.6, could this be configured or would you have to default to adding a link somewhere? Thanks! Julia -- 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/ce5f58ce-175f-4161-b227-c6855bc0e3c9n%40googlegroups.com.
Re: [dspace-tech] Re: Statistics, metrics and Analytics for dspace 7.6
On Fri, Jun 07, 2024 at 08:44:11PM +, DSpace Technical Support wrote: > Hi Sylvester, > > This is an frequent request for DSpace. But, unfortunately, the answer at > this time is that detailed Statistics reports do not yet exist in DSpace. > > As DSpace is built/maintained by it's community of users, we've yet to locate > and institution/volunteer interested in helping to build such detailed > reports. Part of the reason is that *statistics are very difficult to > capture with good accuracy* and reporting tools can be very complex to build > or maintain. May I butt in to add that "statistics" means very different things to different people. Serving them all is not only a difficult problem but a very large and often ill-defined one. The most common request is for usage statistics: how are the contents being consumed over time? But you also ask for submission statistics: what is the behavior of contributors to the repository? When I'm wearing my system-administrator hat, I want to know how and where the repository is growing, and what types of files are coming in, and the proportions of various file formats, and how all that is changing. I also want to keep an eye on the fill-rate of the assetstore(s) and the Solr cores. These is not quite the same thing as submission statistics. > At this time, if you need more detailed reporting, you'd probably want to > use/enable Google > Analytics<https://wiki.lyrasis.org/display/DSDOC7x/DSpace+Google+Analytics+Statistics>. > There's also some early discussion about supporting other Analytics > services like Matomo (but no official work yet): > https://github.com/DSpace/DSpace/issues/8414 It's very difficult for DSpace > to compete with the capabilities of external statistical tools, so these are > the best options for detailed reporting at this time. > > Tim > > On Tuesday, June 4, 2024 at 6:34:28 AM UTC-5 chiko...@gmail.com wrote: > Hi, is there a way for dspace 7 or comming version to have a mechanism to get > analytical reports community wise, collection wise and item wise. > > It would be nice if we could be able to know how many and what items are > uploaded by who over a certain period of time such as daily, monthly or > quarterly basis. If you're doing *exploratory* statistics, you may be better off extracting raw cases and loading them into a general-purpose statistical package, where you can slice and re-slice the data as you require. When one is exploring a dataset, one rarely knows what will be interesting, or how to abstract it, until it is found. This is something that DSpace could support better without a lot of effort. > Also dspace should provide a report on how many people have visited a > specific collection and how many actually downloaded some items. > > I have been asked to provide a report to the management about dspace usage, i > could only see statistics which display just the number of visitors and their > locations but not much details to make a nice and rich report for management > purposes. Now, right there is where I would be asking sharp questions, if the request had come to me, such as: do you want to learn about visitors or visits? Because it may not be possible to uniquely identify anonymous visitors. I should mention that there are businesses which support DSpace and offer their own statistical packages. -- Mark H. Wood Lead Technology Analyst University Library Indiana University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 library.indianapolis.iu.edu -- 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/ZmdFdV9bgH23q9H9%40iu.edu. signature.asc Description: PGP signature
Re: [dspace-tech] Re: DSpace 6.3 Bitstream details table - help needed
On Fri, Jun 07, 2024 at 09:36:37PM +, Kelley Canon wrote: > You don't often get email from kelley_ca...@sil.org. Learn why this is > important<https://aka.ms/LearnAboutSenderIdentification> > Tiim - > > Thanks for your reply. > > Interesting. And a bit frustrating. It would be nice if this were mentioned > in documentation, especially when there are other tables with "Bitstream" in > the name that DO contain most of the information you'd want about bitstreams. > bitstream_id, checksum, size, etc. > > Water under the bridge I guess! > > I do wonder, however, how do we distinguish bitstream data in the > metadatavalue table - in dc.title - from true item titles? One way would be to join the metadatavalue and bitstream tables: SELECT * FROM metadatavalue AS m JOIN bitstream AS b ON m.dspace_object_id = b.uuid limit 1; -- Mark H. Wood Lead Technology Analyst University Library Indiana University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 library.indianapolis.iu.edu -- 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/Zmc8VAgwyuMiV8mV%40iu.edu. signature.asc Description: PGP signature
[dspace-tech] Re: dspace dump error
Dear all, I am requesting help. I am trying to migrate from Dspace 5 to 7.6. When I try to get the Dspace backup using the command : "pg_dump dspace > dspace.backup" I get the following error: -su: dspace.backup: Permission denied Will be grateful for your help. Tom -- 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/CAE%2B4i99WEfoMzCNGtx8HvXoWxGXRAsNjx3c7YbJLUc9hQ3bnMA%40mail.gmail.com.
Re: [dspace-tech] Re: DSpace 6.3 Bitstream details table - help needed
Tiim - Thanks for your reply. Interesting. And a bit frustrating. It would be nice if this were mentioned in documentation, especially when there are other tables with "Bitstream" in the name that DO contain most of the information you'd want about bitstreams. bitstream_id, checksum, size, etc. Water under the bridge I guess! I do wonder, however, *how do we distinguish bitstream data in the metadatavalue table - in dc.title - from true item titles*? Kelley Canon Language & Culture Archives - REAP Administrator SIL International On Fri, Jun 7, 2024 at 3:29 PM DSpace Technical Support < dspace-tech@googlegroups.com> wrote: > Hi Kelley, > > In DSpace 5.x and above. all metadata related to DSpace Objects > (Bitstream, Bundle, Item, Collection, Community, etc) is stored in the > "metadatavalue" table and linked to the appropriate object table via the > "dspace_object_id" column. This means that the name of the Bitstream is > in the "dc.title" field value, and the description is in the > "dc.description" field value. > > In case they are useful, there are some older "Helper SQL functions" that > someone created for DSpace 6 a long time ago: > https://wiki.lyrasis.org/display/DSArchive/Helper+SQL+functions+for+DSpace+6 > > Tim > > On Friday, May 31, 2024 at 2:03:04 PM UTC-5 kelley...@sil.org wrote: > >> Hi all - >> >> We are looking for the name of the table that contains *bitstream >> details such as the filename & description*. The ERD shown on page 810 >> of the DSpace 6.x Documentation shows bitstream and bundle related tables >> in the pink section, but we do not find a table with the details we need. >> (The table named "bitstream" seems the logical location for this data, and >> I do see checksum there, but not the other basic information.) >> >> Are we just missing it, or are all tables not shown there? Or perhaps not >> all the fields for each table are shown? >> >> Thanks in advance for any assistance you can provide! >> >> Kelley Canon >> SIL International >> > -- > 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/5e89de3b-89f9-4a5c-8015-b7b773fb4858n%40googlegroups.com > <https://groups.google.com/d/msgid/dspace-tech/5e89de3b-89f9-4a5c-8015-b7b773fb4858n%40googlegroups.com?utm_medium=email_source=footer> > . > -- 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/CACXx6FtzzaWdthdfnmk7GS0ua65OWVrAb%3DOoV17jtPgzXD1tNw%40mail.gmail.com.
Re: [dspace-tech] Re: Issue with Author Indexing in DSpace 7
I might be able to help with this one. My notes suggest this was a DSpace 7.4 issue where authority keys would be shown in the Author Browse list for non-discoverable/withdrawn items. I seem to recall that updates with the internal discovery mechanism resolved the issue in DSpace 7.5. So I’d suggest upgrading to at least version 7.5 (if you are not there yet), and/or re-running index-authority. We are running DSpace 7.5 and I have not seen this issue since we upgraded. -- Sean From: DSpace Technical Support Date: Friday, June 7, 2024 at 3:37 PM To: DSpace Technical Support Subject: [dspace-tech] Re: Issue with Author Indexing in DSpace 7 Caution! This message was sent from outside the University of Manitoba. Hi Humberto, It's difficult for anyone to help without more information. What version of DSpace 7 are you using? Are these "authors" you are referencing Author *entities* or just Author strings? Are you using DSpace's Authority Control feature? >From the screenshot you've shared & the details in your email, it's very >difficult to determine what the issue may be. It's possible this is an other >bug that's been fixed in a more recent version of 7.x. Or, it could be a new >bug that we're unaware of. You also may want to verify whether you see the same behavior on our demo site (https://demo.dspace.org) as that can verify whether or not this is a bug in DSpace. Tim On Tuesday, June 4, 2024 at 12:36:57 AM UTC-5 hbla...@gmail.com wrote: Hello everyone, I hope you are all well. I am encountering a problem in our DSpace repository that I hope you can help me resolve. Upon reviewing the author indexing, I have noticed that some identifiers are not being indexed correctly, which is affecting the visibility and accessibility of the documents in our repository. Attached is an image with some examples of these identifiers: The specific problem I am observing is as follows: * Incorrectly indexed author identifiers: Instead of displaying the names of the authors, alphanumeric identifiers are being shown. * Impact on visibility: This affects the search and retrieval of documents by end users, as they cannot search directly by author names. Any guidance on how to resolve this issue would be greatly appreciated. If anyone has faced a similar problem or has any suggestions on possible solutions, I would greatly appreciate your help. Thank you very much in advance for your time and support. Humberto -- 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<mailto:dspace-tech+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/e10d1a1f-2010-49d6-a62e-fdc9e4d22f95n%40googlegroups.com<https://groups.google.com/d/msgid/dspace-tech/e10d1a1f-2010-49d6-a62e-fdc9e4d22f95n%40googlegroups.com?utm_medium=email_source=footer>. -- 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/YT3PR01MB1081596713A5AEB0B447D2708E8FB2%40YT3PR01MB10815.CANPRD01.PROD.OUTLOOK.COM.
[dspace-tech] Re: Dspace 1.4.2 - host of issues
Hi Deborah, We also do have a Migration guide which you may wish to be aware of. This guide should walk you through the basic steps of migrating content from any older version of DSpace into a fresh install of DSpace 7. https://wiki.lyrasis.org/display/DSDOC7x/Migrating+DSpace+to+a+new+server Tim On Wednesday, June 5, 2024 at 1:38:03 PM UTC-5 deborah.bast...@gmail.com wrote: > Thank you, Edmund! > > On Tuesday, June 4, 2024 at 12:21:47 AM UTC-7 Edmund Balnaves wrote: > >> Given you are how many versions behind I suggest you would be best to >> export your data and bring that into an new server. The export/import >> functions are fortunately pretty consistent over time. >> >> * export your collection using the item exporter in your current system >> [dspace]/bin/export --type=COLLECTION --id=collID --dest=dest_dir >> --number=seq_num >> * set up an entirely new DSpace server on V7 ( you will need a beefier >> server with at least 16gb memory 4 cpu min) >> * restore your items >> * configure the UI with your branding. >> >> There is pretty good documentation for V7 installation, but it is a quite >> a technical task. >> >> Edmund Balnaves >> Prosentient Systems >> >> >> On Tuesday, June 4, 2024 at 9:10:41 AM UTC+10 Deborah wrote: >> >>> Hello, >>> >>> At our very small university library we are at the very beginning stages >>> of trying to fix, upgrade, change our situation with our Institutional >>> Repository. I’m the head of the library here, but unfamiliar with the >>> technology requirements to fix, or even have a constructive conversation to >>> unravel the issues. Our contracted tech team have asked me to seek some >>> initial guidance on their behalf. >>> >>> Here’s the situation so far. In 2020, Dspace 1.4.2 was installed on >>> server that was, as I understand, cobbled together, and data input began >>> later that year. >>> >>> In Fall 2023, the message on our browsers indicated an expired >>> certificate. Currently the expiration is almost 9 months old. We’ve had >>> discussions with our contracted technology support specialists who began >>> just last year and can’t find any documentation from the previous tech >>> specialist to guide them to the next step. >>> >>> In my small amount of research, I’ve found that we sorely need to update >>> the software, but my understanding is that we need to do this is in steps >>> with 5.0 first and then 7.x. Is that correct? >>> >>> Secondly, we’re wondering if the server is long in the tooth, and needs >>> replacement. There is an idea to split out to virtual servers that might be >>> purchased for another couple of departments. And lastly, maybe it’s just a >>> new certificate we need, then the software update. >>> >>> Have any of you had a similar situation with such old and unsupported >>> software? Would you care to share how you resolved this? What would be the >>> most basic construction/upgrade? What is the licensing cost of a >>> certificate? Would it be advantageous to start again from scratch and >>> reenter the data? >>> >>> Any assistance you can provide will be enormously appreciated. >>> >>> >>> >>> All my best, >>> >>> Deborah >>> >> -- 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/2c961906-0b59-4286-b5fb-052d25fb4203n%40googlegroups.com.
[dspace-tech] Re: sword fails authentication for DSpace 7.6.1
Hi Nick, I think the answer may be that SWORD doesn't support LDAP authentication (and it looks like that's what you are using based on the logs you shared). SWORD *only supports* PasswordAuthentication (DSpace's internal authentication system). So, to login to SWORD, you'd need to use an internally stored username & password. Tim On Tuesday, June 4, 2024 at 11:27:39 AM UTC-5 Joyner Library wrote: > Hi All, > > We have enabled sword version 1 in the local configuration but haven't > changed other sword settings. I can sign on to the frontend and /server > too. When we try to download > https://irdev.ecu.edu/server/sword/servicedocument it gives the white > label error page. The DSpace log file shows: > > INFO unknown 4f89ae89-9baf-49cc-b800-3205dbddef5d > org.dspace.authenticate.LDAPAuthentication @ > anonymous:session_id=0:ip_addr=150.216.*.*:auth:attempting trivial auth of > user=crimin > > 2024-06-04 12:00:32,819 ERROR unknown unknown > org.springframework.boot.web.servlet.support.ErrorPageFilter @ Forwarding > to error page from request [/sword/servicedocument] due to exception > [java.lang.NullPointerException: Cannot invoke > "javax.servlet.http.HttpServletRequest.setAttribute(String, Object)" > because "request" is null] > > How do I sign on successfully to the sword service? > > Nick Crimi > ECU Libraries > -- 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/fb01c4ac-0f28-4c2c-848c-7a02bc26953cn%40googlegroups.com.
[dspace-tech] Re: Statistics, metrics and Analytics for dspace 7.6
Hi Sylvester, This is an frequent request for DSpace. But, unfortunately, the answer at this time is that detailed Statistics reports do not yet exist in DSpace. As DSpace is built/maintained by it's community of users, we've yet to locate and institution/volunteer interested in helping to build such detailed reports. Part of the reason is that *statistics are very difficult to capture with good accuracy* and reporting tools can be very complex to build or maintain. At this time, if you need more detailed reporting, you'd probably want to use/enable Google Analytics <https://wiki.lyrasis.org/display/DSDOC7x/DSpace+Google+Analytics+Statistics>. There's also some early discussion about supporting other Analytics services like Matomo (but no official work yet): https://github.com/DSpace/DSpace/issues/8414 It's very difficult for DSpace to compete with the capabilities of external statistical tools, so these are the best options for detailed reporting at this time. Tim On Tuesday, June 4, 2024 at 6:34:28 AM UTC-5 chiko...@gmail.com wrote: > Hi, is there a way for dspace 7 or comming version to have a mechanism to > get analytical reports community wise, collection wise and item wise. > > It would be nice if we could be able to know how many and what items are > uploaded by who over a certain period of time such as daily, monthly or > quarterly basis. > > Also dspace should provide a report on how many people have visited a > specific collection and how many actually downloaded some items. > > I have been asked to provide a report to the management about dspace > usage, i could only see statistics which display just the number of > visitors and their locations but not much details to make a nice and rich > report for management purposes. > > kindly assist > > > *Chikoti, Sylvester R.* > *+255767106905 <+255%20767%20106%20905>* > -- 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/500187ab-616e-4cb0-bf74-4f60d53b1c3dn%40googlegroups.com.
[dspace-tech] Re: Issue with Author Indexing in DSpace 7
Hi Humberto, It's difficult for anyone to help without more information. What version of DSpace 7 are you using? Are these "authors" you are referencing Author *entities* or just Author strings? Are you using DSpace's Authority Control feature? >From the screenshot you've shared & the details in your email, it's very difficult to determine what the issue may be. It's possible this is an other bug that's been fixed in a more recent version of 7.x. Or, it could be a new bug that we're unaware of. You also may want to verify whether you see the same behavior on our demo site (https://demo.dspace.org) as that can verify whether or not this is a bug in DSpace. Tim On Tuesday, June 4, 2024 at 12:36:57 AM UTC-5 hbla...@gmail.com wrote: > > > Hello everyone, > > I hope you are all well. > > I am encountering a problem in our DSpace repository that I hope you can > help me resolve. Upon reviewing the author indexing, I have noticed that > some identifiers are not being indexed correctly, which is affecting the > visibility and accessibility of the documents in our repository. > > Attached is an image with some examples of these identifiers: > > The specific problem I am observing is as follows: > >- *Incorrectly indexed author identifiers*: Instead of displaying the >names of the authors, alphanumeric identifiers are being shown. >- *Impact on visibility*: This affects the search and retrieval of >documents by end users, as they cannot search directly by author names. > > Any guidance on how to resolve this issue would be greatly appreciated. If > anyone has faced a similar problem or has any suggestions on possible > solutions, I would greatly appreciate your help. > > Thank you very much in advance for your time and support. > > > Humberto > -- 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/e10d1a1f-2010-49d6-a62e-fdc9e4d22f95n%40googlegroups.com.
[dspace-tech] Re: Search filter
Hi Lucas, In DSpace 7.x, it's important to always run the same version of frontend & backend *because all 7.x releases added new features.* So, if you upgraded the backend, you must also upgrade the frontend. We cannot support running a 7.5 frontend running against a 7.6.1 backend, because there were new features / major changes between 7.5 and 7.6. These new features may cause odd behaviors on an older version of the frontend. Tim On Friday, May 31, 2024 at 5:21:21 PM UTC-5 Lucas Silveira wrote: > Thank you very much for responding, > Do you think if we update the backend to 7.6.1 it would solve the problem? > because we already implemented the layout for version 7.5, and I think it > would take a while to adapt the front-end from version 7.5 to 7.6.1 > > Em sexta-feira, 31 de maio de 2024 às 12:30:35 UTC-3, DSpace Technical > Support escreveu: > >> Hi Lucas, >> >> This appears to be working properly on the demo site ( >> https://demo.dspace.org), if I'm understanding correctly. So, that may >> imply this issue has been fixed in 7.6.x. >> >> On the demo site, there's currently an Item with an author named Avilés, >> Raúl >> >> I can successfully use the Browse by Author for that author: >> https://demo.dspace.org/browse/author?value=Avil%C3%A9s,%20Ra%C3%BAl=2 >> >> I can also us the "Author" search filter with that author name and find >> the Item: >> https://demo.dspace.org/search?query==Avil%C3%A9s,%20Ra%C3%BAl,equals >> >> My best guess is this may have already been fixed, so you may just need >> to upgrade. >> >> Tim >> On Monday, May 27, 2024 at 12:28:17 PM UTC-5 Lucas Silveira wrote: >> >>> Dear colleagues, >>> >>> I am using version 7.5 and I have a question. In the filter search, when >>> I select to search by author, I noticed that DSpace does not retrieve >>> authors with accents in their names. For example, if the name is "José" and >>> I include the "é" in the search, it does not return any results, while for >>> any unaccented word, it correctly retrieves authors containing the search >>> string. I tested this on the demo and noticed the same behavior. >>> >>> Has anyone experienced this? Do you know if there is any configuration >>> that can resolve this? >>> >>> Thank you in advance for your response. >>> >> -- 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/647c5ed1-f92b-4995-9812-33f5f65ee2dan%40googlegroups.com.
[dspace-tech] Re: DSpace 6.3 Bitstream details table - help needed
Hi Kelley, In DSpace 5.x and above. all metadata related to DSpace Objects (Bitstream, Bundle, Item, Collection, Community, etc) is stored in the "metadatavalue" table and linked to the appropriate object table via the "dspace_object_id" column. This means that the name of the Bitstream is in the "dc.title" field value, and the description is in the "dc.description" field value. In case they are useful, there are some older "Helper SQL functions" that someone created for DSpace 6 a long time ago: https://wiki.lyrasis.org/display/DSArchive/Helper+SQL+functions+for+DSpace+6 Tim On Friday, May 31, 2024 at 2:03:04 PM UTC-5 kelley...@sil.org wrote: > Hi all - > > We are looking for the name of the table that contains *bitstream details > such as the filename & description*. The ERD shown on page 810 of the > DSpace 6.x Documentation shows bitstream and bundle related tables in the > pink section, but we do not find a table with the details we need. (The > table named "bitstream" seems the logical location for this data, and I do > see checksum there, but not the other basic information.) > > Are we just missing it, or are all tables not shown there? Or perhaps not > all the fields for each table are shown? > > Thanks in advance for any assistance you can provide! > > Kelley Canon > SIL International > -- 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/5e89de3b-89f9-4a5c-8015-b7b773fb4858n%40googlegroups.com.
[dspace-tech] Dspace 7 ERROR on Production
Hello! We're haven issues with an installation of DSpace 7.6.1. When we were on development mode the service was working as expected. We had a DNS with https and the front-end/back-end communication was set like this: ui: ssl: false host: localhost port: 4000 nameSpace: / rateLimiter: windowMs: 6 max: useProxies: true rest: ssl: true host: test.mydspace.com port: 443 nameSpace: /server However, now that we are in production, we've changed the URLs in the front and back configuration files, and the service is working really slow and throwing communications errors from time to time between the backend and frontend. The IT team has detected that this errors are happening because the front-end is passing through the WAF everytime it needs to get data from the back-end. We've tried setting the rest-host to "localhost", but DSpace won't work after that. Is there a way to make both, the frontend and backend point to "localhost" so the backend does not have to go through the firewall? Or is there another possible configuration for this to work smoothly? Best regards, Juan -- 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/29d1f97a-c966-4489-a72d-d25d12c1f976n%40googlegroups.com.
[dspace-tech] Assistance with Configuring Multiple Asset Stores in DSpace Based on Communities
Dear All, I am currently working on a DSpace instance and am looking to configure multiple asset stores such that items are stored in different asset stores based on their respective communities. After reviewing the documentation and various resources, I have a general idea of how to approach this, but I would greatly appreciate guidance from the community. *Define Multiple Asset Stores*: II will define multiple asset stores like so: [dspace]/config/spring/api/assetstore.xml assetstore.dir.0 = /dspace/assetstore1 assetstore.dir.1 = /dspace/assetstore2 Please help, how will we call the particular asset store based on the community document? Regards, Ravi Bhardwaj -- 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/CAKdP8NPRZ4zLru_Goz6Bm1HYh_%2BsPWuFVyrOAx9BLP2imcsCew%40mail.gmail.com.
[dspace-tech] Re: Error in SAFBuilder
Hi Husna, Which version of DSpace are you using? You might have already seen this, but there is a wiki page on the use of SAF Packager. Due to a lack of maintenance, SAF Packager has become outdated, which could be part of the issue you are describing (depending on your DSpace version). There are several other recommended alternatives listed on this page: https://wiki.lyrasis.org/display/DSArchive/Simple+Archive+Format+Packager I hope this points you in the right direction. Please feel free to reply in case it doesn't. We can do some additional digging and someone else might have additional feedback pertaining to your question. Holger On Wednesday, June 5, 2024 at 10:05:10 PM UTC-4 NURHUSNA IDAYU BINTI SUHAIMI wrote: > Hello Dspace Community.. > > I tried to extract the data from excel and move them to a server and when > i tried to do the SAFBuilder and the error pop up (Refer to the picture > below) > > [image: Capture.JPG] > and i receive notification from Dscape as per seen in the picture below . > [image: image.png] > > Is there anything that I must do pertaining to this or is the notification > sent to tell the error of SAFBuilder ? > > > Looking forward to hearing from you. Thank you. > > Regards, > Husna > -- 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/403bc77d-adae-4376-8308-c11b8855cc90n%40googlegroups.com.
[dspace-tech] home page after authorization
Dear colleagues, when opening a link to a collection or object, the user, after authorization, is taken to the home page. We need to open the link again. It is very uncomfortable. Is it possible to make it so that when opening a link to a collection (for example), the user, after authorization, is taken to the collection, and not to the home page? Best, Alex -- 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/40584dc1-e805-4354-8e58-b1f7e7e13a25n%40googlegroups.com.
[dspace-tech] Error in SAFBuilder
Hello Dspace Community.. I tried to extract the data from excel and move them to a server and when i tried to do the SAFBuilder and the error pop up (Refer to the picture below) [image: Capture.JPG] and i receive notification from Dscape as per seen in the picture below . [image: image.png] Is there anything that I must do pertaining to this or is the notification sent to tell the error of SAFBuilder ? Looking forward to hearing from you. Thank you. Regards, Husna -- 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/596a5127-40d7-4dd8-be5b-eb480b02c2b5n%40googlegroups.com.
[dspace-tech] Re: Dspace 1.4.2 - host of issues
Thank you, Edmund! On Tuesday, June 4, 2024 at 12:21:47 AM UTC-7 Edmund Balnaves wrote: > Given you are how many versions behind I suggest you would be best to > export your data and bring that into an new server. The export/import > functions are fortunately pretty consistent over time. > > * export your collection using the item exporter in your current system > [dspace]/bin/export --type=COLLECTION --id=collID --dest=dest_dir > --number=seq_num > * set up an entirely new DSpace server on V7 ( you will need a beefier > server with at least 16gb memory 4 cpu min) > * restore your items > * configure the UI with your branding. > > There is pretty good documentation for V7 installation, but it is a quite > a technical task. > > Edmund Balnaves > Prosentient Systems > > > On Tuesday, June 4, 2024 at 9:10:41 AM UTC+10 Deborah wrote: > >> Hello, >> >> At our very small university library we are at the very beginning stages >> of trying to fix, upgrade, change our situation with our Institutional >> Repository. I’m the head of the library here, but unfamiliar with the >> technology requirements to fix, or even have a constructive conversation to >> unravel the issues. Our contracted tech team have asked me to seek some >> initial guidance on their behalf. >> >> Here’s the situation so far. In 2020, Dspace 1.4.2 was installed on >> server that was, as I understand, cobbled together, and data input began >> later that year. >> >> In Fall 2023, the message on our browsers indicated an expired >> certificate. Currently the expiration is almost 9 months old. We’ve had >> discussions with our contracted technology support specialists who began >> just last year and can’t find any documentation from the previous tech >> specialist to guide them to the next step. >> >> In my small amount of research, I’ve found that we sorely need to update >> the software, but my understanding is that we need to do this is in steps >> with 5.0 first and then 7.x. Is that correct? >> >> Secondly, we’re wondering if the server is long in the tooth, and needs >> replacement. There is an idea to split out to virtual servers that might be >> purchased for another couple of departments. And lastly, maybe it’s just a >> new certificate we need, then the software update. >> >> Have any of you had a similar situation with such old and unsupported >> software? Would you care to share how you resolved this? What would be the >> most basic construction/upgrade? What is the licensing cost of a >> certificate? Would it be advantageous to start again from scratch and >> reenter the data? >> >> Any assistance you can provide will be enormously appreciated. >> >> >> >> All my best, >> >> Deborah >> > -- 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/96d32590-b99d-4e0f-ab50-df7398238cf6n%40googlegroups.com.
Re: [dspace-tech] Re: Dspace-CRIS 2023.02.04 Handle links do not work
The strange thing here is that even the endpoint that is responsible for forwarding the handle (server/api/pid) returns a 500 error. вторник, 4 июня 2024 г. в 13:00:08 UTC+3, elorenzo: > i think you have two ways of creating the dc.identifier.uti (usually > used to store the handle). > > Typically a repository uses:ç > > hdl.handle.net/prefix/suffix--> this only works with a valid prefix > number, provided by CNRI, AND a handle server well configured and > started. > > the other way to build the dc.identifier.uri is > http../yourrepositoryname.xxx.xxx/handle/prefix/suffix any value for > prefix, (123456789 is used by many repositories) will serve. This > URLs will always works (even without a handle server installation) > > use one or another is configurable > > Best luck > EMilio > > El 2024-06-04 11:45, Maksim Donchenko escribió: > > Thanks for the answer, but in previous versions such as 2023.02.03 and > > earlier, everything worked without installing and running the Hande > > server. > > > > вторник, 4 июня 2024 г. в 12:40:06 UTC+3, Julio: > > > >> Hello, if I'm not mistaken, with the default handle it will create a > >> handle at the internal and metadata level, but the link will not > >> work, because handle.net [1] has to be the one that redirects you to > >> your server, if you are not registered on handle.net [1], this last > >> part is not going to work for you. > >> > >> El martes, 4 de junio de 2024 a las 8:57:51 UTC+2, Maksim Donchenko > >> escribió: > >> No, I have not registered at https://handle.net/. I am using the > >> default handle. > >> > >> вторник, 4 июня 2024 г. в 09:48:28 UTC+3, Julio: > >> > >> Hello, have you registered at https://handle.net/? and completed the > >> entire registration process. > >> > >> Do you have the handle server started on your machine? > >> > >> [dspace_dir]/bin/start-handle-server > >> > >> Ports 2641 and 8000 have input and output access on your machine. > >> > >> Review all these points. > >> > >> Greetings > >> > >> El lunes, 3 de junio de 2024 a las 16:41:43 UTC+2, Maksim Donchenko > >> escribió: > >> Hello, everyone. I decided to install the new version of Dspace-CRIS > >> 2023.02.04 and found that the links with Handle do not work, the > >> server just says “No item found for the identifier”. Maybe > >> someone has encountered something similar. Thank you in advance for > >> your response. > >> Sincerely, Maksim. > > > > -- > > 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...@googlegroups.com. > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/dspace-tech/27b53c8c-2762-49d5-a6c8-7aa263268b91n%40googlegroups.com > > [2]. > > > > > > Links: > > -- > > [1] http://handle.net > > [2] > > > https://groups.google.com/d/msgid/dspace-tech/27b53c8c-2762-49d5-a6c8-7aa263268b91n%40googlegroups.com?utm_medium=email_source=footer > -- 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/09101aa9-28d2-4b83-b777-d86e6c86cbb5n%40googlegroups.com.
[dspace-tech] sword fails authentication for DSpace 7.6.1
Hi All, We have enabled sword version 1 in the local configuration but haven't changed other sword settings. I can sign on to the frontend and /server too. When we try to download https://irdev.ecu.edu/server/sword/servicedocument it gives the white label error page. The DSpace log file shows: INFO unknown 4f89ae89-9baf-49cc-b800-3205dbddef5d org.dspace.authenticate.LDAPAuthentication @ anonymous:session_id=0:ip_addr=150.216.*.*:auth:attempting trivial auth of user=crimin 2024-06-04 12:00:32,819 ERROR unknown unknown org.springframework.boot.web.servlet.support.ErrorPageFilter @ Forwarding to error page from request [/sword/servicedocument] due to exception [java.lang.NullPointerException: Cannot invoke "javax.servlet.http.HttpServletRequest.setAttribute(String, Object)" because "request" is null] How do I sign on successfully to the sword service? Nick Crimi ECU Libraries -- 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/bac57938-6f5d-42ba-b9a6-6c985697277dn%40googlegroups.com.
[dspace-tech] DSpace 7 - Optimizing filter-media command line tool
Hi Everyone, We are in the process of migrating a larger DSpace instance from 6 to 7. While running the /opt/bin/dspace filter-media <https://wiki.lyrasis.org/display/DSDOC7x/Mediafilters+for+Transforming+DSpace+Content>command line tool that generates thumbnails, we have noticed that it takes a significant amount of time to complete (a month and a half). In preparation for this instance's production migration, we were curious to know if anyone had experience optimizing this or similar command line tools. We are considering adding more java resources and would love to hear if community members have any suggestions. Thank you and take care. ~Rachel -- 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/9f2eb0fb-aed3-4941-99a9-7ba3b557f44fn%40googlegroups.com.
[dspace-tech] Statistics, metrics and Analytics for dspace 7.6
Hi, is there a way for dspace 7 or comming version to have a mechanism to get analytical reports community wise, collection wise and item wise. It would be nice if we could be able to know how many and what items are uploaded by who over a certain period of time such as daily, monthly or quarterly basis. Also dspace should provide a report on how many people have visited a specific collection and how many actually downloaded some items. I have been asked to provide a report to the management about dspace usage, i could only see statistics which display just the number of visitors and their locations but not much details to make a nice and rich report for management purposes. kindly assist *Chikoti, Sylvester R.* *+255767106905* -- 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/CABJ%2Bh%3DG%2BANANE5YQf6vYGWMdK1jhbtzEheT831QUHv-G99ggcA%40mail.gmail.com.
Re: [dspace-tech] Re: Dspace-CRIS 2023.02.04 Handle links do not work
i think you have two ways of creating the dc.identifier.uti (usually used to store the handle). Typically a repository uses:ç hdl.handle.net/prefix/suffix--> this only works with a valid prefix number, provided by CNRI, AND a handle server well configured and started. the other way to build the dc.identifier.uri is http../yourrepositoryname.xxx.xxx/handle/prefix/suffix any value for prefix, (123456789 is used by many repositories) will serve.This URLs will always works (even without a handle server installation) use one or another is configurable Best luck EMilio El 2024-06-04 11:45, Maksim Donchenko escribió: Thanks for the answer, but in previous versions such as 2023.02.03 and earlier, everything worked without installing and running the Hande server. вторник, 4 июня 2024 г. в 12:40:06 UTC+3, Julio: Hello, if I'm not mistaken, with the default handle it will create a handle at the internal and metadata level, but the link will not work, because handle.net [1] has to be the one that redirects you to your server, if you are not registered on handle.net [1], this last part is not going to work for you. El martes, 4 de junio de 2024 a las 8:57:51 UTC+2, Maksim Donchenko escribió: No, I have not registered at https://handle.net/. I am using the default handle. вторник, 4 июня 2024 г. в 09:48:28 UTC+3, Julio: Hello, have you registered at https://handle.net/? and completed the entire registration process. Do you have the handle server started on your machine? [dspace_dir]/bin/start-handle-server Ports 2641 and 8000 have input and output access on your machine. Review all these points. Greetings El lunes, 3 de junio de 2024 a las 16:41:43 UTC+2, Maksim Donchenko escribió: Hello, everyone. I decided to install the new version of Dspace-CRIS 2023.02.04 and found that the links with Handle do not work, the server just says “No item found for the identifier”. Maybe someone has encountered something similar. Thank you in advance for your response. Sincerely, Maksim. -- 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/27b53c8c-2762-49d5-a6c8-7aa263268b91n%40googlegroups.com [2]. Links: -- [1] http://handle.net [2] https://groups.google.com/d/msgid/dspace-tech/27b53c8c-2762-49d5-a6c8-7aa263268b91n%40googlegroups.com?utm_medium=email_source=footer -- 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/83d6eff0967d75f657ce7cb66fdde74b%40arvo.es.
[dspace-tech] Re: Dspace-CRIS 2023.02.04 Handle links do not work
Thanks for the answer, but in previous versions such as 2023.02.03 and earlier, everything worked without installing and running the Hande server. вторник, 4 июня 2024 г. в 12:40:06 UTC+3, Julio: > Hello, if I'm not mistaken, with the default handle it will create a > handle at the internal and metadata level, but the link will not work, > because handle.net has to be the one that redirects you to your server, > if you are not registered on handle.net, this last part is not going to > work for you. > > El martes, 4 de junio de 2024 a las 8:57:51 UTC+2, Maksim Donchenko > escribió: > >> No, I have not registered at https://handle.net/. I am using the default >> handle. >> >> вторник, 4 июня 2024 г. в 09:48:28 UTC+3, Julio: >> >>> Hello, have you registered at https://handle.net/? and completed the >>> entire registration process. >>> >>> Do you have the handle server started on your machine? >>> >>> [dspace_dir]/bin/start-handle-server >>> >>> Ports 2641 and 8000 have input and output access on your machine. >>> >>> Review all these points. >>> >>> Greetings >>> >>> El lunes, 3 de junio de 2024 a las 16:41:43 UTC+2, Maksim Donchenko >>> escribió: >>> >>>> Hello, everyone. I decided to install the new version of Dspace-CRIS >>>> 2023.02.04 and found that the links with Handle do not work, the server >>>> just says “No item found for the identifier”. Maybe someone has >>>> encountered >>>> something similar. Thank you in advance for your response. >>>> Sincerely, Maksim. >>>> >>> -- 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/27b53c8c-2762-49d5-a6c8-7aa263268b91n%40googlegroups.com.
[dspace-tech] Re: Dspace-CRIS 2023.02.04 Handle links do not work
Hello, if I'm not mistaken, with the default handle it will create a handle at the internal and metadata level, but the link will not work, because handle.net has to be the one that redirects you to your server, if you are not registered on handle.net, this last part is not going to work for you. El martes, 4 de junio de 2024 a las 8:57:51 UTC+2, Maksim Donchenko escribió: > No, I have not registered at https://handle.net/. I am using the default > handle. > > вторник, 4 июня 2024 г. в 09:48:28 UTC+3, Julio: > >> Hello, have you registered at https://handle.net/? and completed the >> entire registration process. >> >> Do you have the handle server started on your machine? >> >> [dspace_dir]/bin/start-handle-server >> >> Ports 2641 and 8000 have input and output access on your machine. >> >> Review all these points. >> >> Greetings >> >> El lunes, 3 de junio de 2024 a las 16:41:43 UTC+2, Maksim Donchenko >> escribió: >> >>> Hello, everyone. I decided to install the new version of Dspace-CRIS >>> 2023.02.04 and found that the links with Handle do not work, the server >>> just says “No item found for the identifier”. Maybe someone has encountered >>> something similar. Thank you in advance for your response. >>> Sincerely, Maksim. >>> >> -- 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/9242c8ad-e09c-4feb-9c52-a2693e204568n%40googlegroups.com.
[dspace-tech] Re: Dspace 1.4.2 - host of issues
Given you are how many versions behind I suggest you would be best to export your data and bring that into an new server. The export/import functions are fortunately pretty consistent over time. * export your collection using the item exporter in your current system [dspace]/bin/export --type=COLLECTION --id=collID --dest=dest_dir --number=seq_num * set up an entirely new DSpace server on V7 ( you will need a beefier server with at least 16gb memory 4 cpu min) * restore your items * configure the UI with your branding. There is pretty good documentation for V7 installation, but it is a quite a technical task. Edmund Balnaves Prosentient Systems On Tuesday, June 4, 2024 at 9:10:41 AM UTC+10 Deborah wrote: > Hello, > > At our very small university library we are at the very beginning stages > of trying to fix, upgrade, change our situation with our Institutional > Repository. I’m the head of the library here, but unfamiliar with the > technology requirements to fix, or even have a constructive conversation to > unravel the issues. Our contracted tech team have asked me to seek some > initial guidance on their behalf. > > Here’s the situation so far. In 2020, Dspace 1.4.2 was installed on > server that was, as I understand, cobbled together, and data input began > later that year. > > In Fall 2023, the message on our browsers indicated an expired > certificate. Currently the expiration is almost 9 months old. We’ve had > discussions with our contracted technology support specialists who began > just last year and can’t find any documentation from the previous tech > specialist to guide them to the next step. > > In my small amount of research, I’ve found that we sorely need to update > the software, but my understanding is that we need to do this is in steps > with 5.0 first and then 7.x. Is that correct? > > Secondly, we’re wondering if the server is long in the tooth, and needs > replacement. There is an idea to split out to virtual servers that might be > purchased for another couple of departments. And lastly, maybe it’s just a > new certificate we need, then the software update. > > Have any of you had a similar situation with such old and unsupported > software? Would you care to share how you resolved this? What would be the > most basic construction/upgrade? What is the licensing cost of a > certificate? Would it be advantageous to start again from scratch and > reenter the data? > > Any assistance you can provide will be enormously appreciated. > > > > All my best, > > Deborah > -- 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/86e74560-b779-4b28-8743-0636a6f0451cn%40googlegroups.com.
[dspace-tech] Re: Dspace-CRIS 2023.02.04 Handle links do not work
No, I have not registered at https://handle.net/. I am using the default handle. вторник, 4 июня 2024 г. в 09:48:28 UTC+3, Julio: > Hello, have you registered at https://handle.net/? and completed the > entire registration process. > > Do you have the handle server started on your machine? > > [dspace_dir]/bin/start-handle-server > > Ports 2641 and 8000 have input and output access on your machine. > > Review all these points. > > Greetings > > El lunes, 3 de junio de 2024 a las 16:41:43 UTC+2, Maksim Donchenko > escribió: > >> Hello, everyone. I decided to install the new version of Dspace-CRIS >> 2023.02.04 and found that the links with Handle do not work, the server >> just says “No item found for the identifier”. Maybe someone has encountered >> something similar. Thank you in advance for your response. >> Sincerely, Maksim. >> > -- 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/835fb292-f6f4-4af4-94ae-a29beaed4587n%40googlegroups.com.
[dspace-tech] Re: Dspace-CRIS 2023.02.04 Handle links do not work
Hello, have you registered at https://handle.net/? and completed the entire registration process. Do you have the handle server started on your machine? [dspace_dir]/bin/start-handle-server Ports 2641 and 8000 have input and output access on your machine. Review all these points. Greetings El lunes, 3 de junio de 2024 a las 16:41:43 UTC+2, Maksim Donchenko escribió: > Hello, everyone. I decided to install the new version of Dspace-CRIS > 2023.02.04 and found that the links with Handle do not work, the server > just says “No item found for the identifier”. Maybe someone has encountered > something similar. Thank you in advance for your response. > Sincerely, Maksim. > -- 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/0dd61155-09cf-4e12-82e8-09ec297b6aaan%40googlegroups.com.
[dspace-tech] Issue with Author Indexing in DSpace 7
Hello everyone, I hope you are all well. I am encountering a problem in our DSpace repository that I hope you can help me resolve. Upon reviewing the author indexing, I have noticed that some identifiers are not being indexed correctly, which is affecting the visibility and accessibility of the documents in our repository. Attached is an image with some examples of these identifiers: The specific problem I am observing is as follows: - *Incorrectly indexed author identifiers*: Instead of displaying the names of the authors, alphanumeric identifiers are being shown. - *Impact on visibility*: This affects the search and retrieval of documents by end users, as they cannot search directly by author names. Any guidance on how to resolve this issue would be greatly appreciated. If anyone has faced a similar problem or has any suggestions on possible solutions, I would greatly appreciate your help. Thank you very much in advance for your time and support. Humberto -- 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/42e0e5ea-4b2b-4b72-b653-3e4d4c997482n%40googlegroups.com.
[dspace-tech] Dspace 1.4.2 - host of issues
Hello, At our very small university library we are at the very beginning stages of trying to fix, upgrade, change our situation with our Institutional Repository. I’m the head of the library here, but unfamiliar with the technology requirements to fix, or even have a constructive conversation to unravel the issues. Our contracted tech team have asked me to seek some initial guidance on their behalf. Here’s the situation so far. In 2020, Dspace 1.4.2 was installed on server that was, as I understand, cobbled together, and data input began later that year. In Fall 2023, the message on our browsers indicated an expired certificate. Currently the expiration is almost 9 months old. We’ve had discussions with our contracted technology support specialists who began just last year and can’t find any documentation from the previous tech specialist to guide them to the next step. In my small amount of research, I’ve found that we sorely need to update the software, but my understanding is that we need to do this is in steps with 5.0 first and then 7.x. Is that correct? Secondly, we’re wondering if the server is long in the tooth, and needs replacement. There is an idea to split out to virtual servers that might be purchased for another couple of departments. And lastly, maybe it’s just a new certificate we need, then the software update. Have any of you had a similar situation with such old and unsupported software? Would you care to share how you resolved this? What would be the most basic construction/upgrade? What is the licensing cost of a certificate? Would it be advantageous to start again from scratch and reenter the data? Any assistance you can provide will be enormously appreciated. All my best, Deborah -- 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/29dad877-1147-4c8b-a48f-010f9262a23bn%40googlegroups.com.
Re: [dspace-tech] How to find number of times a pdf has been downloaded from an item page
Thanks Tim :) Follow-up question: So I've been asked to find how many
times a file has been downloaded and its associated item page visited each
year since the inception of the repository. Since the existing the stats
package just states it per month, I went into the Solr Statistics and ran
this queries like this
one:
http://localhost:1234/solr/statistics/select?facet.field=id=true=true=OR=owningColl%3Aa35c7701-e11d-482c-8b3e-4b9cd69bdf4d%20AND%20type%3A2%20AND%20statistics_type%3Aview%20AND%20isBot%3Afalse%20AND%20time%3A%5B2018-05-01T00%3A00%3A00Z%20TO%202019-04-30T00%3A00%3A00Z%5D
(Ex. Would expect to change the type to 0 for bitstreams, and alter the
date range to encompass different years)
It's really clunky to run the query for EVERY year though, get the counts
of page views for every item id, copy and paste that into an excel file,
and do that over and over again. Would you or anyone else happen to know
if Solr has any magical way to spit this out in a nice excel file for me,
or if there's an easy way to plug a script into the Solr interface that
would do that?
Thanks,
Carolyn.
On Thursday, March 28, 2024 at 5:54:18 PM UTC-4 DSpace Technical Support
wrote:
> Hi Carolyn,
>
> The *intention* of the File Visits is to track file downloads. However, I
> will mention that the built-in DSpace Statistics engine is not always the
> most accurate tool. It sometimes will overcount bot activity and it may
> exclude hits from localhost. I'd *love* for it to be much more accurate,
> but it honestly hasn't had as much attention from volunteers as other
> featuresand we simply are not able to keep as up-to-date with filtering
> out bots as other statistical tools (like Google Analytics).
>
> So, if you want a rough estimate, it's likely good enough. But, if you
> desire more accurate statistics, you'd probably want to use Google
> Analytics. There's also some early discussion about supporting other
> Analytics services like Matomo (but no official work yet):
> https://github.com/DSpace/DSpace/issues/8414
>
> Tim
>
> On Tuesday, March 19, 2024 at 9:45:36 AM UTC-5 Carolyn Sullivan wrote:
>
>> A note to add to the above:
>>
>> The 'File Visits' section from what we've seen so far doesn't appear to
>> accurately reflect the number of actual downloads of a file. From the
>> back-end of Solr, we tried running a query with parameters as follows:
>>
>> "params":{
>> "q":"*:*",
>> "indent":"true",
>> "q.op":"OR",
>> "fq":["owningItem: -Mysterious Unique Id for the item that owned
>> the file of interest-",
>> "bundleName:\"ORIGINAL\""],
>> "rows":"1000",
>> "_":"Thirteen-digit-number"}},
>>
>> The results included at least four responses where staff had gone to the
>> 'Edit' page for the item, but hadn't actually downloaded the file in
>> question (we could tell because the responses include variables such as
>> time and epersonid, the latter of which can be used to determine an
>> authenticated user).
>>
>> So... is there any way to actually tell whether someone downloaded the
>> file from the Solr logs? As it stands, I'm not sure the 'File Visits'
>> statistics are meaningful.
>>
>> Thanks,
>> Carolyn.
>>
>> On Mon, Mar 18, 2024 at 5:40 PM Carolyn Sullivan
>> wrote:
>>
>>> Hello,
>>>
>>> Just wondering--how do we find the number of downloads of a pdf from a
>>> given item in DSpace? If you click on 'Statistics' in the toolbar while
>>> accessing an item page, is the 'File Visits' section equivalent to
>>> 'Downloads'?
>>>
>>> Thanks,
>>> Carolyn.
>>>
>>> --
>>> 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...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/dspace-tech/eb4a0e3e-ed84-4af0-8cb2-c30637c68ad7n%40googlegroups.com
>>>
>>> <https://groups.google.com/d/msgid/dspace-tech/eb4a0e3e-ed84-4af0-8cb2-c30637c68ad7n%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>
--
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/5f9644ea-5d0f-4b44-bb91-670d2cba239bn%40googlegroups.com.
[dspace-tech] Dspace-CRIS 2023.02.04 Handle links do not work
Hello, everyone. I decided to install the new version of Dspace-CRIS 2023.02.04 and found that the links with Handle do not work, the server just says “No item found for the identifier”. Maybe someone has encountered something similar. Thank you in advance for your response. Sincerely, Maksim. -- 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/50247a31-f168-4a22-9b9f-85b2e5e73917n%40googlegroups.com.
[dspace-tech] REST API Statistics
Hello, I have the REST API activated in version 5 of Dspace. I have seen that in the rest.cfg file, you can activate the collection of API usage statistics, with the parameter: stats = true How can these statistics be viewed? Thanks in advance. Greetings -- 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/14329d7f-3429-4218-a27d-32de9031ccaan%40googlegroups.com.
Re: [dspace-tech] Re: Dspace 7.6 issues with make-handle-config
Dear Friends,
The problem was with java class. We solved it by re-installing (build).
Example:
remove source-dspace-server
wget and unzip download source-dspace-server-7.6.1.zip
cd source-dspace-server
mvn package
On Fri, 31 May 2024 at 16:56, Ricardo Ruiz Altamiranda
wrote:
>
> Hi,
>
> Handle Technical Manual (
> http://www.handle.net/tech_manual/HandleTechnicalManual.pdf ), says:
>
>
> "The Handle.net software distribution comes with a browser-based
> administrative client, "admin.war",
> which could be accessed at https://IP-ADDRESS:8000/admin/, where the IP
> address should be the
> public address from siteinfo.json. Note that even though it is accessible
> through the Handle server as
> a convenience, this is a pure client, which talks to the handle server
> over its public HTTP API, and
> could in principle run anywhere".
>
>
>
> El lunes, 19 de febrero de 2024 a las 10:56:56 UTC-5, Mehmet Demirel
> escribió:
>
>> Same Error.
>> dspace bin/make-handle-config: line 63: /dspace/handle-server/config.dct:
>> No such file or directory
>>
>> handle.prefix = 20.500.
>> handle.canonical.prefix = https://hdl.handle.net/
>> handle.dir = ${dspace.dir}/handle-server
>>
>> On Friday 28 July 2023 at 03:46:25 UTC+3 Romy Forrer wrote:
>>
>>> Hi there
>>>
>>> I have had some problems trying to get the CNRI handle server
>>> configuration done on our new Dspace 7.6 production RHEL 8 server.
>>>
>>> We are migrating from current 6.3 production server to 7.6 production
>>> server next Tuesday so already have handle prefix etc. and just need to set
>>> up the handle server config on new server to provide handle admins with new
>>> sitebndl.zip.
>>>
>>> I initially followed instructions on
>>> https://wiki.lyrasis.org/display/DSDOC7x/Handle.Net+Registry+Support just
>>> using the command
>>>
>>> [dspace]/bin/make-handle-config
>>>
>>> This failed to prompt for any information/questions - all I got was
>>> "writing simple Handle server configuration" – no error messages. However
>>> when I opened config.dct to check it it had a different IP address to the
>>> one we want to register and was missing the lines from server_config that
>>> were supposed to appear so figured something went wrong in the process.
>>>
>>> I ran the command again hoping to get a complete file and it seemed to
>>> work ok the second time (renamed previous config.dct and made a new one but
>>> sitebndl.zip unchanged) - however I still didn't get any prompts for
>>> information/questions. I sent the sitebndl.zip to CNRI handle admins and
>>> asked them what IP/ports had come through in the sitebndl.zip since I
>>> couldn’t specify in the question answers and they reported it was the IP
>>> address we didn't want and also port 2643 instead of 2641 (which is the
>>> default handle port and is the one we had opened in our firewall)?
>>>
>>> I found -
>>> https://groups.google.com/g/dspace-tech/c/Dee91VMhkF8/m/mr7jCmmKAQAJ
>>> and figured I would try that method instead. I renamed the previous
>>> handle-server directory to handle-server-old and tried [dspace]/bin/dspace
>>> make-handle-config [dspace]/handle-server as suggested and that worked to
>>> bring up all the questions and the suggested default IP address and ports
>>> in the prompts were correct so assume the sitebndl.zip is too.
>>>
>>> However it finished with the error message below and I not sure if this
>>> is important or not for handle server operation (also had to add in the
>>> server_config parameters for the plug in manually to config.dct).
>>>
>>> "*WARNING: Error adding admin.war to server:*
>>>
>>> *java.io.FileNotFoundException: /[dspace]/admin.war (No such file or
>>> directory)*
>>>
>>> *You will have to add admin.war to the webapps subdirectory manually.*"
>>>
>>> Would someone be able to comment on whether or not we can just ignore
>>> that error (webapps directory in the handle-server directory from the
>>> original simple set up attempt was empty so hoping that admin.war isn't
>>> actually required)?
>>>
>>> I won’t attempt to start the handle server until Tuesday when we have
>>> officially cut over to the new production server so would be good to know
>>> ahead of time.
>>>
>>> Our local.cfg still has some placeholder/test definitions in it since
>>> we'
[dspace-tech] Re: Search filter
Thank you very much for responding, Do you think if we update the backend to 7.6.1 it would solve the problem? because we already implemented the layout for version 7.5, and I think it would take a while to adapt the front-end from version 7.5 to 7.6.1 Em sexta-feira, 31 de maio de 2024 às 12:30:35 UTC-3, DSpace Technical Support escreveu: > Hi Lucas, > > This appears to be working properly on the demo site ( > https://demo.dspace.org), if I'm understanding correctly. So, that may > imply this issue has been fixed in 7.6.x. > > On the demo site, there's currently an Item with an author named Avilés, > Raúl > > I can successfully use the Browse by Author for that author: > https://demo.dspace.org/browse/author?value=Avil%C3%A9s,%20Ra%C3%BAl=2 > > I can also us the "Author" search filter with that author name and find > the Item: > https://demo.dspace.org/search?query==Avil%C3%A9s,%20Ra%C3%BAl,equals > > My best guess is this may have already been fixed, so you may just need to > upgrade. > > Tim > On Monday, May 27, 2024 at 12:28:17 PM UTC-5 Lucas Silveira wrote: > >> Dear colleagues, >> >> I am using version 7.5 and I have a question. In the filter search, when >> I select to search by author, I noticed that DSpace does not retrieve >> authors with accents in their names. For example, if the name is "José" and >> I include the "é" in the search, it does not return any results, while for >> any unaccented word, it correctly retrieves authors containing the search >> string. I tested this on the demo and noticed the same behavior. >> >> Has anyone experienced this? Do you know if there is any configuration >> that can resolve this? >> >> Thank you in advance for your response. >> > -- 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/b5b84dac-1a4e-4ba4-bdf3-7c4a927fa91bn%40googlegroups.com.
[dspace-tech] Index-discovery -b failed
Hi all I have a problem with DSpace update (6.3 to 7.6.1). The database update was successful but index-discovery -b throws the following error: java.lang.NullPointerException at org.dspace.discovery.SolrServiceFileInfoPlugin.additionalIndex(SolrServiceFileInfoPlugin.java:55) at org.dspace.discovery.indexobject.IndexFactoryImpl.buildDocument(IndexFactoryImpl.java:67) at org.dspace.discovery.indexobject.DSpaceObjectIndexFactoryImpl.buildDocument(DSpaceObjectIndexFactoryImpl.java:30) at org.dspace.discovery.indexobject.ItemIndexFactoryImpl.buildDocument(ItemIndexFactoryImpl.java:146) at org.dspace.discovery.indexobject.ItemIndexFactoryImpl.buildDocument(ItemIndexFactoryImpl.java:81) at org.dspace.discovery.SolrServiceImpl.update(SolrServiceImpl.java:169) at org.dspace.discovery.SolrServiceImpl.indexContent(SolrServiceImpl.java:159) at org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:349) at org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:336) at org.dspace.discovery.SolrServiceImpl.createIndex(SolrServiceImpl.java:304) at org.dspace.discovery.IndexClient.internalRun(IndexClient.java:117) at org.dspace.scripts.DSpaceRunnable.run(DSpaceRunnable.java:150) at org.dspace.app.launcher.ScriptLauncher.executeScript(ScriptLauncher.java:154) at org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:132) at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:99) If anyone has an answer, I'll be grateful. Greetings and thanks! -- 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/e2002ee8-54ed-4825-9696-d6ae5f250a5en%40googlegroups.com.
[dspace-tech] DSpace 6.3 Bitstream details table - help needed
Hi all - We are looking for the name of the table that contains *bitstream details such as the filename & description*. The ERD shown on page 810 of the DSpace 6.x Documentation shows bitstream and bundle related tables in the pink section, but we do not find a table with the details we need. (The table named "bitstream" seems the logical location for this data, and I do see checksum there, but not the other basic information.) Are we just missing it, or are all tables not shown there? Or perhaps not all the fields for each table are shown? Thanks in advance for any assistance you can provide! Kelley Canon SIL International -- 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/5889af91-b3c6-4aee-bccc-090f8326314dn%40googlegroups.com.
[dspace-tech] Re: Failure to Access as Community Administrator
Hi Tim, Thanks for your answer! I worked around the issue giving the user Admin privileges on all the sub-communities of the community she should be admin of, which means she can do almost all of her tasks. But it's nice to know it's most likely a bug and not a issue of our repository. I will keep an eye open for these fixes on 7.6.2 Agustin El viernes, 31 de mayo de 2024 a la(s) 12:48:38 p.m. UTC-3, DSpace Technical Support escribió: > Hi Agustin, > > These issues sound very similar to ones that we've been fixing in the > upcoming 7.6.2 release (likely to be out in July/Aug). Namely these bug > tickets: > * https://github.com/DSpace/DSpace/issues/9544 > * https://github.com/DSpace/DSpace/issues/9201 > * https://github.com/DSpace/DSpace/issues/9053 > > These fixes may be difficult to backport manually (as there's a lot of > small changes involved).The cause appears to be when an EPerson is a > member of a large number of groups (either directly or inherited by nested > groups within groups) and they are *not* an Administrator. So, it's a > situation that is more likely to occur for a Community or Collection Admin, > but *not* for someone with full Administrator privileges. > > I don't know of a great way to workaround the issue (other than > temporarily making the user a full Admin or decreasing their group > memberships), but fixes are coming. We're just trying to finish getting > 8.0 out the door and then we'll have a 7.6.2 release full of backported bug > fixes. > > Tim > > On Wednesday, May 29, 2024 at 6:28:10 AM UTC-5 agustin...@unr.edu.ar > wrote: > >> Hi! >> >> I've rolled back the last change that I made "*Disable the Access Rights >> Awareness*" since it caused for some reason that the rest of the users >> lose their privileges on the rest of the communitys and collections. So I'm >> stuck in the same place as in the beginning, the "*too many boolean >> clauses*" error. >> >> Just in case, I'm working with Dspace 7.6.1 on an Ubuntu 22.04 server >> with tomcat 9, Solr 8.11.2 and postgresql 13. >> >> I really need some guidance, since I'm quite stuck with this issue. >> >> El lunes, 27 de mayo de 2024 a la(s) 12:58:27 p.m. UTC-3, Agustín Alfieri >> escribió: >> >>> Well I've found a similar post from *Alan Orth* >>> https://groups.google.com/u/1/g/dspace-tech/c/lYlxeZSVUzw/m/1q5EOlHAAgAJ >>> and I've ended up using the solution proposed on the *"I'm getting >>> "SolrException: Bad Request" followed by a long query or a "tooManyClauses" >>> Exception"* section of >>> https://wiki.lyrasis.org/display/DSArchive/TechnicalFAQ (Dspace 4). >>> >>> First I tried to implement the *maxBooleanClauses;* solution but even >>> after I set it to 8192 it didn't worked. So eventually what I did was >>> *Disable >>> the Access Rights Awareness *( >>> https://wiki.lyrasis.org/display/DSDOC4x/Discovery#Discovery-AccessRightsAwareness) >>> >>> and this appears to solve the problem. >>> >>> Nevertheless I would like to understand a little better what exactly was >>> the problem and if this is the best solution, since I'm not quite sure >>> about it. >>> >>> Again, any help would be appreciated. >>> Agustín. >>> >>> El viernes, 24 de mayo de 2024 a la(s) 12:34:02 p.m. UTC-3, Agustín >>> Alfieri escribió: >>> >>>> Update: I tried to solve the issue by adding a new user to the >>>> Community's Admin group, but the result was the same. >>>> >>>> El viernes, 24 de mayo de 2024 a la(s) 10:46:13 a.m. UTC-3, Agustín >>>> Alfieri escribió: >>>> >>>>> Hi, >>>>> >>>>> I have a user that's an Administrator for Community. When she tries >>>>> to access her Dspace account the page keeps loading the >>>>> "Recent Submissions" section and doesn't load the admin side bar. I tried >>>>> deleting all the user's permissions and setting them back but the error >>>>> persists. >>>>> >>>>> Here's the dspace.log for the error. >>>>> >>>>> 2024-05-24 10:23:18,394 ERROR unknown unknown >>>>> org.dspace.authorize.AuthorizeServiceImpl @ Failed getting getting >>>>> community/collection admin status for *user-account*@gmail.com The >>>>> search error is: Error from server at >>>>> http://localhost:8983/solr/search: >>>>> org.
Re: [dspace-tech] Re: Adding custom metadata to Communities and Collections (Dspace 7)
c.rights" for communities and collections and nothing else). I also thought that being "dc.date.issued" a standard field, it would be indexed by default. And to be fair, I've been unable to find anything in discovery.xml that suggests that it shouldn't be like that. But the fact is that it is not being indexed. Maybe I'm missing some other configuration. Thanks for your suggestions, but I'm afraid I'm still in the same situation. Let's see if anybody else can shed light on this issue... Thanks! Abel El 31/05/2024 a las 16:16, DSpace Technical Support escribió: Hi Abel, While I don't know the exact answer here (off the top of my head), here's the steps that I'd recommend taking to find the solution. First, you should check Solr itself (via http://localhost:8983/solr/ if it's running on standard ports on your localhost). Check the "search" core and search for a Community to see if the "dc.date.issued" field is indexed into Solr. If it is not, then you could try reindexing your site to see if that makes a difference (`dspace index-discovery -b`). You also can reference the DSpace Discovery documentation <https://wiki.lyrasis.org/display/DSDOC7x/Discovery> , especially the settings in discovery.xml to see if something new needs to be added to the Community/Collection settings there. However, since "dc.date.issued" is a standard field in DSpace, I *think* it's already configured in discovery.xml to be indexed by default. (Hopefully someone else on this list can correct me if I'm wrong.) Basically, though, this discovery.xml file is the settings for what fields should be indexed & which are available as facets/filters in Solr. Tim On Thursday, May 23, 2024 at 11:07:20 AM UTC-5 abg...@gmail.com wrote: Hi all, I'd like to add a custom metadata field for Communities and Collections. Let's say, for example, that I want to store the creation date of the Commmunity/Collection in a 'dc.date.issued' field. So far, I have modified the community and collection forms in the UI to be able to set and modify such fields, and it works ok. However, I'd like to be able to search for Communities and Collections based on those custom fields too. E.g., a query like this one: localhost:8080/server/api/discover/search/objects?query=dc.date.issued:2022=COMMUNITY <http://localhost:8080/server/api/discover/search/objects?query=dc.date.issued:2022=COMMUNITY> should return Communities created in 2022. However, the query returns an empty result. I've seen that Solr is not indexing the 'dc.date.issued' field for Communities/Collections, which makes me think that that is the root cause for the empty results. How can I configure the back-end to tell Solr that 'dc.date.issued' should be also indexed for Communities/Collections? I've checked the schema.xml in the Solr config, as well as the discovery.xml file, but I'm afraid I'm a bit lost. Any advice would be appreciated. Regards, Abel -- 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/fe08c14d-c528-4ecf-8773-d327127aca94n%40googlegroups.com <https://groups.google.com/d/msgid/dspace-tech/fe08c14d-c528-4ecf-8773-d327127aca94n%40googlegroups.com?utm_medium=email_source=footer>. -- Abel Gómez Llana, PhD a...@gomez.llana.me https://abel.gomez.llana.me -- 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/b2e7e92e-4117-4a75-b495-36ea5e1d77c1%40gmail.com.
[dspace-tech] Re: Failure to Access as Community Administrator
Hi Agustin, These issues sound very similar to ones that we've been fixing in the upcoming 7.6.2 release (likely to be out in July/Aug). Namely these bug tickets: * https://github.com/DSpace/DSpace/issues/9544 * https://github.com/DSpace/DSpace/issues/9201 * https://github.com/DSpace/DSpace/issues/9053 These fixes may be difficult to backport manually (as there's a lot of small changes involved).The cause appears to be when an EPerson is a member of a large number of groups (either directly or inherited by nested groups within groups) and they are *not* an Administrator. So, it's a situation that is more likely to occur for a Community or Collection Admin, but *not* for someone with full Administrator privileges. I don't know of a great way to workaround the issue (other than temporarily making the user a full Admin or decreasing their group memberships), but fixes are coming. We're just trying to finish getting 8.0 out the door and then we'll have a 7.6.2 release full of backported bug fixes. Tim On Wednesday, May 29, 2024 at 6:28:10 AM UTC-5 agustin...@unr.edu.ar wrote: > Hi! > > I've rolled back the last change that I made "*Disable the Access Rights > Awareness*" since it caused for some reason that the rest of the users > lose their privileges on the rest of the communitys and collections. So I'm > stuck in the same place as in the beginning, the "*too many boolean > clauses*" error. > > Just in case, I'm working with Dspace 7.6.1 on an Ubuntu 22.04 server with > tomcat 9, Solr 8.11.2 and postgresql 13. > > I really need some guidance, since I'm quite stuck with this issue. > > El lunes, 27 de mayo de 2024 a la(s) 12:58:27 p.m. UTC-3, Agustín Alfieri > escribió: > >> Well I've found a similar post from *Alan Orth* >> https://groups.google.com/u/1/g/dspace-tech/c/lYlxeZSVUzw/m/1q5EOlHAAgAJ >> and I've ended up using the solution proposed on the *"I'm getting >> "SolrException: Bad Request" followed by a long query or a "tooManyClauses" >> Exception"* section of >> https://wiki.lyrasis.org/display/DSArchive/TechnicalFAQ (Dspace 4). >> >> First I tried to implement the *maxBooleanClauses;* solution but even >> after I set it to 8192 it didn't worked. So eventually what I did was >> *Disable >> the Access Rights Awareness *( >> https://wiki.lyrasis.org/display/DSDOC4x/Discovery#Discovery-AccessRightsAwareness) >> >> and this appears to solve the problem. >> >> Nevertheless I would like to understand a little better what exactly was >> the problem and if this is the best solution, since I'm not quite sure >> about it. >> >> Again, any help would be appreciated. >> Agustín. >> >> El viernes, 24 de mayo de 2024 a la(s) 12:34:02 p.m. UTC-3, Agustín >> Alfieri escribió: >> >>> Update: I tried to solve the issue by adding a new user to the >>> Community's Admin group, but the result was the same. >>> >>> El viernes, 24 de mayo de 2024 a la(s) 10:46:13 a.m. UTC-3, Agustín >>> Alfieri escribió: >>> >>>> Hi, >>>> >>>> I have a user that's an Administrator for Community. When she tries to >>>> access her Dspace account the page keeps loading the "Recent Submissions" >>>> section and doesn't load the admin side bar. I tried deleting all the >>>> user's permissions and setting them back but the error persists. >>>> >>>> Here's the dspace.log for the error. >>>> >>>> 2024-05-24 10:23:18,394 ERROR unknown unknown >>>> org.dspace.authorize.AuthorizeServiceImpl @ Failed getting getting >>>> community/collection admin status for *user-account*@gmail.com The >>>> search error is: Error from server at http://localhost:8983/solr/search: >>>> org.apache.solr.search.SyntaxError: Cannot parse >>>> 'read:(g71fb6810-8a88-43ad-86bd-b73df11f6540 OR >>>> ecb5e2e7e-603b-47fa-89c8-217a81b9b7d9 OR >>>> g71fb6810-8a88-43ad-86bd-b73df11f6540 OR >>>> g6a10a411-7bd4-41db-bb16-7fe5309e2c43) OR location:( >>>> m65c45c94-d7ed-407a-8788-b20e199cb87e OR >>>> lf19298b2-8d64-4dc7-bb39-0dc3003cccf7 OR >>>> ld065ee92-f56b-41f5-ac2d-f2a323bf88b5 OR >>>> l0cfd4ed6-ea4c-4c63-aa1d-f6ad59c9c30e OR >>>> lb12c1b0a-ead0-4834-9156-621482ed5384... >>>> >>>> *.. (*a lot of other "OR bitstream") >>>> >>>> a21f5-5f33-4b84-b360-1d5462594b3a OR >>>> lf029f785-4a1b-4200-9bd3-28cd6842c036 OR >>>> lf4f36dc2-524b-4433-b188-4e67229
[dspace-tech] Re: articles not listed google scholar search
Hi, We do not have a way to force Google Scholar to index any sites. You should reach out to the Google Scholar team for advice on how to get them to index your site again? See the inclusion guidelines for Google Scholar: https://scholar.google.com/intl/en/scholar/inclusion.html Additionally, please be aware of our Search Engine Optimization guidelines for DSpace: https://wiki.lyrasis.org/display/DSDOC7x/Search+Engine+Optimization While these guidelines are not specific to Google Scholar, many of the hints/tips in them were added based on feedback from the Google Scholar team. So, it's important to double check that you site is following those guidelines if you want Google Scholar to index you well. I can verify that the Google Scholar team does reach out to myself & the DSpace Committers whenever they notice common errors from many different DSpace sites at once. Those common errors may be the sign of some bug in DSpace. When that occurs, the developers make it a priority to fix the issue in the next DSpace release. Overall, you should report your issues to Google Scholar. If they find common issues, they will report them back to DSpace developers to solve within the next release. Tim On Tuesday, May 28, 2024 at 5:41:24 PM UTC-5 sam...@wexl.in wrote: > Hello Team, > > we have created a new Dspace website, had 1000+ published articles. Its > been 8 months. > > I am unable to find these articles in google search, > As I am new to these kind of repositories, can anyone suggest me what > should be done to get indexed in google scholar. > > Thanks in advance and any support will appreciated. > > Regards, > Samdani. > -- 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/d441f98b-4616-4667-a5cb-ffca33c92a54n%40googlegroups.com.
[dspace-tech] Re: Dspace on Ubuntu 24.04
Hi Rupinder, It's very difficult for anyone to help unless you can figure out the underlying error that is occurring. A 500 error simply means that either the User Interface cannot find the REST API, or there's an error occurring in the REST API. Please follow the troubleshooting guide to try to locate the underlying error message https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove) Finding the underlying error message is the only way for others to help, as it will provide clues as to what the problem is. Once you find that error message, you may want to see if it's already answered on this mailing list (by searching the list archives <https://groups.google.com/g/dspace-tech/>) or in our Common Installation Issues <https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues> at the bottom of the Install guide. Tim On Tuesday, May 28, 2024 at 11:46:07 AM UTC-5 jesse...@gmail.com wrote: > Hi, > I just updated my dspace server to latest 24.04. and it made the installed > tomcat 9 non functional.. when I checked the package was not there. When it > tried reinstalling it with apt, it says "this release candidate is not > available". So I installed whatever version was available on 24.04, which > was Apache 10. > Now my dspace server is not showing anything on 8080 REST interface, and > web interface on port 4000 shows an error 500. > > > What is the problem? > > Thanks > Rupinder Singh > -- 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/9606fc1b-6667-497b-b8f4-f6fe40c70cean%40googlegroups.com.
[dspace-tech] Re: Search filter
Hi Lucas, This appears to be working properly on the demo site (https://demo.dspace.org), if I'm understanding correctly. So, that may imply this issue has been fixed in 7.6.x. On the demo site, there's currently an Item with an author named Avilés, Raúl I can successfully use the Browse by Author for that author: https://demo.dspace.org/browse/author?value=Avil%C3%A9s,%20Ra%C3%BAl=2 I can also us the "Author" search filter with that author name and find the Item: https://demo.dspace.org/search?query==Avil%C3%A9s,%20Ra%C3%BAl,equals My best guess is this may have already been fixed, so you may just need to upgrade. Tim On Monday, May 27, 2024 at 12:28:17 PM UTC-5 Lucas Silveira wrote: > Dear colleagues, > > I am using version 7.5 and I have a question. In the filter search, when I > select to search by author, I noticed that DSpace does not retrieve authors > with accents in their names. For example, if the name is "José" and I > include the "é" in the search, it does not return any results, while for > any unaccented word, it correctly retrieves authors containing the search > string. I tested this on the demo and noticed the same behavior. > > Has anyone experienced this? Do you know if there is any configuration > that can resolve this? > > Thank you in advance for your response. > -- 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/942bdaba-9534-4006-8e71-da8064888de6n%40googlegroups.com.
Re: [dspace-tech] Re: Adding custom metadata to Communities and Collections (Dspace 7)
Think you, I was resolving,you know how... I must create under 5 five items... Le ven. 31 mai 2024, 15:16, DSpace Technical Support < dspace-tech@googlegroups.com> a écrit : > Hi Abel, > > While I don't know the exact answer here (off the top of my head), here's > the steps that I'd recommend taking to find the solution. > > First, you should check Solr itself (via http://localhost:8983/solr/ if > it's running on standard ports on your localhost). Check the "search" core > and search for a Community to see if the "dc.date.issued" field is indexed > into Solr. > > If it is not, then you could try reindexing your site to see if that makes > a difference (`dspace index-discovery -b`). > > You also can reference the DSpace Discovery documentation > <https://wiki.lyrasis.org/display/DSDOC7x/Discovery> , especially the > settings in discovery.xml to see if something new needs to be added to the > Community/Collection settings there. However, since "dc.date.issued" is a > standard field in DSpace, I *think* it's already configured in > discovery.xml to be indexed by default. (Hopefully someone else on this > list can correct me if I'm wrong.) Basically, though, this > discovery.xml file is the settings for what fields should be indexed & > which are available as facets/filters in Solr. > > Tim > > On Thursday, May 23, 2024 at 11:07:20 AM UTC-5 abg...@gmail.com wrote: > >> Hi all, >> >> I'd like to add a custom metadata field for Communities and Collections. >> Let's say, for example, that I want to store the creation date of the >> Commmunity/Collection in a 'dc.date.issued' field. >> >> So far, I have modified the community and collection forms in the UI to >> be able to set and modify such fields, and it works ok. >> >> However, I'd like to be able to search for Communities and Collections >> based on those custom fields too. E.g., a query like this one: >> >> >> localhost:8080/server/api/discover/search/objects?query=dc.date.issued:2022=COMMUNITY >> >> should return Communities created in 2022. >> >> However, the query returns an empty result. I've seen that Solr is not >> indexing the 'dc.date.issued' field for Communities/Collections, which >> makes me think that that is the root cause for the empty results. >> >> How can I configure the back-end to tell Solr that 'dc.date.issued' >> should be also indexed for Communities/Collections? >> >> I've checked the schema.xml in the Solr config, as well as the >> discovery.xml file, but I'm afraid I'm a bit lost. >> >> Any advice would be appreciated. >> >> Regards, >> >> Abel >> > -- > 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/fe08c14d-c528-4ecf-8773-d327127aca94n%40googlegroups.com > <https://groups.google.com/d/msgid/dspace-tech/fe08c14d-c528-4ecf-8773-d327127aca94n%40googlegroups.com?utm_medium=email_source=footer> > . > -- 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/CAOQGKUMnn1%3DrfDWX2-2rXfw-Tjy2t4CK5Ad_bHFwCUpXc6Ea6g%40mail.gmail.com.
[dspace-tech] Re: Build backend without internet
Hi Salony, DSpace does require the internet to build. However, it should be possible to build it on a separate machine and copy the results over to the machine where you wish to install DSpace. To do this, you'd need to copy over **more than** just the /dspace/webapps folder. Instead, you'd need to copy over the **entire DSpace installation directory** to the new machine. So, at a basic level, you'd follow the Backend Installation Instructions <https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-BackendRequirements>, but with a few modifications: On the machine that has internet, you will need to unpack the software and run the build 1. Download DSpace code. Make sure Java, Maven & Ant are installed 2. Build via "mvn package" 3. Perform a temporary installation using "ant fresh_install". Make sure you know which folder this install is writing into. By default, it will probably write to a folder named "/dspace" On the machine which does NOT have internet: 1. Make sure Java, Tomcat, Postgres and Solr are installed (or available on another local machine). Make sure this machine has the same version of Java as the other machine. 2. Copy the *entire* installation folder from the other machine to this one. This means copy the entire "/dspace" folder and all directories. 3. Continue the rest of the installation process by initializing your DSpace configuration, the Database, Solr, and deploying to Tomcat. Basically follow the Installation Instructions as normal, but skip the steps related to "mvn" and "ant" (as you already did those on the other machine). I believe those instructions will work. But, it is always possible I've forgotten a step. So, if you run into issues, let us know on this list. Tim On Monday, May 27, 2024 at 3:14:33 AM UTC-5 salony.p...@gmail.com wrote: > Hello All, > > I need a help for building backend of Dspace without internet > > I am using DSpace-7.6 and due to security reasons mvn and ant fresh is not > allowed in my system > > I tried to build the dspace in another system and tried to copy > /dspace/webapps folder from that location to my system and restart all > services but it not worked > > Can anyone help regarding that > > Any help is highly appreciated > > Thanks and Regards > > Salony Permanand > -- 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/585c9d76-158d-4cdb-967b-006440028c85n%40googlegroups.com.
[dspace-tech] Re: Output thumbnail images in OAI
Hi, At this point in time, I don't believe thumbnail images can be shared via OAI-PMH. It would be possible to achieve this, but it'd require customizing the code of the "dspace-oai" module to save the URL of the thumbnail to a metadata field, so that it can be used/shared by the various OAI crosswalks in [dspace]/crosswalks/oai/. We do welcome code contributions from anyone (as DSpace is built/maintained by its community of users). Or you are welcome to submit a ticket <https://github.com/DSpace/DSpace/issues> to request this improvement, and we'll do our best to locate a volunteer (though usually it requires finding someone else who wants this feature). Tim On Sunday, May 26, 2024 at 1:23:52 PM UTC-5 sushan...@gmail.com wrote: > Hello, > > I am using DSpace to harvest data into VuFind, and so far I am able to > output all fields through OAI from DSpace, except for the thumbnail. Is > there a way to include the thumbnail URL in the OAI output? Any pointers > would be greatly appreciated. Thanks! > -- 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/1a3a64e9-f2cf-4261-b507-722fe1e07cc0n%40googlegroups.com.
[dspace-tech] Re: "I confirm the above license" unchecked and disabled - workflow - item submission
Hi Akshay, I've not heard of this behavior myself (and I don't see any reports in our ticketing system <https://github.com/DSpace/dspace-angular/issues> of a similar bug). My best guess here is that there may be an underlying error that is occurring, or possibly some misconfiguration of the submission form (submission-forms.xml) which is causing DSpace to behave oddly. You may want to use our Troubleshooting Guide to see if there's any error appearing in your browser's DevTools "Console" (or "Network") tab when you see this behavior. https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove) If you can find an exact error message, that would provide a clue as to what may be going on. Tim On Sunday, May 26, 2024 at 6:07:05 AM UTC-5 tsak...@gmail.com wrote: > Hi all, > > I am from The Australian National University. We have upgraded our DSpace > recently (20th May 2024) from DSpace 5.8 to Dspace 7.6.1. At the moment, we > are doing the post upgrade support. > > I am facing an issue in item submission page. The item has been submitted > by a person when dspace was in version 5.8. It goes through a workflow and > now, after upgrade, when it is claimed by one of us and tried to edit, it > looks like the deposit license checkbox "I confirm the above license" is > unchecked and disabled. PFA the image. > > I checked the api response through HAL browser for the items in the > workflow and it looks license.granted is false. > > Has anyone faced and solved this problem? > > We would be glad if someone could help us with this. > > Thanks and Regards, > Akshay Karthik Thana Sekar > > -- 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/b6d14a55-9129-4336-b796-5318c9cef43dn%40googlegroups.com.
[dspace-tech] Re: dc.date.available
Hi Maryam, This issue will be solved in the upcoming DSpace 8.0 release. As of 8.0, DSpace no longer sets the "dc.date.available" field by default (existing values in this field will still remain). The reason this has been removed is that the "dc.date.available" no longer accurately represented the correct date when an embargo existed, as Embargoes <https://wiki.lyrasis.org/display/DSDOC8x/Embargo> are now stored on the Item's resource policy (and not in metadata). See the "Breaking Changes" <https://wiki.lyrasis.org/display/DSDOC8x/Release+Notes#ReleaseNotes-BreakingChanges> section of the 8.0 Release Notes for more details. This change will not be backported to 7.x as it's considered a "breaking change" (changes the default submission behavior). But, you could manually backport it yourself by making the code changes in https://github.com/DSpace/DSpace/pull/9103 to your 7.x instance. Tim On Friday, May 24, 2024 at 1:48:49 PM UTC-5 uali...@gmail.com wrote: > Hello Everyone, > > Some ETDs are under an embargo for a set period of time. In those cases we > supply a dc.date.available field with the date the embargo lifts (and so > the content will be accessible) as the value. DSpace seems to create > a dc.date.available field upon submission with the date and time the item > was submitted. I wanted to know if it would be possible to not create a > dc.date.available field if one is already included in the metadata? > if yes, in which file I should make changes? > > Sincerely yours, > Maryam > -- 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/56c3db66-f736-4953-8190-a520cb66fde0n%40googlegroups.com.
[dspace-tech] Re: disable explorying by category
Hi Gladys, It's unclear to me what you are asking to disable. However, since you referenced "webui.browse.vocabularies.disabled = srsc", it sounds like maybe you want to disable the "Browse Subject tree" link that appears on the search page under the "Subject" filter? For example, this link appears on our demo site under the "Subject" filter here https://demo.dspace.org/search?query= If that's what you are looking to achieve, then you should modify the "vocabularies" setting in the User Interface (config.*.yml) to "enabled: false" for this "srsc" vocabulary. See the instructions here: https://wiki.lyrasis.org/display/DSDOC7x/User+Interface+Configuration#UserInterfaceConfiguration-ControlledVocabulariesinSearchFilters If that's not what you are trying to achieve, then it'd be helpful if you can provide a screenshot (or link to the demo site page) that you are trying to disable. Tim On Friday, May 24, 2024 at 5:00:36 AM UTC-5 gvfer...@gmail.com wrote: > Hello everyone, > > I am reaching out to you because I want to remove the category browsing > from the menu, the default tree structure. What I did was modify the line > in the config.prod.yml file that references this to enabled: false and in > dspace.cfg I commented out webui.browse.vocabularies.disabled = srsc. > > I am still seeing it and don't know how to remove it. > > Regards, Gladys > -- 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/c51093c6-8022-4efa-a7c5-0d7a346477adn%40googlegroups.com.
[dspace-tech] Re: Adding custom metadata to Communities and Collections (Dspace 7)
Hi Abel, While I don't know the exact answer here (off the top of my head), here's the steps that I'd recommend taking to find the solution. First, you should check Solr itself (via http://localhost:8983/solr/ if it's running on standard ports on your localhost). Check the "search" core and search for a Community to see if the "dc.date.issued" field is indexed into Solr. If it is not, then you could try reindexing your site to see if that makes a difference (`dspace index-discovery -b`). You also can reference the DSpace Discovery documentation <https://wiki.lyrasis.org/display/DSDOC7x/Discovery> , especially the settings in discovery.xml to see if something new needs to be added to the Community/Collection settings there. However, since "dc.date.issued" is a standard field in DSpace, I *think* it's already configured in discovery.xml to be indexed by default. (Hopefully someone else on this list can correct me if I'm wrong.) Basically, though, this discovery.xml file is the settings for what fields should be indexed & which are available as facets/filters in Solr. Tim On Thursday, May 23, 2024 at 11:07:20 AM UTC-5 abg...@gmail.com wrote: > Hi all, > > I'd like to add a custom metadata field for Communities and Collections. > Let's say, for example, that I want to store the creation date of the > Commmunity/Collection in a 'dc.date.issued' field. > > So far, I have modified the community and collection forms in the UI to be > able to set and modify such fields, and it works ok. > > However, I'd like to be able to search for Communities and Collections > based on those custom fields too. E.g., a query like this one: > > > localhost:8080/server/api/discover/search/objects?query=dc.date.issued:2022=COMMUNITY > > should return Communities created in 2022. > > However, the query returns an empty result. I've seen that Solr is not > indexing the 'dc.date.issued' field for Communities/Collections, which > makes me think that that is the root cause for the empty results. > > How can I configure the back-end to tell Solr that 'dc.date.issued' should > be also indexed for Communities/Collections? > > I've checked the schema.xml in the Solr config, as well as the > discovery.xml file, but I'm afraid I'm a bit lost. > > Any advice would be appreciated. > > Regards, > > Abel > -- 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/fe08c14d-c528-4ecf-8773-d327127aca94n%40googlegroups.com.
[dspace-tech] Re: Dspace 7.6 issues with make-handle-config
Hi,
Handle Technical Manual (
http://www.handle.net/tech_manual/HandleTechnicalManual.pdf ), says:
"The Handle.net software distribution comes with a browser-based
administrative client, "admin.war",
which could be accessed at https://IP-ADDRESS:8000/admin/, where the IP
address should be the
public address from siteinfo.json. Note that even though it is accessible
through the Handle server as
a convenience, this is a pure client, which talks to the handle server over
its public HTTP API, and
could in principle run anywhere".
El lunes, 19 de febrero de 2024 a las 10:56:56 UTC-5, Mehmet Demirel
escribió:
> Same Error.
> dspace bin/make-handle-config: line 63: /dspace/handle-server/config.dct:
> No such file or directory
>
> handle.prefix = 20.500.
> handle.canonical.prefix = https://hdl.handle.net/
> handle.dir = ${dspace.dir}/handle-server
>
> On Friday 28 July 2023 at 03:46:25 UTC+3 Romy Forrer wrote:
>
>> Hi there
>>
>> I have had some problems trying to get the CNRI handle server
>> configuration done on our new Dspace 7.6 production RHEL 8 server.
>>
>> We are migrating from current 6.3 production server to 7.6 production
>> server next Tuesday so already have handle prefix etc. and just need to set
>> up the handle server config on new server to provide handle admins with new
>> sitebndl.zip.
>>
>> I initially followed instructions on
>> https://wiki.lyrasis.org/display/DSDOC7x/Handle.Net+Registry+Support just
>> using the command
>>
>> [dspace]/bin/make-handle-config
>>
>> This failed to prompt for any information/questions - all I got was
>> "writing simple Handle server configuration" – no error messages. However
>> when I opened config.dct to check it it had a different IP address to the
>> one we want to register and was missing the lines from server_config that
>> were supposed to appear so figured something went wrong in the process.
>>
>> I ran the command again hoping to get a complete file and it seemed to
>> work ok the second time (renamed previous config.dct and made a new one but
>> sitebndl.zip unchanged) - however I still didn't get any prompts for
>> information/questions. I sent the sitebndl.zip to CNRI handle admins and
>> asked them what IP/ports had come through in the sitebndl.zip since I
>> couldn’t specify in the question answers and they reported it was the IP
>> address we didn't want and also port 2643 instead of 2641 (which is the
>> default handle port and is the one we had opened in our firewall)?
>>
>> I found -
>> https://groups.google.com/g/dspace-tech/c/Dee91VMhkF8/m/mr7jCmmKAQAJ and
>> figured I would try that method instead. I renamed the previous
>> handle-server directory to handle-server-old and tried [dspace]/bin/dspace
>> make-handle-config [dspace]/handle-server as suggested and that worked to
>> bring up all the questions and the suggested default IP address and ports
>> in the prompts were correct so assume the sitebndl.zip is too.
>>
>> However it finished with the error message below and I not sure if this
>> is important or not for handle server operation (also had to add in the
>> server_config parameters for the plug in manually to config.dct).
>>
>> "*WARNING: Error adding admin.war to server:*
>>
>> *java.io.FileNotFoundException: /[dspace]/admin.war (No such file or
>> directory)*
>>
>> *You will have to add admin.war to the webapps subdirectory manually.*"
>>
>> Would someone be able to comment on whether or not we can just ignore
>> that error (webapps directory in the handle-server directory from the
>> original simple set up attempt was empty so hoping that admin.war isn't
>> actually required)?
>>
>> I won’t attempt to start the handle server until Tuesday when we have
>> officially cut over to the new production server so would be good to know
>> ahead of time.
>>
>> Our local.cfg still has some placeholder/test definitions in it since
>> we're not live yet - that may be why we had problems with
>> make-handle-config (was just trying to do it early so could get the new
>> sitebndl.zip to handle admins ahead of the change date).
>>
>> Kind Regards,
>>
>> Romy
>>
>> Romy Forrer (she/her)
>>
>> Library Systems Coordinator | *Kairuruku Ratonga Matihiko*
>> Library Access and Collections |*Tūāpā Kohinga*
>> Central Library | *Te Puna M**ātauraka o Waitaha*
>>
>> Puaka - James Hight Building| Room 519
>>
>> *Phone:* +64 3 369 3875
>>
>>
[dspace-tech] Re: Dsapce 6.3 redirects to :8443/rest
For anyone still searching for this answer - I was just looking into the same problem. See https://wiki.lyrasis.org/display/DSDOC5x/REST+API -> "Disabling SSL" Anshul Sharma schrieb am Montag, 15. August 2022 um 15:22:27 UTC+2: > Hello, > My dsapce server is live and not on localhost, > When I enter "https://url;, it opens normally but, > When I enter "https://url/rest; it automatically redirects to " > https://url:8443/rest; and shows "This site can't be reached." > > Any advice/solution ? > Thanks > -- 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/22655aea-bb57-409b-88af-1b9d2824c3f2n%40googlegroups.com.
[dspace-tech] Re: Permissions Error with cron PAM configuration
Never mind, I found out that this has more to do with my institution’s extremely secure permissions and user management system. I’m going to just call the cron commands from my sudo user account. On Wednesday, May 29, 2024 at 2:21:16 PM UTC-4 Arta Seyedian wrote: > Hello. > > I am getting this error repeatedly in my server log digest everyday: > **Unmatched Entries** PAM ERROR (Permission denied) FAILED to authorize > user with PAM (Permission denied) PAM ERROR (Permission denied) FAILED to > authorize user with PAM (Permission denied) PAM ERROR (Permission denied) > PAM ERROR (Permission denied) FAILED to authorize user with PAM (Permission > denied) FAILED to authorize user with PAM (Permission denied) PAM ERROR > (Permission denied) FAILED to authorize user with PAM (Permission denied) > PAM ERROR (Permission denied) PAM ERROR (Permission denied) FAILED to > authorize user with PAM (Permission denied) FAILED to authorize user with > PAM (Permission denied) > > I was under the impression that I had resolved this issue because I found > this article > <https://serverfault.com/questions/620157/how-to-fix-a-crontab-access-issue-with-a-pam-configuration-error-message/620186#620186>, > > but I guess it didn’t stick for some reason? Not entirely sure but somehow > access.conf went back to how it was before. > > And then I decided to ssh into my server a couple of weeks after I > finished installing and I wasn’t allowed in. It would just close the port > and kick me out as soon as I would get in. > > I asked my coworker and he said, > > Hey Arta, I also cannot get in, the issue is that PAM is connected to the > Azure AD and that the DSpace user is not in AD so I guess that is why the > cron tab isn’t working. Hopefully we can just restart the SSH daemon on the > server. A lot of the system configs are set by puppet which is a remote > management service so be careful editing those as clearly it can cause some > unintended consequences > > So now I have to figure out how to set PAM permissions for my dspace user > account to run cron chores without touching system config files like > access.conf? And then his advice was to use root but… I have Tomcat set > up under the dspace user account, not root, and the installation > instructions say to set cron under the same account that runs Tomcat. > > Please let me know what I should do in this situation. We don’t have > access to Azure AD, which would be the simplest solution. > > -- 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/513a1528-7169-42ec-8473-ae460ea1155cn%40googlegroups.com.
[dspace-tech] Permissions Error with cron PAM configuration
Hello. I am getting this error repeatedly in my server log digest everyday: **Unmatched Entries** PAM ERROR (Permission denied) FAILED to authorize user with PAM (Permission denied) PAM ERROR (Permission denied) FAILED to authorize user with PAM (Permission denied) PAM ERROR (Permission denied) PAM ERROR (Permission denied) FAILED to authorize user with PAM (Permission denied) FAILED to authorize user with PAM (Permission denied) PAM ERROR (Permission denied) FAILED to authorize user with PAM (Permission denied) PAM ERROR (Permission denied) PAM ERROR (Permission denied) FAILED to authorize user with PAM (Permission denied) FAILED to authorize user with PAM (Permission denied) I was under the impression that I had resolved this issue because I found this article <https://serverfault.com/questions/620157/how-to-fix-a-crontab-access-issue-with-a-pam-configuration-error-message/620186#620186>, but I guess it didn’t stick for some reason? Not entirely sure but somehow access.conf went back to how it was before. And then I decided to ssh into my server a couple of weeks after I finished installing and I wasn’t allowed in. It would just close the port and kick me out as soon as I would get in. I asked my coworker and he said, Hey Arta, I also cannot get in, the issue is that PAM is connected to the Azure AD and that the DSpace user is not in AD so I guess that is why the cron tab isn’t working. Hopefully we can just restart the SSH daemon on the server. A lot of the system configs are set by puppet which is a remote management service so be careful editing those as clearly it can cause some unintended consequences So now I have to figure out how to set PAM permissions for my dspace user account to run cron chores without touching system config files like access.conf? And then his advice was to use root but… I have Tomcat set up under the dspace user account, not root, and the installation instructions say to set cron under the same account that runs Tomcat. Please let me know what I should do in this situation. We don’t have access to Azure AD, which would be the simplest solution. -- 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/ea8f2b99-e148-45fa-adad-ae4dd9bd5c64n%40googlegroups.com.
[dspace-tech] Error
Hola a todos, me podrían ayudar con el siguiente error: [image: error_Dspace.png] -- 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/b87d2f28-9057-41d9-abd7-26b4d57090e7n%40googlegroups.com.
[dspace-tech] Re: Failure to Access as Community Administrator
Hi! I've rolled back the last change that I made "*Disable the Access Rights Awareness*" since it caused for some reason that the rest of the users lose their privileges on the rest of the communitys and collections. So I'm stuck in the same place as in the beginning, the "*too many boolean clauses*" error. Just in case, I'm working with Dspace 7.6.1 on an Ubuntu 22.04 server with tomcat 9, Solr 8.11.2 and postgresql 13. I really need some guidance, since I'm quite stuck with this issue. El lunes, 27 de mayo de 2024 a la(s) 12:58:27 p.m. UTC-3, Agustín Alfieri escribió: > Well I've found a similar post from *Alan Orth* > https://groups.google.com/u/1/g/dspace-tech/c/lYlxeZSVUzw/m/1q5EOlHAAgAJ > and I've ended up using the solution proposed on the *"I'm getting > "SolrException: Bad Request" followed by a long query or a "tooManyClauses" > Exception"* section of > https://wiki.lyrasis.org/display/DSArchive/TechnicalFAQ (Dspace 4). > > First I tried to implement the *maxBooleanClauses;* solution but even > after I set it to 8192 it didn't worked. So eventually what I did was > *Disable > the Access Rights Awareness *( > https://wiki.lyrasis.org/display/DSDOC4x/Discovery#Discovery-AccessRightsAwareness) > > and this appears to solve the problem. > > Nevertheless I would like to understand a little better what exactly was > the problem and if this is the best solution, since I'm not quite sure > about it. > > Again, any help would be appreciated. > Agustín. > > El viernes, 24 de mayo de 2024 a la(s) 12:34:02 p.m. UTC-3, Agustín > Alfieri escribió: > >> Update: I tried to solve the issue by adding a new user to the >> Community's Admin group, but the result was the same. >> >> El viernes, 24 de mayo de 2024 a la(s) 10:46:13 a.m. UTC-3, Agustín >> Alfieri escribió: >> >>> Hi, >>> >>> I have a user that's an Administrator for Community. When she tries to >>> access her Dspace account the page keeps loading the "Recent Submissions" >>> section and doesn't load the admin side bar. I tried deleting all the >>> user's permissions and setting them back but the error persists. >>> >>> Here's the dspace.log for the error. >>> >>> 2024-05-24 10:23:18,394 ERROR unknown unknown >>> org.dspace.authorize.AuthorizeServiceImpl @ Failed getting getting >>> community/collection admin status for *user-account*@gmail.com The >>> search error is: Error from server at http://localhost:8983/solr/search: >>> org.apache.solr.search.SyntaxError: Cannot parse >>> 'read:(g71fb6810-8a88-43ad-86bd-b73df11f6540 OR >>> ecb5e2e7e-603b-47fa-89c8-217a81b9b7d9 OR >>> g71fb6810-8a88-43ad-86bd-b73df11f6540 OR >>> g6a10a411-7bd4-41db-bb16-7fe5309e2c43) OR location:( >>> m65c45c94-d7ed-407a-8788-b20e199cb87e OR >>> lf19298b2-8d64-4dc7-bb39-0dc3003cccf7 OR >>> ld065ee92-f56b-41f5-ac2d-f2a323bf88b5 OR >>> l0cfd4ed6-ea4c-4c63-aa1d-f6ad59c9c30e OR >>> lb12c1b0a-ead0-4834-9156-621482ed5384... >>> >>> *.. (*a lot of other "OR bitstream") >>> >>> a21f5-5f33-4b84-b360-1d5462594b3a OR >>> lf029f785-4a1b-4200-9bd3-28cd6842c036 OR >>> lf4f36dc2-524b-4433-b188-4e6722995110 OR >>> l12a672a4-eb94-44b7-9cc5-68894375b441 OR >>> l501d8332-12b4-4386-955d-5b68ebf30faf OR >>> l0b976fe4-9452-43cc-aabd-6c0e5276f9de)': too many boolean clauses The >>> search resourceType filter was: search.resourcetype:Collection >>> >>> >>> Any help would be appreciated. >>> Agustín. >>> >> -- 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/6568d032-88af-4745-a2a1-c991f02053a7n%40googlegroups.com.
[dspace-tech] Re: What is VuFind and have you configured your DSpace 7.6 to import external metadata from it?
HI, Vufind is a Discovery software that adds a discovery interface on top of your other library software like dspace, or Koha, OJS, or any knowledge management software that you use in your library. The benefit it provides is, VuFind can provide a single-window search retrieval system for all your different library software. VuFind can connect to this software using OAI-PMH protocol to fetch and harvest metadata records and then index it locally in its solr search engine. Once that is done, You and your library users will be able to search and retrieve content from all your connected silos(Koha, Dspace, OJS). , at a single web interface, without going to individual software. Your search will also work, even if any of the connected software goes offline, in that case, Vufind will retrieve results from its local index. It is an amazing Open Source software if you want to implement a discovery system on top of your discrete knowledge management software. Regards Rupinder Singh On Wednesday 29 May, 2024 at 2:36:38 am UTC+5:30 Carolyn Sullivan wrote: > Hello all, > > I'm reviewing the options for importing external metadata to our DSpace > 7.6 instance to ensure we have all our API keys configured and etc. One of > the options for importing external metadata is through a resource called > VuFind. I googled it and found that it's apparently a discovery system. > Is this discovery system mostly available as an option for import to DSpace > for libraries running an instance of VuFind locally? Would a local > researcher be likely to use VuFind if my institution wasn't running VuFind > anyways? Trying to figure out (1) whether to configure it and (2) what id > I'd be using to pull in metadata if I DID configure it. > > Thanks, > Carolyn. > -- 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/80e43af4-c5e7-4bba-a4c0-12aaa44d2eaan%40googlegroups.com.
[dspace-tech] create-administrator problem
When trying to create an administrator account and it throws me the following error message: First name: Admin Last name: Istrator Is the above data correct? (y or n): y Password will not display on screen. Password: Again to confirm: Exception: Error while configuring authority control, metadata field: dc.relation.funding could not be found java.lang.IllegalStateException: Error while configuring authority control, metadata field: dc.relation.funding could not be found at org.dspace.content.authority.MetadataAuthorityServiceImpl.init(MetadataAuthorityServiceImpl.java:154) at org.dspace.content.authority.MetadataAuthorityServiceImpl.makeFieldKey(MetadataAuthorityServiceImpl.java:308) at org.dspace.content.DSpaceObjectServiceImpl.addMetadata(DSpaceObjectServiceImpl.java:457) at org.dspace.content.DSpaceObjectServiceImpl.addMetadata(DSpaceObjectServiceImpl.java:220) at org.dspace.content.DSpaceObjectServiceImpl.addMetadata(DSpaceObjectServiceImpl.java:442) at org.dspace.content.DSpaceObjectServiceImpl.setMetadataSingleValue(DSpaceObjectServiceImpl.java:559) at org.dspace.eperson.EPerson.setLastName(EPerson.java:289) at org.dspace.administer.CreateAdministrator.createAdministrator(CreateAdministrator.java:276) at org.dspace.administer.CreateAdministrator.negotiateAdministratorDetails(CreateAdministrator.java:209) at org.dspace.administer.CreateAdministrator.main(CreateAdministrator.java:107) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:303) at org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:153) at org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:125) at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:100) -- 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/ea9d70e3-4a84-4c87-be1e-38871e79c856n%40googlegroups.com.
[dspace-tech] articles not listed google scholar search
Hello Team, we have created a new Dspace website, had 1000+ published articles. Its been 8 months. I am unable to find these articles in google search, As I am new to these kind of repositories, can anyone suggest me what should be done to get indexed in google scholar. Thanks in advance and any support will appreciated. Regards, Samdani. -- 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/42a3d5d8-7f04-4890-ba83-e4cee14c0d82n%40googlegroups.com.
[dspace-tech] What is VuFind and have you configured your DSpace 7.6 to import external metadata from it?
Hello all, I'm reviewing the options for importing external metadata to our DSpace 7.6 instance to ensure we have all our API keys configured and etc. One of the options for importing external metadata is through a resource called VuFind. I googled it and found that it's apparently a discovery system. Is this discovery system mostly available as an option for import to DSpace for libraries running an instance of VuFind locally? Would a local researcher be likely to use VuFind if my institution wasn't running VuFind anyways? Trying to figure out (1) whether to configure it and (2) what id I'd be using to pull in metadata if I DID configure it. Thanks, Carolyn. -- 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/9eb0aa55-5ab9-409e-9ad8-aebb4d13866en%40googlegroups.com.
[dspace-tech] Dspace on Ubuntu 24.04
Hi, I just updated my dspace server to latest 24.04. and it made the installed tomcat 9 non functional.. when I checked the package was not there. When it tried reinstalling it with apt, it says "this release candidate is not available". So I installed whatever version was available on 24.04, which was Apache 10. Now my dspace server is not showing anything on 8080 REST interface, and web interface on port 4000 shows an error 500. What is the problem? Thanks Rupinder Singh -- 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/CAMLo0tUHEm6KCLc9iRKGsPO%2BakDz_Kvez0x-%3DweU6zwMinWT%3DQ%40mail.gmail.com.
[dspace-tech] Private message regarding: Private message regarding: Issue after restore all from DSpace 5 to Dspace 7
297) at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:292) at org.apache.commons.dbcp2.DelegatingStatement.execute(DelegatingStatement.java:193) at org.apache.commons.dbcp2.DelegatingStatement.execute(DelegatingStatement.java:193) at org.dspace.storage.rdbms.DatabaseUtils.main(DatabaseUtils.java:405) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:283) at org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:134) at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:99) I'm not sure if update-sequences.sql will fix my issue anyway. Any other ideas? Thanks. -- 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/b6cf2453-4f34-4a67-a2df-169d09d91874n%40googlegroups.com.
Re: [dspace-tech] Export to CSV in Administrator Workflow
Thanks for your answer. I am using version 7.6.1 of DSpace. The button is still not shown. Emilia.- El martes, 28 de mayo de 2024 a las 10:18:24 UTC-3, Morgan, Paige escribió: > > Hi, Emilia-- > > Are you running 7.1? I remember when I encountered this problem myself – > it turned out that the export button had been written into the interface, > but it didn't actually have any functionality behind it. > > I did, at Tim Donohue's suggestion, put in a ticket suggesting that > functionality be built in, but I don't think anything has happened with > that, and in more recent versions (7.4), the icon/button has been removed. > > Good luck! > Paige > > - > *Meeting/regular work hours: Monday - Friday, 9am-4:30pm* > > *Dr. Paige C. Morgan* > (she/they) > > Digital Publishing and Copyright Librarian, > Head of Digital Initiatives & Preservation > University of Delaware Library, Museums and Press (on > Lenape land <https://native-land.ca/maps/territories/lenape/>) > Morris 118 > ORCID: https://orcid.org/-0001-8076-7356 > pai...@udel.edu > 302.831.7153 <(302)%20831-7153> > > *** I observe email-free evenings and weekends. *** > > > <https://outlook.office.com/bookwithme/user/9cba1be23fdf4b4098e3adab10600...@udel.edu?anonymous=bwmEmailSignature> > Book > time to meet with me > <https://outlook.office.com/bookwithme/user/9cba1be23fdf4b4098e3adab10600...@udel.edu?anonymous=bwmEmailSignature> > > -- > *From:* dspac...@googlegroups.com on behalf > of Emilia Lobo > *Sent:* Monday, May 27, 2024 09:54 > *To:* DSpace Technical Support > > *Subject:* Re: [dspace-tech] Export to CSV in Administrator Workflow > search-export-metadata > > Hello!, > This process indicates that it completed successfully but I don't see > where to download the completed script from the administrator account. > I don't see any link to recover that generated file. > What can be? > Thanks, > Emilia > > El miércoles, 30 de noviembre de 2022 a las 18:11:20 UTC-3, Tim Donohue > escribió: > > Hi Paige, > > Yes that makes sense. It's clear that in your use case this "Export to > CSV" is not for "Batch Metadata Editing"... it's just to generate a basic > "status report" of items in workflow. > > If you would, could you or Keith submit a bug ticket to > https://github.com/DSpace/dspace-angular/issues ? I'd recommend adding > the step by step instructions for reproducing the error. Then add in some > basic details of how you'd like to use this feature. I can then see if I > can find someone to work on this in the near future, with the hope that we > can fix it (instead of remove it). They will have to investigate the > underlying issue though to see if it's easier to fix quickly.. or remove it > (to solve the bug) temporarily & fix later. > > Overall though, the more I look at this feature, the more I think this was > accidental & never meant to appear on that page. :) So, it may turn out to > be a happy accidental feature! > > Tim > > On Wednesday, November 30, 2022 at 2:57:55 PM UTC-6 pai...@udel.edu wrote: > > Hi Tim, > > Thanks for this response! For use cases, I would find it helpful to have > in process workflow items exportable as a way of tracking what’s going on > with items that are in process, and/or that have been orphaned. When we > were running DSpace 5.3, there was no way for an administrator to even see > broadly what was happening, and what workflow items *were* in process. We > have a number of items that have been hanging out in that space, and this > is the first time that I've actually been able to see them. > > My hope is that I can work on cleaning those up, and then not have so many > sitting around -- but I would find it very helpful to be able to check and > export a CSV periodically, just to check in with folks who use the workflow > setup. > > Does that make sense as a use case? > > Thanks again, > Paige > > On Wed, Nov 30, 2022 at 15:36 Tim Donohue wrote: > > Hi Paige & Keith, > > I can confirm this is happening locally for me as well. It looks like a > possible bug. This "Export to CSV" works fine in normal search results & > also in the "Your submissions" part of MyDSpace. But, I can verify that it > doesn't work when viewing "Workflow tasks". > > That said, I admit, I wonder if that "Export to CSV" link should even > appear on the "Workflow tasks" page, as it's not really possible to perform > batch metadata editing on "Workflow tasks". (The Export
Re: [dspace-tech] Export to CSV in Administrator Workflow
Hi, Emilia-- Are you running 7.1? I remember when I encountered this problem myself – it turned out that the export button had been written into the interface, but it didn't actually have any functionality behind it. I did, at Tim Donohue's suggestion, put in a ticket suggesting that functionality be built in, but I don't think anything has happened with that, and in more recent versions (7.4), the icon/button has been removed. Good luck! Paige - Meeting/regular work hours: Monday - Friday, 9am-4:30pm Dr. Paige C. Morgan (she/they) Digital Publishing and Copyright Librarian, Head of Digital Initiatives & Preservation University of Delaware Library, Museums and Press (on Lenape land<https://native-land.ca/maps/territories/lenape/>) Morris 118 ORCID: https://orcid.org/-0001-8076-7356 paig...@udel.edu<mailto:paig...@udel.edu> 302.831.7153 ** I observe email-free evenings and weekends. ** [cid:47c69843-1b18-4174-80a9-8193c3e74b03]<https://outlook.office.com/bookwithme/user/9cba1be23fdf4b4098e3adab10600...@udel.edu?anonymous=bwmEmailSignature> Book time to meet with me<https://outlook.office.com/bookwithme/user/9cba1be23fdf4b4098e3adab10600...@udel.edu?anonymous=bwmEmailSignature> ________ From: dspace-tech@googlegroups.com on behalf of Emilia Lobo Sent: Monday, May 27, 2024 09:54 To: DSpace Technical Support Subject: Re: [dspace-tech] Export to CSV in Administrator Workflow search-export-metadata Hello!, This process indicates that it completed successfully but I don't see where to download the completed script from the administrator account. I don't see any link to recover that generated file. What can be? Thanks, Emilia El miércoles, 30 de noviembre de 2022 a las 18:11:20 UTC-3, Tim Donohue escribió: Hi Paige, Yes that makes sense. It's clear that in your use case this "Export to CSV" is not for "Batch Metadata Editing"... it's just to generate a basic "status report" of items in workflow. If you would, could you or Keith submit a bug ticket to https://github.com/DSpace/dspace-angular/issues ? I'd recommend adding the step by step instructions for reproducing the error. Then add in some basic details of how you'd like to use this feature. I can then see if I can find someone to work on this in the near future, with the hope that we can fix it (instead of remove it). They will have to investigate the underlying issue though to see if it's easier to fix quickly.. or remove it (to solve the bug) temporarily & fix later. Overall though, the more I look at this feature, the more I think this was accidental & never meant to appear on that page. :) So, it may turn out to be a happy accidental feature! Tim On Wednesday, November 30, 2022 at 2:57:55 PM UTC-6 pai...@udel.edu wrote: Hi Tim, Thanks for this response! For use cases, I would find it helpful to have in process workflow items exportable as a way of tracking what’s going on with items that are in process, and/or that have been orphaned. When we were running DSpace 5.3, there was no way for an administrator to even see broadly what was happening, and what workflow items *were* in process. We have a number of items that have been hanging out in that space, and this is the first time that I've actually been able to see them. My hope is that I can work on cleaning those up, and then not have so many sitting around -- but I would find it very helpful to be able to check and export a CSV periodically, just to check in with folks who use the workflow setup. Does that make sense as a use case? Thanks again, Paige On Wed, Nov 30, 2022 at 15:36 Tim Donohue wrote: Hi Paige & Keith, I can confirm this is happening locally for me as well. It looks like a possible bug. This "Export to CSV" works fine in normal search results & also in the "Your submissions" part of MyDSpace. But, I can verify that it doesn't work when viewing "Workflow tasks". That said, I admit, I wonder if that "Export to CSV" link should even appear on the "Workflow tasks" page, as it's not really possible to perform batch metadata editing on "Workflow tasks". (The Export to CSV feature is primarily used for Batch Metadata Editing purposes) So, this is all to say, I think there's a bug here. But, the bug might be that the option even appears on this page. Is this a specific use case you had for wanting to export Workflow Tasks to CSV? Just curious as maybe there's a way to get this possibly accidental feature "working" rather than remove it altogether. Either way, I do think this is a bug, I'm just not sure which fix is appropriate yet (remove it, or fix it). If you have time, please feel free to submit a bug ticket to https://github.com/DSpace/dspace-angular/issues I'm assuming you likely want it "fixed&qu
Re: [Extern] [dspace-tech] Submission: How to remove placeholder text from input fields
Thanks Michael for you quick help.
Best regards
Franziska
Am 22.05.2024 um 14:18 schrieb Michael Plate:
Hi Franziska,
Am 22.05.24 um 13:23 schrieb Franziska Rapp:
Hi,
We would like to remove the placeholder text in the input fields
during submission, e.g. "Author" in the Author field, "Title" in the
Title field etc.
Which modifications do we need to make?
[…]
solution is CSS:
dynamic-ng-bootstrap-input input[type=text]::placeholder{
opacity: 0 !important;
}
this is just for the standard text input (onebox), it works by setting
the opacity of the placeholder to 0, so the placeholder is there, but
not visible
solution in Typescript:
in your dspace-angular folder, open
src/app/shared/form/builder/ds-dynamic-form-ui/ds-dynamic-form-control-container.component.ts
and in the ngOnInit function set the placeholder of the model to be
empty:
[…]
ngOnInit(): void {
if( this.model.inputType=='text') {
this.model.placeholder='';
}
[…]
there are other places maybe…
CU
Michael
--
Franziska Rapp
Communication and Information Center (kiz)
Ulm University
--
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/3029b5cb-f642-4a69-8ecb-f421f507114f%40uni-ulm.de.
[dspace-tech] Search filter
Dear colleagues, I am using version 7.5 and I have a question. In the filter search, when I select to search by author, I noticed that DSpace does not retrieve authors with accents in their names. For example, if the name is "José" and I include the "é" in the search, it does not return any results, while for any unaccented word, it correctly retrieves authors containing the search string. I tested this on the demo and noticed the same behavior. Has anyone experienced this? Do you know if there is any configuration that can resolve this? Thank you in advance for your response. -- 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/4d3f1662-a750-4fb8-99e0-bb13ba78b881n%40googlegroups.com.
[dspace-tech] Re: Failure to Access as Community Administrator
Well I've found a similar post from *Alan Orth* https://groups.google.com/u/1/g/dspace-tech/c/lYlxeZSVUzw/m/1q5EOlHAAgAJ and I've ended up using the solution proposed on the *"I'm getting "SolrException: Bad Request" followed by a long query or a "tooManyClauses" Exception"* section of https://wiki.lyrasis.org/display/DSArchive/TechnicalFAQ (Dspace 4). First I tried to implement the *maxBooleanClauses;* solution but even after I set it to 8192 it didn't worked. So eventually what I did was *Disable the Access Rights Awareness *(https://wiki.lyrasis.org/display/DSDOC4x/Discovery#Discovery-AccessRightsAwareness) and this appears to solve the problem. Nevertheless I would like to understand a little better what exactly was the problem and if this is the best solution, since I'm not quite sure about it. Again, any help would be appreciated. Agustín. El viernes, 24 de mayo de 2024 a la(s) 12:34:02 p.m. UTC-3, Agustín Alfieri escribió: > Update: I tried to solve the issue by adding a new user to the Community's > Admin group, but the result was the same. > > El viernes, 24 de mayo de 2024 a la(s) 10:46:13 a.m. UTC-3, Agustín > Alfieri escribió: > >> Hi, >> >> I have a user that's an Administrator for Community. When she tries to >> access her Dspace account the page keeps loading the "Recent Submissions" >> section and doesn't load the admin side bar. I tried deleting all the >> user's permissions and setting them back but the error persists. >> >> Here's the dspace.log for the error. >> >> 2024-05-24 10:23:18,394 ERROR unknown unknown >> org.dspace.authorize.AuthorizeServiceImpl @ Failed getting getting >> community/collection admin status for *user-account*@gmail.com The >> search error is: Error from server at http://localhost:8983/solr/search: >> org.apache.solr.search.SyntaxError: Cannot parse >> 'read:(g71fb6810-8a88-43ad-86bd-b73df11f6540 OR >> ecb5e2e7e-603b-47fa-89c8-217a81b9b7d9 OR >> g71fb6810-8a88-43ad-86bd-b73df11f6540 OR >> g6a10a411-7bd4-41db-bb16-7fe5309e2c43) OR location:( >> m65c45c94-d7ed-407a-8788-b20e199cb87e OR >> lf19298b2-8d64-4dc7-bb39-0dc3003cccf7 OR >> ld065ee92-f56b-41f5-ac2d-f2a323bf88b5 OR >> l0cfd4ed6-ea4c-4c63-aa1d-f6ad59c9c30e OR >> lb12c1b0a-ead0-4834-9156-621482ed5384... >> >> *.. (*a lot of other "OR bitstream") >> >> a21f5-5f33-4b84-b360-1d5462594b3a OR >> lf029f785-4a1b-4200-9bd3-28cd6842c036 OR >> lf4f36dc2-524b-4433-b188-4e6722995110 OR >> l12a672a4-eb94-44b7-9cc5-68894375b441 OR >> l501d8332-12b4-4386-955d-5b68ebf30faf OR >> l0b976fe4-9452-43cc-aabd-6c0e5276f9de)': too many boolean clauses The >> search resourceType filter was: search.resourcetype:Collection >> >> >> Any help would be appreciated. >> Agustín. >> > -- 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/38f29ca0-3270-4d59-95fe-001028784fd6n%40googlegroups.com.
Re: [dspace-tech] Export to CSV in Administrator Workflow
search-export-metadata Hello!, This process indicates that it completed successfully but I don't see where to download the completed script from the administrator account. I don't see any link to recover that generated file. What can be? Thanks, Emilia El miércoles, 30 de noviembre de 2022 a las 18:11:20 UTC-3, Tim Donohue escribió: > Hi Paige, > > Yes that makes sense. It's clear that in your use case this "Export to > CSV" is not for "Batch Metadata Editing"... it's just to generate a basic > "status report" of items in workflow. > > If you would, could you or Keith submit a bug ticket to > https://github.com/DSpace/dspace-angular/issues ? I'd recommend adding > the step by step instructions for reproducing the error. Then add in some > basic details of how you'd like to use this feature. I can then see if I > can find someone to work on this in the near future, with the hope that we > can fix it (instead of remove it). They will have to investigate the > underlying issue though to see if it's easier to fix quickly.. or remove it > (to solve the bug) temporarily & fix later. > > Overall though, the more I look at this feature, the more I think this was > accidental & never meant to appear on that page. :) So, it may turn out to > be a happy accidental feature! > > Tim > > On Wednesday, November 30, 2022 at 2:57:55 PM UTC-6 pai...@udel.edu wrote: > >> Hi Tim, >> >> Thanks for this response! For use cases, I would find it helpful to have >> in process workflow items exportable as a way of tracking what’s going on >> with items that are in process, and/or that have been orphaned. When we >> were running DSpace 5.3, there was no way for an administrator to even see >> broadly what was happening, and what workflow items *were* in process. We >> have a number of items that have been hanging out in that space, and this >> is the first time that I've actually been able to see them. >> >> My hope is that I can work on cleaning those up, and then not have so >> many sitting around -- but I would find it very helpful to be able to check >> and export a CSV periodically, just to check in with folks who use the >> workflow setup. >> >> Does that make sense as a use case? >> >> Thanks again, >> Paige >> >> On Wed, Nov 30, 2022 at 15:36 Tim Donohue wrote: >> >>> Hi Paige & Keith, >>> >>> I can confirm this is happening locally for me as well. It looks like a >>> possible bug. This "Export to CSV" works fine in normal search results & >>> also in the "Your submissions" part of MyDSpace. But, I can verify that it >>> doesn't work when viewing "Workflow tasks". >>> >>> That said, I admit, I wonder if that "Export to CSV" link should even >>> appear on the "Workflow tasks" page, as it's not really possible to perform >>> batch metadata editing on "Workflow tasks". (The Export to CSV feature is >>> primarily used for Batch Metadata Editing purposes) >>> >>> So, this is all to say, I think there's a bug here. But, the bug might >>> be that the option even appears on this page. Is this a specific use case >>> you had for wanting to export Workflow Tasks to CSV? Just curious as maybe >>> there's a way to get this possibly accidental feature "working" rather than >>> remove it altogether. Either way, I do think this is a bug, I'm just not >>> sure which fix is appropriate yet (remove it, or fix it). >>> >>> If you have time, please feel free to submit a bug ticket to >>> https://github.com/DSpace/dspace-angular/issues I'm assuming you >>> likely want it "fixed" (rather than removed), so it'd be useful to >>> understand your use cases in this ticket. >>> >>> Thanks! >>> >>> Tim >>> >>> Tim >>> -- >>> *From:* dspac...@googlegroups.com on behalf >>> of Paige Morgan >>> *Sent:* Tuesday, November 29, 2022 3:35 PM >>> *To:* mad...@udel.edu >>> *Cc:* DSpace Technical Support >>> *Subject:* Re: [dspace-tech] Export to CSV in Administrator Workflow >>> >>> To add on to this, I get the exact same response when I try this on the >>> https://demo7.dspace.org/ site. >>> >>> I go to Administer Workflow (while logged in as administrator); it shows >>> 1-10 of 67 total items in process. On the righthand side, there's an icon >>> to
Re: [Extern] [dspace-tech] dspace ssl with apache proxy
Hi, Am 24.05.24 um 23:00 schrieb Nico Lambrechts: i have installed Dspace 7.6 on a new server. this will be a production server running ssl, so i have installed apache to proxy. from a network computer, I access https://dspace.domain, the site open with error 500. I access https://dspace.domain/server, the /server/api site open with no problem. from the server i access http://localhost:4000 and the site open with no problem. http://localhost:8080/server and the site open with no problem. my config below: local.cfg: dspace.server.url = http://localhost:8080/server dspace.ui.url = http://localhost:4000 both URLs need to be the external URLs, in your terms dspace.server.url = https://dspace.domain/server dspace.ui.url = https://dspace.domain config.prod.yml: ui: ssl: false host: localhost port: 4000 nameSpace: / rest: ssl: false host: localhost must be the same like "dspace.ui.url" w/o the protocol, just the hostname, means "dspace.domain" . port: 8080 port: 443 check your apache config and ssl correctness with openssl before going on to dspace: openssl s_client -connect dspace.domain:443 you should have complete cert chain and verify returns 0. CU Michael -- 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/a875ada1-9080-4d87-b1e4-bb5b243c18da%40bibliothek.uni-kassel.de. smime.p7s Description: Kryptografische S/MIME-Signatur
[dspace-tech] Build backend without internet
Hello All, I need a help for building backend of Dspace without internet I am using DSpace-7.6 and due to security reasons mvn and ant fresh is not allowed in my system I tried to build the dspace in another system and tried to copy /dspace/webapps folder from that location to my system and restart all services but it not worked Can anyone help regarding that Any help is highly appreciated Thanks and Regards Salony Permanand -- 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/d642fa0b-79bf-4912-9ad4-ccbda0cf2269n%40googlegroups.com.
RE: [dspace-tech] dspace ssl with apache proxy
Good day, Thank you for your earlier response, however, I have made the suggested changes to my local.cfg (attached). However, from a network connected pc; https://libdspace.ufh.ac.za does not open. https://libdspace.ufh.ac.za/server opens https://libdspace.ufh.ac.za/solr does not open from the dspace server; https://libdspace.ufh.ac.za does not open. http://localhost:4000 does not open https://libdspace.ufh.ac.za/server opens http://localhost:8080/server opens https://libdspace.ufh.ac.za/solr does not open https://localhost:4000 does not open root@dspace:/dspace/config# sudo lsof -i -P -n | grep LISTEN systemd-r 778 systemd-resolve 14u IPv4 20806 0t0 TCP 127.0.0.53:53 (LISTEN) cupsd 860root6u IPv6 21339 0t0 TCP [::1]:631 (LISTEN) cupsd 860root7u IPv4 21340 0t0 TCP 127.0.0.1:631 (LISTEN) java 893 tomcat 37u IPv6 24241 0t0 TCP *:8080 (LISTEN) postgres 959postgres5u IPv4 23627 0t0 TCP 127.0.0.1:5432 (LISTEN) sshd 965root3u IPv4 22280 0t0 TCP *:22 (LISTEN) sshd 965root4u IPv6 22282 0t0 TCP *:22 (LISTEN) apache2 1078root4u IPv6 23641 0t0 TCP *:80 (LISTEN) apache2 1078root6u IPv6 23645 0t0 TCP *:443 (LISTEN) apache2 1083www-data4u IPv6 23641 0t0 TCP *:80 (LISTEN) apache2 1083www-data6u IPv6 23645 0t0 TCP *:443 (LISTEN) apache2 1084www-data4u IPv6 23641 0t0 TCP *:80 (LISTEN) apache2 1084www-data6u IPv6 23645 0t0 TCP *:443 (LISTEN) java 1085solr 46u IPv6 25192 0t0 TCP 127.0.0.1:7983 (LISTEN) java 1085solr 167u IPv6 26754 0t0 TCP *:8983 (LISTEN) sshd 1888 dspace7u IPv6 28048 0t0 TCP [::1]:6010 (LISTEN) sshd 1888 dspace9u IPv4 28049 0t0 TCP 127.0.0.1:6010 (LISTEN) PM2\x20v5 2188root 20u IPv4 31449 0t0 TCP 127.0.0.1:4000 (LISTEN) Please help? It is my goal to access this server (single server) using https://dspace.domain/ From: Daan Lessing Sent: Saturday, May 25, 2024 10:30 AM To: Nico Lambrechts Cc: DSpace Technical Support Subject: Re: [dspace-tech] dspace ssl with apache proxy Good morning Nico, The only change I could see that needs to be done is in your local.cfg. Just remove the port numbers. If you loaded SSL already, just change to https:// dspace.server.url = http://localhost/server dspace.ui.url = http://localhost <http://localhost:4000/> Restart the frontend and backend, run nmap localhost, and see if port 4000 is open My default apache SSL config #DSpace Backend ProxyPass /server http://xxx:8080/server ProxyPassReverse /server http://xxx:8080/server #Angular UI ProxyPass / http:xxx:4000/ ProxyPassReverse / http://xxx:4000/ #solr ProxyPass /solr http://127.0.0.1:8983/solr ProxyPassReverse /solr http://127.0.0.1:8983/solr Hope this helps, Regards, Daan <https://mailtrack.io/trace/mail/551cf2ac59ef13e70043010c952371e403d863f0.png?u=5791065> On Fri, May 24, 2024 at 11:00 PM Nico Lambrechts mailto:lambrechtsn...@gmail.com> > wrote: i have installed Dspace 7.6 on a new server. this will be a production server running ssl, so i have installed apache to proxy. from a network computer, I access https://dspace.domain, the site open with error 500. I access https://dspace.domain/server, the /server/api site open with no problem. from the server i access http://localhost:4000 and the site open with no problem. http://localhost:8080/server and the site open with no problem. my config below: local.cfg: dspace.server.url = http://localhost:8080/server dspace.ui.url = http://localhost:4000 config.prod.yml: ui: ssl: false host: localhost port: 4000 nameSpace: / rest: ssl: false host: localhost port: 8080 nameSpace: /server apache: dspace.conf # Add your domain here. We've added "my.dspace.edu <http://my.dspace.edu> " as an example ServerName dspace.domain #.. setup your host how you want, including log settings... # Most installs will need these options enabled to ensure DSpace knows its hostname and scheme (http or https) # Also required to ensure correct sitemap URLs appear in /robots.txt for User Interface. ProxyPreserveHost On RequestHeader set X-Forwarded-Proto https SSLEngine on SSLCertificateFile /etc/ssl/certs/Cert2024.pem SSLCertificateKeyFile /etc/ssl/private/Cert2024.key SSLHonorCipherOrder off SSLSessionTickets off ProxyPreserveHost on Request
[dspace-tech] Output thumbnail images in OAI
Hello, I am using DSpace to harvest data into VuFind, and so far I am able to output all fields through OAI from DSpace, except for the thumbnail. Is there a way to include the thumbnail URL in the OAI output? Any pointers would be greatly appreciated. Thanks! -- 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/b88ea5d3-0b1d-4413-b205-857237eefab0n%40googlegroups.com.
[dspace-tech] "I confirm the above license" unchecked and disabled - workflow - item submission
Hi all, I am from The Australian National University. We have upgraded our DSpace recently (20th May 2024) from DSpace 5.8 to Dspace 7.6.1. At the moment, we are doing the post upgrade support. I am facing an issue in item submission page. The item has been submitted by a person when dspace was in version 5.8. It goes through a workflow and now, after upgrade, when it is claimed by one of us and tried to edit, it looks like the deposit license checkbox "I confirm the above license" is unchecked and disabled. PFA the image. I checked the api response through HAL browser for the items in the workflow and it looks license.granted is false. Has anyone faced and solved this problem? We would be glad if someone could help us with this. Thanks and Regards, Akshay Karthik Thana Sekar -- 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/4c576eda-01dc-4a6a-9a42-6c8cc9e0c43dn%40googlegroups.com.
