...

• Danny Bernstein
• Andrew Woods 
• Bethany Seeger 
• Jared Whiklo 
• Peter Eichman  
• Doron Shalvi 
• Kevin Ford
• Ben Pennell
• James Silas Creel
• David Wilcox
• Aaron Birkland

Agenda

1. Sign up for the upcoming Alignment Sprint
2. Sprint planning
   1. Close the loop on Ben Pennell's exposition of options for implementing mementos of binaries and their descriptions
      
      1. Outstanding questions:
         1. Should we have LDP responses for mementos?
         2. Does a memento object act as a full LDP object, particularly with respect to headers?
         3. Are the edge things (such as headers) important for our users' workflows?  Should we handle these?
         4. Is versioning for items only currently in the repo, or all items that have ever been in repo?
         5. Should Fedora keep versions of items that have been deleted?
      2. feedback from leadership?
   2. WEB ACLs
      1. Peter Eichman's assessment of moving WebACLs from modeshape.

      2. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2742

         
         
         1. Do we still want to support the current scheme for the sake of backward compatibility?

      3. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2743

         
         
         1. Discuss Aaron Birkland's questions in the issue comments section
         2. Should we consider abandoning Section 5.4 Specify ACL on resource creation in light of this issue as well as 

            Jira
            server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2744

             and 

            Jira
            server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2745

            ?
   3. Documentation mini sprint
      1. Who is interested? 
      2. Timeframe
      3. Objective
      4. Next steps
   4. "Pre-sprint" work that can be done
   5. Reading work? 
   6. Low-hanging JIRA tickets:
      1. ?
3. Shall we consider using Duraspace checkstyle rules?
   
   1. Checkstyle Analysis
   2. Repo
   3. There are three rules in the fedora checkstyle rules that are not in the Duraspace checkstyle rules: 
      
      1. requiring @author in javadoc
      2. "final" required for parameter variables
      3. "final" required for local variables
   4. There are 40-odd lines in fcrepo4  that would need to be corrected to roll this out.
4. OCFL update from Andrew Woods
5. ?

...

1. 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

   
   

2. 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

   
   

3. 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

   
   

Minutes

...

Sprint

...

1. Document has been shared on chat and listserv.  Includes ideas from Esme and Ben.  There have been many suggestions on different ways to create and retrieve binary mementos.
2. What kind of link headers should be provided by Fedora?  Should Fedora determine if a binary and description memento are related?
3. Three possible implementations noted:
   1. Create mementos one by one.  Two requests would be needed.
   2. Similar to 1. above, except on retrieval Fedora would provide a "described by" link to the original resource instead of attempting negotiation.
   3. A single request would create both a binary and description memento, when importing a historical memento.  The description memento would then effectively be a newly created node.
4. Historical mementos are primarily for importing from another Fedora, but could also be used to create additional versions from scratch.
5. Bethany prefers an approach where a single post creates both.  Jared prefers the second approach because it alleviates the server from having to handle negotiation.
6. The group has previously agreed to replace references between resources with literals.  Should we handle headers the same way?
7. Possibly, we are stretching the Memento spec.  When requesting a Memento object, how sould we respond in order to still be compliant with LDP?
8. Deletions
   1. If the canonical object is deleted, the versions are also deleted.  Perhaps split binaries and descriptions into seaprate objects?  Seems not worthwhile.
   2. Should Fedora keep versions of items that have been deleted, so that these could be restored?  Memento is capable of doing so if we desire.  Makes sense in a Disaster Recovery scenario.  To do so, we'd have to move the timemaps out into a separate location in the repo.
   3. Conceptually, is versioning for items only currently in the repo, or all items that have ever been in repo?
9. Outstanding questions:
   1. Should we have LDP responses for mementos?Does a memento object act as a full LDP object, particularly with respect to headers?
   2. Are the edge things (such as headers) important for our users' workflows?  Should we handle these?
   3. Is versioning for items only currently in the repo, or all items that have ever been in repo?
   4. Should Fedora keep versions of items that have been deleted?

...

1. Issues with documentation on the wiki were noted.  Is the documentation correct and sufficient?
2. To be discussed in the tech call next week.

...

1. It would be helpful to finish work from the last sprint - creating mementos of resources - before the next sprint begins, to avoid questions and merge conflicts in next sprint.  This work is defined in an existing ticket describing the creation of binary mementos.  To aid this process, it would be helpful to make decisions on binary mementos now.
2. The next sprint will focus on mementos and ACLs.

3. Peter promised an investigation into moving WebAC from ModeShape to the web layer.

4. The WebAC tickets fall into a few categories: 
   
   1. Fixing headers, aligning with WebAC spec.
   2. Dealing with ACL append mode. Tricky / impossible to do at Modeshape layer.
   3. Implementing support for default ACLs. Separate from ACL append issues?
5. Regarding binary versions, we could use input from the community and Fedora leaders before the next Sprint.  Jared will send an email to Fedora leaders to get input.  David recommends presenting a summary in the email including use cases and benefits, with technical details attached.  Fedora leaders will include input from the Islandora and Samvera communities.
6. Also worthwhile to obtain feedback from Fedora leaders on the deletion issue (true deletes or keep a copy to be restored), since this is a broad issue regarding expectations of a repository.
7. All of the above should be discussed at the next sprint planning meeting.

...

Planning

Memento and Binaries

1. Two topics
   • Which of the three approaches should be taken for creating binary/desc mementos
   • Answers to open questions
2. Bethany/Este to respond to BenP's request to list
3. For the normal case of creating a "current" memento, the pattern is relatively clear
   1. The trickiness is in restoring "historic" mementos
4. What headers do we need to return on requests for Fedora Mementos?
   1. Suggestion: enumerate headers to be returned on GET/HEAD of binary and desc mementos
5. What are the interaction use cases for interacting with creating and retrieving binary/desc mementos?
   1. import/export utility may need to capture headers?
6. No clear consensus on recommended approach
7. Deferring for now, but encouraging BenP to move forward with design

WebAC

1. Discussion of new JIRA tickets
   1. fcrepo-2742: suggestion to move to hash-based ACLs
      • deprecate existing ldp:contains approach
      • emphasize the hash-based approach in documentation
      • question to community: is this a tolerable breaking change in Fedora5 or should existing WebAC model be supported (and flagged as deprecated)
2. ACTION: DannyB to create list of breaking changes in Fedora5
3. ACTION: DannyB to send message out to community wrt whether webac breaking change is tolerable

DuraSpace checkstyle

1. Proposal: all DuraSpace projects adopt new checkstyle rules, with custom suppressions
2. No decision yet
   • Need to open resources linked in agenda
3. Would it make sense to create a pull-request?

Actions

•  Danny Bernstein: to create list of breaking changes in Fedora5
•  Danny Bernstein: to send message to community wrt whether webac breaking change is tolerable in Fedora5 (or should continue to be supported, and deprecated)
•  Peter Eichman Yinlin Chen: Review and update ACL creation documentation: Quick Start with WebAC
•  Ben Pennell: Create a wiki page documenting options for mementos of binaries and their descriptions