Feature #1499

Manual Normalization - Create workflow for manual normalization

Added by Evelyn McLellan over 7 years ago. Updated over 6 years ago.

Status:VerifiedStart date:
Priority:HighDue date:
Assignee:Joseph Perry% Done:

0%

Category:NormalizationEstimated time:24.00 hours
Target version:Release 0.10-beta
Google Code Legacy ID:archivematica-844 Pull Request:
Sponsored:Yes Requires documentation:

Description

Here is a suggested workflow:
1. Objects are normalized to preservation and access copies using Archivematica's default normalization paths if desired
2. In the objects directory of the SIP, the user creates a new folder called manual_normalization
3. The user manually normalizes one or many files (eg any files for which Archivematica had no default normalization paths) and places them in the manual_normalization folder; the filenames (but not the extensions) should be the same as the original files
4. The user approves normalization
5. Archivematica checks for manually normalized files, linking them to their original by the filename and creating PREMIS metadata for them

[g] Legacy categories: Workflow, Sponsored


Related issues

Duplicated by Archivematica - Bug #1203: Add ability to force normalization Duplicate

History

#1 Updated by Joseph Perry over 7 years ago

5. Archivematica checks for manually normalized files, linking them to their original by the filename and creating PREMIS metadata for them

This will be complex to automate.
It assumes manual normalizations will strictly be 1 to 1, and not have the same file extension as the original file, or the user will need to enter a UUID in the filename.

#2 Updated by Evelyn McLellan over 7 years ago

"It assumes manual normalizations will strictly be 1 to 1, and not have the same file extension as the original file" - I think it would be reasonable to expect the users to meet those requirements.

#3 Updated by Evelyn McLellan over 7 years ago

Create wiki page with mock-ups (Evelyn)

#5 Updated by Courtney Mumma about 7 years ago

  • Target version changed from Release 0.9 to Release 0.10-beta

[g] Labels added: Milestone-Release-1.0
[g] Labels removed: Milestone-Release-0.9

#6 Updated by Joseph Perry about 7 years ago

[g] New owner: Joseph Perry

#7 Updated by Evelyn McLellan over 6 years ago

[g] Labels added: Component-Sponsored

#8 Updated by Jesús García Crespo over 6 years ago

  • Sponsored set to Yes

#9 Updated by Joseph Perry over 6 years ago

  • Estimated time set to 24.00

#10 Updated by Joseph Perry over 6 years ago

  • Subject changed from Create workflow for manual normalization to Manual Normalization - Create workflow for manual normalization

#11 Updated by Evelyn McLellan over 6 years ago

  • Tracker changed from Bug to Feature

#12 Updated by Joseph Perry over 6 years ago

  • Status changed from New to Feedback
  • Assignee changed from Joseph Perry to Evelyn McLellan

A few questions:
1. Archivematice uses camel case: manual_normalization -> manualNormalization ?

2. Is this just for preservation files, or is it for access and preservation?
If both, I might suggest distinguishing them by having an access and a preservation directory under the manualNormalization directory.

3. What are we putting for output format for these files?
related to Bug #1450 - Format of normalized files not identified in PREMIS metadata

#13 Updated by Joseph Perry over 6 years ago

  • Status changed from Feedback to QA/Review

1. Archivematice uses camel case: manual_normalization -> manualNormalization ?
-yes
2. Is this just for preservation files, or is it for access and preservation?
If both, I might suggest distinguishing them by having an access and a preservation directory under the manualNormalization directory.
-both, yes two directories.

3. What are we putting for output format for these files?
related to Bug #1450 - Format of normalized files not identified in PREMIS metadata
-run fits on them.

#14 Updated by Evelyn McLellan over 6 years ago

  • Status changed from QA/Review to Feedback
  • Assignee changed from Evelyn McLellan to Joseph Perry

Looks fine. Run FITS on files manually normalized for preservation only (i.e. not for access).

#15 Updated by Evelyn McLellan over 6 years ago

  • Status changed from Feedback to Verified

#16 Updated by Courtney Mumma over 6 years ago

  • Category set to Normalization

Also available in: Atom PDF