Page History

...

1. Sprint Update
   
   1. Board
   2. Backlog
   3. List View of All Unclosed
2. Update on  Ben Pennell's ongoing work on mementos of binaries and their descriptions.
   1. Proposed structure for all binaries

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

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

   : 
   1. Are we comfortable with messages emitted?

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

   , are there any  locations/paths that are designated to hold those ACLs created

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

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

   1. architecture question raised on Slack: http-api and auth-webac dependencies
7. Planning for the Transition:  Two Fledgeling Efforts in need of volunteers.
   

   1. Adopters Guide

   2.  Breaking Changes Between Fedora 4.7.x and 5.0.0
8. Supporting COAR Next Generation Repositories recommended technologies in Fedora
   1. Signposting
   2. ResourceSync
   3. others?
9. 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

...

1. COAR some recommendations for behaviours or technologies for next generation repositories.
   1. A list of things that Fedora already does, but some to consider as an addition or plugin. Some may have been considered.
   2. Signposting - a set of HTTP Headers to allow machine readable data to be added as headers.
   3. Has there been any discussion or consideration of these technologies for use before David takes it to the leaders.
   4. Its likely we will see a push for some of this type of stuff from a strategic level, there was a meeting of this group at CNI. Some members of the group said they might be able to get some funding for this.
   5. Please review the list and have some idea of whether we think it is applicable at the Fedora level or API-X level.
   6. There has been previous discussion of Linked Data Notifications which could be one option.
   7. Activity Streams Paging model might be a way to deal with the many members problem.
2. Couple of documentation efforts that are underway. Not sure if we will get to them on the current sprint, but if you are not on the sprint and would like to help out with one of these efforts. Please reach out to Danny (email/slack) and he'll help you get started.
   1. Adopters guide is around the API transition from Fedora 4.7 to Fedora 5.0
   2. Breaking changes is around the Modeshape implementation.
3. Sprint is moving along and have closed quite a few issues.
   1. Any concerns about the process for the sprint?

Actions