Re: [dspace-tech] DSpace 7.6.1: Switch to myDSpace page directly after login?

[Sascha Szott]

Hi Matthias,

we have solved this by adapting one line in

src/app/core/auth/auth.effects.ts

You need to change the implementation of the redirectAfterLoginSuccess$ 
method by replacing


  this.authService.navigateToRedirectUrl(action.payload);

with


  this.authService.navigateToRedirectUrl('/mydspace');


Best regards
Sascha


Am 15.03.24 um 15:51 schrieb Matthias Letsch:

Hello there,

By default, you remain on the homepage when you log in. Is there a 
(simple) way to set that after logging in you are taken directly to the 
myDSpace page with the overview of your own releases?


Thank you and 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/9dab0f73-5615-49da-84ac-3ce7fbc21b98n%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/e0a98c42-04fc-444d-9659-f5549691764c%40hsu-hh.de.


smime.p7s
Description: Kryptografische S/MIME-Signatur

[dspace-tech] Re: Upgrade Spring version from 5.3.27 to 5.3.32 due to vulnerability issue

[Salony Permanand]

Hello All,

As per my understanding I updated the spring version from 5.3.27 to 5.3.32 
in pom.xml file

After doing that I rebuild the backend code using mvn clean package and ant 
fresh install command

While rebuilding I was getting error "Dependency convergence error for 
org.springframework:spring-context-support".

I resolved that error and build done successfully.

I want to know that only these steps are needed to upgrade spring in DSpace 
or I am missing some steps 

How should I check that Now Server is using upgraded Spring version

Any suggestion or help is highly appreciated
On Wednesday, March 27, 2024 at 6:40:30 PM UTC+5:30 Salony Permanand wrote:

> Hello All,
>
> I am using DSpace 7.6 version .
>
> I have an vulnerability issue with Spring version in my Dspace
>
> It throws warning as "Applications that use 'UriComponentsBuilder' to 
> parse an externally provided URL (e.g. through a query parameter) AND 
> perform validation checks on
> the host of the parsed URL may be vulnerable to a open redirect attack"
>
> The only solution available is upgrade from 5.3.27 to 5.3.32(which is 
> secure version).
>
> But when I am trying to upgrade it create lots of issues with DSpace 
> version and not supported.
>
> Can anyone help regarding that and suggest what to do 
>
> Any help is highly appreciated
>

-- 
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/dee7c49e-07f5-4a97-bcea-225f61746f6fn%40googlegroups.com.

[dspace-tech] Re: Upgrade Spring version from 5.3.27 to 5.3.32 due to vulnerability issue

[DSpace Technical Support]

Hi,

The Spring vulnerability you are likely mentioning is this 
one: https://spring.io/security/cve-2024-22243

While this is a security issue in Spring, at this time, we do not believe 
it impacts DSpace directly because DSpace doesn't use the 
UriComponentsBuilder in the way that is described by the vulnerability.  
Nonetheless, we have already applied this Spring upgrade to our 
"dspace-7_x" branch in our backend's 
codebase: https://github.com/DSpace/DSpace/tree/dspace-7_xThat way the 
upgrade will be included in the 7.6.2 release.

If you wish to apply these same changes locally, the necessary changes to 
7.x are all found in this PR: https://github.com/DSpace/DSpace/pull/9376

As a sidenote, there was also a later follow-up security issue from Spring 
in https://spring.io/security/cve-2024-22259 which reports that they failed 
to fully fix that issue in Spring 5.3.32.  

The secondary fix was to simply update to Spring 5.3.33, which we did in 
this PR: https://github.com/DSpace/DSpace/pull/9422

Again, neither of these Spring updates seem like they are required for 
DSpace sites at this time.  Both will be include in the DSpace 7.6.2 
release (date is to be announced). That said,  if you feel safer applying 
them early, then you are welcome to do so via the two PRs above (or via the 
`dspace-7_x` maintenance branch).

Tim

On Thursday, March 28, 2024 at 7:26:17 AM UTC-5 salony.p...@gmail.com wrote:

>
> Hello All,
>
> As per my understanding I updated the spring version from 5.3.27 to 5.3.32 
> in pom.xml file
>
> After doing that I rebuild the backend code using mvn clean package and 
> ant fresh install command
>
> While rebuilding I was getting error "Dependency convergence error for 
> org.springframework:spring-context-support".
>
> I resolved that error and build done successfully.
>
> I want to know that only these steps are needed to upgrade spring in 
> DSpace or I am missing some steps 
>
> How should I check that Now Server is using upgraded Spring version
>
> Any suggestion or help is highly appreciated
> On Wednesday, March 27, 2024 at 6:40:30 PM UTC+5:30 Salony Permanand wrote:
>
>> Hello All,
>>
>> I am using DSpace 7.6 version .
>>
>> I have an vulnerability issue with Spring version in my Dspace
>>
>> It throws warning as "Applications that use 'UriComponentsBuilder' to 
>> parse an externally provided URL (e.g. through a query parameter) AND 
>> perform validation checks on
>> the host of the parsed URL may be vulnerable to a open redirect attack"
>>
>> The only solution available is upgrade from 5.3.27 to 5.3.32(which is 
>> secure version).
>>
>> But when I am trying to upgrade it create lots of issues with DSpace 
>> version and not supported.
>>
>> Can anyone help regarding that and suggest what to do 
>>
>> Any help is highly appreciated
>>
>

-- 
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/d5896a63-6060-4c66-ac88-23e01d69be15n%40googlegroups.com.

[dspace-tech] Re: Could not find or load main class org.dspace.app.launcher.ScriptLauncher

[DSpace Technical Support]

Hi,

That "ScriptLauncher" class is included in the "dspace-api-[version].jar", 
which should be installed in your [dspace]/lib/ directory.   The error 
seems to be saying that file is either missing or incorrect.  You may want 
to double check that all the upgrade steps have succeeded, especially the 
"ant update" step which installs/updates this JAR into that directory.

Tim

On Saturday, March 16, 2024 at 7:48:04 PM UTC-5 obsole...@gmail.com wrote:

> Hello all,
>
> I'm migration from 7.5 to 7.6.1 following the step by step guide 
> https://wiki.lyrasis.org/display/DSDOC7x/Upgrading+DSpace#UpgradingDSpace-ReleaseNotes/SignificantChanges
>
> However, I have this isue running the command "dspace database info":
>
> Using DSpace installation in: C:\DSpace-dspace-7.6.1\dspace
> Error: Could not find or load main class 
> org.dspace.app.launcher.ScriptLauncher
> Caused by: java.lang.ClassNotFoundException: 
> org.dspace.app.launcher.ScriptLauncher
> Any suggestion or step where I could investigate would be appreciated.
>
> Best regards.
>
>
>

-- 
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/5df31c7a-38eb-4c20-8276-5f3d5e463533n%40googlegroups.com.

Re: [dspace-tech] How to find number of times a pdf has been downloaded from an item page

[DSpace Technical Support]

Hi Carolyn,

The *intention* of the File Visits is to track file downloads.  However, I 
will mention that the built-in DSpace Statistics engine is not always the 
most accurate tool.  It sometimes will overcount bot activity and it may 
exclude hits from localhost.  I'd *love* for it to be much more accurate, 
but it honestly hasn't had as much attention from volunteers as other 
featuresand we simply are not able to keep as up-to-date with filtering 
out bots as other statistical tools (like Google Analytics). 

So, if you want a rough estimate, it's likely good enough.  But, if you 
desire more accurate statistics, you'd probably want to use Google 
Analytics.  There's also some early discussion about supporting other 
Analytics services like Matomo (but no official work 
yet): https://github.com/DSpace/DSpace/issues/8414

Tim

On Tuesday, March 19, 2024 at 9:45:36 AM UTC-5 Carolyn Sullivan wrote:

> A note to add to the above:
>
> The 'File Visits' section from what we've seen so far doesn't appear to 
> accurately reflect the number of actual downloads of a file.  From the 
> back-end of Solr, we tried running a query with parameters as follows:
>
> "params":{
>   "q":"*:*",
>   "indent":"true",
>   "q.op":"OR",
>   "fq":["owningItem: -Mysterious Unique Id for the item that owned the 
> file of interest-",
> "bundleName:\"ORIGINAL\""],
>   "rows":"1000",
>   "_":"Thirteen-digit-number"}},
>
> The results included at least four responses where staff had gone to the 
> 'Edit' page for the item, but hadn't actually downloaded the file in 
> question (we could tell because the responses include variables such as 
> time and epersonid, the latter of which can be used to determine an 
> authenticated user).  
>
> So... is there any way to actually tell whether someone downloaded the 
> file from the Solr logs?  As it stands, I'm not sure the 'File Visits' 
> statistics are meaningful.
>
> Thanks,
> Carolyn.
>
> On Mon, Mar 18, 2024 at 5:40 PM Carolyn Sullivan  
> wrote:
>
>> Hello,
>>
>> Just wondering--how do we find the number of downloads of a pdf from a 
>> given item in DSpace?  If you click on 'Statistics' in the toolbar while 
>> accessing an item page, is the 'File Visits' section equivalent to 
>> 'Downloads'?
>>
>> Thanks,
>> Carolyn.
>>
>> -- 
>> 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/eb4a0e3e-ed84-4af0-8cb2-c30637c68ad7n%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/1f8609e7-a400-4bcf-9dc1-33d3190f31e4n%40googlegroups.com.

[dspace-tech] Re: dspace-ui 7.6.1 installation issue on kubernetes

[DSpace Technical Support]

Hi Manish,

The logs you have shared don't appear to show any errors.  Those are the 
same logs I see when starting up the UI locally (and everything works fine).

The message about "Encourage the library authors to publish an Ivy 
distribution" can be safely ignored.  It's a warning from Angular about a 
few third-party libraries we use for DSpace. That warning doesn't impact 
DSpace's behavior, and it's not something that DSpace can fix.  As soon as 
those libraries update themselves the warning should go away.

Tim

On Wednesday, March 27, 2024 at 5:10:21 AM UTC-5 kuma@hcl.com wrote:

> Hi all, 
>
> I am trying to setup dspace-ui 7.6.1 version on my GCP kubernetes, while 
> doing that I noticed my pods are restarting automatically but not coming 
> up. When I checked logs through gcp cloud cli I found below logs.
>
> *" yarn run v1.22.19*
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *$ yarn base-href$ ts-node --project ./tsconfig.ts-node.json 
> scripts/base-href.tsBuilding development app configOverriding app config 
> with /app/config/config.ymlOverriding app config with 
> /app/config/config.development.yamlApplying environment variable 
> DSPACE_REST_SSL with value trueApplying environment variable 
> DSPACE_REST_HOST with value myserver.com Applying 
> environment variable DSPACE_REST_PORT with value 80Applying environment 
> variable DSPACE_REST_NAMESPACE with value /serverSetting baseHref to / in 
> angular.json$ ts-node --project ./tsconfig.ts-node.json scripts/serve.ts 
> --host 0.0.0.0 --disable-host-checkBuilding development app 
> configOverriding app config with /app/config/config.ymlOverriding app 
> config with /app/config/config.development.yamlApplying environment 
> variable DSPACE_REST_SSL with value trueApplying environment variable 
> DSPACE_REST_HOST with value myserver.com Applying 
> environment variable DSPACE_REST_PORT with value 80Applying environment 
> variable DSPACE_REST_NAMESPACE with value /serverOption 'host' has been 
> specified multiple times. The value '0.0.0.0' will be used.Warning: Running 
> a server with --disable-host-check is a security risk. 
> See 
> https://medium.com/webpack/webpack-dev-server-middleware-security-issues-1489d950874a
>  
> 
>  for 
> more information.- Generating browser application bundles (phase: 
> setup)...Building development app configOverriding app config with 
> /app/config/config.ymlOverriding app config with 
> /app/config/config.development.yamlApplying environment variable 
> DSPACE_REST_SSL with value trueApplying environment variable 
> DSPACE_REST_HOST with value myserver.com Applying 
> environment variable DSPACE_REST_PORT with value 80Applying environment 
> variable DSPACE_REST_NAMESPACE with value /serverAngular config.json file 
> generated correctly at /app/src/assets/config.jsonProcessing legacy "View 
> Engine" libraries:- angular-idle-preload [main/commonjs] 
> (git+https://github.com/gdi2290/angular-idle-preload.git 
> )- ngx-sortablejs 
> [es2015/esm2015] (https://github.com/sortablejs/ngx-sortablejs 
> )- ng2-file-upload 
> [es2015/esm2015] ()Encourage the library authors to publish an Ivy 
> distribution."*
>
> *I* need community help to resolve the issue. However I tried to use *same 
> version docker image* in that case only getting container creating 
> message on pod level.
>
> Thanks,
> Manish Kumar
>

-- 
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/a6b22126-f683-4e29-b838-17dfb00a894bn%40googlegroups.com.

[dspace-tech] Re: Recovering admin access

[DSpace Technical Support]

Hi,

Yes, you can regain Admin access from the commandline.  Simply run the 
"./dspace create-administrator" script in the [dspace]/bin/ folder similar 
to the Installation Instructions. See step 14 
here: 
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-BackendInstallation

This script will create a new Administrative user with the email/password 
you provide.  If that user already exists in the system, it will make that 
user an Admin and change their password to the provided password.

Tim

On Thursday, March 28, 2024 at 4:22:14 PM UTC-5 crisalis...@sagrado.edu 
wrote:

> So the person on my team that had the admin access to the repository left 
> and no one knows the credentials the person used. So, basically currently 
> no one has access as an administrator to the repository. Is there any way 
> to recover this or gain access again? 
> La Universidad del Sagrado Corazón le notifica que el contenido de este 
> correo electrónico, al igual que sus anejos, está destinado únicamente a la 
> persona o personas a quien fue dirigido y puede contener información 
> sensitiva, confidencial y/o privilegiada. Si usted lo recibe 
> equivocadamente, queda apercibido de que el uso, revisión, 
> retroalimentación, divulgación, distribución y reproducción del mismo, ya 
> sea oralmente o por cualquier otro medio, o cualquier acción relacionada 
> con el mismo está prohibida. En tal caso, debe comunicarse con el remitente 
> y eliminar el correo y sus anejos de cualquier computadora en la cual haya 
> sido recibido o depositado.
>
> Universidad del Sagrado Corazón, informs you that the total contents of 
> this e-mail, together with any attachments, is intended only for the person 
> or entity to which it is addressed and may contain sensitive, confidential 
> and/or privileged material.  If you are not the intended recipient of this 
> message you are hereby notified that any use, review, retransmission, 
> dissemination, distribution, reproduction whether orally or through any 
> other media and/or any action taken regarding this message is prohibited.  
> If you received this message in error, please contact the sender and delete 
> the material from any computer.

-- 
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/798a6a95-f166-4300-bb13-c6704cc8b587n%40googlegroups.com.

[dspace-tech] Re: Media Viewer Doesn't work in DSPACE 7.6

[DSpace Technical Support]

This feature should work in DSpace 7.6.x.  It's working on our demo site at 
https://demo.dspace.org   You need to click on the thumbnail (of the image) 
for it to expand into the media viewer.

Here's an example on our demo 
site: https://demo.dspace.org/items/795a6906-498a-42a7-a330-f57a6aa1323e

Tim

On Thursday, March 14, 2024 at 3:56:16 AM UTC-5 vikta...@gmail.com wrote:

> Hello,
>
> We currently have Dspace 7.6 in production use and have activated the 
> media viewer and set it to true in the config.prod.yml
>
> mediaViewer:
>   image: true
>   video: true
>
>
> However there is no effect on the Dspace site, the media viewer doesn't 
> display. The images and videos just show thumbnails.
> Is this a bug in DSPACE 7.6 ?
>

-- 
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/c977f084-d043-42b6-b567-6d6b5b0b4f7bn%40googlegroups.com.

[dspace-tech] Re: Loading Recent Submission problem

[DSpace Technical Support]

In order to debug issues in the User Interface, you should follow our 
Troubleshooting guide to locate the error.  The error may be in either the 
user interface (in your browser's DevTools) or in the backend logs.

https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Tim


-- 
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/28ffc251-893b-4c5f-b288-dd29bb46d1a4n%40googlegroups.com.

[dspace-tech] Re: search bar of filters

[DSpace Technical Support]

Hi Alex,

I believe this bug was fixed in 7.6.1 in this 
PR: https://github.com/DSpace/DSpace/pull/8958

See the original bug report here, which describes a similar 
bug: https://github.com/DSpace/DSpace/issues/8914

Tim

On Monday, March 25, 2024 at 2:46:32 AM UTC-5 zxale...@gmail.com wrote:

> Dear colleagues, in the search bar of filters, for example by author's 
> name, only English works. If the author's name in the system is not written 
> in English, the search string of the filter does not find it. Can these 
> settings be changed? For example, the main search bar in the system finds 
> the author in a language other than English.
>
> [image: Screenshot from 2024-03-25 10-22-11.png]
> [image: Screenshot from 2024-03-25 10-44-38.png]
> Help me please!
>
> Best regards,
> Alex
>

-- 
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/86a16cc2-3ca8-4cd5-8053-77c10977284cn%40googlegroups.com.

[dspace-tech] Re: unable to edit metada on some files in DSpace 7.6

[DSpace Technical Support]

Hi David,

Apologies for the delayed response.  A 500 error is an "Internal Server 
Error" which should mean you'd see an "ERROR" log in your dspace.log file 
which corresponds to that error.  I don't see that in the logs you shared 
though, which is odd.  You may want to check again to make sure it wasn't 
overlooked.

If there's still nothing in the dspace.log, you could **temporarily** tell 
the REST API to return the full Java Stacktrace of the error (this is often 
the details needed to debug the problem).  You can do this by adding this 
to your local.cfg:

server.error.include-stacktrace = always

(This is listed as a step to try in our Troubleshooting 
guide: 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)
 
... see step 3.)

I *believe* you will have to reboot the backend for this setting to take 
effect.  Once it is added, then you'd reproduce the 500 error again, and 
you should see the full Java stacktrace included in that 500 response.  
 It's important to *turn this back off* (remove the configuration) once you 
are done leaving this enabled in Production can be a security issue as 
it allows others to force errors in order to see the details of these Java 
stacktraces, which can give them information about your system.

It's unclear to me as well why this error would occur.  If it's only for 
some files/items, that would imply something perhaps in the data of those 
objects.  But, the Java stacktrace should provide more clues.

Tim


On Tuesday, March 12, 2024 at 11:26:27 AM UTC-5 ntkte...@gmail.com wrote:

> Hi,
>
> in our institution, we have been using Invenio 1, but we have migrated to 
> DSpace 7.6 (we have been preparing the migratio since DSpace 6.something).
>
> Now in DSpace 7.6, metadata of some Items cannot be edited via API nor the 
> Administration Interface. The only way to edit for example URI is direct 
> database access, which is not ideal.
>
> This problem however, occurs only on 50 entries from the total number of 
> 1500+ entries which had underwent the migration. There is no visible 
> difference on the metadata either.
>
> Any attempt to edit metadata from Admin UI gives this response:
>
> HTTP/1.1 500 
> Date: Tue, 12 Mar 2024 15:47:38 GMT
> Server: Apache/2.4.37 (Red Hat Enterprise Linux) OpenSSL/1.1.1k
> Vary: Origin,Access-Control-Request-Method,Access-Control-Request-Headers
> Content-Language: en
> X-Content-Type-Options: nosniff
> X-XSS-Protection: 1; mode=block
> Cache-Control: no-cache, no-store, max-age=0, must-revalidate
> Pragma: no-cache
> Expires: 0
> Strict-Transport-Security: max-age=31536000 ; includeSubDomains
> X-Frame-Options: DENY
> Content-Type: application/json;charset=UTF-8
> Connection: close
> Transfer-Encoding: chunked
> {"timestamp":"2024-03-12T15:47:38.237+00:00","status":500,"error":"Internal 
> Server Error","message":"An exception has 
> occurred","path":"/server/api/core/items/065c1a21-7410-4ce6-8f61-a92b30b8c61a"}
>
> in the DSpace logs, there is nothing meaningfull either. From what I've 
> been able to gather, these are logs significant for the performed action:
>
> 024-03-12 16:47:32,787 INFO  unknown unknown org.eclipse.jetty.util.log @ 
> Logging initialized @4943ms to org.eclipse.jetty.util.log.Slf4jLog
> 2024-03-12 16:47:32,989 INFO  unknown unknown 
> org.dspace.importer.external.service.ImportService @ Loading 6 import 
> sources.
> 2024-03-12 16:47:34,251 INFO  unknown unknown 
> org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor
>  
> @ Autowired annotation should only be used on methods with parameters: 
> public java.lang.String 
> org.dspace.storage.bitstore.S3BitStoreService.getBucketName()
> 2024-03-12 16:47:34,810 INFO  unknown unknown 
> org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor
>  
> @ Autowired annotation is not supported on static methods: public static 
> void 
> org.dspace.rdf.storage.DOIURIGenerator.setFallback(org.dspace.rdf.storage.URIGenerator)
> 2024-03-12 16:47:34,814 INFO  unknown unknown 
> org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor
>  
> @ Autowired annotation is not supported on static methods: public static 
> void 
> org.dspace.rdf.storage.DOIHandleURIGenerator.setFallback(org.dspace.rdf.storage.URIGenerator)
> 2024-03-12 16:47:35,288 INFO  unknown unknown 
> org.ehcache.core.EhcacheManager @ Cache 'sherpa.searchByJournalISSN' 
> removed from Eh107InternalCacheManager.
> 2024-03-12 16:47:35,290 INFO  unknown unknown 
> org.ehcache.core.EhcacheManager @ Cache 'manifests' removed from 
> Eh107InternalCacheManager.
> 2024-03-12 16:47:35,292 INFO  unknown unknown 
> org.ehcache.core.EhcacheManager @ Cache 'canvasdimensions' removed from 
> Eh107InternalCacheManager.
> 2024-03-12 16:47:36,938 INFO  unknown unknown 
> org.apache.commons.beanutils.FluentPropertyBeanIntrospector @ Error when 
> creating PropertyDescriptor for public final void 

[dspace-tech] Re: PM2 error: dspace-ui > 1 rules skipped due to selector errors

[DSpace Technical Support]

Hi Andrew,

I don't believe that's an actual error.  I think that's a warning that 
appears for all sites at this time because of how we do our themes in 
Angular.  It can be ignored safely unless you are noticing some sort of bug 
/ improper behavior.

Tim
On Friday, March 22, 2024 at 12:25:06 PM UTC-5 Andrew K wrote:

> Hi!
> I started using pm2 monit and found that every process constantly throws 
> this error:
>
> *dspace-ui > 1 rules skipped due to selector errors:   
> dspace-ui > 
> .custom-file-input:lang(en)~.custom-file-label -> unmatched pseudo-class 
> :lang*
> What is the problem? How to solve it?
>
> WBR,
> Andrew
>

-- 
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/60bfd85f-6669-4dce-80d4-8e25e5052b67n%40googlegroups.com.

[dspace-tech] Re: Queries on Item table in database and its REST API v6

[DSpace Technical Support]

Answered briefly inline below:

   1. In dspace 7.6.1, each item has an identifier called UUID and in the 
   database, item table we have the item_id column which is id of the items 
   from the dspace 5 or older. This is referred as legacy_id in dspace7 
   backend rest code.Is my understanding  correct?
  - This change occurred in DSpace 6.  As of DSpace 6, all objects have 
  UUIDs instead of "id" columns.  Your understanding is correct.
   2. So, when an item is created in dspace 7.6.1, the 'item_id' column in 
   item table in the database will remain null. Is my understanding  correct?
  - Yes, again as of DSpace 6 all objects have UUIDs.  The old 
  "item_id" column should be empty for new items (old ones may still have 
  values).  Eventually this column should be dropped.
   3.  In dspace 7.6.1, we are currently using dspace REST API v6 
   (deprecated) to integrate an application with Dspace. So, the rest call 
   "POST /items/find-by-metadata-field " response doesn't have the name-value 
   pair "id":"Integer id" any more as in Dspace 5 instead we have uuid.
  - I believe this is correct but am not well versed in the older REST 
  API (v6).  Essentially though, as of DSpace 6 all objects are identified 
by 
  UUID instead of "id" fields
   4.  Even though REST API v6 (deprecated)is used, will the "GET 
   /rest/status" returns  to be "7".
  - Yes, this is correct because the system itself is running version 
  7. 
   

Please also keep in mind that the REST API v6 will be removed in DSpace 8.  
You should work to migrate to the new REST API at some point.
Tim

On Tuesday, March 12, 2024 at 7:15:21 AM UTC-5 tsak...@gmail.com wrote:

> Hi team,
>
> We are in the process of upgrading dspace from version 5 to 7.6.1.
>
> I have a few queries as listed below.
>
> 1. In dspace 7.6.1, each item has an identifier called UUID and in the 
> database, item table we have the item_id column which is id of the items 
> from the dspace 5 or older. This is referred as legacy_id in dspace7 
> backend rest code.
> Is my understanding  correct?
>
> 2. So, when an item is created in dspace 7.6.1, the 'item_id' column in 
> item table in the database will remain null. Is my understanding  correct?
>
> 3. In dspace 7.6.1, we are currently using dspace REST API v6 (deprecated) 
> to integrate an application with Dspace. So, the rest call "POST 
> /items/find-by-metadata-field " response doesn't have the name-value pair 
> "id":"Integer id" any more as in Dspace 5 instead we have uuid.
> Is my understanding correct?
>
> 4. Even though REST API v6 (deprecated)is used, will the "GET 
> /rest/status" returns  to be "7".
> Is my understanding correct? 
>
> Can anyone please help me with my understanding which will be very helpful?
>
> Thanks and Regards,
> Akshay Karthik Thana Sekar
>

-- 
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/49807c7c-c994-4cda-80eb-9d4d6cb6c043n%40googlegroups.com.

[dspace-tech] Recovering admin access

[Crisalis M Carrion Cotto]

So the person on my team that had the admin access to the repository left 
and no one knows the credentials the person used. So, basically currently 
no one has access as an administrator to the repository. Is there any way 
to recover this or gain access again?
-- 
La Universidad del Sagrado Corazón le notifica que el contenido de este 
correo electrónico, al igual que sus anejos, está destinado únicamente a la 
persona o personas a quien fue dirigido y puede contener información 
sensitiva, confidencial y/o privilegiada. Si usted lo recibe 
equivocadamente, queda apercibido de que el uso, revisión, 
retroalimentación, divulgación, distribución y reproducción del mismo, ya 
sea oralmente o por cualquier otro medio, o cualquier acción relacionada 
con el mismo está prohibida. En tal caso, debe comunicarse con el remitente 
y eliminar el correo y sus anejos de cualquier computadora en la cual haya 
sido recibido o depositado.

Universidad del Sagrado Corazón, informs you 
that the total contents of this e-mail, together with any attachments, is 
intended only for the person or entity to which it is addressed and may 
contain sensitive, confidential and/or privileged material.  If you are not 
the intended recipient of this message you are hereby notified that any 
use, review, retransmission, dissemination, distribution, reproduction 
whether orally or through any other media and/or any action taken regarding 
this message is prohibited.  If you received this message in error, please 
contact the sender and delete the material from any computer.

-- 
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/b6bf8fc5-2dc8-4b80-af97-ef313cdac692n%40googlegroups.com.

[dspace-tech] Re: Dspace 7.6 Angular installation

[DSpace Technical Support]

That sounds like an error because something didn't install properly.  I'd 
recommend re-running the "yarn install" by doing this:

# Clean current cached data
yarn clean

# Reinstall all dependencies
yarn install

# Try to build again
yarn build:prod

Hopefully it will succeed this time, as it sounds like it's complaining 
that a dependency wasn't fully installed in that "yarn install" step.

Tim

On Thursday, March 21, 2024 at 4:14:01 AM UTC-5 stb...@gmail.com wrote:

> Dear all,
>
> after building yarn build:prod I have got the error message:
>
> ./node_modules/@ng-dynamic-forms/ui-ng-bootstrap/fesm2020/ui-ng-bootstrap.mjs:736:285-301
>  
> - Error: export 'MaskDirective' (imported as 'i4') was not found in 
> 'ngx-mask' (possible exports: INITIAL_CONFIG, NEW_CONFIG, NGX_MASK_CONFIG, 
> NgxMaskDirective, NgxMaskModule, NgxMaskPipe, NgxMaskService, 
> _configFactory, initialConfig, timeMasks, withoutValidation) 
>
> What should I do now?
>
> Thanking you in advance
> Stefanie 
>

-- 
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/d0c14516-b1ab-4909-b0ef-c783b996ee80n%40googlegroups.com.

[dspace-tech] Re: dspace-ui 7.6.1 installation issue on kubernetes

['Manish Kumar' via DSpace Technical Support]

Hi,

Thanks for your reply, I enabled --verbose and faced so many GET call, that 
was taking time after  *Encourage the library authors to publish an Ivy 
distributio*n, and we had initilize 60 seconds initialDelaySeconds inside 
readinessProbe 
 due to this short time period once wait time reach to limit,  pods restart 
again and again, we increased the time and now able to setup everything and 
UI is running after that.


On Friday, March 29, 2024 at 3:45:13 AM UTC+5:30 DSpace Technical Support 
wrote:

> Hi Manish,
>
> The logs you have shared don't appear to show any errors.  Those are the 
> same logs I see when starting up the UI locally (and everything works fine).
>
> The message about "Encourage the library authors to publish an Ivy 
> distribution" can be safely ignored.  It's a warning from Angular about a 
> few third-party libraries we use for DSpace. That warning doesn't impact 
> DSpace's behavior, and it's not something that DSpace can fix.  As soon as 
> those libraries update themselves the warning should go away.
>
> Tim
>
> On Wednesday, March 27, 2024 at 5:10:21 AM UTC-5 kuma@hcl.com wrote:
>
>> Hi all, 
>>
>> I am trying to setup dspace-ui 7.6.1 version on my GCP kubernetes, while 
>> doing that I noticed my pods are restarting automatically but not coming 
>> up. When I checked logs through gcp cloud cli I found below logs.
>>
>> *" yarn run v1.22.19*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *$ yarn base-href$ ts-node --project ./tsconfig.ts-node.json 
>> scripts/base-href.tsBuilding development app configOverriding app config 
>> with /app/config/config.ymlOverriding app config with 
>> /app/config/config.development.yamlApplying environment variable 
>> DSPACE_REST_SSL with value trueApplying environment variable 
>> DSPACE_REST_HOST with value myserver.com Applying 
>> environment variable DSPACE_REST_PORT with value 80Applying environment 
>> variable DSPACE_REST_NAMESPACE with value /serverSetting baseHref to / in 
>> angular.json$ ts-node --project ./tsconfig.ts-node.json scripts/serve.ts 
>> --host 0.0.0.0 --disable-host-checkBuilding development app 
>> configOverriding app config with /app/config/config.ymlOverriding app 
>> config with /app/config/config.development.yamlApplying environment 
>> variable DSPACE_REST_SSL with value trueApplying environment variable 
>> DSPACE_REST_HOST with value myserver.com Applying 
>> environment variable DSPACE_REST_PORT with value 80Applying environment 
>> variable DSPACE_REST_NAMESPACE with value /serverOption 'host' has been 
>> specified multiple times. The value '0.0.0.0' will be used.Warning: Running 
>> a server with --disable-host-check is a security risk. 
>> See 
>> https://medium.com/webpack/webpack-dev-server-middleware-security-issues-1489d950874a
>>  
>> 
>>  for 
>> more information.- Generating browser application bundles (phase: 
>> setup)...Building development app configOverriding app config with 
>> /app/config/config.ymlOverriding app config with 
>> /app/config/config.development.yamlApplying environment variable 
>> DSPACE_REST_SSL with value trueApplying environment variable 
>> DSPACE_REST_HOST with value myserver.com Applying 
>> environment variable DSPACE_REST_PORT with value 80Applying environment 
>> variable DSPACE_REST_NAMESPACE with value /serverAngular config.json file 
>> generated correctly at /app/src/assets/config.jsonProcessing legacy "View 
>> Engine" libraries:- angular-idle-preload [main/commonjs] 
>> (git+https://github.com/gdi2290/angular-idle-preload.git 
>> )- ngx-sortablejs 
>> [es2015/esm2015] (https://github.com/sortablejs/ngx-sortablejs 
>> )- ng2-file-upload 
>> [es2015/esm2015] ()Encourage the library authors to publish an Ivy 
>> distribution."*
>>
>> *I* need community help to resolve the issue. However I tried to use *same 
>> version docker image* in that case only getting container creating 
>> message on pod level.
>>
>> Thanks,
>> Manish Kumar
>>
>

-- 
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/3ce29318-2ebc-481a-8eb8-5008109d72d1n%40googlegroups.com.