[dspace-tech] DSpace 8.0 Testathon Begins Today, runs through April 19, 2024

['Tim Donohue' via DSpace Technical Support]

Forwarding along on behalf of Kimberly Chapman, DCAT chair.


From: dspacecommunityadvisoryt...@googlegroups.com 
 on behalf of Chapman, Kimberly A 
- (kimberlychapman) 
Sent: Monday, April 8, 2024 12:42 PM
To: 'dspace-commun...@googlegroups.com' ; 
'dspacecommunityadvisoryt...@googlegroups.com' 

Subject: DSpace 8.0 Testathon Begins Today, runs through April 19, 2024


Hello DSpace Community,



The DSpace 8.0 Testathon begins today! Thank you to all the DSpace 8.0 
developers who’ve gotten us this far, and thank you in advance to all of you 
who are going to participate in the Testathon!



Testathon Dates: April 8 – April 19, 2024.



We ask that you take a few minutes of your time to help us fully test this new 
release. We want to ensure we are maintaining the same level of quality that 
you have come to expect out of a new DSpace release. In addition to testing new 
features, the Testathon is an opportunity for existing DSpace sites to ensure 
that the features they care about are working well in 8.0.​​  If any of those 
features have bugs, then Testathon is the opportunity to get immediate 
developer attention​​ on those bugs, to ensure the bugs are fixed prior to the 
8.0 final release.



For more information on the Testathon, please visit the DSpace Release 8.0 
Testathon 
page.

New to testing? Want to test with others? We're offering testathon coworking 
sessions on Zoom at the following dates/times:

  *   Tuesday, April 9th, 1 pm ET.
  *   Wednesday, April 10th, 1 pm ET.
  *   Thursday, April 11th, 1 pm ET
  *   Friday, April 12th, 1 pm ET
  *   Monday, April 15th, 1 pm ET
  *   Tuesday, April 16th, 1 pm ET
  *   Wednesday April 17th, 1 pm ET
  *   Thursday, April 18th, 1 pm ET

The above sessions will be held at this Zoom link: 
https://arizona.zoom.us/j/82004507292 (Meeting ID 820 0450 7292) (Passcode: 
dspace)

Kimberly Chapman
DSpace Community Advisory Team (DCAT) Chair

-- 
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/PH0PR22MB32747B0BDCA0F28ED71C89A9ED002%40PH0PR22MB3274.namprd22.prod.outlook.com.

[dspace-tech] DSpace Program Coordinator Position Announcement (remote)

['Tim Donohue' via DSpace Technical Support]

Forwarding this message to other DSpace lists on behalf of Laurie.  If you have 
questions about the role, please get in touch with Laurie.

Tim


From: dspace-commun...@googlegroups.com  on 
behalf of Laurie Arp 
Sent: Tuesday, January 16, 2024 10:30 AM
To: DSpace Community 
Subject: [dspace-community] DSpace Program Coordinator Position Announcement 
(remote)


Greetings,



Lyrasis is seeking a collaborative and detail-oriented individual to serve as 
the DSpace Program Coordinator.

The Program Coordinator serves as a liaison to the DSpace governance, service 
providers, software developers, and other stakeholders. Key activities of the 
role include building communication and outreach plans and coordinating 
meetings and presentations.

If you are someone who enjoys collaboration and solving interesting problems, 
you will thrive in this role. Individuals with excellent communication skills, 
the ability to interact with a variety of different stakeholders in a global 
community, and an interest in developing relationships with current and 
potential community members are encouraged to apply.

This is currently a part-time position (16-20 hours per week) with the 
potential to grow into a full-time role over time.

This is a remote position.



Applications are accepted until the position is filled but review of 
applications will begin February 6, 2024.



You can view the announcement & apply online at: 
https://lyrasis.isolvedhire.com/jobs.



Best wishes,


Laurie Gemmill Arp

Senior Director, Community Supported Technologies and Hosting Services

laurie@lyrasis.org

800.999.8558 x 2908

--
Laurie Gemmill Arp

-- 
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/PH0PR22MB3274495906BAE30A8B778124ED732%40PH0PR22MB3274.namprd22.prod.outlook.com.

[dspace-tech] Announcing the new https://demo.dspace.org running on Docker!

['Tim Donohue' via DSpace Technical Support]

All,

As of today, our public demo site for DSpace (v7) has moved to 
https://demo.dspace.org . The REST API backend is now available at 
https://demo.dspace.org/server/

This demo site auto-updates itself every time a new change is pushed out to the 
DSpace v7 maintenance branches (dspace-7_x branch) in our frontend or backend 
codebases. So, it will always be running the latest DSpace 7 code.

In addition, for developers, a new https://sandbox.dspace.org site (backend: 
https://sandbox.dspace.org/server/) is available to preview any pre-8.0 code 
and features.  (Because 8.0 development has just begun, this sandbox site is 
currently identical in features to demo.dspace.org.)

Finally, the older DSpace 6 demo site is still temporarily available at a new 
URL of https://demo6.dspace.org .  More information on that is below.

New Demo Platform uses Docker

The demo.dspace.org site is now on a new Docker-based platform, hosted by the 
DSpaceDirect team at Lyrasis.  This new platform allows us to use the Docker 
images generated by the scripts in our codebase to run our demo site.

  *   The demo frontend uses the new "dspace-7_x-dist" image for 
"dspace/dspace-angular" (https://hub.docker.com/r/dspace/dspace-angular), built 
from the script at 
https://github.com/DSpace/dspace-angular/blob/dspace-7_x/docker/docker-compose-dist.yml
  *   The demo backend uses the new "dspace-7_x" image for "dspace/dspace" 
(https://hub.docker.com/r/dspace/dspace), built from the script at 
https://github.com/DSpace/DSpace/blob/dspace-7_x/docker-compose.yml

(The sandbox.dspace.org site works in the same way, but uses the images built 
from the "main" branches in our codebases.)

This demo platform provides verification that these Docker images could be used 
in Production scenarios. That said, because our core development team does not 
have experts on running Docker in Production, we still recommend institutions 
exercise caution & closely analyze these images before using them in your own 
Production setups.  We also welcome anyone to pass along general Docker 
improvements/enhancements as contributions back to DSpace!

Updating old DSpace 7 demo URLs locally

All older DSpace 7 demo URLs, namely https://demo7.dspace.org/ (old demo 
frontend) and https://api7.dspace.org/server/ (old demo backend) will begin 
redirecting to the new locations immediately.  We will also work to 
correct/update these older URLs in our codebase and Wiki to ensure they point 
at the new locations. (Please be patient, as there are many links to update.)

Anyone who is using the older demo URLs locally for testing/development should 
update your configuration to use either demo.dspace.org (for 'dspace-7_x' 
branch) or sandbox.dspace.org (for 'main' branch).  These changes have already 
been made in our GitHub codebase. So, you could also simply pull down the 
latest code.

Old DSpace 6 Demo Site moved to demo6.dspace.org

As we are aware some institutions are still working on their upgrade from v6 to 
v7, we have migrated the older DSpace v6 Demo site to 
https://demo6.dspace.org/. We will do our best to keep this older 6.4 site 
running until the beginning of 2024. However, please keep in mind, because this 
site is on an aging platform & v6 is end-of-life, this demo site may not be as 
stable as it once was.

Acknowledgment / Thank You!

We'd like to thank the DSpaceDirect team at Lyrasis for helping us establish 
this new demo platform and committing to provide ongoing support for the future.

In addition, we owe a HUGE "Thank You" to the Atmire and 4Science teams for 
hosting our prior https://demo7.dspace.org (frontend) and 
https://api7.dspace.org (backend) demo sites, respectively. Both 4Science and 
Atmire have kindly donated these demo sites since the beginning of DSpace 7 
development in 2018. This has been an amazing service and major donation back 
to our entire DSpace community.

Thank you to the Atmire, 4Science and Lyrasis teams!


--

Tim Donohue (he/him)

Technical Lead, DSpace

tim.dono...@lyrasis.org

Lyrasis.org | DSpace.org

[cid:c090b2d3-ffd1-4554-b27a-ee9e4c1258d7]

-- 
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/PH0PR22MB3274AEBB90CA71766AA553D2ED1EA%40PH0PR22MB3274.namprd22.prod.outlook.com.

Re: [dspace-tech] Re: Seemingly crazy catch 22 Dspace DB migration loop question!!!

['Tim Donohue' via DSpace Technical Support]

Hi Euler,

This 5.7 migration is obsolete & it has caused issues with others as well.  See 
this old dspace-tech mailing list thread: 
https://groups.google.com/g/dspace-tech/c/PlOA1WMvd4M/m/eBVE5RfhBgAJ

The solution is to use the new "./dspace database skip" command provided as of 
DSpace 7.5 and skip this problematic migration by running:


./dspace database skip "5.7.2017.04.11"


This is safe to do because the migration is obsolete​.

Tim

From: dspace-tech@googlegroups.com  on behalf of 
euler 
Sent: Monday, July 31, 2023 6:05 AM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] Re: Seemingly crazy catch 22 Dspace DB migration 
loop question!!!

Hi Tim,

Apologies for not reporting back sooner. As per your suggestion, I removed the 
SQL you mentioned, performed 'mvn clean package', and 'ant update'. I did not 
receive any errors when running 'dspace database repair', but when I run 
'dspace database migrate ignored', the console returned a lot of errors too 
long to post here. Please see the attached text file from the output of my 
console. I will try to restore this repository in a local instance with the 
latest 6x version and try to run 'dspace database migrate ignored' from there. 
I suspect there is something wrong with this particular instance because when I 
run the command 'dspace database migrate ignored' on this repository which is 
running version 6.3, it returned this error:

Database URL: jdbc:postgresql://localhost:5432/dspace
Migrating database to latest version AND running previously "Ignored" 
migrations... (Check logs for details)
Migration exception:
java.sql.SQLException: Flyway migration error occurred
at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:673)
at org.dspace.storage.rdbms.DatabaseUtils.main(DatabaseUtils.java:187)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229)
at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81)
Caused by: org.flywaydb.core.internal.dbsupport.FlywaySqlScriptException:
Migration 
V5.7_2017.04.11__DS-3563_Index_metadatavalue_resource_type_id_column.sql failed
-
SQL State  : 42703
Error Code : 0
Message: ERROR: column "resource_type_id" does not exist
Location   : 
org/dspace/storage/rdbms/sqlmigration/postgres/V5.7_2017.04.11__DS-3563_Index_metadatavalue_resource_type_id_column.sql
 
(c:\DSpace\file:\C:\DSpace\lib\dspace-api-6.3.jar!\org\dspace\storage\rdbms\sqlmigration\postgres\V5.7_2017.04.11__DS-3563_Index_metadatavalue_resource_type_id_column.sql)
Line   : 16
Statement  : CREATE INDEX metadatavalue_resource_type_id_idx ON metadatavalue 
(resource_type_id)

at org.flywaydb.core.internal.dbsupport.SqlScript.execute(SqlScript.java:117)
at 
org.flywaydb.core.internal.resolver.sql.SqlMigrationExecutor.execute(SqlMigrationExecutor.java:71)
at org.flywaydb.core.internal.command.DbMigrate.doMigrate(DbMigrate.java:352)
at org.flywaydb.core.internal.command.DbMigrate.access$1100(DbMigrate.java:47)
at 
org.flywaydb.core.internal.command.DbMigrate$4.doInTransaction(DbMigrate.java:308)
at 
org.flywaydb.core.internal.util.jdbc.TransactionTemplate.execute(TransactionTemplate.java:72)
at 
org.flywaydb.core.internal.command.DbMigrate.applyMigration(DbMigrate.java:305)
at org.flywaydb.core.internal.command.DbMigrate.access$1000(DbMigrate.java:47)
at 
org.flywaydb.core.internal.command.DbMigrate$2.doInTransaction(DbMigrate.java:230)
at 
org.flywaydb.core.internal.command.DbMigrate$2.doInTransaction(DbMigrate.java:173)
at 
org.flywaydb.core.internal.util.jdbc.TransactionTemplate.execute(TransactionTemplate.java:72)
at org.flywaydb.core.internal.command.DbMigrate.migrate(DbMigrate.java:173)
at org.flywaydb.core.Flyway$1.execute(Flyway.java:959)
at org.flywaydb.core.Flyway$1.execute(Flyway.java:917)
at org.flywaydb.core.Flyway.execute(Flyway.java:1373)
at org.flywaydb.core.Flyway.migrate(Flyway.java:917)
at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:662)
... 7 more
Caused by: org.postgresql.util.PSQLException: ERROR: column "resource_type_id" 
does not exist
at 
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2422)
at 
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2167)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:306)
at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:441)
at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:365)
at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:307)
at 

[dspace-tech] Re: Display IP-restricted community names to anonymous users

['Tim Donohue' via DSpace Technical Support]

Hi Amy,

I can verify this is correct behavior in DSpace 7 because the backend (REST 
API) needs to apply access restrictions in a consistent manner.

Simply put, in DSpace 7, you must have READ permissions in order to "see" 
any object (including metadata about that object) from the REST API (and 
therefore also the UI).  So, if you make an entire community have an IP 
restriction, then only those IPs will have that "READ" permission.  At this 
time, there's not a way to apply that READ permission differently for 
top-level communities than for their sub-communities/collections/items.  
"READ" always gives the permissions to see the object in DSpace 7.

The only way (that I know of) to achieve the behavior you suggest in DSpace 
7 would be to only apply the READ restrictions to the 
sub-communities/collections/items, and leave the Communities themselves as 
READ Anonymous.  However, that would result in empty looking Communities 
(to anonymous users), but once you login you'd see their 
sub-communities/collections/items.

Simply put, we don't have a way to display *only metadata* for restricted 
Communities/Collections at this time. Doing so would let users without READ 
permissions see the entire "hierarchy" (as you'd be able to read the basic 
metadata about all restricted Communities & Collections).   So, in DSpace 
7, we had to make the definition more strict: if you don't have READ,  then 
the object is "hidden" to you.

Tim
On Monday, July 10, 2023 at 7:20:08 PM UTC-5 amy.ball...@colostate.edu 
wrote:

> We want the names & text blurbs of our IP-restricted communities to be 
> visible to all users on the home page & collections/communities page, even 
> to anonymous / non-logged-in users.  
>
> To put it another way, we want the IP restriction to apply to the 
> sub-communities, collections, and items, but not to the top-level community 
> name & news text. 
>
> This info was visible to everyone in our DSpace6 install, but is not 
> showing up at all in DSpace7. To the anonymous user, it's as if this 
> community does not exist. 
>
> Is this something we can control with authorizations or in the config 
> file? 
>
> Does it work differently in DSpace7 than in DSpace6? 
>
> Thanks in advance to anyone who can advise. 
>
> ~Amy
>
>

-- 
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/52e69774-1703-461c-8325-1555b2aab1fan%40googlegroups.com.

Re: [dspace-tech] Error 500, Service Unavailable

['Tim Donohue' via DSpace Technical Support]

Hi,

This sounds similar to the "Common Installation Issue" listed here: 
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-%22500ServiceUnavailable%22fromtheUserInterface

Essentially, it's caused by the backend and frontend being unable to 
communicate.  See the hints on that page for things to double check... it's 
likely in one of your frontend or backend configurations.

Tim

From: dspace-tech@googlegroups.com  on behalf of 
Robert Thiare 
Sent: Thursday, July 6, 2023 10:39 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Error 500, Service Unavailable

Hello,
I am configuring DSpace5 using docker swarm and traefik to do reverse proxy. My 
problem is that my front-end can't communicate with my back-end because I 
changed the access URL (instead of http://localhost:4000, I use 
dspace.localhost). I've changed "dspace.ui.url" in local.cfg and in dspace.cfg 
but still nothing.


Thanks for your help!
[cap.PNG]
[cap2.PNG]

--
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/012ef217-7514-469e-989f-3286e1ec0bfen%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/PH0PR22MB32745FD8494F4621E1567D63ED2CA%40PH0PR22MB3274.namprd22.prod.outlook.com.

[dspace-tech] Re: Harvesting using OAI-PMH

['Tim Donohue' via DSpace Technical Support]

Hi Sean,

As a basic answer to the original question... you are correct, DSpace 
currently only allows you to set a Collection to harvest a *single* set of 
records.  There's currently no way to provide multiple harvesting settings 
for a single DSpace Collection.

Tim

On Wednesday, June 21, 2023 at 3:40:41 AM UTC-5 sean@gmail.com wrote:

> Is it possible to harvest an existing repository's collections into a new 
> repository so that multiple collections from different communities are 
> combined in the new repository?
>
> For example:
>
> Existing repository collections:
> A
> B
> C
> D
>
> New repository collections: 
> A & C
> B & D
>
> As far as I've been able to figure out, I can set a collection to harvest 
> only a single set of records. I can't find a way to append another set.
>
> Sean
>

-- 
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/05db9783-8779-4c3d-bd2c-c15a3fed7b6en%40googlegroups.com.

Re: [dspace-tech] Oddities around the Creative Commons license configuration in item-submission.xml

['Tim Donohue' via DSpace Technical Support]

All,

A quick follow-up on the CC license listing "CC0" twice.  It appears 
there's a simple configuration in dspace.cfg which can "solve" this problem 
within DSpace itself.  A new PR was just submitted which includes that 
configuration change: https://github.com/DSpace/DSpace/pull/8903

The entire configuration change can be found 
here: https://github.com/DSpace/DSpace/pull/8903/files

This is under review/testing, but assuming it works well (I expect it 
should) this will be in the upcoming 7.6 release.

Tim
On Friday, June 2, 2023 at 8:56:27 AM UTC-5 pai...@udel.edu wrote:

> I would like to know this too -- CC licenses can be confusing for our 
> researchers, and I'd like to make sure we're not adding in any more chaos 
> into the mix than is necessary.
>
> 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 Thu, Jun 1, 2023 at 3:05 PM Erica Johns  wrote:
>
>> follow up question to this issue: what will happen to the items that 
>> selected a CC license until the bug is fixed and selected one of the two 
>> same options? do we have any sense of whether these will map and which CC 
>> license they will map to? perhaps we can make recommendations of which CCO 
>> to select? 
>>
>> thanks, 
>> Erica
>>
>> On Fri, May 12, 2023 at 2:21 PM Paige Morgan  wrote:
>>
>>> Thanks, Erica -- while I don't love bugs, I'm always relieved to hear 
>>> that I'm not the only one seeing them. 
>>>
>>> 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. ***
>>>
>>>
>>> On Fri, May 12, 2023 at 2:18 PM Erica Johns  wrote:
>>>
 hi Paige, 

 We've noticed the same thing at Cornell. I made a ticket 
  for this with dspace 
 and it was determined this is a bug on the CC side. I then made a github 
 ticket with CC to fix. CC has marked the ticket high priority and awaiting 
 triage. 
 https://github.com/creativecommons/creativecommons.org/issues/1273 

 best, 
 Erica

 On Fri, May 12, 2023 at 1:19 PM Paige Morgan  wrote:

> Hi, all--
>
> We recently altered our item-submission.xml config file to start 
> allowing users to select a Creative Commons license during the upload 
> process. It's working, but for reasons that aren't clear to me, users are 
> seeing two options to select CC0 (see below). Other than uncommenting 
> this 
> step, we haven't made any alterations to this part of the code.
>
> Anyone have any ideas about what might be happening? Anyone 
> experiencing the same thing?
>
> Thanks in advance,
> Paige
>
> [image: image.png]
>
> -
> *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 

Re: [dspace-tech] deleting multiple bitstreams results in locked bitstreams

['Tim Donohue' via DSpace Technical Support]

Hi Paige,

I've not been able to reproduce that "locked bitstreams" issue...but can 
reproduce that deleting multiple bitstreams will only delete one bitsteam.

I suspect though that the "locked bitstreams" issue is simply a permissions 
issue.  That should be fixable if you Edit the Item and go to "Status -> 
Authorizations".  If you look at the policies of those locked bitstreams (in 
the ORIGINAL bundle), it's possible that their "READ" policy is wrong.  If you 
want them available anonymously then READ must use the "Anonymous" group.

For more info on managing policies on that page, see the docs at 
https://wiki.lyrasis.org/pages/viewpage.action?pageId=249135668

If that's not the issue you are seeing, then it's possible there's an 
underlying error.  In which case you may need to use the Troubleshooting guide 
to look for errors: 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Tim

From: dspace-tech@googlegroups.com  on behalf of 
Paige Morgan 
Sent: Tuesday, June 13, 2023 1:47 PM
To: Tim Donohue 
Cc: DSpace Technical Support 
Subject: Re: [dspace-tech] deleting multiple bitstreams results in locked 
bitstreams

Thanks, Tim -- out of curiosity, is there anyway to unlock items once they've 
been locked? I didn't see anything in the regular documentation about doing 
that; clicking on the padlock just gets a "this item is forbidden" error 
message.

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
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. **


On Fri, Jun 2, 2023 at 5:45 PM Tim Donohue 
mailto:tim.dono...@lyrasis.org>> wrote:
Hi Paige,

This sounds like this bug: https://github.com/DSpace/DSpace/issues/8029

We are working on a fix that is coming in 7.6 (which is due later this month).  
The fix is in the final stages of review, so I'm sure it will be included in 
7.6.

Tim

From: dspace-tech@googlegroups.com 
mailto:dspace-tech@googlegroups.com>> on behalf 
of Paige Morgan mailto:paig...@udel.edu>>
Sent: Friday, June 2, 2023 8:54 AM
To: DSpace Technical Support 
mailto:dspace-tech@googlegroups.com>>
Subject: [dspace-tech] deleting multiple bitstreams results in locked bitstreams

Hi all--

We've uncovered an unusual behavior in both our production repository and our 
sandbox (both running DSpace 7.4). A colleague and I can mostly reliably 
reproduce it in our instances -- it doesn't happen every single time, but it 
does happen repeatedly. I have not yet been able to reproduce this in the demo 
version, so it may well be something in our local config -- but it's a weird 
phenomenon.

We use DSpace both for our institutional repository, and for our digitized 
collection materials from Special Collections. For that latter set of material, 
occasionally, we need to wholly replace a bitstream -- versioning isn't 
appropriate. When we go in, and try to delete more than one bitstream (by 
clicking on the trashcan icon for the selected bitstreams, and then hitting the 
save button), one of the bitstreams is deleted -- but the other ones selected 
for deletion become locked (previously they were publicly available.) No one 
can delete them, and trying to access them prompts users to log in, but 
eventually results in a 404 page, even though the bitstream is still present, 
and the bitstream access policies all suggest that it's functioning normally.

It's pretty rare for us to delete bitstreams entirely, which is why we're just 
discovering this now, 7 months into running DSpace 7.4. But I'd still like to 
get it sorted out, especially because it's making a couple of items in our 
production instance inaccurate.

Has anyone else encountered anything like this? Thanks in advance--

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
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 

Re: [dspace-tech] No _links section found at...

['Tim Donohue' via DSpace Technical Support]

Hi Donna,

This error is listed in our "Common Installation Issues" at the bottom of the 
Installation guide.  See the hints/tips there for ways to fix it.

https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-%22No_linkssectionfoundat...%22errorfromUserInterface

If none of those work, you may also want to see if other errors appear via our 
troubleshooting guide: 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Tim

From: 'donna@canterbury.ac.nz' via DSpace Technical Support 

Sent: Monday, June 5, 2023 11:38 PM
To: DSpace Technical Support 
Subject: [dspace-tech] No _links section found at...

Hi,

I’m installing DSpace 7.5 but am experiencing the “No _links section found 
at...” error after starting up the UI. The UI loads in the browser, but it 
fails to load the collections and is stuck on an endless loading loop.

I’ve run some tests, and all seems well otherwise. When I visit 
https://irdev3.canterbury.ac.nz/server/api I get output equivalent to 
https://api7.dspace.org/server/api. Running yarn test:rest returns a 200 
response and validation checks are “true”.

I get the feeling that this is where my problem lies - the UI is running on the 
same machine as the backend and they’re both proxied via Apache. There’s no 
local security certificate – the sites are secured via the wider institutional 
firewall (F5 Big-IP), and I’m completely ignorant of the specifics of how 
that’s done. The backend is HTTPS, but I’m seeing some _links showing as http – 
is this an indication of an incorrect configuration somewhere?

  "type": "discover",
  "_links": {
"facets": {
  "href": "http://irdev3.canterbury.ac.nz/server/api/discover/search/facets;
},
"objects": {
  "href": 
"http://irdev3.canterbury.ac.nz/server/api/discover/search/objects;
},
"self": {
  "href": "http://irdev3.canterbury.ac.nz/server/api/discover/search;
}

Help appreciated – let me know if I need to provide any further details.

Thanks,
Donna

--
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/3013f581-4dd5-4dfd-b750-8a4d2072895an%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/PH0PR22MB32745B3E0C3CC756F50ED097ED52A%40PH0PR22MB3274.namprd22.prod.outlook.com.

Re: [dspace-tech] DSpace 7.5 Localhost in citation_pdf_urL

['Tim Donohue' via DSpace Technical Support]

Hi Pierre,

It's likely that your proxy isn't passing though the repository URL information 
to the frontend.  This can be done by using X-Forwarded-* HTTP headers.

For instance:
X-Forwarded-Host corpus.ulaval.ca
X-Forwarded-Proto https

Try setting those headers in your proxy (Apache or similar).  That should solve 
the issue, as DSpace will attempt to detect your deployed URL use it for those 
"citation_pdf_url" tags.

(I've realized this doesn't seem to be clearly documented, so I'll add some 
notes about X-Forwarded headers to our SEO guidelines at: 
https://wiki.lyrasis.org/display/DSDOC7x/Search+Engine+Optimization)

Tim

From: dspace-tech@googlegroups.com  on behalf of 
pierre...@bibl.ulaval.ca 
Sent: Monday, June 5, 2023 10:21 AM
To: DSpace Technical Support 
Subject: [dspace-tech] DSpace 7.5 Localhost in citation_pdf_urL

Bonjour,

We have noticed that DSpace 7.5 is generating a Google Scholar Meta tag 
citation_pdf_url containing a localhost adress instead of our official IR 
address (https://corpus.ulaval.ca).

Example in our repository: 
https://corpus.ulaval.ca/entities/publication/d86954ab-35a0-4b71-a4fe-03b12f979ac1
Looking at the source code of the page, you should see the HTML TAG: http://localhost:4000/bitstreams/[...]

We are not sure where to change this. Is it a configuration? Where should we 
made the change so that DSpace cease to use localhost url for this tag?

Thank you very much for you help!

Best,
Pierre

--
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/09f60b4a-9495-4998-81cd-ff7dc7c6350dn%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/PH0PR22MB3274592DE541106AD87B919DED4DA%40PH0PR22MB3274.namprd22.prod.outlook.com.

Re: [dspace-tech] deleting multiple bitstreams results in locked bitstreams

['Tim Donohue' via DSpace Technical Support]

Hi Paige,

This sounds like this bug: https://github.com/DSpace/DSpace/issues/8029

We are working on a fix that is coming in 7.6 (which is due later this month).  
The fix is in the final stages of review, so I'm sure it will be included in 
7.6.

Tim

From: dspace-tech@googlegroups.com  on behalf of 
Paige Morgan 
Sent: Friday, June 2, 2023 8:54 AM
To: DSpace Technical Support 
Subject: [dspace-tech] deleting multiple bitstreams results in locked bitstreams

Hi all--

We've uncovered an unusual behavior in both our production repository and our 
sandbox (both running DSpace 7.4). A colleague and I can mostly reliably 
reproduce it in our instances -- it doesn't happen every single time, but it 
does happen repeatedly. I have not yet been able to reproduce this in the demo 
version, so it may well be something in our local config -- but it's a weird 
phenomenon.

We use DSpace both for our institutional repository, and for our digitized 
collection materials from Special Collections. For that latter set of material, 
occasionally, we need to wholly replace a bitstream -- versioning isn't 
appropriate. When we go in, and try to delete more than one bitstream (by 
clicking on the trashcan icon for the selected bitstreams, and then hitting the 
save button), one of the bitstreams is deleted -- but the other ones selected 
for deletion become locked (previously they were publicly available.) No one 
can delete them, and trying to access them prompts users to log in, but 
eventually results in a 404 page, even though the bitstream is still present, 
and the bitstream access policies all suggest that it's functioning normally.

It's pretty rare for us to delete bitstreams entirely, which is why we're just 
discovering this now, 7 months into running DSpace 7.4. But I'd still like to 
get it sorted out, especially because it's making a couple of items in our 
production instance inaccurate.

Has anyone else encountered anything like this? Thanks in advance--

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
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%3D2%2BohO%3D-djtPpWsDE7B7oyA4ZG2Qd9iTTWY6Zonxt2nQ%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/PH0PR22MB3274320C32B332D23BE4AEECED4EA%40PH0PR22MB3274.namprd22.prod.outlook.com.

Re: [dspace-tech] Migration Help from 6.3 to 7.5

['Tim Donohue' via DSpace Technical Support]

Hi Michel,

We have a guide for migrating data at 
https://wiki.lyrasis.org/display/DSDOC7x/Migrating+DSpace+to+a+new+server

This should work even migrating data from an old 6.x instance to a new 7.x one.

Tim

From: dspace-tech@googlegroups.com  on behalf of 
Michel Montenegro 
Sent: Friday, June 2, 2023 10:17 AM
To: dspace-tech@googlegroups.com 
Subject: Re: [dspace-tech] Migration Help from 6.3 to 7.5

I will detail our case:
we have version 6.3 (All data) and 7.5 (Clean) running on different servers, we 
simply want to transfer only the data from version 6.3 to 7.5.

We don't understand how to do that even from the documentation you indicated 
(We had already seen it). What exactly do we need to do to export the data from 
6.3 to 7.5? (Assuming 7.5 is running, but it's a clean install and all the data 
we want is in 6.3)

Em sex., 2 de jun. de 2023 às 11:23, Mark H. Wood 
mailto:mwoodiu...@gmail.com>> escreveu:
On Thu, Jun 01, 2023 at 10:40:44PM -0300, Michel Montenegro wrote:
> Where can I find documentation that shows how to migrate from 6.3 to 7.5 or
> how we can migrate?
>
> All documentation I found was out of date or apparently incomplete.

The official upgrade documentation is at:

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

If that is incorrect or incomplete, please tell us about the specific
problem(s) you found.

--
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu

--
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/ZHn7eYw0me8tLAx1%40IUPUI.Edu.


--
Atenciosamente,
Michel Pinheiro Montenegro
- Bacharel em Sistema de Informação
- [Lato Sensu] Especialista em Engenharia de Sistemas
- [Stricto Sensu] Mestre em Ciência da Computação
- [Stricto Sensu] Doutorando em Ciência da Computação

E-mail/Gtalk: michel.montene...@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/CADOAx_jWiA6dkU7O0BSU7BNe0RBek33uCwf3znNXidcBiCZ_og%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/PH0PR22MB32747D132B7DB1209AAA13E4ED4EA%40PH0PR22MB3274.namprd22.prod.outlook.com.

Re: [dspace-tech] Re: dspace-7.5. angular-ui gives no response

['Tim Donohue' via DSpace Technical Support]

Hi Christiane,

Are you certain that localhost is resolving to 127.0.0.1?  Maybe you need to 
check your Hosts file?

Based on what you've shared, it sounds like your REST API is configured 
properly (yarn rest:test succeeds).  It also sounds like the UI is starting up 
on localhost:4000 without reporting any errors.

But, it's really odd that wget gives no response at all for a long time.  It's 
almost like it cannot "find" localhost at all, and then you hit a connection 
timeout.

I've never seen this issue before myself... but it almost sounds like you have 
a lower-level issue with resolving the connection.  It might not be an issue 
with DSpace at all.  If you are seeing no errors and no logs, maybe DSpace is 
"working" but your network connections are not?

You also could try to see if you could get it running at 127.0.0.1:4000 instead 
of localhost:4000.

Those are my best ideas right now, but maybe someone else on this list would 
have other brainstorms to share.

Tim

From: dspace-tech@googlegroups.com  on behalf of 
Christiane Baier 
Sent: Tuesday, May 23, 2023 2:06 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Re: dspace-7.5. angular-ui gives no response

Hi Tim,

Before I posted my problem here I tried everything as as outlined in 
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-FrontendInstallation
It is not working without pm2.

/dspace-ui-deploy$ node ./dist/server/main.js

Building production app config

Overriding app config with /dspace-ui-deploy/config/config.yml

Overriding app config with /dspace-ui-deploy/config/config.prod.yml

Angular config.json file generated correctly at 
/dspace-ui-deploy/dist/browser/assets/config.json


Environment extended with app config


dspace-angular

Version: 7.5.0

Environment: Production


[HPM] Proxy created: /  -> https:///server/sitemaps

[08:20:25 GMT+0200 (Mitteleuropäische Sommerzeit)] Listening at 
http://localhost:4000/

If I do:

wget -v http://localhost:4000

--2023-05-23 08:33:09--  http://localhost:4000/

Auflösen des Hostnamens localhost (localhost) … ::1, 127.0.0.1

Verbindungsaufbau zu localhost (localhost)|::1|:4000 … fehlgeschlagen: 
Verbindungsaufbau abgelehnt.

Verbindungsaufbau zu localhost (localhost)|127.0.0.1|:4000 … verbunden.

HTTP-Anforderung gesendet, auf Antwort wird gewartet …

Then nothing happens. And I mean nothing. I can see the connection in netstat
tcp0  0 localhost:4000  localhost:46794 VERBUNDEN   
dspace 784425 44998/node

And I don't get an answer where I started wget. And I am patient. After more 
then 15 minutes I get

GET / - - ms - -

on the console where I started node
an other 15 minutes:

Lesefehler (Die Wartezeit für die Verbindung ist abgelaufen) beim Vorspann 
(header).

Erneuter Versuch.


--2023-05-23 08:48:10--  (Versuch: 2)  http://localhost:4000/

Verbindungsaufbau zu localhost (localhost)|127.0.0.1|:4000 … verbunden.

HTTP-Anforderung gesendet, auf Antwort wird gewartet …

It starts a third try, before it gives up.
And no clue what is wrong. I did the test:

dspace-angular$ yarn test:rest

yarn run v1.22.19

$ ts-node --project ./tsconfig.ts-node.json scripts/test-rest.ts

Building production app config

Overriding app config with /home/dspace/dspace-angular/config/config.yml

Overriding app config with /home/dspace/dspace-angular/config/config.prod.yml

...Testing connection to REST API at https:///server/api...


RESPONSE: 200 200


Checking JSON returned for validity...

"dspaceVersion" = DSpace 7.5

"dspaceUI" = https://

"dspaceServer" = https:///server

"dspaceServer" property matches UI's "rest" config? true

Does "/api" endpoint have HAL links ("_links" section)? true

Done in 5.38s.

In the Apache Config I included
ProxyPass / http://localhost:4000/
ProxyPassReverse / http://localhost:4000/

I can't do more then doing exactly what is written in the installation  
instructions. So what is wrong?

Kind Regards
Christiane

DSpace Technical Support schrieb am Mittwoch, 17. Mai 2023 um 21:12:32 UTC+2:
Hi Christiane,

Those warnings when running "yarn install" are normal behavior.  They can be 
ignored. They are not causing any issues.

As I mentioned previously, you might want to try starting up the UI *without* 
PM2, just to verify it's working properly standalone & trying to access it on 
the same machine that is is running on using http://localhost:4000/.  If it 
works standalone, then something in your PM2 configuration is the problem.  If 
it doesn't work standalone, then it might give you more useful errors to work 
with.   As I mentioned, this is documented in step 6 of the Installation for 
the UI (called the "Quick Start"): 
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-FrontendInstallation

My best guess is that either the UI is having trouble contacting the backend... 
or something in your proxy configuration (in either PM2 or Apache) is incorrect 

[dspace-tech] Re: Logs overwriting

['Tim Donohue' via DSpace Technical Support]

Hi Ed,

Yikes, that doesn't sound fun.  I don't have any great advice on this one 
other than to perhaps search Stackoverflow.com for similar issues (or even 
Google).  Maybe you'll find clues there which can help determine what has 
gone wrong.  My best guess is your log4j2 configuration has somehow 
confused log4j, but that's a guess.  I've not seen or heard of this sort of 
problem with out-of-the-box DSpace.

For example, here's one similar report on 
StackOverflow: 
https://stackoverflow.com/questions/52772933/log4j2-rolling-file-overwrites-existing-log
  
(I googled "log4j2 log overwrite")

Tim

On Tuesday, May 9, 2023 at 11:36:39 AM UTC-5 ed@colostate.edu wrote:

> Hi folks,
>
> This feels more like a "we did something weird" than a DSpace-specific 
> question, but we're trying to bring 7.5 up for production and recently the 
> logs started getting overwritten during rotation, i.e. dspace.log is 
> chugging along all day fine, but when we check the next day the 
> dspace.log-2023-05-02 style log has a smattering of entries from around the 
> time of rotation (midnight, 1 am or so) and that's it, the previous days 
> entries are all gone. Nothing was changed in the log4j2 configs when this 
> started happening, and we're trying to roll back changes piecemeal to see 
> what may have caused it but so far no joy.
>
> Does anybody with more Java/Tomcat/Log4J2 experience have any pointers on 
> "That happened to me once..." or "that sounds like..."? Not hoping for 
> specific fixes, but if anybody has even seen something like this I'd be 
> grateful because I've also been striking out on Google.
>
> Many thanks,
>
> Ed Hill 
>
> *Pronouns: He/Him*  (pronoun statement ) 
>
> Developer and Applications Administrator 
>
> *(970) 491-3197 <(970)%20491-3197>* 
>
> *Colorado State University Libraries *
>
>  
>
>

-- 
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/2aa937e6-3c68-4282-b16b-a7b2e37c2040n%40googlegroups.com.

Re: [dspace-tech] Attention Tim Donahue

['Tim Donohue' via DSpace Technical Support]

Hi Yvonna,

DSpace doesn't have a hosting program or technical support staff.  DSpace is an 
open-source program which is built and maintained by our worldwide community of 
users.  That means there is no centralized development or technical team. I 
have no developers who work for me.  My role is to help to coordinate with 
developers at institutions around the world who want to help add 
features/improvements to DSpace, etc.

That said, we have a very helpful and kind community on these mailing lists.  
So, you are welcome to use these mailing lists to ask questions and someone on 
this list will do their best to answer.  DSpace also has other free support 
options available at https://wiki.lyrasis.org/display/DSPACE/Support

If you'd rather hire someone or pay for support, DSpace has a large network of 
trusted service providers located around the world.  These service providers 
are for-profit institutions who have developers on staff who specialize in 
DSpace.  They also all give back to DSpace (either through funding or 
development hours, or both).  You can contact one (or more) of them to receive 
a quote for their services. They are all listed on the DSpace website at 
https://dspace.lyrasis.org/rsp/

Tim

From: dspace-tech@googlegroups.com  on behalf of 
Mandee Charl 
Sent: Tuesday, May 9, 2023 2:34 PM
To: dspace-tech@googlegroups.com 
Subject: [dspace-tech] Attention Tim Donahue

Good day Tim

Thank you for your email...

In addition to what you answered, our library is having some difficulties in 
installing the DSpace and would like to find out if our IT department can get 
some technical support in also transferring the data. Can you say if there is a 
fee attached to this.

If possible we would like to get in touch with the DSpace administrator (s) via 
email...  We do have our own hosting space for the program.

Awaiting your response.

Regards

Yvonna Mandy Charles
Hunter J Francois Library
Sir Arthur Lewis Community College
Castries, St. Lucia
West Indies (Caribbean)

[https://s-install.avcdn.net/ipm/preview/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif]
  
Virus-free.www.avast.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/CADv0RP_c%3DoTUWoU2d5xGXEmj_agX8a4e5LJ3RTz_19k4JT57oA%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/PH0PR22MB327401A92FEC4DAF36648B70ED769%40PH0PR22MB3274.namprd22.prod.outlook.com.

[dspace-tech] Re: Cloud Base

['Tim Donohue' via DSpace Technical Support]

Hi,

DSpace is open source software which you can choose to install locally or 
in the cloud.  If you are looking for a hosting provider to install DSpace 
for you, then you would want to contact one of our registered service 
providers.  These service providers can provide hosting services (for a fee 
obviously) of DSpace. You would want to get in touch with them for a quote.

https://dspace.lyrasis.org/rsp/

In terms of "free" hosting, that's only possible if you host it yourself.  
DSpace can be installed in the cloud though, and there are institutions who 
install it themselves on Amazon Web Services or other cloud providers.

Tim

On Thursday, May 4, 2023 at 10:49:23 AM UTC-5 graduate...@gmail.com wrote:

> Good morning 
>
> Our library is planning to make the transition from Greenstone to Dspace..
> but we wanted to find out if 
>
> 1. DSpace is cloudbased (hosting)
>
> Regards
>
> Mandy Charles
>
>
>
>
>
>
> 
>  
> Virus-free.www.avast.com 
> 
>  
> <#m_-5255310240428115909_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>

-- 
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/67371e81-4fd8-47fb-9c7e-330863295689n%40googlegroups.com.

Re: [dspace-tech] Curations in workflow in DSpace 7.5

['Tim Donohue' via DSpace Technical Support]

Have you made sure to turn on the Workflow process for that Collection?

In other words, I'm pretty sure these Curation tasks wired into the workflow 
will only trigger​ if the Collection has at least one workflow step enabled.  
If there are no workflow steps, then newly submitted Item will bypass the 
workflow process altogether and go immediately into the archive.

It's possible that what you are really wanting is the ability to run a curation 
task during the submission​ process (as that way it will trigger whether you 
have a workflow setup or not).  Unfortunately though that feature doesn't work 
yet in 7.x, but it is under development as noted here: 
https://github.com/DSpace/DSpace/issues/2868  (I suspect it may be completed in 
time for 7.6, but cannot verify yet.)

Tim

From: dspace-tech@googlegroups.com  on behalf of 
do...@uoguelph.ca 
Sent: Tuesday, May 2, 2023 10:06 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Curations in workflow in DSpace 7.5

Hello again everyone,

I have written a custom curation task and I'm really struggling to wire it up 
to run as part of a submission workflow. No matter what I try, I can't see any 
indication that it's even trying to run my task at all. There's nothing about 
it in dspace.log at all and the item seems unaffected.

My curation task runs properly when you execute it via the command line or 
through the curation web interface.

Here's a GitHub gist with the relevant configuration that I'm using: 
https://gist.github.com/doana/1dc9fdb53b6fdaf92f23fdac69202f6e

What I've tried so far:

  *   Read configurable workflow docs: 
https://wiki.lyrasis.org/display/DSDOC7x/Configurable+Workflow
  *   Read curation system docs: 
https://wiki.lyrasis.org/display/DSDOC7x/Curation+System#CurationSystem-Inworkflow
  *   Created the configuration as described in the gist above
  *   Rebuilt DSpace and restarted tomcat
  *   In workflow-curation.xml, I've also tried different flowstep values other 
than "archive"
 *   step1
 *   editstep
 *   reviewstep
  *   In workflow-curation.xml I've tried specifying 
rejectas well, despite the fact that I don't really want 
it to reject the item.
  *   In submission-curation.cfg I've tried using the FileReporter instead of 
the LogReporter

When executing my curation task through the CLI or web interface, I can see in 
dspace.log that it is working, and can see that it updates the item metadata 
accordingly.

I've also seen that there are a few issues on GitHub around curation but most 
seem centred around the vscan task and I haven't been able to glean much useful 
info from them. Notably after reading 
#2868 I'm not even 100% clear 
that this is supported at all in DSpace 7 yet.

Can anyone shed any light on this or offer any suggestions?

Thanks!
-Adam





--
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/eee64eb4-e618-4410-91a6-44acc7b28796n%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/PH0PR22MB3274C6BF05CB615D018074A6ED6F9%40PH0PR22MB3274.namprd22.prod.outlook.com.

[dspace-tech] Re: DSpace log warning - We have a collection or community admin with ID without any administrable collection or community!

['Tim Donohue' via DSpace Technical Support]

Hi Adam,

It's a "Warning" which means it's not something severe or serious... but it 
is something to be aware of.

Generally, that warning is saying that your Solr index is possibly 
outdated.  It's saying the user you are logged in as (identified by that 
UUID) is listed in Solr as being a Community or Collection Administrator... 
but DSpace couldn't locate any Community or Collection that they have Admin 
rights in.  This generally means that it's possible your database and Solr 
index are out of sync (you could try a reindex).

This is a new warning in DSpace 7 though... so it's also possible that it's 
inaccurately displayed at times.  The intention of the warning is to let 
you know that the user with that UUID doesn't seem to be able to Administer 
any collections/communities, even though Solr thinks they can.

Not sure if that's helpful, but here's where it triggers in the 
code: 
https://github.com/DSpace/DSpace/blob/main/dspace-api/src/main/java/org/dspace/discovery/SolrServiceImpl.java#L649

Tim
On Wednesday, April 26, 2023 at 9:07:13 AM UTC-5 do...@uoguelph.ca wrote:

> Hello all, 
>
> We're in the process of migrating to DSpace 7.5 and I've come across a 
> warning that frequently show up in our logs: 
>
> org.dspace.discovery.SolrServiceImpl @ We have a collection or community 
> admin with ID: c618e248-39f4-4696-8ba5-a5e2e28d6707 without any 
> administrable collection or community!
>
> This happens whenever I'm logged in as a non-admin user, even a brand new 
> user that has no group memberships at all. The UUID in the error is the id 
> of whatever user I'm logged in as. Each interaction with the angular UI 
> generates this warning multiple (10+) times. My questions for you fine 
> folks: 
>
>1. Is this actually an issue?
>2. Why is it happening? 
>3. Is it an indication that our permissions structure is messed up in 
>some way?
>
> Thanks! Any help you can provide would be greatly appreciated!
> -Adam
>

-- 
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/99f4e02d-ed78-499f-8199-587b4b443f8en%40googlegroups.com.

[dspace-tech] Re: Personalization of dspace

['Tim Donohue' via DSpace Technical Support]

Hi,

We have documentation on how to customize DSpace via a custom theme 
at https://wiki.lyrasis.org/display/DSDOC7x/User+Interface+Customization

Tim

On Tuesday, April 25, 2023 at 3:20:52 PM UTC-5 alex...@gmail.com wrote:

> Hi, i have a question..
>
> Did you know, how to change the main image in dspace home page?
>
> how to substitute the drops image 
>
> Thanks 
> [image: Captura.JPG]
>
>
>

-- 
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/f92ccc56-8705-44d4-8683-6e0eac31e96bn%40googlegroups.com.

[dspace-tech] Re: show the total items by communities on the home page

['Tim Donohue' via DSpace Technical Support]

Hi,

That feature doesn't exist yet in DSpace 7.  (It did exist in DSpace 6 and 
was called "item counts").  It is under development for the new DSpace UI 
in this ticket: https://github.com/DSpace/dspace-angular/issues/1787

It's unclear at this time when the work will be completed, as the current 
developers are working as volunteers.  But, as soon as the feature is 
ready, we'll work to get it into the next version of DSpace.

Tim

On Tuesday, April 25, 2023 at 3:08:45 PM UTC-5 jorge@udb.edu.sv wrote:

> hello
>
> On my dspace home page I wanted to know if it is possible and how to show 
> the total number of items belonging to each community right in the list 
> that is on the home page, which in my case looks like this:
> [image: Captura de pantalla 2023-04-25 140827.png]
>
> so is it possible? , as ? , Thanks in advance for the help
>

-- 
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/914e39da-759a-4f86-b735-63ca2126351an%40googlegroups.com.

[dspace-tech] Re: Filter by [A-Z] and [0-9] in Dspace 7.5

['Tim Donohue' via DSpace Technical Support]

Hi, 

That filter option does not exist in DSpace 7 at this time.   However, it's 
possible to achieve the same behavior in DSpace 7, by just typing the 
single letter in the textbox and clicking "Browse".  So, to filter by "T", 
just type "T" in that textbox and click the button.

Tim

On Tuesday, April 25, 2023 at 5:35:47 AM UTC-5 jrojo@gmail.com wrote:

> Good morning,
>
> Could anyone help me know how to activate this functionality so that it 
> can be filtered by letters of the alphabet (A-Z) and numbers (0-9)? 
>
> This is a screenshot from Dspace 5.6. I need to activate/configure it in 
> Dspace 7.5, since it does not appear by default. 
>
> Thank you very much and best regards.
>
> *Dspace 5.6:*
>
> [image: 5.6.png]
>
> *Dspace 7.5:*
>
> [image: 7.5.png]
>

-- 
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/dad9ee7c-4b42-4ed7-b95d-81e57f00e770n%40googlegroups.com.

[dspace-tech] Re: LDAP Active directory

['Tim Donohue' via DSpace Technical Support]

Hi,

DSpace doesn't maintain instructions specific to every operating system or 
local setup.  However, we do have LDAP configuration instructions in our 
documentation at
https://wiki.lyrasis.org/display/DSDOC7x/Authentication+Plugins#AuthenticationPlugins-LDAPAuthentication

There's also a section for "Debugging LDAP connection and configuration" 
which is handy.  Every LDAP / Active Directory setup is slightly different, 
so you will need to test what works for you.

Tim



On Sunday, April 23, 2023 at 11:32:59 PM UTC-5 m.kussai...@gmail.com wrote:

> Hello dear Dspace community!  I would be grateful if you could help with 
> the difficulties I am having.
> Could you suggest step by step how to enable authorization through Active 
> Directory?
> Dspace 7.4 installed in Ubuntu server.
> Active directory in Windows server.
> How to authorize university employees in Dspace via Active directory?
> Where to put the necessary data from Active Directory in Dspace? Be so 
> kind as to describe the step of action in as much detail as possible.
> I would appreciate your help in this matter.
> Thank you very much.
> Yours sincerely, Mukhametali.
>
>

-- 
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/5292e8db-247e-4413-9bec-7f4649853fc5n%40googlegroups.com.

[dspace-tech] Re: Dspace 7.4 erreur 500

['Tim Donohue' via DSpace Technical Support]

Hi,

A 500 exception is a general error that just means "something went wrong".  
To find the cause of the error, you need to locate the underlying error 
message (either in the User Interface or in the backend logs) by following 
our Troubleshooting 
guide:  
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Tim

On Sunday, April 23, 2023 at 10:34:22 AM UTC-5 mustapha...@enp-oran.dz 
wrote:

> Bonjour a tous,
>
> J’ai réussit a  installez Dspace 7.4 REST API sur une serveur dédié marche 
> sur Debian 11 , avec les packages nécessaires :( Java 17.0.6 / Maven 3.8.7 
> / Postgres 15 /Tomcat9 / Solr 8.11.2 )
>
> Et ca marche très bien lorsque j’accède depuis le navigateur sur : 
> http://@ip:8080 et : http://@ip:8080/server
>
> Puis j’ai installez dspace UI avec la configuration necessaires (Node JS 
> 16 , YARN et PM2)
>
> Et j’ai installer le serveur web apache pour l’utiliser comme reverse 
> proxy pour Tomcat comme ceci :
>
>  
>
> ServerName @ip du serveur
>
> ProxyRequests On
>
> ProxyPass / http://localhost:4000/
>
> ProxyPassReverse / http:// localhost:4000/
>
> 
>
>  
>
>  Mais le problème lorsque je lance le site sur le lien : http://@ip la 
> page initial du demo site s’affiche une instant puis l’erreur 500 m’affiche
>
> Est ce que vous pouvait m’aidez a résoudre ce problème.
>
> [image: Dspace _error_500.PNG]
>
> Cordialement
>
> Mr Mustapha DEHARIB
>

-- 
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/644aa72b-d2e1-4c22-a708-b452867249f8n%40googlegroups.com.

[dspace-tech] Re: Hiding item metadata fields

['Tim Donohue' via DSpace Technical Support]

Hi Deborah,

At this time, the behavior is the same in DSpace 7 as in DSpace 5.  The 
"metadata.hide" settings will hide the metadata field from everyone except 
full Administrators.  See the docs 
at 
https://wiki.lyrasis.org/display/DSDOC7x/Configuration+Reference#ConfigurationReference-HidingMetadata

There have been some occasional discussions of setting permissions on 
metadata fields...but that has no immediate plans because it's rather 
complex.

Tim

On Monday, April 17, 2023 at 5:59:42 PM UTC-5 deborah@lincoln.ac.nz 
wrote:

> Kia ora,
>
>  
>
> In DSpace 5.x we can edit the config file to specify certain metadata 
> fields that can only be viewed by an Administrator, eg
>
> metadata.hide.dc.description.provenance = true
>
>  
>
> We’ve belatedly realised that this means literally in the Administrator 
> group – ie if someone’s instead in a group with community/collection admin 
> rights, they still can’t see this metadata.
>
>  
>
> Is there any chance (wishful thinking…) that there’s a way in DSpace 7.x 
> to specify metadata fields that can be seen by collection administrators 
> while remaining hidden to the public?
>
>  
>
> Deborah
>
> ––
>
> *Deborah Fitchett* (she/her) MLIS, RLIANZA
>
> Associate University Librarian, Digital Scholarship
>
>  
>
> ––
>
> *Learning, Teaching and Library – Te Whare Pūrākau*
>
> PO Box 85064, Lincoln University
>
> Lincoln 7647, Christchurch, New Zealand
>
> +64 3 423 0358 <+64%203%20423%200358>
>
> deborah@lincoln.ac.nz 
>
> ltl.lincoln.ac.nz
>
>  
>
> ––
>
> *Lincoln University*
>
> Te Whare Wānaka o Aoraki
>
> ––
>
>  
>
> --
>
> "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/74b3faf2-648b-4887-8370-8793b7f52156n%40googlegroups.com.

Re: [dspace-tech] find item by rest api

['Tim Donohue' via DSpace Technical Support]

Hi,

You can use the /api/discover/search endpoint to search items (or any object) 
via metadata fields.  The full docs for that endpoint are at 
https://github.com/DSpace/RestContract/blob/main/search-endpoint.md

The easiest way to test queries though is via the new User Interface.  You can 
see every REST API call made from the User Interface from your browser's 
DevTools (Network tab).  We have a guide for how to do advanced searches from 
the User Interface...and all these searches are possible via the REST API. 
https://wiki.lyrasis.org/display/DSDOC7x/Search+-+Advanced

If you have more questions, let us know on this list.
Tim

From: dspace-tech@googlegroups.com  on behalf of 
Alfred Anders 
Sent: Friday, April 21, 2023 6:56 AM
To: DSpace Technical Support 
Subject: [dspace-tech] find item by rest api

I am in the process of migrating a large repo to dspace 7.5 (or later) via the 
rest api.
To find out, whether to use POST or PUT operations, I need to find out, if I do 
a new import
or re-import.

In solr, I  can find the status with a search like 
dc.identifier.other:"one/two/three", since I put the identifier of the original 
repo to that field.

Is there a way to do this with the DSpace REST API ?

Thanks for any hints,
  Alfred

--
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/cc304dad-bb0c-40dd-9f21-9afb4eea926en%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/PH0PR22MB3274D84EF369BDEC7FD1ED609%40PH0PR22MB3274.namprd22.prod.outlook.com.

Re: [dspace-tech] DSpace 7.5 Solr Statistics migration from 5.10 with sharding by year

['Tim Donohue' via DSpace Technical Support]

Thanks James & Tomas for sharing your hints/tips here!  It's obvious we 
didn't document this very well in the DSpace 7 Upgrade process.  Just now, 
I've done my best to summarize your advice & add more hints in Step 10(a) 
of the Upgrade process to help others along. I even linked folks back to 
this useful dspace-tech thread for more details.

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

If others have hints/tips to share, please do feel free to continue this 
thread, or add comments to the docs & we'll get them taken into account.

Tim

On Thursday, April 13, 2023 at 1:54:47 PM UTC-5 ha...@oakland.edu wrote:

> Thanks for the information.  I had similar information sent to me by 
> another person on the list so it seems we are all approaching this about 
> the same way.  I think I have my statistics imported at this point.  
> To rename the statistics files I wound up using the following one liner: 
> cd /opt/dspace/solr-export; for i in $(ls *.csv); do nf=$(echo $i | sed 
> 's/-20[1-2][0-9]_e/_e/g'); mv -v $i $nf; done
>
> Another suggestion was to use rename (e.g. rename 
> "s/-2015_export/_export/g"  *) but for whatever reason that was not 
> working for me on my RHEL 8.7 server.
> After renaming the files and running /opt/dspace/bin/dspace 
> solr-import-statistics -i statistics it looks like I have the statistics 
> imported.
>
> Thanks for the help.
> -Tomas
>
> On Tue, Apr 4, 2023 at 11:25 AM James Holobetz  wrote:
>
>> Hi Tomas,
>>
>> I recently had this issue and I believe that I have found a solution, 
>> which I will document in the next few days. The long and the short of it is 
>> that DSpace 7 does not support solr shards. You have to create one large 
>> solr shard (statistics) from the multiple shards. The biggest problem I 
>> found doing this was that DSpace was only ingesting the current year 
>> statistics only. The solution was to rename the *csv files that are 
>> dumped by solr-export-statistics. For example: the csv files for the solr 
>> core 
>> "statistics-2012" will look something like this -- 
>> statistics-2012_export_2013-12_5.csv. 
>> You have to rename all the csv files to remove the -2012 in the filename to 
>> look like this: statistics_export_2013-12_5.csv. I downloaded the zipped up 
>> cores in csv form to my windows machine so I could use a bulk rename tool 
>> to remove the year suffix in each core. I then uploaded them to my linux 
>> box running DSpace and ingested each one using the solr-import-statistics 
>> tool. 
>> This is a very time consuming task.
>>
>> Hope this helps and I will try to document this in the next few days.
>>
>> Best regards,
>>
>> James Holobetz
>>
>> On Fri, Mar 24, 2023 at 3:37 PM Tomas Hajek  wrote:
>>
>>> Hello, 
>>>I am working on migrating a DSpace 5.10 installation to a new server 
>>> running DSpace 7.5.  I have the basic installation running on RHEL 8.7 with 
>>> Tomcat 9.0.71, Solr 8.11.2, node.js 16.18.1, and pm2 5.2.2.  
>>> I was able to import the database and assetstore and I set up the Solr 
>>> cores (authority,oai,search,statistics) from the installation instructions.
>>>The Solr statistics from the 5.10 installation are sharded by year 
>>> and I exported with the following:
>>>
>>> bin/dspace solr-export-statistics -i statistics-2015
>>> bin/dspace solr-export-statistics -i statistics-2016
>>> ...
>>> bin/dspace solr-export-statistics -i statistics-2022
>>>
>>> I have copied the exported files to the new 7.5 server 
>>> into /opt/dspace/solr-export and am trying to import them but I get the 
>>> following error (example when trying to import the 2015 statistics):
>>>
>>> /opt/dspace/bin/dspace solr-import-statistics -i statistics-2015
>>> Exception: Error from server at 
>>> http://localhost:8983/solr/statistics-2015: Expected mime type 
>>> application/octet-stream but got text/html. 
>>> 
>>> 
>>> Error 404 Not Found
>>> 
>>> HTTP ERROR 404 Not Found
>>> 
>>> URI:/solr/statistics-2015/admin/luke
>>> STATUS:404
>>> MESSAGE:Not Found
>>> SERVLET:default
>>> 
>>>
>>> 
>>> 
>>>
>>> org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: 
>>> Error from server at http://localhost:8983/solr/statistics-2015: 
>>> Expected mime type application/octet-stream but got text/html. 
>>> 
>>> 
>>> Error 404 Not Found
>>> 
>>> HTTP ERROR 404 Not Found
>>> 
>>> URI:/solr/statistics-2015/admin/luke
>>> STATUS:404
>>> MESSAGE:Not Found
>>> SERVLET:default
>>> 
>>>
>>> 
>>> 
>>>
>>> at 
>>> org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:635)
>>> at 
>>> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:266)
>>> at 
>>> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:248)
>>> at org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:214)
>>> at org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:231)
>>> at 
>>> 

[dspace-tech] Re: Angular "dspace-ui-deploy" directory large "core.*" files

['Tim Donohue' via DSpace Technical Support]

Hi,

Those "core.*" files are not being created by DSpace.   DSpace never 
writes/creates new files to that folder once it is running.

It's likely those are memory dumps created by Linux.  It sounds like some 
process (maybe Node.js, or whatever else you are using the run the DSpace 
UI?) is running out of memory and/or crashing frequently. That is likely 
what is creating these "core.*" files.  See this StackOverflow for 
example: https://stackoverflow.com/a/20530587/3750035

Tim

On Thursday, April 13, 2023 at 1:01:26 PM UTC-5 bwe...@gmail.com wrote:

> Forgot I'm using dspace-angular 7.5
>
> On Thursday, April 13, 2023 at 12:59:38 PM UTC-5 hb wooley wrote:
>
>> Hoping someone can help.
>> Under the Angular "dspace-ui-deploy" directory where you copy the Angular 
>> "dist" folder, I'm seeing large core.* files. These (binary) files keep 
>> growing in this directory, can someone tell me what these files are for and 
>> can the number of them be limited, since they can fill up a drive if not 
>> monitored?
>> Example:
>> 2.3G Mar 24 15:28 core.18471
>> 2.3G Mar 25 00:58 core.23446
>> 2.3G Mar 25 21:18 core.10618
>> 2.3G Mar 26 22:59 core.3294
>> 2.3G Mar 28 01:15 core.19507
>> 2.3G Mar 28 12:49 core.16889
>> 2.4G Mar 30 12:30 core.3287
>> 2.3G Apr  1 00:25 core.4652
>> 2.3G Apr  3 14:10 core.7601
>> 2.3G Apr  5 00:59 core.28903
>> 2.3G Apr  5 19:18 core.12439
>> 2.3G Apr  7 09:17 core.9281
>> 2.3G Apr  8 00:19 core.6379
>> 2.3G Apr  8 00:49 core.7008
>> 2.3G Apr  8 12:25 core.18488
>> 2.3G Apr  9 12:23 core.32223
>> 2.3G Apr 10 12:23 core.1507
>> 2.3G Apr 11 20:29 core.3029
>> 2.3G Apr 13 12:22 core.6437
>>
>> 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/9ce2884d-2ff8-430c-bf32-484b971dc20dn%40googlegroups.com.

[dspace-tech] Re: limited bitstream permission and Mirador

['Tim Donohue' via DSpace Technical Support]

Hi all,

This is a known issue.  Currently, Mirador in DSpace isn't able to view 
restricted content, as it cannot pass the authentication info properly back 
to DSpace: https://github.com/DSpace/dspace-angular/issues/1435

There's been ongoing work on this, but it has hit a number of complications 
(as it's not simple): https://github.com/DSpace/dspace-angular/pull/1436

I know Michael Spalti (who created that PR) has been interested in this for 
some time.  There are others who would also like to have this feature... 
it's just a matter of finding a solution that can work for everyone & that 
can be added to out-of-the-box DSpace.

So, basically, we don't have a solution yet here. But, I'm hopeful that 
someone will figure this out & share their approach (whether in code or in 
a specific configuration) so that we can make it available to everyone. If 
you'd like to help, you might get in touch via that PR by adding a comment 
or similar.

Tim



On Tuesday, April 11, 2023 at 2:12:34 AM UTC-5 Evelin Bányai wrote:

> Thanks. Apparently we have Mirador 3, we will try to figure out how the 
> authentication works for Mirador.
>
> Best regards,
> Evelin
>
> west...@umd.edu a következőt írta (2023. április 8., szombat, 17:09:57 
> UTC+2):
>
>> Which version of Mirador? Mirador 3 supports IIIf Authentication (
>> https://iiif.io/api/auth/1.0/), which seems like the way to do this. 
>> Caveat: we have not implemented this ourselves.
>>
>> Josh Westgard
>> University of Maryland College Park
>>
>> On Friday, April 7, 2023 at 6:07:13 PM UTC-4 Chris Clawson wrote:
>>
>>> I have been asked to do this as well. Does anybody know a method?
>>>
>>> On Monday, April 3, 2023 at 7:23:00 AM UTC-4 Evelin Bányai wrote:
>>>
 Hello,

 There are certain items we would like to have with withdrawn_read 
 bitstream permission so the users should ask for permission to download 
 the 
 full picture. However, if we setup up the item with such permission the 
 built-in Mirador viewer won't show anything.

 Is there a way to set up such configuration where the file download is 
 limited but the viewer able to show the image? I have my doubts, but it's 
 worth a try to ask.

 We have version 7.2.1.

 Thanks!
 Evelin

>>>

-- 
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/c6d4782f-8ccf-4d10-9a4d-55dbdffe949en%40googlegroups.com.

[dspace-tech] Re: Password complexity and max failures attempts

['Tim Donohue' via DSpace Technical Support]

Hi,

In DSpace 7, you can manage password complexity rules in a configuration.  
It's controlled by a regex pattern defined here:
https://github.com/DSpace/DSpace/blob/main/dspace/config/modules/authentication-password.cfg#L51

Some examples of different patterns are given in the comments of that 
config file.

At this time though there is no "maximum failure" attempt rules for the 
default password system.  I do agree this would be useful enhancement 
though... so, you are welcome to create a bug ticket regarding this & we'll 
see if we can locate a volunteer interested in implementing 
it. https://github.com/DSpace/DSpace/issues

Tim

On Thursday, April 6, 2023 at 6:20:27 AM UTC-5 Brandon Sauvenière 
(Brandysve) wrote:

> Hello,
>
> Is it possible to manage the password complexity when user create a 
> password? (ex : min 14 chars with uppercase, lowercase, numbers and special 
> chars). 
>
> It there a maximal failures attempts? We're planning to use dspace for our 
> target with +/- 15000 users. We want to be sure that it is safe against 
> attacks.
>
> It is external users so we don't use LDAP, shibboleth, etc...
>
> 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/0f0a2669-55c4-49cc-aee7-7a51e12be664n%40googlegroups.com.

[dspace-tech] Re: "Search query is not valid"

['Tim Donohue' via DSpace Technical Support]

Hi Bryan,

The colon is a reserved character in Solr (which the search engine uses).  
But you should be able to escape it by simply surrounding it with quotes.

So, if you search "My Title: my latest paper" (with the quotes!) that 
should work to search by the colon.  However, if you don't include the 
quotes, then a field-based search will try to run.  For more information on 
using search in DSpace 7, see the docs 
at https://wiki.lyrasis.org/display/DSDOC7x/Search+-+Advanced

Tim
 
On Monday, March 27, 2023 at 9:22:04 PM UTC-5 crims...@gmail.com wrote:

> Hi Team,
>
> We are running Dspace 7.3 and having an issue using ":" in search field. I 
> have done some search and edited solr and dspace configs but nothing seems 
> to work. I won't put them here to avoid confusion for now.
>
> Is there a way to allow colon (:) in the search field?
>
> Regards,
> Bryan
>

-- 
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/d9d38dfd-c2ca-4f2b-9582-e64df3484451n%40googlegroups.com.

[dspace-tech] Re: We can not apply Access Conditions in Dspace 7

['Tim Donohue' via DSpace Technical Support]

Hi,

If the screen is freezing, that is usually a sign of an error occurring 
behind the scenes.  I'd recommend using our Troubleshooting Guide to find 
the detailed error 
message: 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Once you find the detailed error, you can share it back on this list if you 
need more help.

Tim

On Thursday, March 23, 2023 at 6:22:12 AM UTC-5 zeyne...@gmail.com wrote:

> Please help on this subject!
> We upgraded to Dspace 7. After, we made editing on submission form. We 
> excluded the adinistrator option from default access conditions section. 
> Now we can not apply any access conditions type to sources. We see access 
> conditions section on the submission form, but don't apply. For example we 
> choose ambargo , and then date and send. Then, screen freezes, won't 
> progress. We also don't see access conditions section when any item files 
> editing. How we can solve this problem? Could you please share a 
> troubleshooting guide on this subject?
>
>

-- 
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/97f68ffa-9a6d-429c-90c7-47163ae309a4n%40googlegroups.com.

[dspace-tech] Re: Formulas in the "Abstract" field

['Tim Donohue' via DSpace Technical Support]

Hi,

In DSpace 6, IIRC, only the XMLUI "Mirage" and "Mirage2" themes supported 
MathJax to display mathematical 
formulas: 
https://wiki.lyrasis.org/display/DSDOC6x/XMLUI+Configuration+and+Customization#XMLUIConfigurationandCustomization-MathJaxSupport

In DSpace 7, MathJax is also supported, but is disabled by default. 
Enabling it is possible via a simple 
configuration: 
https://wiki.lyrasis.org/display/DSDOC7x/User+Interface+Configuration#UserInterfaceConfiguration-SettingsforrenderingMarkdown,HTMLandMathJaxinmetadata

Tim

On Thursday, March 23, 2023 at 12:18:20 PM UTC-5 bgvi...@unifei.edu.br 
wrote:

> Dear all, I have a question: 
> When registering a dissertation, in Dspace 6.2, is it possible to insert a 
> chemistry/mathematics formula, like the ones below, in the summary field?
>
> [image: Sem título.png]
>
> Thanks.
>
> Att.
>
> Benedito
>

-- 
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/9f0a84f0-57d1-4f76-91cc-cdec02fd15f5n%40googlegroups.com.

[dspace-tech] Re: DSpace 7 Impersonation and Special Groups

['Tim Donohue' via DSpace Technical Support]

Hi David,

I'd recommend logging a bug ticket with the steps to reproduce this issue 
in 7.x.   That way we can get this tracked in a ticket and I can look for 
volunteers to implement.  It sounds like this might be a bug if behavior 
has changed since 6.x, but it'd be useful to provide step-by-step details 
of what you are seeing vs what you are expecting.  Thanks!

https://github.com/DSpace/dspace-angular/issues

Tim

On Thursday, March 23, 2023 at 6:09:09 AM UTC-5 David P. Steelman wrote:

> In our DSpace 7.4 testing, it appears that the "Impersonate EPerson" 
> functionality ignores any "special groups" that are normally assigned to 
> the impersonated user as part of the authentication process.
>
> For example, we use the "org.dspace.authenticate.IPAuthentication" class 
> to assign a "special group" to users, based on their IP address. When an 
> administrator impersonates a user, the impersonated user is not assigned to 
> any special groups (the "switchContextUser" method in the 
> "org.dspace.core.Context" class simply resets the "special groups" to an 
> empty set for the impersonated user).
>
> This seems to affect all the authentication methods (any "special group" 
> handling they might have is not called when the impersonation is performed).
>
> In DSpace 6, impersonated users were assigned to "special groups" -- are 
> there any plans to restore this functionality or any suggestions about how 
> it might be done to provide a more accurate experience when impersonating 
> users?
>
> 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/85917a7b-03b3-4854-86ac-8a0b4b676018n%40googlegroups.com.

[dspace-tech] Re: New to DSpace

['Tim Donohue' via DSpace Technical Support]

Hi,

DSpace doesn't have any *.dll files at all.  So, it sounds like you may be 
hitting issues that are external from DSpace?  It's unclear, as these *.dll 
files are not provided with DSpace.

The DSpace Installation process can be found 
at https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace   If you can 
provide more details about which step failed for you, it might be possible 
for someone to more easily help you.

Tim

On Friday, March 24, 2023 at 6:25:47 AM UTC-5 graduate...@gmail.com wrote:

> Good day all, I our library was using Greenstone as its database but wants 
> to shift to Dspace. I tried downloading the software but it keeps giving 
> some error codes like (The code execution cannot proceed because 
> LOCWIN32.dll, and it keeps asking for different .dll files. example it will 
> ask for CLXwin32.dll and then CALWIN32.DLL and so on. My expertise lies in 
> database management, so I am not too tech-savvy. Can I get some assistance 
> in helping me get Dspace up and running?
>
>
>
> Best Regards
>
> Mandy Charles
> (Caribbean)
>
>
>
>

-- 
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/8fc8309b-3362-43be-8b8c-6fe772d6a578n%40googlegroups.com.

[dspace-tech] Re: URGENT issue index-discovery

['Tim Donohue' via DSpace Technical Support]

Hi,

It's very difficult for anyone to help you unless you locate the detailed 
error message.  It sounds like something must be failing in your indexing 
process. The detailed error is likely in either the dspace.log or Tomcat 
logs.  See the troubleshooting guide for more 
details: 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Once you find the detailed error, you can either share it here, or see if 
it's listed in the common installation 
issues: 
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues

Tim

On Wednesday, March 22, 2023 at 7:53:49 AM UTC-5 hbla...@gmail.com wrote:

> In dspace 7.4 after I do index-discovery, items in users worksapce 
> dissapear
>
> i found in database and item exist
> edocur=# select * from workspaceitem where item_id in (select uuid from 
> item where submitter_id = (select uuid from eperson where netid like 
> 'ivan.tamayo'));
>  workspace_item_id | multiple_titles | published_before | multiple_files | 
> stage_reached | page_reached |   item_id|   
>  collection_id
>
>
> ---+-+--++---+--+--+
> --
>  55211 | f   | f| f  | 
>-1 |   -1 | b397bef8-e6e4-4fa7-9dc7-01a0d4805696 | 
> 633f13b9-283d-4da4-ab65-1c0
> f0ad6d476
>
> and all metadata is in metadatavalue table.
>
> but in the user interface (mydspace?configuration=workspace) is empty.
>
> its like an error or lock in browse solr happends but i cant found the 
> error
>
> Help please
>

-- 
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/d278baac-daa3-4989-a7cc-b6695b607707n%40googlegroups.com.

Re: [dspace-tech] REST API "415 Unsupported Media Type"

['Tim Donohue' via DSpace Technical Support]

Hi,

Usually, a 415 error means you are sending data using an invalid "Content-Type" 
header.  In most scenarios the content-type should be either "application/json" 
or "application/json-patch+json" (for PATCH requests).

However, it's difficult to provide better advice without understanding which 
exact request is returning a 415.

Tim

From: dspace-tech@googlegroups.com  on behalf of 
Lewatle Johannes Phaladi 
Sent: Monday, March 27, 2023 8:44 AM
To: DSpace Technical Support 
Subject: [dspace-tech] REST API "415 Unsupported Media Type"

Hi DSpace Tech,

We are getting the following error "415 Unsupported Media Type" while trying to 
push items using Rest API to DSpace 7.4

Please advise on how to resolve the error.

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/9c91dacb-24e7-4445-b891-6f116d974ce3n%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/PH0PR22MB32740E11414C8E4EF4A5192BED8B9%40PH0PR22MB3274.namprd22.prod.outlook.com.

Re: [dspace-tech] Re: index-discovery error

['Tim Donohue' via DSpace Technical Support]

Hi Andrew,

Glad to hear you figured it out.

Regarding your other URL question, I just answered it in your other email 
thread: https://groups.google.com/g/dspace-tech/c/cLFoNivftB4/m/mjajzzydAAAJ

Tim

From: dspace-tech@googlegroups.com  on behalf of 
Andrew K 
Sent: Tuesday, March 21, 2023 2:53 PM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] Re: index-discovery error

Hi Tim,

Thanks a lot for your reply!

I exported the table workspaceitem and found no identical "item_id" numbers. 
Since I do not care about those old (partially) submitted items, I wanted to 
delete everything in the admin/workflow zone on the website, but somehow it's 
not possible for those old submissions.
So I just truncated the workspaceitem table in the database. And it worked! Now 
index-discovery goes smoothly. Yay!

Can I also ask you if it's possible to keep the old handle-type URLs in DSpace 
7 ?

Best regards,
Andrew

вт, 21 бер. 2023 р. о 18:34 'Tim Donohue' via DSpace Technical Support 
mailto:dspace-tech@googlegroups.com>> пише:

Hi,

Based on that error message, it sounds like you somehow have invalid data in 
your "workspaceitem" database table (this table is used to store information 
about in-progress submissions).  The error seems to be saying that you have two 
different entries in the "workspaceitem" table which reference the *same* 
"item_id".  That shouldn't be possible, as each WorkspaceItem should have a 
*unique* "item_id".

I'm not sure how that could have occurred. But if you can find the duplicate 
entry in "workspaceitem", then it should be possible to just remove one of the 
entries.  I'd recommend making a copy of the database before doing this, as 
it's possible there could be side effects that I'm not foreseeing.  Once that 
duplicate entry is removed though, I suspect the indexing will work properly.

Tim
On Monday, March 20, 2023 at 2:30:32 AM UTC-5 Andrew K wrote:
Hello!

I have a 7.5 server updated from 5.4.
The database update process finished OK.
But the index-discovery fails.

2023-03-20 09:24:03.611 INFO index-discovery - 4 @ The script has started 
2023-03-20 09:24:03.611 INFO index-discovery - 4 @ Updating Index 2023-03-20 
09:24:43.049 ERROR index-discovery - 4 @ null 2023-03-20 09:24:43.050 ERROR 
index-discovery - 4 @ java.lang.IllegalArgumentException: More than one result 
found at 
org.dspace.core.AbstractHibernateDAO.uniqueResult(AbstractHibernateDAO.java:242)
 at 
org.dspace.content.dao.impl.WorkspaceItemDAOImpl.findByItem(WorkspaceItemDAOImpl.java:81)
 at 
org.dspace.content.WorkspaceItemServiceImpl.findByItem(WorkspaceItemServiceImpl.java:243)
 at 
org.dspace.content.ItemServiceImpl.getParentObject(ItemServiceImpl.java:1408) 
at org.dspace.content.ItemServiceImpl.getParentObject(ItemServiceImpl.java:92) 
at 
org.dspace.discovery.SolrServiceResourceRestrictionPlugin.additionalIndex(SolrServiceResourceRestrictionPlugin.java:129)
 at 
org.dspace.discovery.indexobject.IndexFactoryImpl.buildDocument(IndexFactoryImpl.java:67)
 at 
org.dspace.discovery.indexobject.InprogressSubmissionIndexFactoryImpl.buildDocument(InprogressSubmissionIndexFactoryImpl.java:51)
 at 
org.dspace.discovery.indexobject.WorkspaceItemIndexFactoryImpl.buildDocument(WorkspaceItemIndexFactoryImpl.java:63)
 at 
org.dspace.discovery.indexobject.WorkspaceItemIndexFactoryImpl.buildDocument(WorkspaceItemIndexFactoryImpl.java:30)
 at org.dspace.discovery.SolrServiceImpl.update(SolrServiceImpl.java:169) at 
org.dspace.discovery.SolrServiceImpl.indexContent(SolrServiceImpl.java:159) at 
org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:344) at 
org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:331) at 
org.dspace.discovery.IndexClient.internalRun(IndexClient.java:130) at 
org.dspace.scripts.DSpaceRunnable.run(DSpaceRunnable.java:104) at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
 at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
 at java.base/java.lang.Thread.run(Thread.java:829)The database info
Database Type: postgres
Database URL: jdbc:postgresql://localhost:5432/dspace
Database Schema: public
Database Username: dspace
Database Software: PostgreSQL version 14.7 (Ubuntu 14.7-0ubuntu0.22.04.1)
Database Driver: PostgreSQL JDBC Driver version 42.4.3
PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.3)
FlywayDB Version: 8.4.4

+---++--+--+-+--+
| Category  | Version| Description  
| Type | Installed On| State|
+---++--+--+-

[dspace-tech] Re: Item URL in DSpace 7.5

['Tim Donohue' via DSpace Technical Support]

Hi Andrew,

DSpace 7 UI's URLs are not customizable.  However, all old-style 6.x 
Handles should redirect automatically in DSpace 7 to the new URL.  So, an 
old style URL like [dspace.ui.url]/handle/[prefix]/[suffix] should 
automatically redirect to a new style URL like [dspace.ui.url]/items/[uuid].

In other words, while DSpace's new URL structure cannot be customized, all 
old URLs will still work to provide backwards compatibility with 5.x/6.x.

Tim

On Saturday, March 18, 2023 at 12:00:34 PM UTC-5 Andrew K wrote:

> Hello!
>
> I just updated our DSpace 5.4 to 7.5 following the wiki.
> In the new version item URL in browser looks like 
> *website/items/e3fa1110-74f4-4f02-87d6-39f60763fe11*
> While in the old version we had *website/jspui/handle/123456789/12345*
>
> Is there any way to switch back to handle-type URLs?
>
> Thanks,
> 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/dc8acd58-e9d5-4d53-a044-9a7f2aebfda0n%40googlegroups.com.

[dspace-tech] Re: DSPACE7 - a public link for PDF download

['Tim Donohue' via DSpace Technical Support]

Hi Bill,

The DSpace 7 UI *must* redirect to the backend in order to perform the 
download. Otherwise, you'd need to "stream" the file to the UI first, then 
send it to the user.

So, the behavior you are seeing is correct... 

In the UI, the link will always appear like this: 
https://[dspace.ui.url]/bitstreams/[uuid-of-bitstream]/download

However, when a user clicks that link, they are redirected (by the UI) to 
download the file via the backend:
https://[dspace.server.url]/api/core/bitstreams/[uuid-of-bitstream]/content

Notice that the *first* URL will always be based on the "dspace.ui.url" 
setting (i.e. the URL of the UI), which is required for SEO/indexing 
purposes, etc.  However, it necessarily will redirect/send you to the 
"dspace.server.url" (i.e. the URL of the REST API) in order to download the 
file this is necessary for performance purposes, so the backend can 
"stream" the file directly to the user's browser.

Hopefully that clarifies things further.  But, let us know if it brings up 
more questions.

Tim

On Tuesday, March 21, 2023 at 1:54:10 PM UTC-5 tant...@umn.edu wrote:

> That's helpful, and the new style is actually more predictable, however, 
> in my instance when I click on a bitstream link I am redirected to a new 
> url that looks like a REST endpoint, for example
>
>
> https://xxx.xxx.xxx/server/api/core/bitstreams/12ea09a7-d9aa-4666-9a51-aef6358351a5/content
>
> It would be preferable to see the url as it appears to the client, for 
> example
>
>
> https://xxx.xxx.xxx/bitstreams/12ea09a7-d9aa-4666-9a51-aef6358351a5/download
>
> Any thoughts?
>
> On Monday, March 20, 2023 at 10:29:44 AM UTC-5 Tim Donohue wrote:
>
>> Hi Jan,
>>
>> DSpace 7 doesn't provide an option to have a Bitstream (File) download 
>> link based on an Item's assigned Handle.  Instead, download links *are* 
>> persistent and public, but are based on the UUID of the Bitstream/file like 
>> this:
>> https://[dspace.url]/bitstreams/[uuid-of-bitstream]/download
>>
>> That said, DSpace 7 does auto-redirect all older style 6.x URLs to the 
>> new location.  So, for example, in the DSpace 6.x XMLUI, file downloads 
>> used this URL structure:
>> https://[dspace.url]/bitstream/handle/[prefix]/[suffix]/[filename]
>>
>> Those older URLs will redirect automatically to the new URL style (shown 
>> above), in case that's helpful.
>>
>> Tim
>>
>> On Thursday, March 16, 2023 at 5:36:22 AM UTC-5 jan.b...@gmail.com wrote:
>>
>>> Any idea? We need a software solution to generate public links for PDF 
>>> downloads using only a given handle number.
>>> Thanks
>>>
>>> On Wednesday, March 8, 2023 at 8:55:06 AM UTC+1 Jan Broulím wrote:
>>>
 Hi,
 I would like to ask whether it is possible to generate a public link 
 for pdf download - e.g. based on handle number.
 Thank you
 Jan

>>>

-- 
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/c696f211-4c2d-4ede-a756-69a6866b10d1n%40googlegroups.com.

Re: [Extern] Re: [dspace-tech] Is it possible to update jQuery in xmlui in dspace 5?

['Tim Donohue' via DSpace Technical Support]

Hi all,

DSpace 6.4 included fixes to upgrade both the JSPUI and XMLUI to use jQuery 
3, see https://github.com/DSpace/DSpace/pull/2918

This work was never ported to DSpace 5.x (and 5.x is now end-of-life, so 
that port will never occur).  That said, it might be possible to manually 
port this in your local 5.x instance simply by making the same changes as 
were made in that PR. While the PR looks massive, it is mostly replacing 
the old jQuery files with the new ones & making some relatively minor 
updates to the DSpace code.

Another option is to consider upgrading to 6.4, or even to 7.x in the near 
future.

Tim

On Tuesday, March 21, 2023 at 10:54:24 AM UTC-5 Michael Plate wrote:

> Hi,
>
> Am 21.03.23 um 16:03 schrieb Mark H. Wood:
> > On Mon, Mar 20, 2023 at 12:02:35PM -0700, cpgr...@gmail.com wrote:
> >> We have been notified by campus network authorities that our dspace 
> server
> >> is vulnerable because it is running outdated versions of jQuery. We are 
> in
> >> the process of creating a new dspace 7 server to replace this server, 
> but
> >> that will not happen in the short time that we have been given to fix 
> this
> >> vulnerability.
> >>
> >> How can we quickly upgrade jQuery on our server? Where can I find
> >> instructions on updating the jQuery software in our xmlui in our 
> instance
> >> of dspace 5? Can our built process be modified to bring in more up to 
> date
> >> jQuery packages?
> >>
> >> EOL/Obsolete Software: jQuery 1.x and 2.x Detected
> >>
> >> -
> >> 
> >> EOL Software:jQuery Version 1.x or 2.x Detected.
> >> jquery/jquery-1.4.4.min.js
> > 
> > I don't know how much work is required to update to jQuery v3.
> > Updating across two major releases might break a number of things.
> […]
>
> ist seems to be we have the same problem; ours ist jQuery 1.10.2 (by 
> package.json) , and a good place to start seems to be scripts.xml in the 
> theme folder.
>
> Searched a bit and found this
>
> https://www.cvedetails.com/vulnerability-list/vendor_id-6538/Jquery.html
>
>
> and this
>
>
> https://www.computerminds.co.uk/articles/upgrading-jquery-1x-version-3x
>
> Presumably DSpace 6.x is affected to ?
>
> I'll try inspecting on our test-version tomorrow…
>
>

-- 
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/40d9e12f-e7c5-4a8c-8bc0-733ee597ecden%40googlegroups.com.

Re: [dspace-tech] Re: DSpace 7.5 intermittent errors with patch operations

['Tim Donohue' via DSpace Technical Support]

Hi Agustina,

Yes, if you are able to narrow down the issue to code within DSpace, please do 
submit a bug ticket (and possibly also a PR if you've found a fix).  I'm not 
familiar enough with all the DOI code in DSpace to comment further, but 
generally, it's best to report bugs back if you can narrow down the issue to 
DSpace code itself.

Thanks & glad to hear you've started to figure out what is going on.

Tim

From: dspace-tech@googlegroups.com  on behalf of 
Agustina Martinez 
Sent: Tuesday, March 21, 2023 10:55 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Re: DSpace 7.5 intermittent errors with patch operations

Hi Tim,

Many thanks for the hints. Yes, I can confirm now that the issue was completely 
unrelated to CORS. Unfortunately there were no errors at all in any of the 
backend logs regarding this other than a request timeout.

I have managed to track down the issue and it was quite a worrying one, which I 
am happy to share in case others experience similar issues and to also gather 
some advice from you in terms of appropriate fixes:

  *   The root of the issue was a locked DB transaction originating in a time 
consuming curation task that we were running over a large repository 
collection. This curation task iterates over collection items and modifies 
their metadata in certain conditions are matched. The curation task is run via 
the command-line "curate -t" command
  *   We have observed that until the curation task completes successfully all 
of the potentially affected items cannot be edited at all via the user 
interface and the error I reported above is the one that occurs. I.e. patch 
request from UI but request timeouts as there is the DB transaction locked. 
There is no useful message being reported at the DSpace level.
  *   The transaction lock took place when the event dispatcher queue kicks off 
after the curation task has finished iterating over the collection and before 
committing changes to the DB.
  *   The event consumer that was causing for the DB lock was the DOIConsumer, 
and I think that the root of the issue is the "ctx.commit" call in 
https://github.com/DSpace/DSpace/blob/b956bcd3891e372cc0fe5b1595e422e5d059bced/dspace-api/src/main/java/org/dspace/identifier/doi/DOIConsumer.java#L144.

Replacing that commit call with a "ctx.uncacheEntity(dso)" call seems to have 
resolved the DB transaction lock as our curation task now finishes successfully 
and all the events, including discovery indexing take place as expected, but 
wanted to check whether this is the appropriate way of doing it. It makes sense 
to not do a hard commit in the DOIConsumer in case the transaction does not 
finish successfully to be able to roll back but I would like advice here??

Tim, should I open a ticket and try to replicate this with a DSpace standard 
curation task running over a large collection? Your advice would be much 
appreciated.

Best,
Agustina

On Monday, 20 March 2023 at 17:55:12 UTC Tim Donohue wrote:
Hi Agustina,

If you are sure it's not a CORS policy error, then I'd recommend checking the 
backend logs.  That "500 (Internal Server Error)" might also be logged in 
dspace.log or tomcat logs. If so, there may be more information there to help 
out.   If it's reproducible semi-easily, you could also turn on "Debug mode for 
the REST API" per our troubleshooting guide: 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)
   (I wouldn't recommend leaving that on for a long time though, as allows full 
error stacktraces to be seen in every REST API response, which is really useful 
to debug issues...but also can be useful to hackers trying to find 
vulnerabilities in your system.)

Tim

On Friday, March 17, 2023 at 11:46:47 AM UTC-5 Agustina Martinez wrote:
Hi all,

We are experiencing intermittent errors, mostly affecting PATCH operations 
(e.g. modifying items metadata, editing a user or group), when there is heavy 
load in the backend.

We do not see any relevant errors in the backend logs at all, but after some 
timeout takes place I consistently see these two errors in the developer tools:

Access to XMLHttpRequest at 
'OUR-BACKEND-URL/server/api/core/items/421578b1-a644-4016-b3a0-c0afe904b0e8' 
from origin 'https://dspace7-f-dev.lib.cam.ac.uk' has been blocked by CORS 
policy: No 'Access-Control-Allow-Origin' header is present on the requested 
resource.
polyfills.1cded4d53dfa4781.js:1  PATCH 
OUR-BACKEND-URL/server/api/core/items/421578b1-a644-4016-b3a0-c0afe904b0e8 
net::ERR_FAILED 500 (Internal Server Error)

It is definitely not CORS related and that error is mis-leading.

Is anybody experiencing similar issues? So far I have not been able to 
reproduce in the DEMO DSpace site or in my local environment.

Best,
Agustina

--
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 

Re: [dspace-tech] DSpace 6.4 Mirage 2 theme

['Tim Donohue' via DSpace Technical Support]

Hi,

Documentation on modifying the Mirage 2 theme can be found in the DSpace 
6.x docs 
at 
https://wiki.lyrasis.org/display/DSDOC6x/Mirage+2+Configuration+and+Customization
(It's unclear what you mean by the "background picture" as there is no 
default background picture in the Mirage 2 theme's homepage or similar)

Please keep in mind that DSpace 6.x will enter "end of life" as of July 1 
of this year.  So, we recommend new installations start with DSpace 7.x 
instead of DSpace 6.x
https://wiki.lyrasis.org/display/DSPACE/Support+for+DSpace+5+and+6+is+ending+in+2023

DSpace 7 is available 
at https://wiki.lyrasis.org/display/DSDOC7x/Release+Notes

Tim

On Tuesday, March 21, 2023 at 6:50:29 AM UTC-5 project@gmail.com wrote:

> Can anybody help?
>
>
>
>
> On Thu, Mar 16, 2023 at 5:36 PM Arunendra MB  
> wrote:
>
>> Is it possible to change the background picture of Mirage 2 theme?
>> Using:
>> Windows 10 OS
>> Dspace 6.4
>>
>> -- 
>> 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 a topic in the 
>> Google Groups "DSpace Technical Support" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/dspace-tech/7WljY8hYc_Q/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> dspace-tech...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/dspace-tech/62fdd5e9-5bdd-488d-8a99-1b3576306467n%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/3a3cdb1a-6c38-4fc0-9a4f-56fb00666ce2n%40googlegroups.com.

[dspace-tech] Re: DSpace 7.5 migration from 6.3

['Tim Donohue' via DSpace Technical Support]

Hi Milos,

Yes, I'd recommend first starting from the default workflow/submission that 
comes with 7.5 just to ensure everything else is working properly.  Then, 
once you have everything working, you could try to migrate your old configs 
over (either manually or by using the provided migration scripts).

Tim

On Tuesday, March 21, 2023 at 5:40:14 AM UTC-5 imi...@gmail.com wrote:

> Dear Tim,
>
> Thank you for the guidelines. I will dig deeper and understand what is 
> going on.  Perhaps starting from the default workflow and submission form 
> is better than trying to employ the migrated XMLs. 
>
> Kind regards
> Milos
>
>
> понедељак, 20. март 2023. у 16:16:40 UTC+1 Tim Donohue је написао/ла:
>
>> Hi Milos,
>>
>> Unfortunately, the error messages displayed in the UI aren't enough 
>> information to debug the issue.  You'd need to locate the underlying 
>> exceptions behind those error messages, as those will provide more clues as 
>> to whether the problem is one of your configs or maybe something else with 
>> the installation.  We have a troubleshooting guide which walks you through 
>> finding underlying exceptions either in the UI or backend: 
>> https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)
>>
>> Once you locate the underlying exception, it's possible you'll find one 
>> of the common installation errors listed at 
>> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues
>>   
>> If not, and the error text doesn't make sense, you can send it to this list 
>> and hopefully someone here can provide more clues.
>>
>> Tim
>>
>> On Thursday, March 16, 2023 at 3:32:38 AM UTC-5 imi...@gmail.com wrote:
>>
>>> Dear Tim,
>>>
>>> Thank you for your quick response and explanation. It is good to know 
>>> the migration went well. 
>>>
>>> The next thing to look at is the item submission and workflow 
>>> configurations. According to the upgrade guide I did:
>>>
>>> [dspace]/bin/dspace submission-forms-migrate -s 
>>> [dspace]/config/temp/item-submission.xml -f 
>>> [dspace]/config/temp/input-forms.xml
>>>
>>> The "migrated" files are attached. If I leave the default workflow.xml, 
>>> in the UI I cannot submit a new item with the message "You have not the 
>>> privilege to make a new submission." Also, if an admin user goes to 
>>> "Administer workflow", the message "Error fetching search results" 
>>> appears. In 6.3 we used to have a simple "single reviewer" workflow and 
>>> admins for each collection (the old workflow-dspace63.xml is also 
>>> attached). As you can see, I am a little bit confused :)
>>>
>>> Ti, thank you once again for considering our migration issues.
>>>
>>> Kind regards
>>> Milos
>>>
>>> среда, 15. март 2023. у 17:23:08 UTC+1 Tim Donohue је написао/ла:
>>>
 Hi Milos,

 The "Out of Order" response from your migration scripts means that the 
 migration was *successful* but it ran out-of-order.  So, this is expected 
 output after an upgrade.

 It's unclear to me why you are attempting to restart the workflow?  Is 
 there an error you are seeing in the UI?

 You should only need to run "dspace database migrate ignored" and then 
 all your workflow tasks should migrate successfully.  Based on what you've 
 shared so far, it sounds like that process worked as expected.  So, I 
 don't 
 think you need to run the "RestartWorkflow" command at all, unless I'm 
 misunderstanding the issue you are hitting.

 Tim

 On Tuesday, March 14, 2023 at 7:58:02 AM UTC-5 imi...@gmail.com wrote:

> Dear All,
>
> Thanks to this support group, I have (almost) successfully migrated 
> the 6.3 deployment to 7.5. Regarding the basic functionality, the only 
> missing element is the workflow. Upon executing
>
> bin/dspace database migrate ignored 
>
> I have:
>
> | Versioned | 5.0.2014.11.04 | Enable XMLWorkflow Migration   
>   | JDBC | 2023-03-12 16:33:44 | Out of Order 
> |
> | Versioned | 6.0.2015.09.01 | DS 2701 Enable XMLWorkflow Migration   
>   | JDBC | 2023-03-12 16:33:44 | Out of Order 
> |
>
> I found some older threads on this and similar issues, but still not 
> sure what the correct approach is. When trying:
>
> bin/dspace dsrun org.dspace.xmlworkflow.migration.RestartWorkflow -e 
> ad...@myrespository.org
>
> I get the following error:
>
>  org.postgresql.util.PSQLException: ERROR: duplicate key value 
> violates unique constraint "cwf_workflowitem_item_id_key"
>   Detail: Key (item_id)=(ba7ffb7a-7fa0-4b8b-84bb-68dfef778620) already 
> exists.
>
> Any hint?
>
> Kind regards
> Milos
>
>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx

[dspace-tech] Re: index-discovery error

['Tim Donohue' via DSpace Technical Support]

Hi,

Based on that error message, it sounds like you somehow have invalid data 
in your "workspaceitem" database table (this table is used to store 
information about in-progress submissions).  The error seems to be saying 
that you have two different entries in the "workspaceitem" table which 
reference the *same* "item_id".  That shouldn't be possible, as each 
WorkspaceItem should have a *unique* "item_id".

I'm not sure how that could have occurred. But if you can find the 
duplicate entry in "workspaceitem", then it should be possible to just 
remove one of the entries.  I'd recommend making a copy of the database 
before doing this, as it's possible there could be side effects that I'm 
not foreseeing.  Once that duplicate entry is removed though, I suspect the 
indexing will work properly.

Tim
On Monday, March 20, 2023 at 2:30:32 AM UTC-5 Andrew K wrote:

> Hello!
>
> I have a 7.5 server updated from 5.4.
> The database update process finished OK.
> But the index-discovery fails. 
>
> 2023-03-20 09:24:03.611 INFO index-discovery - 4 @ The script has started 
> 2023-03-20 09:24:03.611 INFO index-discovery - 4 @ Updating Index 
> 2023-03-20 09:24:43.049 ERROR index-discovery - 4 @ null 2023-03-20 
> 09:24:43.050 ERROR index-discovery - 4 @ 
> java.lang.IllegalArgumentException: More than one result found at 
> org.dspace.core.AbstractHibernateDAO.uniqueResult(AbstractHibernateDAO.java:242)
>  
> at 
> org.dspace.content.dao.impl.WorkspaceItemDAOImpl.findByItem(WorkspaceItemDAOImpl.java:81)
>  
> at 
> org.dspace.content.WorkspaceItemServiceImpl.findByItem(WorkspaceItemServiceImpl.java:243)
>  
> at 
> org.dspace.content.ItemServiceImpl.getParentObject(ItemServiceImpl.java:1408) 
> at 
> org.dspace.content.ItemServiceImpl.getParentObject(ItemServiceImpl.java:92) 
> at 
> org.dspace.discovery.SolrServiceResourceRestrictionPlugin.additionalIndex(SolrServiceResourceRestrictionPlugin.java:129)
>  
> at 
> org.dspace.discovery.indexobject.IndexFactoryImpl.buildDocument(IndexFactoryImpl.java:67)
>  
> at 
> org.dspace.discovery.indexobject.InprogressSubmissionIndexFactoryImpl.buildDocument(InprogressSubmissionIndexFactoryImpl.java:51)
>  
> at 
> org.dspace.discovery.indexobject.WorkspaceItemIndexFactoryImpl.buildDocument(WorkspaceItemIndexFactoryImpl.java:63)
>  
> at 
> org.dspace.discovery.indexobject.WorkspaceItemIndexFactoryImpl.buildDocument(WorkspaceItemIndexFactoryImpl.java:30)
>  
> at org.dspace.discovery.SolrServiceImpl.update(SolrServiceImpl.java:169) at 
> org.dspace.discovery.SolrServiceImpl.indexContent(SolrServiceImpl.java:159) 
> at 
> org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:344) 
> at 
> org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:331) 
> at org.dspace.discovery.IndexClient.internalRun(IndexClient.java:130) at 
> org.dspace.scripts.DSpaceRunnable.run(DSpaceRunnable.java:104) at 
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
>  
> at 
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
>  
> at java.base/java.lang.Thread.run(Thread.java:829)The database info
> Database Type: postgres
> Database URL: jdbc:postgresql://localhost:5432/dspace
> Database Schema: public
> Database Username: dspace
> Database Software: PostgreSQL version 14.7 (Ubuntu 14.7-0ubuntu0.22.04.1)
> Database Driver: PostgreSQL JDBC Driver version 42.4.3
> PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.3)
> FlywayDB Version: 8.4.4
>
>
> +---++--+--+-+--+
> | Category  | Version| Description 
>  | Type | Installed On| State|
>
> +---++--+--+-+--+
> |   | 1  | << Flyway Init >>   
>  | BASELINE | 2016-02-15 00:03:53 | Baseline |
> | Versioned | 1.1| Initial DSpace 1.1 database schema 
>   | SQL  | 2016-02-15 00:03:53 | Success  |
> | Versioned | 1.2| Upgrade to DSpace 1.2 schema   
>   | SQL  | 2016-02-15 00:03:54 | Success  |
> | Versioned | 1.3| Upgrade to DSpace 1.3 schema   
>   | SQL  | 2016-02-15 00:03:54 | Success  |
> | Versioned | 1.3.9  | Drop constraint for DSpace 1 4 schema   
>  | JDBC | 2016-02-15 00:03:54 | Success  |
> | Versioned | 1.4| Upgrade to DSpace 1.4 schema   
>   | SQL  | 2016-02-15 00:03:54 | Success  |
> | Versioned | 1.5| Upgrade to DSpace 1.5 schema   
>

[dspace-tech] Re: DSpace 7.5 intermittent errors with patch operations

['Tim Donohue' via DSpace Technical Support]

Hi Agustina,

If you are sure it's not a CORS policy error, then I'd recommend checking 
the backend logs.  That "500 (Internal Server Error)" might also be logged 
in dspace.log or tomcat logs. If so, there may be more information there to 
help out.   If it's reproducible semi-easily, you could also turn on "Debug 
mode for the REST API" per our troubleshooting 
guide: 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)
  
 (I wouldn't recommend leaving that on for a long time though, as allows 
full error stacktraces to be seen in every REST API response, which is 
really useful to debug issues...but also can be useful to hackers trying to 
find vulnerabilities in your system.)

Tim

On Friday, March 17, 2023 at 11:46:47 AM UTC-5 Agustina Martinez wrote:

> Hi all,
>
> We are experiencing intermittent errors, mostly affecting PATCH operations 
> (e.g. modifying items metadata, editing a user or group), when there is 
> heavy load in the backend. 
>
> We do not see any relevant errors in the backend logs at all, but after 
> some timeout takes place I consistently see these two errors in the 
> developer tools:
>
> Access to XMLHttpRequest at 
> 'OUR-BACKEND-URL/server/api/core/items/421578b1-a644-4016-b3a0-c0afe904b0e8' 
> from origin 'https://dspace7-f-dev.lib.cam.ac.uk' has been blocked by 
> CORS policy: No 'Access-Control-Allow-Origin' header is present on the 
> requested resource.
> polyfills.1cded4d53dfa4781.js:1  PATCH 
> OUR-BACKEND-URL/server/api/core/items/421578b1-a644-4016-b3a0-c0afe904b0e8 
> net::ERR_FAILED 500 (Internal Server Error)
>
> It is definitely not CORS related and that error is mis-leading.
>
> Is anybody experiencing similar issues? So far I have not been able to 
> reproduce in the DEMO DSpace site or in my local environment.
>
> Best,
> Agustina
>

-- 
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/d3e5b635-5627-43c4-a12b-238270cf92ben%40googlegroups.com.

[dspace-tech] Re: DSpace 7.5 How to modify default Template

['Tim Donohue' via DSpace Technical Support]

Hi,

You appear to be looking at the DSpace *backend* directory.  DSpace has a 
frontend and a backend.  To modify the frontend's settings/theme you must 
locate the directory where you installed the frontend.  It should have the 
setup as described 
in https://wiki.lyrasis.org/display/DSDOC7x/User+Interface+Configuration

Tim

On Thursday, March 16, 2023 at 10:03:32 AM UTC-5 dima19...@gmail.com wrote:

> Hi, i am new user, please help me:
>
> I want to modify default theme "dspace", and cannot find such file as: 
> config/config.*.yml to modifier. 
> How can i modify my default template? ( I can copy this yml file from 
> github but how to "record" this file in a FrontEnd part?)
>
> I learn by this guide:
>
> https://wiki.lyrasis.org/display/DSDOC7x/User+Interface+Configuration?src=contextnavpagetreemode
>
> Adds:
> my site:
> [image: Screenshot (206).png]
> [image: Screenshot (205).png]
> i can not see *.yml files in Config
>
> Info:
> 1)Our site DSpace now is working in LAN adress: http://10.10.20.13:8080 
> and we create new Community and Collection succesfuly.
> 2)I has such folders in dspace directory (and no files in root dspace 
> folder):
> bin
> config
> exports
> handle-server
> lib
> log
> reports
> sitemaps
> solr
> temp
> triplestore
> upload
> var
> webapps
> 3)I can not find ANY file "*.yml" in Dspace folder.
> I can not find also src (source) folder in dspace directory.
>
> (P.S. Sorry for my english)
>
>

-- 
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/b043e347-f503-4b16-8489-bd27a2a8cca0n%40googlegroups.com.

[dspace-tech] Re: Dspace 7.2.1 to 7.5 migration

['Tim Donohue' via DSpace Technical Support]

Hi Raja,

Backend/frontend version requirements for 7.5 are listed 
at https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace

The versions you listed above all look fine.

Tim

On Thursday, March 16, 2023 at 7:25:27 AM UTC-5 raja...@gmail.com wrote:

> Hi Team,
>
> Could you please share software version details and any other important 
> details for the migration in 7.5 Dspace.
>
> As of now have used below software version,
>
> Apache any-1.10.12
> Maven-3.8.5
> Timcat-9
> Java -11
> Postgres-12
> Node-16.14
> Angular-13
> Yarn-1.22
> Cypress-9.6
> Solr-8.11
>
> Please suggest any version upgrade is required
>
> Regards,
> Raja
>

-- 
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/ed308a72-11aa-4936-9900-489c55cc597cn%40googlegroups.com.

[dspace-tech] Re: DSPACE7 - a public link for PDF download

['Tim Donohue' via DSpace Technical Support]

Hi Jan,

DSpace 7 doesn't provide an option to have a Bitstream (File) download link 
based on an Item's assigned Handle.  Instead, download links *are* 
persistent and public, but are based on the UUID of the Bitstream/file like 
this:
https://[dspace.url]/bitstreams/[uuid-of-bitstream]/download

That said, DSpace 7 does auto-redirect all older style 6.x URLs to the new 
location.  So, for example, in the DSpace 6.x XMLUI, file downloads used 
this URL structure:
https://[dspace.url]/bitstream/handle/[prefix]/[suffix]/[filename]

Those older URLs will redirect automatically to the new URL style (shown 
above), in case that's helpful.

Tim

On Thursday, March 16, 2023 at 5:36:22 AM UTC-5 jan.b...@gmail.com wrote:

> Any idea? We need a software solution to generate public links for PDF 
> downloads using only a given handle number.
> Thanks
>
> On Wednesday, March 8, 2023 at 8:55:06 AM UTC+1 Jan Broulím wrote:
>
>> Hi,
>> I would like to ask whether it is possible to generate a public link for 
>> pdf download - e.g. based on handle number.
>> Thank you
>> Jan
>>
>

-- 
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/1e2b39c5-dcd6-45da-9583-65ff5462143cn%40googlegroups.com.

[dspace-tech] Re: DSpace 7.5 migration from 6.3

['Tim Donohue' via DSpace Technical Support]

Hi Milos,

Unfortunately, the error messages displayed in the UI aren't enough 
information to debug the issue.  You'd need to locate the underlying 
exceptions behind those error messages, as those will provide more clues as 
to whether the problem is one of your configs or maybe something else with 
the installation.  We have a troubleshooting guide which walks you through 
finding underlying exceptions either in the UI or 
backend: 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Once you locate the underlying exception, it's possible you'll find one of 
the common installation errors listed 
at 
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues
  
If not, and the error text doesn't make sense, you can send it to this list 
and hopefully someone here can provide more clues.

Tim

On Thursday, March 16, 2023 at 3:32:38 AM UTC-5 imi...@gmail.com wrote:

> Dear Tim,
>
> Thank you for your quick response and explanation. It is good to know the 
> migration went well. 
>
> The next thing to look at is the item submission and workflow 
> configurations. According to the upgrade guide I did:
>
> [dspace]/bin/dspace submission-forms-migrate -s 
> [dspace]/config/temp/item-submission.xml -f 
> [dspace]/config/temp/input-forms.xml
>
> The "migrated" files are attached. If I leave the default workflow.xml, 
> in the UI I cannot submit a new item with the message "You have not the 
> privilege to make a new submission." Also, if an admin user goes to 
> "Administer workflow", the message "Error fetching search results" 
> appears. In 6.3 we used to have a simple "single reviewer" workflow and 
> admins for each collection (the old workflow-dspace63.xml is also 
> attached). As you can see, I am a little bit confused :)
>
> Ti, thank you once again for considering our migration issues.
>
> Kind regards
> Milos
>
> среда, 15. март 2023. у 17:23:08 UTC+1 Tim Donohue је написао/ла:
>
>> Hi Milos,
>>
>> The "Out of Order" response from your migration scripts means that the 
>> migration was *successful* but it ran out-of-order.  So, this is expected 
>> output after an upgrade.
>>
>> It's unclear to me why you are attempting to restart the workflow?  Is 
>> there an error you are seeing in the UI?
>>
>> You should only need to run "dspace database migrate ignored" and then 
>> all your workflow tasks should migrate successfully.  Based on what you've 
>> shared so far, it sounds like that process worked as expected.  So, I don't 
>> think you need to run the "RestartWorkflow" command at all, unless I'm 
>> misunderstanding the issue you are hitting.
>>
>> Tim
>>
>> On Tuesday, March 14, 2023 at 7:58:02 AM UTC-5 imi...@gmail.com wrote:
>>
>>> Dear All,
>>>
>>> Thanks to this support group, I have (almost) successfully migrated the 
>>> 6.3 deployment to 7.5. Regarding the basic functionality, the only missing 
>>> element is the workflow. Upon executing
>>>
>>> bin/dspace database migrate ignored 
>>>
>>> I have:
>>>
>>> | Versioned | 5.0.2014.11.04 | Enable XMLWorkflow Migration 
>>> | JDBC | 2023-03-12 16:33:44 | Out of Order |
>>> | Versioned | 6.0.2015.09.01 | DS 2701 Enable XMLWorkflow Migration 
>>> | JDBC | 2023-03-12 16:33:44 | Out of Order |
>>>
>>> I found some older threads on this and similar issues, but still not 
>>> sure what the correct approach is. When trying:
>>>
>>> bin/dspace dsrun org.dspace.xmlworkflow.migration.RestartWorkflow -e 
>>> ad...@myrespository.org
>>>
>>> I get the following error:
>>>
>>>  org.postgresql.util.PSQLException: ERROR: duplicate key value violates 
>>> unique constraint "cwf_workflowitem_item_id_key"
>>>   Detail: Key (item_id)=(ba7ffb7a-7fa0-4b8b-84bb-68dfef778620) already 
>>> exists.
>>>
>>> Any hint?
>>>
>>> Kind regards
>>> Milos
>>>
>>>

-- 
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/510b4b3c-4a30-4635-a741-de2e6df7afe1n%40googlegroups.com.

[dspace-tech] Re: DSpace 7.5 migration from 6.3

['Tim Donohue' via DSpace Technical Support]

Hi Milos,

The "Out of Order" response from your migration scripts means that the 
migration was *successful* but it ran out-of-order.  So, this is expected 
output after an upgrade.

It's unclear to me why you are attempting to restart the workflow?  Is 
there an error you are seeing in the UI?

You should only need to run "dspace database migrate ignored" and then all 
your workflow tasks should migrate successfully.  Based on what you've 
shared so far, it sounds like that process worked as expected.  So, I don't 
think you need to run the "RestartWorkflow" command at all, unless I'm 
misunderstanding the issue you are hitting.

Tim

On Tuesday, March 14, 2023 at 7:58:02 AM UTC-5 imi...@gmail.com wrote:

> Dear All,
>
> Thanks to this support group, I have (almost) successfully migrated the 
> 6.3 deployment to 7.5. Regarding the basic functionality, the only missing 
> element is the workflow. Upon executing
>
> bin/dspace database migrate ignored 
>
> I have:
>
> | Versioned | 5.0.2014.11.04 | Enable XMLWorkflow Migration   
>   | JDBC | 2023-03-12 16:33:44 | Out of Order |
> | Versioned | 6.0.2015.09.01 | DS 2701 Enable XMLWorkflow Migration   
>   | JDBC | 2023-03-12 16:33:44 | Out of Order |
>
> I found some older threads on this and similar issues, but still not sure 
> what the correct approach is. When trying:
>
> bin/dspace dsrun org.dspace.xmlworkflow.migration.RestartWorkflow -e admin
> @myrespository.org
>
> I get the following error:
>
>  org.postgresql.util.PSQLException: ERROR: duplicate key value violates 
> unique constraint "cwf_workflowitem_item_id_key"
>   Detail: Key (item_id)=(ba7ffb7a-7fa0-4b8b-84bb-68dfef778620) already 
> exists.
>
> Any hint?
>
> Kind regards
> Milos
>
>

-- 
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/235eabdc-c9d1-40ea-b08f-3699976635efn%40googlegroups.com.

[dspace-tech] Re: Default labels for dc metadata fields

['Tim Donohue' via DSpace Technical Support]

Hi Paige,

All DSpace 7 field labels displayed on the Item page should be defined in 
your language pack file in the U, usually right around this location:
https://github.com/DSpace/dspace-angular/blob/main/src/assets/i18n/en.json5#L2490-L2538

I'm not seeing any default given to the "dc.description.acquisition" 
field... and strangely that field doesn't even appear to be in the 
out-of-the-box "dc" schema that comes with 
DSpace: 
https://github.com/DSpace/DSpace/blob/main/dspace/config/registries/dublin-core-types.xml
 

So, my best guess is that this is custom code on your end, or someone added 
this field to your "dc" schema.  All schema can be modified from the Admin 
UI interface (Under "Registries -> Metadata")

Tim

On Wednesday, March 8, 2023 at 12:34:43 PM UTC-6 pai...@udel.edu wrote:

> Hi, all--
>
> My team noticed that when we add material to the field 
> dc.description.acquisition, it shows up in DSpace 7.4 with a field label 
> "Source." To my knowledge, "Source" isn't a DC default label. I'm curious: 
> is there a list somewhere of the labels that are associated with the 
> various dc fields that are available by default? (I'm not seeing it in 
> github, but I could be looking in the wrong spot.). 
>
> Are those labels customizable?
>
> 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. ***
>

-- 
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/a264b4af-f588-4d14-a062-136970c31525n%40googlegroups.com.

[dspace-tech] Re: DSpace 7.5 filter-media -f and diffrent size of thumbnails

['Tim Donohue' via DSpace Technical Support]

Hi Karol,

It's possible you are hitting this bug discovered in 
7.5: https://github.com/DSpace/DSpace/pull/8684

That PR provides a fix that is currently under review for inclusion in 
7.6.  If you find time to try it out yourself, please report back on that 
PR with your findings (as it helps us move along code changes more quickly 
when others have reported that the fix is working for them).

Tim

On Wednesday, March 8, 2023 at 9:18:49 AM UTC-6 karols...@gmail.com wrote:

> Hi,
>
> After migration from dspace 6.3 JSPUI to DSpace 7.5 i have a problem with 
> filter-media -f, it tries to generate new thumbnails, but can't generate 
> new larger ones. Only using filter-media -f -i and indicating the exact 
> bitstream helps - then the thumbnail is generated according to the 
> thumbnail.maxwidth setting.But when I try to do it globally filter-media -f 
> thumbnails are skipped and remain still small from previous dspace 6.3 
> jspui.
> How can I globally generate new thumbnails overwriting the old smaller 
> ones?
>
> Thanks,
>
> 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/88684abd-a128-44e6-be2e-929861e7580bn%40googlegroups.com.

[dspace-tech] Re: Send 'Password Reset' email automatically to new users added via ePeople ?

['Tim Donohue' via DSpace Technical Support]

Hi,

This is a known issue that a community member is working on a fix for... 
hopefully to be fixed in 7.6.

See this bug ticket: https://github.com/DSpace/dspace-angular/issues/2026

An early proposed fix is being developed 
in https://github.com/DSpace/dspace-angular/pull/2130

It's not yet fully working (as you'll see from the comments), but I'm 
hoping it'll be ready in time for 7.6.  If you are interested in 
collaborating on testing or providing feedback to the final fix, let us 
know in the GitHub ticket or PR.

Tim
On Friday, March 3, 2023 at 4:20:07 AM UTC-6 Ross wrote:

> Hi,
>
> When creating a new user via ePeople, I would like to automatically send 
> them an email asking them to set their password so that they don't have to 
> manually click 'Forgot Password' when first signing in. Is it possible? 
> 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/5753bc3e-211f-40fd-bdc9-566cd289905an%40googlegroups.com.

[dspace-tech] Re: don't show admin sidebar with normal logged in user

['Tim Donohue' via DSpace Technical Support]

Hi,

Apologies for the late response.  But, this bug was fixed in 7.5.  The 
sidebar no longer appears if you are a read-only user.  It will only appear 
if you have special permissions to administer a Collection, Community, or 
the entire site.

Tim

On Thursday, March 2, 2023 at 2:43:43 PM UTC-6 jorge@udb.edu.sv wrote:

> hello .
>
> When a user registers in my dspace 7.4 and then logs in, they have access 
> to the administrator menu:
>
> [image: 1.png]
>
> When this user accesses both options, he does not have permission to 
> execute the changes either, this is fine, but I would also like that said 
> sidebar not appear, if not, only to administrators and editors.
>
> can this be done somehow?
> Thanks in advance for the help
>

-- 
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/836fc128-b252-4a32-89c9-d8eb8487e565n%40googlegroups.com.

[dspace-tech] Re: Configure Creative Commons Step as Required in submission form

['Tim Donohue' via DSpace Technical Support]

If this isn't working as you described, then it sounds like there may be a 
bug in the code.  That "mandatory" flag should make the step required when 
it is set to "true".  Please feel free to submit a bug ticket 
to https://github.com/DSpace/dspace-angular/issues and I'll see if I can 
find a volunteer to fix it.

Tim

On Friday, February 24, 2023 at 10:48:39 AM UTC-6 WILLIAN wrote:

> Hi,
>
> I need the Creative Commons step to be required in submission process. I 
> tried changing "mandatory" to "true" in step definitions 
> (item-submission.xml) but it didn't work.
>
> ... 
>
> Is there any configuration for this?
>
> 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/34b77154-c0fb-4323-80db-c33b47788b00n%40googlegroups.com.

[dspace-tech] Re: Get All Items in Specific Collection with API

['Tim Donohue' via DSpace Technical Support]

Hi,

The REST API documentation is available at 
https://github.com/DSpace/RestContract

To find all the Items in a Collection, you'd use the search endpoint, and 
pass in the UUID of the collection as the "scope":

https://github.com/DSpace/RestContract/blob/main/search-endpoint.md#search-endpoint

In general, if you are trying to find which endpoint to use in the REST 
API, you can discover it simply by using the User Interface.  The User 
Interface uses the REST API at all times... so if you click a button or 
visit a page in the User Interface, you can see which REST API endpoints it 
uses to gather that data.  In your browser, you'd open the DevTools and 
take a look at the "Network" tab, where you can see every call the User 
Interface makes to the REST API.

Tim


On Friday, February 24, 2023 at 7:59:04 AM UTC-6 badaka...@gmail.com wrote:

> I'm trying to get all the items in a collection using the endpoint of the 
> Rest-API on Dspace 7. I've looked at the Rest-API documentation on github 
> but I can't find it. I think in Dspace 6 a user can get all the items in a 
> collection using the /collections/{collectionId}/items endpoint, then for 
> dspace 7 what endpoint can I use? 
> Thank you 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/3c55f46d-743a-4f10-a6f1-140abf2abc52n%40googlegroups.com.

[dspace-tech] Re: REST API login not working on DSpace version 7.4 after upgrade from DSpace 6.2

['Tim Donohue' via DSpace Technical Support]

Hi,

That first screenshot shows the error message as :
"405 Only POST is allowed for login requests"

That means that you are calling that "/login" method incorrectly and need 
to use POST.  Here's the docs on that endpoint which has some examples:
https://github.com/DSpace/RestContract/blob/main/authentication.md

Tim

On Friday, February 24, 2023 at 5:54:50 AM UTC-6 joem...@gmail.com wrote:

> Please see attachment 
>
> On Friday, 24 February 2023 at 13:53:25 UTC+2 Lewatle Johannes Phaladi 
> wrote:
>
>> Hi DSpace Team,
>>
>> I have done numerous test using postman to connect to DSpace 7.4 without 
>> luck, when sending request checking status it succeed but when logging in 
>> it fails, please see the following screenshots, the first one is the error 
>> on our API page and the second one is seccess results from Dspace demo site 
>> that I would like to receive, please guide on what to do to solve this 
>> problem :
>>
>> [image: authentication fails.png]
>>
>>
>> [image: authentication success on demo.png]
>>
>> 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/6924322c-18a0-47e7-b58c-278283be701bn%40googlegroups.com.

[dspace-tech] Re: External metadata source in the submission form

['Tim Donohue' via DSpace Technical Support]

Hi Anis,

We have some (higher level) code walkthroughs/examples in the 
videos/webinars available 
here: https://wiki.lyrasis.org/display/DSPACE/Videos+and+Webinars

The most recent was a developer workshop last 
year: 
https://wiki.lyrasis.org/display/DSPACE/2022-11+-+DSpace+7.4+Webinar+Series

This workshop was brief though (only an hour) so it had to concentrate on 
higher level concepts in the UI.  We don't yet have "deep dive" style 
developer workshop. I hope we could have that some day, but it may not come 
until after 7.x development is completed & we've moved on to 8.0... simply 
because the developers who could teach that workshop are all doing active 
feature development.  That said, we welcome questions & you could ask for 
hints/tips on Slack (many developers are 
there): https://wiki.lyrasis.org/display/DSPACE/Slack

Tim

On Friday, February 24, 2023 at 1:13:09 AM UTC-6 Anis wrote:

> Hey, I've been working on a custom external metadata source, where the 
> extracted text from the uploaded pdf is sent to an external API (
> https://annif.org/) to be analyzed and should return some suggestions for 
> controlled vocab subjects. The backend works now nicely and populates the 
> right metadata field with the suggestions, but my next step is to populate 
> the form (probably the controlled vocabulary input field) with these 
> suggestions so the user can pick and choose the correct ones. I've been 
> trying to do a deep dive on the frontend code, but I'm still relatively new 
> with the new dspace frontend and angular 2, so where should I start looking 
> into this? And is there some documentation, material, videos or tutorials 
> on the technical parts of the frontend?
>
> - Anis
>

-- 
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/eee159b3-9bfe-4ee7-a790-084e46b145fen%40googlegroups.com.

[dspace-tech] Re: System-wide Alert error

['Tim Donohue' via DSpace Technical Support]

Hi,

Please follow our troubleshooting guide to locate the detailed error 
message behind the 
scenes. 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

The error messages displayed in the User Interface just let you know there 
was a problem.  But, the only way to determine the cause of the problem is 
to find the detailed error message by following that Troubleshooting 
guide.  Once you've found the error, if you cannot figure it out, you can 
send it to this mailing list for more help.

Tim

On Wednesday, February 22, 2023 at 3:01:10 AM UTC-6 zxale...@gmail.com 
wrote:

> Hi, help me please,
> when I active or inactive System-wide Alert -  I get error - Something 
> went wrong when updating the system-wide alert
>
> Best,
> Alex
>
>  DSpace version:  7.5
>   SCM revision:  ${buildNumber}
> SCM branch:  UNKNOWN_BRANCH
> OS:  Linux(amd64) version 5.15.0-7.86.6.1.el8uek.x86_64
>   Applications:
>  Discovery:  enabled.
>JRE:  Red Hat, Inc. version 17.0.6
>Ant version:  Apache Ant(TM) version 1.10.13 compiled on January 4 2023
>  Maven version:  3.9.0
>DSpace home:  /dspace
>
>
>

-- 
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/944cc0d2-784d-4268-b7f8-0eec0795ec92n%40googlegroups.com.

[dspace-tech] Re: Statistics data not available

['Tim Donohue' via DSpace Technical Support]

Hi,

You may want to check your Statistics configuration to ensure it is 
correct, namely the "solr-statistics.server" setting documented 
here: 
https://wiki.lyrasis.org/display/DSDOC7x/SOLR+Statistics#SOLRStatistics-ConfigurationsettingsforStatistics

If it is correct, and it's still not working, then you might want to look 
for error messages in your backend logs.  Here's our troubleshooting guide 
which has tips for finding that 
info: 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Generally speaking, these statistics should "just work" assuming the 
configurations are correctly pointing at your Statistics index in Solr.  
But, if there are errors occurring on the backend, that may cause them to 
no longer work.  If you find any backend errors and cannot figure them out, 
feel free to send them to this list & we'll see if we can help.

Tim

On Saturday, February 18, 2023 at 6:57:10 PM UTC-6 Cardenas wrote:

> Kind Regards Dspace Technical Support
>
> I hope you can help me with the problem I have to show Solr statistics in 
> my Dspace page, I have searched all the available information and reviewed 
> the documentation, but I can't find a solution, and the statistics page 
> shows the message "data not available", and when I make the query by 
> url/server/#https://url/server/api/statistics I get the message 
> "{
>   "id": null,
>   "type": "statistics"
> }".
>
> Without more to add, I say goodbye, and thank you in advance for your help.
>

-- 
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/7c132d4b-9388-4a22-9c7a-a10b28a2918dn%40googlegroups.com.

[dspace-tech] Re: DSpace 7 with apache tomcat 10

['Tim Donohue' via DSpace Technical Support]

Hi Bill,

I am aware that the DSpace backend's "Hal Browser" may not work properly in 
Tomcat 10: https://github.com/DSpace/DSpace/issues/8173

That's something I'm hoping we'll get solved in 7.6.  

It is possible though that the backend *works* it's just that this 
browser (which is more of a developer tool) may not function properly.

Tim

On Friday, February 17, 2023 at 12:51:00 PM UTC-6 tant...@umn.edu wrote:

> Just wondering if anybody is using apache tomcat 10x with their DSpace 7x 
> installation.  Any problems?
> Thanks,
> ~~Bill
>
> -- 
> Human wheels spin round and round
> While the clock keeps the pace... -- John Mellencamp
> 
> Bill TantzenUniversity of Minnesota Libraries
> 612-626-9949 <(612)%20626-9949> (U of M)612-325-1777 
> <(612)%20325-1777> (cell)
>

-- 
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/54c6b21f-995f-49f1-9b83-9eba0b16a35en%40googlegroups.com.

Re: [dspace-tech] ANNOUNCEMENT: DSpace 7 nearing feature completion. Planning for 8.0 will begin in 2023

['Tim Donohue' via DSpace Technical Support]

Hello,

Sorry for your disappointment.  Our community is made of volunteers, and 
many of those volunteers have been busy of the last 2 weeks finishing up 
the 7.5 release (finished & announced on Feb 20).  Questions on the lists 
will get answered, but when our volunteer helpers are busy with a release, 
those answers may not be immediate at all times.

We have recommendations on finding DSpace answers also own our Support 
page.  It includes hints/tips on searching for answers in mailing lists (as 
sometimes you can find an answer there to someone who asked the same 
question), and also tips about troubleshooting common 
problems.  https://wiki.lyrasis.org/display/DSPACE/Support

Tim

On Thursday, February 16, 2023 at 11:40:51 PM UTC-6 ali.sh...@gmail.com 
wrote:

> what kind of community is this? I need help and you are sending me 
> useless emails, what about my issue? 
> very unprofessional behaviour you guys have.
> I am really disappointed.
>
> On Thu, Feb 16, 2023 at 9:34 PM DSpace Technical Support <
> dspac...@googlegroups.com> wrote:
>
>> Dear Members of the DSpace Community:
>>
>> When DSpace 7.0 
>>  was 
>> released in August, 2021, the DSpace Steering Group 
>>  announced plans to continue 
>> to add missing 6.x features to the 7.x platform in each minor release. This 
>> was a temporary departure from past DSpace releases, as every 7.x release 
>> (7.1 - 7.4) has continued to add new features and functionality to the 
>> platform.  While this approach has allowed us to quickly align 7.x with the 
>> 6.x platform, we recognize that adding new features in minor releases can 
>> complicate upgrades between these releases.
>>
>> As we approach the two year anniversary of DSpace 7, the DSpace Steering 
>> group would like to announce that 7.x will be considered “feature complete” 
>> as soon as it has achieved sufficient feature parity with 6.x. We expect 
>> this feature complete status to arrive in 2023, likely in either the 7.6 or 
>> 7.7 release (to be announced).
>>
>> Once 7.x is “feature complete”, DSpace will revert to its previously 
>> established Release Numbering Scheme 
>> 
>>  and 
>> release schedule. Only major releases (8.x, 9.x, etc.) will receive new 
>> features. Additional minor releases will only contain bug fixes. Similarly, 
>> DSpace will revert to its prior release scheduling of one major release per 
>> year, with regular bug fix releases as necessary.
>>
>> If you or your institution have any questions, please get in touch.  A 
>> few common questions and answers are shared below. 
>>
>> If you or your institution would like to support remaining development, 
>> please contact us at dspaced...@lyrasis.org.  You can also visit the DSpace 
>> wiki 
>> 
>>  for 
>> more information about the DSpace Development Fund and see a list of 
>> institutions that have already contributed.
>>
>> Sincerely,
>>
>> Natalie Baur, on behalf of the DSpace Steering Group
>>
>> What does “feature complete” mean for 7.x?
>>
>> Once Steering determines that 7.x has achieved sufficient feature parity 
>> with 6.x, no additional new features will be added to the 7.x platform. 
>> This does not guarantee that every 6.x feature will have made it into 7.x, 
>> but all the highest priority 6.x features (see prioritized feature list 
>> )
>>  
>> will be in a 7.x release.
>>
>> At this point, 7.x will move into “maintenance”, which means it will only 
>> receive bug and security fixes. 7.x will continue to have new releases, but 
>> it will revert to the release strategy where additional minor releases only 
>> contain bug/security fixes based on our Software Support Policy 
>> .
>>
>> When will 8.0 development begin? What will that release look like?
>>
>> After 7.x is considered “feature complete”, DSpace Steering will begin 
>> planning for the 8.0 release in consultation with the DSpace Leadership 
>> Group  and the entire 
>> DSpace community. The exact release date for 8.0 is to be determined, but 
>> expected to be approximately a year after 7.x achieves “feature complete” 
>> status.
>>
>> 8.x will follow the previously established Release Numbering Scheme 
>> .
>>  
>> This means that 8.0 will contain new features, but any minor releases (8.1, 
>> 8.2, 8.3, etc) will only contain bug/security fixes.
>>
>> -- 
>> All messages to this mailing list should adhere to the Code of Conduct: 
>> 

[dspace-tech] Re: DSpace REST API access denied

['Tim Donohue' via DSpace Technical Support]

Hi,

My general advice when learning about the REST API is to do the following:
* First, look in the REST API documentation 
at https://github.com/DSpace/RestContract/ for related documentation.
* If you cannot find the endpoint that is used, you can *discover it* 
easily by using the User Interface.  Our DSpace UI uses the REST API for 
everything.  So, if you open up the UI and perform an action (like login), 
you can see in your browser's DevTools (Network tab) which REST API calls 
it has made.  You can then look for the docs on those endpoints in our 
documentation at  https://github.com/DSpace/RestContract/

For Authentication, use this 
endpoint: https://github.com/DSpace/RestContract/blob/main/authentication.md
For Collection info, use this 
endpoint: https://github.com/DSpace/RestContract/blob/main/collections.md
For Uploading, you need to first create a submission, 
see https://github.com/DSpace/RestContract/blob/main/submission.md

Tim

On Thursday, February 16, 2023 at 5:02:27 AM UTC-6 joem...@gmail.com wrote:

>
> I have gone through that link and we would like to find the following :
>
>- We need to know when we authenticate to what endpoint to use and 
>what it is expecting. 
>- When retrieving the collection what endpoint to use and what it is 
>expecting. 
>- When uploading a document what endpoint to use and what it is 
>expecting. 
>
>  
>
>
> On Thursday, 9 February 2023 at 15:53:47 UTC+2 Lewatle Johannes Phaladi 
> wrote:
> Hello Tim,
>
> Thanks very much I will read and see if this can be resolved.
>
> Regards,
> Lewatle 
>
> On Wednesday, 8 February 2023 at 17:51:06 UTC+2 Tim Donohue wrote:
>
> Hi Lewatle,
>
> When interacting with the DSpace 7 REST API, a CSRF token is *required* to 
> be sent with any modifying requests (POST, PUT, etc).  See the 
> documentation in our REST contract about this: 
> https://github.com/DSpace/RestContract/blob/main/csrf-tokens.md
>
> The error you are seeing is noting that the CSRF token was either invalid 
> or missing from the request.
>
> Tim
> On Wednesday, February 8, 2023 at 6:25:36 AM UTC-6 joem...@gmail.com 
> wrote:
> Hi DSpace Team,
>
> I am integrating DSpace 7 with external site using REST API, I am getting 
> the following error, site will be pushing items to DSpace 7 repository, I 
> have created collection and added user as admin user to push items to that 
> collection using REST API any advise is appreciated :
>
>  [image: rest api error.png]
> Also please see the following bottom part of log file:
>
> 2023-02-08 14:12:34,633 WARN  8b8d2fb9-8569-4973-9168-b9fbaa0b6015 
> 4be5c62f-c00d-459a-aa19-5e7bc1a3c971 
> org.dspace.app.rest.exception.DSpaceApiExceptionControllerAdvice @ 
> Authentication is required (status:401 exception: Access is denied at: 
> org.springframework.security.access.vote.AffirmativeBased.decide(AffirmativeBased.java:73))
> 2023-02-08 14:12:34,927 INFO  8b8d2fb9-8569-4973-9168-b9fbaa0b6015 
> 566dfe1c-97c9-478a-a7e5-9ed952bfeedf 
> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
> [GET /server/api/authz/authorizations/search/object] originated from 
> /xmlui/browse?type=subject=protein%2Bfolding
> 2023-02-08 14:12:34,927 INFO  8b8d2fb9-8569-4973-9168-b9fbaa0b6015 
> 6988db4c-67d2-421c-a5dd-8c17ed903092 
> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
> [GET /server/api/authz/authorizations/search/object] originated from 
> /xmlui/browse?type=subject=protein%2Bfolding
> 2023-02-08 14:12:34,927 INFO  8b8d2fb9-8569-4973-9168-b9fbaa0b6015 
> 37aaec75-a8ab-4025-a03e-4e7bb9b403a7 
> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
> [GET /server/api/authz/authorizations/search/object] originated from 
> /xmlui/browse?type=subject=protein%2Bfolding
> 2023-02-08 14:12:34,928 INFO  8b8d2fb9-8569-4973-9168-b9fbaa0b6015 
> 06d1084e-3458-44ed-a3cf-b5672829feda 
> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
> [GET /server/api/authz/authorizations/search/object] originated from 
> /xmlui/browse?type=subject=protein%2Bfolding
> 2023-02-08 14:12:34,931 INFO  8b8d2fb9-8569-4973-9168-b9fbaa0b6015 
> 932de25e-437b-48ed-a6f4-7bbdfe783320 
> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
> [GET /server/api/authz/authorizations/search/object] originated from 
> /xmlui/browse?type=subject=protein%2Bfolding
> 2023-02-08 14:12:38,192 INFO  unknown fd90964e-63aa-403f-a1d7-3aa408894d59 
> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
> [GET /server/api] originated from /
> 2023-02-08 14:12:38,208 INFO  b1dc80ab-3b96-4980-b77c-8f5ab83f4724 
> 914c9aea-0a8b-41f6-9fd3-b33912d212fd 
> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
> [GET /server/api/authn/status] originated from /
> 2023-02-08 14:12:38,220 INFO  b1dc80ab-3b96-4980-b77c-8f5ab83f4724 
> 95337709-2af1-4791-997b-e799d22c2e2f 
> 

Re: [dspace-tech] Re: Excluding metadata from browse and search result - dspace 7.3

['Tim Donohue' via DSpace Technical Support]

Hi,

In case you haven't figured it out yet, I think the setting you are looking 
for is this one:
https://github.com/DSpace/DSpace/blob/main/dspace/config/spring/api/discovery.xml#L2421

You likely need to comment out the "dc.contributor.author" field from that 
"author" index and *reindex* your content (./dspace index-discovery -b).  
 That should ensure that only dc.creator is shown in the Author fields in 
search/browse.

Tim

On Thursday, February 16, 2023 at 12:39:47 AM UTC-6 tif...@gmail.com wrote:

> Then you're probably looking for a file discovery.xml in folder 
> .../dspace/config/spring/api
>
> Regards,
> Mariusz
>
> środa, 15 lutego 2023 o 17:48:30 UTC+1 WILLIAN VALMORBIDA napisał(a):
>
>> Hi,
>>
>> I tried this. This configuration only removes the metadata from the 
>> index, but doesn't remove the metadata (dc.contributor.*) shown in the 
>> search results.
>> I believe that this needs to be changed in some page, but I don't located 
>> it.
>>
>> Thanks
>> Willian
>>
>>
>> Em qua., 15 de fev. de 2023 às 08:43, Technologiczny Informator <
>> tif...@gmail.com> escreveu:
>>
>>> Have you tried changing the webui.browse.index.2 parameter in the 
>>> dspace.cfg file?
>>> In your case it should be:
>>> webui.browse.index.2 = author:metadata:dc.creator:text
>>> then rebuild the index.
>>>
>>> Regards,
>>> Mariusz
>>>
>>> wtorek, 14 lutego 2023 o 19:57:20 UTC+1 WILLIAN napisał(a):
>>>
 For a institutional reason, I have changed in the dspace to dc.creator 
 be a main author of the document and I have used dc.contributor as advisor 
 and another informations about the advisor. So, everything is fine a 
 exception that the dc.creator and dc.contributor.* seems as author in the 
 search and browse results. I desire that only dc.creator apear in the 
 result, but no one configuration tha I have tested does that in DSpace 7.3.
 Anybody knows how to exclude dc.contributor.* from search and browse 
 results?

 -- 
>>> 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/dc0321ed-28a4-49d1-a661-126289e393cen%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>
>> [image: http://www.univates.br] 
>
>

-- 
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/020f8ed2-7194-42ae-aec8-1a3a64e3e52en%40googlegroups.com.

[dspace-tech] Re: DSpace7 Not accessible on IP Address

['Tim Donohue' via DSpace Technical Support]

Hi,

If you are still getting this 500 error, there's a guide for solving it in 
our "Common Installation Issues" 
section: 
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues

It usually means there's a misconfiguration between your backend configs 
(local.cfg) and your frontend configs (config.*.yml)  *or* there may be an 
SSL Certificate issue with the backend which is causing the frontend not to 
be able to access it.

Also check our troubleshooting guide for hints/tips on locating the 
underlying issue behind a 500 error, as it's possible that will give you 
more 
clues: 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

If you need further help, send us the underlying error you find to this 
mailing list.

Tim
On Tuesday, February 14, 2023 at 8:51:44 AM UTC-6 ali.sh...@gmail.com wrote:

> Hello Everyone.
> Dear Community,
> Could you help me for the setup of the Local IP Configuration? I have 
> recently installed dspace7 it's working well on localhost:4000 but the 
> problem is that it's not working on the local IP. I want to access dspace7 
> on the local network.
>
> i have already configured the frontend and backend config file. when i hit 
> the link it land on the page and the redirect me on the 500 page the 
> service is unavailable.
> Please see the attached image for your reference.
>
> Please help me...
>

-- 
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/5a21760c-aa2f-4891-a014-55015b20a2d7n%40googlegroups.com.

[dspace-tech] Re: DSPACE 7.4 Upload failed

['Tim Donohue' via DSpace Technical Support]

Hi Jan,

Please use our "Troubleshoot an error" guide to try to locate the 
underlying error 
message: 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

The "Upload failed" announcement is just a user-facing notice, and it 
doesn't tell us what the core problem may be.  So, you should look for more 
specific error messages on either the frontend or backend by following the 
troubleshooting guide.  Once you find the detailed error, if you cannot 
figure out a solution, you can send it this email list and someone here may 
be able to help.

Tim

On Monday, February 13, 2023 at 3:43:47 AM UTC-6 jan.b...@gmail.com wrote:

> Hello,
> I am currently testing managing collections in DSpace 7.4. When I try to 
> upload a new file (New -> Item within some collection), it crashes with 
> "Upload failed" announcement.
> Tested in several browsers.
> Any suggestion for this will be useful.
> Thank you!
> Jan
>

-- 
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/6ea6bd74-0555-42e8-bf16-0e4c4960a54dn%40googlegroups.com.

[dspace-tech] Re: DSpace REST API access denied

['Tim Donohue' via DSpace Technical Support]

Hi Lewatle,

When interacting with the DSpace 7 REST API, a CSRF token is *required* to 
be sent with any modifying requests (POST, PUT, etc).  See the 
documentation in our REST contract about 
this: https://github.com/DSpace/RestContract/blob/main/csrf-tokens.md

The error you are seeing is noting that the CSRF token was either invalid 
or missing from the request.

Tim
On Wednesday, February 8, 2023 at 6:25:36 AM UTC-6 joem...@gmail.com wrote:

> Hi DSpace Team,
>
> I am integrating DSpace 7 with external site using REST API, I am getting 
> the following error, site will be pushing items to DSpace 7 repository, I 
> have created collection and added user as admin user to push items to that 
> collection using REST API any advise is appreciated :
>
>  [image: rest api error.png]
> Also please see the following bottom part of log file:
>
> 2023-02-08 14:12:34,633 WARN  8b8d2fb9-8569-4973-9168-b9fbaa0b6015 
> 4be5c62f-c00d-459a-aa19-5e7bc1a3c971 
> org.dspace.app.rest.exception.DSpaceApiExceptionControllerAdvice @ 
> Authentication is required (status:401 exception: Access is denied at: 
> org.springframework.security.access.vote.AffirmativeBased.decide(AffirmativeBased.java:73))
> 2023-02-08 14:12:34,927 INFO  8b8d2fb9-8569-4973-9168-b9fbaa0b6015 
> 566dfe1c-97c9-478a-a7e5-9ed952bfeedf 
> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
> [GET /server/api/authz/authorizations/search/object] originated from 
> /xmlui/browse?type=subject=protein%2Bfolding
> 2023-02-08 14:12:34,927 INFO  8b8d2fb9-8569-4973-9168-b9fbaa0b6015 
> 6988db4c-67d2-421c-a5dd-8c17ed903092 
> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
> [GET /server/api/authz/authorizations/search/object] originated from 
> /xmlui/browse?type=subject=protein%2Bfolding
> 2023-02-08 14:12:34,927 INFO  8b8d2fb9-8569-4973-9168-b9fbaa0b6015 
> 37aaec75-a8ab-4025-a03e-4e7bb9b403a7 
> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
> [GET /server/api/authz/authorizations/search/object] originated from 
> /xmlui/browse?type=subject=protein%2Bfolding
> 2023-02-08 14:12:34,928 INFO  8b8d2fb9-8569-4973-9168-b9fbaa0b6015 
> 06d1084e-3458-44ed-a3cf-b5672829feda 
> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
> [GET /server/api/authz/authorizations/search/object] originated from 
> /xmlui/browse?type=subject=protein%2Bfolding
> 2023-02-08 14:12:34,931 INFO  8b8d2fb9-8569-4973-9168-b9fbaa0b6015 
> 932de25e-437b-48ed-a6f4-7bbdfe783320 
> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
> [GET /server/api/authz/authorizations/search/object] originated from 
> /xmlui/browse?type=subject=protein%2Bfolding
> 2023-02-08 14:12:38,192 INFO  unknown fd90964e-63aa-403f-a1d7-3aa408894d59 
> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
> [GET /server/api] originated from /
> 2023-02-08 14:12:38,208 INFO  b1dc80ab-3b96-4980-b77c-8f5ab83f4724 
> 914c9aea-0a8b-41f6-9fd3-b33912d212fd 
> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
> [GET /server/api/authn/status] originated from /
> 2023-02-08 14:12:38,220 INFO  b1dc80ab-3b96-4980-b77c-8f5ab83f4724 
> 95337709-2af1-4791-997b-e799d22c2e2f 
> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
> [GET /server/api] originated from /
> 2023-02-08 14:12:38,232 INFO  b1dc80ab-3b96-4980-b77c-8f5ab83f4724 
> c87c18c7-ff99-40a2-b085-a2bfe5f7b610 
> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
> [GET /server/api] originated from /
> 2023-02-08 14:12:38,259 INFO  b1dc80ab-3b96-4980-b77c-8f5ab83f4724 
> 0c08261b-df34-4985-8eaa-3838b66bd616 
> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
> [GET /server/api/pid/find] originated from /
> 2023-02-08 14:12:38,274 INFO  b1dc80ab-3b96-4980-b77c-8f5ab83f4724 
> a9a14e04-2565-4e5a-aa0e-c0995d0863e5 
> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
> [GET /server/api/core/items/a237481f-6f19-4ebf-ba71-cc3d28ef7905] 
> originated from /
> 2023-02-08 14:12:38,316 INFO  b1dc80ab-3b96-4980-b77c-8f5ab83f4724 
> 616f08b5-7fb8-46d1-9c1a-d3251c2a4f51 
> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
> [GET /server/api] originated from /
> 2023-02-08 14:12:38,329 INFO  b1dc80ab-3b96-4980-b77c-8f5ab83f4724 
> d514e9d5-1162-4d9e-9fa9-d6dfba06142b 
> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
> [GET /server/api] originated from /
> 2023-02-08 14:12:38,340 INFO  b1dc80ab-3b96-4980-b77c-8f5ab83f4724 
> 6b23926e-4ff3-4508-b5e7-4f67421c6a8b 
> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
> [GET /server/api] originated from /
> 2023-02-08 14:12:38,895 INFO  b1dc80ab-3b96-4980-b77c-8f5ab83f4724 
> 35240db7-2438-4a2a-9d6c-0dcbc40a0d9f 
> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
> [GET 

[dspace-tech] Re: 500 Error is showing in UI

['Tim Donohue' via DSpace Technical Support]

Hi,

Please follow our troubleshooting guide to find the details behind the 500 
error.  It's not easy to provide any help without the error details. 

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

Once you locate the error details, if you cannot figure out how to solve 
the problem, you may wish to see if the error is one of the "common 
installation issues" listed 
here: 
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues
  
 If you still cannot find the solution, feel free to send the error 
messages to this list and hopefully someone here can provide support.

Tim

On Wednesday, February 8, 2023 at 7:02:52 AM UTC-6 AFA wrote:

> Dear team,
>
> *I install the DSpace 7.4  Backend successfully in AWS ubuntu 22.04 server 
> and It is accessible through MYIP:8080/server*
>
> *and I install the UI also and I did the test run it is also successful 
> but I unable to access it through myIP:4000*
>
> root@ip-XX-XXX-XX-X:/opt/dspace-7-angular/config# *yarn test:rest*
> yarn run v1.22.19
> $ ts-node --project ./tsconfig.ts-node.json scripts/test-rest.ts
> Building production app config
> Overriding app config with /opt/dspace-7-angular/config/config.yml
> Overriding app config with /opt/dspace-7-angular/config/config.prod.yml
> ...Testing connection to REST API at http://localhost:8080/server/api...
>
> RESPONSE: 200
>
> Checking JSON returned for validity...
> "dspaceVersion" = DSpace 7.4
> "dspaceUI" = http://localhost:4000
> "dspaceServer" = http://localhost:8080/server
> "dspaceServer" property matches UI's "rest" config? true
> Does "/api" endpoint have HAL links ("_links" section)? true
> Done in 4.33s.
>
>
> *then I install the nginx and I paste this 
> in /etc/nginx/sites-enabled/default :--*
>
> server { listen 80; 
>   server_name localhost; 
>   access_log /var/log/nginx/dspace-access.log; 
>   error_log /var/log/nginx/dspace-error.log; 
>  location / { 
>proxy_set_header X-Forwarded-Host $host; 
>proxy_set_header X-Forwarded-Server $host; 
>proxy_set_header X-Forwarded-For 
> $proxy_add_x_forwarded_for;
>proxy_pass http://localhost:4000/; 
>  } 
>   }
>
> *then it is accessible by myIP:80 but it through 500 error, Please help me 
> to solve this issue*
>
> *Thanks,*
> *AFA*
>

-- 
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/7023e66b-b30b-4c24-a6c8-c9704f634924n%40googlegroups.com.

Re: [dspace-tech] Issue with database migration 6.3 to 7.4

['Tim Donohue' via DSpace Technical Support]

Hi Jake,

Based on the error you shared, it looks like you are still hitting issues 
with the 5.7 migrations that I mentioned can be ignored.  See my prior 
email https://groups.google.com/g/dspace-tech/c/_7XI9xmwpI8/m/CH__FIU_AwAJ 
The first error in your "dspace7_failed" file is related to that 5.7 
migration. 

The second error (which mentions a 7.0 migration) appears to be because you 
are not running "./dspace database migrate ignored" (instead it looks like 
you left off the "ignored"), which is required when you upgrade from 6.x -> 
7.x

At least that's what it appears to be based on what you have shared.

Tim

On Friday, February 3, 2023 at 10:54:47 AM UTC-6 jacob.cameron wrote:

> That did help me make some progress.  
>
>  
>
> I was able to import the database properly.  I also followed one of Tim’s 
> suggestions so we could skip the 
> V5.7_2017.04.11__DS-3563_Index_metadatavalue_resource_type_id_column.sql 
> issue.
>
>  
>
> Now I’m getting a new error when trying to migrate the database on the 7.4 
> server.  I found a suggestion from Tim to run ./dspace database migrate 
> ignored on my old server to resolve the integer to UUID issue but it fails 
> on my current 6.3 server.  The error is with one of the 7.0 sql queries, 
> I’ve attached a copy of what I am receiving when trying to import on the 
> new server and a copy of what I got when I tried to upgrade the database on 
> my current server.
>
>  
>
> Jake
>
> --
>
> Jake Cameron, BCS(UNB)
>
> Systems Support Specialist III
>
> Information Systems and Technical Services University of Lethbridge Library
>
> Phone:(403)329-2756 <(403)%20329-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:* dspac...@googlegroups.com  *On Behalf 
> Of *Mohammad S. AlMutairi
> *Sent:* February 3, 2023 6:53 AM
> *To:* DSpace Technical Support 
> *Subject:* Re: [dspace-tech] Issue with database migration 6.3 to 7.4
>
>  
>
> 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 phis...@uleth.ca.
>
>  
>
> Hi Jake, 
>
>  
>
> I don't think it's necessary to upgrade the old dspace PostgreSQL version 
> because of this issue ( You already have version 13 installed on the new 
> server ). This is a common issue that can be caused by several causes. It's 
> not related specifically to dspace. Just try the steps you see below and 
> keep us updated here in the list.
>
>  
>
> On the old dspace Server execute (Double check the pg_dump path. 9.6?):
> 1) cd "C:\Program Files\PostgreSQL\9.6\bin"
> 2) .\pg_dump -U postgres -W -h localhost -Fc -v -C -c --if-exists -E UTF8 
> -d dspace -f dspace-63.sql
> 3) Move dspace-63.sql file to the new dspace server
>
> On the new dspace server execute:
> 1) psql --username=postgres dspace
> 2) DROP EXTENSION pgcrypto;
> 3) DROP SCHEMA extensions;
> 4) \q
> 5) cd "C:\Program Files\PostgreSQL\13\bin"
> 6) .\pg_restore -U postgres -W -h localhost -v -e -c --if-exists -d dspace 
> dspace-63.sql
> 7) psql --username=postgres dspace
> 8) \dn
> 9) \dx
> 10) \q
>
>  
>
> ** The -e (--exit-on-error) you see in step 6 should give you a clue why 
> the old or the new restoring was/is failing so watch for any error and post 
> what it shows here to know exactly what's happening in your server 
> (Hopefully not).
>
>  
>
> Regards,
>
>   
>
> On Friday, February 3, 2023 at 1:54:34 AM UTC+3 jacob.cameron wrote:
>
> Hi Mohammad,
>
>  
>
> I’ve actually done that prior to this and still get a large number of 
> errors no matter whether I import using psql or pg_restore for an sql or 
> plain text dump.
>
>  
>
> I’m wondering if I need to upgrade from 9.6 to 13 in Postgres before it’ll 
> fix it.  I’m sure I had to do that when I went from 1.8.3 to 6 originally. 
> I could be wrong.  That was along time ago.  But I have something about 
> that in old notes from that upgrade.
>
>  
>
> Jake
>
>  
>
> --
>
> Jake Cameron, BCS(UNB)
>
> Systems Support Specialist III
>
> Information Systems and Technical Services University of Lethbridge Library
>
> Phone:(403)329-2756 <(403)%20329-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. 

[dspace-tech] Re: Backend 7.1 and frontend 7.4

['Tim Donohue' via DSpace Technical Support]

Hi,

In the DSpace 7 set of releases (7.0-7.4 so far), the minor releases all 
contain new features.  This we necessary in order to migrate 6.x features 
to 7.x over several releases.  However, it does mean that 7.x releases are 
*not* compatible with one another.  You must be running a 7.4 backend to 
run a 7.4 frontend... as 7.4 has several new features not available in 7.1 
(which require new functionality on the backend as well).

For more information on why we had to take this direction with 7.x, 
see https://wiki.lyrasis.org/display/DSPACE/DSpace+Release+7.0+Status

Tim

On Monday, February 6, 2023 at 7:38:19 AM UTC-6 gabrielvi...@gmail.com 
wrote:

> Hey everyone! I'm using a backend in Dspace 7.1 and a frontend in 7.4. I 
> have an Issue loading some components:
>
> Recent submissions (just have an infinity loading), browse by title and 
> browse by issue date ( just don't appear, and get a red message)
>
> What it can be? Does not have compatibility between versions?
>
>

-- 
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/37c27abf-6b65-4d93-ac38-7948fcc460ebn%40googlegroups.com.

Re: [dspace-tech] Restore deleted community

['Tim Donohue' via DSpace Technical Support]

Hi Sonia,

When objects are deleted, they are permanently removed from DSpace.  So, DSpace 
doesn't have an "undo" option for deletion.  That said, you can restore objects 
individually if you do regular backups using AIP Backup & Restore.  The AIP 
backup process allows you to restore a single Community/Collection or Item via 
it's Archival Information Package (AIP): 
https://wiki.lyrasis.org/display/DSDOC7x/AIP+Backup+and+Restore   That said, it 
requires exporting AIPs out of DSpace and storing them somewhere in case they 
are necessary for restoration.

Good luck and let us know on this list if you have other questions.

Tim


From: dspace-tech@googlegroups.com  on behalf of 
Sonia R Thompson 
Sent: Monday, January 30, 2023 4:58 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Restore deleted community

Good morning all,

Is it possible to roll back the deletion of a community from within the DSpace 
v7.3 application without having to restore the full database from backup?

Regards
Sonia

--
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/661f74f4-d0fc-49b3-8787-95a983e85321n%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/PH0PR22MB32743EA133EB3350CD7EF9B5EDD39%40PH0PR22MB3274.namprd22.prod.outlook.com.

Re: [dspace-tech] Issue with database migration 6.3 to 7.4

['Tim Donohue' via DSpace Technical Support]

Hi Sean,

This issue is a known issue which some sites encounter during the upgrade to 
DSpace 7 if they have previously ignored migrations which never ran during a 
past 5.x ->6.x upgrade?.  Essentially, to summarize, there are two "5.7" 
migrations which can fail during the upgrade to 7.x... these migrations are 
obsolete? and can be skipped over.

There's a thread discussing this on dspace-tech here, along with "workarounds" 
to skip the two problematic 5.7 migrations: 
https://groups.google.com/g/dspace-tech/c/PlOA1WMvd4M/m/eBVE5RfhBgAJ

There's also a fix for this coming in the 7.5 release.  In 7.5 (due Feb 20) we 
have a new "./dspace database skip" command which can be used to skip 
problematic migrations.  See the PR at 
https://github.com/DSpace/DSpace/pull/8611

So, you are not the first person to hit this migration bug. An easier fix is 
coming in 7.5... but in the meantime, you can use the dspace-tech link above to 
workaround the issue if you want to upgrade immediately to 7.4.

Tim

From: dspace-tech@googlegroups.com  on behalf of 
Cameron, Jacob 
Sent: Friday, January 27, 2023 12:46 PM
To: Sean Carte 
Cc: DSpace Technical Support 
Subject: RE: [dspace-tech] Issue with database migration 6.3 to 7.4


I’ve tried importing with the postgres account, using an elevated command 
prompt, in pgadmin and they are all giving the same errors.  It’s still 
failing.  I’m at a loss now.  There’s a ton of tables missing when it finishes 
importing.



--

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: Sean Carte 
Sent: January 27, 2023 12:31 AM
To: Cameron, Jacob 
Cc: DSpace Technical Support 
Subject: Re: [dspace-tech] Issue with database migration 6.3 to 7.4



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 had a similar problem with a database I was trying to import: many /N invalid 
commands. I gave my user superuser privileges and was able to import the dump 
without those errors.



Sean



On Thu, 26 Jan 2023 at 23:06, Cameron, Jacob 
mailto:jacob.came...@uleth.ca>> wrote:

Hi Everyone,

I exported my DSpace 6.3 database, imported it on the new server running 7.4.  
There were thousands of invalid command /N that showed up during the import and 
lots of other ERROR: relation "xxx" does not exist.

I did try running dspace database migrate ignored afterwards and was given some 
errors.

I checked the DSpace log and there was some messaged about being unable to find 
the bean by name or database but that may have been when I deleted my old 
database before recreating the new one to import to.

Any thoughts or suggestions would be welcome.  I've seen a few suggestions out 
there and I've tried them, but I haven't had any luck.

C:\DSpace\bin>dspace database migrate ignored
Using DSpace installation in: C:\DSpace

Database URL: jdbc:postgresql://localhost:5432/dspace
Migrating database to latest version AND running previously "Ignored" 
migrations... (Check logs for details)
Migration exception:
java.sql.SQLException: Flyway migration error occurred
at 
org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:785)
at 
org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:672)
at org.dspace.storage.rdbms.DatabaseUtils.main(DatabaseUtils.java:195)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at 
org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:277)
at 
org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:133)
at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:98)
Caused by: org.flywaydb.core.internal.command.DbMigrate$FlywayMigrateException: 
Migration 
V5.7_2017.04.11__DS-3563_Index_metadatavalue_resource_type_id_column.sql failed
-
SQL State  : 42703
Error Code : 0
Message

Re: [dspace-tech] Re: DB Schema / Data model for Dspace 7

['Tim Donohue' via DSpace Technical Support]

Hi Jorge,

As of DSpace 6 (and above), Communities & Collections have metadata just like 
Items.  So that means the Community/Collection name (or title) is stored in a 
"dc.title" metadata field linked to the Community/Collection, in the same way 
that an Item's name (or title) is also stored in a "dc.title" metadata field.

The same is also true for other metadata related to Communities/collections.  
The description for each is stored in "dc.description" metadata, etc.

DSpace 7 continues this same pattern as DSpace 6.  There's no major changes to 
the core database table (that I can recall) in DSpace 7, just some new tables 
added to support features new to DSpace 7.

Tim

From: dspace-tech@googlegroups.com  on behalf of 
Jorge Costa 
Sent: Friday, January 27, 2023 3:35 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Re: DB Schema / Data model for Dspace 7

Hi Tim
Thanks for the quick reply , I will have a look and see if i can successfully 
run that tool to generate a diagram.
Just a quick question and  only reply if you got this on the tip of your 
tongue where on earth is a collection/community name stored in this new 
structure ? I cant , for the life of me , find it ! Its vexing !


On Thursday, January 26, 2023 at 7:52:19 PM UTC Tim Donohue wrote:
Hi,

As you correctly noted, the latest schema diagram we have is for DSpace 6: 
https://wiki.lyrasis.org/display/DSDOC7x/Storage+Layer   This diagram is 
"semi-accurate" for DSpace 7, as v7 uses the same general table structure as 
v6... with a few new tables added to v7 to specifically support Configurable 
Entities & other new features in v7.

Unfortunately, we've not had a volunteer to help us regenerate that fancy 
diagram in the documentation (the previous v6 diagram was created with a paid 
tool).  If anyone is interested in helping generate a pretty diagram for v7, 
we'd appreciate volunteers.

In the meantime, there are many free database tools which can generate an 
interactive ERD (Entity Relationship Diagram) if you just point it at your 
database.  One I've used in the past is pgAdmin 4 
(https://www.pgadmin.org/docs/pgadmin4/6.18/erd_tool.html). To get a 
dynamically built diagram for DSpace 7, you could point pgAdmin 4 against a 
DSpace 7 (Postgres) database, and use its built in ERD Tool.  The advantage to 
this is that you no longer are dealing with a static image file, the diagram is 
interactive & you can easily zoom in to get as much  detail on each table as 
you wish.

Tim

On Wednesday, January 25, 2023 at 5:30:28 AM UTC-6 jorge...@gmail.com wrote:
Hi.
Could I please get the db schema/ data model for Dspace 7 ?

Why ?

We are a large institution with various departments and are required to provide 
quarterly updates per departments. To this end we run SQL queries against the 
database.
We have preset queries which we used in Dspace 4 , which , with a press of a 
button spew out the required information.
These queries/selects obviously no longer work after our migration to dspace 7.
To assist in the "correction" of the queries I was asked to provide the schema 
... the relationships between the tables in the actual database and what they 
hold.

I did attempt to find this on my own , but on the wiki the closest I found was 
dspace 6 schema .
Are they the same ?


--
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/cd90f361-4b13-44af-be0f-0727f076f7ccn%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/PH0PR22MB3274F2D6200162F131E8EAE5EDCC9%40PH0PR22MB3274.namprd22.prod.outlook.com.

[dspace-tech] Re: DB Schema / Data model for Dspace 7

['Tim Donohue' via DSpace Technical Support]

Hi,

As you correctly noted, the latest schema diagram we have is for DSpace 
6: https://wiki.lyrasis.org/display/DSDOC7x/Storage+Layer   This diagram is 
"semi-accurate" for DSpace 7, as v7 uses the same general table structure 
as v6... with a few new tables added to v7 to specifically support 
Configurable Entities & other new features in v7.

Unfortunately, we've not had a volunteer to help us regenerate that fancy 
diagram in the documentation (the previous v6 diagram was created with a 
paid tool).  If anyone is interested in helping generate a pretty diagram 
for v7, we'd appreciate volunteers.

In the meantime, there are many free database tools which can generate an 
interactive ERD (Entity Relationship Diagram) if you just point it at your 
database.  One I've used in the past is pgAdmin 4 
(https://www.pgadmin.org/docs/pgadmin4/6.18/erd_tool.html). To get a 
dynamically built diagram for DSpace 7, you could point pgAdmin 4 against a 
DSpace 7 (Postgres) database, and use its built in ERD Tool.  The advantage 
to this is that you no longer are dealing with a static image file, the 
diagram is interactive & you can easily zoom in to get as much  detail on 
each table as you wish.

Tim

On Wednesday, January 25, 2023 at 5:30:28 AM UTC-6 jorge...@gmail.com wrote:

> Hi.
> Could I please get the db schema/ data model for Dspace 7 ?
>
> Why ?
>
> We are a large institution with various departments and are required to 
> provide quarterly updates per departments. To this end we run SQL queries 
> against the database.
> We have preset queries which we used in Dspace 4 , which , with a press of 
> a button spew out the required information.
> These queries/selects obviously no longer work after our migration to 
> dspace 7.
> To assist in the "correction" of the queries I was asked to provide the 
> schema ... the relationships between the tables in the actual database and 
> what they hold.
>
> I did attempt to find this on my own , but on the wiki the closest I found 
> was dspace 6 schema .
> Are they the same ?
>
>

-- 
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/43e9ad2e-99e4-4234-8241-c3d95518b810n%40googlegroups.com.

[dspace-tech] Re: Problem Disseminating DSpace SITE

['Tim Donohue' via DSpace Technical Support]

Hi,

Based on the initial error "stacktrace" it looks like the error begins here:
https://github.com/DSpace/DSpace/blob/dspace-6.4/dspace-api/src/main/java/org/dspace/content/packager/PackageUtils.java#L822

The error results in a NullPointerException which seems to imply that the 
"groupName" it encounters is either empty string or null (missing).  

Maybe somehow your database has a Group that has *no name*?  That shouldn't 
be possible in DSpace, but it almost sounds like what has occurred here.

To see if you have a nameless Group, you'd want to look in your 
"epersongroup" database table to see if there's an entry in there with a 
null or empty "name" column.  If you find one, you can give it a name (even 
just call it "unnamed" or something) and try the export again.

If you have other questions, let us know on this list.

Tim

On Thursday, January 26, 2023 at 7:49:11 AM UTC-6 itani...@gmail.com wrote:

> [UPDATE]
> Changing the type to METS example /data/bin/dspace packager -d -a -t METS 
> -e dspace@xx   -i 10938/0 /data/BACKUP/aip-backup/dspace-aip.zip
>
> worked!
>
> any idea why AIP is not working?
>
> On Wednesday, January 25, 2023 at 4:14:12 PM UTC+2 Saad Itani wrote:
>
>> Dears we recently updated DSPACE from 5.x to 6.4 and the site is up and 
>> running smoothly, however I am stuck in a problem regarding export of AIP.
>>
>> Info:
>> DSpace version:  6.4
>>
>> If I run this command, I get the following error:
>>
>> /data/bin/dspace packager -d -a -t AIP -e dsp...@xx.com -i 10938/0 
>> dspace-aip.zip
>>
>> Warning at xsl:stylesheet on line 14 column 35
>>   Unrecognized version 1.1: treated as 1.0
>>
>> Disseminating DSpace SITE [ hdl=10938/0 ] to dspace-aip.zip
>>
>> Also disseminating all child objects (recursive mode)..
>> This may take a while, please check your logs for ongoing status while we 
>> process each package.
>> Exception: Failed to export Roles via packager (see wrapped error message 
>> for more details)
>> org.dspace.content.crosswalk.CrosswalkInternalException: Failed to export 
>> Roles via packager (see wrapped error message for more details)
>> at 
>> org.dspace.content.crosswalk.RoleCrosswalk.disseminateElement(RoleCrosswalk.java:236)
>> at 
>> org.dspace.content.packager.AbstractMETSDisseminator.crosswalkToMetsElement(AbstractMETSDisseminator.java:1356)
>> at 
>> org.dspace.content.packager.AbstractMETSDisseminator.makeMdSec(AbstractMETSDisseminator.java:626)
>> at 
>> org.dspace.content.packager.AbstractMETSDisseminator.addToAmdSec(AbstractMETSDisseminator.java:739)
>> at 
>> org.dspace.content.packager.AbstractMETSDisseminator.addAmdSec(AbstractMETSDisseminator.java:765)
>> at 
>> org.dspace.content.packager.AbstractMETSDisseminator.makeManifest(AbstractMETSDisseminator.java:862)
>> at 
>> org.dspace.content.packager.AbstractMETSDisseminator.writeZipPackage(AbstractMETSDisseminator.java:334)
>> at 
>> org.dspace.content.packager.AbstractMETSDisseminator.disseminate(AbstractMETSDisseminator.java:271)
>> at 
>> org.dspace.content.packager.DSpaceAIPDisseminator.disseminate(DSpaceAIPDisseminator.java:165)
>> at 
>> org.dspace.content.packager.AbstractPackageDisseminator.disseminateAll(AbstractPackageDisseminator.java:102)
>> at org.dspace.app.packager.Packager.disseminate(Packager.java:642)
>> at org.dspace.app.packager.Packager.main(Packager.java:461)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at 
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> at 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at 
>> org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229)
>> at 
>> org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81)
>> Caused by: org.dspace.content.packager.PackageException: 
>> java.lang.NullPointerException, Reason: java.lang.NullPointerException
>> at 
>> org.dspace.content.packager.RoleDisseminator.writeToStream(RoleDisseminator.java:255)
>> at 
>> org.dspace.content.packager.RoleDisseminator.disseminate(RoleDisseminator.java:106)
>> at 
>> org.dspace.content.crosswalk.RoleCrosswalk.disseminateElement(RoleCrosswalk.java:205)
>> ... 17 more
>> Caused by: java.lang.NullPointerException
>> at java.util.regex.Matcher.getTextLength(Matcher.java:1283)
>> at java.util.regex.Matcher.reset(Matcher.java:309)
>> at java.util.regex.Matcher.(Matcher.java:229)
>> at java.util.regex.Pattern.matcher(Pattern.java:1093)
>> at 
>> org.dspace.content.packager.PackageUtils.translateGroupNameForExport(PackageUtils.java:822)
>> at 
>> org.dspace.content.packager.RoleDisseminator.writeGroup(RoleDisseminator.java:307)
>> at 
>> 

[dspace-tech] Re: OCR Searchable pdf content in dspace 7+

['Tim Donohue' via DSpace Technical Support]

Hi,

For full-text indexing/searching in DSpace, you need to enable/run the 
"Media 
filters": 
https://wiki.lyrasis.org/display/DSDOC7x/Mediafilters+for+Transforming+DSpace+Content

These are scripts that can extract text out of text-based content (like 
OCR'd PDFs, Word docs, etc).

Most sites choose to run those on a scheduled basis (e.g. once per day, or 
a few times a day) via a Cron Job.  See this 
guide: https://wiki.lyrasis.org/display/DSDOC7x/Scheduled+Tasks+via+Cron

If you have more questions, let us know on this list.

Tim

On Thursday, January 19, 2023 at 12:51:29 AM UTC-6 ruchi...@gmail.com wrote:

> I have installed dspace 7.3 on ubuntu 22.04. 
> Kindly help me to make pdf or other file OCR searchable ie. can be 
> searched with any content in pdf or file and not only from keywords, title, 
> author etc.
>
> Please let me know the settings or steps to be changed in the 
> configuration files.
>

-- 
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/62d0e5bd-7293-4f16-b1e1-908d765a2c39n%40googlegroups.com.

Re: [dspace-tech] "Initial Questions" step in DSpace 7

['Tim Donohue' via DSpace Technical Support]

Hi David,

No, the "Initial Questions" step doesn't exist in DSpace 7.  We dropped it 
because the submission form has moved to a single page (all fields/sections are 
on one webpage).  In DSpace 6, this "Initial Questions" step essentially loaded 
the next page of the form based on the answers provided.  In DSpace 7, that's 
not easy to achieve because the entire form loads at once & users can begin 
interacting with any step/section they want (there's no guarrantee they'd start 
with the "initial questions" step if it appeared).

It is​ possible to dynamically add/remove individual metadata fields (see "Item 
Type Based Metadata Collection" at 
https://wiki.lyrasis.org/display/DSDOC7x/Submission+User+Interface#SubmissionUserInterface-ItemtypeBasedMetadataCollection

It is also possible to create optional​ (mandatory=false) steps/sections which 
do not appear by default, but can be added to the form using the "Add more +" 
button.  But, this requires the user to click on the "Add more +" button to 
access those optional steps.

However, at least at this time, there's no way to dynamically insert entirely 
new steps/sections based on the metadata entered in other steps/sections.  
Instead, we'd recommend looking at using "Item Type Based Metadata Collection" 
to dynamically insert one (or many) fields based on the value of "dc.type".

If this doesn't align with your needs or use cases, then you are welcome to 
submit a new feature request ticket to our ticketing system at 
https://github.com/DSpace/dspace-angular/issues   I'd ask that you describe 
your use case better (perhaps based on how you used this feature in 6.x) and 
why DSpace 7 doesn't align well with this use case.   We can then ask around 
and see if others have a similar need (which would increase the priority) 
and/or find a volunteer to investigate possible solutions for v7.

Tim

From: dspace-tech@googlegroups.com  on behalf of 
David P. Steelman 
Sent: Wednesday, January 18, 2023 12:14 PM
To: dspace-tech@googlegroups.com 
Subject: [dspace-tech] "Initial Questions" step in DSpace 7

All,

Is the "Initial Questions" step functionality from DSpace 6 available in DSpace 
7?

There is a brief mention of it on the "Metadata Recommendations" Confluence 
page (https://wiki.lyrasis.org/display/DSDOC7x/Metadata+Recommendations), but I 
suspect that is just an oversight.

We are particularly interested in any DSpace 7 mechanism to add and remove 
individual steps/sections from the submissions page dynamically, based on user 
input.

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%2BmHiJacSMBNPr9VMAJE_D58U1TH2bi5BoqZnPXYbSibTx3qNA%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/PH0PR22MB3274D692D0E5FC0DA79751CBEDC79%40PH0PR22MB3274.namprd22.prod.outlook.com.

[dspace-tech] Re: DSpace 7.3 Bulk Upload

['Tim Donohue' via DSpace Technical Support]

Hi Tianyi,

The Batch Import / Bulk Upload command wasn't available in the DSpace 7 
Admin UI until the 7.4 release.  See the release notes 
at 
https://wiki.lyrasis.org/display/DSDOC7x/Release+Notes#ReleaseNotes-7.4ReleaseNotes

So, for this feature to work from the Admin UI, you'd need to upgrade to 
7.4.  In 7.3 though, it should work from the commandline (only).

Tim

On Monday, January 16, 2023 at 3:33:53 PM UTC-6 DSpace Technical Support 
wrote:

> Hi Tianyi,
>
> What errors are you getting when you try the CLI command? The thing that 
> stands out to me first is that I don't think you should use the = in your 
> parameters?
> When trying from a 7.x UI, make sure you are logged in as an 
> administrator. You can find the button in the sidebar menu:
>
> Hope this helps!
>
> Kim
>
>
> On Tuesday, January 17, 2023 at 2:11:32 AM UTC+13 gutia...@gmail.com 
> wrote:
>
>> Hi all,
>>
>> I can't see the Batch Import from UI and also have no luck running the 
>> "import' command
>>
>> I follow the guide Importing and Exporting Items via Simple Archive 
>> Format 
>> 
>>
>> The command I used:
>> [dspace]/bin/dspace import --add --eperson=j...@user.com 
>> --collection=CollectionID --source=items_dir --mapfile=mapfile
>>
>> Please advise.
>>
>> Thank you,
>> tianyi
>>
>

-- 
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/75a3db27-0775-447d-9f82-be0d6388d458n%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.

[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 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.

Re: [dspace-tech] Database migrate from DSpace 6 to DSpace 7.4

['Tim Donohue' via DSpace Technical Support]

All,

Just to follow up on this thread, as of today the new "./dspace database 
skip" command has been added to the codebase.  It will be available in 7.5 
(due in Feb).   See https://github.com/DSpace/DSpace/pull/8611

In the meantime, those INSERT commands (documented by Dominik in this email 
thread) are the easiest way to solve this issue for any institutions who 
encounter this problem in 7.4 or below.  (The new "skip" command runs those 
same INSERT commands in an easier fashion)

Tim
On Wednesday, December 14, 2022 at 9:54:03 AM UTC-6 Tim Donohue wrote:

> All,
>
> Just to follow-up on this thread, as several users have hit these same 
> issues in the upgrade from 6.x -> 7.x, I'm working on creating an new 
> "./dspace database skip" command which allows you to easily *skip* 
> failing/problematic (older) migrations. I'm hoping this new command will be 
> available in the upcoming 7.5 release (due in Feb). The early code is at 
> https://github.com/DSpace/DSpace/pull/8611 (and testers are welcome if 
> this is of interest to you).
>
> This new "skip" command will just be an easier way to run the INSERT 
> command(s) that Dominik suggested earlier in this thread.  In the meantime, 
> those INSERT commands are the easiest way to solve this issue. Thanks to 
> Dominik for figuring out the correct solution.
>
> Tim
>
> On Tuesday, December 6, 2022 at 9:55:44 AM UTC-6 banjia...@gmail.com 
> wrote:
>
>> Thank you so much Dominik, it worked. 
>>
>> On Tue, 6 Dec 2022 at 15:48, ZiGi  wrote:
>>
>>> Hi,
>>> Just use command: *select installed_rank from schema_version; *check 
>>> which number is the highest and use one bigger in query.
>>> For example: the biggest number on installed_rank is 32 so your query 
>>> should looks like this:
>>>  
>>> INSERT INTO schema_version 
>>> (installed_rank,version,description,type,script,checksum,installed_by,installed_on,execution_time,success)
>>>  
>>> values (*33*,'5.7.2017.04.11','DS-3563 Index metadatavalue resource 
>>> type id 
>>> column','SQL','V5.7_2017.04.11__DS-3563_Index_metadatavalue_resource_type_id_column.sql',-1,'dspace','2022-12-06
>>>  
>>> 12:32:09.793369',0,true);
>>>
>>> INSERT INTO schema_version 
>>> (installed_rank,version,description,type,script,checksum,installed_by,installed_on,execution_time,success)
>>>  
>>> values (*34*,'5.7.2017.05.05','DS 3431 Add Policies for 
>>> BasicWorkflow','JDBC','DS 3431 Add Policies for 
>>> BasicWorkflow',-1,'dspace','2022-12-06 12:32:09.793369',0,true);
>>>
>>> wtorek, 6 grudnia 2022 o 14:44:09 UTC+1 banjia...@gmail.com napisał(a):
>>>
 Hi Dominik, when i ran the query above I got this error

 ERROR:  duplicate key value violates unique constraint 
 "schema_version_pk"
 DETAIL:  Key (installed_rank)=(27) already exists.

 ERROR:  duplicate key value violates unique constraint 
 "schema_version_pk"
 DETAIL:  Key (installed_rank)=(29) already exists.

 Please am I missing something?

 On Tue, 6 Dec 2022 at 13:38, ZiGi  wrote:

> Nevermind,
> I *SOLVED* this problem by adding two rows to schema_version in 
> dspace database:
>
> *INSERT INTO schema_version 
> (installed_rank,version,description,type,script,checksum,installed_by,installed_on,execution_time,success)
>  
> values (27,'5.7.2017.04.11','DS-3563 Index metadatavalue resource type id 
> column','SQL','V5.7_2017.04.11__DS-3563_Index_metadatavalue_resource_type_id_column.sql',-1,'dspace','2022-12-06
>  
> 12:32:09.793369',0,true);*
>
> *INSERT INTO schema_version 
> (installed_rank,version,description,type,script,checksum,installed_by,installed_on,execution_time,success)
>  
> values (29,'5.7.2017.05.05','DS 3431 Add Policies for 
> BasicWorkflow','JDBC','DS 3431 Add Policies for 
> BasicWorkflow',-1,'dspace','2022-12-06 12:32:09.793369',0,true);*
>
> after that, run command  *./dspace database repair *and then  *./dspace 
> database migrate ignored *. In my case everythig works now.
> Dominik
>
> wtorek, 6 grudnia 2022 o 12:31:40 UTC+1 ZiGi napisał(a):
>
>> Dear Tim,
>> Maybe you could send me the full query which I could use to insert 
>> missing row? Becouse as I said I don't have  anything 
>> like  "V5.7.2017.05.05" or 
>> "V5_7_2017_05_05__DS_3431_Add_Policies_for_BasicWorkflow" on my 
>> schema_version.
>> Thanks,
>> Dominik
>> wtorek, 6 grudnia 2022 o 10:31:20 UTC+1 ZiGi napisał(a):
>>
>>> Hi,
>>> I'm not sure you check the attachment in my first e-mail but I done 
>>> everything one more time. So I don't have anything like  
>>> "V5.7.2017.05.05" 
>>> or 
>>> "V5_7_2017_05_05__DS_3431_Add_Policies_for_BasicWorkflow" on my 
>>> schema_version, you can check that on screenshot in attachment but if I 
>>> run 
>>> ./dspace database info there 
>>> is  "V5_7_2017_05_05__DS_3431_Add_Policies_for_BasicWorkflow" with 

[dspace-tech] Re: Dspace security matters

['Tim Donohue' via DSpace Technical Support]

Hi,

Since you are on DSpace 6.3, I'd recommend minimally upgrading to DSpace 
6.4 as it includes a large number of security fixes to the 6.x platform.  
See the release notes at 
https://wiki.lyrasis.org/display/DSDOC6x/Release+Notes#ReleaseNotes-6.4ReleaseNotes

That said, it's worth being aware that 6.x is nearly "end of life".  
Announcements went across these mailing lists last year.  Here's the end of 
life 
information: 
https://wiki.lyrasis.org/display/DSPACE/Support+for+DSpace+5+and+6+is+ending+in+2023

The latest version of DSpace is 7.4 (and 7.5 is coming soon in February).  
It is the most secure of our releases.So, you may wish to consider an 
upgrade at some point (this is a major upgrade as there is a brand new User 
Interface, etc).  See release notes 
at https://wiki.lyrasis.org/display/DSDOC7x/Release+Notes

If you have additional questions, let us know on this list.  If you wish to 
report security issues, see our Software support policy for how to do 
so: https://wiki.lyrasis.org/display/DSPACE/DSpace+Software+Support+Policy

Thanks,

Tim Donohue

On Monday, January 9, 2023 at 6:35:12 PM UTC-6 noorhaf...@iium.edu.my wrote:

> In addition. we are running Dspace on Ubuntu 18.04.2 LTS
>
>
>
> On Tuesday, January 10, 2023 at 8:30:43 AM UTC+8 Noorhafizah Mohd Akil 
> wrote:
>
>> Hello, 
>> Dear all.
>>
>> I have a security concern with DSpace. Our web server was the victim of a 
>> web shell assault that provided backdoor access to the web server 
>> directory. We are still in the inquiry phase right now.
>>
>> Our system currently utilizes Dspace 6.3, and the most recent version I 
>> could find was 7.4.
>>
>> Does version 6.3 require any patches throughout the upgrade of the 
>> version.
>>
>> 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/83fb6838-37b5-43a9-87e0-2d8adc7cb89en%40googlegroups.com.

[dspace-tech] Re: Customizing "Browse by Author" DSPACE 7.x

['Tim Donohue' via DSpace Technical Support]

Hi,

Unfortunately, I don't think that's possible in DSpace at this time.  Those 
Author fields in the "Browsing by Author" page are simple metadata values 
(as Browse by Author is simply letting you browse all Items by 
"dc.contributor.author" and/or "dc.creator" field values). So, those values 
do *not* correspond with Person Entities.  That means there's no additional 
metadata values that can be displayed, as all "Browse" interfaces in DSpace 
just use simple metadata fields at this time (e.g. Browse by Title is 
browsing all Items by "dc.title", Browse by Subject is browsing all Items 
by "dc.subject", etc.)

Tim

On Wednesday, December 21, 2022 at 6:45:24 AM UTC-6 vzapate...@gmail.com 
wrote:

> In this page query all documents in the index for each author name. It 
> showed author name and all author's documents counter.
>
>
> [image: BrowseByAuthor.png]
> How could I add some metadata values associated to "Person entity" in this 
> author's list inside magenta rectangles? Exists any configuration in 
> discovery.xml to do this? Should I customize frontend and backend? I can't 
> find how to get it.
>
> 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/58c0f733-013c-4b0e-b744-ebe360ebc02en%40googlegroups.com.

Re: [dspace-tech] DSpace 7.x Maximum size of abstract field?

['Tim Donohue' via DSpace Technical Support]

Hi,

All metadata field values in DSpace are stored in a database column (see 
"text_value" column of "metadatavalue" table).  That database column uses the 
PostgreSQL "TEXT" data type, which is documented as having a 1GB limit: 
https://stackoverflow.com/a/39966079/3750035

Tim

From: dspace-tech@googlegroups.com  on behalf of 
P Z 
Sent: Friday, December 16, 2022 2:32 PM
To: DSpace Technical Support 
Subject: [dspace-tech] DSpace 7.x Maximum size of abstract field?

Hello everybody, please do you people know about it, or indicate me a reference 
on documentation?:

What is the maximum allowed size (in bytes) that can be stored in the 
dc.description.abstract field?

Is this limit applicable to any metadata field too?

In which file are the settings for max lenght of abstract field?

Thanks 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/3782303b-c0ce-4b5c-bedd-9e1cab3ea872n%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/PH0PR22MB3274FF714DD3D0D8C358BB0BEDE59%40PH0PR22MB3274.namprd22.prod.outlook.com.

Re: [dspace-tech] Batch import not insert all data in Mapfile

['Tim Donohue' via DSpace Technical Support]

Hi,

We don't have enough information to provide help.  What version of DSpace are 
you using?  What metadata is missing after the import?  How are you performing 
the import (are you running it via the commandline or via the UI, and what 
parameters are you adding to the command)?  Also, could you check your logs to 
see if any errors are written to the logs?

Here's a guide for how to find errors in logs: 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error

If you find more information on the errors thrown, we can provide more help.  
Unfortunately, it's not possible to help until we understand what errors you 
are seeing & what behavior is incorrect.

Finally, I will add that you MUST make sure the CSV is using metadata fields 
which exist in your DSpace site.  I notice one of the columns in your CSV is 
named "dc.description.identity".  Unless you've created that custom field in 
your DSpace site, it may not be a valide field. DSpace doesn't have a field of 
that name by default, so you won't be able to import metadata into that field 
until you create it.  For more information on the CSV format used for batch 
editing / adding, please see our documentation at 
https://wiki.lyrasis.org/display/DSDOC7x/Batch+Metadata+Editing#BatchMetadataEditing-CSVFormat

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

Tim

From: 'Noorhafizah Mohd Akil' via DSpace Technical Support 

Sent: Friday, December 16, 2022 1:11 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Batch import not insert all data in Mapfile


Hello,

I would like to ask for help from an expert regarding batch import.

I have prepared the data on the mapfile, but there are two problems occured.

1. not all data in the mapfile has successfully been inserted.
2. data that successfully been inserted does not sit in the correct metadata. 
for example in mapfile we map the data to dc.description.identifier, but it 
goes under ISSN metadata.

Example : https://studentrepo.iium.edu.my/handle/123456789/11152
Attached below is the example of mapfile.

Thank you 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/f0da59de-5765-4471-8153-7a333568d572n%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/PH0PR22MB3274261715A803C5E2020B52EDE69%40PH0PR22MB3274.namprd22.prod.outlook.com.

Re: [dspace-tech] DSPACE 7.4 webui.browse.link example

['Tim Donohue' via DSpace Technical Support]

Hi Vincente,

The "webui.browse.link.*" settings in your dspace.cfg/local.cfg do not yet work 
in DSpace 7.x.  They were an older DSpace 6.x feature, which we are still 
working to migrate forward.  Essentially, it was a way to hyperlink metadata 
fields (displayed on the Item page or similar) to automatically send you to the 
browse results for that field.  For example, clicking on an Author field that 
had "Donohue, Tim" would send you to the browse results for all Items that had 
"Author: Donohue, Tim".  See docs at 
https://wiki.lyrasis.org/display/DSDOC6x/Configuration+Reference#ConfigurationReference-LinkstoOtherBrowseContexts

This feature is being moved forward into 7.x, so it may exist in the upcoming 
7.5 release.  Here's the early work on it: 
https://github.com/DSpace/dspace-angular/pull/1972

With regards to the "Browse by Author" pages, you can change the number of 
results shown by using the Settings button (in the right corner), as it will 
let you change the "Results per page".  By default, up to 20 results will be 
shown when you are looking at an Author entry.

I'm not sure if that answers your questions or not.  If not, let us know on 
this list.

Tim


From: dspace-tech@googlegroups.com  on behalf of 
Vicente Zapatero Martin 
Sent: Thursday, December 15, 2022 6:17 AM
To: DSpace Technical Support 
Subject: [dspace-tech] DSPACE 7.4 webui.browse.link example

I'm trying to modify some functionality in "All DSpace > By Author". I want to 
modify number of documents in author entries.

Searching in code I have seen a reference to "webui.browse.link" and I don't 
understand where and what it is used for? I have been searching in wiki but I 
don't find but what does it do? Is there any example where to see how it works?

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/efa32d69-4663-46c3-a293-dd67177b1b5fn%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/PH0PR22MB32742D999067340D69B2F8F7EDE19%40PH0PR22MB3274.namprd22.prod.outlook.com.

Re: [dspace-tech] Database migrate from DSpace 6 to DSpace 7.4

['Tim Donohue' via DSpace Technical Support]

All,

Just to follow-up on this thread, as several users have hit these same 
issues in the upgrade from 6.x -> 7.x, I'm working on creating an new 
"./dspace database skip" command which allows you to easily *skip* 
failing/problematic (older) migrations. I'm hoping this new command will be 
available in the upcoming 7.5 release (due in Feb). The early code is 
at https://github.com/DSpace/DSpace/pull/8611 (and testers are welcome if 
this is of interest to you).

This new "skip" command will just be an easier way to run the INSERT 
command(s) that Dominik suggested earlier in this thread.  In the meantime, 
those INSERT commands are the easiest way to solve this issue. Thanks to 
Dominik for figuring out the correct solution.

Tim

On Tuesday, December 6, 2022 at 9:55:44 AM UTC-6 banjia...@gmail.com wrote:

> Thank you so much Dominik, it worked. 
>
> On Tue, 6 Dec 2022 at 15:48, ZiGi  wrote:
>
>> Hi,
>> Just use command: *select installed_rank from schema_version; *check 
>> which number is the highest and use one bigger in query.
>> For example: the biggest number on installed_rank is 32 so your query 
>> should looks like this:
>>  
>> INSERT INTO schema_version 
>> (installed_rank,version,description,type,script,checksum,installed_by,installed_on,execution_time,success)
>>  
>> values (*33*,'5.7.2017.04.11','DS-3563 Index metadatavalue resource type 
>> id 
>> column','SQL','V5.7_2017.04.11__DS-3563_Index_metadatavalue_resource_type_id_column.sql',-1,'dspace','2022-12-06
>>  
>> 12:32:09.793369',0,true);
>>
>> INSERT INTO schema_version 
>> (installed_rank,version,description,type,script,checksum,installed_by,installed_on,execution_time,success)
>>  
>> values (*34*,'5.7.2017.05.05','DS 3431 Add Policies for 
>> BasicWorkflow','JDBC','DS 3431 Add Policies for 
>> BasicWorkflow',-1,'dspace','2022-12-06 12:32:09.793369',0,true);
>>
>> wtorek, 6 grudnia 2022 o 14:44:09 UTC+1 banjia...@gmail.com napisał(a):
>>
>>> Hi Dominik, when i ran the query above I got this error
>>>
>>> ERROR:  duplicate key value violates unique constraint 
>>> "schema_version_pk"
>>> DETAIL:  Key (installed_rank)=(27) already exists.
>>>
>>> ERROR:  duplicate key value violates unique constraint 
>>> "schema_version_pk"
>>> DETAIL:  Key (installed_rank)=(29) already exists.
>>>
>>> Please am I missing something?
>>>
>>> On Tue, 6 Dec 2022 at 13:38, ZiGi  wrote:
>>>
 Nevermind,
 I *SOLVED* this problem by adding two rows to schema_version in dspace 
 database:

 *INSERT INTO schema_version 
 (installed_rank,version,description,type,script,checksum,installed_by,installed_on,execution_time,success)
  
 values (27,'5.7.2017.04.11','DS-3563 Index metadatavalue resource type id 
 column','SQL','V5.7_2017.04.11__DS-3563_Index_metadatavalue_resource_type_id_column.sql',-1,'dspace','2022-12-06
  
 12:32:09.793369',0,true);*

 *INSERT INTO schema_version 
 (installed_rank,version,description,type,script,checksum,installed_by,installed_on,execution_time,success)
  
 values (29,'5.7.2017.05.05','DS 3431 Add Policies for 
 BasicWorkflow','JDBC','DS 3431 Add Policies for 
 BasicWorkflow',-1,'dspace','2022-12-06 12:32:09.793369',0,true);*

 after that, run command  *./dspace database repair *and then  *./dspace 
 database migrate ignored *. In my case everythig works now.
 Dominik

 wtorek, 6 grudnia 2022 o 12:31:40 UTC+1 ZiGi napisał(a):

> Dear Tim,
> Maybe you could send me the full query which I could use to insert 
> missing row? Becouse as I said I don't have  anything 
> like  "V5.7.2017.05.05" or 
> "V5_7_2017_05_05__DS_3431_Add_Policies_for_BasicWorkflow" on my 
> schema_version.
> Thanks,
> Dominik
> wtorek, 6 grudnia 2022 o 10:31:20 UTC+1 ZiGi napisał(a):
>
>> Hi,
>> I'm not sure you check the attachment in my first e-mail but I done 
>> everything one more time. So I don't have anything like  
>> "V5.7.2017.05.05" 
>> or 
>> "V5_7_2017_05_05__DS_3431_Add_Policies_for_BasicWorkflow" on my 
>> schema_version, you can check that on screenshot in attachment but if I 
>> run 
>> ./dspace database info there 
>> is  "V5_7_2017_05_05__DS_3431_Add_Policies_for_BasicWorkflow" with 
>> status 
>> "Ignored". Any help will be  appreciated.
>>  Thanks,
>> Dominik
>>
>> poniedziałek, 5 grudnia 2022 o 16:44:15 UTC+1 Tim Donohue napisał(a):
>>
>>> Hi,
>>>
>>> This database migration error is one that some sites have 
>>> encountered after accidentally not running the "
>>> V5_7_2017_05_05__DS_3431_Add_Policies_for_BasicWorkflow" migration 
>>> during an older 5.x -> 6.x upgrade.   See this email thread: 
>>> https://groups.google.com/g/dspace-tech/c/F6ztOrBjXBA/m/fe3UP0_KAgAJ
>>>
>>> Luckily, this older migration is no longer valid so, if you 
>>> haven't run it already, it can now be skipped 

Re: [dspace-tech] Import and Export menus disappeared from DSpace 7.4 menu?

['Tim Donohue' via DSpace Technical Support]

Hi Paige,

Those import/export options still exist in DSpace 7.4.  However, they are 
obviously only available when you login as an Administrator.

If you are not seeing those options, I'm guessing maybe an error is occurring 
which is blocking them?  Try to follow our Troubleshooting guide to see if you 
can find any errors in your browser's devtools or the backend logs. 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

I just searched our tickets in case there's a reported bug here, and I also 
came across this one related to Shibboleth authentication. 
https://github.com/DSpace/dspace-angular/issues/1953   I just pulled it over to 
our 7.5 board in the hopes I can find a volunteer to fix it for that release.

Tim

From: dspace-tech@googlegroups.com  on behalf of 
Paige Morgan 
Sent: Tuesday, December 13, 2022 8:45 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Import and Export menus disappeared from DSpace 7.4 menu?


Up until recently, the side menu in DSpace 7.4 had options for importing and 
exporting -- you can see them in this video: 
https://www.youtube.com/watch?v=CjH8VS2WDjE

As of this morning, those options have disappeared -- though it looks like it's 
still possible to achieve the same functionality by starting with the process 
menu.

Is this a deliberate change? I haven't seen it mentioned as upcoming.

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
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%2BzEVdmX9dPYtJaAX6eS2-d%3DX%3DVOUPHO%2B3nQVM%3D9qqOJB67xRw%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/PH0PR22MB32748BD9B051A85B052E795CEDE39%40PH0PR22MB3274.namprd22.prod.outlook.com.

[dspace-tech] Re: Dspace7 works with ip but not with fqdn

['Tim Donohue' via DSpace Technical Support]

I forgot to add... if you are trying to simply make the UI available on the 
web, I'd highly recommend considering keeping the UI running on 
"localhost:4000" and using a Proxy to respond at https://[domain name].  
See our installation guide, step 8 "Add HTTPS support" for the Frontend 
install: 
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-FrontendInstallation
  
 (If for some reason you don't want HTTPS, you can follow those same 
instructions to setup HTTP...just make sure to use port 80 and ignore the 
HTTPS/SSL setup.  I don't recommend ever running in HTTP in production 
though, as that's a major security issue.)

Tim

On Monday, December 12, 2022 at 11:06:42 AM UTC-6 Tim Donohue wrote:

> Hi,
>
> The problem may be that you forgot to change the "dspace.ui.url" setting 
> (on the backend) to include the domain name.  When changing the URLs (from 
> IP to hostname), you have to ensure you update the URL settings in the 
> backend's "local.cfg" (both "dspace.server.url" and "dspace.ui.url") and 
> the frontend's "config.*.yml" (especially the "rest" section here).
>
> If that's not the problem, then I'd recommend following our 
> Troubleshooting guide to find the error *behind* that 500 exception.  A 500 
> exception can be thrown for a variety of reasons, so we'd need to determine 
> the exact reason why it's thrown in this scenario.  So, follow the 
> troubleshooting guide to see if there are other errors in the UI or backend 
> logs which provide more info: 
> https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)
>
> Tim
>
> On Monday, December 12, 2022 at 6:18:33 AM UTC-6 jorge...@gmail.com wrote:
>
>> http://[ip]:4000/home works just fine.
>> ITs integrated with my AD
>> I can log in , browse , deposit , delete etc
>>
>> http://[domain name]:4000/home
>> gets me 500 Service Unavailable
>>
>> /etc/hosts has an entry for the domain name to its ip
>>
>> The dns server has an entry
>>
>> What did I miss ?
>> 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/f7822876-1091-4425-a04a-34e9cab4f166n%40googlegroups.com.

[dspace-tech] Re: Dspace7 works with ip but not with fqdn

['Tim Donohue' via DSpace Technical Support]

Hi,

The problem may be that you forgot to change the "dspace.ui.url" setting 
(on the backend) to include the domain name.  When changing the URLs (from 
IP to hostname), you have to ensure you update the URL settings in the 
backend's "local.cfg" (both "dspace.server.url" and "dspace.ui.url") and 
the frontend's "config.*.yml" (especially the "rest" section here).

If that's not the problem, then I'd recommend following our Troubleshooting 
guide to find the error *behind* that 500 exception.  A 500 exception can 
be thrown for a variety of reasons, so we'd need to determine the exact 
reason why it's thrown in this scenario.  So, follow the troubleshooting 
guide to see if there are other errors in the UI or backend logs which 
provide more 
info: 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Tim

On Monday, December 12, 2022 at 6:18:33 AM UTC-6 jorge...@gmail.com wrote:

> http://[ip]:4000/home works just fine.
> ITs integrated with my AD
> I can log in , browse , deposit , delete etc
>
> http://[domain name]:4000/home
> gets me 500 Service Unavailable
>
> /etc/hosts has an entry for the domain name to its ip
>
> The dns server has an entry
>
> What did I miss ?
> 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/69464a95-17f5-4703-bdb8-d4fa12e05f81n%40googlegroups.com.

[dspace-tech] Re: installing dspace with mirage2 theme

['Tim Donohue' via DSpace Technical Support]

Again, as I mentioned in your other email thread 
, please try DSpace 
6.4 as it fixed several major Mirage 2 build issues in 
6.3.  https://wiki.lyrasis.org/display/DSDOC6x/Release+Notes

Tim

On Monday, December 12, 2022 at 6:18:33 AM UTC-6 chiko...@gmail.com wrote:

> hi
> can anyone help me with procedures to install dspace with mirage2 theme. I 
> think there are a  lot of updates which makes difficult to install 
> successful from old instruction posted on git hub 
> https://gist.github.com/otuoma/f7fe8dd108709407b9e885e7d32981d4
>
> Thanks[image: Capture.PNG]
>

-- 
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/b63f9806-93dc-4d04-a948-254d7025ce86n%40googlegroups.com.

[dspace-tech] Re: dspace mirage 2

['Tim Donohue' via DSpace Technical Support]

If I can recall correctly, DSpace 6.3 has encountered some major build 
issues with Mirage 2 as the build process was dependent on very old 
software.  See this ticket / PR: https://github.com/DSpace/DSpace/pull/8292

Those issues were fixed in DSpace 6.4 which was released this past 
July.  https://wiki.lyrasis.org/display/DSDOC6x/Release+Notes  (6.4 also 
fixed a number of security issues in 6.3)

So, if you need to continue to use DSpace 6 + Mirage 2, I'd recommend 
trying version 6.4.  Or, you could look at an upgrade to DSpace 7 in the 
future.

Tim
On Monday, December 12, 2022 at 6:18:33 AM UTC-6 chiko...@gmail.com wrote:

> I followed git instructions to install dspace with Mirage2 theme on: 
> https://gist.github.com/otuoma/f7fe8dd108709407b9e885e7d32981d4
>
> but it failed to build with error
> [ERROR] Failed to execute goal 
> de.saumya.mojo:gem-maven-plugin:1.0.6:initialize (default) on project 
> xmlui-mirage2: error in executing jruby: loading resource from classloader 
> failed: META-INF/jruby.home/bin/gem -> [Help 1]
>
> the following dependecies are installed:
> ruby: 3.1.3
> gem: 3.4.0
> nvm: 0.33.11
> node: 14.15.0
> npm: 6.14.8
> compass: 1.0.1
> sass: 3.4.25
> grunt-cli: 1.4.3
> grunt : 5.3
> bower 1.8.14
> i have edited pom file on xmlui-mirage2 to match the installed deps
>
> But when I run mvn package -Dmirage2.on=true -Dmirage2.deps.included=false
> it fails to build 
>
> [image: Capture.PNG]
>
>
>
> administrator@dspace:~/dspace-6.3-release$ mvn package -Dmirage2.on=true
> [INFO] Scanning for projects...
> [WARNING] The project org.dspace:dspace-parent:pom:6.3 uses prerequisites 
> which is only intended for maven-plugin projects but not for non 
> maven-plugin projects. For such purposes you should use the 
> maven-enforcer-plugin. See 
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] DSpace Parent Project 
>  [pom]
> [INFO] DSpace Addon Modules   
> [pom]
> [INFO] DSpace Kernel :: Additions and Local Customizations   
>  [jar]
> [INFO] DSpace XML-UI Mirage2 Theme :: Local Customisations   
>  [war]
> [INFO] DSpace XML-UI (Manakin) :: Local Customizations   
>  [war]
> [INFO] DSpace JSP-UI :: Local Customizations 
>  [war]
> [INFO] DSpace RDF :: Local Customizations 
> [war]
> [INFO] DSpace REST :: Local Customizations   
>  [war]
> [INFO] DSpace SWORD :: Local Customizations   
> [war]
> [INFO] DSpace SWORD v2 :: Local Customizations   
>  [war]
> [INFO] DSpace SOLR :: Local Customizations   
>  [war]
> [INFO] DSpace OAI-PMH :: Local Customizations 
> [war]
> [INFO] DSpace Assembly and Configuration 
>  [pom]
> [INFO]
> [INFO] --< org.dspace:dspace-parent 
> >--
> [INFO] Building DSpace Parent Project 6.3   
>  [1/13]
> [INFO] [ pom 
> ]-
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-java) @ 
> dspace-parent ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-versions) @ 
> dspace-parent ---
> [INFO]
> [INFO] -< org.dspace:modules 
> >-
> [INFO] Building DSpace Addon Modules 6.3 
> [2/13]
> [INFO] [ pom 
> ]-
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-java) @ modules ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-versions) @ 
> modules ---
> [INFO]
> [INFO] < org.dspace.modules:additions 
> >
> [INFO] Building DSpace Kernel :: Additions and Local Customizations 6.3 
>  [3/13]
> [INFO] [ jar 
> ]-
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-java) @ additions 
> ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-versions) @ 
> additions ---
> [INFO]
> [INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
> additions ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 1 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ 
> additions ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:2.7:testResources 
> (default-testResources) @ additions ---
> [INFO] Not copying test resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.5.1:testCompile