Regular Attendees
- Andrew
- Bill
- Chris
- Dan
- Jonathan
- Danny
General
- Call In To: Free Conference Call HD - DuraCloud Line
- - Indicates who will be taking minutes
Discussion Topic
Advanced Tables - Table Plus | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
|
Actions from last meeting
Last Weeks Actions:
Action Item | Assignee | Status |
---|---|---|
Update your availability for the next 8 weeks in JIRA | All |
|
Get Peter in the system when things are finalized this week | Jonathan |
|
Add task covering in-CloudSync scheduling of tasks (2-day, unscheduled) and update existing task to note that initial 0.2 scheduling with be via cron | Chris |
|
Status
- Jonathan
- Andrew
- Starting migration of DuraCloud Management Console from SimpleDB to LDAP this week
- No news on the Islandora instance
- Bill
- Created very simple webapp with an embedded jetty server, which can be deployed via an executable jar. See code on github
- Experimented with InstallBuilder. Created an installer for both the current DuraCloud Upload Tool (swing app) and the webapp noted above.
- Enterprise license for InstallBuilder (free for open source projects) has been obtained
- Chris
- Dan
- Danny
Minutes
- Dev vs Strategy Meeting
- Plan was to have the DfR meeting be primarily Dev going forward
- For the moment, just including some Strategy topics in the one meeting
- Dan: Still need to test the waters to see how much time we need for each
- Jonathan has asked Dan and Andrew to join the strategy meetings, schedule to be defined
- Dan: Would like to bring everyone up to speed on Data Conservancy and Tessella
- Upcoming meeting with Peter and Tim: Wed at noon
- Peter/Tim are on board, business arrangement has been made
- Peter has worked with Danny before
- Meeting is to make sure that there is shared understanding of the goals
- Jonathan: Touched based with Marine Lab (part of Univ of California system) and Columbia about getting access to researchers for DfR feedback
- Bill and Dan to look at the design docs more in depth prior to meeting
- Sync tool development
- Does the UI need to handle on-demand upload?
- Dan: Expectation that the GUI would be doing nothing but setup
- Bill: Thinking that the UI would collect info about the file system and present that to the UI for user to make selections
- Dan: Having a pathway to an institutional server (on a server in the IT shop)
- Dan: Example, if you have a 30 person shop, they likely share disk support and some applications: this works better as a webapp
- Bill: Running on a local machine, the interaction is different.
- Dan: Presuming the sync tool is running all the time, this needs to be the case for the sync tool to do constant updates
- Jonathan: Prefer that the web UI experience
- Andrew: Seems like we may wan to get a better idea of the requirements before making these choices
- Dan: Expecting that file system access to be handled via the server side
- Bill: Will be out the next two weeks, will have some UI design activities occuring in the meantime
- Plan: Get back to this issue when we have the full time in attendance and when some UI design work has been completed
- Does the UI need to handle on-demand upload?
Action Items
Action Item | Assignee | Status |
---|