Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem: It is possible to end up with a SIP that has no files #419

Open
ross-spencer opened this issue Jan 9, 2019 · 1 comment
Open

Comments

@ross-spencer
Copy link
Contributor

Expected behaviour

When a transfer no-longer has any meaningful files left to process it should fail early.

Current behaviour

In #418 we see a transfer processed by Archivematica through to Job Check transfer directory for objects. The transfer structure looks as follows:

mbox-example$ tree -a
.
└── mbox
    ├── Drafts
    │   └── .mbox
    ├── INBOX
    │   └── .mbox
    ├── Junk
    │   └── .mbox
    ├── processingMCP.xml
    ├── Sent
    │   └── .mbox
    ├── Webmail-old
    │   ├── INBOX
    │   │   └── .mbox
    │   ├── .mbox
    │   └── sent-mail-Oct-2008
    │       └── .mbox
    └── Trash

The hidden files are all removed, leaving just the directories and processingMCP.xml which provides enough structure for Archivematica to attempt to continue processing.

There isn't a lot of feedback for the user when it reaches the final microservice. So between when the hidden files are removed, and when the transfer ostensibly completes, i.e. passes out of Job Check transfer directory for objects with zero error-code, the user might need more information to go on when the SIP doesn't arrive in the Backlog or Ingest tab.

Your environment (version of Archivematica, OS version, etc)

Verified on AM 1.8.


For Artefactual use:
Please make sure these steps are taken before moving this issue from Review to Verified in Waffle:

  • All PRs related to this issue are properly linked 👍
  • All PRs related to this issue have been merged 👍
  • Test plan for this issue has been implemented and passed 👍
  • Documentation regarding this issue has been written and it has been added to the release notes, if needed 👍
@jorikvankemenade
Copy link

jorikvankemenade commented Sep 3, 2019

@ross-spencer thanks for pointing me in the direction of this ticket. I didn't have time to look into the underlying cause of this particular problem, so this is really helpful!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants