Regular Attendees
- Andrew (call in)
- Bill (Vacation)
- Chris
- Dan
- Jonathan
- Danny
General
- Call In To: Free Conference Call HD - DuraCloud Line
- Indicates who will be taking minutes
Discussion Topic
Topic Discussion Leader SI Instance Andrew Outcomes of Peter and Time UI Meeting Jonathan OCS Integration Dan and Chris Availability this week Dan
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
Minutes
Andrew: SI instance up and running, DuraSpace has a copy of the AMI and is running under a DuraSpace account. Dan and Andrew has the key pair and the account credentials. There are separate credentials for the front end Islandora SI App (login from browser).
Action Dan: Provide credentials to Chris when he is ready.
Dan: Has been working on OCS code and preparing to ingest Fedora objects starting locally then to SI demonstration instance. We can restart the instance as needed to clean its out. But we need to open a hole in the firewall. Later determine where to put test and demo code.
Chris: Was anticipating that we would use the SI demo instance and the DfR Test instance for development and testing.
Everyone agress:
Jonathan and Andrew: We can log into the SI demo but cannot do anything that lets us see the demo.
Action Dan: Figure out how to getting the SI doing something interesting.
Dan: The plan is to ingest Fedora object and see if we can match up to a useful content model, visible in the SI instance. We can look at Fedora objects directly in the cloud instance and also in the SI Virtual box but presumably the SI ami is newer and contains DGs refactoring of SI "concepts" to Fedora content models we can make.
Chris: Dan, lets have a working session when I have caught up a bit from vacation.
Jonathan: Did everyone read the email about Tim/Peter not fully understanding Synch. Perhaps we are explaining it poorly especially the work "Synch".
Dan, Andrew: Yes it is confusing.
Dan: It is confusing to describe the difference between Synch and Backup though one-way synch does cover the backup use case. By itself, what we talked them about was a limited view that is not the long term vision.
Andrew: We need to keep that we must develop these capabilities incrementally.
The group discussed synch, especially overwrites and its various aspects. We surfaced various capabilities we could build but realized most are out of scope for the available resources. However, we should discuss what can be done, and describe the future.
Andrew: The simplest thing we can do soon is to put a switch in the synch tool to refuse to update existing files and warn the user.
Chris and Andrew: Both Fedora and DuraCloud keeps audit trails.
Dan: We will need a better capability and some time like keeping versions. We need first backup the "at risk" data and capture richer context information via DfR, then incrementally add capabilities. But without Drop Box level capabilities plus versioning we are not likely to excite researchers.
Action Dan: Reply to email thread.
Action Items
Action Item |
Assignee |
Status |
|---|---|---|
Respond to Peter and Tim regarding questions |
Dan |
|
Pathfind using the DfR SI Instance |
Dan |
Still in progress |
Provide credentials to Chris for DfR SI instance when he is ready |
Dan |
|
Bring Chris up to date after vacation |
Dan |
Mostly done not including OCS |
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 |
|
