Thanks. Overcame the issue.
Now on yarn run build:prod, I get
dspace-angular/src/environments/environment.production.ts:13:3 - error
TS2741: Property 'useProxies' is missing in type '{ ssl: false; host:
string; port: number; nameSpace: string; }'
ts file attached.
On Tuesday, January 3, 2023 at
Any help would be appreciated.
On Tuesday, December 27, 2022 at 5:54:47 PM UTC+5:30 Projects Arunendra
wrote:
> I faced 2 errors:
> While executing yarn install, I got
> error @typescript-eslint/experimen...@5.11.0: The engine "node" is
> incompatible with this mo
I faced 2 errors:
While executing yarn install, I got
error @typescript-eslint/experimental-utils@5.11.0: The engine "node" is
incompatible with this module. Expected version "^12.22.0 || ^14.17.0 ||
>=16.0.0". Got "14.15.1"
I ignored the above error and continued:
yarn run build:prod
yarn run
I have installed DSpace 6.3 on 2 different machines. Using the xmlui Mirage
interface.
But in one installation, there is no Advanced Search link on right hand
corner while in the other installation, it is appearing.
How is it possible?
[image: NoAdvSearch.PNG][image: Advsearch.PNG]
--
All
Say there are 3 items with titles Abc, Mnp and Xyz.
If browse by Titles and give Abc in the search box, the result appears as
Abc followed by the other 2 in alphabetical order.
Then, if I search Xyz, I get only Xyz as the result.
But, after this if I give Mnp, there is no result. The previous
Hi,
I believe there are related responses scattered through out this forum but
I need a summarized idea:
1)What configurations are required when there are large number of items
(i.e optimized search)?
2) What configurations are required when there are large number of
concurrent users?
Will
Is it possible to enter individual metadata for individual bitstream where
multiple such bitstreams belong to a single item?
Using Dspace 5.10
--
All messages to this mailing list should adhere to the Code of Conduct:
https://duraspace.org/about/policies/code-of-conduct/
---
You received this
While batch uploading if somebody unintentionally *import*s metadata of one
type of collection into another collection, having separate metadata, can
Dspace prevent that?
Similarly, while *export*ing, how do I export collection with its own
metadata only and not other metadata fields that are
