I believe that was fixed in 7.2, as part of this PR (which fixed several issues 
in the edit bitstream form): https://github.com/DSpace/dspace-angular/pull/1417

Tim
________________________________
From: [email protected] <[email protected]> on behalf of 
Tyler Mobley <[email protected]>
Sent: Thursday, March 24, 2022 2:58 PM
To: DSpace Technical Support <[email protected]>
Subject: Re: [dspace-tech] (7.0) Bitstreams missing after Simple Archive Import

Tim, not to pile on, but could you also check and verify if you get the 
following error in console and a blank screen when hitting the 'upload' button 
on the bitstream tab when editing an item? I thought I'd upload a new file to 
an existing item to see if at least that new file would show up in the public 
item view, but it appears I found a different problem. Going to upgrade to 7.2 
UI tomorrow to see if that's the problem.

ERROR TypeError: You provided 'undefined' where a stream was expected. You can 
provide an Observable, Promise, Array, or Iterable.

Tyler

On Thursday, March 24, 2022 at 3:50:16 PM UTC-4 Tyler Mobley wrote:
Thanks, Tim!

On Thursday, March 24, 2022 at 3:48:56 PM UTC-4 Tim Donohue wrote:
Hi Tyler,

I can verify that the "Primary Bitstream" toggle when editing a Bitstream 
doesn't appear to work properly for me either.

I've just created a ticket and added it to our project board for more analysis:
https://github.com/DSpace/dspace-angular/issues/1578

Tim

________________________________
From: [email protected] <[email protected]> on behalf of Tyler 
Mobley <[email protected]>
Sent: Thursday, March 24, 2022 10:10 AM

To: DSpace Technical Support <[email protected]>
Subject: Re: [dspace-tech] (7.0) Bitstreams missing after Simple Archive Import
OK, after looking at the console responses I'm seeing the following sequence 
when I go to edit a bitstream, check toggle to make it primary, then click 
Save. In the interface I receive the green 'changes saved' alert. But the 
changes don't occur per what's here:

Cross-Origin Read Blocking (CORB) blocked cross-origin response 
https://api-d.library.cofc.edu/server/api/core/bitstreams/8c205262-d366-48fd-abcf-7e7f303e6a50/content
 with MIME type application/pdf.

bitstreams:1 Form submission canceled because the form is not connected

dspace-rest-response-parsing.service.ts:155 The response for 
'https://api-d.library.cofc.edu/server/api/core/items/5738204b-4cb0-4bc2-b0ed-5a36a5627b16/bundles?page=0&size=9999'
 has the self link 
'https://api-d.library.cofc.edu/server/api/core/items/5738204b-4cb0-4bc2-b0ed-5a36a5627b16/bundles?page=0&size=1000'.
 These don't match. This could mean there's an issue with the REST endpoint


Tyler
On Tuesday, March 22, 2022 at 9:58:01 AM UTC-4 Tyler Mobley wrote:
Circling back to this. I'm now on 7.1.1 and gave this another run this morning. 
I don't see any particular errors, the items are loaded and indexed in solr, 
and now I see that in the full item view only my license.txt file listed. 
HOWEVER, when I login and go to edit the item, the proper files ARE there under 
the bitstreams tab. I can download and view them as wanted. I'm also seeing 
though that these files are not being set as primary and when I edit and click 
the toggle to make them primary and save the changes don't seem to stick. Any 
idea? Permissions problem? Theme problem? Including a sample of my contents 
file below from the import.

BINNICKER-BACHELORSESSAY-2013.pdf       bundle:CONTENT  primary:true
LICENSE.txt     bundle:LICENSE

Thanks!

Tyler

On Friday, October 22, 2021 at 11:24:06 AM UTC-4 Tim Donohue wrote:
I don't believe permissions in the Zip would have an impact.

You may also want to double check that the Zip file is structured as described 
in Simple Archive Format:
https://wiki.lyrasis.org/display/DSDOC7x/Importing+and+Exporting+Items+via+Simple+Archive+Format#ImportingandExportingItemsviaSimpleArchiveFormat-DSpaceSimpleArchiveFormat

Pay close attention to the "contents" file which must obviously list all files 
you want to import.

Another option to try is unzipping​ the content into directories and just 
importing from the directories. Maybe there's something odd going on with the 
unzipping here?  I'm honestly not sure.

I'm slightly surprised there's no errors anywhere...but, maybe that means it's 
doing exactly what it thinks you want. Maybe the PDF file isn't listed in the 
"contents" file and so it's being ignored?

Tim
________________________________
From: [email protected] <[email protected]> on behalf of Tyler 
Mobley <[email protected]>
Sent: Friday, October 22, 2021 9:38 AM

To: DSpace Technical Support <[email protected]>
Subject: Re: [dspace-tech] (7.0) Bitstreams missing after Simple Archive Import

Hi Tim,

I'm not seeing anything specific. In dspace.log I am getting occasional long 
stacktraces about a connection reset by peer error that I imagine is probably a 
firewall issue more than anything else. For a second I thought it might be 
related, but I see the same trace in there today and haven't run the import 
again since posting here. Catalina logs don't seem to have anything. Maybe my 
logging is misconfigured. I'll take a look. Would permissions on the files in 
the zip have any effect? I  don't get why a license.txt would make it through 
but not a PDF though.

Thanks,
Tyler

On Thursday, October 21, 2021 at 5:10:30 PM UTC-4 Tim Donohue wrote:
Hi Tyler,

Are there any errors in the backend logs (dspace.log or Tomcat logs)?  If you 
aren't seeing errors from the commandline process, it's possible they are 
showing up in the logs instead.

Tim


________________________________
From: [email protected] <[email protected]> on behalf of Tyler 
Mobley <[email protected]>
Sent: Thursday, October 21, 2021 12:15 PM
To: DSpace Technical Support <[email protected]>
Subject: [dspace-tech] (7.0) Bitstreams missing after Simple Archive Import

This morning I expunged a list of items in a collection successfully and then 
used the command line import on Dspace 7 to import a zipfile of new items to 
that collection arranged in Simple Archive format. All the items come in 
correctly except for the primary bitstreams which are all PDFs. In the script 
output I can see lines per item where said file is being set as primary 
bitstream as per the contents manifest. However, the only thing appearing 
publicly apart from metadata is the included license.txt file.

I'm not receiving any errors that I can find during the import. Any ideas?

Thanks!
Tyler

--
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/abf20f2a-bdb0-43fe-aa29-38f0b6f3c6f7n%40googlegroups.com<https://groups.google.com/d/msgid/dspace-tech/abf20f2a-bdb0-43fe-aa29-38f0b6f3c6f7n%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/1fe7dddd-3720-4ce3-b4b0-f5d674e266e7n%40googlegroups.com<https://groups.google.com/d/msgid/dspace-tech/1fe7dddd-3720-4ce3-b4b0-f5d674e266e7n%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/0b9a723b-830f-48ec-92a7-4b93e1283c7an%40googlegroups.com<https://groups.google.com/d/msgid/dspace-tech/0b9a723b-830f-48ec-92a7-4b93e1283c7an%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
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 
[email protected]<mailto:[email protected]>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/76421cd9-2e74-4755-90ff-81074ea298e8n%40googlegroups.com<https://groups.google.com/d/msgid/dspace-tech/76421cd9-2e74-4755-90ff-81074ea298e8n%40googlegroups.com?utm_medium=email&utm_source=footer>.

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/PH0PR22MB3274DCFFE3D864D1F2741E69ED199%40PH0PR22MB3274.namprd22.prod.outlook.com.

Reply via email to