...
- Danny Bernstein
- Peter Eichman
- Bethany Seeger
- Jared Whiklo
- Andrew Woods
- Kevin Ford
- Ben Pennell
- Aaron Birkland
- Mohamed Mohideen Abdul Rasheed
Agenda
Announcements
- Sprint 2 Progress
Open questions:
- Shall we stop rejecting PUT requests that only contain SMTs in addition to your chosen triples? (Jared Whiklo )?
- Current situation: to replace non-server managed triples in RDF you must
- GET with `-H"Prefer: return=representation; omit=\"http://fedora.info/definitions/v4/repository#ServerManaged\""` and PUT with `-H"Prefer: handling=lenient; received=minimal"`
- Does the above conflict with https://fcrepo.github.io/fcrepo-specification/#http-put-ldprs
- Also seems to make complicated what should be a simple thing for the user to accomplish.
- Documentation of SMTs:
- Related questions:
- What are our SMTs? What is the impact of allowing them to be modified?
- What is an acceptable workflow for changing interaction models? Does the presence of a matching rdf:type in the RDF matter?
- What is an acceptable workflow for updating the properties of a resource?
- What is an acceptable workflow for restoring a version? (either from a memento or from a local export)
- Should GET ONLY return SMTs when specifically requested?
- Essentially, reverse the current behavior by requiring an "include" header instead of an "omit"
- Should PreferContainment header be considered a subset of SMTs i.e. should they be suppressed on omit SMT? (Not relevant if we going to reverse the current behavior)
- Shall we make all resources versionable by default?
- Follow-on question: Should it be possible to make resources non-versionable? In other words, are we saying, everything is versionable, period?
- Implications:
- Remove DELETE LDPCv
- Remove "Enable Versioning" from HTML UI
- Shall we stop rejecting PUT requests that only contain SMTs in addition to your chosen triples? (Jared Whiklo )?
<your agenda item here>
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
...