Regular Attendees
- Andrew
- Bill
- Brad
- Chris
- Dan
- Jonathan
General
- Call In To: Free Conference Call HD - DuraCloud Line
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 Topics
Planning Board
Task Board
DfR Planning and Estimating - 0.1
Topic Discussion Leader Planning and Task Boards - Iteration Review Dan Planning and Task Boards - Building the Backlog Dan Project Documentation Dan Islandora Security Andrew Project and Partners Jonathan
Actions from last meeting
Last Weeks Actions:
Action Item |
Assignee |
Status |
|---|
Write Cards for Updates to Support OCS - Add on Tasks for Iteration 1 |
Chris |
|
Determine key pipeline tools to demo (characterization), Connect to FITS or others |
Dan and Jonathan |
|
Rephrase DfR 1 to better fit future iterations |
Dan |
|
Rephrase DfR 74 wrt Fedora |
Dan and Chris |
|
Better conceptualize accounts for DfR |
Team |
Postponed |
Conceptualizing/Design Synch Tooling |
Bill |
|
Better set the feasible scope for this year in automated metadata collection |
Team |
|
Connect to Paul Pound on Islandora |
Dan (integration) and Andrew (security) |
|
Add card(s) for documentation |
Dan |
|
Related Information
DfR Software Next Steps - Jan 2012
2012-01-03 - Architecture Meeting, Temple University
Status
- Jonathan
- Andrew
- Bill
- Brad
- Chris
- Dan
- Jonathan
Minutes
Most of todays meeting comments were recorded in Jira.
There was a lively design dicussion regarding file integrity (checksums) for DfR. Dan had revised the wording for DFR-74 but it still missed the mark. The group want to account for two threads (with discussion beween them) regarding file integrity. The other thread is covered by DFR-76. The team agreed that we need to take wholistic design view to file integrity (and scope it to 0.1 with improvements to further releases). The discussion including the ideas that research content will be uploaded to DuraCloud and via Fedora (as part of the Islandora integration). The DFR design must accommodate many on-ramps and off-ramps. Also the OCS, and other applications and processes will be creating and modifying Fedora objects (which end up in DuraCloud). We have several places where checksums are created and/or recorded. We will continue the design work in appropriate group design discussions concentrating for now on those features needed for the 0.1 implementation.
Andrew has taken the assignment to look at DFR-60 User/Group/Role for 0.1 as a modeling-only investigation for later implementation. He will be helped by Chris.
DFR-61 is moved to 0.2 due to time/information limitations.
DFR-62 is to rescoped to an investigation task for 0.1 due to time limitations. Andrew currently will be the contact person.
Dan (and has taken the assignment) to produce an overarching description of DfR in the Wiki for 0.1 as DFR-78.
As part of last weeks discussion, we need a front-end application to inform the DfR design a provide a good, non-production demonstration. Currently the plan is to use Islandora but, as Andrew noted, we cannot expect Discovery Garden, Islandora or Smithsonian to modify their code for this purpose. We can obtain the code but we want to expend most of our resources on DfR core tasks. The resolution is to dig deeper into understand the integration and what needs to be done before we can make conclusions and plan work. We will also gather information from other potential integrations such a Hydra to inform the work. Bill will report on Hydra discussions next week.
Bills name is on DFR-23 and the meeting actions. But this work is expected to include Brad and Dan. The meeting action was under Bill's name but that is likely not right. So I will switch the action name to me for next week, but this will need some designs sessions to list requirements for the synch and synch setup tooling (not just whether is a web or heavy app or where it operates).
Actions
Ask Bill to discuss Hydra meeting.
