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: package names are being modified #201

Closed
jrwdunham opened this issue Sep 24, 2018 · 0 comments
Closed

Problem: package names are being modified #201

jrwdunham opened this issue Sep 24, 2018 · 0 comments
Assignees
Labels
Severity: high A high-priority situation where performance or other uses are significantly impacted or degraded. Type: bug A flaw in the code that causes the software to produce an incorrect or unexpected result.
Milestone

Comments

@jrwdunham
Copy link

Expected behaviour

When a transfer contains a package and that package is extracted by Archivematica and the original package is not deleted, then the package should not be renamed.

Current behaviour

Currently, in the above-described scenario, the package is being renamed. This is due to changes introduced by artefactual/archivematica#1178. These changes need to be undone while still maintaining the fix that that PR was targeting.

Steps to reproduce

Create an AIP from a transfer containing a package and choose to extract packages and not delete them. The final AIP will contain the original package but with a date suffixed to its filename.

See this comment: #116 (comment)

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

  • AM qa/1.x
  • SS qa/0.x

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 👍
  • Release documentation (e.g. release notes, wiki documentation, etc) regarding this issue has been written 👍
@jrwdunham jrwdunham self-assigned this Sep 24, 2018
@jrwdunham jrwdunham added Severity: high A high-priority situation where performance or other uses are significantly impacted or degraded. Type: bug A flaw in the code that causes the software to produce an incorrect or unexpected result. labels Sep 24, 2018
@sromkey sromkey added this to the 1.8.0 milestone Sep 25, 2018
@sevein sevein added the Status: ready The issue is sufficiently described/scoped to be picked up by a developer. label Sep 26, 2018
@jrwdunham jrwdunham added Status: in progress Issue that is currently being worked on. and removed Status: ready The issue is sufficiently described/scoped to be picked up by a developer. labels Sep 26, 2018
@sevein sevein added Status: blocked Work on the issue is not possible until the blocking condition is removed. Status: review The issue's code has been merged and is ready for testing/review. and removed Status: in progress Issue that is currently being worked on. Status: blocked Work on the issue is not possible until the blocking condition is removed. labels Oct 2, 2018
@ablwr ablwr self-assigned this Oct 10, 2018
@ablwr ablwr added Status: verified and removed Status: review The issue's code has been merged and is ready for testing/review. labels Oct 10, 2018
@sromkey sromkey closed this as completed Nov 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Severity: high A high-priority situation where performance or other uses are significantly impacted or degraded. Type: bug A flaw in the code that causes the software to produce an incorrect or unexpected result.
Projects
None yet
Development

No branches or pull requests

4 participants