...
- Danny Bernstein
- Andrew Woods
- Peter Winckles
- Ben Pennell
- Ben Cail
- David Wilcox
- Daniel Lamb
- Calvin Xu
- Esmé Cowles
- Jared Whiklo
- Thomas Bernhart
Agenda
- Announcements/Updates
- Planned Breaking Changes (standing topic)
- Mementos
- Binary and Binary Description Mementos: to version together or apart?
- AG memento behavior (discussed at the bottom of the above document)
- Delete mementos?
- PR Round Up
- Run ITests against all DBs
- Finish fleshing out new storage layer (This PR is blocking two additional PRs that I have ready that depend on it)
- FCREPO-3399 - External URI case sensitivity and handling changes
- Implements rdf_type parameter and output field in simple search.
- do not index deleted resources on rebuild
- High availability
- The use case we've been hearing about
- What would it take for us to supposupport
- Fedora 6 Testing
Your Topic Here
Expand title Tickets resolved this week... Jira server DuraSpace JIRA jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
...
In Review
Expand Jira server DuraSpace JIRA jqlQuery filter=13100 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Please squash a bug!
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Tickets resolved this week:
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Tickets created this week:
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
Notes
- Announcements/Updates
- Fedora
- IMLS grant awarded: F3 -> F6
Valkyrie testing with F6
- Seven test failures: all related to inbound references
- More Samvera tests should be run
- What is needed from the Fedora query service?
- May need to update how Samvera stores model types (rdf:type?)
Breaking changes?
- None
Sprint updates
- Upgrade-utils
- 4.7->5.0 branch has an old PR that needs review/merge
- Versions and ACLs are not included in that PR
- Action: Ben to review/merge: https://github.com/fcrepo4-exts/fcrepo-upgrade-utils/pull/17
- Will support multiple migration paths
- 4->5, 5->6, 4->6
- Will be integrating fcrepo-storage-ocfl
- Will need to eventually support archival groups in 5->6 migrations
- 4.7->5.0 branch has an old PR that needs review/merge
- Fcrepo-storage-ocfl
- 'create-date' can be passed in when creating mementos
- Waiting on Ben's review of: https://github.com/fcrepo4-exts/fcrepo-storage-ocfl/pull/3
- External content should now be working - PR in-review
- Now able to create archival groups in HTML UI
- Need review/merge: https://github.com/fcrepo4/fcrepo4/pull/1736
Fedora 6 Testing
- NLM testing updates
- Currently provisioning MySQL 8 - should be ready in ~1 week
- Running into issue with Tomcat security manager
- Using H2 database, 60k+ objects hangs
- Initial performance tests underway
- Andrew Woods to create tickets for: terraform: configure fedora version, and mounting volume
High Availability
- No time for full discussion
- Preview: how do we support this use case
- user group just wrapped up. 35-40 people. Good participation, and interest in doing more in the future.
- Planned Breaking Changes (standing topic)
- None
- Mementos
- Binary and Binary Description Mementos: to version together or apart?
- Leaning towards "Versioning together". Fairly clean approach, and can use transactions to get around double mementos.
- AG memento behavior (discussed at the bottom of the above document)
- Should all AG resources be versioned together or should the resources be versioned independently?
- After much discussion it was decided that the current main behavior is best
- AG time maps contain the mementos for all of their children
- AG part time maps only contain mementos that apply to the specific resource
- Mementos cannot be created directly on AG parts. They must be created at the AG level
- After much discussion it was decided that the current main behavior is best
- Should we allow creating mementos when there are no content changes?
- Currently, the thought is no. The current behavior is that the request returns success with a link to the head memento
- Should we be updating something other than the last modified timestamp?
- There has to be a binary change to a resources header file in order for a memento to exist. The current idea is to touch the last modified date so that the headers change. The downside of this is that the last modified date now no longer represents the last time the resource content changed. If this is a problem, we will need to touch a different field in the headers.
- Should all AG resources be versioned together or should the resources be versioned independently?
- Delete mementos?
- Didn't get covered
- Binary and Binary Description Mementos: to version together or apart?
Actions
- Danny Bernstein to ensure that a JIRA exists for scenario of transaction does not succeed completely, but rollback does succeed (see: 2020-08-13- Fedora Tech Meeting)
- Peter Winckles to create a JIRA to investigate support for optimistic locking and mutable head (see: 2020-08-13- Fedora Tech Meeting)
- Who: Clarify in documentation that multiple simultaneous writes to OCFL are not supported
- Peter Winckles Create a Jira to update the locations files stored in OCFL
- migration-utils - translating RELS-EXT/INT into RDF in Fedora 6: is the functionality there? If not, add it.
...