Regular Attendees
- Bill
- Dan
- Danny
- Jonathan
General
- Call In To: Free Conference Call HD - DuraCloud Line
- - Indicates who will be taking minutes
Discussion Topic
| Topic | Discussion Leader |
|---|---|
| SiDora Update | Dan |
| Review of Jira tasks in-progress | Bill |
| Review Timing | Dan |
Status
- Bill
- Dan
- See the email record on SIDora
- We have a plan
- We were notified that DG has a clean copy from SI
- Perhaps we are getting closer to an AMI
- Directory creation is nearly done. Remaining:
- A good clean up (done, pushed)
- Better code to prevent attempts to create directories twice (50% done)
- Error and exception handling (maybe atomic ingest TBD) (50% done) (Keeping it simple)
- Choose/make a good content model in Sidora for directories (30% done) (Mostly on hold until we get the new AMI)
- Improve tests (Discussed with Bill) 85% done.
- Only test what we use
- Use "Sidora" Fedora for ITs to avoid having to add a Fedora deployment to the DfR Maven
- There is no feasible way to set up DuraCloud (DuraStore) so use dfrtest for ITs
- Still need to update some ITs particularly the DuraCloud to DfR IT
- Purge in Fedora Client W/R/T Sidora Fedora not working (but in Admin client works)
- I need to revise (decide) the strategy to permit adding a log message for ingest (the old one won't work)
- Modifications to make ITs work in Java 7
- Added a README in the code pointing to this page: Building DfR Software from Source
- Bamboo modifications to support Java 7
- Revised characterization task to use DROID by itself (25% complete)
- See the email record on SIDora
- Danny
Minutes
- Sidora Update:
- They had an image in hand
- It seemed that they were hours away from creating the AMI.
- As of Thursday, Gervais was working on the image (creating it by loading the code onto a new image and then transferring the data onto it rather than copying smithsonian institution image and cutting it down.
- We're hoping to get a tested AMI: Dan will send Jonathan a list of requests for the DG team (or the list will be brought up at the DFR partners meeting)
- Bill doesn't think that it makes sense to try to change their process until they hand us something. Based on the way things are looking it looks like it will be showing up any day now.
- Danny's DFR-143 is done as well as DFR-91. DFR-143 is waiting for DC2.2 release before I check that in (as there are uncommitted changes to the sync tool) . DFR-136 is to be completed imminent. (for DC-136 see Duracloud TimeCapture tool duracloud-priv/duracloud-utilities)
- DFR-126: it would be helpful to have a DGI resource to walk Danny through the code that will need to be tweaked.
- Dan has been improving directory creation code. Also improving code for keeping our metadata in.
We can demonstrate content characterization using the Droid tools alone. Dan was able to reuse Duracloud Droid code. Dan is about a day away from wrapping up the directory creation process. - DFR-109 and DFR-76: once we have a data stream we can put the metadata into we can pick these two off.
- Jonathan's concern: we need to focus on bringing everything together so that we can perform a persuasive demonstration. Perhaps we can get started on this before the other tasks completed. For example, skinning Sidora can happen after we get the demo together. What's the best way to begin moving this demo forward?
- When would be like to be able to do the demo:? The week of the December 17th.
- Dan: if we get Sidora this week, by the end of next week we can begin putting the demo together. Once Sidora is available and running, then we can begin in earnest.
- Code freeze: 1st week in December (Dec. 3rd) Optimally we'll have the code release done before the demo. We'd like everything wrapped up by the end of the year.
- Jonathan is going to try to put together the demo plan: we'll circle up on Monday to review what if anything has been done on the demo plan.
- Dan has put up a page on how to install DFR from scratch: see above.
