No es la mejor solución, pero podrías crear un nuevo metadato para
almacenar la colección, y luego llamar a ese metadato en discovery.
El viernes, 5 de enero de 2024 a las 9:54:01 UTC-3, Salony Permanand
escribió:
>
> Hello All,
>
> I am using DSpace 7.6 version
>
> In frontend I have discover
Hello All,
I am using DSPACE 7.6 version
I want to know that is it possible to link same bitstream to different item
so that I don't need to upload same file again and again and multiple items
will be able to use/view/ download same file whenever needed.
Any help will be highly appreciated.
T
-- Forwarded message -
From: Sidney Campos
Date: Friday, December 15, 2023 at 7:39:19 PM UTC+3
Subject: Re: Help Needed: DSpace 7.6.1 HTTPS Access Issue with Nginx
Reverse Proxy - Windows 10
To: DSpace Technical Support
Thank you very much!
Your responses were instrumental i
Hi All,
Where does subject filter retrieve values from and the language used when
you hover mouse cursor where can it be changed to default English or any
language available to choose from. please see screenshot below, notice
Medicin highlighted is not in English where can that be changed to En
Forwarding this message to other DSpace lists on behalf of Laurie. If you have
questions about the role, please get in touch with Laurie.
Tim
From: dspace-commun...@googlegroups.com on
behalf of Laurie Arp
Sent: Tuesday, January 16, 2024 10:30 AM
To: DSpace C
Hi Andrew,
At this point in time, I believe filter-media is expected to be a scheduled
task (usually run via a cron job or similar). It would be possible to run
it item by item via a Curation Task or similar, but that doesn't exist in
DSpace out-of-the-box.
Tim
On Wednesday, December 20, 202
Hi Hajar,
If you are still having these issues, I'd recommend first figuring out why
your backend is not accessible at the URL you defined. Perhaps check the
DSpace or Tomcat logs for errors.
Whenever the backend is inaccessible, the frontend may throw errors. So,
it's possible the fronten
Hi KS,
This should be possible in DSpace 7, and it's unclear to me from the steps
you described what isn't working. Simply put though the Collection
permissions are only inherited at the *time the Item is submitted*. So,
this process only works for Items created/added *after* the Collection
Hi Albert,
It's difficult to help without more information.
It could be that the collection deposit is throwing an error. If so, you
should follow the troubleshooting guide to locate the exact
error:
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x
All,
For future reference, we also have a page in our REST Contract describing
the steps to performing a submission via the REST
API: https://github.com/DSpace/RestContract/blob/main/submission.md
Tim
On Saturday, January 13, 2024 at 10:40:00 PM UTC-6 aro...@gmail.com wrote:
> Guys, I finally
Hi Kyky,
That's definitely an odd error. Maybe you had previously built an older
version of DSpace and it's encountering some older versions of dependencies?
If so, you can run "yarn clean", then "yarn install" and "yarn build:prod"
again.
If that still doesn't work, you might try reinstalli
Hi,
Please use our Troubleshooting guide to locate the underlying error message
behind the 422 error. It may be in the "dspace.log" file on the
backend.
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)
Generally speaking a 422 tends to mean
Hi Lewatle
Those logs don't appear to show a request to "DELETE
/server/api/core/communities/[uuid]". That's the request that should be
sent by the User Interface whenever you click the Delete button on a
Community. See the REST Contract for Community deletion... these are the
docs that desc
Hi,
Currently, this is not possible to do via the User Interface or REST API.
So, it would require custom code on both the backend and frontend to
support linking a Bitstream to multiple Items. This is not an easy task
unfortunately. You'd likely need to add a new REST endpoint to link
bit
Here is the logs as found in tomcat logs:
0:0:0:0:0:0:0:1 - - [17/Jan/2024:00:26:54 +0545] "OPTIONS
/server/api/authn/login HTTP/1.1" 200 5
0:0:0:0:0:0:0:1 - - [17/Jan/2024:00:26:54 +0545] "POST
/server/api/authn/login HTTP/1.1" 200 5
0:0:0:0:0:0:0:1 - - [17/Jan/2024:00:26:54 +0545] "OPTIONS
Hi,
That error appears to be referencing a "metric-badges.compontent.ts" and a
"metric-donuts.component.ts". Neither of those are standard in DSpace.
So, my best guess is either you are running DSpace-CRIS or have a custom
component causing issues.
Regardless, those seem to be the cause of y
Thanks, Tim.
I think there was just one REST call missing that I didn't find in your
tutorial, which finalizes the submission of an item: *PATCH
server/api/submission/ workspaceitems/{itemId}*
After this step, we will send the item to the workflow, through the POST
call /server/api/workflow/workf
17 matches
Mail list logo