...
- Longshou Situ
- Unknown User (acoburn)
- Esmé Cowles
- Yinlin Chen
- Nick Ruest
- Bethany Seeger
- Aaron Birkland
- Jared Whiklo Jack Hill
- Jim Coble
- Andy Wagner
- Jim Coble
- Andrew Woods
- Jennifer Lindner
- Daniel Lamb
- Doron Shalvi
- Michael Durbin
Agenda
- Updates and Announcements
- Fedora 4.6.0 has been released!
- Registration is open for Fedora Camp NYC November 28-30
- Archivematica Camp - updates? outcomes?
- Import/Export sprint update
- Linked Data Notifications - roll into Fedora as an fcrepo-exts project?
- GraphQL - roll into Fedora as an fcrepo-exts project?
- Process for deprecating fcrepo-transform
- concurrency
- Revisit default behavior on PUT requests containing RDF bodies:
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1928 - Fedora 4.7.0 planning
- Depends on community verification of /fcr:backup and /fcr:restore
Status of "in-flight" tickets
Expand Jira server DuraSpace JIRA jqlQuery filter=13202 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
...
Please squash a bug!
Expand Jira server DuraSpace JIRA jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Tickets resolved this week:
Expand Jira server DuraSpace JIRA jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Tickets created this week:
Expand Jira server DuraSpace JIRA jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
Minutes
- Updates and Announcements
- Fedora 4.6.0 has been released!
- Last release that will be dependent on ModeShape 4. Master branch is now dependent on ModeShape 5 and is expected to be the basis for release 4.7.
- Release Notes will be updated to call out changes that necessitated a new major release (i.e., 4.6 instead of 4.5.2).
- There is now a mandatory database config item. 4.6.0 no longer defaults to LevelDB.
- Registration is open for Fedora Camp NYC November 28-30
- Archivematica Camp - updates? outcomes?
- Not much outcome in terms of Fedora - Archivematica hacking
- Import/Export sprint update
- Sprint began on Monday. Goal is to complete Phase 1 priorities.
- So far, sprint is basically through Phase 1 a, b, and c sub-priorities
- Fedora 4.6.0 has been released!
- Linked Data Notifications - roll into Fedora as an fcrepo-exts project? Unknown User (acoburn)
- Web resources can be linked to an inbox. Clients can then create events on that inbox.
- Some minor contradictions between Fedora and the Linked Data Notifications spec – e.g., in the absence of an Accept header, Fedora will return Turtle and Linked Data Notifications spec calls for JSON-LD in that case.
- Is this worth including as an fcrepo-exts project?
- Examples of what it would be used for? Dropping in notices about resource changes and specific out-of-band events associated with a resource; e.g., photo of college president gets used in a publication.
- Would existing audit functionality allow handling these kinds of events? Currently, no clear way to get from a resource to the audit events associated with that resource (though there is to go from the audit event to the resource).
- Linked Data Notifications has the advantage of having a spec behind it. We would not be making up our own thing.
- Adding this to fcrepo-exts seems to pose no conflict with the intent of fcrepo-exts (a place for interesting functionality related to Fedora that isn't core).
- Unknown User (acoburn) will work on this, though it may be a while before he gets to it.
- GraphQL - roll into Fedora as an fcrepo-exts project? Unknown User (acoburn)
- Most of Fedora deals with a resource as a whole.
- GraphQL is a draft spec for querying REST endpoints and returning only requested data.
- Unknown User (acoburn) will likely experiment with it locally at Amherst and later move it to a fcrepo namespace if it looks like it may be of wider use.
- Process for deprecating fcrepo-transform Andrew Woods
- 4.6.0 still has fcrepo-transform as part of webapp-plus. Work has been done to pull the functionality into a Camel component.
- 4.6.0 returns a deprecation warning header. The plan is to remove it from 4.7 and provide documentation on how to use the new Camel component functionality as a replacement.
- Anything else we should do to inform the community about this particular deprecation (or deprecations in general)? No additional suggestions.
- concurrency
- Closely spaced PUT's to the same named resource can result in resources with same name, except for array type suffix.
- Michael Durbin is working on PR that involves locking.
- How aggressively do we want to lock or do we want to lock at all?
- Opinions
- What Michael Durbin is doing seems to address the issue.
- Any counter-arguments? A. Soroka (not on call) may have some?
- Short-comings of current solution
- Pairtree nodes need to be locked. Michael Durbin will incorporate this.
- Doesn't work with transactions. Note this for now and decide later whether to address.
- Would proposed approach potentially result in long-blocked requests if putting to same part of pairtree as a large binary PUT? Michael Durbin will see how hard it would be to address this concern.
- Consensus is to move forward with proposed approach.
- Longshou Situ is also working on this at the ModeShape level: https://issues.jboss.org/browse/MODE-2624.
- Revisit default behavior on PUT requests containing RDF bodies:
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1928 - Change default behavior of PUT request. Postpone to next call.
- To consider in the meantime:
- How does proposed change align with LDP specs?
- Is the proposed change the desired behavior?
- How does the http requirement for idempotency factor in?
- Fedora 4.7.0 planning – Postponed to next call.