I found a solution in the angular file
file-download-link.components.ts. I can test for the metadata value
of the item there.
-Jose
On Tue, Mar 14, 2023 at 1:27 PM Jose Blanco wrote:
>
> I'd like to change the request copy code in 7.4 to only present the
> Request Copy page for a file if the
Not an authoritative answer but my initial thoughts are:
* You should probably change the prefix back so that any new items are
created correctly
* If items created prior to the upgrade have been displaying broken links,
then changing the prefix would probably fix them
* For items
I'm seeing this in the angular debugger:
dspace-rest-response-parsing.service.ts:200 cannot deserialize type itemrequest
On Tue, Mar 14, 2023 at 1:27 PM Jose Blanco wrote:
>
> I'd like to change the request copy code in 7.4 to only present the
> Request Copy page for a file if the item contains
I'd like to change the request copy code in 7.4 to only present the
Request Copy page for a file if the item contains these two metadata
items:
email.requestcopy
name.requestcopy
So not just for all bitstreams with restricted permissions, but for
the items with these metadata.
Has anyone done
Dear All,
Thanks to this support group, I have (almost) successfully migrated the 6.3
deployment to 7.5. Regarding the basic functionality, the only missing
element is the workflow. Upon executing
bin/dspace database migrate ignored
I have:
| Versioned | 5.0.2014.11.04 | Enable XMLWorkflow
Hi Mo,
I will test these changes and let you know what happens.
Em ter., 14 de mar. de 2023 às 06:34, Mohammad S. AlMutairi <
alo...@gmail.com> escreveu:
> Hi Douglas,
>
> In addition to the previous message, I noticed you are using a Squid Proxy
> in your network. You might need to bypass the
Dear DSpace Colleagues,
On DSpace 7.4 when searching items by titles I am able to find few from
Google Scholar https://scholar.google.com, others are not searchable, is
there anyway to make Google Scholar to index our site for items to be
visible, please see this links that I have followed:
Hi Douglas,
In addition to the previous message, I noticed you are using a Squid Proxy
in your network. You might need to bypass the proxy for the http/https
traffic going from the frontend destined to the backend.
ENV http_proxy http://proxy.uefs.br:3128
ENV https_proxy
