Team members

• Dan Field
• Jenny A'Brook
• Richard Williams
• Youn Noh
• Michal Dulinski
• Remigiusz Malessa
• Andrew Woods

Objectives

1. Create tooling to migrate F3 objects to OCFL (using migration-utils)
2. Create user documentation for the new/updated tooling
3. Create (high-level) technical documentation describing what the tooling does under the covers
4. Produce performance numbers describing how long will a migration take

Tasks

• All tasks (development, testing, and documentation) should have an associated JIRA ticket
• Work on every task should be tracked per the Story Management workflow

Dev

1. Code review and committing process
   1. Someone other than the pull-request author to review and merge
2. Build current software - all developers
3. Create new OCFL impl along side Go/OCFL impl - several JIRA tickets here
   • New OCFL impl should use Peter WincklesOCFL client
     • parent
     • api
     • core
     • filesystem
   • Fill in Fedora4Cient interface methods
     • Include integration tests with all pull-requests
     • See: OCFLFedora4ClientIT.java

Docs Unable to locate Jira server for this macro. It may be due to Application Link configuration.

1. User documentation
   • How to use the tool (update README.md)
2. Technical documentation
   • What does the tool do (either update README.md, or create a new page)

Test

1. Verify user documentation
2. Confirm OCFL results of running the tool
   • Compared with the initial F3 objects
   • Evaluate in terms of the OCFL specification
3. Performance
   • How long does it take to migrate X-number of F3 objects?
   • How long does it take to migrate Y-GB of F3 content?

Tickets

• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Unable to locate Jira server for this macro. It may be due to Application Link configuration.