Re: [dspace-tech] Re: DSpace 7.4 Windows 10

[Mohammad S. AlMutairi]

On Friday, January 13, 2023 at 10:22:00 PM UTC+3 project@gmail.com 
wrote:
But according to the site,  yarn build:prod has to be executed prior to 
that, isn't it??
Don't get it confused. ( yarn build:prod - Will build the frontend but 
won't start it ) or ( yarn start:prod - Will build the frontend and will 
start it ) comes after configuring [dspace-angular]/config/config.prod.yml 
or setting the building environment.
 


On Thu, Jan 12, 2023 at 6:53 PM Mohammad S. AlMutairi  
wrote:
You need to follow the frontend installation procedure you see here 
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-FrontendInstallation
 
Specially step 5. Configuration.


   1. Start a command prompt
   2. copy [dspace-angular]/config/config.example.yml  
   [dspace-angular]/config/config.prod.yml
   3. edit  [dspace-angular]/config/config.prod.yml and modify to fit your 
   environment
   4. Test & Build the Frontend by following steps in the link above.


Hope it help & Good luck


On Thursday, January 12, 2023 at 1:52:07 PM UTC+3 project@gmail.com 
wrote:
Uploaded the config.prod.yml file here.
Same error occurs.


*From,*
*Arunendra MB.*



On Wed, Jan 4, 2023 at 6:25 PM Mohammad S. AlMutairi  
wrote:
You welcome & Hello,

You need to upload  [dspace-angular]/config/config.prod.yml here in the 
group.. I think the configuration in that file is not right.

On Wednesday, January 4, 2023 at 3:01:48 PM UTC+3 project@gmail.com 
wrote:
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 1:58:52 PM UTC+5:30 alo...@gmail.com wrote:
On Tuesday, December 27, 2022 at 3:24:47 PM UTC+3 project@gmail.com 
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 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 v1.22.19
$ yarn run build:ssr
$ ng build --configuration production && ng run 
dspace-angular:server:production
error Command failed with exit code 1

Are the two related?
What is the way out?
How did you install yarn?.

Start over and try this:

Nodejs Installation
1) Download https://nodejs.org/dist/v16.14.0/node-v16.14.0-x64.msi & 
install it.
2) node -v & npm-v
3) npm install -g yarn
4) npm install -g pm2
5) yarn -v & pm2 -v 

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/405822d8-d9a0-421a-ba16-31618a430667n%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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/2c0f0fd3-a515-4626-ad12-ac6d1d5fa692n%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/5dbc9ab4-ab7f-4b83-ad93-5e4dca825386n%40googlegroups.com.

[dspace-tech] Re: Mirador Viewer

['Tim Donohue' via DSpace Technical Support]

Hi Ahmed,

That error makes it sound like your IIIF Image Server (e.g. Cantaloupe) is 
either not running or is throwing an exception of some sort.  It sounds 
like it's not including valid JSON, which is causing the viewer to error 
out.

I'd recommend verifying that your image server is running and is responding 
as described in the IIIF documentation 
at https://wiki.lyrasis.org/display/DSDOC7x/IIIF+Configuration

Tim

On Thursday, December 22, 2022 at 6:22:49 AM UTC-6 ahmad.n...@gmail.com 
wrote:

>   I intall ubuntu server 20.04 and dspace 7.3 every thng working ok and i 
> intall  IIIF Configuration 
>  for viewing 
> photo and  Enable IIIF Support on Backend but when i go front to view photo 
> using  Mirador Viewer on Frontend it give me this error message
>
> SyntaxError: Unexpected non-whitespace character after JSON at position 4
>
> how can solve this problem error , i attach error message
>
> Ahmed Nasser
> GU senior system administrator
>
>

-- 
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/8a971d49-2ddc-410c-b6df-7ccf20fc8a01n%40googlegroups.com.

Re: [dspace-tech] Re: DSpace 7.4 Windows 10

[ArunendraMB]

But according to the site,  yarn build:prod has to be executed prior to
that, isn't it??
This leads to " Property 'useProxies' is missing in type '{ ssl: false;
host: string; port: number; nameSpace: string; }'" error.
Anyway, I am going to check the steps again.



*From,*
*Arunendra MB.*



On Thu, Jan 12, 2023 at 6:53 PM Mohammad S. AlMutairi 
wrote:

> You need to follow the frontend installation procedure you see here
> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-FrontendInstallation
> Specially step 5. Configuration.
>
>
>1. Start a command prompt
>2. copy [dspace-angular]/config/config.example.yml
>[dspace-angular]/config/config.prod.yml
>3. edit  [dspace-angular]/config/config.prod.yml and modify to fit
>your environment
>4. Test & Build the Frontend by following steps in the link above.
>
>
> Hope it help & Good luck
>
>
> On Thursday, January 12, 2023 at 1:52:07 PM UTC+3 project@gmail.com
> wrote:
>
>> Uploaded the config.prod.yml file here.
>> Same error occurs.
>>
>>
>> *From,*
>> *Arunendra MB.*
>>
>>
>>
>> On Wed, Jan 4, 2023 at 6:25 PM Mohammad S. AlMutairi 
>> wrote:
>>
>>> You welcome & Hello,
>>>
>>> You need to upload  [dspace-angular]/config/config.prod.yml here in the
>>> group.. I think the configuration in that file is not right.
>>>
>>> On Wednesday, January 4, 2023 at 3:01:48 PM UTC+3 project@gmail.com
>>> wrote:
>>>
 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 1:58:52 PM UTC+5:30 alo...@gmail.com
 wrote:

> On Tuesday, December 27, 2022 at 3:24:47 PM UTC+3
> project@gmail.com 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 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 v1.22.19
>> $ yarn run build:ssr
>> $ ng build --configuration production && ng run
>> dspace-angular:server:production
>> error Command failed with exit code 1
>>
>> Are the two related?
>> What is the way out?
>>
> How did you install yarn?.
>
> Start over and try this:
>
> Nodejs Installation
> 1) Download https://nodejs.org/dist/v16.14.0/node-v16.14.0-x64.msi &
> install it.
> 2) node -v & npm-v
> 3) npm install -g yarn
> 4) npm install -g pm2
> 5) yarn -v & pm2 -v
>
 --
>>> 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...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/dspace-tech/405822d8-d9a0-421a-ba16-31618a430667n%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/2c0f0fd3-a515-4626-ad12-ac6d1d5fa692n%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/CAO_tGrLdv2MzU0xuOUmkuuqCYa8%3D3f2J5SUabA7_WBurmG-e_Q%40mail.gmail.com.

[dspace-tech] Re: DSpace 7.5 and angular 14

['Tim Donohue' via DSpace Technical Support]

Hi,

No, DSpace 7.5 will still use Angular 13.  The upgrade to Angular 14 (or 
possibly even Angular 15) will be in 7.6.

Here's a ticket for the Angular 14 
upgrade: https://github.com/DSpace/dspace-angular/issues/2043  If you are 
interested in chipping in on this in any way, feel free to let us know on 
that ticket.

Tim
On Tuesday, January 3, 2023 at 10:43:26 AM UTC-6 karols...@gmail.com wrote:

> Hi,
>
> will dspace 7.5 be compatible with angular 14.x ? Greetings,
>
> Karol
>

-- 
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/faed5eab-6bf5-4673-81f6-7b7e9b7cfc2dn%40googlegroups.com.

[dspace-tech] RE: DSpace 7.4 Backend Whitelabel errors

[Cameron, Jacob]

The CATALINA\localhost\ROOT.xml isn't loading properly.  If I copy the server 
folder into the Tomcat\webapps folder and rename it Root, it's all good.

It seems odd that the HAL browser was loading but nothing worked but it all 
works fine.  Something to ponder on Monday I guess.

Thanks Tim!

Jake

--
Jake Cameron, BCS(UNB)
Systems Support Specialist III
Information Systems and Technical Services University of Lethbridge Library
Phone:(403)329-2756
This e-mail, including any and all attachments, is only for the use of the 
intended recipient(s) and may contain information that is confidential or 
privileged. If you are not the intended recipient, you are advised that any 
dissemination, copying or other use of this e-mail is prohibited. Please notify 
the sender of the error in communication by return e-mail and destroy all 
copies of this e-mail. Thank you.

From: Tim Donohue 
Sent: January 13, 2023 11:14 AM
To: Cameron, Jacob ; DSpace Technical Support 

Subject: Re: DSpace 7.4 Backend Whitelabel errors

Caution: This email was sent from someone outside of the University of 
Lethbridge. Do not click on links or open attachments unless you know they are 
safe. Suspicious emails should be forwarded to 
phish...@uleth.ca.

Hi Jacob,

I'd recommend checking the Tomcat logs as well.  If it's a 404, that implies 
that "http://localhost:8080/server; is an invalid URL in Tomcat.  Maybe 
something went wrong in deploying the "server" webapp to Tomcat, which would 
explain why it's not loading.

Here's our Troubleshooting guide in case you hit other setup issues along the 
way: 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

If you need more help let us know on this list.

Tim

From: dspace-tech@googlegroups.com 
mailto:dspace-tech@googlegroups.com>> on behalf 
of Cameron, Jacob mailto:jacob.came...@uleth.ca>>
Sent: Thursday, January 12, 2023 2:53 PM
To: DSpace Technical Support 
mailto:dspace-tech@googlegroups.com>>
Subject: [dspace-tech] DSpace 7.4 Backend Whitelabel errors

Hi Everyone,

My log files are only showing 404, no errors or anything, but whenever I go to 
http://localhost:8080/server the following shows up:

Whitelabel Error Page

This application has no explicit mapping for /error, so you are seeing this as 
a fallback.
Thu Jan 12 13:48:13 MST 2023
There was an unexpected error (type=Not Found, status=404).
No message available

However, I am getting no errors in any of my log files, the local_access_log 
for tomchat shows:

127.0.0.1 - - [12/Jan/2023:13:48:13 -0700] "GET /server/ HTTP/1.1" 404 306

Dspace.log shows:

2023-01-12 13:48:12,988 INFO  unknown 2a6f3b2c-06b7-4aa3-b96d-97c8d6a20435 
org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request [GET 
/server/] originated from unknown

Any requests to any of the APIs show the same Whitelabel errors.  Any thoughts?

Jake

--
Jake Cameron, BCS(UNB)
Systems Support Specialist III
Information Systems and Technical Services University of Lethbridge Library
Phone:(403)329-2756
This e-mail, including any and all attachments, is only for the use of the 
intended recipient(s) and may contain information that is confidential or 
privileged. If you are not the intended recipient, you are advised that any 
dissemination, copying or other use of this e-mail is prohibited. Please notify 
the sender of the error in communication by return e-mail and destroy all 
copies of this e-mail. Thank you.

--
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/YQBPR0101MB50317945B6CBA0337684685C84FD9%40YQBPR0101MB5031.CANPRD01.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/YQBPR0101MB503117B9397ACC26DE0863DC84C29%40YQBPR0101MB5031.CANPRD01.PROD.OUTLOOK.COM.

[dspace-tech] Re: Dspace 7 separate backend and frontend servers

['Tim Donohue' via DSpace Technical Support]

There are really no special requirements to run the frontend & backend on 
separate servers.  Just follow the Installation guide as normal.  But, you 
*will* need to ensure the frontend and backend are both running HTTPS 
(otherwise, I believe authentication-related cookies will be blocked by 
your browser).

https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace

If you have more specific questions or hit errors, let us know on this list.

Tim

On Tuesday, January 3, 2023 at 8:23:08 AM UTC-6 cpgr...@gmail.com wrote:

> When the back end and front end servers are on different servers, what 
> configuration is necessary to let the front end talk to the back end? Is 
> this documented somewhere?
>

-- 
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/96242b72-5ce3-44d3-bb49-d96083752cd8n%40googlegroups.com.

[dspace-tech] Re: unable to enable full text snippets or searching for DSpace 7.4

['Tim Donohue' via DSpace Technical Support]

Hi Paige,

Just a quick answer... I don't believe fulltext snippets are working yet in 
DSpace 7 (at least I don't think code exists to support this in the UI & I 
don't recall seeing this working yet).   DSpace 7 *does* support hit 
highlighting in metadata fields though (e.g. title, author, abstract, etc) 
in the search results.  (That said there was a bug in the title hit 
highlighting of 7.4 that we recently fixed & will be in 
7.5: https://github.com/DSpace/dspace-angular/pull/1973)

Tim

On Tuesday, January 3, 2023 at 3:36:38 PM UTC-6 pai...@udel.edu wrote:

> I figured I'd try re-boosting this in the new year, after not hearing from 
> anyone in early December. We've tried a number of things, but we're still 
> having no success turning on full text snippets for searches in DSpace -- 
> and indeed, it doesn't seem like full text searching is enabled at all, and 
> that's a significant concern.
>
> We've made sure that our Text Extractor Media Filter is turned on (per this 
> documentation 
> ),
>  
> and we've changed the settings in our discovery.xml file, including the 
> following code snippet from the documentation wiki on customizing hit 
> highlighting) 
> .
>  
> We're not concerned about snippets showing up from restricted or embargoed 
> items; that's fine. We've made sure to restart Tomcat.
>
> -
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
> Nothing seems to be working. If any of you have successfully enabled full 
> text snippets in 7.4, or you've been able to troubleshoot  full text 
> searching, can you recommend what settings we might want to check?
>
> Any recommendations much appreciated -- thanks!
>
> Paige
>
> -
> *Meeting/regular work hours: Monday - Thursday, 9am-5pm; limited email on 
> Friday mornings.*
>
> Dr. Paige C. Morgan
> (she/her/they)
> Digital Publishing and Copyright Librarian, 
> Head of Digital Initiatives & Preservation
> University of Delaware Library, Museums and Press (on Lenape land 
> )
> Morris 118 
> ORCID: https://orcid.org/-0001-8076-7356
> pai...@udel.edu
> 302.831.7153 <(302)%20831-7153>
>
> Make an appointment to meet with me: https://calendly.com/paigecm/ (Meetings 
> available via Zoom, phone, etc.)
> *** I observe email-free evenings and weekends. ***
>
>
> On Fri, Dec 9, 2022 at 12:42 PM Paige Morgan  wrote:
>
>> Has anyone running DSpace 7.x been successful in turning on full text 
>> snippets in search results?
>>
>> We've made sure that our Text Extractor Media Filter is turned on (per this 
>> documentation 
>> ),
>>  
>> and we've changed the settings in our discovery.xml file, including the 
>> following code snippet from the documentation wiki on customizing hit 
>> highlighting) 
>> .
>>  
>> We're not concerned about snippets showing up from restricted or embargoed 
>> items; that's fine. We've made sure to restart Tomcat.
>>
>> ->> class="org.dspace.discovery.configuration.DiscoveryHitHighlightFieldConfiguration">
>>>
>>> 
>>>
>>> 
>>>
>>> 
>>>
>>> 
>>>
>>> 
>>>
>> Nothing seems to be working. If any of you have successfully enabled full 
>> text snippets in 7.4, can you recommend what settings we might want to 
>> check?
>>
>> Thanks so much (and happy Friday!)
>>
>> Paige
>>
>> -
>> *Meeting/regular work hours: Monday - Thursday, 9am-5pm; limited email on 
>> Friday mornings.*
>>
>> Dr. Paige C. Morgan
>> (she/her/they)
>> Digital Publishing and Copyright Librarian, 
>> Head of Digital Initiatives & Preservation
>> University of Delaware Library, Museums and Press (on Lenape land 
>> )
>> Morris 118 
>> ORCID: https://orcid.org/-0001-8076-7356
>> pai...@udel.edu
>> 302.831.7153 <(302)%20831-7153>
>>
>> Make an appointment to meet with me: https://calendly.com/paigecm/ (Meetings 
>> available via Zoom, phone, etc.)
>> *** I observe email-free evenings and weekends. ***
>>
>

-- 
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/e16f7582-74a5-4adb-a929-7348a3fa30bdn%40googlegroups.com.

[dspace-tech] Re: openAire implementation in dspace 7.4

['Tim Donohue' via DSpace Technical Support]

Hi,

First off, I'll admit, I'm not an OpenAIRE v4 expert. But, I think the info 
you might be missing is that DSpace does *not* store metadata in the exact 
same fields documented by OpenAIRE.  One example is that, in DSpace, the 
title is stored in "dc.title", even if those OpenAIRE docs say that it 
expects a Title to be in "datacite:title".

However, when DSpace shares its data to OpenAIRE (via OAI-PMH), DSpace will 
translate those internal fields into the fields that OpenAIRE *expects* 
(when you use the OAI-PMH "OpenAIRE4" context).  So, in OAI-PMH, the Title 
field is translated from "dc.title" (the internal field) into 
"datacite:title".  You can see an example of this by looking at the 
"OpenAIRE4" context for the OAI-PMH server on our demo site 
at 
https://api7.dspace.org/server/oai/openaire4?verb=ListRecords=oai_openaire

So, the behavior you are seeing in your DSpace is correct.  DSpace will 
store metadata in it's own fields at times.  However, those fields will be 
translated into OpenAIREv4 fields in the OAI-PMH context.

Hopefully that helps, but let us know on this list if you have more 
questions.

Tim

On Thursday, January 5, 2023 at 10:16:25 AM UTC-6 jorge@udb.edu.sv 
wrote:

> hello ?
>
> El martes, 3 de enero de 2023 a las 8:57:59 UTC-6, Jorge Alberto Bonilla 
> Castaneda escribió:
>
>> Hello, I had some doubts about what I have to do so that my repository 
>> complies with the guidelines defined in OpenAIRE
>>
>> Following the documentation I wrote on my server:
>>
>> [/dspace]/bin/dspace initialize-entities -f 
>> [/dspace]/config/entities/openaire4-relationships.xml
>> [/dspace]/bin/dspace registry-loader-metadata 
>> [/dspace]/config/registries/openaire4-types.xml
>>
>> and it did not return any error, it seemed that it had worked and that I 
>> already had the metadata to adapt my submission-forms.xml , but when I saw 
>> the list of metadata I noticed that I was missing some,
>>
>> for example in the list defined in 
>>
>> https://openaire-guidelines-for-literature-repository-managers.readthedocs.io/en/latest/application_profile.html
>>
>>  there are many that use datacite , but looking at my list I only have 
>> these:
>> [image: Captura de pantalla 2023-01-03 085609.png]
>>
>>
>> Only those 2, is there any step that I am missing? or have I 
>> misunderstood how OpenAire is implemented? Thank you very much for your 
>> help 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/c094a25a-f204-4cd9-ad14-645b5ca28227n%40googlegroups.com.

[dspace-tech] Re: DSpace 7.4 - no suggestions when adding a new metadata field to an existing item

['Tim Donohue' via DSpace Technical Support]

Hi,

I'd recommend debugging this using our Troubleshooting guide.  While it's 
useful to look at the backend logs, it's also *necessary* to look at the 
UI's behavior in your browser's dev tools. Sometimes an error will only 
appear in your browser and not make it to the backend logs (this can happen 
when the UI is having communication issues with the backend or if the error 
is in the UI itself).  So, check for other possible errors at the UI level 
by following the troubleshooting guide:
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

If you find additional errors, let us know on this list.  You could also 
try a full reindex of Solr (./dspace index-discovery -b) to see if that 
fixes things.

Tim

On Wednesday, January 11, 2023 at 7:27:34 AM UTC-6 oriol@udl.cat wrote:

> Hi all,
>
> in DSpace 7.4, while adding new metadata to an existing item I'm not 
> getting any suggestions in the input box, is there any configuration step 
> I'm missing?
> [image: image.png]
>
> I see in *dspace.log* that there is this API call when I type something 
> in the input box: 
> GET /server/api/core/metadatafields/search/byFieldName  
> so I tried this with no results: 
> api/core/metadatafields/search/byFieldName?query=author . 
> The same API call in the DSpace 7 demo site returns 3 results: 
> https://api7.dspace.org/server/#api/core/metadatafields/search/byFieldName?query=author
>
> Also, in *solr.log* I see this call: 
> 2023-01-11 13:09:55.709 INFO (qtp359742806-22) [ x:search] 
> o.a.s.c.S.Request [search] webapp=/solr path=/select 
> params={q=*:*=search.resourcetype,search.resourceid,search.uniqueid,database_status=0=
> *fieldName_keyword:author**==javabin=2} *hits=0* status=0 
> QTime=1
>
> Maybe there is a problem with SOLR?
>
> Thank you very much,
> Oriol
>
>
>
>

-- 
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/78bf6c68-e0d8-4d24-8618-57f9f00ec847n%40googlegroups.com.

Re: [dspace-tech] ingesting HTML archives

['Tim Donohue' via DSpace Technical Support]

Hi John,

It appears that this is not yet supported in DSpace 7.  I'm not seeing a way to 
get this to work either, because the DSpace 7 Bitstream URLs have changed from 
the structure in DSpace 6.

I've created a bug ticket for this: 
https://github.com/DSpace/DSpace/issues/8635  I'm not sure offhand how to 
resolve this, as I think it needs more detailed analysis & prioritization.

Tim

From: dspace-tech@googlegroups.com  on behalf of 
John Rodriquez (praaks) 
Sent: Wednesday, January 11, 2023 7:10 AM
To: DSpace Technical Support 
Subject: [dspace-tech] ingesting HTML archives

Hi,

The documentation on how to handle HTML archives which contain relative links 
hasn't been updated for DSpace 7 
(https://wiki.lyrasis.org/display/DSDOC7x/Ingesting+HTML+Archives). In DSpace 7 
(I'm running 7.4), I realize bitstreams now have UUIDs instead of sequence ids 
in their URLs. This seems to break the relative links in the HTML file. Links 
that worked in DSpace 6 no longer work in DSpace 7. The relative link is 
converted to a link containing the main HTML files's UUID. For example:

The main HTML file link in the item record:
http://dspace..ee:8080/server/api/core/bitstreams/412b6597-1b7a-4edf-8ca1-1effd3185276/content

The relative link in the main HTML file for a "goto.html" becomes:
http://dspace..ee:8080/server/api/core/bitstreams/412b6597-1b7a-4edf-8ca1-1effd3185276/goto.html
   ... resulting in a 404 error ...

... though of course, this second file has its own UUID, and its direct address 
is:
http://testdspace.tktk.ee:8080/server/api/core/bitstreams/fe3299dc-327e-429f-9ec8-8652e84af8f3/content

Is there a way to get around this so relative links aren't broken? Maybe I've 
misunderstood something? Maybe it's a configuration issue?

Regards,

John Rodriquez
Educational Technologist
Tallinna Tehnikakõrgkool, UAS





--
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/b7d9836d-005d-4df7-91d7-ba8ee8907019n%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/SN4PR22MB3270CEC404B5832FBAEA279CEDC29%40SN4PR22MB3270.namprd22.prod.outlook.com.

Re: [dspace-tech] Dynamic control of submission-process steps?

['Tim Donohue' via DSpace Technical Support]

Hi David,

As of DSpace 7.3 (or later) this is possible.  DSpace 7 has the same 
"type-based fields" () functionality that was available in DSpace 6. 
 See the documentation at 
https://wiki.lyrasis.org/display/DSDOC7x/Submission+User+Interface#SubmissionUserInterface-ItemtypeBasedMetadataCollection

Tim

From: dspace-tech@googlegroups.com  on behalf of 
David P. Steelman 
Sent: Wednesday, January 11, 2023 12:59 PM
To: dspace-tech@googlegroups.com 
Subject: [dspace-tech] Dynamic control of submission-process steps?

All,

Just wondering if there was any DSpace 7 functionality to support 
adding/removing submission-process steps dynamically, based on user input. 
Specifically we want the Creative Commons step ("cclicense") to display only if 
the user sets the "Type" field to "Dataset".

I know it is possible to control the submission-process steps at the collection 
level (using ""), but what we would like to do is add/remove 
steps based on the value of the "Type" field, similar to how the "" 
property can be used to control the display of fields in a form.

Thanks,

David

--
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/CA%2BmHiJZJO7Reg1Uuw85WLTBNjqAnFHumRUfOQXtfEaRzwFRZAQ%40mail.gmail.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/SN4PR22MB32700375B895B780B25D04E2EDC29%40SN4PR22MB3270.namprd22.prod.outlook.com.

[dspace-tech] Re: DSpace 7.4 Backend Whitelabel errors

['Tim Donohue' via DSpace Technical Support]

Hi Jacob,

I'd recommend checking the Tomcat logs as well.  If it's a 404, that implies 
that "http://localhost:8080/server; is an invalid URL in Tomcat.  Maybe 
something went wrong in deploying the "server" webapp to Tomcat, which would 
explain why it's not loading.

Here's our Troubleshooting guide in case you hit other setup issues along the 
way: 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

If you need more help let us know on this list.

Tim

From: dspace-tech@googlegroups.com  on behalf of 
Cameron, Jacob 
Sent: Thursday, January 12, 2023 2:53 PM
To: DSpace Technical Support 
Subject: [dspace-tech] DSpace 7.4 Backend Whitelabel errors

Hi Everyone,

My log files are only showing 404, no errors or anything, but whenever I go to 
http://localhost:8080/server the following shows up:

Whitelabel Error Page

This application has no explicit mapping for /error, so you are seeing this as 
a fallback.
Thu Jan 12 13:48:13 MST 2023
There was an unexpected error (type=Not Found, status=404).
No message available

However, I am getting no errors in any of my log files, the local_access_log 
for tomchat shows:

127.0.0.1 - - [12/Jan/2023:13:48:13 -0700] "GET /server/ HTTP/1.1" 404 306

Dspace.log shows:

2023-01-12 13:48:12,988 INFO  unknown 2a6f3b2c-06b7-4aa3-b96d-97c8d6a20435 
org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request [GET 
/server/] originated from unknown

Any requests to any of the APIs show the same Whitelabel errors.  Any thoughts?

Jake

--
Jake Cameron, BCS(UNB)
Systems Support Specialist III
Information Systems and Technical Services University of Lethbridge Library
Phone:(403)329-2756
This e-mail, including any and all attachments, is only for the use of the 
intended recipient(s) and may contain information that is confidential or 
privileged. If you are not the intended recipient, you are advised that any 
dissemination, copying or other use of this e-mail is prohibited. Please notify 
the sender of the error in communication by return e-mail and destroy all 
copies of this e-mail. Thank you.

--
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/YQBPR0101MB50317945B6CBA0337684685C84FD9%40YQBPR0101MB5031.CANPRD01.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/SN4PR22MB3270038770D3C2711B63E1E5EDC29%40SN4PR22MB3270.namprd22.prod.outlook.com.