[dspace-tech] How to debug frontend

[geethanjali alaguraj]

Hello,

How to debug the front end can anyone tell the procedures . I have tried 
angular devtools to debug the frontend code but it shows like this:

We detected an application built with production configuration. Angular 
DevTools only supports development builds. 
How to resolve this or is there any other method to debug?.

-- 
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/855629b1-4b1c-4c39-ab7c-0e866cf838d8n%40googlegroups.com.

Re: [dspace-tech] Re: Solr statistics shards in DSpace 7.6?

[Keith Gilbertson]

On Mon, Nov 6, 2023 at 2:38 PM DSpace Technical Support <
dspace-tech@googlegroups.com> wrote:

> While awaiting an answer to your question, may I propose a tangential
> question of my own:  what do you think sharding is doing for you, and have
> you seen evidence to support this?
>
>
>
>
Mark, I don't know if it's doing anything for us now.

I can't remember, but honestly, I don't think that we took any measurements
of "before sharding" or "after sharding" performance except possibly
anecdotal "seems better now, the system is slow less often" notes. If I
recall correctly (and this is fuzzy), part of our motivation in finally
doing the sharding was to help with logistics in resolving another issue
that we were having. When DSpace added the uuid fields to supplement or
replace the id fields, some of our statistics reports (perhaps customs one
we had here)  were inaccurate or broken. Terry Brady supplied a very nice
tool to update old statistics records with IDs to use the new uuid instead,
but we had difficulties using this tool on our very large statistics core,
with an operating production system, with the particular storage hardware
that we were using at the time. With our setup then, it ran slowly and
slowed the system so that the web interface was unusable. The initial
sharding helped us to use Terry's tool to update the smaller and static
cores for each previous year offline, completely away from the production
system, and reinstall them when we were finished.

Beyond that logistical motivation to help resolve the missing uuid issue, I
suspect that as a group we just read that DSpace supports sharding and that
sharding helps performance problems, noticed that we sometimes have
performance problems, and thought that sharding was a best practice and we
should implement it.

Do we currently get any benefits from the sharding on our system? I don't
know. We have at least one drawback under DSpace 6 with sharding. If our
Tomcat shuts down and restarts too fast (by monit), sometimes it tries to
reopen one of those statistics cores before the lock was released by the
previous instance, ultimately resulting in a problem where DSpace
temporarily can't see statistics in any previous year cores until we
restart Tomcat again.

The systems administrators here strongly support the decision to allow Solr
to be placed on a different host, and that's what they're doing. My
understanding is that separating things this way will help us to get better
at identifying the particular bottlenecks (e.g. is the problem solr, or
something else?), allowing them to allocate appropriate resources to each
component when needed, and ultimately letting us be more scientific about
performance. Also, it should help us comply with organizational security
requirements faster. If there are any emergency security patches for solr,
the admins can handle them within their normally scheduled update times.

-- 
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/CAOgKO9nXVyShB_h6-a5X-DbpVCuH3Z5QAzGXvM7zHMN%3DQPeECA%40mail.gmail.com.

RE: [dspace-tech] Epub rendering in DSpace7.6

[Fitchett, Deborah]

Kia ora,

That feature isn’t available in out-of-the-box DSpace. Possibly a plugin might 
exist (though I haven’t heard of one) or you may be able to develop one 
yourself.

But DSpace by default is a repository to store materials in whatever format – 
it doesn’t focus on displaying the materials. You may see PDFs display in the 
browser but that’s dependent entirely on how each browser is coded/configured, 
it isn’t DSpace functionality.

Deborah

From: dspace-tech@googlegroups.com  On Behalf Of 
suresh patil
Sent: Tuesday, November 7, 2023 1:00 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Epub rendering in DSpace7.6

You don't often get email from 
patilm.sur...@gmail.com. Learn why this is 
important

Caution: This email originated from outside our organisation. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.

Hi Team,

How to render/open EPub files in DSpace? currently it is getting downloaded. i 
want to open it in the browser itself.

Thanks
--
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/a442af04-b34a-45ae-ba7d-92917f99c521n%40googlegroups.com.



"The contents of this e-mail (including any attachments) may be confidential 
and/or subject to copyright. Any unauthorised use, distribution, or copying of 
the contents is expressly prohibited. If you have received this e-mail in 
error, please advise the sender by return e-mail or telephone and then delete 
this e-mail together with all attachments from your system."

-- 
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/ME3PR01MB752410788870084E37503663C5AAA%40ME3PR01MB7524.ausprd01.prod.outlook.com.

[dspace-tech] Re: Solr statistics shards in DSpace 7.6?

[DSpace Technical Support]

While awaiting an answer to your question, may I propose a tangential 
question of my own:  what do you think sharding is doing for you, and have 
you seen evidence to support this?  Because DSpace uses Solr's sharding 
support in a very eccentric manner, and I have my doubts that it actually 
buys us anything.  That is why I accepted the need to remove it in 7.0, in 
exchange for the option to place Solr on a separate host if desired (since 
supported Solr versions must now be installed separately anyway).  The 
custom sharding code in DSpace doesn't get enough information to work 
across hosts.  If sharding is really needed, Solr can do it much better on 
its own, and we could scrap *all* of the sharding support in DSpace.

On Monday, November 6, 2023 at 12:35:55 PM UTC-5 keith.gi...@gmail.com 
wrote:


Hello DSpace fans,

Is sharding of the statistics cores with a separate core for each 
individual year of statistics supported again in the most recent version of 
DSpace?

The installation documentation mentions that sharding is no longer 
supported in DSpace 7, but we noticed some recent commits to the DSpace 
project that reference sharding and wondered if it is available again.

In past  versions of DSpace during solr index updates or maintenance we've 
sometimes struggled with slow updates or running out of memory. We have 
about 12 years of sharded statistics cores in DSpace 6 and are working on a 
strategy for importing them into DSpace 7, perhaps doing most of the 
exporting and importing on a separate server with solr before our upgrade 
day. I am curious about whether we should import all statistics into the 
same core for DSpace 7, as expected, or if we should keep them separated if 
it turns out that sharding is supported again.

Can someone please help to clarify which parts of sharding are now 
supported, and which still do not work, and provide observations or advice?

Thank you for the time,
Keith
 

-- 
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/f2953515-e38f-4ea3-81c9-751ef4a9afc7n%40googlegroups.com.

[dspace-tech] Solr statistics shards in DSpace 7.6?

[Keith Gilbertson]

Hello DSpace fans,

Is sharding of the statistics cores with a separate core for each
individual year of statistics supported again in the most recent version of
DSpace?

The installation documentation mentions that sharding is no longer
supported in DSpace 7, but we noticed some recent commits to the DSpace
project that reference sharding and wondered if it is available again.

In past  versions of DSpace during solr index updates or maintenance we've
sometimes struggled with slow updates or running out of memory. We have
about 12 years of sharded statistics cores in DSpace 6 and are working on a
strategy for importing them into DSpace 7, perhaps doing most of the
exporting and importing on a separate server with solr before our upgrade
day. I am curious about whether we should import all statistics into the
same core for DSpace 7, as expected, or if we should keep them separated if
it turns out that sharding is supported again.

Can someone please help to clarify which parts of sharding are now
supported, and which still do not work, and provide observations or advice?

Thank you for the time,
Keith

-- 
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/CAOgKO9mxW-J5CEVKvceS4sOBZzBg7TgFqd2Q1AuPuyCweNGmOA%40mail.gmail.com.

[dspace-tech] DSpace 7.6 and CC licenses

[Paige Morgan]

Hi, all--

We're running a sandbox with DSpace 7.6; we've commented out the
jurisdiction in our config, and according to the documentation
,
that should result in 4.0 international licenses.

Unfortunately, what we're getting is 3.0 licenses, with the jurisdiction
permanently set to US. You can see the jurisdiction in the interface, but
you can't change it.

Has anyone else run into this problem? Anyone have suggestions for a
solution?

Thanks,
Paige

-
*Meeting/regular work hours: Monday - Friday, 9am-4:30pm*

Dr. Paige C. Morgan
(she/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
paig...@udel.edu
302.831.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/CA%2BzEVd%3Ddn_hRY5isBMb99Y-om9UvOrZzQ6BZZ0yCdE%3DKLh%2BGEQ%40mail.gmail.com.

Re: [dspace-tech] Dspace 7.6.1 Doi registration error (DataCite)

[Matthias Letsch]

Thank you Manuele!

Unfortunately, the typo only happened to me here in the problem description.

The correct test prefix at DataCite is 10.82770 and also in the dspace.cfg 
is identifier.doi.prefix = 10.82770

So the numbers match. The problem must lie elsewhere.

Kind regards,
Matthias

Manuele Lorusso schrieb am Montag, 6. November 2023 um 15:09:36 UTC+1:

> Hello Matthias,
>
> probably your config "identifier.doi.prefix" was overwritten through the 
> upgrade or a typo has happened
>
> Your registered DataCite DOI Prefix (10.87220) differs from the prefix in 
> the Exception Message (10.82770).
>
> Best,
> Manuele
>
> Herr Manuele Lorusso
> Softwareentwickler / Abt. IT-Dienste Forschung, Lehre, Infrastruktur
> Kommunikations-, Informations-, Medienzentrum (KIM)
> Universität Konstanz
> 78457 Konstanz+49 (0)7531 / 88-5403 <+49%207531%20885403>
> Raum B 707
>
> On 03.11.23 13:53, Matthias Letsch wrote:
>
> Hello together,
>
>  
>
> we have a DataCite membership and doi registration to our fabrica test 
> environment just worked fine with the configurations set like described in 
> https://wiki.lyrasis.org/display/DSDOC7x/DOI+Digital+Object+Identifier. 
> We use the DataCite API directly.
>
>  
>
> some weeks ago we updated up to version 7.6.1-SNAPSHOT (because of the 
> "browse by subject group" bugfix). I also updated all necessary 
> configuration files regarding the doi registration process:
> - config/dspace.cfg (everything in "DOI registration agency credential" as 
> well as "crosswalk.dissemination.DataCite.publisher")
>
> - config/spring/api/identifier-service.xml (see attachment)
>
> - config/item-submission.xml (only for showing pending dois in the 
> submission form)
>
> - config/modules/identifiers.cfg (see attachment)
>
>  
>
> By submission a doi is created in the following syntax: 10.87220/x (x = 
> serial number, e.g. 10.87220/7 etc.)
>
> Now our doi registration has some strange behaviors and I don’t understand 
> where they come from:
>
> 1. The status of the doi doesn't switch automatically from "pending" 
> to "Queued for registration" when a new submission is accepted by admin. 
> (Before the update to 7.6.1, this was the case). 
>
> 2. So I enabled „registering doi from admin“ to manually set the 
> status "Queued for registration" in the status tab of the item via 
> "identifiers.item-status.register-doi = true" in 
> config/modules/identifiers.cfg.
>
> 3. Now, with some items with doi status "queued for registration" 
> (database: 1), I used the typical dspace commands „./dspace doi-organiser 
> -u/-s/-r/-d“, but in command –r (register) an error occured:
>
>  
>
> It wasn't possible to register this identifier: doi:10.82770/7
> Exception: Database table DOI contains a DOI  that is not valid: 
> doi:10.82770/7!
> java.lang.IllegalStateException: Database table DOI contains a DOI  that 
> is not valid: doi:10.82770/7!
> at (...)
>
>  
>
> How is 10.82770/7 not valid? DSpace did register all dois with that syntax 
> just fine before the dspace version update. 
>
>  
>
> 4. So I concluded that the registration didn’t work. Yet here the 
> funny thing is: I looked up our datacite fabrica test environment at 
> https://doi.test.datacite.org/ and there a new item with doi 10.82770/7 
> actually found its way to the registered dois. So DSpace did send the doi 
> to DataCite. BUT in our dspace database at table doi, the doi 10.82770/7 
> STILL has status 1 instead of 3 (1 = queued for registration, 3 = 
> registered) and no doi was written into the metadata (dc.identifier).
>
>  
>
> Does anyone know how this can happen and which configuration file I need 
> to change?
>
> Thank you very much!
>
> Kind regards,
>
> Matthias
>
> -- 
> 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/9bc03cb4-0167-4891-9283-8d1f0a23585cn%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/43f5c2c5-0062-444d-ba66-ae4ab190d127n%40googlegroups.com.

Re: [dspace-tech] Dspace 7.6.1 Doi registration error (DataCite)

[Manuele Lorusso]

Hello Matthias,

probably your config "identifier.doi.prefix" was overwritten through the 
upgrade or a typo has happened


Your registered DataCite DOI Prefix (10.87220) differs from the prefix 
in the Exception Message (10.82770).


Best,
Manuele

Herr Manuele Lorusso
Softwareentwickler / Abt. IT-Dienste Forschung, Lehre, Infrastruktur
Kommunikations-, Informations-, Medienzentrum (KIM)
Universität Konstanz
78457 Konstanz
+49 (0)7531 / 88-5403
Raum B 707

On 03.11.23 13:53, Matthias Letsch wrote:


Hello together,

we have a DataCite membership and doi registration to our fabrica test 
environment just worked fine with the configurations set like 
described in 
https://wiki.lyrasis.org/display/DSDOC7x/DOI+Digital+Object+Identifier. 
We use the DataCite API directly.


some weeks ago we updated up to version 7.6.1-SNAPSHOT (because of the 
"browse by subject group" bugfix). I also updated all necessary 
configuration files regarding the doi registration process:
- config/dspace.cfg (everything in "DOI registration agency 
credential" as well as "crosswalk.dissemination.DataCite.publisher")


- config/spring/api/identifier-service.xml (see attachment)

- config/item-submission.xml (only for showing pending dois in the 
submission form)


- config/modules/identifiers.cfg (see attachment)

By submission a doi is created in the following syntax: 10.87220/x (x 
= serial number, e.g. 10.87220/7 etc.)


Now our doi registration has some strange behaviors and I don’t 
understand where they come from:


1.The status of the doi doesn't switch automatically from "pending" to 
"Queued for registration" when a new submission is accepted by admin. 
(Before the update to 7.6.1, this was the case).


2.So I enabled „registering doi from admin“ to manually set the status 
"Queued for registration" in the status tab of the item via 
"identifiers.item-status.register-doi = true" in 
config/modules/identifiers.cfg.


3.Now, with some items with doi status "queued for registration" 
(database: 1), I used the typical dspace commands „./dspace 
doi-organiser -u/-s/-r/-d“, but in command –r (register) an error occured:


It wasn't possible to register this identifier: doi:10.82770/7
Exception: Database table DOI contains a DOI  that is not valid: 
doi:10.82770/7!
java.lang.IllegalStateException: Database table DOI contains a DOI 
 that is not valid: doi:10.82770/7!

at (...)

How is 10.82770/7 not valid? DSpace did register all dois with that 
syntax just fine before the dspace version update.


4.So I concluded that the registration didn’t work. Yet here the funny 
thing is: I looked up our datacite fabrica test environment at 
https://doi.test.datacite.org/ and there a new item with doi 
10.82770/7 actually found its way to the registered dois. So DSpace 
did send the doi to DataCite. BUT in our dspace database at table doi, 
the doi 10.82770/7 STILL has status 1 instead of 3 (1 = queued for 
registration, 3 = registered) and no doi was written into the metadata 
(dc.identifier).


Does anyone know how this can happen and which configuration file I 
need to change?


Thank you very much!

Kind regards,

Matthias

--
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/9bc03cb4-0167-4891-9283-8d1f0a23585cn%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/059db01a-f320-4ee0-b500-a753134d852c%40uni-konstanz.de.


smime.p7s
Description: S/MIME Cryptographic Signature

[dspace-tech] Epub rendering in DSpace7.6

[suresh patil]

Hi Team,

How to render/open EPub files in DSpace? currently it is getting 
downloaded. i want to open it in the browser itself.

Thanks

-- 
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/a442af04-b34a-45ae-ba7d-92917f99c521n%40googlegroups.com.

[dspace-tech] Re: Move community with its sub-community and collections on DSpace 7.6

[Lewatle Johannes Phaladi]

Hello Tim,

Much appreciated for the respond. I will try community filiator hoping in 
future versions of DSpace we can get the feature to move communities.

Regards,
Lewatle 

On Friday, 3 November 2023 at 18:36:04 UTC+2 DSpace Technical Support wrote:

> Hi Lewatle,
>
> This currently is not possible in the DSpace 7 User Interface.  However, 
> you should be able to use the "Community Filiator" command line tool to 
> change your Community hierarchy in this way.  See the documentation at 
> https://wiki.lyrasis.org/display/DSDOC7x/Managing+Community+Hierarchy
>
> Tim
>
> On Tuesday, October 31, 2023 at 7:22:32 AM UTC-5 joem...@gmail.com wrote:
>
>> Dear DSpace Colleagues,
>>
>> Please help on how to move community with its sub-communities and 
>> collections on DSpace 7.6 to new community on same DSpace frontend. 
>>
>> Regards,
>> Lewatle 
>>
>

-- 
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/c67dfa83-f911-4c4a-b0ee-5eb7c3edf531n%40googlegroups.com.