Page History

Regular Attendees

• Andrew
• Bill
• Chris
• Dan
• Jonathan
• Danny

General

• Call In To: Free Conference Call HD - DuraCloud Line

  Info
  Please note that we will be using the Free Conference Call HD line for this call. Information about calling into this line is available from the link above.

• - Indicates who will be taking minutes

Discussion Topic

Planning Board
Task Board
DfR Planning and Estimating - 0.1

Actions from last meeting

Last meeting

Last Weeks Actions:

Related Information
DfR Software Next Steps - Jan 2012
2012-01-03 - Architecture Meeting, Temple University

Status

• Jonathan
  • Advisory Group meeting this afternoon on "what is the value proposition for DfR, given an increasingly crowded market?"
• Andrew
• Bill
• Brad
• Chris
• Dan
  • Working on Islandora Integration
  • Working overview documentation (received some good input from Jonathan - being incorporated)
  • Working on synch tool requirements
  • Met with SI meeting in DC
  • Creating cards from for Iteration 2 for critiques, pointing and prioritization
  • Reviewed Spring integration particularly for Apache Camel and Mule, Also Spring Web MVC
  • Moved DFR-79 and created DFR-88 (needs to be pointed)
• Danny

Minutes

How we are tracking tasks

1. The team will revert to a process closer to that found in DuraCloud
   1. At beginning of iteration, technical tasks are defined
   2. An in-person meeting is held for this
      • No in-person meeting this iteration
      • Need complete list of tasks for this iteration
   3. However, would like to have a discussion of iteration "stories" first
   4. Phone call meetings should be tracking tasks
   5. Need more focus on tech discussions
   6. Will likely split meetings into two parts (tech and management)
   7. Agile tool in jira is a bit too heavy-weight

Time allocation

1. Chris
   • 1 day Fedora
   • 3 days on DfR
2. Bill
   • 1 day DfR
   • The rest on DuraCloud
3. Andrew
   • 50/50 split between DuraCloud/DfR
4. Peter will be engaged
5. Danny will be out for most of this iteration
6. Dan will be available 50%

0.2 Iteration

1. DGI integration
   • Will review collaboration plan defined a D.C. meeting
2. Need to list features for synctool
   • Add anything needed beyond the DuraCloud version
3. Split DfR-23 into UI and underlying tasks
   • one deliverable is wiki documentation around features/capabilities
4. DfR-80, viewing files in Islandora
   • This is not related to security
   • Basic objects should already be viewable SI
   • Certain Fedora objects are tagged as concepts
   • Other Fedora objects are tagged as directories/files
   • Islandora has a python-based micro-service engine
   • There are two places where content can be updates
     • as Fedora objects
     • by the micro-services
   • We will also be adding metadata in OCS
   • We will be collaborating on shared tool suite
   • DGI will guide us in creating useful Fedora objects
   • Data streams will be stored in DuraCloud
5. Will deploying SI locally happen in 0.2?
   • There may be work still needed to remove Smithsonian-specific details
   • Which is better to use?
     • Vanilla Islandora
     • Smithsonian-specific Islandora
       • Contains notion of "Concepts"
6. Dan, Andrew, Jonathan, DGI, Thorny
   • Organize a call this week
   • Asking for SI-AMI
7. Goals of SI/DfR integration
   1. Ingesting Fedora objects
   2. Managing security infrastructure
   3. Integration of Islandora-Fedora & DuraCloud
8. Danny and Peter have a f2f meeting next Monday
   • Design session
   • At that point Peter will be positioned to move forward
   • Danny to check-in with Jonathan & Dan
     • 11am Friday (May 4)
9. Need to populate tasks before next Monday
   • Migrate 0.2 security jiras to 0.3
   • Tech group needs to pull tasks together
     • Tech meeting on Friday @1pm
   • Monday meeting to present those tasks to Jonathan
     • Determine which tasks are un-needed, and where the gaps may be

0.2 Jira Tasks