...
- Danny Bernstein
- Peter Winckles
- Jared Whiklo
- Ben Pennell
- Peter Eichman
- Daniel Lamb
- Ben Cail
- Andrew Woods
- Thomas Bernhart
- Jon Roby
...
- Announcements
- Sprint checking
- Round robin
- Ben PennelPennell
- Binary GET, POST done
- Binary PUT is in Review
- PATCH binary and Fixity checks might be the next steps
- Jon
- confirmed that FCREPO-3169 is fixed, currently have a PR in for FCREPO-3177 and will be working on FCREPO-3168, FCREPO-3026 and FCREPO-3122 and see how far I get by the end tomorrow
- Andrew
- 2020 Sprints - Fedora 6#2020SprintsFedora6-Migration-utils
- Migration utils this sprint is bug fixes and minor new features
- Doesn't know what to do with the .fcrepo directory stuff at the moment in the migration utils
- Q: is fedora 6 meant to be able to handle a ocfl repo that wasn't made for fcrepo6?
- Yes
- Can we start from OCFL copied from one fcrepo to another?
- What does rebuildability look like? On demand? Flag that has to be enabled? Command/User interaction?
- Peter Winckles
- Mostly local stuff
- Looked at bugs for resources not being closed in migration util
- Danny
- Done some refactoring in 3188
- PR for getting Archival groups working
- Ben PennelPennell
- Rebuild on start would be a valuable next step for opening the door to revealing what happens next, over CRUD completeness. Danny may focus on this next.
- Check in with Peter E about containment and if support is needed.
- Round robin
- -
- Pairtrees:
- Andrew Woods : let's avoid creating
- PUT to a/b/c (where a does not exist : should it
- create a, b, and c as basic containers?
- would this be backwards compatible?
- No because it would change the LDP structure of the resources
- would this be backwards compatible?
- fail because a and b don't exist?
- this would be ideal
- Succeed but create pairtrees
- should be avoided if we can
- Succeed, creating new resource at created URL, but not filling in missing parents as resources
- this would be the best scenario, makes the URIs semantics less important to functionality
- introduces complications:
- A number of parts of the code base make assumptions based on URI hierarchy.
- Situations where client creates a/b/c, and then creates a/b. Would fedora have to change containment of c from a to b? Or fail?
- create a, b, and c as basic containers?
- Jared is willing to look at fcrepo4/5 to document existing behavior
- Danny concerned with user errors if semantics of uris don't matter anymore
- Andrew advocating for determining what degree of backwards compatibility is required, not just doing things because of what previous versions did.
- Danny will put together email to gather community feedback, might be helpful to create a document that users can comment on
- PUT to a/b/c (where a does not exist : should it
- Andrew Woods : let's avoid creating
- Build Fedora 6 docker container
- Thomas - Could we build a docker at the end of the CI?
- Existing docker work: Deployment Tooling
- Thomas interested in just a fedora 6 docker container, without the additional environment
- Since we are building with Travis, all we need is one or two steps in the pipeline to produce this
- Would push the fedora 6 docker container to dockerhub. Might need an organization for it
- Thomas will create a few tickets:
1) setup dockerhub org, :Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3194
2) update travis with simple docker file:Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3193
Actions
- Clarify in in documentation that multiple simultaneous writes to OCFL are not supported
...