Re: [dspace-tech] MetadataValue: latestForDiscovery

['Eike Martin Löhden' via DSpace Technical Support]

Hej,

as far as I can oversee it, the problem is, that there is no 
metadatafield "relation.isPersonOfJob". You have to add the metadata 
fields "relation.isPersonOfJob.latestForDiscovery", 
"relation.isPersonOfJob", "relation.isJobOfPerson.latestForDiscovery" 
and "relation.isJobOfPerson" into your metadata registry 
[dspace-instance]/config/registries/relationship-formats.xml. Then you 
can load the updated registry via command line ("dspace registry-loader 
-metadata ") and it hopefully works...


Kind regards,
Eike.

Am 13.02.24 um 13:39 schrieb Aly Badr:


Hello,

I tried to add a new entity called "Job" and link it with the existing 
entity "Person". While everything is working smoothly, there's a 
glitch in the submission form where the chosen "Job" doesn't show up 
properly. There's also an error in the log, but without more details, 
it's hard to pinpoint the exact problem.


Since the relation "isJobOfPerson" is set up correctly in the relevant 
files "relationship-types.xml", 
"discovery.xml","virtual-metadata.xml", "submission-forms.xml" what 
else need to be checked to correct this problem?


Certainly, the initialization of entities has been executed, and 
reindexing, as well as server restarts, have been performed as part of 
troubleshooting


Thanks,
Aly
 virtual-metadata.xml 

    


    
        
            dc.title
        
    
    
    

 virtual-metadata.xml 


ERROR: org.dspace.content.RelationshipMetadataServiceImpl @ A 
MetadataValue was attempted to construct with MetadataField for 
parameters: metadataschema: relation, metadataelement: isJobOfPerson, 
metadataqualifier: null


ERROR:  org.dspace.content.RelationshipMetadataServiceImpl @ A 
MetadataValue was attempted to construct with MetadataField for 
parameters: metadataschema: relation, metadataelement: isJobOfPerson, 
metadataqualifier: latestForDiscovery


ERROR: org.dspace.content.RelationshipMetadataServiceImpl @ A 
MetadataValue was attempted to construct with MetadataField for 
parameters: metadataschema: relation, metadataelement: isPersonOfJob, 
metadataqualifier: latestForDiscovery


ERROR: org.dspace.content.RelationshipMetadataServiceImpl @ A 
MetadataValue was attempted to construct with MetadataField for 
parameters: metadataschema: relation, metadataelement: isJobOfPerson, 
metadataqualifier: null


ERROR: org.dspace.content.RelationshipMetadataServiceImpl @ A 
MetadataValue was attempted to construct with MetadataField for 
parameters: metadataschema: relation, metadataelement: isPersonOfJob, 
metadataqualifier: null

--
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/6e2c2970-1da0-4152-b07c-5e8203331869n%40googlegroups.com 
.


--
Eike Martin Löhden
Projektmitarbeiter, DFG-Projekt mediarep, Infrastruktur Digitale Sammlungen
Philipps-Universität Marburg
Deutschhausstraße 9
35032 Marburg

+49 6421 28-25238
eike.loeh...@staff.uni-marburg.de

--
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/38c7b7eb-e796-4a31-b6c8-ba8a4b2566e1%40staff.uni-marburg.de.


smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: [dspace-tech] Problem with Creating user in docker

['Eike Martin Löhden' via DSpace Technical Support]

Hej!

there is another possibility: you can set the user and password in the 
command line via "dspace create-administrator" and later change the 
privileges of the account via the UI.


However, getting dspace-mail running inside the docker container is a 
bit tricky. If you have a SMTP client running on your host, you'll can 
address it via "host.docker.internal".  You have to add 
"--add-host=host.docker.internal:host-gateway" to your docker-run 
command, so every request to your host can be routed through this 
address. After that, you have to allow port 25 in the firewall of the 
host for your docker-network IP-range and perhaps also modify the 
setting of your mail client. That's how it worked for us.


Kind regards,
Eike.

Am 27.01.24 um 20:09 schrieb K S:

Hi,
When creating new users, how can we set/reset password? Is it only 
through email? If it is only through email, when using docker 
deployment, we don't get the email to reset password. Was wondering 
how we can create user and set password when using DSPace with docker 
deployment. Thanks so much.

--
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/9e2af31c-8912-4be0-bd13-9215f7385608n%40googlegroups.com 
.


--
Eike Martin Löhden
Projektmitarbeiter, DFG-Projekt mediarep, Infrastruktur Digitale Sammlungen
Philipps-Universität Marburg
Deutschhausstraße 9
35032 Marburg

+49 6421 28-25238
eike.loeh...@staff.uni-marburg.de

--
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/ccd0d4b9-20e5-4245-b1d2-1f5484edbf31%40staff.uni-marburg.de.


smime.p7s
Description: Kryptografische S/MIME-Signatur

Re: [dspace-tech] External IIIF Manifest

['Eike Martin Löhden' via DSpace Technical Support]

Hei,

as far as I know, there is no possibility for this, but you can just add 
the links to the manifests and the Cantaloupe in the metadata of the 
items. And then display the metadata on the UI.


Kind regards,

Eike.


On 3.11.2023 18.43, José Luis Rodríguez Gómez wrote:

Hi all,

I wonder if there is a development or a module that allows to give a 
url of an external manifest and that dspace displays it in miradorx. I 
have a Dspace 7.6 installation.


The problem is that I have a cantaloupe and the manifests previously 
created for all my collections and I don't want to store the image 
files or the manifests in dspace.


Thanks in advance.

--
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/ca91933c-0253-4ce9-ad01-63578ce41bd7n%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/fab3a469-f9f5-4249-baec-b60cd179dcff%40staff.uni-marburg.de.


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [dspace-tech] After server down, the community, collection and item are not showing although exist in database

['Eike Martin Löhden' via DSpace Technical Support]

Hei,

did you try (re)index your content: [dspace]/bin/dspace index-discovery -b
The "-b" means, the whole repository is going to be reindexed. If you 
have a lot of data inside you might want try without this option first.


Kind regards,
Eike.


On 1.11.2023 5.24, frendy ardian wrote:

Greetings,

I have recently installed Dspace 7.6 on the university's on-premise 
server last month, yet after server maintenance last week, the 
community, collection, and item that I have pre-inputted are not shown 
on the frontend, even though I checked them still exist and are stored 
in the database. Rather, frontend shows the data in the state where it 
was last month the first time I just installed. This case has happened 
twice.


I already checked the dspace log, and tomcat log yet no clue, please help.

I am looking forward to your assistance.

Regards,
--
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/83f2799f-d2f8-45bd-b088-1c82cfa7c434n%40googlegroups.com 
.


--
_

Eike Martin Löhden
DFG-Projekt media/rep/, Projekt Infrastruktur Digitale Sammlungen

Deutschhausstraße 9
D-35037 Marburg

+49 6421 28-25238
eike.loeh...@staff.uni-marburg.de

--
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/aefe3f55-87a9-4468-bd69-b0f5d5316ec5%40staff.uni-marburg.de.


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [dspace-tech] 500 - Service unavailable

['Eike Martin Löhden' via DSpace Technical Support]

Hei,

a 500 error normally means, that the backend can't reach the frontend. 
You can try to run "yarn test:rest" to check, if the backend is 
available. Apart from this further help is difficult due to the lack of 
further information. I can only recommend to follow the troubleshoot 
guide: https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error


Kind regards,
Eike Löhden.

Am 11.09.23 um 06:47 schrieb deeksha:

Hello everyone,

I'm trying to install dspace 7.5 on my system but getting a 500 error 
with my UI. Refer to

the following attachment which contains the image of the UI.
Can someone help out with this?


--
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/6a666812-0990-4f84-9b06-8c04e8b71acbn%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/d1f47954-0f1a-a07a-4ee9-e0ba79b00644%40staff.uni-marburg.de.

Re: [dspace-tech] Large number of info-messages in log-file after accessing a collection.

['Eike Martin Löhden' via DSpace Technical Support]

Hei,

a short update to the problem. The error message at the end had nothing 
to do with the initial problem. It was just a wrong configuration in my 
virtual-medata.xml.


Kind regards,
Eike.

Am 11.09.23 um 08:52 schrieb 'Eike Martin Löhden' via DSpace Technical 
Support:


God morning!

I'm currently stuck on a problem with my dspace 7.6 instance. After a 
migration to a new server, I discovered the following problem. If I 
tried to access a collection with 100 or more items, the loading 
process became quite long and my backend logs (dspace.log) started to 
fire a hundreds of /INFO/ messages, with the following content:


2023-09-08 07:33:52,598 INFO 5b4796a9-01a8-4695-b036-db4bfe7a0687 
0c6004e9-b0ba-4cb4-a7b7-42079b79c761 
org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before 
request [GET /server/api/core/relationships/search/byLabel] originated 
from /collections/b52738a9-790d-44f7-b9e9-1e07977b8dd8


and one /ERROR/ at the end:

2023-09-08 07:34:30,393 ERROR 5b4796a9-01a8-4695-b036-db4bfe7a0687 
7077926b-486b-4002-87f9-7e6258ba13f7 
org.dspace.content.RelationshipMetadataServiceImpl @ A MetadataValue 
was attempted to construct with MetadataField for parameters: 
metadataschema: person, metadataelement: contributor, 
metadataqualifier: other


I looked through the logs of the DB, SOLR and the browser console, but 
I did not find anything like a Warning or Error. DSpace runs in a 
docker-based container setting and I'm using postgresql 15.2 and solr 
9.3. I already redid the migration process (based on the descriptions 
in the DSpace-Wiki).


Has anyone seen or experienced something similar?

Kind regards,
Eike.

--
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/691d6eb2-071d-49df-2689-3b1699a0cb62%40staff.uni-marburg.de 
<https://groups.google.com/d/msgid/dspace-tech/691d6eb2-071d-49df-2689-3b1699a0cb62%40staff.uni-marburg.de?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/53ce9cee-90cb-703c-2fc9-33a4bc1fe7d5%40staff.uni-marburg.de.

[dspace-tech] Large number of info-messages in log-file after accessing a collection.

['Eike Martin Löhden' via DSpace Technical Support]

God morning!

I'm currently stuck on a problem with my dspace 7.6 instance. After a 
migration to a new server, I discovered the following problem. If I 
tried to access a collection with 100 or more items, the loading process 
became quite long and my backend logs (dspace.log) started to fire a 
hundreds of /INFO/ messages, with the following content:


2023-09-08 07:33:52,598 INFO 5b4796a9-01a8-4695-b036-db4bfe7a0687 
0c6004e9-b0ba-4cb4-a7b7-42079b79c761 
org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
[GET /server/api/core/relationships/search/byLabel] originated from 
/collections/b52738a9-790d-44f7-b9e9-1e07977b8dd8


and one /ERROR/ at the end:

2023-09-08 07:34:30,393 ERROR 5b4796a9-01a8-4695-b036-db4bfe7a0687 
7077926b-486b-4002-87f9-7e6258ba13f7 
org.dspace.content.RelationshipMetadataServiceImpl @ A MetadataValue was 
attempted to construct with MetadataField for parameters: 
metadataschema: person, metadataelement: contributor, metadataqualifier: 
other


I looked through the logs of the DB, SOLR and the browser console, but I 
did not find anything like a Warning or Error. DSpace runs in a 
docker-based container setting and I'm using postgresql 15.2 and solr 
9.3. I already redid the migration process (based on the descriptions in 
the DSpace-Wiki).


Has anyone seen or experienced something similar?

Kind regards,
Eike.

--
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/691d6eb2-071d-49df-2689-3b1699a0cb62%40staff.uni-marburg.de.


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [dspace-tech] Dspace BE not reading local.cfg

['Eike Martin Löhden' via DSpace Technical Support]

Good Morning Dale,

I don't know, if this is the case, but the settings might be overwritten 
by environment variables. This could happen for example, if you us a 
docker setting and the default docker-compose.yml from DSpace.


Kind regards,
Eike.

Am 28.08.23 um 22:03 schrieb 'Poulter, Dale' via DSpace Technical Support:


Good afternoon,

Any reason for the Dspace BE (rest api) interface to not read the 
local.cfg file?    In the properties both at 
https://dev-BEinternal.edu/server/#/server/api 
 I get


"dspaceUI": http://localhost:4000,

"dspaceName": "DSpace at My University",

"dspaceServer": http://localhost:8080/server 
,


  "dspaceVersion": "DSpace 7.6",

However, in the local.cfg I have this

# DSpace base host URL.  Include port number etc.

dspace.baseUrl = https://dev-internal.edu 



dspace.ui.url = https://dev-internal.edu 



dspace.server.url = https://dev-BEinternal.edu/serveri 
  I get


# Name of the site

dspace.name = DEVELOPMENT  VUIR

dspace.shortname = VUIR-DEV

-Dale

Vanderbilt 





*Dale Poulter*
Director, Library Technology and Digital Services
Vanderbilt Libraries | Vanderbilt University
615-343-5388 | dale.poul...@vanderbilt.edu 
 | 
https://www.library.vanderbilt.edu 


Pronouns: he/him/his

/My working day may not be your working day. Please do not feel 
obliged to reply to this email outside of your normal working hours./


--
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/BN0PR08MB7470B409C8A73DDEFC148215FEE0A%40BN0PR08MB7470.namprd08.prod.outlook.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/7c0dbb94-0bff-0d29-ff37-23738aba6c16%40staff.uni-marburg.de.


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [dspace-tech] Re: Enable filter by an Item Type

['Eike Martin Löhden' via DSpace Technical Support]

Hey,

the type in this filter only refers to the field "dspace.entity.type". 
What you need is a filter for the field "dc.type". It already exists, 
but must be added to the default search-configuration in your 
discovery.xml ([dspace]/config/spring/api/discovery.xml). In this 
section: 
https://github.com/DSpace/DSpace/blob/bf8df5b1e8b49f0f3c13f2475d0b8732acc7fd93/dspace/config/spring/api/discovery.xml#L161


Add " to the searchFilters and 
sidebarFacets. Then execute "[dspace]/bin/dspace index-discovery -b" and 
restart the tomcat. Now it should a appear at the sidebar, if there is 
any item with this metadata-field in your repository.


Kind regards,
Eike.

Hello everybody.  In order to enable the filter "dc.type" at section 
of search in the user interface.


After reading and understanding the steps to enable the "Configurable 
Entities" , according to the guide 
,*I 
was finally able to enable them!*. According to the guide you must 
enable a defined entity model, it MUST be imported into the DSpace 
database; this is achieved by using the "initialize-entities" script. 
then through the command console I enter the following statement: sudo 
/dspace/bin/dspace initialize-entities -f 
/dspace/config/entities/relationship-types.xml


Everything is fine until here, But when I want filtering by "dc.type" 
in the search section; the*"Item Type"* filter appears; but this 
filter refers to filter by "dspace.entity.type". So when I doing click 
on the filter "Item type", shows only the *types of entities* that 
exist ( in this example are Person and Publication), and not the types 
of files ( for example a book, an article, an Learning object, etc) 
that i select when creating an item.


entities.jpg
When i create an item, i always select a type of item ( for example a 
book, an article, an Learning object, etc).


entities 2.jpg

but this type *doesn't appear* when i click in the filter "Item type"; 
this filter shows only the type of entities that exists.


How can i do in order to solve this?

Thank you very much.

On Wednesday, May 17, 2023 at 4:03:50 PM UTC-3 DSpace Technical 
Support wrote:


Hi,

The Filter By "Item Type" section will only appear if you enable
Configurable Entities.  That filter will limit the results to a
particular Entity or Item Type.
https://wiki.lyrasis.org/display/DSDOC7x/Configurable+Entities

On the demo site, we have Configurable Entities enabled by
default, which is how that filter appears.  It will automatically
appear as soon as Entities are enabled and you create two or more
types of Entities.

Tim
On Wednesday, May 17, 2023 at 10:58:06 AM UTC-5
protoste...@gmail.com wrote:

Hi everybody, I'm stuck with enabling the filter by type in
the search section of dspace.

I was researching according to this guide
, but I
can't figure out how to enable it.

this is an image capture about dspace demo, and how would it
be according to what I need

filtering.jpg
filtering.jpg

please, any kind of help will be appreciate.
thank you.
Sebastian. 


--
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/c91d862a-9337-4721-91e4-7212c426c0c4n%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/8fb08659-9736-8854-c528-c13a62f6559b%40staff.uni-marburg.de.


smime.p7s
Description: S/MIME Cryptographic Signature

[dspace-tech] Re: Incorrect URLs in OAI-interface

['Eike Martin Löhden' via DSpace Technical Support]

Hi Mohammad,

thank you very much for your help! It actually solved the problem with 
the layout and the links. But now I get a 500 error, when I try to open 
"http://localhost:8080/server/oai/request?verb=Identify;. And in the 
logs, it shows me the following stack-trace:


```
05-Jan-2023 15:08:29.852 SEVERE [http-nio-8080-exec-3] 
org.apache.catalina.core.ApplicationDispatcher.invoke Servlet.service() 
for servlet [dispatcherServlet] threw exception
    java.lang.IllegalStateException: getOutputStream() has already 
been called for this response
    at 
org.apache.catalina.connector.Response.getWriter(Response.java:584)
    at 
org.apache.catalina.connector.ResponseFacade.getWriter(ResponseFacade.java:227)
    at 
org.springframework.boot.autoconfigure.web.servlet.error.ErrorMvcAutoConfiguration$StaticView.render(ErrorMvcAutoConfiguration.java:228)
    at 
org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1401)
    at 
org.springframework.web.servlet.DispatcherServlet.processDispatchResult(DispatcherServlet.java:1145)
    at 
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1084)
    at 
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:963)
    at 
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1006)
    at 
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:898)
    at 
javax.servlet.http.HttpServlet.service(HttpServlet.java:626)
    at 
org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883)
    at 
javax.servlet.http.HttpServlet.service(HttpServlet.java:733)
    at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:227)
    at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
    at 
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
    at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
    at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
    at 
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:102)
    at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
    at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
    at 
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:102)
    at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
    at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
    at 
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:102)
    at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
    at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
    at 
org.apache.logging.log4j.web.Log4jServletFilter.doFilter(Log4jServletFilter.java:64)
    at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
    at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
    at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:710)
    at 
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:457)
    at 
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:384)
    at 
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:312)
    at 
org.springframework.boot.web.servlet.support.ErrorPageFilter.handleErrorStatus(ErrorPageFilter.java:161)
    at 
org.springframework.boot.web.servlet.support.ErrorPageFilter.doFilter(ErrorPageFilter.java:128)
    at 
org.springframework.boot.web.servlet.support.ErrorPageFilter.access$000(ErrorPageFilter.java:64)
    at 
org.springframework.boot.web.servlet.support.ErrorPageFilter$1.doFilterInternal(ErrorPageFilter.java:101)
    at 
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117)
    at 
org.springframework.boot.web.servlet.support.ErrorPageFilter.doFilter(ErrorPageFilter.java:119)
    at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
   

[dspace-tech] Incorrect URLs in OAI-interface

['Eike Martin Löhden' via DSpace Technical Support]

Hi,

I'm currently developing a DSpace-7.2 platform for medieval charters and 
facing an issue with the OAI-PMH interface. I think the same issue has 
once been reported as a bug 
(https://github.com/DSpace/DSpace/issues/8332), but marked as "cannot 
reproduce".
If I open the OAI-interface under [dspace.server.url]/oai, the links to 
- for example - "Identify" is redirected to 
[dspace.server.url]/request?verb=Identify. The OAI-page also doesn't 
have a layout, because it can't find the necessary files like 
"bootstrap.min.css", "style.css" and so on. The browser console shows a 
404 Error. I think, there is a problem with the oai-url, but I can't 
find it.
I've installed DSpace on a Debian bullseye Server with JDK-11 and using 
a postgres database.

Does anyone know this error?

Thanks and kind regards,
Eike


--
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/839cd15d-78ca-66b4-673d-840d4b3372ef%40staff.uni-marburg.de.