[dspace-tech] Private message regarding: Cannot fetch workflow groups | DSPACE 7.5

2023-02-27 Thread Aman Budgujar 
Alright. I will created a pull request on github.
Thanks for the reply.

On Saturday, February 25, 2023 at 3:33:55 AM UTC+5:30 DSpace Technical 
Support wrote:

Hi,

For code reviews, I'd recommend creating a Pull Request in GitHub or 
linking to code in GitHub.  It's very difficult to review code via email.

If you are looking to give this code back to DSpace, see our contribution 
guidelines at https://github.com/DSpace/DSpace/blob/main/CONTRIBUTING.md

Tim

On Friday, February 24, 2023 at 6:27:10 AM UTC-6 amanbu...@gmail.com wrote:

I am trying to delete all the workflow groups of a collection when the 
collection itself is deleted but I am unable to fetch any workflow group of 
any collection.
Kindly, review my code.

My modified code is from line 803 to 807. I have attached the file below. 
Original code can be found at the path - 
'dspace-api\src\main\java\org\dspace\content\CollectionServiceImpl.java';

-- 
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/6cc7dfe2-d967-4d74-94f7-91911059ce83n%40googlegroups.com.

Re: [dspace-tech] Re: Excluding metadata from browse and search result - dspace 7.3

2023-02-27 Thread WILLIAN VALMORBIDA 
Hi,

I solved this, changing the interface file:
src/app/shared/object-list/search-result-list-element/item-search-result/item-types/item/item-search-result-list-element.component.html

Thanks

--
Atenciosamente,
Willian Valmorbida
Analista de TI - Biblioteca - Univates
+55 51 3714-7000 Ramal 5992
Lajeado - RS - Brasil
www.univates.br


Em sex., 24 de fev. de 2023 às 17:50, 'Tim Donohue' via DSpace Technical
Support  escreveu:

> Hi,
>
> In case you haven't figured it out yet, I think the setting you are
> looking for is this one:
>
> https://github.com/DSpace/DSpace/blob/main/dspace/config/spring/api/discovery.xml#L2421
>
> You likely need to comment out the "dc.contributor.author" field from that
> "author" index and *reindex* your content (./dspace index-discovery -b).
>  That should ensure that only dc.creator is shown in the Author fields in
> search/browse.
>
> Tim
>
> On Thursday, February 16, 2023 at 12:39:47 AM UTC-6 tif...@gmail.com
> wrote:
>
>> Then you're probably looking for a file discovery.xml in folder
>> .../dspace/config/spring/api
>>
>> Regards,
>> Mariusz
>>
>> środa, 15 lutego 2023 o 17:48:30 UTC+1 WILLIAN VALMORBIDA napisał(a):
>>
>>> Hi,
>>>
>>> I tried this. This configuration only removes the metadata from the
>>> index, but doesn't remove the metadata (dc.contributor.*) shown in the
>>> search results.
>>> I believe that this needs to be changed in some page, but I don't
>>> located it.
>>>
>>> Thanks
>>> Willian
>>>
>>>
>>> Em qua., 15 de fev. de 2023 às 08:43, Technologiczny Informator <
>>> tif...@gmail.com> escreveu:
>>>
 Have you tried changing the webui.browse.index.2 parameter in the
 dspace.cfg file?
 In your case it should be:
 webui.browse.index.2 = author:metadata:dc.creator:text
 then rebuild the index.

 Regards,
 Mariusz

 wtorek, 14 lutego 2023 o 19:57:20 UTC+1 WILLIAN napisał(a):

> For a institutional reason, I have changed in the dspace to dc.creator
> be a main author of the document and I have used dc.contributor as advisor
> and another informations about the advisor. So, everything is fine a
> exception that the dc.creator and dc.contributor.* seems as author in the
> search and browse results. I desire that only dc.creator apear in the
> result, but no one configuration tha I have tested does that in DSpace 
> 7.3.
> Anybody knows how to exclude dc.contributor.* from search and browse
> results?
>
> --
 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/dc0321ed-28a4-49d1-a661-126289e393cen%40googlegroups.com
 
 .

>>>
>>> [image: http://www.univates.br] 
>>
>> --
> 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/020f8ed2-7194-42ae-aec8-1a3a64e3e52en%40googlegroups.com
> 
> .
>

-- 
 

-- 
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/CAG2_CwAb6LuaTy2m_sPrvMix27gR%3DHmQc0qgTYZG1MFMiu1yyA%40mail.gmail.com.

[dspace-tech] How to get OAI-PMH harvester back on track with deleted records

2023-02-27 Thread 'Dirk Leinders' via DSpace Technical Support 
Dear all

DSpace supports transient deletions 
 via OAI. 
Our external harvester has now lost track, because we have expunged many 
records. What are the options to get our external harvester back on track?

Would it be an option to re-insert the deleted records with a withdrawn 
flag in the item table? Could issues arise when we give these records that 
will not have any metadata, their required owning collection and submitter?

Best regards

Dirk

-- 
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/e3a3864d-e8a4-4b5e-b763-27597a7c7f2bn%40googlegroups.com.

[dspace-tech] dc.subject is not repeatable [Bug]

2023-02-27 Thread Jorge Alberto Bonilla Castaneda 
Good morning

revising the submission-forms.xml I was going to modify the dc.subject 
field so that it also had the "add more" button that has fields such as 
alternative title, authors, ISBN identifier. but when I went to the field 
to enable it to be repeatable I realized that it was already defined that 
way:
[image: Captura de pantalla 2023-02-27 084730.png]

but the "add more" button still does not appear

[image: Captura de pantalla 2023-02-27 084816.png]

Is there some extra configuration that I'm forgetting? , Thanks in advance.

-- 
*AVISO DE CONFIDENCIALIDAD:* Este mensaje y cualquier archivo adjunto al 
mismo, se dirige exclusivamente a su(s) destinatario(s), y no puede ser 
compartido o reenviado a un tercero sin autorización del remitente. Solo 
puede ser utilizado por las personas o entidades a las cuales está 
dirigido. 
Si usted no es el destinatario al que ha sido remitida esta 
información, queda prohibida, cualquier modificación, retención, difusión o 
copia total o parcial, y no puede emprender con ella ningún tipo de acción. 
Le rogamos que lo comunique inmediatamente por esta misma vía y proceda a 
su eliminación.
Si es miembro de la Comunidad Educativa de la UDB y viola 
lo anterior será sujeto a sanción disciplinaria conforme al Art.134, 
literales “r”, “s”, y “t” del Reglamento General Administrativo-Académico. 

*CONFIDENTIALITY NOTICE:* The content of this email and any attachments 
are intended solely for the addressee(s). The information cannot be shared 
without the authorization of the sender. It can only be used by the 
intended recipients.
If you are not the intended recipient, you are hereby 
notified that any modification, dissemination, full or partial copy of this 
email is forbidden. You must not take any kind of action in reliance on it. 
Please, notify the sender by replying to this email and delete the message 
without copying or disclosing it.
If you are a member of the UDB community 
and were to violate the foregoing, you will be subject to disciplinary 
actions in accordance to Article 134, literal “r”, “s”, and “t” of the 
General Administrative-Academic Regulations.

-- 
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/398529c7-4546-4907-a746-5c6217dab501n%40googlegroups.com.

Re: [dspace-tech] dc.subject is not repeatable [Bug]

2023-02-27 Thread Oliver Goldschmidt 

Hello Jorge,

this is not a bug - in fact the subject field is repeatable, although it 
does not have an "Add more" button. The input type "tag" just looks a 
little bit different... You can add multiple fields here just by hitting 
enter, after you have typed a subject. If you think, this is not 
intuitive enough, you can change the input type into "onebox" - there 
you will have the button "Add more" to add more fields.


Best regards
Oliver

Am 27.02.23 um 15:48 schrieb Jorge Alberto Bonilla Castaneda:

Good morning

revising the submission-forms.xml I was going to modify the dc.subject 
field so that it also had the "add more" button that has fields such 
as alternative title, authors, ISBN identifier. but when I went to the 
field to enable it to be repeatable I realized that it was already 
defined that way:

Captura de pantalla 2023-02-27 084730.png

but the "add more" button still does not appear

Captura de pantalla 2023-02-27 084816.png

Is there some extra configuration that I'm forgetting? , Thanks in 
advance.


*AVISO DE CONFIDENCIALIDAD:* Este mensaje y cualquier archivo adjunto 
al mismo, se dirige exclusivamente a su(s) destinatario(s), y no puede 
ser compartido o reenviado a un tercero sin autorización del 
remitente. Solo puede ser utilizado por las personas o entidades a las 
cuales está dirigido.
Si usted no es el destinatario al que ha sido remitida esta 
información, queda prohibida, cualquier modificación, retención, 
difusión o copia total o parcial, y no puede emprender con ella ningún 
tipo de acción. Le rogamos que lo comunique inmediatamente por esta 
misma vía y proceda a su eliminación.
Si es miembro de la Comunidad Educativa de la UDB y viola lo anterior 
será sujeto a sanción disciplinaria conforme al Art.134, literales 
“r”, “s”, y “t” del Reglamento General Administrativo-Académico.


*CONFIDENTIALITY NOTICE:* The content of this email and any 
attachments are intended solely for the addressee(s). The information 
cannot be shared without the authorization of the sender. It can only 
be used by the intended recipients.
If you are not the intended recipient, you are hereby notified that 
any modification, dissemination, full or partial copy of this email is 
forbidden. You must not take any kind of action in reliance on it. 
Please, notify the sender by replying to this email and delete the 
message without copying or disclosing it.
If you are a member of the UDB community and were to violate the 
foregoing, you will be subject to disciplinary actions in accordance 
to Article 134, literal “r”, “s”, and “t” of the General 
Administrative-Academic Regulations.

--
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/398529c7-4546-4907-a746-5c6217dab501n%40googlegroups.com 
.



--
Oliver Goldschmidt
Technische Universität Hamburg (TUHH)
Universitätsbibliothek / Digitale Dienste
Denickestr. 22
21071 Hamburg - Harburg
Tel.+49 (0)40 / 428 78 - 32 91
eMail   o.goldschm...@tuhh.de
--
GPG/PGP-Schlüssel:
http://www.tub.tu-harburg.de/ext/keys/Oliver_Goldschmidt_pub.asc  (Attention: 
The key is issued on the name Marahrens, which is my birthname - so yes, its 
really 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/9813cea5-998d-5284-3848-92bc9bde6826%40tuhh.de.

Re: [dspace-tech] dc.subject is not repeatable [Bug]

2023-02-27 Thread Jorge Alberto Bonilla Castaneda 
hello.

mmm I understand, what you explain makes a lot of sense, I will make the 
change and compile again, thank you very much for your help.

greetings

El lunes, 27 de febrero de 2023 a las 8:59:57 UTC-6, Oliver Goldschmidt 
escribió:

> Hello Jorge,
>
> this is not a bug - in fact the subject field is repeatable, although it 
> does not have an "Add more" button. The input type "tag" just looks a 
> little bit different... You can add multiple fields here just by hitting 
> enter, after you have typed a subject. If you think, this is not intuitive 
> enough, you can change the input type into "onebox" - there you will have 
> the button "Add more" to add more fields.
>
> Best regards
> Oliver
>
> Am 27.02.23 um 15:48 schrieb Jorge Alberto Bonilla Castaneda:
>
> Good morning
>
> revising the submission-forms.xml I was going to modify the dc.subject 
> field so that it also had the "add more" button that has fields such as 
> alternative title, authors, ISBN identifier. but when I went to the field 
> to enable it to be repeatable I realized that it was already defined that 
> way:
> [image: Captura de pantalla 2023-02-27 084730.png]
>
> but the "add more" button still does not appear 
>
> [image: Captura de pantalla 2023-02-27 084816.png]
>
> Is there some extra configuration that I'm forgetting? , Thanks in advance.
>
> *AVISO DE CONFIDENCIALIDAD:* Este mensaje y cualquier archivo adjunto al 
> mismo, se dirige exclusivamente a su(s) destinatario(s), y no puede ser 
> compartido o reenviado a un tercero sin autorización del remitente. Solo 
> puede ser utilizado por las personas o entidades a las cuales está 
> dirigido. 
> Si usted no es el destinatario al que ha sido remitida esta información, 
> queda prohibida, cualquier modificación, retención, difusión o copia total 
> o parcial, y no puede emprender con ella ningún tipo de acción. Le rogamos 
> que lo comunique inmediatamente por esta misma vía y proceda a su 
> eliminación.
> Si es miembro de la Comunidad Educativa de la UDB y viola lo anterior será 
> sujeto a sanción disciplinaria conforme al Art.134, literales “r”, “s”, y 
> “t” del Reglamento General Administrativo-Académico. 
>
> *CONFIDENTIALITY NOTICE:* The content of this email and any attachments 
> are intended solely for the addressee(s). The information cannot be shared 
> without the authorization of the sender. It can only be used by the 
> intended recipients.
> If you are not the intended recipient, you are hereby notified that any 
> modification, dissemination, full or partial copy of this email is 
> forbidden. You must not take any kind of action in reliance on it. Please, 
> notify the sender by replying to this email and delete the message without 
> copying or disclosing it.
> If you are a member of the UDB community and were to violate the 
> foregoing, you will be subject to disciplinary actions in accordance to 
> Article 134, literal “r”, “s”, and “t” of the General 
> Administrative-Academic Regulations.
> -- 
> 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/398529c7-4546-4907-a746-5c6217dab501n%40googlegroups.com
>  
> 
> .
>
>
> -- 
> Oliver Goldschmidt
> Technische Universität Hamburg (TUHH)
> Universitätsbibliothek / Digitale Dienste
> Denickestr. 22
> 21071 Hamburg - Harburg
> Tel.  +49 (0)40 / 428 78 - 32 91
> eMail o.gold...@tuhh.de
> --
> GPG/PGP-Schlüssel: 
> http://www.tub.tu-harburg.de/ext/keys/Oliver_Goldschmidt_pub.asc (Attention: 
> The key is issued on the name Marahrens, which is my birthname - so yes, its 
> really me)
>
>
-- 
*AVISO DE CONFIDENCIALIDAD:* Este mensaje y cualquier archivo adjunto al 
mismo, se dirige exclusivamente a su(s) destinatario(s), y no puede ser 
compartido o reenviado a un tercero sin autorización del remitente. Solo 
puede ser utilizado por las personas o entidades a las cuales está 
dirigido. 
Si usted no es el destinatario al que ha sido remitida esta 
información, queda prohibida, cualquier modificación, retención, difusión o 
copia total o parcial, y no puede emprender con ella ningún tipo de acción. 
Le rogamos que lo comunique inmediatamente por esta misma vía y proceda a 
su eliminación.
Si es miembro de la Comunidad Educativa de la UDB y viola 
lo anterior será sujeto a sanción disciplinaria conforme al Art.134, 
literales “r”, “s”, y “t” del Reglamento General Administrativo-Académico. 

*CONFIDENTIALITY NOTICE:* The content of this email and any attachments 
are inten

[dspace-tech] Register for DSpace 7.5 Live Question and Answer Session!

2023-02-27 Thread DSpace Technical Support 


Register for DSpace 7.5 Live Question and Answer Session!


When: March 29, 2023 at 14:00-15:00 UTC (use this tool to convert your 
local time to UTC time ) 


Where: Register to attend the live Zoom session 
  


In this live event, DSpace Technical Lead Tim Donohue and DSpace Program 
Coordinator Natalie Baur will host a DSpace 7.5 question and answer session. 
This free webinar will review the latest DSpace release and answer 
community questions about DSpace 7.5.  


*Please add questions that you would like to be answered during the event 
on** the following Q&A document*: https://tinyurl.com/dspace75QA  


A recording of this webinar will be made available to registrants after the 
event. 

-- 
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/67e3ea1f-ceda-4314-a7bf-60f0388346edn%40googlegroups.com.

[dspace-tech] Re: DSpace 7.5 OAI problem

2023-02-27 Thread 'Tim Donohue' via DSpace Technical Support 
Hi Milos,

The lines you shared from your logs are just a generic WARNING.  They are 
not the cause of the 500 exception & I see that same harmless warning in my 
logs even though OAI-PMH is working for me on DSpace 7.5. 

A 500 exception should have a corresponding "ERROR" in the logs (either the 
DSpace logs or Tomcat logs, or both).  See our Troubleshooting guide for 
hints/tips on finding the detailed 
error: 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Unfortunately, I'm not sure what the cause may be.  It could be something 
in your Solr setup, or maybe some sort of configuration issue?  If you can 
find an error in the logs, that may provide us with more clues.  I can 
verify though that OAI-PMH is working fine for me on 7.5, so it's likely 
there's some sort of install/configuration error in your local site.

If you can find a more detailed error, and cannot figure out the cause, 
feel free to send it to this list for additional help.

Tim
On Saturday, February 25, 2023 at 12:56:38 PM UTC-6 imi...@gmail.com wrote:

> Dear All,
>
> I have just installed the latest and greatest DSpace 7.5. On the first 
> glance, everything works ok, except for the OAI. The Solr index seems ok 
> too, and:
>
> bin/dspace oai import -c
>
> also executes without error. However, 
>
> curl http://localhost:8080/server/oai/request?verb=Identify
>
> gives error 500. In dspace.log, there are some occurrences of:
>
> 2023-02-25 19:33:09,396 WARN  unknown unknown 
> org.dspace.servicemanager.DSpaceServiceManager @ Unable to locate bean by 
> name or id=oai. Will try to look up bean by type next.
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean 
> named 'oai' available
> at 
> org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:872)
>  
> ~[spring-beans-5.3.20.jar:5.3.20]
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory.getMergedLocalBeanDefinition(AbstractBeanFactory.java:1344)
>  
> ~[spring-beans-5.3.20.jar:5.3.20]
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:309)
>  
> ~[spring-beans-5.3.20.jar:5.3.20]
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:213)
>  
> ~[spring-beans-5.3.20.jar:5.3.20]
> at 
> org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1160)
>  
> ~[spring-context-5.3.20.jar:5.3.20]
> at 
> org.dspace.servicemanager.DSpaceServiceManager.getServiceByName(DSpaceServiceManager.java:426)
>  
> [dspace-services-7.5.jar:7.5]
> at 
> org.dspace.scripts.ScriptServiceImpl.getScriptConfiguration(ScriptServiceImpl.java:34)
>  
> [dspace-api-7.5.jar:7.5]
> at 
> org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:125) 
> [dspace-api-7.5.jar:7.5]
> at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:98) 
> [dspace-api-7.5.jar:7.5]
>
> Perhaps, it is related to the OAI error. Any advice on where to look at?
>
> Thanks in advance!
> Milos
>
>
>

-- 
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/8c96d695-03e9-4873-93ce-8c8244f9510dn%40googlegroups.com.

[dspace-tech] Wrong URI on Collection/Community Pages

2023-02-27 Thread Cameron, Jacob 
Hello Everyone,

When I migrated the server to production, for some reason the old IP address is 
displaying as part of the collection and community URI.  I've attached a 
screenshot.

Everything is pointing to https://opus.uleth.ca in the yaml file, local.cfg, 
pm2 files, etc..  I'm not sure what's going on here and I've tried clearing the 
cache on my PC.  I've attached my files.  I don't see anything in the logs that 
is pointing anywhere near the old development server IP.

Any thoughts or suggestions would be appreciated.

Jake

--
Jake Cameron, BCS(UNB)
Systems Support Specialist III
Information Systems and Technical Services University of Lethbridge Library
Phone:(403)329-2756
This e-mail, including any and all attachments, is only for the use of the 
intended recipient(s) and may contain information that is confidential or 
privileged. If you are not the intended recipient, you are advised that any 
dissemination, copying or other use of this e-mail is prohibited. Please notify 
the sender of the error in communication by return e-mail and destroy all 
copies of this e-mail. Thank you.

-- 
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/YQBPR0101MB503132C36C20401C85059D0184AF9%40YQBPR0101MB5031.CANPRD01.PROD.OUTLOOK.COM.


dspace-ui.json
Description: dspace-ui.json


config.production.yml
Description: config.production.yml

[dspace-tech] Re: Wrong URI on Collection/Community Pages

2023-02-27 Thread DSpace Technical Support 
Hi Jake,

More than likely, that's the value in the "dc.identifier.uri" metadata 
field for that object.   You could update that for Items  using the Batch 
Metadata Editing 
tools... https://wiki.lyrasis.org/display/DSDOC7x/Batch+Metadata+Editing

However, if you are comfortable with SQL, the easiest fix might be to 
replace all these values at the database level in the "metadatavalue" 
table.   There's some examples of doing that in this old question to 
dspace-tech: 
https://groups.google.com/g/dspace-tech/c/o_sTXCJon24/m/hbAYPuvUBgAJ  
 (WARNING: While this is the easiest approach, I would recommend testing 
this first or backing up the database first.  You don't want to make a typo 
that results in the wrong changes to your database.)

Tim

On Monday, February 27, 2023 at 10:44:35 AM UTC-6 jacob.cameron wrote:

> Hello Everyone,
>
> When I migrated the server to production, for some reason the old IP 
> address is displaying as part of the collection and community URI. I've 
> attached a screenshot.
>
> Everything is pointing to https://opus.uleth.ca in the yaml file, 
> local.cfg, pm2 files, etc.. I'm not sure what's going on here and I've 
> tried clearing the cache on my PC. I've attached my files. I don't see 
> anything in the logs that is pointing anywhere near the old development 
> server IP.
>
> Any thoughts or suggestions would be appreciated.
>
> Jake
>
> --
> Jake Cameron, BCS(UNB)
> Systems Support Specialist III
> Information Systems and Technical Services University of Lethbridge Library
> Phone:(403)329-2756 <(403)%20329-2756>
> This e-mail, including any and all attachments, is only for the use of the 
> intended recipient(s) and may contain information that is confidential or 
> privileged. If you are not the intended recipient, you are advised that any 
> dissemination, copying or other use of this e-mail is prohibited. Please 
> notify the sender of the error in communication by return e-mail and 
> destroy all copies of this e-mail. Thank you.
>
>

-- 
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/b6b4e1d3-c816-4372-98d1-3957d03a6066n%40googlegroups.com.

[dspace-tech] Re: DSpace 7.5 OAI problem

2023-02-27 Thread Milos Ivanovic 
Dear Tim,

Many thanks for your quick and detailed reply. Fortunately, I managed to 
resolve the problem. I forgot to put *ReadWritePaths=/opt/dspace-7/ *into 
my tomcat9 systemd unit file. Now it works perfectly. 

Miloš

понедељак, 27. фебруар 2023. у 16:44:50 UTC+1 Tim Donohue је написао/ла:

> Hi Milos,
>
> The lines you shared from your logs are just a generic WARNING.  They are 
> not the cause of the 500 exception & I see that same harmless warning in my 
> logs even though OAI-PMH is working for me on DSpace 7.5. 
>
> A 500 exception should have a corresponding "ERROR" in the logs (either 
> the DSpace logs or Tomcat logs, or both).  See our Troubleshooting guide 
> for hints/tips on finding the detailed error: 
> https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)
>
> Unfortunately, I'm not sure what the cause may be.  It could be something 
> in your Solr setup, or maybe some sort of configuration issue?  If you can 
> find an error in the logs, that may provide us with more clues.  I can 
> verify though that OAI-PMH is working fine for me on 7.5, so it's likely 
> there's some sort of install/configuration error in your local site.
>
> If you can find a more detailed error, and cannot figure out the cause, 
> feel free to send it to this list for additional help.
>
> Tim
> On Saturday, February 25, 2023 at 12:56:38 PM UTC-6 imi...@gmail.com 
> wrote:
>
>> Dear All,
>>
>> I have just installed the latest and greatest DSpace 7.5. On the first 
>> glance, everything works ok, except for the OAI. The Solr index seems ok 
>> too, and:
>>
>> bin/dspace oai import -c
>>
>> also executes without error. However, 
>>
>> curl http://localhost:8080/server/oai/request?verb=Identify
>>
>> gives error 500. In dspace.log, there are some occurrences of:
>>
>> 2023-02-25 19:33:09,396 WARN  unknown unknown 
>> org.dspace.servicemanager.DSpaceServiceManager @ Unable to locate bean by 
>> name or id=oai. Will try to look up bean by type next.
>> org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean 
>> named 'oai' available
>> at 
>> org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:872)
>>  
>> ~[spring-beans-5.3.20.jar:5.3.20]
>> at 
>> org.springframework.beans.factory.support.AbstractBeanFactory.getMergedLocalBeanDefinition(AbstractBeanFactory.java:1344)
>>  
>> ~[spring-beans-5.3.20.jar:5.3.20]
>> at 
>> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:309)
>>  
>> ~[spring-beans-5.3.20.jar:5.3.20]
>> at 
>> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:213)
>>  
>> ~[spring-beans-5.3.20.jar:5.3.20]
>> at 
>> org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1160)
>>  
>> ~[spring-context-5.3.20.jar:5.3.20]
>> at 
>> org.dspace.servicemanager.DSpaceServiceManager.getServiceByName(DSpaceServiceManager.java:426)
>>  
>> [dspace-services-7.5.jar:7.5]
>> at 
>> org.dspace.scripts.ScriptServiceImpl.getScriptConfiguration(ScriptServiceImpl.java:34)
>>  
>> [dspace-api-7.5.jar:7.5]
>> at 
>> org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:125) 
>> [dspace-api-7.5.jar:7.5]
>> at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:98) 
>> [dspace-api-7.5.jar:7.5]
>>
>> Perhaps, it is related to the OAI error. Any advice on where to look at?
>>
>> Thanks in advance!
>> Milos
>>
>>
>>

-- 
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/a7aa7438-5037-4528-9e88-3d54b4f2ccecn%40googlegroups.com.

RE: [dspace-tech] Re: Wrong URI on Collection/Community Pages

2023-02-27 Thread Cameron, Jacob 
Thanks Tim!  I ran the SQL command, it took care of the problem.

--
Jake Cameron, BCS(UNB)
Systems Support Specialist III
Information Systems and Technical Services University of Lethbridge Library
Phone:(403)329-2756
This e-mail, including any and all attachments, is only for the use of the 
intended recipient(s) and may contain information that is confidential or 
privileged. If you are not the intended recipient, you are advised that any 
dissemination, copying or other use of this e-mail is prohibited. Please notify 
the sender of the error in communication by return e-mail and destroy all 
copies of this e-mail. Thank you.

From: DSpace Technical Support 
Sent: February 27, 2023 10:02 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Re: Wrong URI on Collection/Community Pages

Caution: This email was sent from someone outside of the University of 
Lethbridge. Do not click on links or open attachments unless you know they are 
safe. Suspicious emails should be forwarded to 
phish...@uleth.ca.

Hi Jake,

More than likely, that's the value in the "dc.identifier.uri" metadata field 
for that object.   You could update that for Items  using the Batch Metadata 
Editing tools... https://wiki.lyrasis.org/display/DSDOC7x/Batch+Metadata+Editing

However, if you are comfortable with SQL, the easiest fix might be to replace 
all these values at the database level in the "metadatavalue" table.   There's 
some examples of doing that in this old question to dspace-tech: 
https://groups.google.com/g/dspace-tech/c/o_sTXCJon24/m/hbAYPuvUBgAJ   
(WARNING: While this is the easiest approach, I would recommend testing this 
first or backing up the database first.  You don't want to make a typo that 
results in the wrong changes to your database.)

Tim
On Monday, February 27, 2023 at 10:44:35 AM UTC-6 jacob.cameron wrote:
Hello Everyone,

When I migrated the server to production, for some reason the old IP address is 
displaying as part of the collection and community URI. I've attached a 
screenshot.

Everything is pointing to https://opus.uleth.ca in the yaml file, local.cfg, 
pm2 files, etc.. I'm not sure what's going on here and I've tried clearing the 
cache on my PC. I've attached my files. I don't see anything in the logs that 
is pointing anywhere near the old development server IP.

Any thoughts or suggestions would be appreciated.

Jake

--
Jake Cameron, BCS(UNB)
Systems Support Specialist III
Information Systems and Technical Services University of Lethbridge Library
Phone:(403)329-2756
This e-mail, including any and all attachments, is only for the use of the 
intended recipient(s) and may contain information that is confidential or 
privileged. If you are not the intended recipient, you are advised that any 
dissemination, copying or other use of this e-mail is prohibited. Please notify 
the sender of the error in communication by return e-mail and destroy all 
copies of this e-mail. Thank you.
--
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/b6b4e1d3-c816-4372-98d1-3957d03a6066n%40googlegroups.com.

-- 
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/YQBPR0101MB503167A2F43E8ACC37312DC684AF9%40YQBPR0101MB5031.CANPRD01.PROD.OUTLOOK.COM.

[dspace-tech] Handle Server Issue

2023-02-27 Thread Cameron, Jacob 
Hi Everyone,

Windows, Tomcat 9.6, DSpace 7.4

I saw the posts https://groups.google.com/g/dspace-tech/c/7WHZ9gkMxSo and 
https://groups.google.com/g/dspace-tech/c/lr7kfeLLEjg/m/PAptuDo8BAAJ.  I have 
tried replacing the JARs as suggested, even though the missing JARs were 
associated with DSpace 7.3.  I also tried rebuilding the backend to make sure 
there was nothing funky there but I still get the same error with the handle 
server.  Nothing is showing up in any of the other log files.

"2023-02-27 14:17:00.660-0700" 25 Started new run.
"2023-02-27 14:17:00.660-0700" 25 Handle.net Server Software version 9.3.0
Exception in thread "main" java.lang.NoClassDefFoundError: 
com/sleepycat/je/DatabaseException
at net.handle.server.HandleServer.initTxnQueue(HandleServer.java:732)
at net.handle.server.HandleServer.(HandleServer.java:382)
at net.handle.server.AbstractServer.getInstance(AbstractServer.java:120)
at net.handle.server.Main.initialize(Main.java:255)
at net.handle.server.Main.main(Main.java:122)
Caused by: java.lang.ClassNotFoundException: com.sleepycat.je.DatabaseException
at 
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
at 
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
... 5 more

--
Jake Cameron, BCS(UNB)
Systems Support Specialist III
Information Systems and Technical Services University of Lethbridge Library
Phone:(403)329-2756
This e-mail, including any and all attachments, is only for the use of the 
intended recipient(s) and may contain information that is confidential or 
privileged. If you are not the intended recipient, you are advised that any 
dissemination, copying or other use of this e-mail is prohibited. Please notify 
the sender of the error in communication by return e-mail and destroy all 
copies of this e-mail. Thank you.

-- 
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/YQBPR0101MB5031C612FC1352B99273B30784AF9%40YQBPR0101MB5031.CANPRD01.PROD.OUTLOOK.COM.

[dspace-tech] Re: Handle Server Issue

2023-02-27 Thread Mohammad S. AlMutairi 
Hello Jake,

See if this old post would help ( 
https://groups.google.com/g/dspace-tech/c/wiI45y7xSRs/m/XddGRNE6AQAJ ). 

BR
On Tuesday, February 28, 2023 at 12:23:38 AM UTC+3 Cameron, Jacob wrote:

> Hi Everyone,
>
> Windows, Tomcat 9.6, DSpace 7.4
>
> I saw the posts https://groups.google.com/g/dspace-tech/c/7WHZ9gkMxSo and 
> https://groups.google.com/g/dspace-tech/c/lr7kfeLLEjg/m/PAptuDo8BAAJ. I 
> have tried replacing the JARs as suggested, even though the missing JARs 
> were associated with DSpace 7.3. I also tried rebuilding the backend to 
> make sure there was nothing funky there but I still get the same error with 
> the handle server. Nothing is showing up in any of the other log files.
>
> "2023-02-27 14:17:00.660-0700" 25 Started new run.
> "2023-02-27 14:17:00.660-0700" 25 Handle.net Server Software version 9.3.0
> Exception in thread "main" java.lang.NoClassDefFoundError: 
> com/sleepycat/je/DatabaseException
> at net.handle.server.HandleServer.initTxnQueue(HandleServer.java:732)
> at net.handle.server.HandleServer.(HandleServer.java:382)
> at net.handle.server.AbstractServer.getInstance(AbstractServer.java:120)
> at net.handle.server.Main.initialize(Main.java:255)
> at net.handle.server.Main.main(Main.java:122)
> Caused by: java.lang.ClassNotFoundException: 
> com.sleepycat.je.DatabaseException
> at 
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
> at 
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
> ... 5 more
>
> --
> Jake Cameron, BCS(UNB)
> Systems Support Specialist III
> Information Systems and Technical Services University of Lethbridge Library
> Phone:(403)329-2756 <(403)%20329-2756>
> This e-mail, including any and all attachments, is only for the use of the 
> intended recipient(s) and may contain information that is confidential or 
> privileged. If you are not the intended recipient, you are advised that any 
> dissemination, copying or other use of this e-mail is prohibited. Please 
> notify the sender of the error in communication by return e-mail and 
> destroy all copies of this e-mail. Thank you.
>
>

-- 
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/9a303d71-fec9-4a47-aca7-fafe6a606725n%40googlegroups.com.

RE: [dspace-tech] Re: Handle Server Issue

2023-02-27 Thread Cameron, Jacob 
Thanks Mohammad.

I’m not sure what was different.  Your initial instructions were the ones I 
followed when I created here.  I deleted my old handle-server folder and tried 
them again and now it works.

--
Jake Cameron, BCS(UNB)
Systems Support Specialist III
Information Systems and Technical Services University of Lethbridge Library
Phone:(403)329-2756
This e-mail, including any and all attachments, is only for the use of the 
intended recipient(s) and may contain information that is confidential or 
privileged. If you are not the intended recipient, you are advised that any 
dissemination, copying or other use of this e-mail is prohibited. Please notify 
the sender of the error in communication by return e-mail and destroy all 
copies of this e-mail. Thank you.

From: dspace-tech@googlegroups.com  On Behalf Of 
Mohammad S. AlMutairi
Sent: February 27, 2023 2:34 PM
To: DSpace Technical Support 
Subject: [dspace-tech] Re: Handle Server Issue

Caution: This email was sent from someone outside of the University of 
Lethbridge. Do not click on links or open attachments unless you know they are 
safe. Suspicious emails should be forwarded to 
phish...@uleth.ca.

Hello Jake,

See if this old post would help ( 
https://groups.google.com/g/dspace-tech/c/wiI45y7xSRs/m/XddGRNE6AQAJ ).
BR
On Tuesday, February 28, 2023 at 12:23:38 AM UTC+3 Cameron, Jacob wrote:
Hi Everyone,

Windows, Tomcat 9.6, DSpace 7.4

I saw the posts https://groups.google.com/g/dspace-tech/c/7WHZ9gkMxSo and 
https://groups.google.com/g/dspace-tech/c/lr7kfeLLEjg/m/PAptuDo8BAAJ. I have 
tried replacing the JARs as suggested, even though the missing JARs were 
associated with DSpace 7.3. I also tried rebuilding the backend to make sure 
there was nothing funky there but I still get the same error with the handle 
server. Nothing is showing up in any of the other log files.

"2023-02-27 14:17:00.660-0700" 25 Started new run.
"2023-02-27 14:17:00.660-0700" 25 Handle.net Server Software version 9.3.0
Exception in thread "main" java.lang.NoClassDefFoundError: 
com/sleepycat/je/DatabaseException
at net.handle.server.HandleServer.initTxnQueue(HandleServer.java:732)
at net.handle.server.HandleServer.(HandleServer.java:382)
at net.handle.server.AbstractServer.getInstance(AbstractServer.java:120)
at net.handle.server.Main.initialize(Main.java:255)
at net.handle.server.Main.main(Main.java:122)
Caused by: java.lang.ClassNotFoundException: com.sleepycat.je.DatabaseException
at 
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
at 
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
... 5 more

--
Jake Cameron, BCS(UNB)
Systems Support Specialist III
Information Systems and Technical Services University of Lethbridge Library
Phone:(403)329-2756
This e-mail, including any and all attachments, is only for the use of the 
intended recipient(s) and may contain information that is confidential or 
privileged. If you are not the intended recipient, you are advised that any 
dissemination, copying or other use of this e-mail is prohibited. Please notify 
the sender of the error in communication by return e-mail and destroy all 
copies of this e-mail. Thank you.
--
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/9a303d71-fec9-4a47-aca7-fafe6a606725n%40googlegroups.com.

-- 
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/YQBPR0101MB503180EAD27B8F7D86C928AB84AF9%40YQBPR0101MB5031.CANPRD01.PROD.OUTLOOK.COM.

Re: [dspace-tech] Re: Handle Server Issue

2023-02-27 Thread Mohammad S. AlMutairi 
Hi Jake,

You did not need to copy the 6 jar files (not if what you have is dspace 
version 7.4 ).The handle issue you faced and reported in this thread ( 
Exception in thread "main" java.lang.NoClassDefFoundError: 
com/sleepycat/je/DatabaseException  ) is the exact same issue Lewatle 
faced. It's caused by a missing handle storage plugin setup in 
[dspace]/handle-server/config.dct 
and the fix to it is by adding the plugin configuration and it's totally 
different from what Fatih reported in his thread. Fatih was using DSpace 
7.3 and the 6 jar files was missing in that version and the fix is by 
adding those jars files.

BR


On Tuesday, February 28, 2023 at 1:50:10 AM UTC+3 Cameron, Jacob wrote:

Thanks Mohammad.

 

I’m not sure what was different.  Your initial instructions were the ones I 
followed when I created here.  I deleted my old handle-server folder and 
tried them again and now it works.  

 

--

Jake Cameron, BCS(UNB)

Systems Support Specialist III

Information Systems and Technical Services University of Lethbridge Library

Phone:(403)329-2756

This e-mail, including any and all attachments, is only for the use of the 
intended recipient(s) and may contain information that is confidential or 
privileged. If you are not the intended recipient, you are advised that any 
dissemination, copying or other use of this e-mail is prohibited. Please 
notify the sender of the error in communication by return e-mail and 
destroy all copies of this e-mail. Thank you.

 

*From:* dspac...@googlegroups.com  *On Behalf Of 
*Mohammad S. AlMutairi
*Sent:* February 27, 2023 2:34 PM
*To:* DSpace Technical Support 
*Subject:* [dspace-tech] Re: Handle Server Issue

 

Caution: This email was sent from someone *outside of the University of 
Lethbridge*. Do not click on links or open attachments unless you know they 
are safe. Suspicious emails should be forwarded to phis...@uleth.ca.

 

Hello Jake, 

 

See if this old post would help ( 
https://groups.google.com/g/dspace-tech/c/wiI45y7xSRs/m/XddGRNE6AQAJ ). 

BR

On Tuesday, February 28, 2023 at 12:23:38 AM UTC+3 Cameron, Jacob wrote:

Hi Everyone, 

Windows, Tomcat 9.6, DSpace 7.4 

I saw the posts https://groups.google.com/g/dspace-tech/c/7WHZ9gkMxSo and 
https://groups.google.com/g/dspace-tech/c/lr7kfeLLEjg/m/PAptuDo8BAAJ. I 
have tried replacing the JARs as suggested, even though the missing JARs 
were associated with DSpace 7.3. I also tried rebuilding the backend to 
make sure there was nothing funky there but I still get the same error with 
the handle server. Nothing is showing up in any of the other log files. 

"2023-02-27 14:17:00.660-0700" 25 Started new run. 
"2023-02-27 14:17:00.660-0700" 25 Handle.net Server Software version 9.3.0 
Exception in thread "main" java.lang.NoClassDefFoundError: 
com/sleepycat/je/DatabaseException 
at net.handle.server.HandleServer.initTxnQueue(HandleServer.java:732) 
at net.handle.server.HandleServer.(HandleServer.java:382) 
at net.handle.server.AbstractServer.getInstance(AbstractServer.java:120) 
at net.handle.server.Main.initialize(Main.java:255) 
at net.handle.server.Main.main(Main.java:122) 
Caused by: java.lang.ClassNotFoundException: 
com.sleepycat.je.DatabaseException 
at 
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
 

at 
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
 

at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522) 
... 5 more 

-- 
Jake Cameron, BCS(UNB) 
Systems Support Specialist III 
Information Systems and Technical Services University of Lethbridge Library 
Phone:(403)329-2756 
This e-mail, including any and all attachments, is only for the use of the 
intended recipient(s) and may contain information that is confidential or 
privileged. If you are not the intended recipient, you are advised that any 
dissemination, copying or other use of this e-mail is prohibited. Please 
notify the sender of the error in communication by return e-mail and 
destroy all copies of this e-mail. Thank you. 

-- 
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/9a303d71-fec9-4a47-aca7-fafe6a606725n%40googlegroups.com
 

.

-- 
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 fro