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] deleting multiple bitstreams results in locked bitstreams

[Paige Morgan]

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  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  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/CA%2BzEVd%3DbDHL_by_gX9gmJoBPgv0mtWKkw7tR42BJ0b6TqCy1cA%40mail.gmail.com.

Re: [dspace-tech] Re: DSpace 7.5 Problem with the cleanup operation

[Mark H. Wood]

On Mon, Jun 12, 2023 at 10:58:26PM -0700, Technologiczny Informator wrote:
> I reported this problem at the end of December last year, but no one 
> responded. That's why I'm writing again, because the problem has not 
> disappeared after updating to DSpace 7.5.
> Not only that ... I had the opportunity to update to version 7.5 on a 
> completely different database than mine. Her assetstore folder is over 170 
> GB. The owner of this DSpace wanted to split the database into two separate 
> instances. This is what happened and in each of them a large number of 
> items had to be removed (over 24,000 in one of them). After this operation, 
> I wanted to clean the database with the cleanup option, but the effect so 
> far - I only post the error message this time::
> 
> Caused by: org.postgresql.util.PSQLException: ERROR: update or delete on 
> table "bitstream" violates foreign key constraint 
> "bundle_primary_bitstream_id_fkey" on table "bundle"
>   Detail: Key (uuid)=(02caead4-de93-4011-8105-0e6921f286d8) is still 
> referenced from table "bundle".

I get those sometimes.  Here are the notes that I made for myself
about manually resolving the situation:

DSpace 6+:

  \set a BITSTREAM-UUID
  SELECT uuid AS b FROM bundle WHERE primary_bitstream_id = :'a';
  \gset
  SELECT * FROM bundle2bitstream WHERE bundle_id = :'b';

  -- Is bitstream A in bundle B?  Yes:  problem?

  SELECT deleted FROM bitstream WHERE uuid = :'a';

  -- Deleted?  No:  problem?

  UPDATE bundle SET primary_bitstream_id = null WHERE uuid = :'b';

where BITSTREAM-UUID is replaced by the actual UUID.  I type the first
'\set' in by hand and paste the UUID; after that I just copy/paste
each command and watch for errors, including those noted in the
comments.  This procedure isn't *quite* right yet to be scripted, but
it works for me.

I sometimes find that there are multiple bitstreams with this problem.
Unfortunately, the cleanup tool exits after the first one (aborting
its single transaction, alas!), so sometimes I need to run cleanup
several times, fixing one bitstream at a time.

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


signature.asc
Description: PGP signature

[dspace-tech] DSpace CRIS - Export as BibText - CSL error ("this.engine" is null)

[schul...@effective-webwork.de]

Hello,

we are currently trying to use the BibTex-export in one of our CRIS 
projects (and possible other CSL-based exports), but the export ist 
constantly failing, returning the following error. The same error occurs on 
all installations (server and local development) and with both OpenJDK or 
Oracle JDK. Maybe someone has seen this before and got some ideas how to 
get this functionality to work.

Regards
Johannes

//--

*2023-06-13 13:26:28,990 ERROR unknown unknown 
org.dspace.app.rest.scripts.handler.impl.RestDSpaceRunnableHandler @ 
Process id: 42, script name: item-export, message: null*

*java.lang.RuntimeException: java.lang.NullPointerException: Cannot invoke 
"javax.script.ScriptEngine.eval(java.io.Reader)" because "this.engine" is 
null*

*at 
org.dspace.app.rest.scripts.handler.impl.RestDSpaceRunnableHandler.handleException(RestDSpaceRunnableHandler.java:176)
 
[classes/:cris-2022.03.01-SNAPSHOT]*

*at 
org.dspace.app.rest.scripts.handler.impl.RestDSpaceRunnableHandler.handleException(RestDSpaceRunnableHandler.java:143)
 
[classes/:cris-2022.03.01-SNAPSHOT]*

*at 
org.dspace.content.integration.crosswalks.script.ItemExport.internalRun(ItemExport.java:99)
 
~[dspace-api-cris-2022.03.01-SNAPSHOT.jar:cris-2022.03.01-SNAPSHOT]*

*at org.dspace.scripts.DSpaceRunnable.run(DSpaceRunnable.java:104) 
[dspace-api-cris-2022.03.01-SNAPSHOT.jar:cris-2022.03.01-SNAPSHOT]*

*at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) 
[?:?]*

*at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) 
[?:?]*

*at java.lang.Thread.run(Thread.java:833) [?:?]*

*Caused by: java.lang.NullPointerException: Cannot invoke 
"javax.script.ScriptEngine.eval(java.io.Reader)" because "this.engine" is 
null*

*at 
de.undercouch.citeproc.script.JREScriptRunner.eval(JREScriptRunner.java:60) 
~[citeproc-java-1.0.1.jar:?]*

*at 
de.undercouch.citeproc.script.AbstractScriptRunner.loadScript(AbstractScriptRunner.java:29)
 
~[citeproc-java-1.0.1.jar:?]*

*at de.undercouch.citeproc.CSL.getRunner(CSL.java:386) 
~[citeproc-java-1.0.1.jar:?]*

*at de.undercouch.citeproc.CSL.(CSL.java:264) 
~[citeproc-java-1.0.1.jar:?]*

*at de.undercouch.citeproc.CSL.(CSL.java:242) 
~[citeproc-java-1.0.1.jar:?]*

*at de.undercouch.citeproc.CSL.(CSL.java:221) 
~[citeproc-java-1.0.1.jar:?]*

*at de.undercouch.citeproc.CSL.(CSL.java:185) 
~[citeproc-java-1.0.1.jar:?]*

*at de.undercouch.citeproc.CSL.(CSL.java:154) 
~[citeproc-java-1.0.1.jar:?]*

*at 
org.dspace.content.integration.crosswalks.csl.CSLNestedGenerator.createCitationProcessor(CSLNestedGenerator.java:43)
 
~[dspace-api-cris-2022.03.01-SNAPSHOT.jar:cris-2022.03.01-SNAPSHOT]*

*at 
org.dspace.content.integration.crosswalks.csl.CSLNestedGenerator.generate(CSLNestedGenerator.java:36)
 
~[dspace-api-cris-2022.03.01-SNAPSHOT.jar:cris-2022.03.01-SNAPSHOT]*

*at 
org.dspace.content.integration.crosswalks.CSLItemDataCrosswalk.disseminate(CSLItemDataCrosswalk.java:85)
 
~[dspace-api-cris-2022.03.01-SNAPSHOT.jar:cris-2022.03.01-SNAPSHOT]*

*at 
org.dspace.content.integration.crosswalks.CSLItemDataCrosswalk.disseminate(CSLItemDataCrosswalk.java:71)
 
~[dspace-api-cris-2022.03.01-SNAPSHOT.jar:cris-2022.03.01-SNAPSHOT]*

*at 
org.dspace.content.integration.crosswalks.script.ItemExport.performExport(ItemExport.java:107)
 
~[dspace-api-cris-2022.03.01-SNAPSHOT.jar:cris-2022.03.01-SNAPSHOT]*

*at 
org.dspace.content.integration.crosswalks.script.ItemExport.internalRun(ItemExport.java:96)
 
~[dspace-api-cris-2022.03.01-SNAPSHOT.jar:cris-2022.03.01-SNAPSHOT]*

*... 4 more*

-- 
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/91a11eec-5352-4ce4-866b-c32a5bfd35abn%40googlegroups.com.

[dspace-tech] Problem in scopus Integration in DSpace-Cris

[Salony Permanand]

Greetings!!

I installed DSpace cris-2022.03.01 for our institutional work . I am using 
import-publication command to import publications in Dspace-Cris with help 
of API from scopus.

While using command, I am mapping all the fields in scopus-integration.xml 
, but only first author and first Affiliation is coming. 

 I am not getting multiple author , abstract and multiple affiliation in 
Dspace User Interface . 

Please help asap

-- 
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/ba3ed749-8c1e-45b8-a7c7-cdeae2582bd1n%40googlegroups.com.

Re: [dspace-tech] Migrated DSpace 7.4 to cloud and deposit and forgot password error

[Lewatle Johannes Phaladi]

Dear Thierry,

Much appreciated for help, I have gave user tomcat access and also change 
file permissions but the same remain, I will do upgrade from 7.4 to 7.5 as 
it is latest by next week, if error still persist I will come back to the 
group and report it.

Regards,
Lewatle 

On Tuesday, 6 June 2023 at 16:25:20 UTC+2 Thierry RUGWIZANGOGA wrote:

> Dear Lewatle,
>
> For item deposit, did you check the assetstore ownership and permitions to 
> be tomcat:tomcat and 755 ? 
>
> On Tue, 6 Jun 2023, 14:48 Lewatle Johannes Phaladi,  
> wrote:
>
>> Dear DSpace Colleagues,
>>
>> We have migrated to cloud and when user tries to deposit item they get 
>> the following error, also when one forgot passwords tries to reset it they 
>> get this error,  please share your idea on what to try in order to fix this 
>> problem.
>>
>> [image: submission issues.png]
>>
>>
>>
>>
>>
>> [image: image_2023-06-06_144542599.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...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/dspace-tech/d205c645-2316-4694-a85b-fa75f3dcf422n%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/1da4cd37-eaaf-410d-9a75-d28d26602f34n%40googlegroups.com.

[dspace-tech] Bulk Import a publication from an external source

[Rift Blaster]

Hello Team,
I have Dspace 7.5 and I'm trying to Import a publication from an external 
source using ORCID. but, I can do it for only one ORCID id at once.
Any way to import bulk publications in DSpace from ORCID?

-- 
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/217eca0a-6418-4b17-8e95-fe11e38b2774n%40googlegroups.com.