hi Mark,
One more question sorry - what about metadata-only records? do they also
point to a dummy or blank file, or does the bitstore-migrator not look for
files from metadata-only records?
Actually that was two questions.
Thanks,
Gary
On Wednesday, July 31, 2019 at 12:20:51 AM UTC+10, Mark H. Wood wrote:
>
> On Tue, Jul 30, 2019 at 01:58:15PM +0000, Gary Browne wrote:
> > You're right that there is a record in the database for this file, but
> the "deleted" field value is "true". I'm assuming in this case that there
> should be no file in the assetstore and that the bitstore migrator should
> ignore it?
>
> No, a Bitstream marked "deleted", with no corresponding file in the
> assetstore, is damaged. The "deleted" flag just means that the
> Bitstream record *and* assetstore file should be deleted when we run
> 'bin/dspace cleanup' ("cleanup: Remove deleted bitstreams from the
> assetstore").
>
> In a good conservative design, the migrator probably *should* attempt
> to move a "deleted" Bitstream with its content. The Bitstream in
> question here is something that should not happen. I would argue that
> the migrator, when it cannot move a Bitstream, should skip over it and
> continue without altering it, giving as much information as it can
> about the nature of the failure.
>
> --
> 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 DuraSpace Code of
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
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/4e56e045-a06a-4027-86ec-4a2d32ba44d4%40googlegroups.com.
