...
- Round table check-in:
- What's working / what's not
- Availability for this week
- Are we on track to realize our sprint goals?
- core
- CRUD for containers and binaries.
- migration
- core
- Sprint closing meeting
Notes
- Round table check-in
- Peter E
- Some of the design discussions difficult to keep up with, rate of PRs and changes
- Some local work Tuesday, meetings. Otherwise, available.
- Peter W
- Been working on bugs/fixes with ocfl client, been reworking paths in windows
- mostly available
- Ben P
- Finishing up ocfl obj session, locking. Reviewing other PRs.
- mostly available aside from meetings
- Andrew W
- need stakeholder testing of migration tool, it is becoming increasingly usable, needs docs
- want to see how well it will handle scale, multi-processing
- Suggesting looking at list of goals for the sprint
- need stakeholder testing of migration tool, it is becoming increasingly usable, needs docs
- Danny B
- Many parallel activities going on making things complicated, all layers working independently
- hopeful about getting read-write capability for at least some resource types
- Scattering of meetings, otherwise available. Can't get on early friday morning.
- Many parallel activities going on making things complicated, all layers working independently
- Peter E
- Are we on track to realize our sprint goals?
- Core - these goals are our intent for the end of the year
- read/write involves versioning and transactions
- versioning is a little bit vague, are we going to support writing past versions? deleting?
- should be on target for writing them
- transactions
- should be decently well defined
- fixity
- some could come from OCFL, need to make decision of how to use the built in fixity aspects
- Many members
- Will need to get things further along in terms of all aspects of the stack working together to have a estimate of how this will ultimately perform
- There is a "real world tests" folder somewhere that has a many member script that could be used.
- services, index, persistence operations, and ocfl creation all currently in play.
- Basic content migration seems to be there
- right now it creates ocfl objects with turtle files
- will need to line up what persistence layout, look at that today
- Indexing
- PeterE - still in the early stages of planning https://docs.google.com/document/d/1yv_Tf_B4EqY8N1IDlm0avOt4mCF-5VuN0sOCtUyg_uQ/edit#
- Locking
- half isolated transactions - lines up with fcrepo4
- optimistic locking with merge
- ocfl client would not provide merge behavior
- is there a strong use case for merging?
- Peter's case does not have multiple clients writing at the same time.
- Andrew - Does fedora have a way of recognizing that object is in modification elsewhere, maybe communicate this?
- Ben - Not sure about doing this based off of persistence level info, versus http layer info like etag/last modified
- Transactions are hard
- going to start with last commit wins, work up to other types of optimistic locking
- at persistence layer, will focus on preventing simultaneous commits to object at same time
- Core - these goals are our intent for the end of the year