mw...@iu.edu wrote:
If you can get more details on how the content of the repository was
rebuilt, it may be helpful in finding the best way forward or, at
least, understanding the repository's current state.
I do think we figured out how the mess came to be. I think they
restored a database from a defunct dspace install, not realizing that
there was no backup of the assetstore. So, basically, the file is
missing but all the database side of stuff is there. Since we know the
date we rebuilt, we should be able to find all the items which have been
created before that time and "fix" those. It looks like we can
initially do a search of something like: dc.date.issued:[1999 TO
2024-03-20] to find all the records.
They still do have most of the assets in digital form, but it will be
work to find them scattered across multiple computers. It looks like
the best process for fixing them, if we have the original file, is
follow these instructions you gave:
It is possible to delete an existing bitstream from, and to up load
a new one to, an Item when logged in with appropriate rights (such
as a member of the Administrator group). Navigate to the Item, use
the pencil / Edit this item button at top right, select the
Bitstreams tab, and you'll see a list of bitstreams with action
buttons, plus uploading controls at the top.
And then we will have the joyous task of dealing with all the ones that
fall through the cracks, whether because they cannot find the original
file, or because the item was somehow skipped when they were fixing.
Anyway. I think you have helped; at least I know where things stand.
It may be easier for them to bulk delete all the ones that are certainly
no longer there and simply upload all the ones that they do have. I
will let them figure that one out.
- Tim Young
On 10/30/2024 1:47 PM, mw...@iu.edu wrote:
On Tue, Oct 29, 2024 at 03:33:35PM +0000, Tim Young wrote:
I am a linux tech who is helping some librarians debug their dspace. The complaint is
that they are seeing some error pages after clicking on the "pdf" link after
looking at an item.
Whitelabel Error Page
This application has no explicit mapping for /error, so you are seeing this as
a fallback.
Tue Oct 29 15:04:16 UTC 2024
There was an unexpected error (type=Internal Server Error, status=500).
An internal read or write operation failed
(snip)
--
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 visit
https://groups.google.com/d/msgid/dspace-tech/71b47112-ea99-4bdc-b22d-61e3f2218650%40LightSys.org.
