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
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
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
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:
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:
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
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
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'
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:
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
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
11 matches
Mail list logo
